Communication method and device

By releasing or suspending the SRB and resetting the DRB protocol entity after receiving a message indicating that it enters the deactivated state in 3GPP new wireless technology, the problem that the deactivated state terminal cannot directly send uplink data is solved, and the service delay is reduced and power consumption effect.

CN113891353BActive Publication Date: 2024-11-29HUAWEI TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202111081604.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-03-01
Publication Date
2024-11-29
Estimated Expiration
2038-03-01

AI Technical Summary

Technical Problem

In the new 3GPP wireless technology, deactivated terminals cannot directly send uplink data, resulting in business delay problems.

Method used

After receiving a message indicating entering the deactivated state from the access network device, the terminal releases or suspends the dedicated signaling wireless bearer SRB and resets the protocol entity of the data wireless bearer DRB, so as to directly process the uplink data in the deactivated state.

Benefits of technology

It reduces the service delay of the terminal, improves data processing efficiency, and reduces power consumption and signaling overhead.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113891353B_ABST
    Figure CN113891353B_ABST
Patent Text Reader

Abstract

The present application discloses a communication method and device, which relates to the field of communication technology and can solve the problem of service delay caused by the inability to directly send uplink data. The method of the present application includes: receiving a first message from a first access network device, then releasing or suspending a configured dedicated signaling radio bearer SRB, and resetting a protocol entity corresponding to a configured data radio bearer DRB, the first message is used to indicate that the terminal enters a radio resource control RRC deactivated state, and the first message carries an identifier of the terminal in the radio resource control RRC deactivated state and radio access network notification area RNA information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to communication methods and devices. Background Art

[0002] The inactive state is a Radio Resource Control (RRC) state introduced in the 3rd Generation Partnership Project (3GPP) New Radio (NR) technology.

[0003] In one possible way, in the deactivated state, the terminal disconnects the RRC connection of the air interface from the access network device, and the terminal receives downlink data, downlink signaling, etc. at the agreed time and frequency position. For example, the terminal can receive a paging message sent by the access network device. In addition, in the deactivated state, the access network device stores the access layer context of the terminal and allocates a Radio Access Network Notification Area (RNA) and an identifier of the terminal in the deactivated state to the terminal. Among them, RNA can be used for mobility management of the terminal.

[0004] Currently, no technical solution has been proposed to enable a terminal in a deactivated state to directly send uplink data. If the terminal cannot directly send uplink data when there is a demand for uplink data, it will cause service delays of the terminal. Summary of the invention

[0005] The present application provides a communication method and device, which can solve the problem of service delay caused by the inability of a deactivated terminal to directly send uplink data.

[0006] In order to achieve the above purpose, the embodiments of the present application adopt the following technical solutions:

[0007] In a first aspect, an embodiment of the present application provides a communication method, which can be implemented by a terminal or a chip that can be used for a terminal, and the method includes: receiving a first message from a first access network device, and then releasing or suspending the configured dedicated signaling radio bearer SRB, and resetting the protocol entity corresponding to the configured data radio bearer DRB.

[0008] Among them, the first message is used to instruct the terminal to enter the RRC deactivated state, and the first message carries the identifier of the terminal in the RRC deactivated state and RNA information.

[0009] By adopting this method, the terminal can receive a first message from the first access network device indicating that it has entered a deactivated state, thereby releasing or suspending the configured dedicated SRB, and resetting the protocol entity corresponding to the configured DRB. It can be seen that in the embodiment of the present application, since the terminal retains and resets the DRB and the corresponding protocol layer entity, after the terminal enters the deactivated state, if there is uplink data to be transmitted, the uplink data can be directly processed through the reset DRB, thereby reducing the service delay of the terminal.

[0010] It should be noted that the embodiments of the present application can be applied to NR and other types of wireless access networks. For example, if applied to a wireless access network of Long Term Evolution (LTE), since there is no SDAP layer and SDAP layer entity in LTE, the protocol entity corresponding to the DRB includes a packet data convergence protocol (PDCP) layer entity, a radio link control (RLC) layer entity, and a common medium access control MAC entity. Accordingly, when the terminal performs a reset operation, the PDCP, RLC, and MAC layer entities need to be reset.

[0011] If applied to the wireless access network of NR technology, since there are SDAP layer and SDAP layer entities in NR technology, the protocol entities corresponding to DRB include entities of PDCP, RLC, MAC and SDAP layers. Accordingly, when the terminal performs a reset operation, it is necessary to reset the entities of PDCP, RLC, MAC and SDAP layers. The embodiment of this application mainly takes the application to NR technology as an example, that is, the following takes the protocol entities corresponding to DRB including entities of PDCP, RLC, MAC and SDAP layers as an example.

[0012] Optionally, the first message carries timing information, where the timing information is used to indicate a preset duration.

[0013] In one possible design, releasing or suspending the configured dedicated SRB and resetting the protocol entity corresponding to the configured DRB can be specifically implemented as follows: if no scheduling information is received within a preset time after receiving the first message, then releasing or suspending the configured dedicated SRB and the corresponding protocol layer entity, and resetting the configured dedicated DRB and the corresponding protocol layer entity after the preset time.

[0014] Exemplarily, when the scheme of the embodiment of the present application is applied to the wireless access network of LTE, the configured dedicated SRB is released or suspended, and the protocol entity corresponding to the configured DRB is reset. Specifically, it can be implemented as follows: if the scheduling information is not received within a preset time after receiving the first message, the configured dedicated SRB and the corresponding protocol layer entity are released or suspended after the preset time, and the configured PDCP, RLC and MAC layer entities are reset.

[0015] When the solution of the embodiment of the present application is applied to the wireless access network of NR, the configured dedicated SRB is released or suspended, and the protocol entity corresponding to the configured DRB is reset. Specifically, it can be implemented as follows: if the scheduling information is not received within a preset time after receiving the first message, the configured dedicated SRB and the corresponding protocol layer entity are released or suspended after the preset time, and the configured PDCP, RLC, MAC and SDAP layer entities are reset.

[0016] It should be noted that, in addition to determining the preset duration according to the timing information carried in the first message, the preset duration may also be a time value pre-stored in the terminal.

[0017] In a possible design, releasing or suspending the configured dedicated SRB and the corresponding protocol layer entity, resetting the configured dedicated DRB and the corresponding protocol layer entity may also be implemented as follows:

[0018] After receiving the first message, performing a cell reselection operation;

[0019] If the first cell is reselected within the preset time, the configured dedicated SRB is released or suspended, and the protocol entity corresponding to the configured DRB is reset. The first cell belongs to the cell indicated by the RNA information and is different from the cell where the first message is received.

[0020] With this method, after receiving the first message sent by the first access network device, the terminal does not immediately enter the deactivated state, but enters the deactivated state only when a specific condition is met, and the specific condition includes: the terminal reselects to the first cell within a preset time after receiving the first message, or the terminal does not reselect to the first cell within a preset time after receiving the first message and does not receive scheduling information. Thus, after the terminal enters the deactivated state, the amount of uplink information (including uplink data and uplink information) sent is reduced, and the power consumption of the terminal is reduced.

[0021] In one possible design, if there is uplink data to be transmitted, the uplink data is transmitted through the DRB corresponding to the uplink data; or, if there is uplink signaling to be transmitted, the uplink signaling is transmitted through a common signaling radio bearer.

[0022] In a possible design, after releasing or suspending the configured dedicated SRB and the corresponding protocol layer entity and resetting the configured dedicated DRB and the corresponding protocol layer entity according to the first message, the following may also be performed:

[0023] If the cell covered by the second access network device is reselected and there is uplink information to be transmitted, a second message is sent to the second access network device.

[0024] Among them, the second message carries the identifier of the terminal in the RRC deactivated state and the information of the reason for triggering the sending of the second message. The reselected cell belongs to the cell indicated by the RNA information. Assuming that the cell covered by the first access network device where the terminal initially resides is called the source cell, the reselected cell and the source cell belong to the same cell indicated by the RNA. In addition, the identifier of the terminal in the RRC deactivated state is associated with the first access network device and the architecture of the first access network device. Specifically, the identifier of the terminal in the RRC deactivated state can carry the identifier of the first access network device and information related to whether the first access network device is a centralized unit (Central Unit, CU) / distributed unit (Distributed Unit, DU) architecture. Optionally, the second access network device can address the first access network device according to the identifier of the first access network device. The second access network device can determine whether to migrate the anchor access network device of the terminal based on the CU / DU architecture of the first access network device.

[0025] By adopting this method, when the terminal reselects to a cell covered by the second access network device and there is uplink information to be transmitted, the terminal can send a second message to the second access network device to trigger the second access network device to determine whether to migrate the anchor access network device of the terminal. Among them, the second access network device can determine whether to migrate the anchor access network device of the terminal based on the information of the reason for triggering the sending of the second message (also referred to as the reason information in this article) and / or the architecture of the first access network device. Furthermore, the anchor access network device of the terminal is migrated only when the triggering conditions for migrating the anchor access network device are met, thereby avoiding the problem of high signaling overhead caused by frequent migration of anchor points, and while saving signaling overhead, it can also reduce the power consumption of the terminal.

[0026] In a second aspect, an embodiment of the present application provides a communication method, which can be implemented by a first access network device or a chip that can be used for the first access network device, and the method includes: the first access network device sends a first message to a terminal, and then the first access network device releases or suspends a dedicated signaling radio bearer SRB configured corresponding to the terminal, and resets a protocol entity corresponding to a data radio bearer DRB configured corresponding to the terminal.

