Communication method and apparatus

Abstract

Embodiments of the present application provide a communication method and apparatus, relating to the field of wireless communication. When a terminal moves from the coverage range of a second network device to the coverage range of a first network device and there is data to be transmitted, the second network device can decide whether to request a handover of the data channel from the core network device, improving the flexibility of data processing. The method includes: The first network device receives a first request message for requesting to resume a suspended radio resource control connection and uplink data from the terminal; The first network device sends a second request message to the second network device according to the first request message and the uplink data, so that the second network device determines whether to release a first data channel between the second network device and the core network device; or determines whether to send the context of the terminal to the first network device.

Description

Technical Field

[0001] This application relates to the field of wireless communication, and in particular, to a communication method and apparatus. Background Art

[0002] In a communication system, when a terminal has data to transmit, a radio resource control (RRC) connection can be established between the terminal and a network device, and a data channel can be established between the network device and a core network device. At this time, the terminal is in the radio resource control connected (RRC-connected) state. The terminal carries the data to be sent in an RRC message and sends it to the network device. After receiving the data, the network device sends the data to the core network device through the data channel. After the communication ends, the terminal in the RRC-connected state can be switched from the RRC-connected state to the radio resource control inactive (RRC-inactive) state by receiving an RRC connection release message from the network device.

[0003] Subsequently, if the terminal moves from the coverage area of this network device to the coverage area of another network device and has data to transmit again, the terminal will send the data to be transmitted to the other network device. After receiving the data, the other network device will request the core network device to establish a data channel with the other network device and request the core network device to release the data channel with the network device. That is to say, after receiving the data, the other network device will request the core network device to switch the data channel. However, the movement of the terminal is random, and it is very unlikely that the terminal is still within the coverage area of the network device during this data transmission when the terminal has data to transmit next time. Therefore, when the terminal moves into the coverage area of a new network device and has data to transmit each time, it is not necessary for the new network device to request the core network device to switch the data channel every time. Summary of the Invention

[0004] Embodiments of this application provide a communication method and apparatus. When a terminal moves from the coverage area of one network device to the coverage area of another network device and has data to transmit, the one network device can decide whether to request the core network device to switch the data channel, improving the flexibility of data processing.

[0005] To achieve the above object, the embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, an embodiment of the present application provides a communication method, which includes: a first network device receives a first request message and uplink data from a terminal, where the first request message is used to request to resume a suspended radio resource control (RRC) connection; the first network device sends a second request message to a second network device according to the first request message and the uplink data, where the second network device is the previous serving network device of the terminal, and the second request message includes information about the uplink data; the second request message is used to request the second network device to release a first data channel between the second network device and a core network device; or, the second request message is used to request the second network device to send the context of the terminal to the first network device.

[0007] For the method provided in the first aspect above, after receiving the first request message from the terminal, the first network device may send the second request message to the second network device according to the first request message, so that the second network device determines whether to release the first data channel according to the second request message, or so that the second network device determines whether to send the context of the terminal to the first network device according to the second request message. In this way, the second network device can decide whether to release the first data channel according to the second request message, or the second network device can decide whether to send the context of the terminal to the first network device according to the second request message, improving the flexibility of the first network device and the second network device in processing uplink data.

[0008] In combination with the first aspect, in a first possible implementation manner, the second request message is used to request the second network device to release the first data channel between the second network device and the core network device, and the information about the uplink data is used by the second network device to determine whether to release the first data channel; or, the second request message is used to request the second network device to send the context of the terminal to the first network device, and the information about the uplink data is used by the second network device to determine whether to send the context of the terminal to the first network device. Based on the above method, the information about the uplink data is used by the second network device to determine whether to release the first data channel, and the second network device can decide whether to release the first data channel according to the information about the uplink data; the information about the uplink data is used by the second network device to determine whether to send the context of the terminal to the first network device, and the second network device can decide whether to send the context of the terminal to the first network device according to the information about the uplink data. In this way, the flexibility of the first network device and the second network device in processing uplink data is improved.

[0009] Combined with the first aspect and the first possible implementation manner of the first aspect, in the second possible implementation manner, the information of the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the first network device, and the second indication information is used to indicate that the uplink data is not included in the first request message. Based on the above method, the second network device can decide whether to release the first data channel according to various information, or decide whether to send the context of the terminal to the first network device.

[0010] Combined with the first aspect and various possible implementation manners of the first aspect, in the third possible implementation manner, the method further includes: the first network device receives a buffer status report from the terminal, and the buffer status report is used to indicate the data volume of the remaining uplink data; the second request message further includes the information of the data volume of the remaining uplink data. Based on the above method, the first network device can also send the information of the data volume of the remaining uplink data to the second network device, so that the second network device determines whether to release the first data channel according to the information of the data volume of the remaining uplink data, or so that the second network device determines whether to send the context of the terminal to the first network device according to the information of the data volume of the remaining uplink data.

[0011] Combined with the first aspect and various possible implementation manners of the first aspect, in the fourth possible implementation manner, the second request message further includes third indication information, and the third indication information is used to indicate that the first network device has the ability to configure authorization for the terminal. Based on the above method, the first network device can also send the third indication information to the second network device, so that the second network device determines whether to release the first data channel according to the third indication information, or so that the second network device determines whether to send the context of the terminal to the first network device according to the third indication information.

[0012] Combined with the first aspect, the first possible implementation manner and the second possible implementation manner of the first aspect, in the fifth possible implementation manner, the second request message is used to request the second network device to release the first data channel between the second network device and the core network device, and the method further includes: the first network device receives a first response message from the second network device; the data volume of the uplink data is greater than or equal to a first threshold, and the first response message is used to indicate that the second network device releases the first data channel; or, the data volume of the uplink data is less than or equal to the first threshold, and the first response message is used to indicate that the second network device retains the first data channel. Based on the above method, the second network device releases the first data channel when the data volume of the uplink data is greater than or equal to the first threshold, and retains the first data channel when the data volume of the uplink data is less than or equal to the first threshold.

[0013] Combining the third possible implementation manner and the fourth possible implementation manner of the first aspect, in the sixth possible implementation manner, the second request message is used to request the second network device to release the first data channel between the second network device and the core network device. The method further includes: the first network device receives a first response message from the second network device; the data volume of the remaining uplink data is greater than or equal to a second threshold, and the first response message is used to instruct the second network device to release the first data channel; or, the data volume of the remaining uplink data is less than or equal to the second threshold, and the first response message is used to instruct the second network device to retain the first data channel. Based on the above method, the second network device releases the first data channel when the data volume of the remaining uplink data is greater than or equal to the second threshold, and retains the first data channel when the data volume of the remaining uplink data is less than or equal to the second threshold.

[0014] Combining the fourth possible implementation manner of the first aspect, in the seventh possible implementation manner, the second request message is used to request the second network device to release the first data channel between the second network device and the core network device. The method further includes: the first network device receives a first response message from the second network device, and the first response message is used to instruct the second network device to release the first data channel; or, the first response message is used to instruct the second network device to retain the first data channel. Based on the above method, when the second request message includes third indication information, the second network device can either release the first data channel or retain the first data channel.

[0015] Combining the fifth possible implementation manner, the sixth possible implementation manner and the seventh possible implementation manner of the first aspect, in the eighth possible implementation manner, the first request message includes the configuration authorization capability of the terminal; or, the first response message includes the configuration authorization capability of the terminal. Based on the above method, the first network device can obtain the configuration authorization capability of the terminal in two ways, namely, reported by the terminal or sent by the second network device, so that the first network device can determine whether to configure authorization for the terminal.

[0016] Combining the eighth possible implementation manner of the first aspect, in the ninth possible implementation manner, the first response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, and the arrival timing of the terminal evaluated by the second network device. Based on the above method, the first response message can further include the information of the service model, so that the first network device can configure authorization for the terminal according to the information of the service model.

[0017] Combined with the fifth to ninth possible implementation manners of the first aspect, in the tenth possible implementation manner, the first response message is further used to establish a communication tunnel between the first network device and the second network device, where the communication tunnel is used to transmit the uplink data, and the communication tunnel has a corresponding relationship with the source logical channel identifier. Based on the above method, the second network device can also establish a communication tunnel with the first network device through the first response message, so that the first network device can send uplink data to the second network device through the communication tunnel subsequently.

[0018] Combined with the third and sixth possible implementation manners of the first aspect, in the eleventh possible implementation manner, if the data volume of the remaining uplink data is greater than or equal to a second threshold, the method further includes: the first network device establishes an RRC connection with the terminal. Based on the above method, when the data volume of the remaining uplink data is greater than or equal to the second threshold, the first network device can also establish an RRC connection with the terminal to receive the remaining uplink data from the terminal.

[0019] Combined with the first aspect and the first to fourth possible implementation manners of the first aspect, in the twelfth possible implementation manner, the second request message is used to request the second network device to send the context of the terminal to the first network device, and the method further includes: the first network device receives a second response message from the second network device; the second response message includes the configuration of the source packet data convergence protocol and the configuration of the source radio link control. Based on the above method, the second network device can send the context of the terminal to the first network device, so that the first network device can process the uplink data processed by the terminal according to the context of the terminal to obtain the uplink data before the terminal processes it.

[0020] Combined with the twelfth possible implementation manner of the first aspect, in the thirteenth possible implementation manner, the first request message includes the configuration authorization capability of the terminal; or, the second response message further includes the configuration authorization capability of the terminal. Based on the above method, the first network device can obtain the configuration authorization capability of the terminal in two ways, namely, reported by the terminal or sent by the second network device, so that the first network device can determine whether to configure authorization for the terminal.

[0021] Combining the twelfth possible implementation manner and the thirteenth possible implementation manner of the first aspect, in the fourteenth possible implementation manner, the second response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, or the arrival timing of the terminal evaluated by the second network device. Based on the above method, the second response message may further include information about the service model, so that the first network device can configure authorization for the terminal according to the information about the service model.

[0022] Combining the twelfth possible implementation manner to the fourteenth possible implementation manner of the first aspect, in the fifteenth possible implementation manner, the second response message is further used to indicate the establishment of a communication tunnel between the first network device and the second network device, and the communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier. Based on the above method, the second network device may also establish a communication tunnel with the first network device through the second response message, so that the first network device can send uplink data to the second network device through the communication tunnel subsequently.

[0023] Combining the first aspect and various possible implementation manners of the first aspect, in the sixteenth possible implementation manner, the first request message and the uplink data are multiplexed in one message. Based on the above method, the first network device can receive the first request message and the uplink data simultaneously, saving signaling overhead.

[0024] In a second aspect, an embodiment of the present application provides a communication method, and the method includes: the second network device receives a second request message from the first network device, the second request message includes information about uplink data, and the second request message is used to request the second network device to release a first data channel between the second network device and a core network device, and the second network device is a previous serving network device of the terminal; the second network device releases the first data channel according to the second request message; or, the second network device receives a second request message from the first network device, the second request message includes information about uplink data, and the second request message is used to request the second network device to send the context of the terminal to the first network device, and the second network device is a previous serving network device of the terminal; the second network device sends the context of the terminal to the first network device according to the second request message.

[0025] For the method provided in the second aspect above, after receiving the second request message, the second network device may release the first data channel according to the second request message, or send the context of the terminal to the first network device according to the second request message. In this way, the second network device can decide whether to release the first data channel according to the second request message, or the second network device can decide whether to send the context of the terminal to the first network device according to the second request message, improving the flexibility of the first network device and the second network device in processing uplink data.

[0026] Combined with the second aspect, in a first possible implementation manner, the information of the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the first network device, and the second indication information is used to indicate that the uplink data is not included in the first request message, and the first request message is used for the terminal to request the first network device to resume the suspended RRC connection. Based on the above method, the second network device can decide whether to release the first data channel according to various information, or decide whether to send the context of the terminal to the first network device.

[0027] Combined with the second aspect and the first possible implementation manner of the second aspect, in a second possible implementation manner, the second request message further includes information on the data volume of the remaining uplink data. Based on the above method, the second network device can further determine whether to release the first data channel according to the information on the data volume of the remaining uplink data, or the second network device can further determine whether to send the context of the terminal to the first network device according to the information on the data volume of the remaining uplink data.

[0028] Combined with the second aspect and various possible implementation manners of the second aspect, in a third possible implementation manner, the second request message further includes third indication information, and the third indication information is used to indicate that the first network device has the ability to configure authorization for the terminal. Based on the above method, the second network device can further determine whether to release the first data channel according to the third indication information, or the second network device can further determine whether to send the context of the terminal to the first network device according to the third indication information.

[0029] Combined with the second aspect and various possible implementation manners of the second aspect, in the fourth possible implementation manner, the second request message is used to request the second network device to release a first data channel between the second network device and the core network device. The method further includes: the second network device sends a first response message to the first network device; when the data volume of the uplink data is greater than or equal to a first threshold, the first response message is used to instruct the second network device to release the first data channel; or when the data volume of the uplink data is less than or equal to the first threshold, the first response message is used to instruct the second network device to retain the first data channel. Based on the above method, the second network device releases the first data channel when the data volume of the uplink data is greater than or equal to the first threshold, and retains the first data channel when the data volume of the uplink data is less than or equal to the first threshold.

[0030] Combined with the second possible implementation manner and the third possible implementation manner of the second aspect, in the fifth possible implementation manner, the second request message is used to request the second network device to release a first data channel between the second network device and the core network device. The method further includes: the second network device sends a first response message to the first network device; when the data volume of the remaining uplink data is greater than or equal to a second threshold, the first response message is used to instruct the second network device to release the first data channel; or when the data volume of the remaining uplink data is less than or equal to the second threshold, the first response message is used to instruct the second network device to retain the first data channel. Based on the above method, the second network device releases the first data channel when the data volume of the remaining uplink data is greater than or equal to the second threshold, and retains the first data channel when the data volume of the remaining uplink data is less than or equal to the second threshold.

[0031] Combined with the third possible implementation manner of the second aspect, in the sixth possible implementation manner, the second request message is used to request the second network device to release a first data channel between the second network device and the core network device. The method further includes: the second network device sends a first response message to the first network device; the first response message is used to instruct the second network device to release the first data channel; or the first response message is used to instruct the second network device to retain the first data channel. Based on the above method, when the second request message includes third indication information, the second network device may release the first data channel or retain the first data channel.

[0032] Combined with the fourth possible implementation manner to the sixth possible implementation manner of the second aspect, in the seventh possible implementation manner, the first request message includes the configuration authorization capability of the terminal; or the first response message includes the configuration authorization capability of the terminal. Based on the above method, the first network device can obtain the configuration authorization capability of the terminal in two ways, namely, reported by the terminal or sent by the second network device, so that the first network device can determine whether to configure authorization for the terminal.

[0033] Combined with the seventh possible implementation manner of the second aspect, in the eighth possible implementation manner, the first response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, and the arrival timing of the terminal evaluated by the second network device. Based on the above method, the first response message may further include information about the service model, so that the first network device configures authorization for the terminal according to the information about the service model.

[0034] Combined with the fourth possible implementation manner to the eighth possible implementation manner of the second aspect, in the ninth possible implementation manner, the first response message is further used to establish a communication tunnel between the first network device and the second network device, and the communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier. Based on the above method, the second network device may also establish a communication tunnel with the first network device through the first response message, so that the first network device subsequently sends uplink data to the second network device through the communication tunnel.

[0035] Combined with the second aspect and the first possible implementation manner to the third possible implementation manner of the second aspect, in the tenth possible implementation manner, the second request message is used to request the second network device to send the context of the terminal to the first network device, and the method further includes: the second network device sending a second response message to the first network device; the second response message includes the configuration of the source packet data convergence protocol and the configuration of the source radio link control. Based on the above method, the second network device may send the context of the terminal to the first network device, so that the first network device processes the uplink data received and processed by the terminal to obtain the uplink data before the terminal is processed.

[0036] Combined with the tenth possible implementation manner of the second aspect, in the eleventh possible implementation manner, the first request message includes the configuration authorization capability of the terminal; or, the second response message further includes the configuration authorization capability of the terminal. Based on the above method, the first network device may obtain the configuration authorization capability of the terminal in two ways, namely, reported by the terminal or sent by the second network device, so that the first network device determines whether to configure authorization for the terminal.

[0037] Combining the tenth possible implementation manner and the eleventh possible implementation manner of the second aspect, in the twelfth possible implementation manner, the second response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, and the arrival timing of the terminal evaluated by the second network device. Based on the above method, the second response message may further include information about the service model, so that the first network device configures authorization for the terminal according to the information about the service model.

[0038] Combining the tenth possible implementation manner to the twelfth possible implementation manner of the second aspect, in the thirteenth possible implementation manner, the second response message is further used to establish a communication tunnel between the first network device and the second network device, and the communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier. Based on the above method, the second network device may also establish a communication tunnel with the first network device through the second response message, so that the first network device subsequently sends uplink data to the second network device through the communication tunnel.

[0039] Combining the second aspect and various possible implementation manners of the second aspect, in the fourteenth possible implementation manner, the first request message and the uplink data are multiplexed in one message. Based on the above method, the first network device can receive the first request message and the uplink data simultaneously, saving signaling overhead.

[0040] In a third aspect, an embodiment of the present application provides a communication device, which can implement the method in the first aspect or any possible implementation manner of the first aspect. The device includes corresponding units or components for executing the above method. The units included in the device can be implemented in software and / or hardware manners. The device may be, for example, a terminal, or a chip, a chip system, or a processor that can support the terminal to implement the above method.

[0041] In a fourth aspect, an embodiment of the present application provides a communication device, which can implement the method in the second aspect or any possible implementation manner of the second aspect. The device includes corresponding units or components for executing the above method. The units included in the device can be implemented in software and / or hardware manners. The device may be, for example, a network device, or a chip, a chip system, or a processor that can support the network device to implement the above method.

[0042] In a fifth aspect, an embodiment of the present application provides a communication device, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the device implements the method described in the first aspect or any possible implementation manner of the first aspect.

[0043] In a sixth aspect, an embodiment of the present application provides a communication device, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the device implements the method described in the above second aspect or any possible implementation manner of the second aspect.

[0044] In a seventh aspect, an embodiment of the present application provides a communication device, and the device is used to implement the method described in the above first aspect or any possible implementation manner of the first aspect.

[0045] In an eighth aspect, an embodiment of the present application provides a communication device, and the device is used to implement the method described in the above second aspect or any possible implementation manner of the second aspect.

[0046] In a ninth aspect, an embodiment of the present application provides a computer-readable medium, on which computer programs or instructions are stored. When the computer programs or instructions are executed, the computer executes the method described in the above first aspect or any possible implementation manner of the first aspect.

[0047] In a tenth aspect, an embodiment of the present application provides a computer-readable medium, on which computer programs or instructions are stored. When the computer programs or instructions are executed, the computer executes the method described in the above second aspect or any possible implementation manner of the second aspect.

[0048] In an eleventh aspect, an embodiment of the present application provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer executes the method described in the above first aspect or any possible implementation manner of the first aspect.

[0049] In a twelfth aspect, an embodiment of the present application provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer executes the method described in the above second aspect or any possible implementation manner of the second aspect.

[0050] In a thirteenth aspect, an embodiment of the present application provides a chip, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the chip implements the method described in the above first aspect or any possible implementation manner of the first aspect.

[0051] In a fourteenth aspect, an embodiment of the present application provides a chip, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the chip implements the method described in the above second aspect or any possible implementation manner of the second aspect.

[0052] In a fifteenth aspect, an embodiment of the present application provides a communication system. The system includes the device described in the above third aspect and / or the device described in the above fourth aspect, or the system includes the device described in the above fifth aspect and / or the device described in the above sixth aspect, or the system includes the device described in the above seventh aspect and / or the device described in the above eighth aspect.

[0053] It can be understood that any of the above provided communication devices, chips, computer-readable media, computer program products, or communication systems, etc. are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods, and will not be elaborated here.

[0054] In a sixteenth aspect, an embodiment of the present application provides a communication method, which includes: a first network element receives a first request message and uplink data from a terminal, and the first request message is used to request to resume a suspended radio resource control (RRC) connection; the first network element sends information of the first request message and the uplink data to a second network element according to the first request message and the uplink data.

[0055] For the method provided in the above sixteenth aspect, when the first network element receives the first request message and uplink data from the terminal, it can send the information of the first request message and the uplink data to the second network element according to the first request message and the uplink data, so that the second network element can obtain the context of the terminal according to the information of the uplink data. Only when the second network element obtains the context of the terminal can it process the uplink data. Compared with the situation where the second network element can only send the uplink data to the second network device for processing, the flexibility of the first network element and the second network element in processing the uplink data is improved.

[0056] Combined with the sixteenth aspect, in a first possible implementation manner, the information of the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the first network element, and the second indication information is used to indicate that the uplink data is not included in the first request message. Based on the above method, the second network element can make a decision on whether to request the context of the terminal according to multiple pieces of information.

[0057] Combined with the first possible implementation manner of the sixteenth aspect, in the second possible implementation manner, the method further includes: the first network element receives a buffer status report from the terminal, where the buffer status report is used to indicate the amount of remaining uplink data; the first network element sends information about the amount of the remaining uplink data to the second network element. Based on the above method, the first network element may further send information about the amount of the remaining uplink data to the second network element, so that the second network element determines whether to request the context of the terminal from the second network device according to the information about the amount of the remaining uplink data.

[0058] Combined with the second possible implementation manner of the sixteenth aspect, in the third possible implementation manner, the method further includes: if the amount of the remaining uplink data is greater than or equal to a threshold, the first network element receives a first message from the second network element, where the first message is used to indicate that the first network element establishes an RRC connection with the terminal. Based on the above method, when the amount of the remaining uplink data is greater than or equal to the threshold, the second network element may further indicate that the first network element establishes an RRC connection with the terminal, so that the first network element receives the remaining uplink data from the terminal.