[0027] The first message is used to instruct the terminal to enter the radio resource control RRC deactivated state, and the first message carries the identifier of the terminal in the RRC deactivated state and the radio access network notification area RNA information.

[0028] Using this method, the first access network device sends a first message to the terminal to instruct the terminal to enter a deactivated state, and then releases or suspends the configured dedicated SRB, and resets the protocol entity corresponding to the configured DRB. It can be seen that in the embodiment of the present application, since the terminal retains and resets the DRB and the corresponding protocol layer entity, after the terminal enters the deactivated state, if there is uplink data to be transmitted, the uplink data can be directly processed through the reset DRB, thereby reducing the service delay of the terminal.

[0029] Referring to the above description, the protocol entities corresponding to the DRB include entities of the PDCP, RLC, MAC and SDAP layers, or the protocol entities corresponding to the DRB include entities of the PDCP, RLC and MAC layers.

[0030] In one possible design, the first access network device releases or suspends the dedicated SRB configured corresponding to the terminal, and resets the protocol entity corresponding to the DRB configured corresponding to the terminal. Specifically, it can be implemented as follows: if scheduling information is not sent to the terminal within a preset time after sending the first message, then the dedicated SRB configured corresponding to the terminal is released or suspended after the preset time, and the protocol entity corresponding to the DRB configured corresponding to the terminal is reset.

[0031] In a possible design, the first access network device releases or suspends the dedicated SRB configured corresponding to the terminal, and resets the protocol entity corresponding to the DRB configured corresponding to the terminal, which can also be implemented as follows: if it is determined that the terminal reselects to the first cell within a preset time after the first access network device sends the first message, the dedicated SRB configured corresponding to the terminal is released or suspended, and the protocol entity corresponding to the DRB configured corresponding to the terminal is reset. This means that within the preset time, the terminal reselects to the first cell and can also trigger the process of entering the deactivated state.

[0032] With this method, after the first access network device sends the first message to the terminal, a preset duration can be set. Before the preset duration is reached, if the terminal reselects to the first cell, the first access network device can instruct the terminal to enter the deactivated state. Alternatively, if the terminal does not reselect to the first cell or receive scheduling information within the preset duration after receiving the first message, it can instruct the terminal to enter the deactivated state. Thus, after instructing the terminal to enter the deactivated state, the amount of uplink information (uplink information includes uplink data and uplink information) sent by the terminal is reduced, thereby reducing the power consumption of the terminal.

[0033] In a possible design, if the first access network device includes a CU and a DU, the first access network device sends a first message to the terminal, which can be specifically implemented as follows: the first access network device sends the first message to the terminal through the DU.

[0034] In one possible design, you can also do:

[0035] The CU in the first access network device sends a third message to the DU, and then the DU of the first access network device determines the relevant configuration of the wireless bearer of the terminal. The DU determines the relevant configuration of the wireless bearer of the terminal, which can be specifically implemented by: releasing or suspending the SRB configured corresponding to the terminal and the protocol entity corresponding to the configured SRB in the DU, releasing or suspending the radio link control RLC protocol entity corresponding to the DRB configured corresponding to the terminal, and resetting the entity of the public medium access control layer.

[0036] Afterwards, after the CU in the first access network device sends the third message to the DU, the CU of the first access network device releases or suspends the configured SRB and the protocol entity corresponding to the configured SRB in the CU, resets the configured DRB and the protocol entity corresponding to the configured DRB in the CU, and generates an RLC protocol entity corresponding to the DRB.

[0037] Alternatively, after the DU determines the relevant configuration of the terminal's wireless bearer, the DU sends a response message to the third message to the CU. After receiving the response message to the third message, the CU releases or suspends the configured SRB and the protocol entity corresponding to the configured SRB in the CU, resets the configured DRB and the protocol entity corresponding to the configured DRB in the CU, and generates an RLC protocol entity corresponding to the DRB.

[0038] The third message includes the identifier of the terminal in the RRC connected state. For example, the identifier of the terminal in the RRC connected state is C-RNTI. The third message is used to instruct the DU to transfer the terminal to the deactivated state. The response message of the third message is used to indicate that the DU has processed the wireless bearer and protocol entity of the terminal.

[0039] By adopting this method, after the terminal enters the deactivated state, the RLC protocol entity corresponding to the DRB of the terminal is deployed on the CU, and the RLC protocol entity corresponding to the terminal on the DU is released or suspended. Therefore, when uplink data arrives, the CU in the first access network device can process the uplink data in the MAC SDU format through the deployed RLC protocol entity, and then send the processed uplink data to the PDCP and SDAP entities for processing in turn, without the need for frequent interaction with the DU, thereby reducing processing delay.

[0040] In a possible design, when it is determined that the migration of the terminal at the entrance of the core network from the first access network device to the second access network device will not be triggered, the following can be executed: the first access network device receives the uplink information of the terminal forwarded by the second access network device, and then the first access network device processes the uplink information through the protocol entity corresponding to the uplink information of the terminal.

[0041] The uplink information carries the identifier of the terminal in the RRC deactivated state.

[0042] By adopting this method, when it is determined not to migrate the anchor access network device of the terminal, the first access network device completes the data or signaling interaction with the terminal, avoiding the problem of high signaling overhead caused by frequent migration of the anchor access network device, and at the same time, it can also reduce the power consumption of the terminal.

[0043] In one possible design, the uplink information carries verification information corresponding to the terminal. Accordingly, before the first access network device processes the uplink information through the protocol entity, it can be performed as follows: the first access network device authenticates the identity of the terminal according to the verification information, and after the verification is passed, the first access network device processes the uplink information through the protocol entity.

[0044] In a possible design, the uplink information carries the cause information. Accordingly, the first access network device can determine whether to update the access layer security key corresponding to the terminal according to the cause information.

[0045] In one possible design, when it is determined that the trigger is to migrate the terminal's entrance in the core network from the first access network device to the second access network device, it can be executed: the first access network device receives a request message for obtaining the terminal context sent by the second access network device, and then the first access network device sends the context information of the terminal to the second access network device.

[0046] The request message carries an identifier of the terminal in the RRC deactivated state.

[0047] By adopting this method, if the anchor access network device of the terminal needs to be migrated, the second access network device will provide coverage service for the terminal. Since the second access network device is usually closer to the terminal or has better service quality, the communication quality of the terminal can be improved.

[0048] In one possible design, before the first access network device receives the request message for obtaining the terminal context sent by the second access network device, it can also be performed: the first access network device sends architecture indication information to the second access network device. The architecture indication information is used to indicate whether the first access network device is an access network device of the CU / DU architecture type.

[0049] Using this method, the first access network device sends architecture indication information to the second access network device to instruct the second access network device to determine whether to migrate the anchor access network device of the terminal based on the architecture of the first access network device. If the first access network device is a CU / DU architecture, the anchor point of the terminal is migrated to the second access network device, and the second access network device processes the uplink information of the terminal, thereby reducing signaling overhead.

[0050] In a third aspect, an embodiment of the present application provides a communication method, which can be implemented by a second access network device or a chip that can be used for the second access network device, the method comprising: the second access network device receives a second message sent by a terminal, if the second access network device determines, based on information about a reason for triggering the sending of the second message, to trigger the migration of the terminal at the entrance of the core network from the first access network device to the second access network device, then the second access network device sends a request message to the first access network device to obtain context information of the terminal, and then the second access network device receives the context information of the terminal sent by the first access network device.

[0051] The second message carries information about an identifier of the terminal in a radio resource control (RRC) deactivated state and a reason for triggering sending the second message.

[0052] By adopting this method, the second access network device can receive the second message sent by the terminal, and determine whether to migrate the anchor access network device of the terminal based on the reason information in the second message. Furthermore, the anchor access network device of the terminal is migrated only when the triggering conditions for migrating the anchor access network device are met, thereby avoiding the problem of high signaling overhead caused by frequent migration of anchor points. While saving signaling overhead, it can also reduce the power consumption of the terminal.

[0053] In a possible design, after the second access network device receives the context information of the terminal sent by the first access network device, it can also execute: the second access network device generates a protocol entity corresponding to the DRB of the terminal according to the context information of the terminal.

[0054] By adopting this method, after determining the anchor access network device of the terminal to be migrated, the second access network device processes the uplink information of the terminal and provides coverage service for the terminal. Since the second access network device is usually closer to the terminal or has better service quality, the communication quality of the terminal can be improved.

[0055] Referring to the above description, the protocol entities corresponding to the DRB include a PDCP entity, an RLC entity, a common MAC entity and an SDAP entity, or the protocol entities corresponding to the DRB include a PDCP entity, an RLC entity and a common MAC entity.

[0056] In one possible design, the cause information includes: uplink cache status report, service / slice type and quality of service QoS category information to which the uplink data belongs, and network load.

[0057] In one possible design, it can also be executed: the second access network device determines whether the first access network device is a centralized unit CU / distributed unit DU architecture; if the first access network device is a CU / DU architecture, it triggers the migration of the terminal's entrance in the core network from the first access network device to the second access network device.

[0058] Using this method, if the second access network device determines that the first access network device is a CU / DU architecture, the anchor point of the terminal is migrated to the second access network device, and the second access network device processes the uplink information of the terminal, thereby reducing signaling overhead.

[0059] In one possible design, the second access network device determines whether the first access network device is a CU / DU architecture, which can be specifically implemented as follows: the second access network device obtains the architecture indication information sent by the first access network device, and then the second access network device determines whether the first access network device is a CU / DU architecture based on the architecture indication information.

[0060] Exemplarily, the second access network device obtains the architecture indication information of the first access network device, which can be specifically implemented as follows: the first access network device sends the architecture indication information to the second access network device, and correspondingly, the second access network device receives the architecture indication information.

[0061] The second access network device determines whether the first access network device is a CU / DU architecture, which can also be implemented as follows: the second access network device determines whether the first access network device is a CU / DU architecture based on an identifier of the terminal in an RRC deactivated state.

[0062] In a possible design, it can also be executed: if the second access network device determines based on the reason information not to trigger the migration of the terminal's entrance in the core network from the first access network device to the second access network device, the second access network device sends uplink information to the first access network device.

[0063] By adopting this method, when the second access network device determines not to migrate the anchor access network device of the terminal, it instructs the first access network device to process the uplink information of the terminal to complete the data or signaling interaction with the terminal, thereby avoiding the problem of high signaling overhead caused by frequent migration of anchor access network devices, and at the same time, it can also reduce the power consumption of the terminal.

[0064] In a fourth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the method described in the first aspect above. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the device can be a terminal, or can be a chip that can be used for a terminal.

[0065] In one possible design, the device is a terminal, and the terminal includes a processor, and the processor is configured to support the terminal to perform the corresponding functions in the above method. Further, the terminal may also include a transmitter and a receiver, and the transmitter and the receiver are used to support communication between the terminal and the network side device. Further, the terminal may also include a memory, and the memory is used to couple with the processor, which stores the necessary program instructions and data of the terminal. Here, the network side device includes but is not limited to the first access network device and the second access network device.

[0066] In a fifth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the method described in the second aspect above. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the device can be a base station, or can be a chip that can be used for a base station.

[0067] In one possible design, the apparatus is a base station, and the base station includes a processor, and the processor is configured to support the base station to perform corresponding functions in the above method. Further, the base station may also include a transmitter and a receiver, and the transmitter and the receiver are used to support communication between the base station and the terminal. Further, the base station may also include a memory, and the memory is used to be coupled with the processor, and the memory stores necessary program instructions and data for the base station.

[0068] In a sixth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the method described in the third aspect above. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the device can be a base station, or can be a chip that can be used for a base station.

[0069] In one possible design, the apparatus is a base station, and the base station includes a processor, and the processor is configured to support the base station to perform corresponding functions in the above method. Further, the base station may also include a transmitter and a receiver, and the transmitter and the receiver are used to support communication between the base station and the terminal, or to support communication between base stations. Further, the base station may also include a memory, and the memory is used to be coupled with the processor, and the memory stores necessary program instructions and data for the base station.

[0070] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the terminal described in the above aspects and a first access network device and a second access network device.

[0071] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer executes the method described in the first aspect, the second aspect, or the third aspect above.

[0072] In a ninth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the first aspect, the second aspect, or the third aspect above.

[0073] In the tenth aspect, an embodiment of the present application provides a chip system, which is applied to a terminal, and the chip system includes at least one processor, a memory and an interface circuit, the memory, the transceiver and the at least one processor are interconnected through lines, and instructions are stored in the at least one memory; the instructions are executed by the processor to execute the method described in the first aspect above.

[0074] In the eleventh aspect, an embodiment of the present application provides a chip system, which is applied to a network side device, exemplarily, to a first access network device, wherein the chip system includes at least one processor, a memory and an interface circuit, wherein the memory, the transceiver and the at least one processor are interconnected via lines, and instructions are stored in the at least one memory; the instructions are executed by the processor to execute the method described in the second aspect above.

[0075] In the twelfth aspect, an embodiment of the present application provides a chip system, which is applied to a network side device, exemplarily, to a second access network device, wherein the chip system includes at least one processor, a memory and an interface circuit, wherein the memory, the transceiver and the at least one processor are interconnected via lines, and instructions are stored in the at least one memory; the instructions are executed by the processor to execute the method described in the third aspect above.

[0076] Through the solution of the embodiment of the present application, the terminal receives a first message from the first access network device indicating entering the deactivated state, and then releases or suspends the configured dedicated SRB, and resets the protocol entity corresponding to the configured DRB. That is, the embodiment of the present application provides a DRB that can be used to directly process uplink data, so that when the terminal has uplink data to be transmitted, the uplink data can be directly processed through the reset DRB, reducing the service delay of the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] Figure 1aA schematic diagram of the structure of a communication system provided in an embodiment of the present application;

[0078] Figure 1b A schematic diagram of the structure of a base station provided in an embodiment of the present application;

[0079] Figure 2 A flow chart of a communication method provided in an embodiment of the present application;

[0080] Figure 3 A schematic diagram of a protocol stack provided in an embodiment of the present application;

[0081] Figure 4 A flow chart of a communication method provided in an embodiment of the present application;

[0082] Figure 5 A flow chart of a communication method provided in an embodiment of the present application;

[0083] Figure 6 A flow chart of a communication method provided in an embodiment of the present application;

[0084] Figure 7 A flow chart of a communication method provided in an embodiment of the present application;

[0085] Figure 8 A flow chart of a communication method provided in an embodiment of the present application;

[0086] Fig. 9 A flow chart of a communication method provided in an embodiment of the present application;

[0087] Fig.10 A flow chart of a communication method provided in an embodiment of the present application;

[0088] Fig.11 A schematic diagram of a protocol stack provided in an embodiment of the present application;

[0089] Fig.12 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0090] Fig.13 A schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0091] Fig.14 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0092] Fig.15 A schematic diagram of the structure of a base station provided in an embodiment of the present application. DETAILED DESCRIPTION

[0093] The system architecture and business scenarios described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided by this application. A person of ordinary skill in the art will appreciate that, with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided by this application are equally applicable to similar technical problems.

[0094] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0095] In this application, “of”, “corresponding”, “relevant” and “corresponding” may sometimes be used interchangeably. It should be pointed out that when the distinction is not emphasized, the meanings they intend to express are the same.

[0096] The embodiments of the present application are applied to NR and other types of wireless access networks.

[0097] like Figure 1a As shown, Figure 1a A schematic diagram of a possible communication system of the present application is shown, which communication system may include at least one core network device (only one is shown in the figure), one or more access network devices that communicate with the core network device and the terminal, and a terminal that accesses the core network through the access network device.

[0098] Among them, the core network equipment referred to in this application is a device deployed in the core network to provide services to the terminal. The core network equipment referred to in this application includes but is not limited to: Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy and Charging Rules Function (PCRF), and devices combined therefrom. In systems using different wireless access technologies, the names of core network devices with similar wireless communication functions may be different. For the convenience of description only, in the embodiments of this application, the above-mentioned devices that can provide services to the terminal are collectively referred to as core network devices.

[0099] The access network equipment referred to in this application is a device deployed in a wireless access network to provide wireless communication functions for terminals. The access network equipment referred to in this application includes but is not limited to: various forms of macro base stations, micro base stations (also called small stations), relay stations, transmission reception points (Transmission Reception Point, TRP), next generation network nodes (gNode B, gNB), evolved Node B (ng evolved Node B, ng-eNB) connected to the next generation core network, etc., and may also include wireless local area network (WLAN) access equipment and other wireless access network equipment of non-3GPP systems. In systems using different wireless access technologies, the names of wireless access network devices with similar wireless communication functions may be different. For the convenience of description only, in the embodiments of this application, the above-mentioned devices that can provide wireless communication functions for terminals are collectively referred to as access network equipment.

[0100] The terminal referred to in this application is a device with wireless transceiver function, which can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The terminal can include various types of mobile phones, tablets (Pad), computers with wireless transceiver function, wireless data cards, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, machine type communication (MTC) terminal devices, terminal devices in industrial control, terminal devices in self-driving, terminal devices in remote medical, terminal devices in smart grid, terminal devices in transportation safety, terminal devices in smart city, and wearable devices (such as smart watches, smart bracelets, pedometers, etc.), etc. In systems using different wireless access technologies, the names of terminals with similar wireless communication functions may be different. For the convenience of description only, in the embodiments of the present application, the above-mentioned devices with wireless transceiver communication functions are collectively referred to as terminals.

[0101] In the communication system in the embodiment of the present application, the access network device and the core network device can communicate through the NG interface, and the access network devices can communicate through the Xn interface. It is understandable that the access network device and the core network device can also communicate through other types of interfaces, and similarly, the access network devices can also communicate through other types of interfaces, and the embodiment of the present application is not limited to this.

[0102] The access network device of the embodiment of the present application is described below using a base station as an example.

[0103] like Figure 1b As shown in FIG. 1 , in one possible manner, a base station can be composed of a centralized unit (CU) and a distributed unit (DU). A CU can be connected to a DU, or multiple DUs can share a CU, which can save costs and facilitate network expansion. The CU and DU can be divided according to the protocol stack. One possible manner is to deploy the radio resource control (RRC), service data adaptation protocol (SDAP) and PDCP layers in the CU, and the remaining RLC layer, MAC layer and physical layer (PHY layer) in the DU.

[0104] The above-mentioned protocol stack segmentation method is not completely limited in the embodiments of the present application, and other segmentation methods may also be used. Figure 1b When describing the architecture of CU and DU, when the embodiments of the present application mention access network equipment, it may refer to CU, DU, or a system composed of CU and DU, depending on the corresponding implementation function.

[0105] It is understandable that the base station mentioned in the embodiments of the present application is not limited to Figure 1b The form of the wireless communication device may be any device deployed in a wireless access network to provide wireless communication functions for terminals.