[0059] Combined with the sixteenth aspect and various possible implementation manners of the sixteenth aspect, in the fourth possible implementation manner, the method further includes: the first network element receives a second message from the second network element, where the second message includes the configuration of the source radio link control. Based on the above method, the first network element may further receive the configuration of the source radio link control from the second network element, so that the first network element processes the received uplink data according to the configuration of the source radio link control.

[0060] Combined with the fourth possible implementation manner of the sixteenth aspect, in the fifth possible implementation manner, the second message further includes indication information for indicating a communication tunnel between the second network element and the first network element, where the communication tunnel is used to transmit the uplink data. Based on the above method, the second network element may further indicate to the first network element the communication tunnel between the first network element and the second network element for transmitting the uplink data, so that the first network element sends the uplink data to the second network element through the communication tunnel.

[0061] Combined with the sixteenth aspect and various possible implementation manners of the sixteenth aspect, in the sixth possible implementation manner, the method further includes: the first network element receives a third message from the second network element, where the third message is used to indicate that the first network element deletes the uplink data; the first network element deletes the uplink data according to the third message. Based on the above method, the second network element may further indicate to the first network element to delete the uplink data. In this way, when the first network element cannot parse the uplink data, the first network element can delete the uplink data, saving the storage resources of the first network element.

[0062] Combined with the sixteenth aspect and various possible implementation manners of the sixteenth aspect, in the seventh possible implementation manner, the first request message and the uplink data are multiplexed in one message. Based on the above method, the first network element can receive the first request message and the uplink data simultaneously, saving signaling overhead.

[0063] In a seventeenth aspect, an embodiment of the present application provides a communication method, and the method includes: a second network element receives information about a first request message and uplink data from a first network element; the second network element obtains the context of the terminal according to the information about the first request message and the uplink data.

[0064] For the method in the above seventeenth aspect, the second network element can receive the information about the first request message and the uplink data from the first network element, and obtain the context of the terminal according to the information about the first request message and the uplink data. The second network element can process the uplink data only after obtaining the context of the terminal. Compared with the case where the second network element can only send the uplink data to the second network device for processing, the flexibility of the first network element and the second network element in processing the uplink data is improved.

[0065] Combined with the seventeenth aspect, in the first possible implementation manner, the information about the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the first network element, and the second indication information is used to indicate that the uplink data is not included in the first request message. Based on the above method, the second network element can make a decision on whether to request the context of the terminal from the second network device according to various information.

[0066] Combined with the seventeenth aspect and the first possible implementation manner of the seventeenth aspect, in the second possible implementation manner, the method further includes: the second network element receives information about the data volume of the remaining uplink data from the first network element, and the information about the data volume of the remaining uplink data is used to indicate the data volume of the remaining uplink data. Based on the above method, the second network element can also receive the information about the data volume of the remaining uplink data from the first network element, so that the second network element can determine whether to request the context of the terminal from the second network device according to the information about the data volume of the remaining uplink data.

[0067] Combined with the second possible implementation manner of the seventeenth aspect, in the third possible implementation manner, the method further includes: if the data volume of the remaining uplink data is greater than or equal to a threshold, the second network element sends a first message to the first network element, and the first message is used to indicate that the first network element establishes a radio resource control (RRC) connection with the terminal. Based on the above method, when the data volume of the remaining uplink data is greater than or equal to the threshold, the second network element can also indicate the first network element to establish an RRC connection with the terminal, so that the first network element can receive the remaining uplink data from the terminal.

[0068] Combined with the seventeenth aspect and various possible implementation manners of the seventeenth aspect, in the fourth possible implementation manner, the context of the terminal includes the configuration of the source packet data convergence protocol and the configuration of the source radio link control. Based on the above method, the second network element can obtain the configuration of the source packet data convergence protocol and the configuration of the source radio link control. In this way, the second network element can process the uplink data according to the configuration of the source packet data convergence protocol and the configuration of the source radio link control, improving the flexibility of the first network element and the second network element in processing the uplink data.

[0069] Combined with the fourth possible implementation manner of the seventeenth aspect, in the fifth possible implementation manner, the method further includes: the second network element sends a second message to the first network element, and the second message includes the configuration of the source radio link control in the context of the terminal. Based on the above method, the second network element can also send the configuration of the source radio link control in the context of the terminal to the first network element, so that the first network element can process the uplink data received from the terminal according to the configuration of the source radio link control.

[0070] Combined with the fifth possible implementation manner of the seventeenth aspect, in the sixth possible implementation manner, the second message further includes indication information for indicating a communication tunnel between the second network element and the first network element, and the communication tunnel is used for transmitting the uplink data. Based on the above method, the second network element can also indicate to the first network element the communication tunnel between the first network element and the second network element for transmitting the uplink data, so that the first network element can send the uplink data to the second network element through the communication tunnel.

[0071] Combined with the seventeenth aspect and various possible implementation manners of the seventeenth aspect, in the seventh possible implementation manner, the second network element does not obtain the context of the terminal, and the method further includes: the second network element sends a third message to the first network element, and the third message is used for indicating the first network element to delete the uplink data. Based on the above method, when the second network element does not obtain the context of the terminal, it can also indicate the first network element to delete the uplink data. Since the second network element does not obtain the context of the terminal and cannot send the configuration of the source radio link control to the first network element, the first network element cannot parse the uplink data. Therefore, the second network element indicating the first network element to delete the uplink data can save the storage resources of the first network element.

[0072] Combined with the seventeenth aspect and various possible implementation manners of the seventeenth aspect, in the eighth possible implementation manner, the first request message and the uplink data are multiplexed in one message. Based on the above method, the first network element can receive the first request message and the uplink data simultaneously, saving signaling overhead.

[0073] In an eighteenth aspect, an embodiment of the present application provides a communication device, which includes: a receiving unit and a transmitting unit; the receiving unit is configured to receive a first request message and uplink data from a terminal, where the first request message is used to request resuming a suspended radio resource control (RRC) connection; the transmitting unit is configured to send information about the first request message and the uplink data to a second network element according to the first request message and the uplink data.

[0074] In combination with the eighteenth aspect, in a first possible implementation manner, the information of the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the communication device, and the second indication information is used to indicate that the uplink data is not included in the first request message.

[0075] In combination with the eighteenth aspect and the first possible implementation manner of the eighteenth aspect, in a second possible implementation manner, the receiving unit is further configured to receive a buffer status report from the terminal, where the buffer status report is used to indicate the data volume of the remaining uplink data; the transmitting unit is further configured to send information about the data volume of the remaining uplink data to the second network element.

[0076] In combination with the second possible implementation manner of the eighteenth aspect, in a third possible implementation manner, if the data volume of the remaining uplink data is greater than or equal to a threshold, the receiving unit is further configured to receive a first message from the second network element, where the first message is used to indicate that the communication device establishes an RRC connection with the terminal.

[0077] In combination with the eighteenth aspect and various possible implementation manners of the eighteenth aspect, in a fourth possible implementation manner, the receiving unit is further configured to receive a second message from the second network element, where the second message includes the configuration of the source radio link control.

[0078] In combination with the fourth possible implementation manner of the eighteenth aspect, in a fifth possible implementation manner, the second message further includes indication information for indicating a communication tunnel between the second network element and the communication device, where the communication tunnel is used to transmit the uplink data.

[0079] In combination with the eighteenth aspect and various possible implementation manners of the eighteenth aspect, in a sixth possible implementation manner, the communication device further includes a processing unit; the receiving unit is further configured to receive a third message from the second network element, where the third message is used to indicate that the communication device deletes the uplink data; the processing unit is configured to delete the uplink data according to the third message.

[0080] Combined with the eighteenth aspect and various possible implementation manners of the eighteenth aspect, in the seventh possible implementation manner, the first request message and the uplink data are multiplexed in one message.

[0081] In a nineteenth aspect, an embodiment of the present application provides a communication device, including: a receiving unit and a processing unit; the receiving unit is configured to receive information about a first request message and uplink data from a first network element; the processing unit is configured to obtain a context of a terminal according to the information about the first request message and the uplink data.

[0082] Combined with the nineteenth aspect, in a first possible implementation manner, the information about the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or a source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the first network element, and the second indication information is used to indicate that the uplink data is not included in the first request message.

[0083] Combined with the nineteenth aspect and the first possible implementation manner of the nineteenth aspect, in a second possible implementation manner, the receiving unit is further configured to receive information about the data volume of remaining uplink data from the first network element, and the information about the data volume of the remaining uplink data is used to indicate the data volume of the remaining uplink data.

[0084] Combined with the second possible implementation manner of the nineteenth aspect, in a third possible implementation manner, the communication device further includes: a sending unit; the sending unit is configured to, if the data volume of the remaining uplink data is greater than or equal to a threshold, send a first message to the first network element, and the first message is used to indicate that the first network element establishes a radio resource control (RRC) connection with the terminal.

[0085] Combined with the nineteenth aspect and various possible implementation manners of the nineteenth aspect, in a fourth possible implementation manner, the context of the terminal includes a configuration of a source packet data convergence protocol and a configuration of a source radio link control.

[0086] Combined with the fourth possible implementation manner of the nineteenth aspect, in a fifth possible implementation manner, the communication device further includes: a sending unit; the sending unit is configured to send a second message to the first network element, and the second message includes a configuration of a source radio link control in the context of the terminal.

[0087] Combined with the fifth possible implementation manner of the nineteenth aspect, in a sixth possible implementation manner, the second message further includes indication information for indicating a communication tunnel between the communication device and the first network element, and the communication tunnel is used to transmit the uplink data.

[0088] Combined with the nineteenth aspect and various possible implementation manners of the nineteenth aspect, in the seventh possible implementation manner, the communication device does not obtain the context of the terminal, and the communication device further includes: a sending unit; the sending unit is configured to send a third message to the first network element, and the third message is used to instruct the first network element to delete the uplink data.

[0089] Combined with the nineteenth aspect and various possible implementation manners of the nineteenth aspect, in the eighth possible implementation manner, the first request message and the uplink data are multiplexed in one message.

[0090] The twentieth aspect provides a communication device according to an embodiment of the present application, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the device implements the method described in the above sixteenth aspect or any possible implementation manner of the sixteenth aspect.

[0091] The twenty-first aspect provides a communication device according to an embodiment of the present application, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the device implements the method described in the above seventeenth aspect or any possible implementation manner of the seventeenth aspect.

[0092] The twenty-second aspect provides a communication device according to an embodiment of the present application, and the device is used to implement the method described in the above sixteenth aspect or any possible implementation manner of the sixteenth aspect.

[0093] The twenty-third aspect provides a communication device according to an embodiment of the present application, and the device is used to implement the method described in the above seventeenth aspect or any possible implementation manner of the seventeenth aspect.

[0094] The twenty-fourth aspect provides a computer-readable medium according to an embodiment of the present application, on which computer programs or instructions are stored. When the computer programs or instructions are executed, the computer executes the method described in the above sixteenth aspect or any possible implementation manner of the sixteenth aspect.

[0095] The twenty-fifth aspect provides a computer-readable medium according to an embodiment of the present application, on which computer programs or instructions are stored. When the computer programs or instructions are executed, the computer executes the method described in the above seventeenth aspect or any possible implementation manner of the seventeenth aspect.

[0096] The twenty-sixth aspect provides a computer program product according to an embodiment of the present application, which includes computer program code. When the computer program code runs on a computer, the computer executes the method described in the above sixteenth aspect or any possible implementation manner of the sixteenth aspect.

[0097] In a twenty-seventh aspect, an embodiment of the present application provides a computer program product, which includes computer program code. When the computer program code runs on a computer, it causes the computer to execute the method described in the above seventeenth aspect or any possible implementation manner of the seventeenth aspect.

[0098] In a twenty-eighth aspect, an embodiment of the present application provides a chip, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the chip implements the method described in the above sixteenth aspect or any possible implementation manner of the sixteenth aspect.

[0099] In a twenty-ninth aspect, an embodiment of the present application provides a chip, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the chip implements the method described in the above seventeenth aspect or any possible implementation manner of the seventeenth aspect.

[0100] In a thirtieth aspect, an embodiment of the present application provides a communication system. The system includes the device described in the above eighteenth aspect and / or the device described in the above nineteenth aspect, or the system includes the device described in the above twentieth aspect and / or the device described in the above twenty-first aspect, or the system includes the device described in the above twenty-second aspect and / or the device described in the above twenty-third aspect.

[0101] It can be understood that any of the above-provided communication devices, chips, computer-readable media, computer program products, or communication systems, etc. are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods, and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0102] Figure 1A It is a schematic diagram of the communication system architecture provided by an embodiment of the present application;

[0103] Figure 1B It is a first schematic diagram of the process of transmitting data between a terminal and a network device provided by an embodiment of the present application;

[0104] Figure 1C It is a schematic diagram of the architecture of the network device provided by an embodiment of the present application;

[0105] Figure 1D It is a schematic diagram of the process of transmitting data between a terminal and a network device provided by an embodiment of the present application Figure 2 ;

[0106] Figure 1ESchematic diagram of the four-step random access process provided by the embodiments of the present application;

[0107] Figure 1F Schematic diagram of the two-step random access process provided by the embodiments of the present application;

[0108] Figure 2 Schematic diagram of the hardware structure of the communication device provided by the embodiments of the present application;

[0109] Figure 3 Schematic diagram one of the flow of the communication method provided by the embodiments of the present application;

[0110] Figure 4 Schematic diagram of the flow of the communication method provided by the embodiments of the present application Figure 2 ;

[0111] Figure 5 Schematic diagram of the flow of the communication method provided by the embodiments of the present application Figure 3 ;

[0112] Figure 6 Schematic diagram of the flow of the communication method provided by the embodiments of the present application Figure 4 ;

[0113] Figure 7 Schematic diagram of the flow of the communication method provided by the embodiments of the present application Figure 5 ;

[0114] Figure 8 Schematic diagram of the flow of the communication method provided by the embodiments of the present application Figure 6 ;

[0115] Figure 9 Schematic diagram one of the structure of the communication device provided by the embodiments of the present application;

[0116] Figure 10 Schematic diagram of the structure of the communication device provided by the embodiments of the present application Figure 2 ;

[0117] Figure 11 Schematic diagram of the structure of the communication device provided by the embodiments of the present application Figure 3 ;

[0118] Figure 12 Schematic diagram of the structure of the communication device provided by the embodiments of the present application Figure 4 ;

[0119] Figure 13 Schematic diagram of the structure of the communication device provided by the embodiments of the present application Figure 5 ;

[0120] Figure 14 Schematic diagram of the structure of the communication device provided by the embodiments of the present application Figure 6 ;

[0121] Figure 15 Structural schematic diagram of the communication device provided by the embodiment of the present application Figure 7 ;

[0122] Figure 16 Structural schematic diagram of the communication device provided by the embodiment of the present application Figure 8 ;

[0123] Figure 17 Schematic diagram one of the composition of the communication system provided by the embodiment of the present application;

[0124] Figure 18 Composition schematic diagram of the communication system provided by the embodiment of the present application Figure 2 。 Detailed implementation manners

[0125] The implementation manners of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0126] As Figure 1A shown, it is a schematic diagram of the architecture of the communication system 100 provided by the embodiment of the present application. Figure 1A In it, the communication system 100 includes a network device 101, a network device 102, terminals 103 - 105, and a core network device 106.

[0127] The network device 101 is connected to the network device 102, and data can be transmitted between them. The network device 101 can also provide wireless access services for the terminals 103 and 104, and the network device 102 can also provide wireless access services for the terminal 105. Specifically, each network device corresponds to a service coverage area, and the terminals entering this area can communicate with the network device through the Uu interface to receive the wireless access services provided by the network device. For example, the terminal 103 can send uplink data to the network device 101, and the network device 101 can send downlink data to the terminal 103.

[0128] The network device 101 establishes a data channel 1 with the core network device 106 based on the terminal 103. The network device 101 sends the data from the terminal 103 to the core network device 106 or receives the data from the core network 106 through this data channel 1. The network device 101 is called the anchor node of the terminal 103. The network device 101 establishes a data channel 2 with the core network device 106 based on the terminal 104. The network device 101 sends the data from the terminal 104 to the core network device 106 or receives the data from the core network 106 through this data channel 2. The network device 101 is called the anchor node of the terminal 104. The network device 102 establishes a data channel 3 with the core network device 106 based on the terminal 105. The network device 102 sends the data from the terminal 105 to the core network device 106 or receives the data from the core network 106 through this data channel 3. The network device 102 is called the anchor node of the terminal 105.

[0129] The network device 101 or the network device 102 can be any device with wireless transceiver functions, including but not limited to: the evolved Node B (NodeB or eNB or e-NodeB, evolutional Node B) in Long Term Evolution (LTE), the base station (gNodeB or gNB) or transmission receiving point (TRP) in New Radio (NR), the base station evolved from the subsequent evolution of the 3rd Generation Partnership Project (3GPP), the access node in a Wireless-Fidelity (WiFi) system, the wireless relay node, the wireless backhaul node, etc. The base station can be: a macro base station, a micro base station, a pico base station, a small station, a relay station, or a balloon station, etc. Multiple base stations can support the networks of the same technology mentioned above, or can support the networks of different technologies mentioned above. The base station can include one or more co-located or non-co-located TRPs. The network device can also be a wireless controller, a centralized unit (CU), and / or a distributed unit (DU) in the scenario of a cloud radio access network (CRAN). Hereinafter, the network device 101 or the network device 102 being a base station is taken as an example for illustration. The network device 101 or the network device 102 can be of the same type of base station, or can be of different types of base stations. The base station can communicate with the terminal, or can communicate with the terminal through a relay station. The terminal can communicate with multiple base stations of different technologies. For example, the terminal can communicate with the base station supporting the LTE network, can also communicate with the base station supporting the 5G network, and can also support dual connection with the base station of the LTE network and the base station of the 5G network.

[0130] Terminals 103 - 105 are devices with wireless transceiver functions that can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; they can also be deployed on water (such as ships, etc.); and they can also be deployed in the air (such as on airplanes, balloons, satellites, etc.). The terminal can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a terminal in industrial control, a vehicle-mounted terminal device, a terminal in self-driving, a terminal in assisted driving, a terminal in remote medical, a terminal in smart grid, a terminal in transportation safety, a terminal in smart city, a terminal in smart home, etc. The embodiments of this application do not limit the application scenarios. A terminal can sometimes also be referred to as a terminal device, a user equipment (UE), an access terminal device, a vehicle-mounted terminal, an industrial control terminal, a UE unit, a UE station, a mobile station, a mobile device, a remote station, a remote terminal device, a mobile device, a UE terminal device, a wireless communication device, a machine terminal, a UE agent, or a UE device, etc. A terminal can be fixed or mobile.

[0131] By way of example and not limitation, in this application, the terminal can be a wearable device. A wearable device can also be called a wearable intelligent device, which is the general term for devices developed by applying wearable technology to the intelligent design of daily wear, 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. A wearable device is not just a hardware device, but more importantly, it realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can achieve complete or partial functions without relying on a smartphone, such as smart watches or smart glasses, etc., and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones, such as various smart bracelets and smart jewelry for monitoring physical signs.

[0132] The core network device 106 may be a user plane function (UPF) entity. The UPF is mainly responsible for forwarding and receiving user data. The UPF can receive downlink data from a data network (DN), and then transmit the downlink data to the terminal through a radio access network (RAN). The UPF can also receive uplink data from the terminal through the RAN, and then forward the uplink data to the DN.

[0133] It should be noted that Figure 1A The illustrated communication system 100 is only for illustration and is not intended to limit the technical solutions of this application. Those skilled in the art should understand that in the specific implementation process, the communication system 100 may further include other devices, and the number of network devices, terminals, and core network devices can also be determined according to specific needs.

[0134] In some embodiments, the process of transmitting data between the terminal and the network device may be as Figure 1B shown. Figure 1BAmong them, the terminal includes a Packet Data Convergence Protocol (PDCP) layer entity, a Radio Link Control (RLC) layer entity, a Media Access Control (MAC) layer entity, and a Physical Layer (PHY) entity. The network device includes a PDCP layer entity, an RLC layer entity, a MAC layer entity, and a PHY entity. Taking the example of the terminal 103 sending uplink data of the user plane to the network device 101, when there is uplink data of the user plane arriving at the terminal 103, the PDCP layer entity in the terminal 103 processes the uplink data using the PDCP configuration and delivers the processed uplink data to the RLC layer entity in the terminal 103. The RLC layer entity in the terminal 103 processes the uplink data that has been processed by the PDCP layer entity using the RLC configuration and delivers the processed uplink data to the MAC layer entity in the terminal 103. The MAC layer entity in the terminal 103 processes the uplink data that has been processed by the PDCP layer entity and the RLC layer entity using the MAC configuration, generates a MAC Protocol Data Unit (PDU) including a Logical Channel Identity (LCID), and delivers the MAC PDU to the PHY entity in the terminal 103. The PHY entity in the terminal 103 processes the MAC PDU using the PHY configuration and sends the processed MAC PDU to the network device 101. Among them, the PDCP layer entity in the terminal 103 processes the uplink data according to the PDCP configuration means that: the PDCP layer entity in the terminal 103 adds the PDCP Serial Number (SN) length, encryption, and other operations in the PDCP header corresponding to the uplink data. The RLC layer entity in the terminal 103 processes the uplink data that has been processed by the PDCP layer entity according to the RLC configuration means that: the RLC layer entity in the terminal 103 adds the RLC SN length and other operations in the RLC header corresponding to the uplink data that has been processed by the PDCP layer entity.