[0106] The method involved in the embodiment of the present application is mainly used in a wireless access network, that is, the method of the embodiment of the present application is mainly used in an access network system composed of an access network device and a terminal. The above communication system composed of a terminal, an access network device and a core network device includes an access network system.

[0107] The terms in the embodiments of the present application are explained below.

[0108] The context information of the terminal is used to characterize all information about the identity, background and status of the terminal. Exemplarily, the context information of the terminal includes but is not limited to the location information of the terminal, the terminal identification, and the dedicated wireless bearer configuration information. Among them, the access network device can generate a protocol entity corresponding to the terminal according to the context information of the terminal, and process the data or signaling of the terminal through the corresponding protocol entity.

[0109] Anchor access network device is used to maintain the context of the terminal. Among them, the terminal may migrate the anchor access network device when moving. For example, the terminal initially resides in the first access network device, and the first access network device stores and maintains the context information of the terminal. Later, the terminal changes its location and its current service access network device is the second access network device. If it is determined that the terminal's entry in the core network is migrated from the first access network device to the second access network device, the terminal context information maintained by the first access network device needs to be transmitted to the second access network device, so that the second access network device can process the terminal's data or signaling according to the obtained terminal context information and interact with the terminal.

[0110] Combination Figure 1a The communication system shown and Figure 1b The base station shown in the embodiment of the present application provides a communication method, such as Figure 2 As shown, the method includes:

[0111] S201. A first access network device sends a first message to a terminal.

[0112] Correspondingly, the terminal receives the first message sent by the first access network device.

[0113] Among them, the first message is used to instruct the terminal to enter the RRC deactivated state, and the first message carries the identifier of the terminal in the RRC deactivated state and RNA information.

[0114] Optionally, the identifier of the terminal in the RRC deactivated state can be the inactive-Radio Network Temporary Identifier (I-RNTI) of the terminal, and the RNA information is used to indicate the RNA. The access network device can allocate the RNA to the terminal, and an RNA usually includes at least one cell. As an exemplary scheme, the RNA information can be a list of cell identifiers. It can be understood that when the terminal position changes, if the current position of the terminal is within the range included in the RNA, the terminal may not send the current location information to the access network device. If the terminal has currently moved out of the range included in the RNA, in order to manage the terminal position, the terminal needs to send the current location information to the access network device. In addition, if the terminal has not moved out of the range included in the RNA, but after the preset time is reached, the terminal also needs to send the current location information to the access network device. For example, the cells covered by the first access network device are cell 1 to cell 3, and the cells covered by the second access network device are cell 4 to cell 5. Assuming that the terminal initially accesses cell 1 of the first access network device, and the first access network device allocates RNA_1 to the terminal, and RNA_1 includes cells 1 to cell 3, when the terminal moves to the coverage area of ​​cell 2 or cell 3, since the terminal has not moved out of the coverage area of ​​RNA_1, the terminal may not report the current location information to the access network device. When the terminal moves to cell 4, cell 5 or cell 6, since the terminal has moved out of the coverage area of ​​RNA_1, the terminal needs to report the current location information to the access network device.

[0115] It can be understood that the first access network device can detect the data transmission status of the terminal. When it is detected that the terminal has not transmitted data for a period of time, the first access network device can send a first message to the terminal to instruct the terminal to enter a deactivated state. Alternatively, the terminal detects its own data transmission status. When it is detected that it has not transmitted data for a period of time, the terminal initiates a request to the first access network device to enter the deactivated state. After receiving the request from the terminal, the first access network device sends a first message to the terminal to instruct the terminal to enter the deactivated state.

[0116] Optionally, when the first access network device is a base station of a CU / DU architecture, for example, when the first access network device is Figure 1b When the base station is shown, the first access network device generates a first message through the CU and sends the first message to the terminal through the DU.

[0117] S202. The terminal releases or suspends the configured dedicated signaling radio bearer (SRB), and resets the protocol entity corresponding to the configured data radio bearer (DRB).

[0118] It should be noted that the embodiments of the present application can be applied to NR and other types of wireless access networks. Exemplarily, if applied to a wireless access network of LTE, since there is no SDAP layer and SDAP layer entity in LTE, the protocol entity corresponding to the DRB includes a packet data convergence protocol (PDCP) layer entity, a radio link control (RLC) layer entity, and a common medium access control MAC entity. Accordingly, when the terminal performs a reset operation, the PDCP, RLC, and MAC layer entities need to be reset.

[0119] If applied to the wireless access network of NR technology, since there are SDAP layer and SDAP layer entities in NR technology, the protocol entities corresponding to DRB include PDCP, RLC, MAC and SDAP layer entities. Accordingly, when the terminal performs a reset operation, it is necessary to reset the PDCP, RLC, MAC and SDAP layer entities.

[0120] The following mainly uses the wireless access network applied to NR technology as an example to illustrate the solution of the embodiment of the present application, that is, the DRB protocol entity includes entities of PDCP, RLC, MAC and SDAP layers as an example.

[0121] After receiving the first message, the terminal may perform the following operations:

[0122] First: Release or suspend the configured dedicated SRB.

[0123] In the 3GPP protocol, SRBs include dedicated SRBs and public SRBs. Dedicated SRBs are signaling radio bearers that use acknowledged mode (AM) for transmission. Dedicated SRBs include but are not limited to SRB1, SRB2, and SRB3. Public SRBs include but are not limited to SRB0 that uses transparent mode (TM). In an embodiment of the present application, the terminal releases or suspends the dedicated SRB after receiving the first message.

[0124] Specifically, the terminal releases or suspends the protocol entity corresponding to the dedicated SRB, and the protocol entity corresponding to the dedicated SRB includes but is not limited to the entities of the RRC layer, PDCP layer and RLC layer. Release means that the relevant functions of the wireless bearer and / or protocol entity are turned off or removed, that is, after the release operation, the terminal cannot process the uplink signaling through the relevant functions of the protocol entity, nor can it transmit the processed uplink signaling through the dedicated SRB. Suspension means retaining the wireless bearer and / or protocol entity, as well as the corresponding configuration information, but suspending their use to process the corresponding protocol data, and suspending the operation of the corresponding timers and counters.

[0125] If there is a dedicated SRB corresponding to multiple logical channels, the terminal needs to reset the corresponding entity corresponding to the dedicated SRB. Exemplarily, the dedicated SRB is a split radio bearer, that is, one dedicated SRB corresponds to two logical channels. If each logical channel corresponds to an RLC entity, that is, one dedicated SRB has two corresponding RLC entities, then the terminal needs to reset the two RLC entities corresponding to the dedicated SRB.

[0126] Of course, after releasing or suspending the configured dedicated SRB, the terminal can perform signaling interaction with the first access network device through SRB0.

[0127] Second: the terminal resets the protocol entity corresponding to the configured DRB.

[0128] Taking the application in NR as an example, the protocol entities corresponding to DRB include entities of the PDCP, RLC, MAC and SDAP layers.

[0129] Among them, one SDAP entity corresponds to a packet data unit (PDU) session of the terminal, and one PDU session corresponds to one or more DRBs. Exemplarily, if there is a configured DRB as a split radio bearer, assuming that one DRB corresponds to two logical channels, each logical channel corresponds to an RLC entity, that is, the DRB has two corresponding RLC entities, then the terminal needs to reset the two RLC entities corresponding to the configured DRB. Accordingly, the terminal needs to reset other related protocol layer entities corresponding to the two logical channels.

[0130] It should be noted that there is no time sequence between the first and second steps. For example, the terminal may execute the first step first and then the second step, or may execute the first and second steps at the same time. This embodiment of the application does not limit this.

[0131] It is understandable that after executing the two steps included in S202, the terminal enters a deactivated state. In the deactivated state, the terminal enters an energy-saving state, but the terminal can perform operations such as monitoring a paging channel so that the access network device can address the terminal when it needs to transmit downlink data.

[0132] In this way, after the deactivated terminal receives the uplink data, it can map the uplink data from the Quality of Service (QoS) flow to the DRB through the SDAP entity, and send the processed data to the corresponding PDCP entity. The PDCP entity compresses and encrypts the data, and sends the compressed and encrypted data to the RLC entity. The RLC entity segmented the data and sent the segmented data to the MAC entity. The MAC entity performs multiplexing and other operations. After that, the physical layer protocol entity transmits the uplink data processed by each layer entity.

[0133] Exemplarily, before the terminal receives the first message, Figure 3 As shown in (a), the terminal is configured with 4 dedicated radio bearers and 1 public SRB. Among them, the 4 dedicated radio bearers include SRB1, SRB2, DRB1, DRB2, and the public SRB is SRB0. Among them, SRB0 corresponds to the RRC layer protocol entity, and the protocol entity corresponding to SRB1 includes the RRC layer, PDCP layer and RLC layer entities. The protocol entity corresponding to SRB2 includes the RRC layer, PDCP layer and RLC layer entities. The protocol entity corresponding to DRB1 includes SDAP, PDCP, RLC, and public MAC layer entities. The protocol entity corresponding to DRB2 includes SDAP, PDCP, RLC, and public MAC layer entities. DRB1 and DRB2 share an SDAP entity. The terminal is also configured with a PHY layer entity.

[0134] After the terminal receives the first message, the protocol stack of the terminal is as follows Figure 3 (b) or Figure 3 As shown in (c), accordingly, the operations performed by the terminal may include the following two situations:

[0135] Case 1:

[0136] like Figure 3 As shown in (b), the terminal releases SRB1 and SRB2. Specifically, the terminal releases the RRC layer, PDCP layer and RLC layer entities corresponding to SRB1 and SRB2. In addition, the terminal also resets Figure 3 DRB1, DRB2 shown in (b), and their corresponding SDAP, PDCP, RLC and MAC layer entities.

[0137] It should be noted that Figure 3The white filled portion in the figure indicates that the corresponding protocol entity is reset. Thus, the terminal can process uplink data through the protocol entities corresponding to DRB1 and DRB2 in the reset state. Optionally, the PHY entity is also reset, so that the processed uplink data is transmitted by the PHY entity. In addition, the PHY entity can also be in other states that can be used to transmit uplink information (including uplink data and uplink signaling), which is not limited in the embodiments of the present application.

[0138] In this way, if the terminal has uplink data to be transmitted, as a possible implementation method, the terminal can process the uplink data through the protocol entity corresponding to the DRB. Exemplarily, the terminal can map the uplink data from the QoS flow to the DRB through the SDAP entity, send the processed data to the PDCP entity, and the PDCP entity compresses and encrypts the data, and sends the compressed and encrypted data to the RLC entity, and the RLC entity performs operations such as segmentation on the data. Afterwards, the terminal sends the segmented data to the MAC entity, and the MAC entity performs operations such as multiplexing, and then the PHY entity transmits the processed uplink data.

[0139] If the terminal has uplink signaling to be transmitted, as a possible implementation method, the terminal can process the uplink signaling to be transmitted through SRB0. Specifically, the terminal can process the uplink signaling to be transmitted in sequence through the RRC protocol entity and the MAC layer entity corresponding to SRB0, and then transmit the processed uplink signaling through the PHY entity.

[0140] Case 2:

[0141] like Figure 3 As shown in (c), the terminal suspends SRB1 and SRB2, specifically, the terminal suspends the RRC layer, PDCP layer and RLC layer entities corresponding to SRB1 and SRB2, respectively, and resets the SDAP, PDCP, RLC and MAC layer entities corresponding to DRB1 and DRB2, respectively.

[0142] It should be noted that Figure 3 The shaded portion in (c) indicates that the corresponding protocol entity is suspended.

[0143] In this way, if the terminal has uplink data to be transmitted, the terminal processes the uplink data through the DRB corresponding to the uplink data. If the terminal has uplink signaling to be transmitted, the terminal processes the uplink signaling through SRB0.

[0144] Correspondingly, after sending the first message, the first access network device also needs to perform corresponding operations on the corresponding bearer and the protocol entity corresponding to the bearer, that is, the terminal executes S202, and correspondingly, the first access network device executes the following S203.

[0145] S203. The first access network device releases or suspends the dedicated SRB configured for the above-mentioned terminal. The dedicated SRB includes but is not limited to SRB1, SRB2, and SRB3. As a possible implementation, the terminal can transmit signaling with the first access network device through the public SRB (e.g., SRB0). In addition, the first access network device resets the protocol entity corresponding to the DRB configured for the terminal, so that the terminal can transmit uplink data through the DRB.

[0146] It is understandable that the terminal or access network device may perform some or all of the steps in the above embodiments, and these steps or operations are only examples, and the embodiments of the present application may also perform other operations or variations of various operations. In addition, the various steps may be performed in different orders presented in the above embodiments, and it is possible that not all of the operations in the above embodiments need to be performed.

[0147] In the communication method provided in the embodiment of the present application, the terminal receives a first message from the first access network device indicating that the terminal has entered a deactivated state, and then releases or suspends the configured dedicated SRB, and resets the protocol entity corresponding to the configured DRB. It can be seen that in the embodiment of the present application, since the terminal retains and resets the DRB and the corresponding protocol layer entity, after the terminal enters the deactivated state, if there is uplink data to be transmitted, the uplink data can be directly processed through the reset DRB, thereby reducing the service delay of the terminal.

[0148] Combination Figure 2 In the method shown, optionally, in an implementation provided in an embodiment of the present application, the terminal does not immediately enter the deactivated state after receiving the first message, but enters the deactivated state under specific conditions. Based on this, an embodiment of the present application also provides a communication method, such as Figure 4 As shown, the method includes: S401 to S406.

[0149] S401. A first access network device sends a first message to a terminal.

[0150] Correspondingly, the terminal receives the first message sent by the first access network device.

[0151] Among them, the first message is used to instruct the terminal to enter the RRC deactivated state, and the first message carries the identifier and RNA information of the terminal in the RRC deactivated state.

[0152] It can be understood that the first access network device can detect the data transmission status of the terminal. When it is detected that the terminal has not transmitted data for a period of time, the first access network device can send a first message to the terminal to instruct the terminal to enter a deactivated state. Alternatively, the terminal detects its own data transmission status. When it is detected that it has not transmitted data for a period of time, the terminal initiates a request to the first access network device to enter the deactivated state. After receiving the request from the terminal, the first access network device sends a first message to the terminal to instruct the terminal to enter the deactivated state.

[0153] S402: The terminal performs a cell reselection operation.

[0154] After the terminal receives the first message, the terminal performs a cell reselection operation, so that it can reselect to another cell.

[0155] If the terminal reselects to the first cell within a preset time period after receiving the first message, the following S403 is executed.

[0156] The first cell belongs to the cell indicated by the RNA information and is different from the cell where the terminal is located when receiving the first message. Assuming that the cell where the terminal is located when receiving the first message is called the source cell, after cell reselection, the terminal reselects to the first cell, then the first cell and the source cell are not the same cell. The preset duration is used to specify the timing duration of the timer. The preset duration can be set according to the actual application situation. For example, the preset duration can be set to 100ms.

[0157] Alternatively, if the terminal does not reselect to the first cell and does not receive scheduling information within a preset time after receiving the first message, the terminal executes the following step S403 after the preset time. If the terminal receives scheduling information within a preset time after receiving the first message, the terminal executes the following step S404.

[0158] As an exemplary implementation, optionally, the first message described in S401 carries timing information, and the timing information is used to indicate the above-mentioned preset duration. Then, after receiving the first message, the terminal enables the timer and sets the timing duration of the timer to the preset duration carried in the first message. If the terminal does not receive the scheduling information of the first access network device before the timer times out, in order to reduce power consumption, the terminal can execute the process shown in S403 above to enter the deactivated state.

[0159] As another implementation manner, after receiving the first message, the terminal directly activates the timer and sets the timing duration of the timer to a preset duration even if the first message does not carry the timing information.

[0160] S403: The terminal releases or suspends the configured dedicated SRB and resets the protocol entity corresponding to the configured DRB.

[0161] S404. The terminal remains in the RRC connected state.

[0162] It can be understood that if before the timer expires, the terminal receives scheduling information sent by the first access network device, indicating that the terminal has data or signaling transmission requirements, the terminal stops the timer and stops the cell reselection operation, and remains in the RRC connection state, so that the terminal can transmit data or signaling according to the scheduling information sent by the first access network device.

[0163] Correspondingly, after sending the first message, the first access network device also starts the timer. If the first access network device determines that the terminal reselects to the first cell within the preset time after sending the first message (i.e., before the timer times out), the first access network device executes S405. Alternatively, if the first access network device does not send scheduling information to the terminal within the preset time after sending the first message and determines that the terminal does not reselect to the first cell, the first access network device executes the following step S405 after the preset time. If the first access network device sends scheduling information to the terminal within the preset time after sending the first message, the first access network device executes the following step S406.

[0164] S405. The first access network device releases or suspends the dedicated SRB configured corresponding to the terminal, and resets the protocol entity corresponding to the DRB configured corresponding to the terminal.

[0165] S406. The first access network device instructs the terminal to remain in the RRC connected state.

[0166] In the communication method provided by the embodiment of the present application, after receiving the first message sent by the first access network device, the terminal does not immediately enter the deactivated state, but enters the deactivated state only when a specific condition is met, and the specific condition includes: the terminal reselects to the first cell within a preset time after receiving the first message, or the terminal does not reselect to the first cell within a preset time after receiving the first message and does not receive scheduling information. Thus, after the terminal enters the deactivated state, the amount of uplink information (including uplink data and uplink information) sent is reduced, and the power consumption of the terminal is reduced.

[0167] It is understandable that the terminal and the first access network device may perform some or all of the steps in the above embodiments, and these steps or operations are only examples. The embodiments of the present application may also perform other operations or variations of various operations. In addition, the various steps may be performed in different orders presented in the above embodiments, and it is possible that not all operations in the above embodiments need to be performed.

[0168] Combination Figure 2 or Figure 4Correspondingly, if the terminal in the deactivated state moves to a cell covered by the second access network device, it is necessary to re-determine the anchor access network device of the terminal so as to facilitate the exchange of uplink and downlink information between the terminal and the new anchor access network device. Based on this, an embodiment of the present application also provides a communication method, such as Figure 5 As shown, the method includes S501 to S506:

[0169] Among them, S501 to S502 are respectively the same as the above-mentioned S201 and S202, and will not be repeated here.

[0170] S503: If the terminal reselects to a cell covered by the second access network device and there is uplink information to be transmitted, send a second message to the second access network device.

[0171] Correspondingly, the second access network device receives the second message sent by the terminal.

[0172] The reselected cell belongs to the cell indicated by the RNA information, that is, the cell covered by the first access network device and the reselected cell belong to the same RNA.

[0173] Uplink information includes uplink data and uplink signaling. Uplink signaling includes but is not limited to paging response messages, RNA update messages, and TA update messages.

[0174] The second message carries the identifier of the terminal in the RRC deactivated state and information about the reason for triggering the sending of the second message.