[0135] After the PHY entity in the network device 101 receives the processed MAC PDU, it processes the processed MAC PDU using the PHY configuration to obtain the MAC PDU, and delivers the MAC PDU to the MAC layer entity in the network device 101. The MAC layer entity in the network device 101 processes the MAC PDU using the MAC configuration to obtain the uplink data processed by the PDCP layer entity and the RLC layer entity in the terminal 103, and delivers the uplink data processed by the PDCP layer entity and the RLC layer entity in the terminal 103 to the RLC layer entity in the network device 101. The RLC layer entity in the network device 101 processes the uplink data processed by the PDCP layer entity and the RLC layer entity in the terminal 103 using the RLC configuration to obtain the uplink data processed by the PDCP layer entity in the terminal 103, and delivers the uplink data processed by the PDCP layer entity in the terminal 103 to the PDCP layer entity in the network device 101. The PDCP layer entity in the network device 101 processes the uplink data processed by the PDCP layer entity in the terminal 103 using the PDCP configuration to obtain the above-mentioned user plane uplink data. Subsequently, the network device 101 sends the uplink data to the core network device 106. The RLC layer entity in the network device 101 processes the uplink data processed by the PDCP layer entity and the RLC layer entity in the terminal 103 according to the RLC configuration, which means that the RLC layer entity in the network device 101 removes the RLC SN length in the header corresponding to the uplink data processed by the PDCP layer entity and the RLC layer entity in the terminal 103 and other operations. The PDCP layer entity in the network device 101 processes the uplink data processed by the PDCP layer entity in the terminal 103 according to the PDCP configuration, which means that the PDCP layer entity in the network device 101 removes the PDCP SN length in the header corresponding to the uplink data processed by the PDCP layer entity in the terminal 103, decrypts and other operations.

[0136] In some embodiments, the network device 101 and / or the network device 102 may be a CU-DU separated architecture. That is to say, the network device 101 and / or the network device 102 may include a CU and one or more DUs. Among them, the CU is mainly responsible for centralized radio resource and connection management control, and has the functions of the radio high layer protocol stack, for example, the PDCP layer function, etc. The DU has the function of distributed user plane processing, and mainly has the functions of the physical layer and the layer 2 functions with high real-time requirements. For example, the DU has functions such as PHY function, MAC layer function and RLC layer function.

[0137] Taking the network device 101 with a CU-DU separated architecture as an example, the architecture of the network device 101 can be as Figure 1C shown. Figure 1CAmong them, the network device 101 includes a CU 1011, a DU 1012, and a DU 1013. Among them, the DU 1012 and the DU 1013 can be connected to terminals. For example, the DU 1012 is connected to the terminal 103, and the DU 1013 is connected to the terminal 104. The CU 1011 can be connected to other network devices. For example, the CU 1011 is connected to the network device 102. The CU 1011 can also be connected to a core network device. For example, the CU 1011 can also be connected to the core network device 106.

[0138] Optionally, a General Packet Radio Service (GPRS) Tunnelling Protocol (GTP) tunnel is established between each DU and the CU. This GTP tunnel is used to transmit the user plane data between the DU and the CU. For example, a GTP tunnel 1 is established between the CU 1011 and the DU 1012. The GTP tunnel 1 is used to transmit the user plane data between the CU 1011 and the DU 1012. A GTP tunnel 2 is established between the CU 1011 and the DU 1013. The GTP tunnel 2 is used to transmit the user plane data between the CU 1011 and the DU 1013.

[0139] It should be understood that Figure 1C The shown CU-DU architecture is only for illustration and is not used to limit the technical solutions of this application. Those skilled in the art should understand that in the specific implementation process, the number of CUs and DUs in the above CU-DU architecture can be determined according to specific needs. At the same time, the above CU 1011, DU 1012, and DU 1013 can be deployed in the same device or in different devices, without limitation.

[0140] If the network device 101 and / or the network device 102 is a CU-DU separated architecture, the process of transmitting user plane data between the terminal and the network device can be as Figure 1D shown. Figure 1DAmong them, the terminal includes a PDCP layer entity, an RLC layer entity, a MAC layer entity, and a PHY entity. When facing the terminal, the DU includes an RLC layer entity, a MAC layer entity, and a PHY entity; when facing the CU, the DU includes an F1 application protocol (F1AP) layer entity, a stream control transmission protocol (SCTP) layer entity, an internet protocol (IP) layer entity, a layer 2 (L2) entity, and a layer 1 (L1) entity. The CU includes an F1AP layer entity, an SCTP layer entity, an IP layer entity, an L2 layer entity, and an L1 layer entity. Taking the example of the terminal 103 sending user plane uplink data to the CU 1011 via the DU 1012, when there is user plane uplink data arriving at the terminal 103, the terminal 103 can, according to the method of the terminal 103 sending user plane uplink data to the network device 101 as described above, send the processed MAC PDU to the DU 1012. After the PHY entity in the DU 1012 receives the processed MAC PDU, it can process the received processed MAC PDU according to the method of the PHY entity, MAC layer entity, and RLC layer entity in the network device 101 processing data as described above, obtain the uplink data processed by the PDCP layer entity in the terminal 103, and send the uplink data processed by the PDCP layer entity in the terminal 103 to the CU 1011 through the GTP tunnel between the DU 1012 and the CU 1011. After the CU 1011 receives the uplink data processed by the PDCP layer entity in the terminal 103, it can process the received data according to the method of the PDCP layer entity in the network device 101 processing data as described above, and obtain the above-mentioned user plane uplink data. Subsequently, the CU 1011 sends the uplink data to the core network device 106.

[0141] It should be noted that the terminal can send uplink data to the network device through the random access process.

[0142] Exemplarily, the random access process can include a four-step random access process and a two-step random access process. The terminal can send uplink data to the network device through the third message (Msg3) in the four-step random access process; or, the terminal can also send uplink and downlink data to the network device through the message A (MsgA) in the two-step random access process.

[0143] Among them, the four-step random access process can be as Figure 1E shown, and the four-step random access process can include the following steps:

[0144] Step a1: The terminal sends a random access request to the network device. The random access request may include a random access preamble. Herein, the random access request is also referred to as the first message or message 1 (Msg1) in the random access procedure.

[0145] Step a2: After detecting the random access preamble sent by the terminal, the network device sends a random access response (RAR) to the terminal. Herein, the random access response is also referred to as the second message or message 2 (Msg2) in the random access procedure.

[0146] Step a3: The terminal receives the RAR from the network device and sends an uplink signaling to the network device. Herein, the uplink signaling is also referred to as the third message or message 3 (Msg3) in the random access procedure. Herein, Msg3 may include uplink data.

[0147] Step a4: The network device receives Msg3 and sends a contention resolution message to the terminal. Correspondingly, the terminal receives the contention resolution message from the network device. If it is determined that the random access conflict is won according to the contention resolution message, the random access can be determined to be successful; otherwise, the terminal determines that the random access fails and can perform the random access procedure again. Herein, the contention resolution message is also referred to as the fourth message or message 4 (Msg4).

[0148] Herein, the two-step random access procedure may be as Figure 1F shown. The two-step random access procedure may include the following steps:

[0149] Step b1, the terminal sends a random access request to the network device.

[0150] Herein, the random access request may also be referred to as message A (MsgA). The random access request includes a random access preamble and uplink signaling, which is equivalent to Msg1 and Msg3 in the above Figure 1E and can also be understood as "sending Msg1 and Msg3 together".

[0151] Step b2, the network device receives the random access request from the terminal and sends message B (MsgB) to the terminal.

[0152] Herein, MsgB is the response information for the random access request, and may also be referred to as message B, including at least one of the response information for the random access preamble and the response information for the uplink signaling.

[0153] Optionally, in the embodiments of the present application Figure 1AEach network element in [the system], such as network device 102 or terminal 103, may be a functional module within a device. It can be understood that the above functions can be either network components in a hardware device, such as a communication chip in a mobile phone, or software functions running on dedicated hardware, or virtualized functions instantiated on a platform (such as a cloud platform).

[0154] For example, Figure 1A each network element in [the system] can be implemented through Figure 2 the communication device 200 in [the system]. Figure 2 The figure shows a schematic diagram of the hardware structure of a communication device applicable to the embodiments of the present application. The communication device 200 includes at least one processor 201, a communication line 202, a memory 203, and at least one communication interface 204.

[0155] The processor 201 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application solution.

[0156] The communication line 202 may include a path for transmitting information between the above components, such as a bus.

[0157] The communication interface 204 uses any device such as a transceiver for communicating with other devices or communication networks, such as an Ethernet interface, a RAN interface, a wireless local area networks (WLAN) interface, etc.

[0158] The memory 203 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory can exist independently and be connected to the processor through the communication line 202. The memory can also be integrated with the processor. The memory provided in the embodiments of the present application generally has non-volatility. Among them, the memory 203 is used to store the computer execution instructions involved in implementing the solution of the present application, and is controlled by the processor 201 to execute. The processor 201 is used to execute the computer execution instructions stored in the memory 203, so as to implement the method provided in the embodiments of the present application.

[0159] Optionally, the computer execution instructions in the embodiments of the present application can also be referred to as application program code, and the embodiments of the present application do not make specific limitations thereto.

[0160] In a specific implementation, as an embodiment, the processor 201 can include one or more CPUs, such as Figure 2 CPU0 and CPU1 in

[0161] In a specific implementation, as an embodiment, the communication device 200 can include multiple processors, such as Figure 2 the processor 201 and the processor 207 in

[0162] In a specific implementation, as an example, the communication device 200 may further include an output device 205 and an input device 206. The output device 205 communicates with the processor 201 and can display information in various ways. For example, the output device 205 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 206 communicates with the processor 201 and can receive user input in various ways. For example, the input device 206 may be a mouse, a keyboard, a touch screen device, or a sensing device, etc.

[0163] The above-mentioned communication device 200 may be a general-purpose device or a special-purpose device. In a specific implementation, the communication device 200 may be a laptop, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal, an embedded device, or a device with a Figure 2 similar structure. The embodiments of the present application do not limit the type of the communication device 200.

[0164] The communication method provided by the embodiments of the present application will be specifically described below.

[0165] It should be noted that the message names between the network elements or the names of the parameters in the messages in the following embodiments of the present application are only examples. In a specific implementation, they may also be other names. The embodiments of the present application do not make specific limitations on this.

[0166] It should be noted that in the description of the present application, terms such as "first" or "second" are only used for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order. The "first network device" and other network devices with different numbers in the present application are only for the convenience of writing in the context. Different sequence numbers themselves do not have specific technical meanings. For example, the first network device, the second network device, etc. can be understood as one or any one of a series of network devices. It can be understood that in a specific implementation, the network devices with different numbers may also be of the same type. The present application does not make limitations on this.

[0167] It can be understood that in the embodiments of the present application, the first network device, the second network device, the first network element or the second network element may execute some or all of the steps in the embodiments of the present application. These steps are only examples, and the embodiments of the present application may also execute other steps or various deformations of the steps. In addition, each step may be executed in a different order presented in the embodiments of the present application, and it is possible not to execute all the steps in the embodiments of the present application.

[0168] As Figure 3 shown, a communication method provided by an embodiment of the present application includes step 301-step 303.

[0169] Step 301: The terminal sends a first request message to the first network device.

[0170] Among them, the terminal may be Figure 1A any one of terminals 103-105 in Figure 1A . When the terminal is Figure 1A terminal 103 or terminal 104 in Figure 1A , the first network device is Figure 1A network device 101 in

[0171] Optionally, the terminal is in the RRC inactive (RRC-inactive) state. The previous serving network device of the terminal is the second network device. In other words, the second network device stores the context of the terminal, or the second network device has a data channel with the core network device based on the terminal. Among them, when the first network device is Figure 1A network device 101 in Figure 1A , the second network device may be Figure 1A network device 102 in Figure 1A , and when the first network device is

[0172] network device 102 in

[0173] Optionally, the RRC release message further includes a source RRC reconfiguration. After receiving the RRC release message, the terminal stores the source RRC reconfiguration. The source RRC reconfiguration is allocated by the second network device for the terminal. The source RRC reconfiguration includes a source data radio bearer (DRB) configuration, a source PDCP configuration, and a source RLC configuration. The source DRB configuration includes the mapping relationship between the source DRB and the source PDCP, and the mapping relationship between the source DRB and the source RLC. The source PDCP configuration includes the length of the source PDCP SN. The source RLC configuration includes the length or mode indication of the source RLC SN, for example, the acknowledged mode (AM) or the unacknowledged mode (UM), etc. The source RRC reconfiguration is used to process uplink data when the terminal transmits uplink data next time.

[0174] Optionally, the terminal has mobility. When the terminal moves from the service coverage area of the second network device to the service coverage area of the first network device and uplink data arrives at the terminal, the terminal sends a first request message to the first network device. Among them, the uplink data may be user-plane uplink data, and the first request message may be used to request the resumption of a suspended RRC connection. The first request message may be an RRC resume request, and the first request message includes the above-mentioned first identifier. The terminal may also send the uplink data to the first network device. The terminal may send the first request message and the uplink data simultaneously, or the terminal may also send the first request message and the uplink data separately. When the terminal sends the first request message and the uplink data simultaneously, the uplink data and the first request message are multiplexed in one message, or the uplink data is encapsulated in the first request message. For example, the terminal sends a first request message to the first network device, and the first request message includes the uplink data.

[0175] It can be understood that the first request message and the uplink data are sent to the first network device after being processed by the PDCP layer entity, RLC layer entity, MAC layer entity, and PHY entity of the terminal.

[0176] In a possible implementation, uplink data and a first request message are multiplexed in one message. The first request message is sent by the terminal to the first network device after being processed according to the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration. The uplink data is processed by the terminal according to the source PDCP configuration and source RLC configuration corresponding to the DRB to which the uplink data belongs in the source RRC reconfiguration. Subsequently, the data processed according to the source PDCP configuration and source RLC configuration is further processed according to the common MAC configuration and common PHY configuration and then sent to the first network device. In this case, the MAC PDU sent to the first network device includes at least two MAC service data units (SDUs). One of the MAC SDUs encapsulates the uplink data, and the other MAC SDU encapsulates the first request message.

[0177] In another possible implementation, the uplink data is encapsulated in the first request message. After processing the uplink data according to the source PDCP configuration corresponding to the DRB to which the uplink data belongs in the source RRC reconfiguration, the terminal puts the processed uplink data into the first request message. The terminal processes the first request message according to the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration, and sends the processed first request message to the first network device.

[0178] It should be noted that the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration in the embodiments of this application are configurations known to the terminal, the first network device, and the second network device. For example, the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration are pre-configured in the terminal, the first network device, or the second network device, or the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration are received by the terminal, the first network device, or the second network device through a broadcast message or specified by a protocol. The source PDCP configuration and source RLC configuration in the embodiments of this application are dedicated configurations of the terminal and the second network device. That is, the first network device does not know the source PDCP configuration and source RLC configuration before receiving the source PDCP configuration and source RLC configuration.

[0179] Optionally, the first request message, or the first request message and the uplink data are sent to the first network device during a random process initiated by the terminal. For example, the first request message, or the first request message and the uplink data are sent to the first network device through the third message in the four-step random access process. Another example is that the first request message, or the first request message and the uplink data are sent to the first network device through message A in the two-step random access process.

[0180] Optionally, the first request message further includes a first identifier.

[0181] Optionally, the terminal may further send a buffer status report to the first network device. The buffer status report is used to indicate the amount of remaining uplink data. The amount of remaining uplink data is used to indicate the size of the remaining uplink data and / or the number of data packets in the remaining uplink data.

[0182] In a possible implementation, the buffer status report includes the total amount of the remaining uplink data. In another possible implementation, the buffer status report includes the amount of the remaining uplink data for each LCH in a logical channel group (LCG) corresponding to the remaining uplink data. Exemplarily, taking the remaining uplink data corresponding to LCG 1 and LCG 2, LCG 1 including LCH 1 and LCH 2, and LCG 2 including LCH 3 as an example, the buffer status report may be as shown in Table 1. In Table 1, if the amount of the remaining uplink data for LCH 1 is 20 bytes, the amount of the remaining uplink data for LCH 2 is 80 bytes, and the amount of the remaining uplink data for LCH 3 is 50 bytes, then the amount of the remaining uplink data in LCG 1 is 100 bytes (20 bytes + 80 bytes), the amount of the remaining uplink data in LCG 2 is 50 bytes, and the total amount of the remaining uplink data is 150 bytes (100 bytes + 50 bytes).

[0183] Table 1

[0184]

[0185] It should be noted that Table 1 is only an example of the buffer status report, and the buffer status report may also be in other forms, which is not limited.

[0186] Optionally, the terminal may further send the configured grant (CG) capability of the terminal to the first network device. The CG capability of the terminal is used to indicate whether the terminal supports CG.

[0187] Step 302: The first network device receives the first request message from the terminal, and sends a second request message to the second network device according to the first request message.

[0188] Among them, the second request message can be used to request the second network device to release the first data channel between the second network device and the core network device; or, the second request message can be used to request the second network device to send the context of the terminal to the first network device. The second request message includes information about the uplink data. The second request message can be carried in a Retrieve UEContext Request message.

[0189] Among them, the core network device can be Figure 1A the core network device 106 in

[0190] Optionally, the second request message is used to request the second network device to release the first data channel between the second network device and the core network device, and the information about the uplink data is used by the second network device to determine whether to release the first data channel; the second request message is used to request the second network device to send the context of the terminal to the first network device, and the information about the uplink data is used by the second network device to determine whether to send the context of the terminal to the first network device.

[0191] Optionally, the first network device can also receive uplink data from the terminal. The description of the uplink data and the first request message can refer to that described in step 301 above and will not be elaborated here.

[0192] The processing process of the first network device for the received uplink data and the first request message is as follows:

[0193] A possible implementation method is that if the uplink data and the first request message are multiplexed in one message, the first network device can process the received first request message processed according to the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration based on the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration to obtain the first request message; the first network device can process the received uplink data processed according to the source PDCP configuration, source RLC configuration, common MAC configuration, and common PHY configuration based on the common MAC configuration and common PHY configuration to obtain the uplink data processed according to the source PDCP configuration and source RLC configuration. Since the first network device does not know the source PDCP configuration and source RLC configuration, it cannot obtain this uplink data. The first network device needs to request the context of the terminal from the second network device to obtain this uplink data.

[0194] Another possible implementation method. If the uplink data is encapsulated in the first request message, the first network device can process the received first request message processed according to the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration based on the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration to obtain the first request message. The first request message includes the uplink data processed according to the source PDCP configuration. Since the first network device does not know the source PDCP configuration, it cannot obtain the uplink data. The first network device needs to request the context of the terminal from the second network device to obtain the uplink data.

[0195] It can be understood that when the first network device receives the uplink data from the terminal and the uplink data and the first request message are multiplexed in one message, when the uplink data is encapsulated in the first request message, and when the first network device does not receive the uplink data, the process of the first network device sending the second request message to the second network device according to the first request message is different, and the content included in the information of the uplink data is also different. Specifically, it can be as shown in the following Examples 1-3.

[0196] Example 1: When the uplink data and the first request message are multiplexed in one message, the first network device sends the second request message to the second network device according to the first request message and the uplink data. Among them, the first network device sending the second request message to the second network device according to the first request message and the uplink data includes: the first network device determining the information of the uplink data according to the first request message and the uplink data; the first network device sending the second request message to the second network device, and the second request message includes the information of the uplink data.

[0197] Among them, the information of the uplink data may include at least one of the following: the first indication information, the second indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data.

[0198] Among them, the first indication information can be used to indicate that the uplink data has reached the first network device; or, the first indication information is used to indicate that the uplink data is sent to the first network device through the third message in the four-step random access process; or, the first indication information is used to indicate that the uplink data is sent to the first network device through the message A in the two-step random access process; or, the first indication information is used to indicate that the terminal initiates early data transmission (EDT) so that the second network device can determine whether the first network device has received the uplink data. EDT can indicate that the terminal carries uplink data in the random process initiated to the first network device.

[0199] Among them, the second indication information can be used to indicate that the uplink data is not included in the first request message, so that the second network device can determine that the context of the terminal required by the first network device includes the source PDCP configuration and the source RLC configuration.

[0200] Among them, the data volume of the uplink data can be used to indicate the size of the uplink data and / or the number of data packets in the uplink data, so that the second network device can determine the data volume of the uplink data. In one possible implementation, the data volume of the uplink data includes the total data volume of the uplink data. In another possible implementation, the data volume of the uplink data includes the data volume of the uplink data of each LCH in the LCG corresponding to the uplink data. Exemplarily, taking the uplink data corresponding to LCG 1 and LCG 2, where LCG 1 includes LCH 1, and LCG 2 includes LCH 2 and LCH 3 as an example, the data volume of the uplink data can be as shown in Table 2. In Table 2, the data volume of the uplink data of LCH 1 is 80 bytes, the data volume of the uplink data of LCH 2 is 30 bytes, and the data volume of the uplink data of LCH 3 is 50 bytes. Then, the remaining data volume of the uplink data in LCG 1 is 80 bytes, and the remaining data volume of the uplink data in LCG 2 is 80 bytes (30 bytes + 50 bytes), and the total data volume of the uplink data is 160 bytes (80 bytes + 80 bytes).

[0201] Table 2

[0202]

[0203] It should be noted that Table 2 is only an example of the data volume of the uplink data, and the data volume of the uplink data can also be in other forms, which is not limited.

[0204] Among them, the source LCID corresponding to the uplink data is included in the MAC PDU corresponding to the uplink data. Therefore, the first network device can obtain the uplink data received from the terminal processed according to the source PDCP configuration, the source RLC configuration, the common MAC configuration, and the common PHY configuration by processing it according to the common MAC configuration and the common PHY configuration. The source LCID corresponding to the uplink data can be used by the second network device to establish a communication tunnel with the first network device.

[0205] Example 2: When the uplink data is encapsulated in the first request message, the first network device sends a second request message to the second network device according to the first request message. Among them, the first network device sending a second request message to the second network device according to the first request message includes: the first network device determining the information of the uplink data according to the first request message; the first network device sending a second request message to the second network device, and the second request message includes the information of the uplink data.