[0175] Among them, the identifier in the RRC deactivated state can be I-RNTI. I-RNTI is used to identify the terminal within the cell range indicated by the RNA information. Optionally, the identifier of the terminal in the RRC deactivated state is associated with the first access network device and the architecture of the first access network device. Specifically, the identifier of the terminal in the RRC deactivated state carries the first access network device identifier and information related to whether the first access network device is a CU / DU architecture. The first access network device identifier is used by the second access network device to address the first access network device. The architecture-related information of the first access network device is used by the second access network device to determine whether to migrate the anchor access network device of the terminal.

[0176] The information of the reason for triggering the sending of the second message (referred to as the reason information in this article) includes the reason value for triggering the sending of the second message and other information of the anchor access network device used to determine whether to migrate the terminal. Exemplarily, the reason information may be an uplink cache status report, the service / slice type and QoS category information to which the uplink data belongs, and the network load.

[0177] As an example, if the second message carries QoS category information, and the QoS category information indicates that the terminal is sensitive to transmission delay, then after the second access network device receives the second message, in order to reduce the transmission delay of the terminal, you can choose to migrate the anchor point to the second access network device, and then the second access network device that is closer to the terminal or has better service quality will provide coverage service for the terminal, thereby reducing the transmission delay of the terminal and improving the service quality of the terminal.

[0178] Optionally, the second message also includes a short media access control integrity verification value (Medium Access Control integrity protection, MAC-I), and the short MAC-I is used by the access network device to authenticate the terminal.

[0179] Optionally, the second message also includes uplink data. Exemplarily, the terminal processes the uplink data in the second message through the protocol entity corresponding to the DRB, and the embodiment of the present application does not limit the specific manner of processing the second message.

[0180] Optionally, the second message also includes uplink signaling. Exemplarily, the terminal processes the uplink signaling in the second message through the protocol entity corresponding to SRB0, and the embodiment of the present application does not limit the specific manner of processing the second message.

[0181] Optionally, the second message also includes a state transfer request, where the state transfer request is used by the terminal to request to transfer from the deactivated state to the connected state.

[0182] It should be noted that when the terminal has uplink data or signaling to send to the network, the terminal can send the uplink data or signaling to the access network device through a random access process or agreed resources. For example, the terminal sends the uplink data or signaling to the access network device through the grant-free resource broadcast by the system information. Accordingly, in the embodiment of the present application, the way in which the terminal sends uplink data can be implemented as follows:

[0183] In the first implementation, the terminal needs to perform an RRC state transition first, and then send uplink data to the second access network device. Exemplarily, the terminal may first send a second message containing a state transition request to the second access network device, and then the terminal receives a state transition request response sent by the second access network device. If the state transition response indicates that the second access network device determines that the terminal can be converted from a deactivated state to a connected state, the terminal may send uplink data to the second access network device so that the second access network device processes the uplink data. Alternatively, if the second access network device determines that no migration anchor point is required (the migration anchor point is to migrate the terminal at the entrance of the core network from the first access network device to the second access network device), the second access network device sends the uplink data to the first access network device, and the first access network device processes the uplink data.

[0184] In the second implementation, the RRC state transition and uplink data processing processes can be performed simultaneously. Exemplarily, the terminal can send a second message including a state transition request and uplink data to the second access network device, and the second access network device instructs the terminal to enter a connected state according to the state transition request carried in the second message, and the second access network device processes the uplink data carried in the second message. In the second implementation, since the terminal can send uplink data during the RRC state transition process, the service delay of the terminal is shortened.

[0185] In the third implementation, the terminal can directly send uplink data to the second access network device so that the second access network device processes the uplink data. That is, in the third implementation, the RRC state transition process is reduced, further shortening the service delay of the terminal.

[0186] Among them, the above only takes the second message containing a state transition request, or containing a state transition request and uplink data, or containing uplink data as an example to illustrate the second message in the embodiment of the present application. The specific information contained in the second message can be determined according to the actual application scenario, and the embodiment of the present application is not limited to this.

[0187] Optionally, after the second access network device receives the second message, the second access network device may send a response message to the second message to the terminal.

[0188] Exemplarily, if the second message carries uplink data to be transmitted, the response message of the second message can feedback the transmission status of the uplink data. For example, if the uplink data is successfully transmitted, the second access network device sends a response message of the second message to the terminal, and the response message indicates that the uplink data of the terminal has been successfully transmitted.

[0189] If the second message is a message for initiating a state transition request, after the terminal sends the second message containing the state transition request to the second access network device, the second access network device may send a response message to the terminal indicating the state of the terminal, for example, the response message may indicate that the terminal remains in the RRC deactivated state, or the response message may indicate that the terminal enters the RRC connected state. It is understandable that if the response message of the second message indicates that the terminal remains in the RRC deactivated state, the second access network device may optionally update the context information of the terminal, for example, update the terminal identifier in the deactivated state and / or the RNA information of the terminal.

[0190] S504: The second access network device determines whether it is necessary to migrate the entry of the terminal in the core network from the first access network device to the second access network device.

[0191] If the anchor access network device of the terminal needs to be migrated, S505 and S506 are executed. If the anchor access network device of the terminal does not need to be migrated, the uplink information (if any) is cached and S507 is executed.

[0192] Optionally, the second access network device determines whether to migrate the anchor access network device according to reason information carried in the second message sent by the terminal.

[0193] S505: The second access network device sends a request message for acquiring terminal context information to the first access network device.

[0194] Correspondingly, the first access network device receives the request message sent by the second access network device.

[0195] The request message carries an identifier of the terminal in the RRC deactivated state.

[0196] Optionally, after receiving the second message, the second access network device addresses the first access network device according to the identifier of the terminal in the deactivated state carried in the second message. Exemplarily, the second access network device addresses the first access network device according to the first access network device identifier carried in the identifier of the terminal in the deactivated state.

[0197] S506: The first access network device sends context information of the terminal to the second access network device.

[0198] Correspondingly, the second access network device receives the context information of the terminal sent by the first access network device.

[0199] It can be understood that after receiving the context information of the terminal, the second access network device can generate a protocol entity corresponding to the terminal according to the context information of the terminal, and process the data or signaling of the terminal through the corresponding protocol entity.

[0200] S507: The second access network device sends uplink information to the first access network device.

[0201] Correspondingly, the first access network device receives the uplink information sent by the second access network device.

[0202] As a possible implementation method, after receiving the second message, the second access network device addresses the first access network device according to the identifier of the terminal in the deactivated state carried in the second message. Exemplarily, the second access network device addresses the first access network device according to the first access network device identifier carried in the identifier of the terminal in the deactivated state.

[0203] Optionally, the second access network device sends uplink information in the following format to the first access network device:

[0204] 1. MAC PDU format.

[0205] 2. The format of the combination of {MAC service data unit (SDU), logical channel identity (LCID), I-RNTI, short MAC-I}.

[0206] The format of the uplink information sent by the second access network device to the first access network device is not limited to the two formats listed.

[0207] Optionally, the second access network device may also send reason information corresponding to the uplink information to the first access network device through an interface encapsulation protocol between access network devices. The role of the reason information is described above and will not be repeated here.

[0208] At present, the narrowband Internet of Things (NB-IoT) of 3GPP LTE always needs to migrate the anchor access network device. In the process of migrating the anchor access network device, the second access network device needs to obtain the terminal context information from the first access network device, etc., which increases the signaling overhead and the terminal power consumption. In the communication method provided in the embodiment of the present application, the second access network device can determine whether to migrate the anchor access network device of the terminal according to the reason information in the second message, and only migrate the anchor access network device of the terminal when the condition of migrating the anchor access network device is met. Exemplarily, on the one hand, the embodiment of the present application can not migrate the anchor access network device when transmitting a small amount of data, thereby alleviating the problem of large signaling overhead caused by the transmission of context information between the first access network device and the second access network device. On the other hand, if the anchor access network device of the terminal needs to be migrated, the second access network device provides services for the terminal. Since the second access network device is usually closer to the terminal or has better service quality, the communication quality of the terminal can be improved.

[0209] Combination Figure 2 , Figure 4 and Figure 5 In the corresponding method, optionally, if the second access network device determines not to trigger the migration of the terminal from the first access network device to the second access network device at the entrance of the core network, the first access network device processes the uplink information of the terminal. Based on this, in an implementation method provided in an embodiment of the present application, Figure 6 As shown, in S507, after the second access network device sends the uplink information to the first access network device, the process of the first access network device processing the uplink information of the terminal includes:

[0210] S601. A first access network device processes uplink information of a terminal through a protocol entity corresponding to the uplink information of the terminal.

[0211] Optionally, the format of the uplink information received by the first access network device is as follows:

[0212] 1. MAC PDU format.

[0213] 2. The format of the combination of {MAC SDU, LCID, I-RNTI, short MAC-I}.

[0214] Among them, short MAC-I is the verification information corresponding to the terminal, which is used for the identity authentication of the terminal.

[0215] The second access network device may also send reason information to the first access network device. The function of the reason information is described above and will not be repeated here.

[0216] Optionally, before S601, the identity information of the terminal can be verified to ensure the security of the wireless access network. Specifically, the verification information corresponding to the terminal can be carried in the uplink information. After the first access network device receives the uplink information of the terminal, it authenticates the terminal according to the verification information of the terminal. When the verification is passed, the first access network device processes the uplink information of the terminal through the protocol entity. Exemplarily, the verification information can be the above-mentioned short MAC-I, and the embodiment of the present application does not limit the specific form of the verification information. Optionally, the reason information can also be used to indicate whether to update the access layer security key corresponding to the terminal. It can be understood that if the first access network device determines that the access layer security key of the terminal needs to be updated according to the reason information, the verification information can be updated accordingly, so that the first access network device uses the updated verification information to authenticate the terminal.