[0206] Among them, the information of the uplink data may include at least one of the following: first indication information, fourth indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data.

[0207] Among them, the introduction of the first indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data may refer to that described in the above Example 1 and will not be elaborated.

[0208] Among them, the fourth indication information may be used to indicate that the uplink data is included in the first request message, so that the second network device determines that the context of the terminal required by the first network device includes the source PDCP configuration.

[0209] Example 3: When the first network device does not receive the uplink data, the first network device sends a second request message to the second network device according to the first request message. Among them, the first network device sending the second request message to the second network device according to the first request message includes: the first network device determining the information of the uplink data according to the first request message; the first network device sending the second request message to the second network device, and the second request message includes the information of the uplink data.

[0210] Among them, the information of the uplink data includes fifth indication information. The fifth indication information may be used to indicate that the uplink data has not reached the first network device; or, the fifth indication information is used to indicate that the uplink data has not been sent to the first network device through the third message in the four-step random access procedure; or, the fifth indication information is used to indicate that the uplink data has not been sent to the first network device through message A in the two-step random access procedure; or, the fifth indication information is used to indicate that the terminal initiates a non-EDT, so that the second network device determines whether the first network device has received the uplink data. Non-EDT may indicate that the terminal does not carry uplink data during the random access procedure initiated to the first network device.

[0211] Optionally, the first network device also receives a buffer status report from the terminal. In this case, the second request message may further include information on the data volume of the remaining uplink data, and the information on the data volume of the remaining uplink data includes the data volume of the remaining uplink data. The introduction of the buffer status report and the data volume of the remaining uplink data may refer to that described in step 301 above and will not be elaborated.

[0212] It should be noted that if the buffer status includes the total data volume of the remaining uplink data, the information on the data volume of the remaining uplink data includes the total data volume of the remaining uplink data. If the buffer status report includes the data volume of the remaining uplink data for each LCH in the LCG corresponding to the remaining uplink data, the information on the data volume of the remaining uplink data includes the total data volume of the remaining uplink data, or the data volume of the remaining uplink data for each LCH in the LCG corresponding to the remaining uplink data.

[0213] It should be noted that if the amount of remaining uplink data is greater than or equal to the second threshold, the first network device and the terminal establish an RRC connection so that the terminal can send the remaining uplink data to the first network device.

[0214] Optionally, the first network device also receives the capability of the CG of the terminal from the terminal. In this case, the first network device can determine whether to configure the CG for the terminal according to the capability of the CG of the terminal. In a possible implementation, if the CG capability of the terminal indicates that the terminal supports CG, the first network device determines to configure the CG for the terminal.

[0215] Optionally, when the first network device determines to configure the CG for the terminal, the second request message may further include third indication information, and the third indication information is used to indicate that the first network device has the capability to configure the CG for the terminal.

[0216] Optionally, the second request message further includes a first identifier.

[0217] Step 303: The second network device receives the second request message from the first network device, and determines whether to release the first data channel with the core network device according to the second request message; or determines whether to send the context of the terminal to the first network device according to the second request message.

[0218] Among them, the introduction of the second request message can refer to that described in step 302 above, and will not be elaborated here.

[0219] First, the specific process of the second network device determining whether to release the first data channel according to the second request message is introduced.

[0220] In a possible implementation, for the above Example 1, there are the following two cases:

[0221] Case 1: The information of the uplink data includes at least one of the first indication information, the second indication information, or the source LCID corresponding to the uplink data. The second network device determines to release the first data channel; or the second network device determines to retain the first data channel. In this case, the second network device can determine whether to release the first data channel according to its own load, etc. For example, if the load of the second network device is greater than or equal to the third threshold, the second network device determines to release the first data channel; if the load of the second network device is less than or equal to the third threshold, the second network device determines to retain the first data channel.

[0222] Case 2: The information of the uplink data includes at least the amount of the uplink data. If the amount of the uplink data is greater than or equal to the first threshold, the second network device determines to release the first data channel; if the amount of the uplink data is less than or equal to the first threshold, the second network device determines to retain the first data channel.

[0223] In a possible implementation, for the above Example 2, there are the following two cases:

[0224] Case 3: The information of the uplink data includes at least one of the first indication information, the fourth indication information, or the source LCID corresponding to the uplink data. The second network device determines to release the first data channel; or, the second network device determines to retain the first data channel. In this case, the second network device can determine whether to release the first data channel according to its own load, etc. For example, if the load of the second network device is greater than or equal to the third threshold, the second network device determines to release the first data channel; if the load of the second network device is less than or equal to the third threshold, the second network device determines to retain the first data channel.

[0225] Case 4: The information of the uplink data includes at least the data volume of the uplink data. If the data volume of the uplink data is greater than or equal to the first threshold, the second network device determines to release the first data channel; if the data volume of the uplink data is less than or equal to the first threshold, the second network device determines to retain the first data channel.

[0226] In a possible implementation, for the above Example 3, the second network device determines to release the first data channel.

[0227] In a possible implementation, in addition to the information of the uplink data shown in Case 1 or Case 3, the second request message further includes the information of the data volume of the remaining uplink data, or, the second request message further includes the information of the data volume of the remaining uplink data and the third indication information. If the data volume of the remaining uplink data is greater than or equal to the second threshold, the second network device determines to release the first data channel; if the data volume of the remaining uplink data is less than or equal to the second threshold, the second network device determines to retain the first data channel.

[0228] In a possible implementation, in addition to the information of the uplink data shown in Case 1 or Case 3, the second request message further includes the third indication information. The second network device determines to release the first data channel; or, the second network device determines to retain the first data channel. In this case, the second network device can determine whether to release the first data channel according to its own load, etc. For example, if the load of the second network device is greater than or equal to the third threshold, the second network device determines to release the first data channel; if the load of the second network device is less than or equal to the third threshold, the second network device determines to retain the first data channel.

[0229] In a possible implementation, in addition to the information of the uplink data shown in Case 2 or Case 4, the second request message further includes the information of the data volume of the remaining uplink data, or the second request message further includes the information of the data volume of the remaining uplink data and the third indication information. When the data volume of the remaining uplink data is greater than or equal to the second threshold, the second network device determines to release the first data channel; when the data volume of the remaining uplink data is less than or equal to the second threshold, the second network device determines to retain the first data channel.

[0230] In a possible implementation, in addition to the information of the uplink data shown in Case 2 or Case 4, the second request message further includes the information of the data volume of the remaining uplink data, or the second request message further includes the information of the data volume of the remaining uplink data and the third indication information. When the data volume of the uplink data is greater than or equal to the first threshold, the second network device determines to release the first data channel; when the data volume of the uplink data is less than or equal to the first threshold, the second network device determines to retain the first data channel.

[0231] In a possible implementation, in addition to the information of the uplink data shown in Case 2 or Case 4, the second request message further includes the third indication information. When the data volume of the uplink data is greater than or equal to the first threshold, the second network device determines to release the first data channel; when the data volume of the uplink data is less than or equal to the first threshold, the second network device determines to retain the first data channel.

[0232] In a possible implementation, in addition to the information of the uplink data shown in Example 3, the second request message further includes the information of the data volume of the remaining uplink data and / or the third indication information, and the second network device determines to release the first data channel.

[0233] Optionally, after the second network device determines whether to release the first data channel according to the second request message, the second network device sends a first response message to the first network device. When the second network device determines to release the first data channel, the first response message is used to indicate that the second network device releases the first data channel; when the second network device determines to retain the first data channel, the first response message is used to indicate that the second network device retains the first data channel.

[0234] Optionally, the first response message includes at least one of the following information: the capabilities of the terminal's CG, service model information, or the configuration information of the terminal's CG under the second network device. Among them, the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, and the arrival timing of the terminal evaluated by the second network device. Subsequently, the first network device can determine whether to configure the CG for the terminal according to the capabilities of the terminal's CG. When the first network device determines to configure the CG for the terminal, it can refer to the configuration information of the terminal's CG under the second network device to configure the CG for the terminal; the first network device can determine the possible data arrival period of the terminal, the possible transport block size of the terminal's uplink data, or the possible arrival timing of the terminal according to the service model information.

[0235] In a possible implementation, when the second request message includes the third indication information, the first response message includes at least one of the following information: the capabilities of the terminal's CG, service model information, and the configuration information of the terminal's CG under the second network device, so that the first network device can configure the CG for the terminal according to the above information.

[0236] Optionally, the first response message is also used to establish a communication tunnel between the first network device and the second network device. This communication tunnel is used to transmit uplink data. For example, this communication tunnel is an Xn GTP-U tunnel. The number of this communication tunnel is one or more. This communication tunnel has a corresponding relationship with the source LCID. When the number of this communication tunnel is one, this communication tunnel corresponds to one or more source LCIDs. When the number of this communication tunnel is multiple, each of the multiple communication tunnels corresponds to one or more source LCIDs, and the source LCIDs corresponding to different communication tunnels can be the same or different. This corresponding relationship can be pre-configured in the second network device. It should be noted that because this communication tunnel has a corresponding relationship with the source LCID, the second network device can establish this communication tunnel only when it knows the source LCID. For example, when the information of the uplink data includes the source LCID corresponding to the uplink data, the first response message is also used to establish this communication tunnel.

[0237] In a possible implementation, the first response message further includes an identifier of the communication tunnel, and this identifier of the communication tunnel has a corresponding relationship with the source LCID.

[0238] In another possible implementation, the first response message further includes an address of the communication tunnel, and this address of the communication tunnel has a corresponding relationship with the source LCID.

[0239] It should be noted that if the second network device determines to release the first data channel, the first response message further includes the context of the terminal, where the context of the terminal includes the source PDCP configuration and the source RLC configuration, so that the first network device can obtain the above-mentioned uplink data according to the source PDCP configuration and the source RLC configuration and send the uplink data to the core network device. Further optionally, after sending the context of the terminal to the first network device, the second network device releases the context of the terminal stored locally.

[0240] Correspondingly, the first network device receives the first response message from the second network device.

[0241] In a possible implementation, the first response message instructs the second network device to release the first data channel, and the first network device establishes a second data channel with the core network device. The second data channel is used for the first network device to forward the uplink data sent by the terminal to the core network device, or the second data channel is used for the first network device to receive the data to be sent to the terminal from the core network device. After the first network device establishes the second data channel with the core network device, the first network device becomes the anchor node of the terminal. Subsequently, the first network device can send the above-mentioned uplink data to the core network device through the second data channel. The first network device can also send an RRC release message to the terminal to release the RRC connection between the first network device and the terminal.

[0242] In a possible implementation, the first response message instructs the second network device to retain the first data channel, and the first network device sends uplink data to the second network device. Further, the first network device sends the above-mentioned uplink data to the second network device through the above-mentioned communication tunnel. It can be understood that the uplink data sent by the first network device can be the uplink data received from the terminal and not processed by the first network device. After receiving the uplink data, the second network device can process the uplink data according to the context of the terminal and send the processed uplink data to the core network device through the first data channel. Subsequently, the second network device can send an RRC release message to the terminal through the first network device, and the RRC release message is used to notify that the RRC state of the terminal is the RRC inactive state or the RRC idle state.

[0243] It should be noted that the uplink data sent by the first network device can also be the data received from the terminal and processed according to the context of the terminal. After receiving the uplink data, the second network device can send it to the core network device through the first data channel.

[0244] The following introduces the specific process for the second network device to determine whether to send the context of the terminal to the first network device according to the second request message.

[0245] In a possible implementation, for the above Example 1, and in the case where in addition to the information of the uplink data shown in Example 1, the second request message further includes the information of the amount of remaining uplink data: the second network device determines to send the context of the terminal to the first network device, and the context of the terminal includes the source PDCP configuration and the source RLC configuration; or, the second network device determines not to send the context of the terminal to the first network device. In this case, the second network device may determine whether to send the context of the terminal to the first network device according to its own remaining storage resources, etc. For example, if the remaining storage resources of the second network device are greater than or equal to the fourth threshold, the second network device determines not to send the context of the terminal to the first network device; if the remaining storage resources of the second network device are less than or equal to the fourth threshold, the second network device determines to send the context of the terminal to the first network device, and the context of the terminal includes the source PDCP configuration and the source RLC configuration. After the second network device sends the context of the terminal to the first network device, it releases the context of the terminal.

[0246] In a possible implementation, for the above Example 2, and in the case where in addition to the information of the uplink data shown in Example 2, the second request message further includes the information of the amount of remaining uplink data: the second network device determines to send the context of the terminal to the first network device, and the context of the terminal includes the source PDCP configuration; or, the second network device determines not to send the context of the terminal to the first network device. In this case, the second network device may determine whether to send the context of the terminal to the first network device according to its own remaining storage resources, etc. For example, if the remaining storage resources of the second network device are greater than or equal to the fourth threshold, the second network device determines not to send the context of the terminal to the first network device; if the remaining storage resources of the second network device are less than or equal to the fourth threshold, the second network device determines to send the context of the terminal to the first network device, and the context of the terminal includes the source PDCP configuration and the source RLC configuration. After the second network device sends the context of the terminal to the first network device, it releases the context of the terminal.

[0247] In a possible implementation, for the above Example 3, and in the case where in addition to the information of the uplink data shown in Example 3, the second request message further includes the information of the amount of remaining uplink data and / or the third indication information: the second network device determines to send the context of the terminal to the first network device, and the context of the terminal includes the source PDCP configuration and the source RLC configuration.

[0248] In a possible implementation, in addition to the information of the uplink data shown in Example 1 or Example 2, the second request message further includes the third indication information, and the second network device determines to send the context of the terminal to the first network device, and the context of the terminal source PDCP configuration and the source RLC configuration.

[0249] In a possible implementation, in addition to the information of the uplink data shown in Example 1 or Example 2, the second request message further includes information on the data volume of the remaining uplink data and third indication information, and the second network device determines to send the context of the terminal to the first network device. The context of the terminal includes the source PDCP configuration and the source RLC configuration.

[0250] It should be noted that if the second network device determines to send the context of the terminal to the first network device, the second network device determines the context of the terminal according to the first identifier included in the second request message and sends the context of the terminal to the first network device.

[0251] It should be noted that the above first threshold, second threshold, third threshold or fourth threshold can be preset or set by the user according to needs, without limitation.

[0252] Optionally, after the second network device determines whether to send the context of the terminal to the first network device according to the second request message, the second network device sends a second response message to the first network device. When the second network device determines to send the context of the terminal to the first network device, the second response message includes the context of the terminal; when the second network device determines not to send the context of the terminal to the first network device, the second response message is used to indicate that the second network device does not send the context of the terminal to the first network device.

[0253] Optionally, the second response message includes at least one of the following information: the capabilities of the terminal's CG, service model information, or the CG configuration information of the terminal under the second network device.

[0254] Optionally, the second response message is also used to establish a communication tunnel between the first network device and the second network device.

[0255] It should be noted that the case where the second response message includes at least one of the capabilities of the terminal's CG, service model information, or the CG configuration information of the terminal under the second network device, and the case where the second response message is also used to establish a communication tunnel between the first network device and the second network device can refer to the introduction in the above first response message and will not be elaborated.

[0256] Optionally, the second response message is a Retrieve UE Context Response message.

[0257] It can be understood that if the second response message includes the context of the terminal, the second network device can release the first data channel; if the second response message indicates that the second network device does not send the context of the terminal to the first network device, the second network device can retain the first data channel.

[0258] Correspondingly, the first network device receives a second response message from the second network device.

[0259] In a possible implementation, the second response message includes a source PDCP configuration, and the first network device obtains uplink data according to the source PDCP configuration. Subsequently, the first network device may establish a second data channel with the core network and send the uplink data to the core network device through the second data channel; or, the first network device sends the uplink data to the second network device, and after receiving the uplink data, the second network device sends the uplink data to the core network device through the first data channel. Among them, the introduction of the second data channel can refer to the description in the above first response message and will not be elaborated.

[0260] In a possible implementation, the second response message includes a source PDCP configuration and a source RLC configuration, and the first network device obtains uplink data according to the source PDCP configuration and the source RLC configuration. Subsequently, the first network device may establish a second data channel with the core network and send the uplink data to the core network device through the second data channel; or, the first network device sends the uplink data to the second network device, and after receiving the uplink data, the second network device sends the uplink data to the core network device through the first data channel.

[0261] In a possible implementation, the second response message instructs the second network device to determine not to send the context of the terminal to the first network device, and the first network device deletes the uplink data stored locally; or, the first network device sends an indication message to the terminal to re-send the uplink data; or, the first network device sends the uplink data to the second network device. Further, the first network device sends the above uplink data to the second network device through the above communication tunnel. It can be understood that the uplink data sent by the first network device may be uplink data received from the terminal and not processed by the first network device. After receiving the uplink data, the second network device may process the uplink data according to the context of the terminal and send the processed uplink data to the core network device through the first data channel. Subsequently, the second network device may send an RRC release message to the terminal through the first network device, and the RRC release message is used to notify that the RRC state of the terminal is the RRC inactive state or the RRC idle state.

[0262] In a possible implementation, if the first network device does not receive the second response message within a preset time, the first network device deletes the uplink data stored locally; or, the first network device sends indication information for resending the uplink data to the terminal; or, the first network device sends the uplink data to the second network device. Further, the first network device sends the above-mentioned uplink data to the second network device through the above-mentioned communication tunnel. It can be understood that the uplink data sent by the first network device can be the uplink data received from the terminal and not processed by the first network device. After receiving the uplink data, the second network device can process the uplink data according to the context of the terminal and send the processed uplink data to the core network device through the first data channel. Subsequently, the second network device can send an RRC release message to the terminal through the first network device. The RRC release message is used to notify that the RRC state of the terminal is the RRC inactive state or the RRC idle state.

[0263] It should be noted that the second request message can also be used to request the second network device to release the first data channel and to request the second network device to send the context of the terminal to the first network device. In this case, for the specific process of the second network device determining whether to release the first data channel and whether to send the context of the terminal to the first network device according to the second request message, reference can be made to the introduction in the above-mentioned content where the second request message is used to request the second network device to release the first data channel and the above-mentioned content where the second request message is used to request the second network device to send the context of the terminal to the first network device, and details are not described herein.

[0264] Based on Figure 3 the method shown above, after receiving the first request message from the terminal, the first network device can send a second request message to the second network device according to the first request message, so that the second network device can determine whether to release the first data channel according to the second request message, or so that the second network device can determine whether to send the context of the terminal to the first network device according to the second request message. In this way, the second network device can decide whether to release the first data channel according to the second request message, or the second network device can decide whether to send the context of the terminal to the first network device according to the second request message, improving the flexibility of the first network device and the second network device in processing uplink data.

[0265] Figure 3 For the method shown above where the second network device decides whether to release the first data channel or decides whether to send the context of the terminal to the first network device, in addition, the first network device can also decide whether to release the first data channel or decide whether to send the context of the terminal to the first network device. Specifically, as Figure 4 shown, another communication method provided by an embodiment of the present application includes step 401-step 402.

[0266] Step 401: The terminal sends a first request message to the first network device.

[0267] For the description of step 401, reference can be made to the introduction in step 301 above, and details are not repeated here.

[0268] Step 402: The first network device receives the first request message from the terminal, and determines whether to establish a second data channel with the core network device according to the first request message; or determines whether to request the context of the terminal from the second network device according to the first request message.

[0269] Among them, the core network device may be Figure 1A the core network device 106 in. The second data channel is used for the first network device to forward the uplink data sent by the terminal to the core network device, or the second data channel is used for the first network device to receive the data to be sent to the terminal from the core network device. If a second data channel is established between the first network device and the core network device, the first network device is the anchor node of the terminal.

[0270] Optionally, the first network device also receives uplink data from the terminal. For the description of the uplink data and the first request message, reference can be made to that described in step 301 above, and details are not repeated here. The processing process of the first request message and the uplink data received from the terminal by the first network device can be referred to that described in step 302 above, and details are not repeated here.

[0271] Optionally, the first network device also receives a buffer status report from the terminal. The buffer status report is used to indicate the data volume of the remaining uplink data. For the introduction of the buffer status report and the data volume of the remaining uplink data, reference can be made to that described in step 302 above, and details are not repeated here.

[0272] It should be noted that if the data volume of the remaining uplink data is greater than or equal to the second threshold, the first network device and the terminal establish an RRC connection so that the terminal can send the remaining uplink data to the first network device.

[0273] Optionally, the first network device also receives the CG capability of the terminal from the terminal. In this case, the first network device can determine whether to configure CG for the terminal according to the CG capability of the terminal. A possible implementation method is that if the CG capability of the terminal indicates that the terminal supports CG, the first network device determines to configure CG for the terminal.

[0274] Optionally, when the first network device determines to configure CG for the terminal, the first network device sends third indication information to the second network device, and the third indication information is used to indicate that the first network device has the ability to configure CG for the terminal.

[0275] It can be understood that when the first network device receives uplink data from the terminal and the uplink data and the first request message are multiplexed in one message, when the first network device receives uplink data from the terminal and the uplink data is encapsulated in the first request message, when the first network device does not receive the uplink data, when the first network device receives a buffer status report from the terminal, and when the first network device receives the capabilities of the CG of the terminal from the terminal, the process by which the first network device determines whether to establish a second data channel with the core network device based on the first request message is different, and the process by which the first network device determines whether to request the context of the terminal from the second network device based on the first request message is different.

[0276] First, introduce the specific process by which the first network device determines whether to establish a second data channel with the core network device based on the first request message.

[0277] In a possible implementation, when the uplink data and the first request message are multiplexed in one message, the first network device determines whether to establish a second data channel with the core network device based on the first request message and the uplink data. Among them, the first network device determines whether to establish a second data channel with the core network device based on the first request message and the uplink data, including: the first network device determines the information of the uplink data based on the first request message and the uplink data; the first network device determines whether to establish a second data channel with the core network device based on the information of the uplink data.