[0217] As a possible implementation method, the first access network device can determine the protocol entity corresponding to the uplink information of the terminal based on the LCID carried in the uplink information, and the protocol entity processes the received uplink information in sequence, and then sends the processed uplink information to the core network device, or sends the processed uplink information to the RRC entity, and the RRC entity performs corresponding operations on the processed uplink information.

[0218] Combination Figure 2 , Figures 4 to 6 Corresponding method, optionally, if the second access network device determines to trigger the migration of the terminal from the first access network device to the second access network device at the entrance of the core network, the second access network device should process the uplink information of the terminal. Based on this, in an implementation method provided in an embodiment of the present application, such as Figure 7 As shown, in S506, after the first access network device sends the context information of the terminal to the second access network device, the process of the second access network device processing the uplink information of the terminal includes:

[0219] S701. The second access network device generates a protocol entity corresponding to a DRB of a terminal according to context information of the terminal.

[0220] After receiving the context information of the terminal, the second access network device triggers the path switching process to migrate the terminal's entry in the core network from the initial anchor access network device (i.e., the first access network device) to the second access network device. The detailed process of path switching can be referred to the literature related to 3GPP NR technology.

[0221] After triggering the path switching, the second access network device may generate a protocol entity corresponding to the DRB of the terminal, and may process the uplink information of the terminal through the generated protocol entity.

[0222] Combination Figure 2 , Figures 4 to 7 Corresponding method, the embodiment of the present application also provides a method for determining whether to trigger the migration of the terminal from the first access network device to the second access network device at the entrance of the core network, such as Figure 8 As shown, the method includes S801 to S805:

[0223] S801. A second access network device obtains architecture indication information of a first access network device, wherein the architecture indication information is used to indicate whether the first access network device is an access network device of a CU / DU architecture type.

[0224] As a possible implementation, S801 may be specifically implemented as follows: the first access network device sends architecture indication information to the second access network device. Correspondingly, the second access network device receives the architecture indication information sent by the first access network device.

[0225] Specifically, through the Xn setup process initialized by the Xn interface between base stations, the first access network device sends architecture indication information to the second access network device, or the first access network device updates the architecture indication information through the configuration update (ie, configurationupdate) process and sends the updated architecture indication information to the second access network device.

[0226] S802. The terminal sends a second message to the second access network device.

[0227] The second message has the same function as the second message mentioned above, which will not be described in detail here.

[0228] It should be noted that there is no chronological order between S801 and S802. S801 can be executed first and then S802, or S802 can be executed first and then 801. The embodiments of the present application do not limit this.

[0229] S803. The second access network device determines whether the first access network device is a CU / DU architecture.

[0230] If the first access network device is a CU / DU architecture, execute S804; otherwise, execute S805.

[0231] As a possible implementation manner, the second access network device determines whether the first access network device is a CU / DU architecture based on the architecture indication information sent by the first access network device.

[0232] Alternatively, the second access network device determines whether the first access network device is a CU / DU architecture based on the identifier of the terminal in the RRC deactivated state in the second message. Exemplarily, the identifier of the terminal in the deactivated state may be an I-RNTI, and the I-RNTI may carry information for determining the architecture of the first access network device. For example, the highest 20 bits of the I-RNTI may be used to identify whether the first access network device is a CU / DU architecture. It is understandable that only the highest 20 bits of the I-RNTI are used as identification bits for example here. The specific number of bits and the specific positions of the bits used in the I-RNTI can be determined based on the actual application scenario, and the embodiments of the present application are not limited to this.

[0233] S804: Trigger migration of the terminal's entry in the core network from the first access network device to the second access network device.

[0234] S805. Determine, based on the cause information, whether to trigger migration of the terminal at the entry of the core network from the first access network device to the second access network device.

[0235] The communication method provided in the embodiment of the present application determines whether to migrate the anchor access network device of the terminal according to the architecture of the first access network device. If the first access network device is a CU / DU architecture, the anchor access network device of the terminal is migrated to the second access network device, and the second access network device processes the uplink information of the terminal. Compared with the prior art, when the first access network device of the CU / DU architecture processes the uplink information, signaling overhead needs to be interacted between the CU and the DU, which increases the signaling overhead.

[0236] Combination Figure 2 , Figures 4 to 8 Corresponding method, optionally, in the embodiment of the present application, it is also possible to determine whether to migrate the anchor access network device of the terminal through multiple indicators. Based on this, in another implementation method provided in the embodiment of the present application, such as Fig. 9 As shown, the process of determining whether to migrate the anchor access network device of the terminal may also include the following steps:

[0237] S901. The second access network device determines whether to trigger migration of the terminal at the entrance of the core network from the first access network device to the second access network device based on the cause information and / or the architecture of the first access network device.

[0238] Optionally, when the first access network device is a CU / DU architecture, such as Figure 8 The corresponding method migrates the anchor access network device of the terminal to the second access network device regardless of whether the reason information indicates to migrate the anchor access network device. When the first access network device is a non-CU / DU architecture, further combined with the following Figures 5 to 8 The process shown determines whether to migrate the anchor access network device based on the reason information.

[0239] Alternatively, when the first access network device is a CU / DU architecture and the reason information indicates to migrate the anchor access network device, the anchor access network device of the terminal is migrated to the second access network device.

[0240] It should be noted that since the uplink data is usually in MAC SDU format, and the uplink data in this format usually arrives at the CU of the access network device first, if the following method is adopted Figure 1b The protocol stack segmentation method shown in FIG. 1 (i.e., RLC and lower protocol layers are deployed on DU, and PDCP and higher protocol layers are deployed on CU) requires the CU in the first access network device to send uplink data to DU, and the uplink data is processed by the RLC entity deployed in DU. For example, the RLC entity combines the segmented uplink data and sends the combined data to CU, and the uplink data is processed by the PDCP entity deployed in CU. For example, the PDCP entity decompresses and decrypts the uplink data. It can be seen that in order to realize the processing of uplink data, frequent interactions are required between CU and DU, which will lead to a large processing delay.

[0241] In order to alleviate the problem of processing delay caused by frequent interaction between CU and DU, Figure 2 , Figures 4 to 9 Corresponding method, when the first access network device is a CU / DU architecture (ie, the first access network device includes a CU and a DU), the embodiment of the present application further provides a communication method, such as Fig.10 , the method includes S1001 to S1005:

[0242] S1001. A first access network device sends a first message to a terminal.

[0243] Optionally, the DU in the first access network device sends a first message to the terminal.

[0244] S1002. The terminal releases or suspends the configured dedicated signaling radio bearer (SRB), and resets the protocol entity corresponding to the configured data radio bearer (DRB).

[0245] S1002 may refer to the description of S202 above, which will not be repeated here.

[0246] S1003. The CU in the first access network device sends a third message to the DU.

[0247] Correspondingly, the DU in the first access network device receives the third message sent by the CU.

[0248] The third message includes an identifier of the terminal in the RRC connected state, and the third message is used to instruct the DU to transfer the terminal to the deactivated state. Exemplarily, the identifier of the terminal in the RRC connected state is C-RNTI.

[0249] It should be noted that there is no time sequence between the above S1001 and S1003. For example, the terminal may execute S1001 first and then S1003, or may execute S1001 and S1003 at the same time. This embodiment of the application is not limited to this.

[0250] S1004. The DU of the first access network device releases or suspends the SRB configured corresponding to the terminal, releases or suspends the RLC protocol entity corresponding to the DRB configured corresponding to the terminal, and resets the MAC layer entity.

[0251] Optionally, the first access network device may also reset the PHY entity.

[0252] For example, Fig.11As shown, assuming that the terminal is configured with 4 dedicated radio bearers and 1 public SRB, wherein the 4 dedicated radio bearers are SRB1, SRB2, DRB1, and DRB2, and the public SRB is SRB0, before and after the CU sends the third message to the DU, the protocol stack in the DU is respectively as follows: Fig.11 As shown. Accordingly, the operations performed by the DU may include the following situations: The DU needs to perform:

[0253] First: DU releases or suspends SRB1 and SRB2. Specifically, DU releases or suspends the RLC layer entities corresponding to SRB1 and SRB2. Fig.11 As shown in (a), it is a schematic diagram of DU releasing corresponding bearers and protocol entities, such as Fig.11 (b) is a schematic diagram of DU suspending corresponding bearers and protocol entities.

[0254] Second: DU resets the common MAC layer entity.

[0255] Third: Release or suspend the RLC protocol entity corresponding to the DRB of the terminal. Fig.11 As shown in (a), the RLC protocol entity corresponding to the DRB of the DU release terminal is Fig.11 As shown in (b), the DU suspends the RLC protocol entity corresponding to the DRB of the terminal.

[0256] Optionally, after this step, the DU of the first access network device sends a response message of the third message to the CU to indicate that the DU has processed the bearer and protocol entity of the terminal.

[0257] S1005. The CU of the first access network device releases or suspends the configured SRB and the protocol entity corresponding to the configured SRB in the CU, resets the configured DRB and the protocol entity corresponding to the configured DRB in the CU, and generates the RLC protocol entity corresponding to the DRB of the terminal.

[0258] Optionally, the CU performs this step after receiving a response message to the third message sent by the DU, or the CU may also directly perform this step after sending the third message. The embodiment of the present application is not limited to this.