[0278] Among them, the information of the uplink data may include at least one of the following: the first indication information, the second indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data. The introduction of the first indication information, the second indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data can refer to that described in step 302 above and will not be elaborated.

[0279] There are the following two situations for the first network device to determine whether to establish a second data channel with the core network device based on the information of the uplink data:

[0280] Situation 5: The information of the uplink data includes at least one of the first indication information, the second indication information, or the source LCID corresponding to the uplink data, and the first network device determines to establish a second data channel with the core network device; or, the first network device determines not to establish a second data channel with the core network device. In this case, the first network device can determine whether to establish a second data channel with the core network device according to its own load, etc. For example, if the load of the first network device is greater than or equal to the third threshold, the first network device determines not to establish a second data channel with the core network device; if the load of the first network device is less than or equal to the third threshold, the first network device determines to establish a second data channel with the core network device.

[0281] Scenario 6: The information of the uplink data includes at least the data volume of the uplink data. When the data volume of the uplink data is greater than or equal to the first threshold, the first network device determines to establish a second data channel with the core network device; when the data volume of the uplink data is less than or equal to the first threshold, the second network device determines not to establish a second data channel with the core network device.

[0282] In a possible implementation, when the uplink data is encapsulated in the first request message, the first network device determines whether to establish a second data channel with the core network device according to the first request message. Among them, the first network device determines whether to establish a second data channel with the core network device according to the first request message, including: the first network device determines the information of the uplink data according to the first request message; the first network device determines whether to establish a second data channel with the core network device according to the information of the uplink data.

[0283] Among them, the information of the uplink data may include at least one of the following: the first indication information, the fourth indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data. The introductions of the first indication information, the fourth indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data can refer to those described in step 302 above and will not be elaborated here.

[0284] There are the following two cases for the first network device to determine whether to establish a second data channel with the core network device according to the information of the uplink data:

[0285] Scenario 7: The information of the uplink data includes at least one of the first indication information, the fourth indication information, or the source LCID corresponding to the uplink data. The first network device determines not to establish a second data channel with the core network device; or, the first network device determines to establish a second data channel with the core network device. In this case, the first network device can determine whether to establish a second data channel with the core network device according to its own load, etc. For example, if the load of the first network device is greater than or equal to the third threshold, the first network device determines not to establish a second data channel with the core network device; if the load of the first network device is less than or equal to the third threshold, the first network device determines to establish a second data channel with the core network device.

[0286] Scenario 8: The information of the uplink data includes at least the data volume of the uplink data. When the data volume of the uplink data is greater than or equal to the first threshold, the first network device determines to establish a second data channel with the core network device; when the data volume of the uplink data is less than or equal to the first threshold, the first network device does not establish a second data channel with the core network device.

[0287] In a possible implementation, when the first network device does not receive uplink data, the first network device determines whether to establish a second data channel with the core network device according to the first request message. Among them, the first network device determines whether to establish a second data channel with the core network device according to the first request message, including: the first network device determines the information of the uplink data according to the first request message; the first network device determines whether to establish a second data channel with the core network device according to the information of the uplink data.

[0288] Among them, the information of the uplink data includes the fifth indication information. The introduction of the fifth indication information can refer to that described in step 302 above and will not be elaborated here. In this case, the first network device determines to establish a second data channel with the core network device.

[0289] In a possible implementation, in addition to the information of the uplink data shown in case 5 or case 7, the first network device also determines whether to establish a second data channel with the core network device according to the buffer status report. In this case, if the data volume of the remaining uplink data is greater than or equal to the second threshold, the first network device determines to establish a second data channel with the core network device; if the data volume of the remaining uplink data is less than or equal to the second threshold, the first network device determines not to establish a second data channel with the core network device.

[0290] In a possible implementation, in addition to the information of the uplink data shown in case 5 or case 7, the first network device also determines whether to establish a second data channel with the core network device according to the capabilities of the CG of the terminal. In this case, the first network device determines to establish a second data channel with the core network device; or, the first network device determines not to establish a second data channel with the core network device. In this case, the first network device can determine whether to establish a second data channel with the core network device according to its own load, etc. For example, if the load of the first network device is greater than or equal to the third threshold, the first network device determines not to establish a second data channel with the core network device; if the load of the first network device is less than or equal to the third threshold, the first network device determines to establish a second data channel with the core network device.

[0291] In a possible implementation, in addition to the information of the uplink data shown in case 5 or case 7, the first network device also determines whether to establish a second data channel with the core network device according to the buffer status report and the capabilities of the CG of the terminal. In this case, if the data volume of the remaining uplink data is greater than or equal to the second threshold, the first network device determines to establish a second data channel with the core network device; if the data volume of the remaining uplink data is less than or equal to the second threshold, the first network device determines not to establish a second data channel with the core network device.

[0292] In a possible implementation, in addition to the information of the uplink data shown in Case 6 or Case 8, the first network device determines whether to establish a second data channel with the core network device according to the received buffer status report. In this case, if the data volume of the remaining uplink data is greater than or equal to the second threshold, the first network device determines to establish a second data channel with the core network device; if the data volume of the remaining uplink data is less than or equal to the second threshold, the first network device determines not to establish a second data channel with the core network device.

[0293] In a possible implementation, in addition to the information of the uplink data shown in Case 6 or Case 8, the first network device also determines whether to establish a second data channel with the core network device according to the buffer status report. In this case, if the data volume of the uplink data is greater than or equal to the first threshold, the first network device determines to establish a second data channel with the core network device; if the data volume of the uplink data is less than or equal to the first threshold, the first network device does not establish a second data channel with the core network device.

[0294] In a possible implementation, in addition to the information of the uplink data shown in Case 6 or Case 8, the first network device also determines whether to establish a second data channel with the core network device according to the capability of the CG of the terminal. In this case, if the data volume of the uplink data is greater than or equal to the first threshold, the first network device determines to establish a second data channel with the core network device; if the data volume of the uplink data is less than or equal to the first threshold, the first network device does not establish a second data channel with the core network device.

[0295] In a possible implementation, in addition to the information of the uplink data shown in Case 6 or Case 8, the first network device also determines whether to establish a second data channel with the core network device according to the buffer status report and the capability of the CG of the terminal. In this case, if the data volume of the remaining uplink data is greater than or equal to the second threshold, the first network device determines to establish a second data channel with the core network device; if the data volume of the remaining uplink data is less than or equal to the second threshold, the first network device determines not to establish a second data channel with the core network device.

[0296] In a possible implementation, in addition to the information of the uplink data shown in Case 6 or Case 8, the first network device also determines whether to establish a second data channel with the core network device according to the buffer status report and the capability of the CG of the terminal. In this case, if the data volume of the uplink data is greater than or equal to the first threshold, the first network device determines to establish a second data channel with the core network device; if the data volume of the uplink data is less than or equal to the first threshold, the first network device does not establish a second data channel with the core network device.

[0297] In a possible implementation, in addition to the information of the uplink data shown in Example 3, the first network device also determines whether to establish a second data channel with the core network device based on the buffer status report and / or the capabilities of the CG of the terminal. In this case, the first network device determines to establish a second data channel with the core network device.

[0298] The following describes the specific process of the first network device determining whether to request the context of the terminal from the second network device according to the first request message.

[0299] In a possible implementation, when the uplink data and the first request message are multiplexed in one message, the first network device determines whether to request the context of the terminal from the second network device according to the first request message and the uplink data. Among them, the first network device determining whether to request the context of the terminal from the second network device according to the first request message and the uplink data includes: the first network device determines the information of the uplink data according to the first request message and the uplink data; the first network device determines whether to request the context of the terminal from the second network device according to the information of the uplink data.

[0300] Among them, the information of the uplink data may include at least one of the following: the first indication information, the second indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data. The introduction of the first indication information, the second indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data can refer to that described in step 302 above and will not be elaborated.

[0301] In this case, the first network device determines to request the context of the terminal from the second network device, and the context of the terminal includes the source PDCP configuration and the source RLC configuration; or, the first network device determines not to request the context of the terminal from the second network device. In this case, the first network device may determine whether to request the context of the terminal from the second network device according to its own remaining storage resources, etc. For example, if the remaining storage resources of the first network device are greater than or equal to the fifth threshold, the first network device determines to request the context of the terminal from the second network device; if the remaining storage resources of the first network device are less than or equal to the fifth threshold, the second network device determines not to request the context of the terminal from the second network device.

[0302] In addition to the information of the uplink data described above, the first network device may also determine whether to request the context of the terminal from the second network device based on the capabilities of the CG of the terminal, or the first network device may also determine whether to request the context of the terminal from the second network device based on the buffer status report and the capabilities of the CG of the terminal. If the first network device determines to configure the CG for the terminal based on the capabilities of the CG of the terminal, the first network device determines to request the context of the terminal from the second network device, and the context of the terminal includes the source PDCP configuration and the source RLC configuration; if the first network device determines not to configure the CG for the terminal based on the capabilities of the CG of the terminal, the first network device determines to request the context of the terminal from the second network device, and the context of the terminal includes the source PDCP configuration and the source RLC configuration; or, the first network device determines not to request the context of the terminal from the second network device.

[0303] In a possible implementation, when the uplink data is encapsulated in the first request message, the first network device determines whether to request the context of the terminal from the second network device based on the first request message. Among them, the first network device determines whether to request the context of the terminal from the second network device based on the first request message, including: the first network device determines the information of the uplink data according to the first request message; the first network device determines whether to request the context of the terminal from the second network device according to the information of the uplink data.

[0304] Among them, the information of the uplink data may include at least one of the following: the first indication information, the fourth indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data. The introduction of the first indication information, the fourth indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data can refer to that described in step 302 above and will not be elaborated.

[0305] In this case, in this case, the first network device determines to request the context of the terminal from the second network device, and the context of the terminal includes the source PDCP configuration; or, the first network device determines not to request the context of the terminal from the second network device. In this case, the first network device may determine whether to request the context of the terminal from the second network device according to its own remaining storage resources, etc. For example, if the remaining storage resources of the first network device are greater than or equal to the fifth threshold, the first network device determines to request the context of the terminal from the second network device; if the remaining storage resources of the first network device are less than or equal to the fifth threshold, the second network device determines not to request the context of the terminal from the second network device.

[0306] In addition to the information of the uplink data described above, the first network device may also determine whether to request the context of the terminal from the second network device according to the capabilities of the CG of the terminal, or the first network device may also determine whether to request the context of the terminal from the second network device according to the buffer status report and the capabilities of the CG of the terminal. If the first network device determines to configure the CG for the terminal according to the capabilities of the CG of the terminal, the first network device determines to request the context of the terminal from the second network device, and the context of the terminal includes the source PDCP configuration; if the first network device determines not to configure the CG for the terminal according to the capabilities of the CG of the terminal, the first network device determines to request the context of the terminal from the second network device, and the context of the terminal includes the source PDCP configuration; or, the first network device determines not to request the context of the terminal from the second network device.

[0307] In a possible implementation, when the first network device does not receive uplink data, the first network device determines whether to request the context of the terminal from the second network device according to the first request message. Among them, the first network device determines whether to request the context of the terminal from the second network device according to the first request message, including: the first network device determines the information of the uplink data according to the first request message; the first network device determines whether to request the context of the terminal from the second network device according to the information of the uplink data.

[0308] Among them, the information of the uplink data includes the fifth indication information. The introduction of the fifth indication information can refer to that described in step 302 above and will not be elaborated here. In this case, the first network device determines to request the context of the terminal from the second network device, and the context of the terminal includes the source PDCP configuration and the source RLC configuration.

[0309] It should be noted that the above first threshold, the above second threshold, the above third threshold, or the above fifth threshold may be preset or set by the user according to needs, without limitation.

[0310] Based on Figure 4 the method shown, after receiving the first request message from the terminal, the first network device may determine whether to establish a second data channel with the core network device according to the first request message; or determine whether to request the context of the terminal from the second network device according to the first request message. In this way, the flexibility of the first network device and the second network device in processing uplink data is improved.

[0311] Further optionally, when the first network device determines to establish a second data channel with the core network device, or when the first network device determines not to establish a second data channel with the core network device, or when the first network device determines to request the context of the terminal from the second network device, the first network device sends a communication message to the second network device. Specifically, as Figure 5 shown, Figure 4The method shown also includes step 403.

[0312] Step 403: The first network device sends a notification message to the second network device.

[0313] When the first network device determines to establish a second data channel with the core network device, when the first network device determines not to establish a second data channel with the core network device, and when the first network device determines to request the context of the terminal from the second network device, the functions of the notification message are different. Specifically, the notification message is introduced as follows:

[0314] Case 9: The first network device determines to establish a second data channel with the core network device, and this notification message is used to instruct the second network device to release the first data channel between the second network device and the core network device.

[0315] Among them, the first data channel is used for the second network device to forward the uplink data sent by the terminal to the core network device, or the first data channel is used for the second network device to receive the data to be sent to the terminal from the core network device. At this time, the second network device is the anchor node of the terminal. Subsequently, the first network device can send the above uplink data to the core network device through the second data channel. The first network device can also send an RRC release message to the terminal to suspend the RRC connection between the first network device and the terminal.

[0316] In this case, the first network device can also receive a response message from the second network device, and this response message can be used to indicate that the second network device has successfully released the first data channel. The response message can include the context of the terminal, and the context of the terminal includes the source PDCP configuration and the source RLC configuration, so that the first network device can obtain the above uplink data according to the source PDCP configuration and the source RLC configuration and send the uplink data to the core network device. It can be understood that after the second network device sends the context of the terminal to the first network device, it releases the context of the terminal stored locally.

[0317] Case 10: The first network device determines not to establish a second data channel with the core network device, and this notification message is used to instruct the second network device to retain the first data channel between the second network device and the core network device.

[0318] Among them, the first data channel is used for the second network device to forward the uplink data sent by the terminal to the core network device, or the first data channel is used for the second network device to receive the data to be sent to the terminal from the core network device. At this time, the second network device is the anchor node of the terminal.

[0319] In this case, the first network device may also receive a response message from the second network device, and the response message is used to establish a communication tunnel between the first network device and the second network device. For the introduction of this communication tunnel, reference may be made to that described in step 303 above, which will not be elaborated here.

[0320] In this case, after the first network device receives the response message from the second network device, the first network device sends uplink data to the second network device. Further, the first network device sends the uplink data to the second network device through the above-mentioned communication tunnel. It can be understood that the uplink data sent by the first network device may be the uplink data received from the terminal and not processed by the first network device. After receiving the uplink data, the second network device may process the uplink data according to the context of the terminal, and send the processed uplink data to the core network device through the first data channel. Subsequently, the second network device may send an RRC release message to the terminal through the first network device, and the RRC release message is used to notify that the RRC state of the terminal is the RRC inactive state or the RRC idle state.

[0321] It should be noted that the uplink data sent by the first network device may also be the data received from the terminal and processed according to the context of the terminal. After receiving the uplink data, the second network device may send it to the core network device through the first data channel.

[0322] It can be understood that the uplink data may also be sent to the second network device in a notification message.

[0323] Situation 11: The first network device determines to request the context of the terminal from the second network device, and the notification message is used to instruct the second network device to send the context of the terminal to the first network device. The notification message includes a first identifier, so that the second network device can determine the context of the terminal according to the first identifier.

[0324] In this case, the first network device may also receive a response message from the second network device. The response message includes the context of the terminal. Subsequently, the first network device may obtain uplink data according to the context of the terminal.

[0325] Optionally, the context of the terminal includes the source PDCP configuration, or the source PDCP configuration and the source RLC configuration.

[0326] In a possible implementation, the context of the terminal includes the source PDCP configuration. The first network device obtains the uplink data according to the source PDCP configuration. Subsequently, the first network device may establish a second data channel with the core network and send the uplink data to the core network device through the second data channel; or, the first network device sends the uplink data to the second network device, and after receiving the uplink data, the second network device sends the uplink data to the core network device through the first data channel. Among them, the introduction of the second data channel can refer to that described in step 303 above and will not be elaborated here.

[0327] In another possible implementation, the context of the terminal includes the source PDCP configuration and the source RLC configuration. The first network device obtains the uplink data according to the source PDCP configuration and the source RLC configuration. Subsequently, the first network device may establish a second data channel with the core network and send the uplink data to the core network device through the second data channel; or, the first network device sends the uplink data to the second network device, and after receiving the uplink data, the second network device sends the uplink data to the core network device through the first data channel.

[0328] Optionally, if the first network device does not receive the response message within the preset time, the first network device may delete the uplink data stored locally; or, the first network device may send indication information for resending the uplink data to the terminal; or, the first network device sends the uplink data to the second network device. Further, the first network device sends the above uplink data to the second network device through the above communication tunnel. It can be understood that the uplink data sent by the first network device may be the uplink data received from the terminal and not processed by the first network device. After receiving the uplink data, the second network device may process the uplink data according to the context of the terminal and send the processed uplink data to the core network device through the first data channel. Subsequently, the second network device may send an RRC release message to the terminal through the first network device, and the RRC release message is used to notify that the RRC state of the terminal is the RRC inactive state or the RRC idle state.

[0329] It can be understood that if the notification message instructs the second network device to send the context of the terminal to the first network device, the second network device may release the first data channel.

[0330] Optionally, the response message in the above three cases further includes at least one of the capabilities of the CG of the terminal, the service model information, or the configuration information of the CG of the terminal under the second network device. The introduction of the capabilities of the CG of the terminal, the service model information, or the configuration information of the CG of the terminal under the second network device can be referred to in step 303 above and will not be elaborated here. Subsequently, the first network device may determine whether to configure the CG for the terminal according to the capabilities of the CG of the terminal. When the first network device determines to configure the CG for the terminal, it may configure the CG for the terminal with reference to the configuration information of the CG of the terminal under the second network device; the first network device may determine the possible data arrival period of the terminal, the possible transmission block size of the uplink data of the terminal, or the possible arrival timing of the terminal according to the service model information.

[0331] Based on Figure 5 the method shown above, when the first network device determines to establish a second data channel with the core network device, or when the first network device determines not to establish a second data channel with the core network device, or when the first network device determines to request the context of the terminal from the second network device and send a communication message to the second network device, it can thus notify the second network device to release the first data channel, or notify the second network device to retain the first data channel, or notify the second network device to send the context of the terminal to the first network device.

[0332] It can be understood that Figure 3 the first network device in the method shown above may be an architecture with CU-DU separation. When the first network device is an architecture with CU-DU separation, the embodiments of the present application provide a communication method that can enable the second network device to decide whether to release the first data channel, or decide whether to send the context of the terminal to the CU of the first network device. Specifically, as Figure 6 shown, this communication method includes step 601-step 604.

[0333] Step 601: The terminal sends a first request message to the first network element.

[0334] Among them, the terminal may be Figure 1A any one of terminals 103-104 in Figure 1C The first network element is DU 1012 or DU 1013 in

[0335] Optionally, the terminal is in the RRC inactive state. The previous serving network device of the terminal is the second network device. In other words, the second network device stores the context of the terminal, or the second network device has a data channel based on the terminal with the core network device. Among them, the second network device may be Figure 1A network device 102 in

[0336] In practical applications, when the terminal is in the RRC-connected state, it can receive an RRC release message from a second network device; the terminal can suspend the RRC connection with the second network device according to the RRC release message and enter the RRC-inactive state. Among them, the RRC release message includes a first identifier, which is used to identify the context of the terminal. The first identifier can be allocated by the second network device when the terminal receives this RRC release message this time, or can be allocated when the terminal previously received an RRC release message from the second network device. The first identifier is a unique identifier in multiple cells under different network devices. For example, the first identifier is the resume ID.

[0337] It should be noted that the above second network device can be replaced by a second network element. The second network element can be Figure 1C the CU 1011 in. When the second network device is replaced by a second network element, the terminal is in the service coverage area of a third network element before receiving the RRC release message. The third network element is different from the second network element. For example, if the second network element is Figure 1C the DU 1012 in, the third network element is Figure 1C the DU 1013 in; if the second network element is Figure 1C the DU 1013 in, the third network element is Figure 1C the DU1012 in. Figure 6 The method shown takes the previous serving network device of the terminal as the second network device as an example for introduction. For the situation where the terminal is in the service coverage area of a third network element before receiving the RRC release message, reference can be made to Figure 6 the method shown and will not be elaborated here.

[0338] Optionally, the RRC release message further includes a source RRC reconfiguration. After receiving the RRC release message, the terminal stores the source RRC reconfiguration. The source RRC reconfiguration is allocated by the second network device for the terminal. The source RRC reconfiguration includes a source DRB configuration, a source PDCP configuration, and a source RLC configuration. The source DRB configuration includes the mapping relationship between the source DRB and the source PDCP, and the mapping relationship between the source DRB and the source RLC. The source PDCP configuration includes the length of the source PDCP SN. The source RLC configuration includes the length or mode indication of the source RLC SN, for example, the acknowledged mode (AM) or the unacknowledged mode (UM), etc. The source RRC reconfiguration is used to process the uplink data when the terminal transmits uplink data next time.

[0339] Optionally, the terminal has mobility. When the terminal moves from the service coverage area of the second network device to the service coverage area of the first network element and there is uplink data arriving at the terminal, the terminal sends a first request message to the first network element. Among them, the uplink data can be user plane uplink data, and the first request message can be used to request the resumption of a suspended RRC connection. The first request message can be an RRC resume request, and the first request message includes the above-mentioned first identifier. The terminal can also send the uplink data to the first network element. The terminal can send the first request message and the uplink data simultaneously, or the terminal can also send the first request message and the uplink data separately. When the terminal sends the first request message and the uplink data simultaneously, the uplink data and the first request message are multiplexed in one message, or the uplink data is encapsulated in the first request message. For example, the terminal sends a first request message to the first network element, and the first request message includes the uplink data.

[0340] It can be understood that the first request message and the uplink data are sent to the first network element after being processed by the PDCP layer entity, RLC layer entity, MAC layer entity, and PHY entity of the terminal. This process can refer to the description in step 301 above, where the first request message and the uplink data are sent to the first network device after being processed by the PDCP layer entity, RLC layer entity, MAC layer entity, and PHY entity of the terminal, and will not be elaborated here.

[0341] Optionally, the first request message, or the first request message and the uplink data are sent to the first network element during the random process initiated by the terminal. For example, the first request message, or the first request message and the uplink data are sent to the first network element through the third message in the four-step random access process. Another example is that the first request message, or the first request message and the uplink data are sent to the first network element through message A in the two-step random access process.

[0342] Optionally, the first request message further includes a first identifier.

[0343] Optionally, the terminal can also send a buffer status report to the first network element. The introduction of the buffer status report can refer to that described in step 301 above and will not be elaborated here.

[0344] Optionally, the terminal can also send the capability of the terminal's CG to the first network element. The capability of the terminal's CG is used to indicate whether the terminal supports CG.

[0345] Step 602: The first network element receives the first request message from the terminal and sends information about the first request message and the uplink data to the second network element according to the first request message.

[0346] Optionally, the first network element may also receive uplink data from the terminal. The descriptions of the uplink data and the first request message may refer to those described in step 601 above and will not be elaborated here.

[0347] It should be noted that if the uplink data and the first request message are multiplexed in one message, the first network element may process the received first request message processed according to the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration based on the common RLC configuration, common MAC configuration, and common PHY configuration to obtain the first request message processed according to the common PDCP configuration; the first network element may process the received uplink data processed according to the source PDCP configuration, source RLC configuration, common MAC configuration, and common PHY configuration based on the common MAC configuration and common PHY configuration to obtain the uplink data processed according to the source PDCP configuration and source RLC configuration and the source LCID. Since the first network element does not know the source RLC configuration, it cannot obtain the uplink data processed according to the source PDCP configuration. If the first network element wants to obtain the uplink data processed according to the source PDCP configuration, it needs to request the context of the terminal from the second network element through the second network element.

[0348] It should be noted that if the uplink data is encapsulated in the first request message, the first network element may process the received first request message processed according to the common PDCP configuration, common RLC configuration, common MAC configuration, and common PHY configuration based on the common RLC configuration, common MAC configuration, and common PHY configuration to obtain the first request message processed according to the common PDCP configuration. Subsequently, the first network element may send the first request message processed according to the common PDCP configuration to the second network element so that the second network element processes the first request message processed according to the common PDCP configuration based on the common PDCP configuration to obtain the first request message.

[0349] It can be understood that when the first network element receives the uplink data from the terminal and the uplink data and the first request message are multiplexed in one message, when the uplink data is encapsulated in the first request message, and when the first network element does not receive the uplink data, the content included in the information of the uplink data is different. Specifically, it can be as shown in the following Examples 4 - 6.

[0350] Example 4: When the uplink data and the first request message are multiplexed in one message, the first network element sends information about the first request message and the uplink data to the second network element according to the first request message and the uplink data. Among them, the first network element sending information about the first request message and the uplink data to the second network element according to the first request message and the uplink data includes: the first network element determining information about the uplink data according to the first request message and the uplink data; the first network element sending information about the first request message and the uplink data to the second network element.

[0351] Among them, the information about the uplink data may include at least one of the following: first indication information, second indication information, the data volume of the uplink data, the source LCID corresponding to the uplink data, and the number information of the logical channel corresponding to the uplink data.

[0352] Among them, the first indication information may be used to indicate that the uplink data has reached the first network element; or, the first indication information is used to indicate that the uplink data is sent to the first network element through the third message in the four-step random access procedure; or, the first indication information is used to indicate that the uplink data is sent to the first network element through message A in the two-step random access procedure; or, the first indication information is used to indicate that the terminal initiates EDT, so that the second network element can determine whether the first network device has received the uplink data. The number information of the logical channel corresponding to the uplink data is used to indicate the number of logical channels corresponding to the uplink data.

[0353] Among them, the introduction of the second indication information, the data volume of the uplink data, and the source LCID corresponding to the uplink data can refer to that described in step 302 above and will not be elaborated.

[0354] Example 5: When the uplink data is encapsulated in the first request message, the first network element sends the first request message to the second network element according to the first request message. Among them, the first network element sending information about the first request message and the uplink data to the second network element according to the first request message includes: the first network element determining information about the uplink data according to the first request message; the first network element sending information about the first request message and the uplink data to the second network element.

[0355] Among them, the information about the uplink data may include at least one of the following: first indication information, fourth indication information, the data volume of the uplink data, the source LCID corresponding to the uplink data, and the number information of the logical channel corresponding to the uplink data.

[0356] Among them, the introduction of the first indication information, the data volume of the uplink data, the source LCID corresponding to the uplink data, and the number information of the logical channel corresponding to the uplink data can refer to that described in Example 4 above and will not be elaborated.

[0357] Among them, the fourth indication information can be used to indicate that the uplink data is included in the first request message, so that the second network element can determine that the context of the terminal required by the second network element includes the source PDCP configuration.

[0358] Example 6: When the first network element does not receive uplink data, the first network element sends the first request message and the information of the uplink data to the second network element according to the first request message. Among them, the first network element sending the first request message and the information of the uplink data to the second network element according to the first request message includes: the first network element determining the information of the uplink data according to the first request message; the first network element sending the first request message and the information of the uplink data to the second network element.

[0359] Among them, the information of the uplink data includes the fifth indication information. The fifth indication information can be used to indicate that the uplink data has not reached the first network element; or, the fifth indication information is used to indicate that the uplink data has not been sent to the first network element through the third message in the four-step random access procedure; or, the fifth indication information is used to indicate that the uplink data has not been sent to the first network element through message A in the two-step random access procedure; or, the fifth indication information is used to indicate that the terminal initiates a non-EDT, so that the second network element can determine whether the first network element has received the uplink data.

[0360] Optionally, the first network element also receives a buffer status report from the terminal. The buffer status report is used to indicate the data volume of the remaining uplink data. The information of the data volume of the remaining uplink data can be sent to the second network element together with the first request message and the information of the uplink data, or can be sent separately, without limitation. The introduction of the buffer status report and the information of the data volume of the remaining uplink data can refer to that described in step 302 above, and will not be elaborated here.

[0361] It should be noted that if the data volume of the remaining uplink data is greater than or equal to the second threshold, the first network element and the terminal establish an RRC connection so that the terminal can send the remaining uplink data to the first network element. For example, if the data volume of the remaining uplink data is greater than or equal to the second threshold, the first network element receives a first message from the second network element. The first message is used to indicate that the first network element establishes an RRC connection with the terminal.

[0362] Optionally, the first network element also receives the capability of the terminal's CG from the terminal. In this case, the first network element also sends the capability of the terminal's CG to the second network element so that the second network element can determine whether to configure CG for the terminal according to the capability of the terminal's CG.

[0363] Step 603: The second network element receives the first request message and the information of the uplink data from the first network element, and sends a second request message to the second network device according to the first request message and the information of the uplink data.

[0364] Among them, the second request message can be used to request the second network device to release the first data channel between the second network device and the core network device; or, the second request message can be used to request the second network device to send the context of the terminal to the second network element. The second request message includes information about uplink data. The second request message can be carried in a Retrieve UE Context Request message. Among them, the core network device can be Figure 1A the core network device 106 in

[0365] Optionally, the second request message is used to request the second network device to release the first data channel between the second network device and the core network device, and the information about uplink data is used by the second network device to determine whether to release the first data channel; the second request message is used to request the second network device to send the context of the terminal to the second network element, and the information about uplink data is used by the second network device to determine whether to send the context of the terminal to the second network element.

[0366] Optionally, the second network element also receives information about the data volume of the remaining uplink data from the first network element. In this case, the second request message may further include information about the data volume of the remaining uplink data.

[0367] It should be noted that if the data volume of the remaining uplink data is greater than or equal to the second threshold, the second network element may instruct the first network element and the terminal to establish an RRC connection. For example, if the data volume of the remaining uplink data is greater than or equal to the second threshold, the second network element sends a first message to the first network element, and the first message is used to instruct the first network element to establish an RRC connection with the terminal.

[0368] Optionally, the second network element also receives the CG capability of the terminal from the first network element. In this case, the second network element may determine whether to configure CG for the terminal according to the CG capability of the terminal. A possible implementation is that if the CG capability of the terminal indicates that the terminal supports CG, the second network element determines to configure CG for the terminal.

[0369] Optionally, when the second network element determines to configure CG for the terminal, the second request message may further include third indication information, and the third indication information is used to indicate that the second network element has the ability to configure CG for the terminal.

[0370] Optionally, the second request message further includes a first identifier.

[0371] Step 604: The second network device receives a second request message from the second network element, and determines whether to release the first data channel with the core network device according to the second request message; or determines whether to send the context of the terminal to the second network element according to the second request message.

[0372] Among them, the introduction of the second request message can refer to that described in step 603 above, and will not be elaborated here.

[0373] For the specific process of the second network device determining whether to release the first data channel according to the second request message, and the specific process of the second network device determining whether to send the context of the terminal to the second network element according to the second request message, reference can be made to the corresponding introduction in step 303 above, and will not be elaborated here. The difference is that after the second network device determines whether to release the first data channel according to the second request message, the second network device sends a first response message to the second network element; after the second network device determines whether to send the context of the terminal to the second network element according to the second request message, the second network device sends a second response message to the second network element. The introduction of the first response message and the second response message can refer to the corresponding introduction in step 303 above, and will not be elaborated here.

[0374] Correspondingly, the second network element receives the first response message from the second network device; or the second network element receives the second response message from the second network device.

[0375] It can be understood that since the functions of the first response message / second response message are different, the processing methods of the second network element after receiving the first response message / second response message are different. Specifically, the processing methods of the second network element after receiving the first response message / second response message can be as follows:

[0376] Method 1: The first response message instructs the second network device to release the first data channel, and the second network element establishes a second data channel with the core network device.

[0377] Among them, the second data channel is used for the second network element to forward the uplink data sent by the terminal to the core network device, or the second data channel is used for the second network element to receive the data to be sent to the terminal from the core network device.

[0378] Optionally, after receiving the first response message from the second network device, the second network element sends indication information to the first network element to indicate a communication tunnel between the second network element and the first network element. This communication tunnel is used to transmit uplink data. For example, this communication tunnel is a GTP tunnel. This communication tunnel can be a newly established communication tunnel or a previously established communication tunnel. The indication information may include the IP address of the second network element, the tunnel endpoint identifier (TEID) of this communication tunnel, and the source LCID. The indication information may further include the source DRB identifier. The indication information may indicate one communication tunnel or multiple communication tunnels. When the indication information indicates multiple communication tunnels, the second network element may use all the communication tunnels to receive the uplink data sent by the first network element, or may use some of the communication tunnels to receive the uplink data sent by the first network element. The second network element may also determine the number of this communication tunnel according to the number of logical channels corresponding to the uplink data or the number of logical channels in the context of the terminal.

[0379] Optionally, when the first response message includes the context of the terminal, the second network element may further send the source RLC configuration to the first network element, so that the first network element can obtain the uplink data processed according to the source PDCP configuration based on the configuration of the source RLC. This RLC configuration may be the source RCL configuration corresponding to the source LCID. Subsequently, the second network element may receive, through this communication tunnel, the uplink data processed according to the source PDCP configuration from the first network element. After receiving the uplink data processed according to the source PDCP configuration, the second network element may obtain the uplink data according to the source PDCP configuration and send the uplink data to the core network device through the second data channel. The second network element may also send an RRC release message to the terminal through the first network element to suspend the RRC connection between the second network element and the terminal.

[0380] Method 2: The first response message instructs the second network device to retain the first data channel, and the second network element sends uplink data to the second network device.

[0381] A possible implementation is that the second network element obtains uplink data from the first network element. Exemplarily, the second network element sends indication information to the first network element to indicate a communication tunnel between the second network element and the first network element. This communication tunnel is used to transmit uplink data, and the second network element receives the uplink data from the first network element through this communication tunnel. The introduction of the indication information and the communication tunnel may refer to that described in Method 1 above.

[0382] Optionally, when the first response message includes the context of the terminal, the second network element may also send the source RLC configuration to the first network element, so that the first network element can obtain the uplink data processed according to the source PDCP configuration based on the configuration of the source RLC. The RLC configuration may be the source RCL configuration corresponding to the source LCID. Subsequently, the second network element may receive, through the communication tunnel, the uplink data processed according to the source PDCP configuration from the first network element. After receiving the uplink data processed according to the source PDCP configuration, the second network element may obtain the uplink data based on the source PDCP configuration, and send the uplink data to the second network device through the communication tunnel between the second network element and the second network device. After receiving the uplink data, the second network device sends the uplink data to the core network device through the first data channel. Subsequently, the second network device may send an RRC release message to the terminal through the second network element and the first network element. The RRC release message is used to notify that the RRC state of the terminal is the RRC inactive state or the RRC idle state.

[0383] It should be noted that the uplink data sent by the first network element to the second network element may be the uplink data received from the terminal and not processed by the first network element. After receiving the uplink data, the second network element may send the uplink data to the second network device. After receiving the uplink data, the second network device may process the uplink data according to the context of the terminal, and send the processed uplink data to the core network device through the first data channel.

[0384] Method 3: The second response message includes the source PDCP configuration, and the second network element obtains the uplink data according to the source PDCP configuration.

[0385] A possible implementation is that the second network element obtains the uplink data from the first network element. Exemplarily, the second network element sends indication information for indicating the communication tunnel between the second network element and the first network element to the first network element. The communication tunnel is used to transmit the uplink data. The introduction of the indication information and the communication tunnel may refer to that described in the above Method 1. The second network element may receive, through the communication tunnel, the uplink data processed according to the source PDCP configuration from the first network element. After receiving the uplink data processed according to the source PDCP configuration, the second network element may obtain the uplink data based on the source PDCP configuration. Subsequently, the second network element may establish a second data channel with the core network and send the uplink data to the core network device through the second data channel; or, the second network element sends the uplink data to the second network device, and after receiving the uplink data, the second network device sends the uplink data to the core network device through the first data channel.

[0386] Method 4: The second response message includes the source PDCP configuration and the source RLC configuration. The second network element sends a second message to the first network element. The second message includes the source RLC configuration so that the first network element can obtain the uplink data processed according to the source PDCP configuration based on the source RLC configuration. The second message may further include indication information for indicating the communication tunnel between the second network element and the first network element. This communication tunnel is used to transmit the uplink data. The introduction of this indication information and the communication tunnel can refer to that described in Method 1 above. The second network element may receive the uplink data processed according to the source PDCP configuration from the first network element through this communication tunnel. After receiving the uplink data processed according to the source PDCP configuration, the second network element can obtain the uplink data according to the source PDCP configuration. Subsequently, the second network element may establish a second data channel with the core network and send the uplink data to the core network device through the second data channel; or, the second network element sends the uplink data to the second network device, and after receiving the uplink data, the second network device sends the uplink data to the core network device through the first data channel.

[0387] Method 5: The second response message instructs the second network device to determine not to send the context of the terminal to the second network element. The second network element sends a third message to the first network element. The third message is used to instruct the first network element to delete the uplink data stored locally; or, the third message is used to instruct the first network element to send indication information for re-sending the uplink data to the terminal; or, the third message instructs the first network element to send the uplink data received from the terminal and not processed by the first network element to the second network element. After receiving the uplink data, the second network element sends the uplink data to the second network device. After receiving the uplink data, the second network device can process the uplink data according to the context of the terminal and send the processed uplink data to the core network device through the first data channel.

[0388] It can be understood that if the second network element does not receive the second response message within the preset time, the second network element may also send the above-mentioned third message to the first network element.

[0389] It should be noted that the second request message may also be used to request the second network device to release the first data channel and to request the second network device to send the context of the terminal to the second network element. In this case, the specific process for the second network device to determine whether to release the first data channel and whether to send the context of the terminal to the second network element according to the second request message can refer to the introduction in the above-mentioned second request message for requesting the second network device to release the first data channel and the above-mentioned second request message for requesting the second network device to send the context of the terminal to the second network element, which will not be elaborated here.

[0390] Based on Figure 6In the method shown, after the first network element receives the first request message from the terminal, it may send the first request message and information on uplink data to the second network element according to the first request message. After receiving the first request message and the information on uplink data, the second network element may send a second request message to the second network device, so that the second network device determines whether to release the first data channel according to the second request message, or so that the second network device determines whether to send the context of the terminal to the second network element according to the second request message. In this way, the second network device can decide whether to release the first data channel according to the second request message, or the second network device can decide whether to send the context of the terminal to the second network element according to the second request message, improving the flexibility of the second network element and the second network device in processing uplink data.

[0391] It can be understood that Figure 4 or Figure 5 The first network device in the method shown may be an architecture with CU-DU separation. When the first network device is an architecture with CU-DU separation, an embodiment of the present application provides a communication method, which can enable the CU of the first network device to decide whether to establish a second data channel with the core network device, or decide whether to request the context of the terminal from the second network device. Specifically, as Figure 7 shown, this communication method includes step 701-step 703.

[0392] Step 701: The terminal sends a first request message to the first network element.

[0393] Step 702: The first network element receives the first request message from the terminal, and sends the first request message and information on uplink data to the second network element according to the first request message.

[0394] The descriptions of step 701-step 702 can be referred to the above step 601-step 602 and will not be elaborated.

[0395] Step 703: The second network element receives the first request message and information on uplink data from the first network element, and determines whether to establish a second data channel with the core network according to the first request message and the information on uplink data; or determines whether to request the context of the terminal from the second network device according to the first request message and the information on uplink data.

[0396] Among them, the core network device may be Figure 1A the core network device 106 in. The second data channel is used for the second network element to forward the uplink data sent by the terminal to the core network device, or the second data channel is used for the second network element to receive the data to be sent to the terminal from the core network device.

[0397] Optionally, the second network element also receives information on the amount of remaining uplink data from the first network element.

[0398] It should be noted that if the amount of remaining uplink data is greater than or equal to the second threshold, the second network element may instruct the first network element and the terminal to establish an RRC connection. For example, if the amount of remaining uplink data is greater than or equal to the second threshold, the second network element sends a first message to the first network element, and the first message is used to instruct the first network element to establish an RRC connection with the terminal.

[0399] Optionally, the second network element also receives the CG capability of the terminal from the first network element. In this case, the second network element may determine whether to configure CG for the terminal according to the CG capability of the terminal. A possible implementation is that if the CG capability of the terminal indicates that the terminal supports CG, the second network element determines to configure CG for the terminal.

[0400] In summary, the second network element may determine whether to establish a second data channel with the core network according to the first request message and the information of the uplink data; or determine whether to request the context of the terminal from the second network device according to the first request message and the information of the uplink data. The second network element may also determine whether to establish a second data channel with the core network according to the first request message, the information of the uplink data, and the information of the amount of remaining uplink data; or determine whether to request the context of the terminal from the second network device according to the first request message, the information of the uplink data, and the amount of remaining uplink data. The second network element may also determine whether to establish a second data channel with the core network according to the first request message, the information of the uplink data, and the CG capability of the terminal; or determine whether to request the context of the terminal from the second network device according to the first request message, the information of the uplink data, and the CG capability of the terminal. The second network element may further determine whether to establish a second data channel with the core network according to the first request message, the information of the uplink data, the amount of remaining uplink data, and the CG capability of the terminal; or determine whether to request the context of the terminal from the second network device according to the first request message, the information of the uplink data, the amount of remaining uplink data, and the CG capability of the terminal. Specifically, reference may be made to the corresponding descriptions in step 402 above for the first network device to determine whether to establish a second data channel with the core network device and the first network device to determine whether to request the context of the terminal from the second network device, which will not be elaborated here.

[0401] Based on Figure 7 In the method shown above, after receiving the first request message from the terminal, the first network element may send the information of the first request message and the uplink data to the second network element according to the first request message. After receiving the information of the first request message and the uplink data, the second network element may determine whether to establish a second data channel with the core network device according to the first request message and the information of the uplink data; or determine whether to request the context of the terminal from the second network device according to the first request message and the information of the uplink data. In this way, the flexibility of the second network element and the second network device in processing uplink data is improved.

[0402] Further optionally, when the second network element determines to establish a second data channel with the core network device, or when the second network element determines not to establish a second data channel with the core network device, or when the second network element determines to request the context of the terminal from the second network device, the second network element sends a communication message to the second network device. Specifically, as Figure 8 shown, Figure 7 the method shown also includes step 704.

[0403] Step 704: The second network element sends a notification message to the second network device.

[0404] When the second network element determines to establish a second data channel with the core network device, when the second network element determines not to establish a second data channel with the core network device, and when the second network element determines to request the context of the terminal from the second network device, the functions of the notification message are different. Specifically, the introduction of the notification message is as follows:

[0405] Case 12: The second network element determines to establish a second data channel with the core network device, and this notification message is used to instruct the second network device to release the first data channel between the second network device and the core network device.

[0406] Wherein, the first data channel is used for the second network device to forward the uplink data sent by the terminal to the core network device, or the first data channel is used for the second network device to receive the data to be sent to the terminal from the core network device. At this time, the second network device is the anchor node of the terminal.

[0407] In this case, the second network element may also receive a response message from the second network device, and this response message may be used to indicate that the second network device has successfully released the first data channel. The response message may include the context of the terminal, and the context of the terminal includes the source PDCP configuration and the source RLC configuration, so that the second network element can obtain the uplink data and send the uplink data to the core network device. It can be understood that after the second network device sends the context of the terminal to the second network element, it releases the context of the terminal stored locally.