[0259] Exemplarily, the CU performs the following operations:

[0260] First: CU releases or suspends SRB1 and SRB2. Specifically, CU releases the RRC layer and PDCP layer entities corresponding to SRB1 and SRB2. Fig.11 As shown in (a), it is a schematic diagram of the terminal protocol stack before and after the CU releases the protocol entities corresponding to SRB1 and SRB2 of the terminal, as shown in FIG. Fig.11(b) is a schematic diagram of the terminal protocol stack before and after the CU suspends the protocol entities corresponding to SRB1 and SRB2 of the terminal.

[0261] Accordingly, the terminal may process the uplink signaling to be transmitted through the RRC layer entity corresponding to SRB0, and transmit the processed uplink signaling through SRB0.

[0262] Second: CU resets the PDCP layer entities corresponding to DRB1 and DRB2 and resets the configured SDAP layer entity. In addition, it generates the RLC entity corresponding to the DRB of the terminal, so that when the terminal has uplink data transmission requirements, the uplink data can be processed by the entities of the SDAP layer, PDCP layer and RLC layer in turn.

[0263] The communication method provided in the embodiment of the present application deploys the RLC protocol entity corresponding to the DRB of the terminal on the CU after the terminal enters the deactivated state, and releases or suspends the RLC protocol entity corresponding to the terminal on the DU, so that when uplink data arrives, the CU in the first access network device can process the uplink data in the MAC SDU format through the deployed RLC protocol entity, and then send the processed uplink data to the PDCP and SDAP entities in sequence for processing, without the need for frequent interactions with the DU, thereby reducing processing delay.

[0264] It can be understood that the message names involved in the embodiments of the present application are only for the convenience of description. In the specific implementation, other message names may be used. The various information listed in the embodiments of the present application may be sent simultaneously, such as in one message, or may be sent at different times, such as in different messages.

[0265] Above Figure 2 , Figures 4 to 11 In each method embodiment, access network equipment and terminals are used as examples for explanation. It can be understood that the methods and functions implemented by the access network equipment in the above method embodiments can also be implemented by a chip that can be used for the access network equipment, and the methods and functions implemented by the terminal can also be implemented by a chip that can be used for the terminal.

[0266] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between different network elements. It can be understood that in order to realize the above functions, the network side equipment (including but not limited to the first access network equipment and the second access network equipment) and the terminal include hardware structures and / or software modules corresponding to the execution of each function. In combination with the units and algorithm steps of each example described in the embodiments disclosed in this application, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may 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 technical solution of the embodiment of the present application.

[0267] The embodiments of the present application can divide the network side devices and terminals into functional units according to the above method examples. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0268] Fig.12 1200 is a schematic block diagram of a communication device provided in an embodiment of the present application. The communication device 1200 may exist in the form of software, or may be a terminal, or may be a chip that can be used for a terminal. The device 1200 includes: a processing unit 1202 and a communication unit 1203. For example, the processing unit 1202 may be used to support the device 1200 to execute Figure 2 S201 in Figure 5 S503 in the embodiment, and / or other processes of the solution described herein. The communication unit 1203 is used to support communication between the apparatus 1200 and other network elements (eg, network side devices).

[0269] Optionally, the communication device 1200 may further include a storage unit 1201 for storing program codes and data of the device 1200, where the data may include but is not limited to original data or intermediate data.

[0270] In one possible manner, the processing unit 1202 may be a processor or a controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements a computing function, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The communication unit 1203 may be a transceiver, a transceiver circuit or a communication interface, and the like. The storage unit 1201 may be a memory.

[0271] In one possible manner, when the processing unit 1202 is a processor, the communication unit 1203 is a transceiver, and the storage unit 1201 is a memory, the terminal involved in the embodiment of the present application can be Fig.13 Terminal shown.

[0272] Fig.13 The simplified schematic diagram of a possible design structure of a terminal involved in the embodiment of the present application is shown. The terminal 1300 includes a transmitter 1301, a receiver 1302 and a processor 1303. The processor 1303 may also be a controller. Fig.13 1303 . Optionally, the terminal 1300 may further include a modem processor 1305 , wherein the modem processor 1305 may include an encoder 1306 , a modulator 1307 , a decoder 1308 and a demodulator 1309 .

[0273] In one example, the transmitter 1301 adjusts (e.g., analog conversion, filtering, amplification, up-conversion, etc.) the output sample and generates an uplink signal, which is transmitted to the base station described in the above embodiment via an antenna. On the downlink, the antenna receives the downlink signal transmitted by the base station in the above embodiment. The receiver 1302 adjusts (e.g., filters, amplifies, down-converts, and digitizes) the signal received from the antenna and provides input samples. In the modem processor 1305, the encoder 1306 receives the service data and signaling message to be sent on the uplink, and processes the service data and signaling message (e.g., formatting, encoding, and interleaving). The modulator 1307 further processes (e.g., symbol mapping and modulation) the encoded service data and signaling message and provides output samples. The demodulator 1309 processes (e.g., demodulates) the input sample and provides symbol estimation. The decoder 1308 processes (e.g., deinterleaves and decodes) the symbol estimation and provides decoded data and signaling messages sent to the terminal 1300. The encoder 1306, modulator 1307, demodulator 1309 and decoder 1308 can be implemented by the synthesized modem processor 1305. These units perform processing according to the radio access technology (e.g., LTE and other access technologies of evolved systems) adopted by the radio access network. It should be noted that when the terminal 1300 does not include the modem processor 1305, the above functions of the modem processor 1305 can also be completed by the processor 1303.

[0274] The processor 1303 controls and manages the actions of the terminal 1300, and is used to execute the processing performed by the terminal 1300 in the above-mentioned embodiment of the present application. For example, the processor 1303 is also used to execute Figure 2 , Figures 4 to 6 The method shown involves the processing process of the terminal and / or other processes of the technical solution described in this application.

[0275] Furthermore, the terminal 1300 may also include a memory 1304 , and the memory 1304 is used to store program codes and data for the terminal 1300 .

[0276] Fig.14 A possible exemplary block diagram of another communication device involved in the embodiments of the present application is shown. The device 1400 can exist in the form of software, or can be a network-side device, such as a base station, or can be a chip that can be used for a network-side device. The device 1400 includes: a processing unit 1402 and a communication unit 1403. The processing unit 1402 is used to control and manage the actions of the device 1400. For example, if the device is a first access network device, the processing unit 1402 is used to support the device 1400 to execute Figure 2 S203 in Figure 4If the device is a second access network device, the processing unit 1402 is used to support the device 1400 to execute Figure 5 S504, S505, S507, Figure 7 S701 in, and / or other processes for the technology described herein. The communication unit 1403 is used to support the communication between the device 1400 and other network entities (such as terminals). The device 1400 may also include a storage unit 1401 for storing program codes and data of the device 1400.

[0277] Among them, the processing unit 1402 can be a processor or a controller, for example, it can be a CPU, a general processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication unit 1403 can be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a general term. In a specific implementation, the communication interface can include multiple interfaces, for example, it can include: an interface between a base station and a terminal and / or other interfaces. The storage unit 1401 can be a memory.

[0278] When the processing unit 1402 is a processor, the communication unit 1403 is a communication interface, and the storage unit 1401 is a memory, the device 1400 involved in the embodiment of the present application can be Fig.15 The base station shown.

[0279] See also Fig.15 As shown, the base station 1500 includes: a processor 1502, a communication interface 1503, and a memory 1501. Optionally, the base station 1500 may also include a bus 1504. The communication interface 1503, the processor 1502, and the memory 1501 may be interconnected via the bus 1504; the bus 1504 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus 1504 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.15 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0280] It will be appreciated by those skilled in the art that in the above embodiments, the embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, the embodiments may 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 process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may 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 may be transmitted from a website site, computer, server, or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0281] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical or other forms.

[0282] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network devices. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0283] In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, or each functional unit can exist independently, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0284] Through the description of the above implementation methods, the technicians in the relevant field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, hard disk or optical disk, etc., and includes a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0285] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: Acquire information about the reason why the terminal triggers sending the second message in a radio resource control (RRC) deactivated state; Determine whether to migrate the anchor access network device of the terminal according to the reason information, the anchor access network device being an access network device that maintains the context of the terminal.

2. The method according to claim 1, characterized in that The acquiring of the reason information of the terminal triggering the sending of the second message includes: The second message is received from the terminal, where the second message carries an identifier of the terminal in the RRC deactivated state and reason information for triggering sending the second message.

3. The method according to claim 1 or 2, characterized in that: The reason information includes at least one of the following: uplink cache status report, service / slice type and quality of service QoS category information to which the uplink data belongs, and network load.

4. The method according to claim 1 or 2, characterized in that: The second message also includes uplink data.

5. The method according to claim 1 or 2, characterized in that: The second message also includes uplink signaling.

6. The method according to claim 1 or 2, characterized in that: The second message also includes a state transfer request, where the state transfer request is used to request a transfer from the deactivated state to the connected state.

7. A communication device, characterized in that: The method comprises modules for implementing the method as claimed in any one of claims 1 to 6.

8. A readable storage medium, characterized in that: A program or instruction is stored thereon, and when the program or instruction is executed, the method according to any one of claims 1 to 6 is implemented.

9. A computer program product, characterized in that When it is run on a computer, the method according to any one of claims 1 to 6 is implemented.

Citation Information

Patent Citations

  • Method for paging and connecting terminal and terminal and system for fast activating data transmission

    CN101115292A

  • Data sending method and device, and data transmission method and device

    CN107645779A