[0408] Optionally, the second network element also sends indication information to the first network element for indicating a communication tunnel between the second network element and the first network element. This communication tunnel is used for transmitting uplink data. For example, this communication tunnel is a GTP tunnel. This communication tunnel can be a newly established communication tunnel or a previously established communication tunnel. The indication information may include the IP address of the second network element, the TEID of this communication tunnel, and the source LCID. The indication information may further include a source DRB identifier. The indication information can indicate one communication tunnel or multiple communication tunnels. When the indication information indicates multiple communication tunnels, the second network element can use all the communication tunnels to receive the uplink data sent by the first network element, or can use some of the communication tunnels to receive the uplink data sent by the first network element. The second network element can also determine the number of this communication tunnel according to the number of logical channels corresponding to the uplink data or the number of logical channels in the context of the terminal.

[0409] Optionally, when the response message may include the context of the terminal, the second network element may further send a source RLC configuration to the first network element, so that the first network element can obtain the uplink data processed according to the source PDCP configuration based on the configuration of the source RLC. This RLC configuration may be the source RCL configuration corresponding to the source LCID. Subsequently, the second network element can receive, through this communication tunnel, the uplink data processed according to the source PDCP configuration from the first network element. After receiving the uplink data processed according to the source PDCP configuration, the second network element can obtain the uplink data according to the source PDCP configuration and send the uplink data to the core network device through the second data channel. The second network element can also send an RRC release message to the terminal through the first network element to release the RRC connection between the second network element and the terminal.

[0410] Scenario 13: The second network element determines not to establish a second data channel with the core network device, and this notification message is used to indicate that the second network device retains the first data channel between the second network device and the core network device.

[0411] Wherein, the first data channel is used for the second network device to forward the uplink data sent by the terminal to the core network device, or the first data channel is used for the second network device to receive the data to be sent to the terminal from the core network device. At this time, the second network device is the anchor node of the terminal.

[0412] In this case, the second network element may also receive a response message from the second network device, which is used to establish a communication tunnel between the second network element and the second network device. This communication tunnel is used to transmit uplink data. For example, this communication tunnel is an Xn GTP-U tunnel. The number of such communication tunnels is one or more. There is a corresponding relationship between this communication tunnel and the source LCID. When the number of communication tunnels is one, this communication tunnel corresponds to one or more source LCIDs. When the number of communication tunnels is multiple, each of the multiple communication tunnels corresponds to one or more source LCIDs, and the source LCIDs corresponding to different communication tunnels may be the same or different. This corresponding relationship may be preset in the second network device. It should be noted that because there is a corresponding relationship between this communication tunnel and the source LCID, the second network device can establish this communication tunnel only when it knows the source LCID. For example, when the information of the uplink data includes the source LCID corresponding to the uplink data, this response message is also used to establish this communication tunnel.

[0413] In a possible implementation, this response message includes an identifier of the communication tunnel, and there is a corresponding relationship between the identifier of the communication tunnel and the source LCID.

[0414] In another possible implementation, this response message includes an address of the communication tunnel, and there is a corresponding relationship between the address of the communication tunnel and the source LCID.

[0415] Optionally, this response message further includes the context of the terminal. The context of the terminal includes the source PDCP configuration and the source RLC configuration.

[0416] In this case, after the second network element receives the response message from the second network device, the second network element sends uplink data to the second network device. Optionally, the second network element obtains the uplink data from the first network element. Exemplarily, the second network element sends indication information for indicating the communication tunnel between the second network element and the first network element to the first network element, and this communication tunnel is used for transmitting the uplink data. The introduction of this indication information and the communication tunnel can refer to the description in the above case 12. When the response message includes the context of the terminal, the second network element may also send the source RLC configuration to the first network element, so that the first network element can obtain the uplink data processed according to the source PDCP configuration based on the configuration of the source RLC. This RLC configuration may be the source RCL configuration corresponding to the source LCID. Subsequently, the second network element may receive the uplink data processed according to the source PDCP configuration from the first network element through the communication tunnel between the second network element and the first network element. After receiving the uplink data processed according to the source PDCP configuration, the second network element may obtain the uplink data according to the source PDCP configuration and send the uplink data to the second network device through the communication tunnel between the second network element and the second network device. After receiving the uplink data, the second network device sends the uplink data to the core network device through the first data channel. Subsequently, the second network device may send an RRC release message to the terminal through the second network element and the first network element, and the RRC release message is used to notify that the RRC state of the terminal is the RRC inactive state or the RRC idle state.

[0417] It should be noted that the uplink data sent by the first network element to the second network element may be the uplink data received from the terminal and not processed by the first network element. After receiving the uplink data, the second network element may send the uplink data to the second network device. After receiving the uplink data, the second network device may process the uplink data according to the context of the terminal and send the processed uplink data to the core network device through the first data channel.

[0418] It can be understood that the uplink data may also be sent to the second network device in the notification message.

[0419] Case 14: The second network element determines to request the context of the terminal from the second network device, and this notification message is used to instruct the second network device to send the context of the terminal to the second network element. This notification message includes a first identifier, so that the second network device can determine the context of the terminal according to the first identifier.

[0420] In this case, the second network element may also receive the response message from the second network device. This response message includes the context of the terminal. Subsequently, the second network element and the first network element may obtain the uplink data according to the context of the terminal.

[0421] Optionally, the context of the terminal includes the source PDCP configuration, or the context of the terminal includes the source PDCP configuration and the source RLC configuration.

[0422] In a possible implementation, the context of the terminal includes the source PDCP configuration, and the second network element obtains uplink data from the first network element. Exemplarily, the second network element sends indication information for indicating the communication tunnel between the second network element and the first network element to the first network element, and this communication tunnel is used for transmitting uplink data. The introduction of this indication information and the communication tunnel can refer to that described in Case 12 above. The second network element can receive the uplink data processed according to the source PDCP configuration from the first network element through this communication tunnel. After receiving the uplink data processed according to the source PDCP configuration, the second network element can obtain the uplink data according to the source PDCP configuration.

[0423] In another possible implementation, the context of the terminal includes the source PDCP configuration and the source RLC configuration. The second network element sends a second message to the first network element, and the second message includes the source RLC configuration, so that the first network element can obtain the uplink data processed according to the source PDCP configuration according to the source RLC configuration. The second message may further include indication information for indicating the communication tunnel between the second network element and the first network element, and this communication tunnel is used for transmitting uplink data. The introduction of this indication information and the communication tunnel can refer to that described in Case 12 above. The second network element can receive the uplink data processed according to the source PDCP configuration from the first network element through this communication tunnel. After receiving the uplink data processed according to the source PDCP configuration, the second network element can obtain the uplink data according to the source PDCP configuration.

[0424] Optionally, if the second network element does not receive the response message within a preset time or the response message received by the second network element does not include the context of the terminal, the second network element sends a third message to the first network element. The third message is used to instruct the first network element to delete the uplink data stored locally; or, the third message is used to instruct the first network element to send indication information for resending the uplink data to the terminal; or, the third message instructs the first network element to send the uplink data received from the terminal and not processed by the first network element to the second network element. After receiving the uplink data, the second network element sends the uplink data to the second network device. After receiving the uplink data, the second network device can process the uplink data according to the context of the terminal and send the processed uplink data to the core network device through the first data channel.

[0425] It can be understood that if the second network element determines not to request the context of the terminal from the second network device, the second network element can also send a third message to the first network element.

[0426] It can be understood that if the notification message instructs the second network device to send the context of the terminal to the second network element, the second network device can release the first data channel.

[0427] Optionally, the response message in the above three cases further includes at least one of the capabilities of the CG of the terminal, the service model information, or the configuration information of the CG of the terminal under the second network device. The introduction of the capabilities of the CG of the terminal, the service model information, or the configuration information of the CG of the terminal under the second network device can refer to that described in step 303 above and will not be elaborated here. Subsequently, the second network element can determine whether to configure the CG for the terminal according to the capabilities of the CG of the terminal. When the second network element determines to configure the CG for the terminal, it can configure the CG for the terminal with reference to the configuration information of the CG of the terminal under the second network device; the second network element can determine the possible data arrival period of the terminal, the possible transport block size of the uplink data of the terminal, or the possible arrival timing of the terminal according to the service model information.

[0428] Based on Figure 8 the method shown, when the second network element determines to establish a second data channel with the core network device, or when the second network element determines not to establish a second data channel with the core network device, or when the second network element determines to request the context of the terminal from the second network device and send a communication message to the second network device, it can thus notify the second network device to release the first data channel, or notify the second network device to retain the first data channel, or notify the second network device to send the context of the terminal to the second network element.

[0429] The above mainly introduces the solution provided by the embodiments of the present application from the perspective of the interaction between each network element. It can be understood that in order to implement the above functions, the above first network device, second network device, first network element, or second network element, etc. include the corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should easily realize that, combined with the units and algorithm operations of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0430] The embodiments of the present application can divide the first network device, the second network device, the first network element, or the second network element into functional modules according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, only a logical function division, and there can be other division methods in actual implementation.

[0431] For example, in the case of dividing each functional module in an integrated manner, Figure 9 FIG. shows a schematic structural diagram of a communication device 90. The communication device 90 may be a first network device, or a chip or system-on-chip in the first network device, or other combined devices, components, etc. that can implement the functions of the above-mentioned first network device. The communication device 90 may be used to execute the functions of the first network device involved in the above embodiments.

[0432] As a possible implementation manner, Figure 9 The shown communication device 90 includes: a receiving unit 901 and a transmitting unit 902.

[0433] The receiving unit 901 is configured to receive a first request message and uplink data from a terminal. The first request message is used to request to resume a suspended radio resource control (RRC) connection.

[0434] The transmitting unit 902 is configured to send a second request message to a second network device according to the first request message and the uplink data. The second network device is the previous serving network device of the terminal. The second request message includes information about the uplink data.

[0435] Wherein, the second request message is used to request the second network device to release a first data channel with a core network device; or, the second request message is used to request the second network device to send the context of the terminal to the communication device 90.

[0436] Optionally, the second request message is used to request the second network device to release the first data channel with the core network device, and the information about the uplink data is used for the second network device to determine whether to release the first data channel; or, the second request message is used to request the second network device to send the context of the terminal to the communication device 90, and the information about the uplink data is used for the second network device to determine whether to send the context of the terminal to the communication device 90.

[0437] Optionally, the information about the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the communication device 90, and the second indication information is used to indicate that the uplink data is not included in the first request message.

[0438] Optionally, the receiving unit 901 is further configured to receive a buffer status report from the terminal. The buffer status report is used to indicate the data volume of the remaining uplink data; the second request message further includes information about the data volume of the remaining uplink data.

[0439] Optionally, the second request message further includes third indication information for indicating that the communication device 90 has the ability to configure authorization for the terminal.

[0440] Optionally, the second request message is used to request the second network device to release the first data channel between the second network device and the core network device. The receiving unit 901 is further configured to receive a first response message from the second network device. The data volume of the uplink data is greater than or equal to a first threshold, and the first response message is used to indicate that the second network device releases the first data channel; or, the data volume of the uplink data is less than or equal to the first threshold, and the first response message is used to indicate that the second network device retains the first data channel.

[0441] Optionally, the second request message is used to request the second network device to release the first data channel between the second network device and the core network device. The receiving unit 901 is further configured to receive a first response message from the second network device. The data volume of the remaining uplink data is greater than or equal to a second threshold, and the first response message is used to indicate that the second network device releases the first data channel; or, the data volume of the remaining uplink data is less than or equal to the second threshold, and the first response message is used to indicate that the second network device retains the first data channel.

[0442] Optionally, the second request message is used to request the second network device to release the first data channel between the second network device and the core network device. The receiving unit 901 is further configured to receive a first response message from the second network device. The first response message is used to indicate that the second network device releases the first data channel; or, the first response message is used to indicate that the second network device retains the first data channel.

[0443] Optionally, the first request message includes the ability of the terminal to configure authorization; or, the first response message includes the ability of the terminal to configure authorization.

[0444] Optionally, the first response message further includes service model information for indicating at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, and the arrival timing of the terminal evaluated by the second network device.

[0445] Optionally, the first response message is further used to establish a communication tunnel between the communication device 90 and the second network device. The communication tunnel is used to transmit the uplink data, and the communication tunnel has a corresponding relationship with the source logical channel identifier.

[0446] Optionally, as Figure 10As shown, the communication device 90 further includes a processing unit 903; if the data volume of the remaining uplink data is greater than or equal to a second threshold, the processing unit 903 is configured to establish an RRC connection with the terminal.

[0447] Optionally, the second request message is used to request the second network device to send the context of the terminal to the communication device 90, and the receiving unit 901 is further configured to receive a second response message from the second network device; the second response message includes the configuration of the source packet data convergence protocol and the configuration of the source radio link control.

[0448] Optionally, the first request message includes the configuration authorization capability of the terminal; or, the second response message further includes the configuration authorization capability of the terminal.

[0449] Optionally, the second response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transmission block size of the uplink data evaluated by the second network device, or the arrival timing of the terminal evaluated by the second network device.

[0450] Optionally, the second response message is further used to indicate the establishment of a communication tunnel between the communication device 90 and the second network device, and the communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier.

[0451] Optionally, the first request message and the uplink data are multiplexed in one message.

[0452] Wherein, all relevant contents of the operations involved in the above method embodiments can be cited in the function descriptions of the corresponding functional modules, and will not be elaborated here.

[0453] In this embodiment, the communication device 90 is presented in the form of dividing each functional module in an integrated manner. Here, the "module" may refer to a specific ASIC, circuit, processor and memory that execute one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can think that the communication device 90 can adopt Figure 2 the form shown.

[0454] For example, Figure 2 the processor 201 in can make the communication device 90 execute the communication method in the above method embodiment by calling the computer execution instructions stored in the memory 203.

[0455] Exemplarily, Figure 10 the functions / implementation processes of the receiving unit 901, the sending unit 902 and the processing unit 903 in can be passed throughFigure 2 The processor 201 in Figure 10 invokes the computer-executable instructions stored in the memory 203 to implement. Or, Figure 2 the function / implementation process of the processing unit 903 in Figure 10 can be implemented by the processor 201 in Figure 2 invoking the computer-executable instructions stored in the memory 203,

[0456] Since the communication device 90 provided in this embodiment can execute the above communication method, the technical effects it can obtain can refer to the above method embodiment and will not be elaborated here.

[0457] For example, in the case of dividing each functional module in an integrated manner, Figure 11 shows a schematic structural diagram of a communication device 110. The communication device 110 can be a second network device or a chip or system-on-chip in the second network device, or other combined devices, components, etc. that can implement the functions of the above second network device. The communication device 110 can be used to execute the functions of the second network device involved in the above embodiment.

[0458] As a possible implementation manner, Figure 11 the communication device 110 shown includes: a receiving unit 1101 and a processing unit 1102.

[0459] The receiving unit 1101 is configured to receive a second request message from a first network device. The second request message includes information of uplink data, and the second request message is used to request the communication device 110 to release a first data channel between the communication device 110 and a core network device. The communication device 110 is a former serving network device of a terminal; the processing unit 1102 is configured to release the first data channel according to the second request message; or,

[0460] The receiving unit 1101 is configured to receive a second request message from a first network device. The second request message includes information of uplink data, and the second request message is used to request the communication device 110 to send the context of the terminal to the first network device. The communication device 110 is a former serving network device of the terminal; the processing unit 1102 is configured to send the context of the terminal to the first network device according to the second request message.

[0461] Optionally, the information of the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data reaches the first network device, and the second indication information is used to indicate that the uplink data is not included in the first request message, and the first request message is used for the terminal to request the first network device to resume a suspended radio resource control (RRC) connection.

[0462] Optionally, the second request message further includes information about the data volume of the remaining uplink data.

[0463] Optionally, the second request message further includes third indication information, and the third indication information is used to indicate that the first network device has the ability to configure authorization for the terminal.

[0464] Optionally, as Figure 12 shown, the communication device 110 further includes a sending unit 1103; the second request message is used to request the communication device 110 to release a first data channel between the communication device 110 and a core network device, and the sending unit 1103 is configured to send a first response message to the first network device; the data volume of the uplink data is greater than or equal to a first threshold, and the first response message is used to indicate that the communication device 110 releases the first data channel; or, the data volume of the uplink data is less than or equal to the first threshold, and the first response message is used to indicate that the communication device 110 retains the first data channel.

[0465] Optionally, the second request message is used to request the communication device 110 to release a first data channel between the communication device 110 and a core network device, and the sending unit 1103 is configured to send a first response message to the first network device; the data volume of the remaining uplink data is greater than or equal to a second threshold, and the first response message is used to indicate that the communication device 110 releases the first data channel; or, the data volume of the remaining uplink data is less than or equal to the second threshold, and the first response message is used to indicate that the communication device 110 retains the first data channel.

[0466] Optionally, the second request message is used to request the communication device 110 to release a first data channel between the communication device 110 and a core network device, and the sending unit 1103 is configured to send a first response message to the first network device; the first response message is used to indicate that the communication device 110 releases the first data channel; or, the first response message is used to indicate that the communication device 110 retains the first data channel.

[0467] Optionally, the first request message includes the ability of the terminal to configure authorization; or, the first response message includes the ability of the terminal to configure authorization.

[0468] Optionally, the first response message further includes service model information, which is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the communication device 110, the transport block size of the uplink data evaluated by the communication device 110, and the arrival timing of the terminal evaluated by the communication device 110.

[0469] Optionally, the first response message is further used to establish a communication tunnel between the first network device and the communication device 110. The communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier.

[0470] Optionally, the second request message is used to request the communication device 110 to send the context of the terminal to the first network device. The sending unit 1103 is used to send a second response message to the first network device; the second response message includes the configuration of the source packet data convergence protocol and the configuration of the source radio link control.

[0471] Optionally, the first request message includes the configuration authorization capability of the terminal; alternatively, the second response message further includes the configuration authorization capability of the terminal.

[0472] Optionally, the second response message further includes service model information, which is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the communication device 110, the transport block size of the uplink data evaluated by the communication device 110, and the arrival timing of the terminal evaluated by the communication device 110.

[0473] Optionally, the second response message is further used to establish a communication tunnel between the first network device and the communication device 110. The communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier.

[0474] Optionally, the first request message and the uplink data are multiplexed in one message.

[0475] Wherein, all relevant contents of each operation involved in the above method embodiments can be cited in the function descriptions of the corresponding functional modules, and will not be elaborated here.

[0476] In this embodiment, the communication device 110 is presented in the form of dividing each functional module in an integrated manner. Here, a "module" may refer to a specific ASIC, circuit, processor and memory that execute one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can think that the communication device 110 can adopt Figure 2 the form shown.

[0477] For example,Figure 2 The processor 201 in Figure 2 can cause the communication device 110 to execute the communication method in the above method embodiments by calling computer-executable instructions stored in the memory 203.

[0478] Exemplarily, Figure 12 the functions / implementation processes of the receiving unit 1101, the processing unit 1102, and the sending unit 1103 in Figure 12 can be Figure 2 implemented by the processor 201 in Figure 2 calling computer-executable instructions stored in the memory 203. Or, Figure 12 the function / implementation process of the processing unit 1102 in Figure 12 can be Figure 2 implemented by the processor 201 in Figure 2 calling computer-executable instructions stored in the memory 203, Figure 12 and the functions / implementation processes of the receiving unit 1101 and the sending unit 1103 in Figure 12 can be Figure 2 implemented by the communication interface 204 in Figure 2 .

[0479] Since the communication device 110 provided in this embodiment can execute the above communication method, the technical effects that can be obtained thereby can refer to the above method embodiments and will not be elaborated herein.

[0480] For example, in the case of dividing each functional module in an integrated manner, Figure 13 FIG. shows a schematic structural diagram of a communication device 130. The communication device 130 can be a first network element or a chip or system-on-chip in the first network element, or other combined devices, components, etc. that can implement the functions of the above first network element, and the communication device 130 can be used to execute the functions of the first network element involved in the above embodiments.

[0481] As a possible implementation manner, Figure 13 the communication device 130 shown in Figure 13 includes: a receiving unit 1301 and a sending unit 1302.

[0482] The receiving unit 1301 is configured to receive a first request message and uplink data from a terminal, where the first request message is used to request to resume a suspended radio resource control (RRC) connection.

[0483] The sending unit 1302 is configured to send information of the first request message and the uplink data to a second network element according to the first request message and the uplink data.

[0484] Optionally, the information of the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the communication device 130, and the second indication information is used to indicate that the uplink data is not included in the first request message.

[0485] Optionally, the receiving unit 1301 is further configured to receive a buffer status report from the terminal, where the buffer status report is used to indicate the amount of remaining uplink data; the sending unit 1302 is further configured to send information about the amount of the remaining uplink data to the second network element.

[0486] Optionally, if the amount of the remaining uplink data is greater than or equal to a threshold, the receiving unit 1301 is further configured to receive a first message from the second network element, where the first message is used to indicate that the communication device 130 establishes an RRC connection with the terminal.

[0487] Optionally, the receiving unit 1301 is further configured to receive a second message from the second network element, where the second message includes a configuration of a source radio link control.

[0488] Optionally, the second message further includes indication information for indicating a communication tunnel between the second network element and the communication device 130, where the communication tunnel is used to transmit the uplink data.

[0489] Optionally, as Figure 14 shown, the communication device 130 further includes a processing unit 1303; the receiving unit 1301 is further configured to receive a third message from the second network element, where the third message is used to indicate that the communication device 130 deletes the uplink data; the processing unit 1303 is configured to delete the uplink data according to the third message.

[0490] Optionally, the first request message and the uplink data are multiplexed in one message.

[0491] Wherein, all relevant contents of each operation involved in the foregoing method embodiments can be cited in the function descriptions of the corresponding functional modules, and will not be elaborated herein.

[0492] In this embodiment, the communication device 130 is presented in a form of dividing each functional module in an integrated manner. Here, the "module" may refer to a specific ASIC, a circuit, a processor and a memory that execute one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the foregoing functions. In a simple embodiment, those skilled in the art can think that the communication device 130 can adopt Figure 2 the form shown.

[0493] For example, Figure 2 the processor 201 in [reference] can call computer execution instructions stored in the memory 203, so that the communication device 130 executes the communication method in the foregoing method embodiments.

[0494] Exemplarily, Figure 14The functions / implementation processes of the receiving unit 1301, the sending unit 1302 and the processing unit 1303 can be Figure 2 The processor 201 in the embodiment calls the computer execution instruction stored in the memory 203 to implement. Or, Figure 14 The function / implementation process of the processing unit 1303 in Figure 2 The processor 201 in the embodiment calls the computer execution instruction stored in the memory 203 to implement, Figure 14 The functions / implementation processes of the receiving unit 1301 and the sending unit 1302 can be Figure 2 This is achieved by the communication interface 204 in .

[0495] Since the communication device 130 provided in this embodiment can execute the above-mentioned communication method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.

[0496] For example, when the functional modules are divided in an integrated manner, Figure 15 The structure diagram of a communication device 150 is shown. The communication device 150 may be a second network element or a chip or system on chip in the second network element, or other combined devices, components, etc. that can implement the functions of the second network element. The communication device 150 may be used to perform the functions of the second network element involved in the above embodiments.

[0497] As a possible implementation, Figure 15 The communication device 150 shown includes: a receiving unit 1501 and a processing unit 1502 .

[0498] The receiving unit 1501 is configured to receive a first request message and uplink data information from a first network element.

[0499] The processing unit 1502 is configured to obtain the context of the terminal according to the first request message and the uplink data information.

[0500] Optionally, the information of the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or a source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data has arrived at the first network element, and the second indication information is used to indicate that the uplink data is not included in the first request message.

[0501] Optionally, the receiving unit 1501 is further used to receive information about the amount of remaining uplink data from the first network element, where the information about the amount of remaining uplink data is used to indicate the amount of the remaining uplink data.

[0502] Optional, such as Figure 16As shown in the figure, the communication device 150 further includes: a sending unit 1503; the sending unit 1503 is configured to, if the data volume of the remaining uplink data is greater than or equal to a threshold, send a first message to the first network element, where the first message is used to instruct the first network element to establish a Radio Resource Control (RRC) connection with the terminal.

[0503] Optionally, the context of the terminal includes the configuration of the source Packet Data Convergence Protocol and the configuration of the source Radio Link Control.

[0504] Optionally, the sending unit 1503 is further configured to send a second message to the first network element, where the second message includes the configuration of the source Radio Link Control in the context of the terminal.

[0505] Optionally, the second message further includes indication information for indicating a communication tunnel between the communication device 150 and the first network element, and the communication tunnel is used to transmit the uplink data.

[0506] Optionally, when the communication device 150 fails to obtain the context of the terminal, the sending unit 1503 is further configured to send a third message to the first network element, where the third message is used to instruct the first network element to delete the uplink data.

[0507] Optionally, the first request message and the uplink data are multiplexed in one message.

[0508] Wherein, all relevant content of each operation involved in the above method embodiment can be cited in the function description of the corresponding functional module, and will not be elaborated here.

[0509] In this embodiment, the communication device 150 is presented in a form that divides each functional module in an integrated manner. Here, a "module" may refer to a specific ASIC, circuit, processor and memory that execute one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can think that the communication device 150 can adopt Figure 2 the form shown.

[0510] For example, Figure 2 the processor 201 in can call computer execution instructions stored in the memory 203 to cause the communication device 150 to execute the communication method in the above method embodiment.

[0511] Exemplarily, Figure 16 the functions / implementation processes of the receiving unit 1501, the processing unit 1502, and the sending unit 1503 in can be implemented by Figure 2 the processor 201 in calling computer execution instructions stored in the memory 203. Alternatively, Figure 16 the function / implementation process of the processing unit 1502 in can be implemented byFigure 2 The processor 201 in Figure 16 calls the computer-executable instructions stored in the memory 203 to implement, Figure 2 The functions / implementation processes of the receiving unit 1501 and the sending unit 1503 in

[0512] Since the communication device 150 provided in this embodiment can execute the above-mentioned communication method, the technical effects that can be obtained thereby can refer to the above method embodiment and will not be elaborated here.

[0513] Figure 17 shows a schematic diagram of the composition of a communication system, as Figure 17 shown. The communication system 170 may include: a network device 1701, a network device 1702, and a terminal 1703. It should be noted that, Figure 17 This is only an exemplary drawing, and the embodiments of the present application do not limit Figure 17 the network elements included in the communication system 170 shown and the number of network elements.

[0514] Among them, the network device 1701 has the functions of the above-mentioned Figure 9 or Figure 10 shown communication device 90, and can be used to receive a first request message and uplink data from the terminal 1703, and send a second request message to the network device 1702 according to the first request message and the uplink data.

[0515] The network device 1702 has the functions of the above-mentioned Figure 11 or Figure 12 shown communication device 110, and can receive the second request message from the network device 1701 and release the first data channel according to the second request message; or, it can receive the second request message from the network device 1701 and send the context of the terminal 1703 to the network device 1701 according to the second request message.

[0516] The terminal 1703 can be used to send a first request message and uplink data to the network device 1701.

[0517] It should be noted that all relevant contents of each step involved in the above method embodiment can be cited in the function descriptions of the corresponding network elements of the communication system 170 and will not be elaborated here.

[0518] Figure 18 shows a schematic diagram of the composition of a communication system, as Figure 18 shown. The communication system 180 may include: a network element 1801, a network element 1802, and a terminal 1803. It should be noted that, Figure 18 This is only an exemplary drawing, and the embodiments of the present application do not limit Figure 18The network elements included in the communication system 180 shown and the number of network elements.

[0519] Among them, the network element 1801 has the functions of the above-mentioned Figure 13 or Figure 14 functions of the communication device 130 shown, can receive a first request message and uplink data from the terminal 1803, and according to the first request message and the uplink data, send information about the first request message and the uplink data to the network element 1802.

[0520] The network element 1802 has the functions of the above-mentioned Figure 15 or Figure 16 functions of the communication device 150 shown, can receive information about the first request message and uplink data from the network element 1801, and obtain the context of the terminal 1803 according to the information about the first request message and uplink data.

[0521] The terminal 1803 can be used to send a first request message and uplink data to the network element 1801.

[0522] It should be noted that all relevant contents of the steps involved in the above method embodiments can be cited in the function descriptions of the corresponding network elements of the communication system 180, and will not be repeated here.

[0523] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server, data center, etc. that contains one or more integrated media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0524] Although the present application has been described in connection with various embodiments, it will be understood by those skilled in the art that other variations of the disclosed embodiments can be understood and effected while practicing the claimed application, by studying the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or acts, and the indefinite article "a" or "an" does not exclude a plurality. A single processor or other unit may implement several functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not indicate that these measures cannot be combined to advantage.

[0525] Although the present application has been described in connection with specific features and their embodiments, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the application. It is obvious that those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these changes and modifications.

Claims

1. A communication method, characterized in that, The method includes: A first network device receives a first request message and uplink data from a terminal, where the first request message is used to request resuming a suspended Radio Resource Control (RRC) connection. The first network device sends a second request message to a second network device according to the first request message and the uplink data, where the second network device is the previous serving network device of the terminal, and the second request message includes information about the uplink data. The second request message is used to request the second network device to release a first data channel between the second network device and a core network device, and the information about the uplink data is used by the second network device to determine whether to release the first data channel. The information about the uplink data includes at least one of the following: a first indication information, a second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data. The first indication information is used to indicate that the uplink data arrives at the first network device, and the second indication information is used to indicate that the uplink data is not included in the first request message.

2. The method according to claim 1, wherein: The second request message is used to request the second network device to release a first data channel between the second network device and a core network device, or The second request message is used to request the second network device to send the context of the terminal to the first network device, and the information about the uplink data is used by the second network device to determine whether to send the context of the terminal to the first network device.

3. The method according to any one of claims 1-2, characterized in that, The method further includes: The first network device receives a buffer status report from the terminal, where the buffer status report is used to indicate the data volume of the remaining uplink data. The second request message further includes information about the data volume of the remaining uplink data.

4. The method according to any one of claims 1-2, characterized in that, The second request message further includes a third indication information, where the third indication information is used to indicate that the first network device has the ability to configure authorization for the terminal.

5. The method according to claim 1, wherein The second request message is used to request the second network device to release a first data channel between the second network device and a core network device, and the method further includes: The first network device receives a first response message from the second network device. If the data volume of the uplink data is greater than or equal to a first threshold, the first response message is used to indicate that the second network device releases the first data channel; or If the data volume of the uplink data is less than or equal to a first threshold, the first response message is used to indicate that the second network device retains the first data channel.

6. The method according to claim 3, wherein The second request message is used to request the second network device to release a first data channel between the second network device and a core network device, and the method further includes: The first network device receives a first response message from the second network device. If the data volume of the remaining uplink data is greater than or equal to a second threshold, the first response message is used to indicate that the second network device releases the first data channel; or If the data volume of the remaining uplink data is less than or equal to a second threshold, the first response message is used to indicate that the second network device retains the first data channel.

7. The method according to claim 4, characterized in that, The second request message is used to request the second network device to release a first data channel between the second network device and a core network device. The method further includes: The first network device receives a first response message from the second network device. The first response message is used to indicate that the second network device releases the first data channel; or, the first response message is used to indicate that the second network device retains the first data channel.

8. The method according to any one of claims 5 to 7, characterized in that The first request message includes the configuration authorization capability of the terminal; or, the first response message includes the configuration authorization capability of the terminal.

9. The method according to claim 8, characterized in that, The first response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, the arrival timing of the terminal evaluated by the second network device.

10. The method according to any one of claims 5 - 7, characterized in that, The first response message is further used to establish a communication tunnel between the first network device and the second network device. The communication tunnel is used to transmit the uplink data, and the communication tunnel has a corresponding relationship with the source logical channel identifier.

11. The method according to claim 3, wherein If the data volume of the remaining uplink data is greater than or equal to a second threshold, the method further includes: The first network device establishes an RRC connection with the terminal.

12. The method according to any one of claims 1-2, characterized in that, The second request message is used to request the second network device to send the context of the terminal to the first network device. The method further includes: The first network device receives a second response message from the second network device; the second response message includes the configuration of the source packet data convergence protocol and the configuration of the source radio link control.

13. The method according to claim 12, wherein The first request message includes the configuration authorization capability of the terminal; or, the second response message further includes the configuration authorization capability of the terminal.

14. The method according to claim 12, wherein The second response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, or the arrival timing of the terminal evaluated by the second network device.

15. The method according to claim 12, characterized in that, The second response message is further used to indicate the establishment of a communication tunnel between the first network device and the second network device. The communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier.

16. The method according to any one of claims 1-2, characterized in that, The first request message and the uplink data are multiplexed in one message.

17. A communication method, characterized in that, The method includes: A second network device receives a second request message from a first network device. The second request message includes information about uplink data. The second request message is used to request the second network device to release a first data channel between the second network device and a core network device. The second network device is a former serving network device of the terminal. The second network device releases the first data channel according to the information of the uplink data; the information of the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the first network device, and the second indication information is used to indicate that the uplink data is not included in the first request message, and the first request message is used for the terminal to request the first network device to resume a suspended radio resource control (RRC) connection.

18. The method according to claim 17, wherein The second request message further includes information on the data volume of the remaining uplink data.

19. The method according to any one of claims 17 - 18, characterized in that, The second request message further includes third indication information, and the third indication information is used to indicate that the first network device has the ability to configure authorization for the terminal.

20. The method according to claim 17 or 18, characterized in that The second request message is used to request the second network device to release the first data channel between the second network device and the core network device. The method further includes: The second network device sends a first response message to the first network device. If the data volume of the uplink data is greater than or equal to a first threshold, the first response message is used to indicate that the second network device releases the first data channel; or, If the data volume of the uplink data is less than or equal to the first threshold, the first response message is used to indicate that the second network device retains the first data channel.

21. The method according to claim 18, wherein The second request message is used to request the second network device to release the first data channel between the second network device and the core network device. The method further includes: The second network device sends a first response message to the first network device. If the data volume of the remaining uplink data is greater than or equal to a second threshold, the first response message is used to indicate that the second network device releases the first data channel; or, If the data volume of the remaining uplink data is less than or equal to the second threshold, the first response message is used to indicate that the second network device retains the first data channel.

22. The method according to claim 19, wherein The second request message is used to request the second network device to release the first data channel between the second network device and the core network device. The method further includes: The second network device sends a first response message to the first network device; the first response message is used to indicate that the second network device releases the first data channel; or, the first response message is used to indicate that the second network device retains the first data channel.

23. The method according to any one of claims 21-22, characterized in that, The first request message includes the ability of the terminal to configure authorization; or, the first response message includes the ability of the terminal to configure authorization.

24. The method according to claim 23, wherein The first response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, the arrival timing of the terminal evaluated by the second network device.

25. The method according to any one of claims 21-22, characterized in that, The first response message is further used to establish a communication tunnel between the first network device and the second network device, and the communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier.

26. The method according to any one of claims 17-18, characterized in that, The second request message is used to request the second network device to send the context of the terminal to the first network device. The method further includes: A second response message from the second network device to the first network device; the second response message includes the configuration of the source packet data convergence protocol and the configuration of the source radio link control.

27. The method according to claim 26, wherein The first request message includes the configuration authorization capability of the terminal; alternatively, the second response message further includes the configuration authorization capability of the terminal.

28. The method according to claim 27, wherein The second response message further includes service model information, which is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, and the arrival timing of the terminal evaluated by the second network device.

29. The method according to any one of claims 27-28, characterized in that, The second response message is further used to establish a communication tunnel between the first network device and the second network device, and the communication tunnel is used to transmit the uplink data. The identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier.

30. The method according to any one of claims 17-18, characterized in that, The first request message and the uplink data are multiplexed in one message.

31. A communication device, characterized in that, The communication device includes: a receiving unit and a transmitting unit; The receiving unit is configured to receive a first request message and uplink data from a terminal, where the first request message is used to request to resume a suspended radio resource control (RRC) connection. The transmitting unit is configured to send a second request message to a second network device according to the first request message and the uplink data. The second network device is the previous serving network device of the terminal, and the second request message includes information about the uplink data. The second request message is used to request the second network device to release a first data channel between the second network device and a core network device; the information about the uplink data is used for the second network device to determine whether to release the first data channel; the information about the uplink data includes at least one of the following: a first indication information, a second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the communication device, and the second indication information is used to indicate that the uplink data is not included in the first request message.

32. The communication device according to claim 31, wherein The second request message is used to request the second network device to release a first data channel between the second network device and a core network device, or The second request message is used to request the second network device to send the context of the terminal to the communication device, and the information about the uplink data is used for the second network device to determine whether to send the context of the terminal to the communication device.

33. The communication device according to any one of claims 31-32, wherein The receiving unit is further configured to receive a buffer status report from the terminal, and the buffer status report is used to indicate the data volume of the remaining uplink data. The second request message further includes information about the data volume of the remaining uplink data.

34. The communication device according to any one of claims 31-32, characterized in that, The second request message further includes third indication information for indicating that the communication device has the ability to configure authorization for the terminal.

35. The communication device according to claim 31, wherein The second request message is used to request the second network device to release a first data channel between the second network device and the core network device. The receiving unit is further configured to receive a first response message from the second network device. The data volume of the uplink data is greater than or equal to a first threshold, and the first response message is used to instruct the second network device to release the first data channel; or The data volume of the uplink data is less than or equal to a first threshold, and the first response message is used to instruct the second network device to retain the first data channel.

36. The communication device according to claim 33, characterized in that, The second request message is used to request the second network device to release a first data channel between the second network device and the core network device. The receiving unit is further configured to receive a first response message from the second network device. The data volume of the remaining uplink data is greater than or equal to a second threshold, and the first response message is used to instruct the second network device to release the first data channel; or The data volume of the remaining uplink data is less than or equal to a second threshold, and the first response message is used to instruct the second network device to retain the first data channel.

37. The communication device according to claim 34, wherein The second request message is used to request the second network device to release a first data channel between the second network device and the core network device. The receiving unit is further configured to receive a first response message from the second network device, where the first response message is used to instruct the second network device to release the first data channel; or the first response message is used to instruct the second network device to retain the first data channel.

38. The communication device according to any one of claims 35-37, characterized in that, The first request message includes the ability of the terminal to configure authorization; or the first response message includes the ability of the terminal to configure authorization.

39. The communication device according to claim 38, wherein The first response message further includes service model information for indicating at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, and the arrival timing of the terminal evaluated by the second network device.

40. The communication device according to any one of claims 35 to 37, characterized in that, The first response message is further used to establish a communication tunnel between the communication device and the second network device, where the communication tunnel is used to transmit the uplink data, and the communication tunnel has a corresponding relationship with the source logical channel identifier.

41. The communication device according to claim 33, wherein If the data volume of the remaining uplink data is greater than or equal to a second threshold, the communication device further includes a processing unit. The processing unit is configured to establish an RRC connection with the terminal.

42. The communication device according to any one of claims 31-32, characterized in that, The second request message is used to request the second network device to send the context of the terminal to the communication device. The receiving unit is further configured to receive a second response message from the second network device; the second response message includes the configuration of the source packet data convergence protocol and the configuration of the source radio link control.

43. The communication device according to claim 42, characterized in that, The first request message includes the ability of the terminal to configure authorization; or the second response message further includes the ability of the terminal to configure authorization.

44. The communication device according to claim 43, wherein, The second response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the second network device, the transport block size of the uplink data evaluated by the second network device, or the arrival timing of the terminal evaluated by the second network device.

45. The communication device according to any one of claims 43-44, characterized in that, The second response message is further used to indicate the establishment of a communication tunnel between the communication device and the second network device, where the communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier.

46. The communication device according to any one of claims 31-32, characterized in that, The first request message and the uplink data are multiplexed in one message.

47. A communication device, characterized in that, The communication device includes: a receiving unit and a processing unit; The receiving unit is configured to receive a second request message from a first network device, where the second request message includes information about uplink data, and the second request message is used to request the communication device to release a first data channel between the communication device and a core network device, and the communication device is a previous serving network device of the terminal. The processing unit is configured to release the first data channel according to the information about the uplink data; the information about the uplink data includes at least one of the following: first indication information, second indication information, the data volume of the uplink data, or the source logical channel identifier corresponding to the uplink data; the first indication information is used to indicate that the uplink data arrives at the first network device, and the second indication information is used to indicate that the uplink data is not included in the first request message, and the first request message is used by the terminal to request the first network device to resume a suspended radio resource control (RRC) connection.

48. The communication device according to claim 47, characterized in that, The second request message further includes information about the data volume of the remaining uplink data.

49. The communication device according to any one of claims 47 - 48, characterized in that, The second request message further includes third indication information, and the third indication information is used to indicate that the first network device has the ability to configure authorization for the terminal.

50. The communication device according to any one of claims 47-48, characterized in that, The second request message is used to request the communication device to release a first data channel between the communication device and a core network device, and the communication device further includes: a sending unit; The sending unit is configured to send a first response message to the first network device; When the data volume of the uplink data is greater than or equal to a first threshold, the first response message is used to indicate that the communication device releases the first data channel; or, When the data volume of the uplink data is less than or equal to the first threshold, the first response message is used to indicate that the communication device retains the first data channel.

51. The communication device according to claim 48, wherein The second request message is used to request the communication device to release a first data channel between the communication device and a core network device, and the communication device further includes: a sending unit; The sending unit is configured to send a first response message to the first network device; When the data volume of the remaining uplink data is greater than or equal to a second threshold, the first response message is used to indicate that the communication device releases the first data channel; or, When the data volume of the remaining uplink data is less than or equal to the second threshold, the first response message is used to indicate that the communication device retains the first data channel.

52. The communication device according to claim 49, characterized in that, The second request message is used to request the communication device to release a first data channel between the communication device and a core network device. The communication device further includes: a sending unit; The sending unit is configured to send a first response message to the first network device. The first response message is used to instruct the communication device to release the first data channel; or, the first response message is used to instruct the communication device to retain the first data channel.

53. The communication device according to any one of claims 51-52, characterized in that, The first request message includes the configuration authorization capability of the terminal; or, the first response message includes the configuration authorization capability of the terminal.

54. The communication device according to claim 53, wherein, The first response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the communication device, the transport block size of the uplink data evaluated by the communication device, and the arrival timing of the terminal evaluated by the communication device.

55. The communication device according to any one of claims 51-52, characterized in that, The first response message is further used to establish a communication tunnel between the first network device and the communication device. The communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier.

56. The communication device according to any one of claims 47-48, characterized in that, The second request message is used to request the communication device to send the context of the terminal to the first network device. The communication device further includes: a sending unit; The sending unit is configured to send a second response message to the first network device. The second response message includes the configuration of the source packet data convergence protocol and the configuration of the source radio link control.

57. The communication device according to claim 56, characterized in that, The first request message includes the configuration authorization capability of the terminal; or, the second response message further includes the configuration authorization capability of the terminal.

58. The communication device according to claim 57, characterized in that, The second response message further includes service model information, and the service model information is used to indicate at least one of the following parameters: the data arrival period of the terminal evaluated by the communication device, the transport block size of the uplink data evaluated by the communication device, and the arrival timing of the terminal evaluated by the communication device.

59. The communication device according to any one of claims 57-58, characterized in that, The second response message is further used to establish a communication tunnel between the first network device and the communication device. The communication tunnel is used to transmit the uplink data, and the identifier of the communication tunnel has a corresponding relationship with the source logical channel identifier.

60. The communication device according to any one of claims 47 - 48, characterized in that, The first request message and the uplink data are multiplexed in one message.

61. A communication device, characterized in that, Including: A processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the device is caused to execute the method according to any one of claims 1 to 16, or execute the method according to any one of claims 17 to 30.

62. A computer-readable medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instruction is executed, the computer is caused to execute the method according to any one of claims 1 to 16 or the method according to any one of claims 17 to 30.

Images