WO2019166032A1 - 通信方法及装置 - Google Patents
通信方法及装置 Download PDFInfo
- Publication number
- WO2019166032A1 WO2019166032A1 PCT/CN2019/082443 CN2019082443W WO2019166032A1 WO 2019166032 A1 WO2019166032 A1 WO 2019166032A1 CN 2019082443 W CN2019082443 W CN 2019082443W WO 2019166032 A1 WO2019166032 A1 WO 2019166032A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- access network
- network device
- terminal
- entity
- message
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 184
- 238000004891 communication Methods 0.000 title claims abstract description 81
- 230000011664 signaling Effects 0.000 claims abstract description 59
- 230000008569 process Effects 0.000 claims description 63
- 230000005012 migration Effects 0.000 claims description 19
- 238000013508 migration Methods 0.000 claims description 19
- 230000004044 response Effects 0.000 claims description 17
- 238000012795 verification Methods 0.000 claims description 16
- 230000009849 deactivation Effects 0.000 claims description 13
- 230000001934 delay Effects 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 42
- 238000012545 processing Methods 0.000 description 26
- 238000013461 design Methods 0.000 description 25
- 230000005540 biological transmission Effects 0.000 description 21
- 238000010586 diagram Methods 0.000 description 16
- 238000005516 engineering process Methods 0.000 description 16
- 101001055444 Homo sapiens Mediator of RNA polymerase II transcription subunit 20 Proteins 0.000 description 15
- 102100026165 Mediator of RNA polymerase II transcription subunit 20 Human genes 0.000 description 15
- 108091005487 SCARB1 Proteins 0.000 description 15
- 102100037118 Scavenger receptor class B member 1 Human genes 0.000 description 15
- 230000007704 transition Effects 0.000 description 14
- 101150090033 DRB2 gene Proteins 0.000 description 8
- 101001100327 Homo sapiens RNA-binding protein 45 Proteins 0.000 description 8
- 101100117568 Oryza sativa subsp. japonica DRB5 gene Proteins 0.000 description 8
- 102100038823 RNA-binding protein 45 Human genes 0.000 description 8
- 230000003993 interaction Effects 0.000 description 8
- 230000008878 coupling Effects 0.000 description 6
- 238000010168 coupling process Methods 0.000 description 6
- 238000005859 coupling reaction Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 101100150275 Caenorhabditis elegans srb-3 gene Proteins 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 239000002131 composite material Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W68/005—Transmission of information for alerting of incoming communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/34—Selective release of ongoing connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/38—Connection release triggered by timers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/02—Data link layer protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/20—Selecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
Definitions
- the present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.
- the inactive state is a Radio Resource Control (RRC) state introduced in the 3rd Generation Partnership Project (3GPP) New Radio (NR) technology.
- RRC Radio Resource Control
- the terminal disconnects the RRC connection of the air interface with the access network device, and the terminal receives downlink data, downlink signaling, etc. at the agreed time-frequency location, for example, the terminal can receive the access.
- 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.
- RNA can be used for mobility management of terminals.
- the present invention provides a communication method and device, which can solve the problem of service delay caused by the inability of the deactivated terminal to directly send uplink data.
- an embodiment of the present application provides a communication method, which may be implemented by a terminal or a chip applicable to a terminal, the method comprising: receiving a first message from a first access network device, and then releasing or suspending the configuration
- the first message is used to indicate that the terminal enters an RRC deactivation state, and the first message carries the identifier of the terminal in the RRC deactivated state and the RNA information.
- the terminal may receive a first message indicating the entry of the deactivated state from the first access network device, 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 can be directly processed by the reset DRB. Data, thereby reducing the service delay of the terminal.
- the embodiments of the present application can be applied to NR and other types of radio access networks.
- the protocol entity corresponding to the DRB includes a packet data convergence protocol (packet).
- PDCP data convergence protocol
- RLC radio link control
- MAC common medium access control
- the entity of the SDB layer and the SDAP layer exists in the NR technology, and the protocol entity corresponding to the DRB includes the entities of the PDCP, RLC, MAC, and SDAP layers.
- the terminal performs a reset operation, the entities of the PDCP, RLC, MAC, and SDAP layers need to be reset.
- the embodiment of the present application is mainly applied to the NR technology, that is, an entity that includes a PDCP, an RLC, a MAC, and a SDAP layer in the protocol entity corresponding to the DRB is taken as an example.
- the first message carries timing information, and the timing information is used to indicate a preset duration.
- releasing or suspending the configured dedicated SRB and resetting the configured protocol entity of the DRB may be implemented as follows: if the scheduled information is not received within the preset duration after receiving the first message, Then, after the preset duration, the configured dedicated SRB and the corresponding protocol layer entity, the dedicated DRB of the reset configuration, and the corresponding protocol layer entity are released or suspended.
- the specific implementation may be implemented as follows: If the scheduling information is not received within the preset duration after a message, the configured dedicated SRB and the corresponding protocol layer entity are released or suspended, and the configured PDCP, RLC, and MAC layer entities are reset.
- releasing or suspending the configured dedicated SRB, and resetting the protocol entity corresponding to the configured DRB may be implemented as follows: after receiving the first message, If the scheduling information is not received within the preset duration, the configured dedicated SRB and the corresponding protocol layer entity are released or suspended, and the PDCP, RLC, MAC, and SDAP layer entities of the configuration are reset.
- the preset duration may also be a pre-stored time value in the terminal.
- releasing or suspending the configured dedicated SRB and the corresponding protocol layer entity, the dedicated DRB of the reset configuration, and the corresponding protocol layer entity may also be implemented as:
- 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 in which the first message is received.
- the terminal 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 after the specific condition is met, and the specific condition includes: the terminal is receiving The device is reselected to the first cell within a preset duration after the first message, or the terminal does not reselect to the first cell within the preset duration after receiving the first message. Therefore, after the terminal enters the deactivated state, the transmission amount of the uplink information (including the uplink data and the uplink information) is reduced, and the power consumption of the terminal is reduced.
- the uplink data is transmitted through the DRB corresponding to the uplink data, or if there is an uplink signaling to be transmitted, the uplink signaling is transmitted through the public signaling radio bearer.
- the configured dedicated SRB and the corresponding protocol layer entity are released or suspended according to the first message, the following:
- the second message is sent to the second access network device.
- the second message carries the identifier of the terminal in the RRC deactivated state and the information that triggers the reason for sending the second message.
- the reselected cell belongs to the cell indicated by the RNA information. If the cell covered by the first access network device where the terminal initially camps is called the source cell, the reselected cell and the source cell belong to the cell indicated by the same RNA.
- the identity of the terminal in the RRC deactivation state is associated with the architecture of the first access network device and the first access network device.
- the identifier of the terminal in the RRC deactivated state may carry the first access network device identifier and whether the first access network device is a Central Unit (CU)/Distributed Unit (DU) architecture. information.
- the second access network device may address the first access network device according to the identifier of the first access network device.
- the second access network device may determine, according to the CU/DU architecture of the first access network device, whether to migrate the anchor of the terminal to access the network device.
- the terminal may send a second message to the second access network device to trigger the second access network device to determine. Whether to migrate the action of the anchor of the terminal to access the network device.
- the second access network device may determine, according to the information that triggers the reason for sending the second message (also referred to herein as the cause information) and/or the architecture of the first access network device, whether to migrate the anchor access network of the terminal. device.
- the anchor access network device of the terminal is migrated only when the triggering condition of the migration anchor access network device is met, thereby avoiding the problem of large signaling overhead caused by frequent migration of the anchor point, while saving signaling overhead. It can also reduce the power consumption of the terminal.
- an embodiment of the present application provides a communication method, which may be implemented by a first access network device or a chip that can be used by a first access network device, where the method includes: the first access network device to the terminal The first message is sent, and then the first access network device releases or suspends the dedicated signaling radio bearer SRB corresponding to the terminal and the protocol entity corresponding to the data radio bearer DRB corresponding to the reset terminal.
- the first message is used to indicate that the terminal enters the radio resource control RRC deactivation 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.
- the first access network device sends a first message for instructing the terminal to enter the deactivated state, then releases or suspends the configured dedicated SRB, and resets the configured protocol entity corresponding to the 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 can be directly processed by the reset DRB. Data, thereby reducing the service delay of the terminal.
- the protocol entity corresponding to the DRB includes 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.
- the first access network device releases or suspends the dedicated SRB configured corresponding to the terminal, and the protocol entity corresponding to the DRB corresponding to the reset terminal, which may be implemented as follows: after the first message is sent The scheduling information is not sent to the terminal within the preset duration, and the dedicated SRB corresponding to the terminal and the protocol entity corresponding to the DRB corresponding to the reset terminal are released or suspended after the preset duration.
- the first access network device releases or suspends the dedicated SRB corresponding to the terminal, and the protocol entity corresponding to the DRB corresponding to the reset terminal, and may also be implemented as: After the device sends the first message, the terminal reselects to the first cell, and then releases or suspends the dedicated SRB corresponding to the terminal and the protocol entity corresponding to the DRB corresponding to the reset terminal. In other words, within a preset duration, the terminal reselecting to the first cell may also trigger the process of entering the deactivated state.
- the preset time length may be set. Before the preset time length is reached, if the terminal reselects to the first cell, the first access network device may indicate the terminal. Enter the deactivated state. Alternatively, if the terminal does not reselect to the first cell and does not receive the scheduling information within the preset duration after receiving the first message, the terminal may instruct the terminal to enter the deactivated state. Therefore, after the terminal is instructed to enter the deactivated state, the transmission amount of the terminal uplink information (the uplink information includes the uplink data and the uplink information) is reduced, and the power consumption of the terminal is reduced.
- the terminal uplink information includes the uplink data and the uplink information
- the first access network device if the first access network device includes the CU and the DU, the first access network device sends the first message to the terminal, which may be implemented by: the first access network device sends the terminal to the terminal through the DU. The first message.
- 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 radio bearer of the terminal.
- the determining the configuration of the radio bearer of the terminal may be implemented by: releasing or suspending the configured SRB corresponding to the terminal and the configured protocol entity of the SRB in the DU, releasing or suspending the configuration corresponding to the terminal.
- the radio link corresponding to the DRB controls the RLC protocol entity and the entity that resets the common medium access control layer.
- the CU of the first access network device releases or suspends the configured SRB and the configured SRB in the CU corresponding to the protocol entity and the reset configuration.
- the DRB and the configured DRB are corresponding to the protocol entity in the CU, and the DRB corresponding RLC protocol entity is generated.
- the DU after the DU determines the related configuration of the radio bearer of the terminal, the DU sends a response message of the third message to the CU, and after receiving the response message of the third message, the CU releases or suspends the configured SRB and the configured SRB in the CU.
- the corresponding protocol entity, the DRB of the reset configuration, and the corresponding protocol entity of the configured DRB in the CU, and the DRB corresponding RLC protocol entity are examples of the configuration of the radio bearer of the terminal.
- the third message includes the identifier of the terminal in the RRC connected state.
- 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 radio bearer and protocol entity of the terminal.
- 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, so that when the uplink data arrives, the first
- the CU in the 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 the SDAP entity for processing, without frequent interaction with the DU, thereby reducing Handling delays.
- the first access network device receives the second The uplink information of the terminal forwarded by the access network device, and then the first access network device processes the uplink information by using a protocol entity corresponding to the uplink information of the terminal.
- the uplink information carries the identifier of the terminal in the RRC deactivated state.
- the first access network device completes data or signaling interaction with the terminal, thereby avoiding signaling caused by frequent migration of the anchor access network device.
- the problem of large overhead can also reduce the power consumption of the terminal.
- the uplink information carries the verification information corresponding to the terminal.
- the first access network device performs identity verification on the terminal according to the verification information, and after the verification is passed, the first access network device processes the protocol through the protocol entity. Uplink information.
- the uplink information carries the cause information.
- the first access network device may determine, according to the cause information, whether to update the access layer security key corresponding to the terminal.
- the first access network device may receive the second connection.
- the request message carries the identifier of the terminal in the RRC deactivated state.
- the second access network device provides the coverage service for the terminal, because the second access network device is usually closer to the terminal or the service quality is better, thereby Can improve the communication quality of the terminal.
- the first access network device may further send: the first access network device sends the second access network device to the second access network device.
- Architecture instructions is used to indicate whether the first access network device is an access network device of a CU/DU architecture type.
- the first access network device sends the architecture indication information to the second access network device, to indicate that the second access network device determines, according to the architecture of the first access network device, whether to migrate the anchor access network device of the terminal. 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.
- an embodiment of the present application provides a communication method, which may be implemented by a second access network device or a chip applicable to a second access network device, where the method includes: receiving, by a second access network device, a terminal Sending a second message, if the second access network device determines, according to the information that triggers the reason for sending the second message, triggering the migration of the terminal at the core network from the first access network device to the second access network device, The second access network device sends a request message for acquiring the terminal context information to the first access network device, and then the second access network device receives the context information of the terminal sent by the first access network device.
- the second message carries the identifier of the terminal in the radio resource control RRC deactivation state and the information that triggers the reason for sending the second message.
- the second access network device can receive the second message sent by the terminal, and determine, according to the cause information in the second message, whether to migrate the anchor point access network device of the terminal, and further, only if the migration anchor point is met. Under the trigger condition of the network device, the anchor access network device of the terminal is migrated, which avoids the problem of large signaling overhead caused by frequent migration of the anchor point, and saves signaling overhead, and can also reduce the power consumption of the terminal.
- the second access network device may further generate a DRB corresponding to the terminal according to the context information of the terminal. Agreement entity.
- the second access network device processes the uplink information of the terminal to provide an coverage service for the terminal, because the second access network device is usually closer to the terminal or The quality of service is better, and thus, the communication quality of the terminal can be improved.
- the protocol entity corresponding to the DRB includes a PDCP entity, an RLC entity, a public MAC entity, and a SDAP entity, or the protocol entity corresponding to the DRB includes a PDCP entity, an RLC entity, and a public MAC entity.
- the cause information includes: an uplink buffer status report, a service/slice type and quality of service QoS category information to which the uplink data belongs, and a network load.
- the second access network device determines whether the first access network device is a centralized unit CU/distribution unit DU architecture, and if the first access network device is a CU/DU architecture, The trigger migrates the terminal at the entrance of the core network from the first access network device to the second access network device.
- the anchor point of the terminal is migrated to the second access network device, and the second access network device processes the uplink of the terminal.
- Information reducing signaling overhead.
- the second access network device determines whether the first access network device is a CU/DU architecture, and may be implemented by: the second access network device acquiring the architecture indication sent by the first access network device. Information, then, the second access network device determines, according to the architecture indication information, whether the first access network device is a CU/DU architecture.
- the second access network device obtains the architecture indication information of the first access network device, where the first access network device sends the architecture indication information to the second access network device, and correspondingly, the second The access network device receives the architecture indication information.
- the second access network device determines whether the first access network device is a CU/DU architecture, and the second access network device determines whether the first access network device is determined according to the identifier of the terminal in the RRC deactivated state. CU/DU architecture.
- the second access network device determines, according to the reason information, that the terminal is not migrating 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.
- the first access network device is instructed to process the uplink information of the terminal to complete data or signaling interaction with the terminal, thereby avoiding
- the problem of large signaling overhead caused by frequent migration of the anchor access network device can also reduce the power consumption of the terminal.
- an embodiment of the present application provides a communication device, which has the function of implementing the method described in the foregoing first aspect.
- the functions may be implemented by hardware or by corresponding software implemented by hardware.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the device can be a terminal or can be a chip that can be used for a terminal.
- the device is a terminal, and the terminal includes a processor configured to support the terminal to perform a corresponding function in the above method. Further, the terminal may further include a transmitter and a receiver for supporting communication between the terminal and the network side device. Further, the terminal may further include a memory for coupling with the processor, which stores program instructions and data necessary for the terminal.
- the network side devices include, but are not limited to, a first access network device and a second access network device.
- 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 functions may be implemented by hardware or by corresponding software implemented by hardware.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the device can be a base station or can be a chip that can be used for a base station.
- the apparatus is a base station, and the base station includes a processor configured to support the base station to perform corresponding functions in the above methods. Further, the base station may further include a transmitter and a receiver for supporting communication between the base station and the terminal. Further, the base station may further include a memory for coupling with the processor, which stores necessary program instructions and data of the base station.
- the embodiment of the present application provides a communication device, which has the function of implementing the method described in the foregoing third aspect.
- the functions may be implemented by hardware or by corresponding software implemented by hardware.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the device can be a base station or can be a chip that can be used for a base station.
- the apparatus is a base station, and the base station includes a processor configured to support the base station to perform corresponding functions in the above methods. Further, the base station may further include a transmitter and a receiver for supporting communication between the base station and the terminal, or supporting communication between the base stations. Further, the base station can also include a memory for coupling with the processor that stores the necessary program instructions and data for the base station.
- the embodiment of the present application provides a communication system, where the system includes the terminal, the first access network device, and the second access network device.
- an embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores instructions, when executed on a computer, causing the computer to perform the first aspect or the second aspect or the The method described in three aspects.
- an embodiment of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect or the second or third aspect described above.
- an embodiment of the present application provides a chip system, which is applied to a terminal, where the chip system includes at least one processor, a memory and an interface circuit, the memory, the transceiver, and the at least one processor An instruction is stored in the at least one memory by a line interconnect; the instructions are executed by the processor to perform the method of the first aspect described above.
- an embodiment of the present application provides a chip system, which is applied to a network side device, and is exemplarily applied to a first access network device, where the chip system includes at least one processor, a memory, and an interface. a circuit, the memory, the transceiver, and the at least one processor are interconnected by a line, the at least one memory storing instructions; the instructions being executed by the processor to perform the second aspect described above method.
- an embodiment of the present application provides a chip system, which is applied to a network side device, and is exemplarily applied to a second access network device, where the chip system includes at least one processor, a memory, and an interface. a circuit, the memory, the transceiver, and the at least one processor are interconnected by a line, the at least one memory storing instructions; the instructions being executed by the processor to perform the method of the third aspect described above method.
- the terminal receives, from the first access network device, a first message for indicating to enter the deactivated state, and then releases or suspends the configured dedicated SRB, and resets the configured protocol entity corresponding to the DRB. That is, the embodiment of the present application provides a DRB that can be used to directly process the uplink data, so that when the terminal has uplink data to be transmitted, the uplink data can be directly processed by the reset DRB, and the service delay of the terminal is reduced.
- FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application.
- FIG. 1b is a schematic structural diagram of a base station according to an embodiment of the present application.
- FIG. 2 is a flowchart of a communication method according to an embodiment of the present application.
- FIG. 3 is a schematic diagram of a protocol stack provided by an embodiment of the present application.
- FIG. 5 is a flowchart of a communication method according to an embodiment of the present application.
- FIG. 6 is a flowchart of a communication method according to an embodiment of the present application.
- FIG. 7 is a flowchart of a communication method according to an embodiment of the present application.
- FIG. 8 is a flowchart of a communication method according to an embodiment of the present application.
- FIG. 9 is a flowchart of a communication method according to an embodiment of the present application.
- FIG. 10 is a flowchart of a communication method according to an embodiment of the present application.
- FIG. 11 is a schematic diagram of a protocol stack according to an embodiment of the present application.
- FIG. 12 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
- FIG. 13 is a schematic structural diagram of a terminal according to an embodiment of the present application.
- FIG. 14 is a schematic structural diagram of a communication apparatus according to an embodiment of the present disclosure.
- FIG. 15 is a schematic structural diagram of a base station according to an embodiment of the present application.
- Embodiments of the present application are applied to NR and other types of radio access networks.
- FIG. 1a shows a schematic diagram of a possible communication system of the present application, which may include at least one core network device (only one is shown in the figure), which communicates with the core network device and the terminal.
- the core network device referred to in the present application is a device deployed in the core network to provide services for the terminal.
- the core network devices referred to in this application include, but are not limited to, Access and Mobility Management Function (AMF), Session Management Function (SMF), and User Plane Function (UPF). , Policy and Charging Rules Function (PCRF, and their combined devices).
- AMF Access and Mobility Management Function
- SMF Session Management Function
- UPF User Plane Function
- PCRF Policy and Charging Rules Function
- core network devices are collectively referred to as core network devices.
- An access network device which is referred to in the present application, is a device deployed in a radio access network to provide a wireless communication function for a terminal.
- the access network device referred to in this application includes but is not limited to: various forms of macro base stations. , micro base station (also known as small station), relay station, transmission reception point (TRP), next generation network node (g Node B, gNB), and evolved node B (ng evolved Node) connected to the next generation core network B, ng-eNB), etc., may also include a wireless access network device of a non-3GPP system such as a wireless local area network (WLAN) access device.
- WLAN wireless local area network
- the names of wireless access network devices with similar wireless communication capabilities may vary.
- the foregoing devices that can provide wireless communication functions for terminals are collectively referred to as access network devices.
- the terminal referred to in the present application is a device with wireless transceiver function, which can be deployed on land, indoors or outdoors, hand-held or on-board; it can also be deployed on the water surface (such as a ship); it can also be deployed in the air ( Such as airplanes, balloons and satellites, etc.).
- the terminal may include various types of mobile phones, tablets, computers with wireless transceiver functions, wireless data cards, virtual reality (VR) terminal devices, and augmented reality (AR).
- Terminal equipment terminal equipment of machine type communication (MTC), terminal equipment in industrial control, terminal equipment in self driving, terminal equipment in remote medical , terminal equipment in the smart grid, terminal equipment in transport safety, terminal equipment in smart city, and wearable devices (such as smart watches, smart bracelets, pedometers) wait wait wait.
- MTC machine type communication
- terminal equipment in industrial control terminal equipment in self driving
- terminal equipment in remote medical terminal equipment in the smart grid
- terminal equipment in transport safety terminal equipment in smart city
- wearable devices such as smart watches, smart bracelets, pedometers
- the devices having the wireless communication function are collectively referred to as terminals. .
- 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 can be understood that the access network device and the core network device can communicate with each other through other types of interfaces. Similarly, the access network devices can communicate with each other through other types of interfaces. Make restrictions.
- the access network device in this embodiment of the present application is described below by taking a base station as an example.
- the base station may be composed of a centralized unit (CU) and a distributed unit (DU), and one CU may be connected to one DU, or may be multiple DUs. Sharing a single CU saves costs and makes network expansion easy.
- the severing of the CU and the DU can be performed according to the protocol stack.
- One possible way is to deploy radio resource control (RRC), Service Data Adaptation Protocol (SDAP), and PDCP layer in the CU.
- RRC radio resource control
- SDAP Service Data Adaptation Protocol
- PDCP layer The remaining RLC layer, the MAC layer, and the physical layer (PHY layer) are deployed in the DU.
- the foregoing protocol stack splitting manner is not completely limited, and other splitting manners may also be used.
- the network device is, for example, the architecture of the CU and the DU of FIG. 1b
- the embodiment of the present application may refer to a CU, or may be a DU, or a system composed of a CU and a DU, depending on the specific For the corresponding implementation functions.
- the base station mentioned in the embodiment of the present application is not limited to the form of FIG. 1b, and may be any device that provides deployment in the radio access network to provide wireless communication functions for the terminal.
- the method in the embodiment of the present application is mainly applied to a radio access network, that is, the method in the embodiment of the present application is mainly applied to an access network system formed by 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.
- the context information of the terminal which is used to characterize all the information about the identity, background and status of the terminal.
- the context information of the terminal includes, but is not limited to, location information of the terminal, terminal identifier, and dedicated radio bearer configuration information.
- the access network device may generate a protocol entity corresponding to the terminal according to the context information of the terminal, and process data or signaling of the terminal by using a corresponding protocol entity.
- the anchor accesses the network device and maintains the context of the terminal.
- the situation that the migration anchor accesses the network device may occur when the terminal moves.
- 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, and then the terminal changes its location, and the current serving access network device is the second access network.
- the device if it is determined that the terminal 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 is transmitted to the second access network device. So that the second access network device processes the data or signaling of the terminal according to the acquired terminal context information, and interacts with the terminal.
- an embodiment of the present application provides a communication method. As shown in FIG. 2, the method includes:
- the first access network device sends a first message to the terminal.
- the terminal receives the first message sent by the first access network device.
- the first message is used to indicate that the terminal enters an RRC deactivation state, and the first message carries the identifier of the terminal in the RRC deactivated state and the RNA information.
- the identifier of the terminal in the RRC deactivated state may be an inactive-Radio Network Temporary Identifier (I-RNTI) of the terminal, where the RNA information is used to indicate the RNA, and may be used by the access network device.
- I-RNTI inactive-Radio Network Temporary Identifier
- an RNA typically includes at least one cell.
- the RNA information can be a list of cell identities. It can be understood that, when the location of the terminal changes, if the current location of the terminal is within the range of the RNA, the terminal may not send the current location information to the access network device, if the terminal currently removes the RNA included Within the scope, in order to manage the terminal location, the terminal needs to send the current location information to the access network device.
- the terminal also needs to send the current location information to the access network device.
- the cell covered by the first access network device is the cell 1 to the cell 3
- the cell covered by the second access network device is the cell 4 to the cell 5
- the terminal is initially connected to the cell 1 of the first access network device.
- the first access network device allocates RNA_1 to the terminal, and the RNA_1 includes the cell 1 to the cell 3.
- the terminal may The current location information is not reported to the access network device.
- the terminal moves to the cell 4 or the cell 5 or the cell 6, the terminal needs to report the current location information to the access network device because the terminal has moved out of the range covered by the RNA_1.
- the first access network device can detect the data transmission situation of the terminal. When detecting that the terminal does not have data transmission for a period of time, the first access network device can send a first message to the terminal to indicate that the terminal enters. Deactivated, or the terminal detects its own data transmission. When it detects that there is no data transmission within a certain period of time, the terminal initiates a request to enter the deactivation state to the first access network device, and the first access network device receives After the terminal's request, the first message is sent to the terminal to instruct the terminal to enter the deactivated state.
- the first access network device when the first access network device is a base station of the CU/DU architecture, for example, when the first access network device is the base station shown in FIG. 1b, the first access network device generates the first message by using the CU. And sending the first message to the terminal through the DU.
- the terminal releases or suspends the configured dedicated signaling radio bearer (SRB), and the protocol entity corresponding to the data radio bearer (DRB) of the reset configuration.
- SRB configured dedicated signaling radio bearer
- DRB data radio bearer
- the embodiments of the present application can be applied to NR and other types of radio access networks.
- the protocol entity corresponding to the DRB includes a packet data convergence protocol (PDCP) layer.
- PDCP packet data convergence protocol
- RLC radio link control
- MAC common medium access control
- the entity of the SDB layer and the SDAP layer exists in the NR technology, and the protocol entity corresponding to the DRB includes the entities of the PDCP, RLC, MAC, and SDAP layers.
- the terminal performs a reset operation the entities of the PDCP, RLC, MAC, and SDAP layers need to be reset.
- the entity in the DRB protocol entity includes the PDCP, RLC, MAC, and SDAP layers.
- the terminal may perform the following operations:
- the SRB includes a dedicated SRB and a public SRB.
- the dedicated SRB is a signaling radio bearer transmitted in an acknowledged mode (AM), and the dedicated SRB includes but is not limited to SRB1, SRB2, and SRB3.
- the public SRB includes, but is not limited to, SRB0 in Transparent Mode (TM).
- the terminal releases or suspends the dedicated SRB after receiving the first message.
- the terminal releases or suspends a protocol entity corresponding to the dedicated SRB
- the protocol entity corresponding to the dedicated SRB includes but is not limited to an entity of the RRC layer, the PDCP layer, and the RLC layer.
- the release means that the related functions of the radio bearer and/or the protocol entity are disabled or removed. That is, after the release operation, the terminal cannot process the uplink signaling through the related function of the protocol entity, and cannot be processed by the dedicated SRB.
- Uplink signaling. Suspending refers to preserving radio bearers and/or protocol entities, and corresponding configuration information, but suspending them to process corresponding protocol data, suspending the operation of corresponding timers and counters, and the like.
- the terminal needs to reset the corresponding entity corresponding to the dedicated SRB.
- the dedicated SRB is a split radio bearer, that is, one dedicated SRB corresponds to two logical channels, and if each logical channel corresponds to one RLC entity, that is, one dedicated SRB has two corresponding RLC entities, Then, the terminal needs to reset two RLC entities corresponding to the dedicated SRB.
- the terminal can perform signaling interaction with the first access network device through SRB0.
- the terminal resets the protocol entity corresponding to the configured DRB (that is, the configured DRB).
- the RB is applied to the NR, and the protocol entity corresponding to the DRB includes entities of the PDCP, RLC, MAC, and SDAP layers.
- One SDAP entity corresponds to one Packet Data Unit (PDU) session of the terminal, and one PDU session corresponds to one or more DRBs.
- PDU Packet Data Unit
- one DRB session corresponds to one or more DRBs.
- the terminal You need to reset the two RLC entities corresponding to the configured DRB.
- the terminal needs to reset other related protocol layer entities corresponding to the two logical channels.
- the terminal may perform the first step and then the second step, or may perform the first and second steps simultaneously. This embodiment of the present application does not limit this.
- the terminal After performing the two steps included in S202, the terminal enters a deactivated state. In the deactivated state, the terminal enters a power saving state, but the terminal can perform operations such as listening to the paging channel to be able to address the terminal when the access network device has a need to transmit downlink data.
- the terminal in the deactivated state can perform the mapping process of 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, and the RLC entity segments the data, and sends the segmented data to the MAC entity for multiplexing by the MAC entity.
- the uplink data processed by each layer entity is transmitted by the physical layer protocol entity.
- the terminal before the terminal receives the first message, as shown in (a) of FIG. 3, the terminal is configured with 4 dedicated radio bearers and 1 common SRB.
- the four dedicated radio bearers include SRB1, SRB2, DRB1, and DRB2, and the common SRB is SRB0.
- the SRB0 corresponds to an RRC layer protocol entity
- the protocol entity corresponding to the SRB1 includes an RRC layer, a PDCP layer, and an RLC layer entity.
- the protocol entity corresponding to SRB2 includes an RRC layer, a PDCP layer, and an RLC layer entity.
- the protocol entities corresponding to DRB1 include SDAP, PDCP, RLC, and entities of the public MAC layer.
- the protocol entities corresponding to DRB2 include SDAP, PDCP, RLC, and entities of the public MAC layer.
- DRB1 and DRB2 share one SDAP entity.
- the terminal is also configured with a PHY layer entity.
- the protocol stack of the terminal is as shown in FIG. 3(b) or FIG. 3(c). Accordingly, the operations performed by the terminal may include the following two situations:
- the terminal releases SRB1 and SRB2. Specifically, the terminal releases the RRC layer, the PDCP layer, and the RLC layer entity corresponding to each of SRB1 and SRB2. In addition, the terminal also resets DRB1, DRB2 as shown in (b) of FIG. 3, and respective corresponding SDAP, PDCP, RLC, and MAC layer entities.
- the white padding portion in FIG. 3 indicates that the corresponding protocol entity is reset. Therefore, the terminal can process the uplink data through the protocol entity corresponding to the DRB1 and the DRB2 in the reset state.
- the PHY entity is also reset such that the processed uplink data is transmitted by the PHY entity.
- the PHY entity may be in other states that can be used to transmit uplink information, including uplink data and uplink signaling, which is not limited in this embodiment of the present application.
- the terminal can process the uplink data through the protocol entity corresponding to the DRB.
- the terminal may perform QoS flow to DRB mapping processing on the uplink data through the SDAP entity, send the processed data to the PDCP entity, compress and encrypt the data by the PDCP entity, and send the compressed and encrypted data to the An RLC entity that performs operations such as segmenting data by an RLC entity.
- the terminal sends the segmented data to the MAC entity, and the MAC entity performs multiplexing and the like, and then the processed uplink data is transmitted by the PHY entity.
- the terminal can process the uplink signaling to be transmitted through SRB0 as a possible implementation manner. Specifically, the terminal may process the uplink signaling to be transmitted in sequence through the RRC protocol entity and the MAC layer entity corresponding to the SRB0, and then transmit the processed uplink signaling by using the PHY entity.
- the terminal suspends SRB1 and SRB2. Specifically, the terminal suspends the RRC layer, the PDCP layer, and the RLC layer entity corresponding to each of SRB1 and SRB2.
- the SDAP, PDCP, RLC, and MAC layer entities corresponding to each of DRB1 and DRB2 are reset.
- the terminal processes the uplink data by using the DRB corresponding to the uplink data. If the terminal has uplink signaling to be transmitted, the terminal processes the uplink signaling through SRB0.
- the first access network device after transmitting the first message, the first access network device also needs to perform corresponding operations on the corresponding bearer and the corresponding protocol entity of the bearer, that is, the terminal performs S202, and correspondingly, the first access network device performs the next operation. S203.
- the first access network device releases or suspends a dedicated SRB configured for the terminal.
- the dedicated SRB includes but is not limited to SRB1, SRB2, and SRB3.
- the terminal may transmit signaling between the first access network device through the public SRB (for example, SRB0).
- the first access network device is reset to a protocol entity corresponding to the DRB configured by the terminal, so that the terminal can transmit uplink data by using the DRB.
- the terminal or the access network device may perform some or all of the steps in the foregoing embodiments. These steps or operations are merely examples, and other operations or variations of various operations may be performed in the embodiments of the present application. Further, the various steps may be performed in a different order as presented in the above embodiments, and it is possible that not all of the operations in the above embodiments are performed.
- the terminal receives, from the first access network device, a first message for indicating to enter the deactivated state, and then releases or suspends the configured dedicated SRB, and resets the configured protocol entity corresponding to the 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 can be directly processed by the reset DRB. Data, thereby reducing the service delay of the terminal.
- the terminal does not immediately enter the deactivated state after receiving the first message, but enters the deactivated state under certain conditions.
- the embodiment of the present application further provides a communication method. As shown in FIG. 4, the method includes: S401 to S406.
- the first access network device sends a first message to the terminal.
- the terminal receives the first message sent by the first access network device.
- the first message is used to indicate that the terminal enters an RRC deactivation state, and the first message carries the identifier and RNA information of the terminal in the RRC deactivated state.
- the first access network device can detect the data transmission situation of the terminal. When detecting that the terminal does not have data transmission for a period of time, the first access network device can send a first message to the terminal to indicate that the terminal enters. Deactivated, or the terminal detects its own data transmission. When it detects that there is no data transmission within a certain period of time, the terminal initiates a request to enter the deactivation state to the first access network device, and the first access network device receives After the terminal's request, the first message is sent to the terminal to instruct the terminal to enter the deactivated state.
- the terminal performs a cell reselection operation.
- the terminal After the terminal receives the first message, the terminal performs a cell reselection operation, so that the terminal can be reselected into other cells.
- the terminal If the terminal reselects to the first cell within a preset duration after receiving the first message, the following S403 is performed.
- the first cell belongs to the cell indicated by the foregoing RNA information, and is different from the cell where the terminal receives the first message. It is assumed that the cell in which the terminal is located when receiving the first message is referred to as the source cell. After the cell reselection, the terminal reselects to the first cell, and 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. For example, the preset duration can be set to 100ms.
- the terminal performs the following step S403 after the preset duration. If the terminal receives the scheduling information within a preset duration after receiving the first message, the terminal performs the following step S404.
- the first message described in S401 carries timing information, where the timing information is used to indicate the preset duration. Then, after receiving the first message, the terminal enables the timer, and sets the timer duration of the timer to be 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 expires, the terminal may perform the process shown in S403 to enter the deactivated state in order to reduce the power consumption.
- the terminal after receiving the first message, the terminal directly enables the timer even if the first message does not carry the timing information, and sets the timer duration of the timer to a preset duration.
- the terminal releases or suspends the configured dedicated SRB and the protocol entity corresponding to the reset configured DRB.
- the terminal if the terminal receives the scheduling information sent by the first access network device before the timer expires, indicating that the terminal has data or signaling transmission requirements, the terminal stops the timer and stops the cell reselection operation, and keeps In the RRC connected state, the terminal transmits data or signaling according to the scheduling information sent by the first access network device.
- the timer is also enabled. If the first access network device is within the preset duration after the first message is sent, that is, before the timer expires, the terminal is determined to be heavy. When the first cell is selected, the first access network device performs S405. Or, if the first access network device does not send the scheduling information to the terminal within the preset duration after the first message is sent, and determines that the terminal is not reselected to the first cell, the first access network device after the preset duration The following step S405 is performed. If the first access network device sends the scheduling information to the terminal within a preset duration after the first message is sent, the first access network device performs the following step S406.
- the first access network device releases or suspends a dedicated SRB configured corresponding to the terminal, and a protocol entity corresponding to the DRB corresponding to the reset terminal.
- the first access network device indicates that the terminal remains in an RRC connected state.
- the terminal 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 after the specific condition is met, the specific condition.
- the method includes: the terminal reselects to the first cell within a preset duration after receiving the first message, or the terminal does not reselect to the first cell and does not receive the scheduling information within a preset duration after receiving the first message. . Therefore, after the terminal enters the deactivated state, the transmission amount of the uplink information (including the uplink data and the uplink information) is reduced, and the power consumption of the terminal is reduced.
- the terminal and the first access network device may perform some or all of the steps in the foregoing embodiments. These steps or operations are merely examples, and other operations or variations of various operations may be performed in the embodiments of the present application. Further, the various steps may be performed in a different order as presented in the above embodiments, and it is possible that not all of the operations in the above embodiments are performed.
- the anchor access network device of the terminal needs to be re-determined, so as to facilitate the terminal and the new anchor.
- Point access network devices exchange upstream and downstream information.
- an embodiment of the present application further provides a communication method. As shown in FIG. 5, the method includes S501 to S506:
- the S501 to S502 are the same as the above S201 and S202, and are not described herein again.
- the terminal If the terminal reselects to the cell covered by the second access network device and has uplink information to be transmitted, send a second message to the second access network device.
- the second access network device receives the second message sent by the terminal.
- the reselected cell belongs to the cell indicated by the RNA information. That is, the cell covered by the first access network device belongs to the same RNA as the reselected cell.
- the uplink information includes uplink data and uplink signaling.
- Uplink signaling includes, but is not limited to, a paging response message, an RNA update message, and a TA update message.
- the second message carries the identifier of the terminal in the RRC deactivated state and the information that triggers the reason for sending the second message.
- the identifier in the RRC deactivated state may be an I-RNTI.
- the I-RNTI is used to identify the terminal within the cell range indicated by the RNA information.
- the identifier of the terminal in the RRC deactivation state is associated with the architecture of the first access network device and the first access network device.
- the identifier of the terminal in the RRC deactivated state carries the first access network device identifier and whether the first access network device is related to the 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 of the terminal to access the network device.
- the information triggering the reason for transmitting the second message includes a cause value that triggers the transmission of the second message and other information for determining whether to migrate the anchor access network device of the terminal.
- the cause information may be an uplink buffer status report, a service/slice type and QoS category information to which the uplink data belongs, and a network load.
- the QoS class information indicates that the terminal is sensitive to the transmission delay, and after the second access network device receives the second message, in order to reduce the transmission of the terminal.
- the delay may be such that the anchor point is migrated to the second access network device, and the second access network device that is closer to the terminal or has better quality of service provides the coverage service for the terminal, thereby reducing the transmission delay of the terminal and improving The quality of service of the terminal.
- the second message further includes a Short Medium Access Control Integrity (MAC-I), and the short MAC-I is used by the access network device to authenticate the terminal.
- MAC-I Short Medium Access Control Integrity
- the second message further includes uplink data.
- the terminal processes the uplink data in the second message by using the protocol entity corresponding to the DRB.
- the embodiment of the present application does not limit the specific manner of processing the second message.
- the second message further includes uplink signaling.
- the terminal processes the uplink signaling in the second message by using the protocol entity corresponding to the SRB0.
- the embodiment of the present application does not limit the specific manner of processing the second message.
- the second message further includes a state transition request for the terminal to request to be transferred from the deactivated state to the connected state.
- the terminal may send uplink data or signaling to the access network device through a random access procedure or an agreed resource, for example, the terminal broadcasts through system information. Grant-free resources send uplink data or signaling to access network devices.
- the manner in which the terminal sends the uplink data may be implemented as:
- the terminal needs to perform RRC state transition first, and then send uplink data to the second access network device.
- the terminal may first send a second message including a state transition request to the second access network device, after which the terminal receives a state transition request response sent by the second access network device, and if the state transition response indicates the second access
- the network device determines that the terminal can be switched from the deactivated state to the connected state, and the terminal may send the uplink data to the second access network device, so that the second access network device processes the uplink data, or if the second access network device determines
- There is no need to migrate the anchor point (the migration anchor point is that the terminal is migrated from the first access network device to the second access network device at the entrance of the core network), and the second access network device sends the uplink data to the first access network.
- the device processes the uplink data by the first access network device.
- the flow of the RRC state transition and the uplink data processing may be performed simultaneously.
- the terminal may send a second message including a state transition request and uplink data to the second access network device, where the second access network device instructs the terminal to enter the 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.
- the terminal can send uplink data in the process of RRC state transition, thereby shortening the service delay of the terminal.
- the terminal may 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 manner, the RRC state transition process is reduced, and the service delay of the terminal is further shortened.
- the foregoing describes the second message in the embodiment of the present application by using the state transition request, the state transition request and the uplink data, or the uplink data as an example.
- the information included in the second message may be specifically included in the second message.
- the embodiment of the present application does not limit this according to the actual application scenario.
- the second access network device may send a response message of the second message to the terminal.
- the response message of the second message may feed back the transmission 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, where the response message indicates that the uplink data of the terminal has been successfully transmitted.
- the second access network device may send the terminal to indicate the terminal status.
- the response message for example, the response message may indicate that the terminal is maintained in the RRC deactivated state, or the response message may indicate that the terminal enters the RRC connected state. It can be understood that, if the response message of the second message indicates that the terminal maintains the RRC deactivated state, the second access network device optionally updates the context information of the terminal, for example, updating the identifier of the terminal in the deactivated state and / or terminal RNA information.
- the second access network device determines whether the terminal needs to be migrated from the first access network device to the second access network device at the ingress of the core network.
- S505 and S506 are performed. If the anchor access point network device of the terminal is not required to be migrated, the uplink information (if any) is cached and S507 is executed.
- the second access network device determines, according to the reason information carried in the second message sent by the terminal, whether to migrate the anchor access network device.
- the second access network device sends a request message for acquiring terminal context information to the first access network device.
- the first access network device receives the request message sent by the second access network device.
- the request message carries the identifier of the terminal in the RRC deactivated state.
- the second access network device addresses the first access network device according to the identifier of the terminal carried in the second message in the deactivated state, for example, the second access The 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.
- the first access network device sends the context information of the terminal to the second access network device.
- the second access network device receives the context information of the terminal sent by the first access network device.
- the second access network device may 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 by using the corresponding protocol entity.
- the second access network device sends uplink information to the first access network device.
- the first access network device receives the uplink information sent by the second access network device.
- the second access network device after receiving the second message, addresses the first access network device according to the identifier of the terminal carried in the second message in the deactivated state, for example, 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.
- the second access network device sends the uplink information in the following format to the first access network device:
- SDU MAC Service Data Unit
- LCID Logical Channel Identity
- I-RNTI short MAC-I ⁇ .
- 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.
- the second access network device may further send the cause information corresponding to the uplink information to the first access network device by using an interface encapsulation protocol between the access network devices.
- the role of the cause information is described above, and is not described here.
- the narrowband Internet-of-Things (NB-IoT) of 3GPP LTE always needs to migrate the anchor access network equipment.
- the second access network equipment The terminal context information needs to be obtained from the first access network device to increase signaling overhead and terminal power consumption.
- the second access network device can determine, according to the cause information in the second message, whether to migrate the anchor point access network device of the terminal, only if the migration anchor access network device is satisfied. The anchor of the terminal is migrated to access the network device.
- the embodiment of the present application may not migrate the anchor access network device when transmitting a small amount of data, thereby alleviating the transmission of context information between the first access network device and the second access network device.
- the resulting signaling overhead is large.
- the anchor access network device of the terminal needs to be migrated, the second access network device provides services for the terminal, because the second access network device is usually closer to the terminal or has better service quality, thereby being able to Improve the communication quality of the terminal.
- the second access network device determines not to trigger the migration of the terminal at the core network from the first access network device to the second access network device. Then, the uplink information of the terminal is processed by the first access network device. Based on this, in an implementation manner provided by the embodiment of the present application, as shown in FIG. 6, after the second access network device sends the uplink information to the first access network device, the first access network device processes The process of uplink information of the terminal includes:
- the first access network device processes the uplink information by using a protocol entity corresponding to the uplink information of the terminal.
- the format of the uplink information received by the first access network device is as follows:
- the short MAC-I is the authentication information corresponding to the terminal, and is used for identity verification of the terminal.
- the second access network device may also send the cause information to the first access network device.
- the function of the cause information is described above, and details are not described herein again.
- the identity information of the terminal may be verified to ensure the security of the radio access network.
- the uplink information may carry the authentication information corresponding to the terminal, and after receiving the uplink information of the terminal, the first access network device performs identity verification on the terminal according to the verification information of the terminal, and after the verification is passed, the first access The network device processes the uplink information of the terminal through the protocol entity.
- the verification information may be the short MAC-I described above, and the specific embodiment of the verification information is not limited in the embodiment of the present application.
- the reason information may also be used to indicate whether to update the access layer security key corresponding to the terminal.
- the verification information may be updated accordingly, so that the first access network device uses the updated verification information to the terminal. Authenticate.
- the first access network device may determine, according to the LCID carried in the uplink information, a protocol entity corresponding to the uplink information of the terminal, and the protocol entity sequentially processes the received uplink information, and then processes the processed uplink information.
- the uplink information is sent to the core network device, or the processed uplink information is sent to the RRC entity, and the RRC entity performs corresponding operations on the processed uplink information.
- the second access network device determines to trigger the migration of the terminal in the core network from the first access network device to the second access network device.
- the uplink information of the terminal should be processed by the second access network device. Based on this, in an implementation manner provided by the embodiment of the present application, as shown in FIG. 7, after the first access network device sends the context information of the terminal to the second access network device, the second access network
- the process of processing the uplink information of the terminal by the device includes:
- the second access network device generates a protocol entity corresponding to the DRB of the terminal according to the context information of the terminal.
- the second access network device After receiving the context information of the terminal, the second access network device triggers a path switching process, and migrates the terminal from the initial anchor access network device (ie, the first access network device) to the second. Access network equipment.
- the detailed process of path switching can refer to the literature related to 3GPP NR technology.
- the second access network device may generate a protocol entity corresponding to the DRB of the terminal, and process the uplink information of the terminal by using the generated protocol entity.
- the embodiment of the present application further provides a method for determining whether to trigger migration of a terminal at a core network from a first access network device to a second access network device. As shown in FIG. 8, the method includes S801 to S805:
- the second access network device acquires architecture indication information of the first access network device.
- 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.
- the S801 may be implemented by: the first access network device sending the architecture indication information to the second access network device.
- the second access network device receives the architecture indication information sent by the first access network device.
- the first access network device sends the architecture indication information to the second access network device by using the Xn setup process initiated by the inter-base station Xn interface, or the first access network device updates through a configuration update process.
- the architecture indicates information and sends updated architectural indication information to the second access network device.
- the terminal sends a second message to the second access network device.
- the second message has the same function as the second message mentioned above. I won't go into details here.
- S801 may be executed first, then S802 may be executed, or S802 may be executed first, and then 801 is executed.
- the second access network device determines whether the first access network device is a CU/DU architecture.
- the first access network device is a CU/DU architecture, then execute S804; otherwise, execute S805.
- the second access network device determines, according to the architecture indication information sent by the first access network device, whether the first access network device is a CU/DU architecture.
- the second access network device determines, according to the identifier of the terminal in the RRC deactivation state in the second message, whether the first access network device is a CU/DU architecture.
- 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.
- the highest 20 bits of the I-RNTI may be used. Identifies whether the first access network device is a CU/DU architecture. It can be understood that only the highest 20 bits of the I-RNTI are used as the identifiers.
- the specific location of the bits and the bits in the specific I-RNTI can be determined according to the actual application scenario. This is a limitation.
- the trigger migrates the terminal at the entrance of the core network from the first access network device to the second access network device.
- S805. Determine, according to the cause information, whether to trigger the migration of the terminal at the core network from the first access network device to the second access network device.
- the communication method provided by the embodiment of the present application determines whether to migrate the anchor point 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 point of the terminal is connected. The network access device migrates to the second access network device, and the second access network device processes the uplink information of the terminal. In the prior art, when the uplink information is processed by the first access network device of the CU/DU architecture, the CU and the CU are processed. Inter-signaling is required between the DUs, which increases the signaling overhead and reduces the signaling overhead.
- whether the anchor point of the terminal is migrated to access the network device may be determined by using multiple indicators. Based on this, in another implementation manner provided by the embodiment of the present application, as shown in FIG. 9, the process of determining whether to migrate the anchor point access network device of the terminal may further include the following steps:
- the second access network device determines, according to the reason information and/or the architecture of the first access network device, whether to trigger the migration of the terminal in the core network from the first access network device to the second access network device.
- the anchor access network device of the terminal is migrated to the network device.
- Second access network device when the first access network device is a non-CU/DU architecture, the process shown in FIG. 5 to FIG. 8 is further combined to determine whether to migrate the anchor access network device according to the cause information.
- the anchor access network device of the terminal is migrated to the second access network device.
- the protocol stack split mode (ie, RLC and below) as shown in FIG. 1b is adopted.
- the protocol layer is deployed on the DU, and the PDCP and the foregoing protocol layer are deployed on the CU.
- the CU in the first access network device needs to send the uplink data to the DU, and the uplink data is processed by the RLC entity deployed in the DU.
- the RLC entity combines the uplink data of the segment and sends the combined data to the CU, and the PDCP entity deployed in the CU processes the uplink data.
- the PDCP entity decompresses and decrypts the uplink data. It can be seen that in order to implement the processing of the uplink data, frequent interactions between the CU and the DU are required, which will result in a large processing delay.
- the first access network device is a CU/DU architecture (ie, the first access network, in conjunction with the method corresponding to FIG. 2, FIG. 4 to FIG.
- the embodiment of the present application further provides a communication method. As shown in FIG. 10, the method includes S1001 to S1005:
- the first access network device sends a first message to the terminal.
- the DU in the first access network device sends the first message to the terminal.
- S1002 The terminal releases or suspends the configured dedicated signaling radio bearer (SRB), and the protocol entity corresponding to the data radio bearer (DRB) of the reset configuration.
- SRB configured dedicated signaling radio bearer
- DRB data radio bearer
- S1003 The CU in the first access network device sends a third message to the DU.
- the DU in the first access network device receives the third message sent by the CU.
- the third message includes an identifier of the terminal in an RRC connected state, and the third message is used to instruct the DU to transfer the terminal to the deactivated state.
- the identity of the terminal in the RRC connected state is C-RNTI.
- the terminal may execute S1001 and then perform 1003, or may perform S1001 and S1003 at the same time.
- This embodiment of the present application does not limit this.
- the DU of the first access network device releases or suspends the configured SRB corresponding to the terminal, releases or suspends the RLC protocol entity corresponding to the configured DRB corresponding to the terminal, and resets the MAC layer entity.
- the first access network device may also reset the PHY entity.
- the terminal is configured with 4 dedicated radio bearers and 1 common SRB, wherein 4 dedicated radio bearers are SRB1, SRB2, DRB1, and DRB2, and the common SRB is SRB0, then Before and after the CU sends the third message to the DU, the protocol stack in the DU is as shown in FIG. Accordingly, the operations performed by the DU may include the following cases: the DU needs to be executed:
- DU releases or suspends SRB1 and SRB2. Specifically, the DU releases or suspends the RLC layer entity corresponding to each of SRB1 and SRB2.
- a schematic diagram of releasing a corresponding bearer and a protocol entity for a DU is a schematic diagram of suspending a corresponding bearer and a protocol entity for the DU.
- the DU resets the public MAC layer entity.
- the DU releases the RLC protocol entity corresponding to the DRB of the terminal, and as shown in (b) of FIG. 11, the DU suspends the RLC protocol entity corresponding to the DRB of the terminal.
- 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 the protocol entity of the terminal.
- S1005 the SRB of the CU release or suspension configuration of the first access network device, and the corresponding protocol entity in the CU, the DRB of the reset configuration, and the DRB of the configured DRB in the CU and the DRB of the generated terminal.
- RLC protocol entity the SRB of the CU release or suspension configuration of the first access network device, and the corresponding protocol entity in the CU, the DRB of the reset configuration, and the DRB of the configured DRB in the CU and the DRB of the generated terminal.
- the CU performs the step after receiving the response message of the third message sent by the DU, or the CU may directly perform the step after sending the third message.
- This embodiment of the present application does not limit this.
- the CU performs the following operations:
- the CU releases or suspends SRB1 and SRB2. Specifically, the CU releases the RRC layer and the PDCP layer entity corresponding to each of SRB1 and SRB2.
- the schematic diagram of the terminal protocol stack before and after the protocol entity corresponding to SRB1 and SRB2 of the CU release terminal corresponds to SRB1 and SRB2 of the CU suspended terminal. Schematic diagram of the terminal protocol stack before and after the protocol entity.
- the terminal may process the uplink signaling to be transmitted through the RRC layer entity corresponding to the SRB0, and transmit the processed uplink signaling through the SRB0.
- the CU resets the PDCP layer entity corresponding to each of DRB1 and DRB2 and the SDAP layer entity of the reset configuration. Moreover, the RLC entity corresponding to the DRB of the terminal is generated, so that when the terminal has an uplink data transmission requirement, the uplink data can be processed by the entities of the SDAP layer, the PDCP layer, and the RLC layer in sequence.
- the communication method provided by the embodiment of the present application after the terminal enters the deactivated state, deploys the RLC protocol entity corresponding to the DRB of the terminal on the CU, and releases or suspends the RLC protocol entity corresponding to the terminal on the DU, thereby performing uplink data.
- 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 the SDAP entity for processing, without frequent interaction with the DU. Interaction, which reduces processing latency.
- message names involved in the embodiments of the present application are only for convenience of description, and may be other message names in the specific implementation.
- the various information exemplified in the embodiments of the present application may be simultaneously sent, for example, It can be sent in one message, or it can be sent at different times, such as in different messages.
- the access network device and the terminal are taken as an example for description. It can be understood that the methods and functions implemented by the access network device in the foregoing method embodiments are also It can be implemented by a chip that can be used for an access network device, and the method and function implemented by the terminal can also be implemented by a chip that can be used for the terminal.
- the solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between different network elements.
- the network side devices including but not limited to the first access network device and the second access network device
- the terminal include corresponding hardware structures and/or software modules for performing the respective functions in order to implement the above functions.
- the embodiments of the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements of the examples and algorithm steps described in the embodiments disclosed in the application. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.
- the embodiments of the present application may divide the functional units of the network side device, the terminal, and the like according to the foregoing method examples.
- each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit.
- the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
- FIG. 12 shows 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, may be a terminal, or may be a chip usable for the terminal.
- the apparatus 1200 includes a processing unit 1202 and a communication unit 1203.
- processing unit 1202 can be used to support apparatus 1200 to perform S201 in FIG. 2, S503 in FIG. 5, and/or other processes for the schemes described herein.
- the communication unit 1203 is for supporting communication between the device 1200 and other network elements (e.g., network side devices).
- the communication device 1200 may further include a storage unit 1201 for storing program codes and data of the device 1200, and the data may include not limited to original data or intermediate data.
- the processing unit 1202 may be a processor or a controller, such as a central processing unit (CPU), a general-purpose processor, and a digital signal processing (DSP), application-specific integration.
- DSP digital signal processing
- ASIC Application Specific Integrated Circuit
- FPGA Field-Programmable Gate Array
- the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
- the communication unit 1203 may be a transceiver, a transceiver circuit, a communication interface, or the like.
- the storage unit 1201 may be a memory.
- the terminal involved in the embodiment of the present application may be the terminal shown in FIG.
- FIG. 13 is a simplified schematic diagram showing a possible design structure of a terminal involved in the embodiment of the present application.
- the terminal 1300 includes a transmitter 1301, a receiver 1302, and a processor 1303.
- the processor 1303 may also be a controller, and is represented as "controller/processor 1303" in FIG.
- the terminal 1300 may further include a modem processor 1305.
- the modem processor 1305 may include an encoder 1306, a modulator 1307, a decoder 1308, and a demodulator 1309.
- the transmitter 1301 conditions (eg, analog transforms, filters, amplifies, upconverts, etc.) the output samples and generates an uplink signal that is transmitted via an antenna to the base station described in the above embodiments. .
- the antenna receives the downlink signal transmitted by the base station in the above embodiment.
- Receiver 1302 conditions (eg, filters, amplifies, downconverts, digitizes, etc.) the signals received from the antenna and provides input samples.
- encoder 1306 receives the traffic data and signaling messages to be transmitted on the uplink and processes (e.g., formats, codes, and interleaves) the traffic data and signaling messages.
- Modulator 1307 further processes (e.g., symbol maps and modulates) the encoded service data and signaling messages and provides output samples.
- Demodulator 1309 processes (e.g., demodulates) the input samples and provides symbol estimates.
- the decoder 1308 processes (e.g., deinterleaves and decodes) the symbol estimate and provides decoded data and signaling messages that are sent to the terminal 1300.
- Encoder 1306, modulator 1307, demodulator 1309, and decoder 1308 may be implemented by a composite modem processor 1305. These units are processed according to the radio access technology employed by the radio access network (e.g., access technologies of LTE and other evolved systems). It should be noted that when the terminal 1300 does not include the modem processor 1305, the foregoing functions of the modem processor 1305 may also be completed by the processor 1303.
- the processor 1303 performs control and management on the operations of the terminal 1300, and is used to perform the processing performed by the terminal 1300 in the foregoing embodiment of the present application.
- the processor 1303 is also configured to perform the processes involved in the terminal in the methods illustrated in Figures 2, 4-6, and/or other processes of the technical solutions described herein.
- the terminal 1300 may further include a memory 1304 for storing program codes and data for the terminal 1300.
- FIG. 14 shows a possible exemplary block diagram of another communication device involved in the embodiment of the present application.
- the device 1400 may be in the form of software, or may be a network side device, such as a base station, or may be A chip that can be used for network side devices.
- the device 1400 includes a processing unit 1402 and a communication unit 1403.
- the processing unit 1402 is configured to control and control the action of the device 1400. For example, if the device is the first access network device, the processing unit 1402 is configured to support the device 1400 to perform S203 in FIG. 2, S405, S406 in FIG. And/or other processes for the techniques described herein.
- the processing unit 1402 is configured to support the device 1400 to perform S504, S505, S507 in FIG. 5, S701 in FIG. 7, and/or other processes for the techniques described herein.
- Communication unit 1403 is used to support communication of device 1400 with other network entities, such as terminals.
- the device 1400 can also include a storage unit 1401 for storing program codes and data of the device 1400.
- the processing unit 1402 may be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
- the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
- the communication unit 1403 may be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a collective name. In a specific implementation, the communication interface may include multiple interfaces, for example, may include: an interface between the base station and the terminal and/or Or other interface.
- the storage unit 1401 may be a memory.
- the apparatus 1400 involved in the embodiment of the present application may be the base station shown in FIG.
- the base station 1500 includes a processor 1502, a communication interface 1503, and a memory 1501.
- the base station 1500 may further include a bus 1504.
- the communication interface 1503, the processor 1502, and the memory 1501 may be connected to each other through a bus 1504.
- the bus 1504 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
- PCI Peripheral Component Interconnect
- EISA Extended Industry Standard Architecture
- the bus 1504 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 15, but it does not mean that there is only one bus or one type of bus.
- the computer program product includes one or more computer instructions.
- the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
- the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
- the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
- the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)). )Wait.
- a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
- an optical medium for example, a digital video disc (DVD)
- DVD digital video disc
- SSD solid state disk
- the disclosed system, apparatus, and method may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
- the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical or otherwise.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network devices. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, or each functional unit may exist independently, or two or more units may 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.
- 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. .
- the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer.
- a hard disk or optical disk, etc. includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请公开了一种通信方法及装置,涉及通信技术领域,可以解决无法直接发送上行数据导致的业务时延的问题。本申请的方法包括:从第一接入网设备接收第一消息,然后,释放或挂起配置的专用信令无线承载SRB,以及复位配置的数据无线承载DRB对应的协议实体,第一消息用于指示终端进入无线资源控制RRC去激活态,第一消息中携带终端在无线资源控制RRC去激活态下的标识以及无线接入网通知区RNA信息。
Description
本申请要求于2018年3月1日提交中国国家知识产权局、申请号为201810172450.7、申请名称为“通信方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信技术领域,尤其涉及通信方法及装置。
去激活态(inactive state)是第三代合作伙伴计划(3rd Generation Partnership Project,3GPP)新无线(New Radio,NR)技术中引入的一种无线资源控制(Radio Resource Control,RRC)状态。
一种可能的方式中,在去激活态下,终端与接入网设备断开了空口的RRC连接,终端在约定的时频位置接收下行数据、下行信令等,例如,终端可以接收接入网设备发送的寻呼消息。并且,在去激活态下,接入网设备存储终端的接入层上下文,并为终端分配无线接入网通知区(Radio Access Network Notification Area,RNA)和终端在去激活态下的标识。其中,RNA可以用于终端的移动性管理。
目前还未提出使得去激活态终端直接发送上行数据的技术方案,若终端不能在有上行数据需求时直接发送上行数据,会导致终端的业务时延。
发明内容
本申请提供一种通信方法及装置,可以解决去激活态终端无法直接发送上行数据导致的业务时延的问题。
为了实现上述目的,本申请的实施例采用如下技术方案:
第一方面,本申请的实施例提供一种通信方法,该方法可以由终端或可用于终端的芯片实现,该方法包括:从第一接入网设备接收第一消息,然后释放或挂起配置的专用信令无线承载SRB,以及复位配置的数据无线承载DRB对应的协议实体。
其中,第一消息用于指示终端进入RRC去激活态,第一消息中携带终端在RRC去激活态下的标识以及RNA信息。
采用该方法,终端可以从第一接入网设备接收用于指示进入去激活态的第一消息,进而释放或挂起配置的专用SRB,以及复位配置的DRB对应的协议实体。可见,本申请实施例中,由于终端保留并复位了DRB及对应的协议层实体,因此,终端在进入去激活态后,如果存在待传输的上行数据,则可通过复位的DRB直接处理该上行数据,从而降低终端的业务时延。
需要说明的是,本申请实施例可以应用于NR以及其他类型的无线接入网中。示例性地,若应用于长期演进(Long Term Evolution,LTE)的无线接入网中,由于LTE中不存在SDAP层以及SDAP层的实体,所以,DRB对应的协议实体包括分组数据汇聚协议(packet data convergence protocol,PDCP)层的实体、无线链路控制(radio link control,RLC)层的实体和公共的介质访问控制MAC实体。相应地,终端进行复位操作时,需复位PDCP、RLC、MAC层的实体。
若应用于NR技术的无线接入网,由于NR技术中存在SDAP层以及SDAP层的实体,所以,DRB对应的协议实体包括PDCP、RLC、MAC和SDAP层的实体。相应地,终端进行复位操作时,需复位PDCP、RLC、MAC和SDAP层的实体。本申请实施例中主要以应用于NR技术为例,即下文中以DRB对应的协议实体包括PDCP、RLC、MAC和SDAP层的实体为例。
可选地,第一消息中携带定时信息,定时信息用于指示预设时长。
在一种可能的设计中,释放或挂起配置的专用SRB,以及复位配置的DRB对应的协议实体,具体可以实现为:若在接收到第一消息后的预设时长内未收到调度信息,则在预设时长后释放或挂起配置的专用SRB及对应的协议层实体、复位配置的专用DRB及对应的协议层实体。
示例性的,当本申请实施例的方案应用于LTE的无线接入网中,释放或挂起配置的专用SRB,以及复位配置的DRB对应的协议实体,具体可以实现为:若在接收到第一消息后的预设时长内未收到调度信息,则在预设时长后释放或挂起配置的专用SRB及对应的协议层实体、复位配置的PDCP、RLC和MAC层的实体。
当本申请实施例的方案应用于NR的无线接入网中,释放或挂起配置的专用SRB,以及复位配置的DRB对应的协议实体,具体可以实现为:若在接收到第一消息后的预设时长内未收到调度信息,则在预设时长后释放或挂起配置的专用SRB及对应的协议层实体、复位配置的PDCP、RLC、MAC和SDAP层的实体。
需要说明的是,除了根据第一消息中携带的定时信息确定预设时长,预设时长还可以为终端中预先存储的时间数值。
在一种可能的设计中,释放或挂起配置的专用SRB及对应的协议层实体、复位配置的专用DRB及对应的协议层实体,还可以实现为:
在接收到第一消息后,执行小区重选操作;
若在预设时长内重选至第一小区,则释放或挂起配置的专用SRB,以及复位配置的DRB对应的协议实体。第一小区属于RNA信息所指示的小区,且不同于接收第一消息所在的小区。
采用该方法,终端在接收到第一接入网设备发送的第一消息之后,并不立即进入去激活态,而是在满足特定条件下才进入去激活态,该特定条件包括:终端在接收到第一消息后的预设时长内重选至第一小区,或者,终端在接收到第一消息后的预设时长内未重选至第一小区也未收到调度信息。从而,在终端进入去激活态之后,减少上行信息(包括上行数据和上行信息)的发送量,降低终端的耗电量。
在一种可能的设计中,若存在待传输上行数据,则通过上行数据对应的DRB传输上行数据,或者,若存在待传输上行信令,则通过公共信令无线承载传输上行信令。
在一种可能的设计中,在根据第一消息释放或挂起配置的专用SRB及对应的协议层实体、复位配置的专用DRB及对应的协议层实体之后,还可以执行:
若重选至第二接入网设备所覆盖的小区且存在待传输上行信息,则向第二接入网设备发送第二消息。
其中,第二消息中携带终端在RRC去激活态下的标识以及触发发送第二消息的原因的信息。重选的小区属于RNA信息所指示的小区,假定终端初始驻留的第一接入网设备所覆盖的小区称为源小区,则重选的小区与源小区属于同一RNA所指示的小区。并且,终端在RRC去激活态下的标识与第一接入网设备以及第一接入网设备的架构关联。具体地,终端在RRC去激活态下的标识可以携带第一接入网设备标识以及第一接入网设备是否为集中单元(Central Unit,CU)/分布单元(Distributed Unit,DU)架构相关的信息。可选地,第二接入网设备可以根据第一接入网设备的标识对第一接入网设备进行寻址。第二接入网设备可以根据第一接入网设备的CU/DU架构判断是否迁移终端的锚点接入网设备。
采用该方法,当终端重选至第二接入网设备所覆盖的小区且存在待传输上行信息时,终端可以向第二接入网设备发送第二消息,以触发第二接入网设备判断是否迁移终端的锚点接入网设备的动作。其中,第二接入网设备可以根据触发发送第二消息的原因的信息(本文中也称之为原因信息)和/或第一接入网设备的架构判断是否迁移终端的锚点接入网设备。进而,只有在满足迁移锚点接入网设备的触发条件下,才迁移终端的锚点接入网设备,避免了频繁迁移锚点导致的信令开销大的问题,在节约信令开销的同时,还可以降低终端的耗电量。
第二方面,本申请的实施例提供一种通信方法,该方法可以由第一接入网设备或者可用于第一接入网设备的芯片实现,该方法包括:第一接入网设备向终端发送第一消息,然后,第一接入网设备释放或挂起与终端对应配置的专用信令无线承载SRB、以及复位终端对应配置的数据无线承载DRB对应的协议实体。
其中,第一消息用于指示终端进入无线资源控制RRC去激活态,第一消息中携带终端在RRC去激活态下的标识以及无线接入网通知区RNA信息。
采用该方法,第一接入网设备向终端发送用于指示终端进入去激活态的第一消息,然后释放或挂起配置的专用SRB,以及复位配置的DRB对应的协议实体。可见,本申请实施例中,由于终端保留并复位了DRB及对应的协议层实体,因此,终端在进入去激活态后,如果存在待传输的上行数据,则可通过复位的DRB直接处理该上行数据,从而降低终端的业务时延。
参考上述描述,DRB对应的协议实体包括PDCP、RLC、MAC和SDAP层的实体,或者,DRB对应的协议实体包括PDCP、RLC和MAC层的实体。
在一种可能的设计中,第一接入网设备释放或挂起与终端对应配置的专用SRB、以及复位终端对应配置的DRB对应的协议实体,具体可以实现为:若在发送第一消息后的预设时长内未向终端发送调度信息,则在预设时长后释放或挂起与终端对应配置的专用SRB、以及复位终端对应配置的DRB对应的协议实体。
在一种可能的设计中,第一接入网设备释放或挂起与终端对应配置的专用SRB、以及复位终端对应配置的DRB对应的协议实体,还可以实现为:若在第一接入网设备发送第一消息后的预设时长内,确定终端重选至第一小区,则释放或挂起与终端对应配置的专用SRB、以及复位终端对应配置的DRB对应的协议实体。也就意味着,在预设时长内,终端重选至第一小区也可以触发进入去激活态的流程。
采用该方法,第一接入网设备向终端发送第一消息之后,可以设置预设时长,当达到预设时长之前,若终端重选至第一小区,则第一接入网设备可以指示终端进入去激活态。 或者,终端在接收到第一消息后的预设时长内未重选至第一小区也未收到调度信息,则其可以指示终端进入去激活态。从而,在指示终端进入去激活态之后,减少终端上行信息(上行信息包括上行数据和上行信息)的发送量,降低终端的耗电量。
在一种可能的设计中,若第一接入网设备包括CU和DU,则第一接入网设备向终端发送第一消息,具体可以实现为:第一接入网设备通过DU向终端发送第一消息。
在一种可能的设计中,还可以执行:
第一接入网设备中的CU向DU发送第三消息,然后第一接入网设备的DU确定终端的无线承载的相关配置。其中,DU确定终端的无线承载的相关配置,具体可以实现为:释放或挂起与终端对应的配置的SRB及配置的SRB在DU中对应的协议实体、释放或挂起与终端对应的配置的DRB对应的无线链路控制RLC协议实体以及复位公共介质访问控制层的实体。
之后,在第一接入网设备中的CU向DU发送第三消息之后,第一接入网设备的CU释放或挂起配置的SRB及配置的SRB在CU中对应的协议实体、复位配置的DRB及配置的DRB在CU中对应的协议实体、生成DRB对应RLC协议实体。
或者,在DU确定终端的无线承载的相关配置之后,DU向CU发送第三消息的响应消息,在接收到第三消息的响应消息之后,CU释放或挂起配置的SRB及配置的SRB在CU中对应的协议实体、复位配置的DRB及配置的DRB在CU中对应的协议实体、生成DRB对应RLC协议实体。
其中,第三消息包括终端在RRC连接态下的标识,示例性地,终端在RRC连接态下的标识为C-RNTI,第三消息用于指示DU将终端转移至去激活态。第三消息的响应消息用于表明DU已经对终端的无线承载及协议实体进行了处理。
采用该方法,在终端进入去激活态之后,将终端的DRB对应的RLC协议实体部署在CU上,并且释放或挂起DU上的终端对应的RLC协议实体,从而当上行数据到达时,第一接入网设备中的CU可以通过部署的RLC协议实体处理MAC SDU格式的上行数据,再将处理后的上行数据依次送至PDCP、SDAP实体中进行处理,无需与DU进行频繁的交互,从而降低处理时延。
在一种可能的设计中,在确定不触发将终端在核心网的入口由第一接入网设备迁移至第二接入网设备的情况下,可以执行:第一接入网设备接收第二接入网设备转发的终端的上行信息,然后第一接入网设备通过与终端的上行信息对应的协议实体处理上行信息。
其中,上行信息中携带终端在RRC去激活态下的标识。
采用该方法,当确定不迁移终端的锚点接入网设备时,由第一接入网设备完成与终端的数据或信令交互,避免了频繁迁移锚点接入网设备所导致的信令开销大的问题,同时,也能够降低终端的耗电量。
在一种可能的设计中,上行信息中携带终端对应的验证信息。相应的,在第一接入网设备通过协议实体处理上行信息之前,可以执行:第一接入网设备根据验证信息对终端进行身份验证,验证通过后,第一接入网设备通过协议实体处理上行信息。
在一种可能的设计中,上行信息中携带原因信息。相应的,第一接入网设备可以根据原因信息确定是否更新终端对应的接入层安全密钥。
在一种可能的设计中,在确定触发将终端在核心网的入口由第一接入网设备迁移至第 二接入网设备的情况下,可以执行:第一接入网设备接收第二接入网设备发送的获取终端上下文的请求消息,然后,第一接入网设备向第二接入网设备发送终端的上下文信息。
其中,请求消息中携带终端在RRC去激活态下的标识。
采用该方法,若需迁移终端的锚点接入网设备,则由第二接入网设备为终端提供覆盖服务,由于第二接入网设备通常距离终端较近或者服务质量更好,从而,能够提升终端的通信质量。
在一种可能的设计中,在第一接入网设备接收第二接入网设备发送的获取终端上下文的请求消息之前,还可以执行:第一接入网设备向第二接入网设备发送架构指示信息。其中,架构指示信息用于指示第一接入网设备是否为CU/DU架构类型的接入网设备。
采用该方法,第一接入网设备向第二接入网设备发送架构指示信息,以指示第二接入网设备根据第一接入网设备的架构判断是否迁移终端的锚点接入网设备,若第一接入网设备为CU/DU架构,则将终端的锚点迁移至第二接入网设备,由第二接入网设备处理终端的上行信息,减少了信令开销。
第三方面,本申请的实施例提供一种通信方法,该方法可以由第二接入网设备或者可用于第二接入网设备的芯片实现,该方法包括:第二接入网设备接收终端发送的第二消息,若第二接入网设备根据触发发送第二消息的原因的信息确定触发将终端在核心网的入口由第一接入网设备迁移至第二接入网设备,则第二接入网设备向第一接入网设备发送获取终端上下文信息的请求消息,然后,第二接入网设备接收第一接入网设备发送的终端的上下文信息。
其中,第二消息中携带终端在无线资源控制RRC去激活态下的标识以及触发发送第二消息的原因的信息。
采用该方法,第二接入网设备可以接收终端发送的第二消息,并根据第二消息中的原因信息判断是否迁移终端的锚点接入网设备,进而,只有在满足迁移锚点接入网设备的触发条件下,才迁移终端的锚点接入网设备,避免了频繁迁移锚点导致的信令开销大的问题,在节约信令开销的同时,还可以降低终端的耗电量。
在一种可能的设计中,在第二接入网设备接收第一接入网设备发送的终端的上下文信息之后,还可以执行:第二接入网设备根据终端的上下文信息生成终端的DRB对应的协议实体。
采用该方法,在确定需迁移终端的锚点接入网设备之后,由第二接入网设备处理终端的上行信息,为终端提供覆盖服务,由于第二接入网设备通常距离终端较近或者服务质量更好,从而,能够提升终端的通信质量。
参考上述描述,DRB对应的协议实体包括PDCP实体、RLC实体、公共的MAC实体和SDAP实体,或者,DRB对应的协议实体包括PDCP实体、RLC实体和公共的MAC实体。
在一种可能的设计中,原因信息包括:上行缓存状态报告、上行数据所属的业务/切片类型和服务质量QoS类别信息、网络负荷。
在一种可能的设计中,还可以执行:第二接入网设备确定第一接入网设备是否为集中单元CU/分布单元DU架构,若第一接入网设备为CU/DU架构,则触发将终端在核心网的入口由第一接入网设备迁移至第二接入网设备。
采用该方法,若第二接入网设备确定第一接入网设备为CU/DU架构,则将终端的锚点 迁移至第二接入网设备,由第二接入网设备处理终端的上行信息,减少了信令开销。
在一种可能的设计中,第二接入网设备确定第一接入网设备是否为CU/DU架构,具体可以实现为:第二接入网设备获取第一接入网设备发送的架构指示信息,然后,第二接入网设备根据架构指示信息确定第一接入网设备是否为CU/DU架构。
示例性地,第二接入网设备获取第一接入网设备的架构指示信息,具体可以实现为:第一接入网设备向第二接入网设备发送架构指示信息,相应地,第二接入网设备接收架构指示信息。
第二接入网设备确定第一接入网设备是否为CU/DU架构,还可以实现为:第二接入网设备根据终端在RRC去激活态下的标识确定第一接入网设备是否为CU/DU架构。
在一种可能的设计中,还可以执行:若第二接入网设备根据原因信息确定不触发将终端在核心网的入口由第一接入网设备迁移至第二接入网设备,则第二接入网设备向第一接入网设备发送上行信息。
采用该方法,当第二接入网设备确定不迁移终端的锚点接入网设备时,指示第一接入网设备处理终端的上行信息,以完成与终端的数据或信令交互,避免了频繁迁移锚点接入网设备所导致的信令开销大的问题,同时,也能够降低终端的耗电量。
第四方面,本申请实施例提供一种通信装置,该装置具有实现上述第一方面所述的方法的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。例如,该装置可以为终端,或者可以为可用于终端的芯片。
在一种可能的设计中,该装置为终端,终端包括处理器,所述处理器被配置为支持终端执行上述方法中相应的功能。进一步地,终端还可以包括发射器和接收器,所述发射器和接收器用于支持终端与网络侧设备之间的通信。进一步的,终端还可以包括存储器,所述存储器用于与处理器耦合,其保存终端必要的程序指令和数据。这里,网络侧设备包括但不限于第一接入网设备和第二接入网设备。
第五方面,本申请实施例提供一种通信装置,该装置具有实现上述第二方面所述的方法的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。例如,该装置可以为基站,或者可以为可用于基站的芯片。
在一种可能的设计中,该装置为基站,基站包括处理器,所述处理器被配置为支持基站执行上述方法中相应的功能。进一步地,基站还可以包括发射器和接收器,所述发射器和接收器用于支持基站与终端之间的通信。进一步的,基站还可以包括存储器,所述存储器用于与处理器耦合,其保存基站必要的程序指令和数据。
第六方面,本申请实施例提供一种通信装置,该装置具有实现上述第三方面所述的方法的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。例如,该装置可以为基站,或者可以为可用于基站的芯片。
在一种可能的设计中,该装置为基站,基站包括处理器,所述处理器被配置为支持基站执行上述方法中相应的功能。进一步地,基站还可以包括发射器和接收器,所述发射器和接收器用于支持基站与终端之间的通信,或者,支持基站之间的通信。进一步的,基站 还可以包括存储器,所述存储器用于与处理器耦合,其保存基站必要的程序指令和数据。
第七方面,本申请实施例提供一种通信***,该***包括上述方面所述的终端和第一接入网设备、第二接入网设备。
第八方面,本申请实施例提供一种计算机可读存储介质,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机执行上述第一方面或第二方面或第三方面所述的方法。
第九方面,本申请的实施例提供一种包括指令的计算机程序产品,当其在计算机上运行时,使得计算机执行如上述第一方面或第二方面或第三方面所述的方法。
第十方面,本申请的实施例提供一种芯片***,应用于终端中,所述芯片***包括至少一个处理器,存储器和接口电路,所述存储器、所述收发器和所述至少一个处理器通过线路互联,所述至少一个存储器中存储有指令;所述指令被所述处理器执行,以执行上述第一方面所述的方法。
第十一方面,本申请的实施例提供一种芯片***,应用于网络侧设备中,示例性地,应用于第一接入网设备中,所述芯片***包括至少一个处理器,存储器和接口电路,所述存储器、所述收发器和所述至少一个处理器通过线路互联,所述至少一个存储器中存储有指令;所述指令被所述处理器执行,以执行上述第二方面所述的方法。
第十二方面,本申请的实施例提供一种芯片***,应用于网络侧设备中,示例性地,应用于第二接入网设备中,所述芯片***包括至少一个处理器,存储器和接口电路,所述存储器、所述收发器和所述至少一个处理器通过线路互联,所述至少一个存储器中存储有指令;所述指令被所述处理器执行,以执行上述第三方面所述的方法。
通过本申请实施例的方案,终端从第一接入网设备接收用于指示进入去激活态的第一消息,进而释放或挂起配置的专用SRB,以及复位配置的DRB对应的协议实体。即本申请实施例给出了可以用于直接处理上行数据的DRB,从而当终端存在待传输的上行数据时,可以通过复位的DRB直接处理该上行数据,降低终端的业务时延。
图1a为本申请实施例提供的通信***的结构示意图;
图1b为本申请实施例提供的一种基站的结构示意图;
图2为本申请实施例提供的一种通信方法的流程图;
图3为本申请实施例提供的协议栈的示意图;
图4为本申请实施例提供的一种通信方法的流程图;
图5为本申请实施例提供的一种通信方法的流程图;
图6为本申请实施例提供的一种通信方法的流程图;
图7为本申请实施例提供的一种通信方法的流程图;
图8为本申请实施例提供的一种通信方法的流程图;
图9为本申请实施例提供的一种通信方法的流程图;
图10为本申请实施例提供的一种通信方法的流程图;
图11为本申请实施例提供的协议栈的示意图;
图12为本申请实施例提供的一种通信装置的结构示意图;
图13为本申请实施例提供的终端的结构示意图;
图14为本申请实施例提供的一种通信装置的结构示意图;
图15为本申请实施例提供的基站的结构示意图。
本申请描述的***架构及业务场景是为了更加清楚的说明本申请的技术方案,并不构成对于本申请提供的技术方案的限定,本领域普通技术人员可知,随着***架构的演变和新业务场景的出现,本申请提供的技术方案对于类似的技术问题,同样适用。
需要说明的是,本申请中,“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言,使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请中“的(英文:of)”,相应的“(英文corresponding,relevant)”和“对应的(英文:corresponding)”有时可以混用,应当指出的是,在不强调其区别时,其所要表达的含义是一致的。
本申请的实施例应用于NR及其他类型的无线接入网中。
如图1a所示,图1a示出了本申请的一种可能的通信***示意图,该通信***可以包括至少一个核心网设备(图中仅示出1个)、与核心网设备和终端通信的一个或多个接入网设备,以及通过接入网设备接入核心网的终端。
其中,本申请所称的核心网设备,是一种部署在核心网中用以为终端提供服务的装置。本申请所称的核心网设备包括但不限于:接入和移动管理功能(AMF,Access and Mobility Management Function)、会话管理功能(SMF,Session Management Function)、用户面功能(UPF,User Plane Function)、策略和计费规则功能(PCRF,Policy and Charging Rules Function),以及它们组合的设备。在采用不同的无线接入技术的***中,具备相类似无线通信功能的核心网设备的名称可能会有所不同。仅为描述方便,本申请实施例中,上述可以为终端提供服务的装置统称为核心网设备。
本申请所称的接入网设备,是一种部署在无线接入网中用以为终端提供无线通信功能的装置,本申请所称的接入网设备包括但不限于:各种形式的宏基站,微基站(也称为小站),中继站,发送接收点(Transmission Reception Point,TRP),下一代网络节点(g Node B,gNB)、连接下一代核心网的演进型节点B(ng evolved Node B,ng-eNB)、等,还可以包括无线局域网(wireless local area network,WLAN)接入设备等非3GPP***的无线接入网设备。在采用不同的无线接入技术的***中,具备相类似无线通信功能的无线接入网设备的名称可能会有所不同。仅为描述方便,本申请实施例中,上述可以为终端提供无线通信功能的装置统称为接入网设备。
本申请所称的终端,是一种具有无线收发功能的设备,可以部署在陆地上,包括室内或室外、手持或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等)。该终端可以包括各种类型的手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、无线数据卡、虚拟现实(Virtual Reality,VR)终端设备、增强现实(augmented reality,AR)终端设备、机器类型通信(machine type communication,MTC)的终端设备,工业控制(industrial control)中的终端设备、无人驾驶(self driving)中的终端设备、远程医疗(remote medical)中的终端设备、智能电网(smart grid)中 的终端设备、运输安全(transportation safety)中的终端设备、智慧城市(smart city)中的终端设备,以及可穿戴设备(如智能手表,智能手环,计步器等)等等。在采用不同的无线接入技术的***中,具备相类似无线通信功能的终端的名称可能会有所不同,仅为描述方便,本申请实施例中,上述具有无线收发通信功能的装置统称为终端。
在本申请实施例中的通信***中,接入网设备与核心网设备之间可以通过NG接口进行通讯,接入网设备之间可以通过Xn接口进行通讯。可以理解的是,接入网设备与核心网设备之间还可以通过其他类型的接口进行通讯,同样地,接入网设备之间也可以通过其他类型的接口进行通讯,本申请实施例不对此进行限制。
以下以基站为例对本申请实施例的接入网设备进行说明。
如图1b所示,一种可能的方式中,基站可以由集中式单元(centralized unit,CU)和分布式单元(distributed unit,DU)构成,一个CU可以连接一个DU,或者也可以多个DU共用一个CU,可以节省成本,以及易于网络扩展。CU和DU的切分可以按照协议栈切分,其中一种可能的方式是将无线资源控制(radio resource control,RRC)、业务数据匹配协议(Service Data Adaptation Protocol,SDAP)以及PDCP层部署在CU,其余的RLC层、MAC层以及物理层(physical layer,PHY layer)部署在DU。
本申请实施例中并不完全限定上述协议栈切分方式,还可以有其它的切分方式。当网络设备是例如图1b的CU和DU的架构时,本申请实施例提到接入网设备时,可能是指CU,也可能是指DU,或者是由CU和DU构成的***,具体依赖于相应的实现功能。
可以理解的是,本申请实施例中所提到的基站不限于图1b的形式,可以是任何提供部署在无线接入网中用以为终端提供无线通信功能的装置。
其中,本申请实施例涉及的方法主要应用在无线接入网中,即本申请实施例的方法主要应用在接入网设备和终端构成的接入网***中。上述由终端、接入网设备和核心网设备构成的通信***包括接入网***。
以下对本申请实施例中的术语进行说明。
终端的上下文信息,用于表征终端的身份、背景和状态的全部信息。示例性地,终端的上下文信息包括但不限于终端的位置信息,终端标识,专用无线承载配置信息。其中,接入网设备可以根据终端的上下文信息生成终端对应的协议实体,并通过相应的协议实体处理终端的数据或信令。
锚点接入网设备,用于维护终端的上下文。其中,终端在移动时可能发生迁移锚点接入网设备的情况。例如,终端初始驻留在第一接入网设备,由第一接入网设备存储、维护终端的上下文信息,之后,终端发生位置变化,其当前的服务接入网设备为第二接入网设备,则若确定将终端在核心网的入口由第一接入网设备迁移至第二接入网设备,需将第一接入网设备维护的终端上下文信息传输至第二接入网设备,以便于第二接入网设备根据获取的终端上下文信息处理终端的数据或信令,与终端进行交互。
结合图1a所示的通信***以及图1b所示的基站,本申请的实施例提供一种通信方法,如图2所示,该方法包括:
S201、第一接入网设备向终端发送第一消息。
相应的,终端接收第一接入网设备发送的第一消息。
其中,第一消息用于指示终端进入RRC去激活态,第一消息中携带终端在RRC去激活 态下的标识以及RNA信息。
可选地,终端在RRC去激活态下的标识可以为终端的去激活态无线网络临时标识(inactive-Radio Network Temporary Identifier,I-RNTI),RNA信息用于指示RNA,可以由接入网设备为终端分配RNA,一个RNA通常包括至少一个小区。作为一种示例性的方案,RNA信息可以为小区标识列表。可以理解的是,当终端位置发生变化时,若终端当前所处位置在RNA包含的范围内,则终端可以不向接入网设备发送当前所处的位置信息,若终端当前已移出RNA包含的范围内,则为了对终端位置进行管理,则终端需向接入网设备发送当前所处的位置信息。此外,若终端并未移出RNA包含的范围内,但是当达到预设时间之后,终端也需向接入网设备发送当前所处的位置信息。举例来说,第一接入网设备覆盖的小区为小区1至小区3,第二接入网设备覆盖的小区为小区4至小区5,假定终端初始接入第一接入网设备的小区1,并由第一接入网设备为终端分配RNA_1,RNA_1包含小区1至小区3,则当终端移动至小区2或小区3的覆盖范围内,由于终端并未移出RNA_1覆盖的范围,所以终端可以不向接入网设备上报当前的位置信息,当终端移动至小区4或小区5或小区6时,由于终端已移出RNA_1覆盖的范围,则终端需向接入网设备上报当前的位置信息。
可以理解的是,第一接入网设备可以检测终端的数据传输情况,当检测到终端在一段时间内未存在数据传输,第一接入网设备可以向终端发送第一消息,以指示终端进入去激活态,或者,终端检测自身的数据传输情况,当检测到自身在一段时间内未存在数据传输,终端向第一接入网设备发起进入去激活态请求,第一接入网设备接收到终端的请求之后,向终端发送第一消息,以指示终端进入去激活态。
可选地,当第一接入网设备为CU/DU架构的基站时,例如,当第一接入网设备为图1b所示的基站时,第一接入网设备通过CU生成第一消息,并通过DU向终端发送第一消息。
S202、终端释放或挂起配置的专用信令无线承载(Signalling Radio Bearer,SRB)、以及复位配置的数据无线承载(Data Radio Bearer,DRB)对应的协议实体。
需要说明的是,本申请实施例可以应用于NR以及其他类型的无线接入网中。示例性地,若应用于LTE的无线接入网中,由于LTE中不存在SDAP层以及SDAP层的实体,所以,DRB对应的协议实体包括分组数据汇聚协议(packet data convergence protocol,PDCP)层的实体、无线链路控制(radio link control,RLC)层的实体和公共的介质访问控制MAC实体。相应地,终端进行复位操作时,需复位PDCP、RLC、MAC层的实体。
若应用于NR技术的无线接入网,由于NR技术中存在SDAP层以及SDAP层的实体,所以,DRB对应的协议实体包括PDCP、RLC、MAC和SDAP层的实体。相应地,终端进行复位操作时,需复位PDCP、RLC、MAC和SDAP层的实体。
下文中主要以应用于NR技术的无线接入网为例对本申请实施例的方案进行说明,即以DRB协议实体包括PDCP、RLC、MAC和SDAP层的实体为例。
在接收到第一消息之后,终端可以执行如下操作:
第一:释放(release)或挂起(suspend)配置的专用SRB。
在3GPP协议中,SRB包括专用SRB和公共SRB。专用SRB为采用确认模式(acknowledged mode,AM)进行传输的信令无线承载,专用SRB包括但不限于SRB1、SRB2、SRB3。公共SRB包括但不限于采用透传模式(Transparent Mode,TM)的SRB0。本申请实施例中,终 端在接收到第一消息后释放或挂起专用SRB。
具体地,终端释放或挂起专用SRB对应的协议实体,专用SRB对应的协议实体包括但不限于RRC层、PDCP层和RLC层的实体。其中,释放是指无线承载和/或协议实体的相关功能被关闭或移除,即经过释放这一操作,终端无法通过协议实体的相关功能处理上行信令,也无法通过专用SRB传输处理后的上行信令。挂起是指保留无线承载和/或协议实体,以及对应的配置信息,但暂停用它们处理对应的协议数据,暂停对应定时器和计数器等的运行。
如果存在专用SRB对应多个逻辑信道,则终端需要复位该专用SRB对应的相应实体。示例性地,专用SRB为劈裂无线承载(Split radio bearer),即一个专用SRB对应两个逻辑信道,若每个逻辑信道对应一个RLC实体,也就是一个专用SRB有两个对应的RLC实体,则终端需要复位该专用SRB对应的两个RLC实体。
当然,在释放或挂起已配置的专用SRB后,终端可以通过SRB0与第一接入网设备之间进行信令交互。
第二:终端复位(reset)配置的DRB(即configured DRB)对应的协议实体。
以应用于NR中为例,则DRB对应的协议实体包括PDCP、RLC、MAC和SDAP层的实体。
其中,一个SDAP实体对应终端的一个分组数据单元(Packet Data Unit,PDU)会话(session),一个PDU会话对应一个或多个DRB。示例性地,如果存在配置的DRB为劈裂无线承载(Split radio bearer),假定一个DRB对应两个逻辑信道,每个逻辑信道对应一个RLC实体,即DRB有两个对应的RLC实体,则终端需要复位配置的DRB对应的两个RLC实体。相应地,终端需复位该两个逻辑信道对应的其他相关协议层实体。
需要说明的是,上述第一、第二步骤之间并无时间先后顺序。示例性地,终端可以先执行第一步骤、再执行第二步骤,也可以同时执行第一、第二步骤。本申请实施例对此不进行限制。
可以理解的是,在执行S202所包括的两个步骤之后,终端进入去激活态。在去激活态,终端进入节能状态,但是,终端可以执行诸如监听寻呼信道的操作,以便在接入网设备有传输下行数据的需求时,能够寻址到终端。
这样,去激活态的终端收到上行数据后,可以通过SDAP实体对上行数据进行服务质量(Quality of Service,QoS)流到DRB的映射处理,将处理后的数据送至对应的PDCP实体,由PDCP实体对数据进行压缩、加密,并将压缩加密后的数据发送至RLC实体,由RLC实体对数据进行分段等操作,并将分段后的数据送至MAC实体,由MAC实体进行复用等操作,之后,由物理层协议实体传输经过各层实体处理后的上行数据。
示例性的,在终端接收到第一消息之前,如图3中(a)所示,终端配置有4个专用无线承载和1个公共的SRB。其中,该4个专用无线承载包括SRB1、SRB2、DRB1、DRB2,公共的SRB为SRB0。其中,SRB0对应有RRC层协议实体,SRB1对应的协议实体包括RRC层、PDCP层和RLC层实体。SRB2对应的协议实体包括RRC层、PDCP层和RLC层实体。DRB1对应的协议实体包括SDAP、PDCP、RLC、公共MAC层的实体。DRB2对应的协议实体包括SDAP、PDCP、RLC、公共MAC层的实体。DRB1和DRB2共用一个SDAP实体。终端还配置有PHY层实体。
在终端接收第一消息之后,终端的协议栈如图3中(b)或图3中(c)所示,相应地, 终端执行的操作可以包括以下两种情况:
情况一:
如图3中(b)所示,终端释放SRB1和SRB2。具体地,终端释放SRB1、SRB2各自对应的RRC层、PDCP层和RLC层实体。此外,终端还复位如图3中(b)所示的DRB1、DRB2,以及各自对应的SDAP、PDCP、RLC和MAC层实体。
需要说明的是,图3中白色填充部分表示,相应协议实体被复位。从而终端能够通过复位状态的DRB1、DRB2对应的协议实体处理上行数据。可选地,PHY实体也被复位,从而由PHY实体传输处理后的上行数据。此外,PHY实体还可以处于其他可用于传输上行信息(包括上行数据和上行信令)的状态,本申请实施例对此不进行限制。
这样,若终端存在待传输的上行数据,则作为一种可能的实现方式,终端可以通过DRB对应的协议实体对上行数据进行处理。示例性地,终端可以通过SDAP实体对上行数据进行QoS流到DRB的映射处理,将处理后的数据送至PDCP实体,由PDCP实体对数据进行压缩、加密,并将压缩加密后的数据送至RLC实体,由RLC实体对数据进行分段等操作。之后,终端将分段后的数据送至MAC实体,由MAC实体进行复用等操作,之后,由PHY实体传输处理后的上行数据。
若终端存在待传输的上行信令,则作为一种可能的实现方式,终端可以通过SRB0处理待传输的上行信令。具体的,终端可以通过SRB0对应的RRC协议实体、MAC层实体依次处理待传输的上行信令,然后通过PHY实体传输该处理后的上行信令。
情况二:
如图3中(c)所示,终端挂起SRB1和SRB2,具体地,终端挂起SRB1、SRB2各自对应的RRC层、PDCP层和RLC层实体。复位DRB1、DRB2各自对应的SDAP、PDCP、RLC、MAC层实体。
需要说明的是,图3中(c)阴影部分表示相应协议实体被挂起。
这样,若终端存在待传输上行数据,则终端通过上行数据对应的DRB处理上行数据。若终端存在待传输上行信令,则终端通过SRB0处理上行信令。
相应地,第一接入网设备在发送第一消息之后,也需对相应的承载及承载对应的协议实体进行相应操作,即由终端执行S202,相应地,由第一接入网设备执行下述S203。
S203、第一接入网设备释放或挂起为上述终端配置的专用SRB。其中,专用SRB包括但不限于SRB1、SRB2、SRB3。作为一种可能的实现方式,终端可以通过该公共SRB(例如SRB0)传输与第一接入网设备之间的信令。并且,第一接入网设备复位为终端配置的DRB对应的协议实体,从而终端能够通过DRB传输上行数据。
可以理解的,终端或接入网设备可以执行上述实施例中的部分或全部步骤,这些步骤或操作仅是示例,本申请实施例还可以执行其它操作或者各种操作的变形。此外,各个步骤可以按照上述实施例呈现的不同的顺序来执行,并且有可能并非要执行上述实施例中的全部操作。
本申请实施例提供的通信方法,终端从第一接入网设备接收用于指示进入去激活态的第一消息,进而释放或挂起配置的专用SRB,以及复位配置的DRB对应的协议实体。可见,本申请实施例中,由于终端保留并复位了DRB及对应的协议层实体,因此,终端在进入去激活态后,如果存在待传输的上行数据,则可通过复位的DRB直接处理该上行数据,从而 降低终端的业务时延。
结合图2所示的方法,可选地,在本申请实施例提供的一种实现方式中,终端在接收第一消息之后并不立即进入去激活态,而是在特定条件下进入去激活态。基于此,本申请实施例还提供一种通信方法,如图4所示,该方法包括:S401至S406。
S401、第一接入网设备向终端发送第一消息。
相应的,终端接收第一接入网设备发送的第一消息。
其中,第一消息用于指示终端进入RRC去激活态,第一消息中携带终端在RRC去激活态下的标识、RNA信息。
可以理解的是,第一接入网设备可以检测终端的数据传输情况,当检测到终端在一段时间内未存在数据传输,第一接入网设备可以向终端发送第一消息,以指示终端进入去激活态,或者,终端检测自身的数据传输情况,当检测到自身在一段时间内未存在数据传输,终端向第一接入网设备发起进入去激活态请求,第一接入网设备接收到终端的请求之后,向终端发送第一消息,以指示终端进入去激活态。
S402、终端执行小区重选操作。
其中,在终端接收到第一消息之后,终端执行小区重选操作,从而可以重选至其他小区中。
若终端在接收到第一消息后的预设时长内重选至第一小区,则执行下述S403。
其中,第一小区属于上述RNA信息所指示的小区,且不同于终端接收第一消息时所在的小区。假定终端在接收第一消息时所在的小区称为源小区,进行小区重选后,终端重选至第一小区,则第一小区与源小区不是同一小区。预设时长用于指定定时器的定时时长。可以根据实际应用情况设置预设时长,例如,预设时长可以设置为100ms。
或者,若终端在接收到第一消息后的预设时长内未重选至第一小区也未收到调度信息,则在预设时长后终端执行下述步骤S403。若终端在接收到第一消息后的预设时长内收到调度信息,则终端执行下述步骤S404。
作为一种示例性的实现方式,可选的,S401中所述的第一消息中携带定时信息,该定时信息用于指示上述预设时长。那么,终端在接收到第一消息之后,启用定时器,并设置定时器的定时时长为第一消息中携带的该预设时长。若在定时器超时之前,终端均未收到第一接入网设备的调度信息,则为了降低耗电量,终端可以执行上述S403所示的流程以进入去激活态。
作为另一种实现方式,终端在接收到第一消息之后,则即使该第一消息中未携带定时信息,也直接启用定时器,并设置定时器的定时时长为预设时长。
S403、终端释放或挂起配置的专用SRB以及复位配置的DRB对应的协议实体。
S404、终端保持在RRC连接态。
可以理解的是,若在定时器超时之前,终端接收到第一接入网设备发送的调度信息,表明终端有数据或信令传输需求,则终端停止定时器以及停止小区重选操作,并保持在RRC连接态,以便于终端根据第一接入网设备发送的调度信息传输数据或信令。
相应地,第一接入网设备在发送第一消息之后,也启用定时器,若第一接入网设备在发送第一消息后的预设时长内(即定时器超时之前),确定终端重选至第一小区,则第一接入网设备执行S405。或者,若第一接入网设备在发送第一消息后的预设时长内,未向终 端发送调度信息且确定终端未重选至第一小区,则在预设时长后第一接入网设备执行下述步骤S405。若第一接入网设备在发送第一消息后的预设时长内,向终端发送调度信息,则第一接入网设备执行下述步骤S406。
S405、第一接入网设备释放或挂起与终端对应配置的专用SRB、以及复位终端对应配置的DRB对应的协议实体。
S406、第一接入网设备指示终端保持在RRC连接态。
本申请实施例提供的通信方法,终端在接收到第一接入网设备发送的第一消息之后,并不立即进入去激活态,而是在满足特定条件下才进入去激活态,该特定条件包括:终端在接收到第一消息后的预设时长内重选至第一小区,或者,终端在接收到第一消息后的预设时长内未重选至第一小区也未收到调度信息。从而,在终端进入去激活态之后,减少上行信息(包括上行数据和上行信息)的发送量,降低终端的耗电量。
可以理解的,终端、第一接入网设备可以执行上述实施例中的部分或全部步骤,这些步骤或操作仅是示例,本申请实施例还可以执行其它操作或者各种操作的变形。此外,各个步骤可以按照上述实施例呈现的不同的顺序来执行,并且有可能并非要执行上述实施例中的全部操作。
结合图2或图4对应的方法,若处于去激活态的终端移动至第二接入网设备所覆盖的小区之后,需重新确定终端的锚点接入网设备,以便于终端与新的锚点接入网设备之间交互上、下行信息。基于此,本申请的实施例还提供一种通信方法,如图5所示,该方法包括S501至S506:
其中,S501至S502分别与上述S201、S202相同,此处不再赘述。
S503、若终端重选至第二接入网设备所覆盖的小区且存在待传输上行信息,则向第二接入网设备发送第二消息。
相应的,第二接入网设备接收终端发送的第二消息。
其中,重选的小区属于RNA信息所指示的小区。即第一接入网设备所覆盖的小区与重选的小区属于同一个RNA。
上行信息包括上行数据和上行信令。上行信令包括但不限于寻呼响应消息、RNA更新消息、TA更新消息。
第二消息中携带终端在RRC去激活态下的标识以及触发发送第二消息的原因的信息。
其中,RRC去激活态下的标识可以为I-RNTI。I-RNTI用于在RNA信息指示的小区范围内标识该终端。可选的,终端在RRC去激活态下的标识与第一接入网设备以及第一接入网设备的架构关联。具体地,终端在RRC去激活态下的标识携带第一接入网设备标识以及第一接入网设备是否为CU/DU架构相关的信息。第一接入网设备标识用于第二接入网设备寻址第一接入网设备。第一接入网设备的架构相关信息用于第二接入网设备判断是否迁移终端的锚点接入网设备。
触发发送第二消息的原因的信息(本文中称为原因信息)包括触发发送第二消息的原因值和其他用于判断是否迁移终端的锚点接入网设备的信息。示例性地,原因信息可以为上行缓存状态报告、上行数据所属的业务/切片类型和QoS类别信息、网络负荷。
作为一种举例,若第二消息中携带有QoS类别信息,该QoS类别信息指示终端对传输时延较为敏感,则在第二接入网设备接收到该第二消息后,为了降低终端的传输时延,可 以选择将锚点迁移至第二接入网设备,进而由距离终端较近的或者服务质量更好的第二接入网设备为终端提供覆盖服务,降低终端的传输时延,提升终端的服务质量。
可选的,第二消息中还包括短(short)媒体接入控制完整性验证值(Medium Access Control integrity protection,MAC-I),short MAC-I用于接入网设备对终端进行身份验证。
可选的,第二消息中还包括上行数据。示例性地。终端通过DRB对应的协议实体处理第二消息中的上行数据,本申请实施例不对处理第二消息的具体方式进行限制。
可选的,第二消息中还包括上行信令。示例性地。终端通过SRB0对应的协议实体处理第二消息中的上行信令,本申请实施例不对处理第二消息的具体方式进行限制。
可选地,第二消息中还包括状态转换请求,该状态转换请求用于终端请求由去激活态转移至连接态。
需要说明的是,当终端有上行数据或信令需要发送给网络时,终端可以通过随机接入过程或约定的资源向接入网设备发送上行数据或信令,例如,终端通过***信息广播的免授权共享(Grant-free)资源向接入网设备发送上行数据或信令。相应地,在本申请实施例中,终端发送上行数据的方式可以实现为:
在第一种实现方式中,终端需先进行RRC状态转换,之后,向第二接入网设备发送上行数据。示例性地,终端可以先向第二接入网设备发送包含状态转换请求的第二消息,之后,终端接收第二接入网设备发送的状态转换请求响应,若状态转换响应表明第二接入网设备确定终端可以由去激活态转换至连接态,则终端可以向第二接入网设备发送上行数据,以使得第二接入网设备处理上行数据,或者,若第二接入网设备确定不需迁移锚点(迁移锚点即将终端在核心网的入口由第一接入网设备迁移至第二接入网设备),则第二接入网设备将上行数据发送至第一接入网设备,并由第一接入网设备处理上行数据。
在第二种实现方式中,RRC状态转换与上行数据处理的流程可以同时进行。示例性地,终端可以向第二接入网设备发送包含状态转换请求、上行数据的第二消息,第二接入网设备根据第二消息中携带的状态转换请求指示终端进入连接态,并且,第二接入网设备处理第二消息中携带的上行数据。在第二种实现方式中,由于终端在RRC状态转换的过程中就可以发送上行数据,进而缩短了终端的业务时延。
在第三种实现方式中,终端可以直接向第二接入网设备发送上行数据,以使得第二接入网设备处理上行数据。即在第三种实现方式中,减少了RRC状态转换流程,进一步缩短终端的业务时延。
其中,上述仅以第二消息中包含状态转换请求,或者包含状态转换请求和上行数据,或者包含上行数据为例对本申请实施例中的第二消息进行说明,第二消息中具体包含的信息可以根据实际应用场景确定,本申请实施例不对此进行限制。
可选地,在第二接入网设备接收到第二消息之后,第二接入网设备可以向终端发送第二消息的响应消息。
示例性地,若第二消息携带有待传输的上行数据,则第二消息的响应消息可以反馈上行数据的传输情况。例如,若上行数据成功传输,则第二接入网设备向终端发送第二消息的响应消息,该响应消息指示终端的上行数据已被成功传输。
若第二消息为用于发起状态转换请求的消息,则在终端向第二接入网设备发送包含状 态转换请求的第二消息之后,第二接入网设备可以向终端发送用于指示终端状态的响应消息,例如,该响应消息可以指示终端维持在RRC去激活态,或者该响应消息可以指示终端进入RRC连接态。可以理解的是,若第二消息的响应消息指示终端维持在RRC去激活态,则可选地,第二接入网设备更新终端的上下文信息,例如,更新终端在去激活态下的标识和/或终端的RNA信息。
S504、第二接入网设备判断是否需要将终端在核心网的入口由第一接入网设备迁移至第二接入网设备。
若需迁移终端的锚点接入网设备,则执行S505和S506,若不需迁移终端的锚点接入网设备,则缓存上行信息(如果存在)以及执行S507。
可选地,第二接入网设备根据终端发送的所述第二消息中携带的原因信息判断是否迁移锚点接入网设备。
S505、第二接入网设备向第一接入网设备发送获取终端上下文信息的请求消息。
相应地,第一接入网设备接收第二接入网设备发送的请求消息。
其中,请求消息中携带终端在RRC去激活态下的标识。
可选地,在接收到第二消息之后,第二接入网设备根据第二消息中携带的终端在去激活态下的标识寻址第一接入网设备,示例性地,第二接入网设备根据终端在去激活态下的标识中携带的第一接入网设备标识寻址第一接入网设备。
S506、第一接入网设备向第二接入网设备发送终端的上下文信息。
相应地,第二接入网设备接收第一接入网设备发送的终端的上下文信息。
可以理解的是,在接收到终端的上下文信息之后,第二接入网设备可以根据终端的上下文信息生成终端对应的协议实体,并通过相应的协议实体处理终端的数据或信令。
S507、第二接入网设备向第一接入网设备发送上行信息。
相应地,第一接入网设备接收第二接入网设备发送的上行信息。
作为一种可能的实现方式,在接收到第二消息之后,第二接入网设备根据第二消息中携带的终端在去激活态下的标识寻址第一接入网设备,示例性地,第二接入网设备根据终端在去激活态下的标识中携带的第一接入网设备标识寻址第一接入网设备。
可选地,第二接入网设备向第一接入网设备发送如下格式的上行信息:
1、MAC PDU格式。
2、{MAC服务数据单元(service Data Unit,SDU),逻辑信道标识(Logical Channel Identity,LCID),I-RNTI,short MAC-I}组合的格式。
其中,第二接入网设备向第一接入网设备发送的上行信息的格式并不局限于所列举的两种格式。
可选地,第二接入网设备还可以通过接入网设备之间的接口封装协议向第一接入网设备发送该上行信息对应的原因信息。其中,原因信息的作用参见上文描述,这里不再赘述。
目前,3GPP LTE的窄带物联网(Narrow Band Internet-of-Things,NB-IoT)总是需迁移锚点接入网设备,在迁移锚点接入网设备的过程中,第二接入网设备需从第一接入网设备获取终端上下文信息等,增大信令开销和终端耗电。本申请实施例提供的通信方法,第二接入网设备能够根据第二消息中的原因信息判断是否迁移终端的锚点接入网设备,只有在满足迁移锚点接入网设备的条件下,才迁移终端的锚点接入网设备。示例性地,一方 面,本申请实施例可以在传输少量数据时,不迁移锚点接入网设备,进而缓解因第一接入网设备与第二接入网设备之间传输上下文信息等所导致的信令开销较大的问题。另一方面,若需迁移终端的锚点接入网设备,则由第二接入网设备为终端提供服务,由于第二接入网设备通常距离终端较近或者服务质量更好,从而,能够提升终端的通信质量。
结合图2、图4和图5对应的方法,可选地,若第二接入网设备确定不触发将终端在核心网的入口由第一接入网设备迁移至第二接入网设备,则由第一接入网设备处理终端的上行信息。基于此,在本申请实施例提供的一种实现方式中,如图6所示,在S507、第二接入网设备向第一接入网设备发送上行信息之后,第一接入网设备处理终端的上行信息的流程包括:
S601、第一接入网设备通过与终端的上行信息对应的协议实体处理上行信息。
可选地,第一接入网设备接收的上行信息的格式如下:
1、MAC PDU格式。
2、{MAC SDU,LCID,I-RNTI,short MAC-I}组合的格式。
其中,short MAC-I为终端对应的验证信息,用于终端的身份验证。
第二接入网设备还可以向第一接入网设备发送原因信息,原因信息的作用参见上文描述,这里不再赘述。
可选地,在S601之前,可以验证终端的身份信息,以确保无线接入网的安全。具体地,可以在上行信息中携带有终端对应的验证信息,第一接入网设备接收到终端的上行信息之后,根据终端的验证信息对终端进行身份验证,当验证通过后,第一接入网设备通过协议实体处理终端的上行信息。示例性地,验证信息可以为上述的short MAC-I,本申请实施例不对验证信息的具体形式加以限制。可选的,原因信息还可以用于指示是否更新终端对应的接入层安全密钥。可以理解的是,若第一接入网设备根据原因信息确定需更新终端的接入层安全密钥,则相应的可以更新验证信息,从而第一接入网设备使用更新后的验证信息对终端进行身份验证。
作为一种可能的实现方式,第一接入网设备可以根据上行信息中携带的LCID确定与终端的上行信息对应的协议实体,由协议实体依次对接收的上行信息进行处理,然后将处理后的上行信息发送至核心网设备,或者,将处理后的上行信息发送给RRC实体,由RRC实体对处理后的上行信息进行相应的操作。
结合图2、图4至图6对应的方法,可选地,若第二接入网设备确定触发将终端在核心网的入口由第一接入网设备迁移至第二接入网设备,则应当由第二接入网设备处理终端的上行信息。基于此,在本申请实施例提供的一种实现方式中,如图7所示,在S506、第一接入网设备向第二接入网设备发送终端的上下文信息之后,第二接入网设备处理终端的上行信息的流程包括:
S701、第二接入网设备根据终端的上下文信息生成终端的DRB对应的协议实体。
其中,第二接入网设备接收到终端的上下文信息之后,触发路径切换过程,将终端在核心网的入口从初始的锚点接入网设备(即第一接入网设备)迁移到第二接入网设备。路径切换的详细过程可以参考3GPP NR技术相关的文献。
在触发路径切换之后,第二接入网设备可以生成终端的DRB对应的协议实体,并可以通过生成的协议实体处理终端的上行信息。
结合图2、图4至图7对应的方法,本申请实施例还提供一种用于判断是否触发将终端在核心网的入口由第一接入网设备迁移至第二接入网设备的方法,如图8所示,该方法包括S801至S805:
S801、第二接入网设备获取第一接入网设备的架构指示信息。其中,架构指示信息用于指示第一接入网设备是否为CU/DU架构类型的接入网设备。
作为一种可能的实现方式,S801可以具体实现为:第一接入网设备向第二接入网设备发送架构指示信息。相应的,第二接入网设备接收第一接入网设备发送的架构指示信息。
具体地,通过基站间Xn接口初始化的Xn setup过程,第一接入网设备向第二接入网设备发送架构指示信息,或者,第一接入网设备通过配置更新(即configuration update)流程更新架构指示信息,并向第二接入网设备发送更新的架构指示信息。
S802、终端向第二接入网设备发送第二消息。
其中,第二消息与上述提及的第二消息的作用相同。这里不再赘述。
需要说明的是,S801和S802并没有时间先后顺序,既可以先执行S801,再执行S802,也可以先执行S802,再执行801,本申请实施例对此不进行限制。
S803、第二接入网设备确定第一接入网设备是否为CU/DU架构。
若第一接入网设备为CU/DU架构,则执行S804,否则,执行S805。
作为一种可能的实现方式,第二接入网设备根据第一接入网设备发送的架构指示信息确定第一接入网设备是否为CU/DU架构。
或者,第二接入网设备根据第二消息中的终端在RRC去激活态下的标识确定第一接入网设备是否为CU/DU架构。示例性地,终端在去激活态下的标识可以为I-RNTI,I-RNTI中可以携带有用于确定第一接入网设备架构的信息,例如,I-RNTI的最高20位bit可以用于标识第一接入网设备是否为CU/DU架构。可以理解的是,这里仅仅以I-RNTI的最高20位为标识位进行举例,具体I-RNTI中采用几个比特位和比特位的具***置,可以根据实际应用场景确定,本申请实施例不对此进行限制。
S804、触发将终端在核心网的入口由第一接入网设备迁移至第二接入网设备。
S805、根据原因信息判断是否触发将终端在核心网的入口由第一接入网设备迁移至第二接入网设备。
本申请实施例提供的通信方法,根据第一接入网设备的架构判断是否迁移终端的锚点接入网设备,若第一接入网设备为CU/DU架构,则将终端的锚点接入网设备迁移至第二接入网设备,由第二接入网设备处理终端的上行信息,与现有技术中,由CU/DU架构的第一接入网设备处理上行信息时,CU和DU之间需交互信令,增加了信令开销相比,减少了信令开销。
结合图2、图4至图8对应的方法,可选地,在本申请实施例中,还可以通过多个指标判断是否迁移终端的锚点接入网设备。基于此,在本申请实施例提供的另一种实现方式中,如图9所示,判断是否迁移终端的锚点接入网设备的流程还可以包括如下步骤:
S901、第二接入网设备根据原因信息和/或第一接入网设备的架构判断是否触发将终端在核心网的入口由第一接入网设备迁移至第二接入网设备。
可选地,当第一接入网设备为CU/DU架构时,如图8对应的方法,无论原因信息是否指示迁移锚点接入网设备,均将终端的锚点接入网设备迁移至第二接入网设备。当第一接 入网设备为非CU/DU架构时,进一步结合如图5至图8所示的流程,根据原因信息判断是否迁移锚点接入网设备。
或者,当第一接入网设备为CU/DU架构,且原因信息指示迁移锚点接入网设备时,才将终端的锚点接入网设备迁移至第二接入网设备。
需要说明的是,由于上行数据通常为MAC SDU格式,且该格式的上行数据通常先到达接入网设备的CU,所以,若采取如图1b所示的协议栈切分方式(即RLC及以下协议层部署在DU上,PDCP及以上协议层部署在CU上),则第一接入网设备中的CU需将上行数据送至DU,通过DU中部署的RLC实体处理上行数据,例如,由RLC实体对分段的上行数据进行组合,并将组合后的数据送至CU,由CU中部署的PDCP实体处理上行数据,例如,由PDCP实体对上行数据进行解压缩、解密操作。可见,为了实现对上行数据的处理,CU、DU之间需进行频繁的交互,这将导致较大的处理时延。
为了缓解CU、DU之间需频繁交互,导致处理时延的问题,结合图2、图4至图9对应的方法,当第一接入网设备为CU/DU架构(即第一接入网设备包括CU和DU)时,本申请实施例还提供一种通信方法,如图10,该方法包括S1001至S1005:
S1001、第一接入网设备向终端发送第一消息。
可选地,第一接入网设备中的DU向终端发送第一消息。
S1002、终端释放或挂起配置的专用信令无线承载(Signalling Radio Bearer,SRB)、以及复位配置的数据无线承载(Data Radio Bearer,DRB)对应的协议实体。
S1002可参见上述S202的描述,这里不再赘述。
S1003、第一接入网设备中的CU向DU发送第三消息。
相应地,第一接入网设备中的DU接收CU发送的第三消息。
其中,第三消息包括终端在RRC连接态下的标识,第三消息用于指示DU将终端转移至去激活态。示例性地,终端在RRC连接态下的标识为C-RNTI。
需要说明的是,上述S1001与S1003之间并无时间先后顺序。示例性地,终端可以先执行S1001、再执行是1003,也可以同时执行S1001、S1003。本申请实施例对此不进行限制。
S1004、第一接入网设备的DU释放或挂起与终端对应的配置的SRB、释放或挂起与终端对应的配置的DRB对应的RLC协议实体、以及复位MAC层的实体。
可选地,第一接入网设备还可以复位PHY实体。
示例性地,如图11所示,假定终端配置有4个专用无线承载和1个公共的SRB,其中,4个专用无线承载为SRB1、SRB2、DRB1、DRB2,公共的SRB为SRB0,则在CU向DU发送第三消息前后,DU中的协议栈分别如图11所示。相应地,DU执行的操作可以包括以下情况:DU需执行:
第一:DU释放或挂起SRB1和SRB2。具体地,DU释放或挂起SRB1、SRB2各自对应的RLC层实体。如图11中(a)所示,为DU释放相应承载以及协议实体的示意图,如图11中(b)所示,为DU挂起相应承载以及协议实体的示意图。
第二:DU复位公共的MAC层实体。
第三:释放或挂起终端的DRB对应的RLC协议实体。如图11中(a)所示,DU释放终端的DRB对应的RLC协议实体,如图11中(b)所示,DU挂起终端的DRB对应的RLC协议 实体。
可选地,在本步骤之后,第一接入网设备的DU向CU发送第三消息的响应消息,用以表明DU已经对终端的承载及协议实体进行了处理。
S1005、第一接入网设备的CU释放或挂起配置的SRB及配置的SRB在CU中对应的协议实体、复位配置的DRB及配置的DRB在CU中对应的协议实体、生成终端的DRB对应RLC协议实体。
可选地,CU在接收到DU发送的第三消息的响应消息之后,执行本步骤,或者,CU也可以在发送第三消息之后,直接执行本步骤。本申请实施例不对此进行限制。
示例性地,CU执行如下操作:
第一:CU释放或挂起SRB1和SRB2,具体地,CU释放SRB1、SRB2各自对应的RRC层、PDCP层实体。如图11中(a)所示,为CU释放终端的SRB1和SRB2对应的协议实体前后,终端协议栈的示意图,如图11中(b)所示,为CU挂起终端的SRB1和SRB2对应的协议实体前后,终端协议栈的示意图。
相应地,终端可以通过SRB0对应的RRC层实体处理待传输的上行信令,并通过SRB0传输处理后的上行信令。
第二:CU复位DRB1、DRB2各自对应的PDCP层实体和复位配置的SDAP层实体。并且,生成终端的DRB对应的RLC实体,从而,当终端有上行数据传输需求时,能够依次由SDAP层、PDCP层和RLC层的实体处理上行数据。
本申请实施例提供的通信方法,在终端进入去激活态之后,将终端的DRB对应的RLC协议实体部署在CU上,并且释放或挂起DU上的终端对应的RLC协议实体,从而当上行数据到达时,第一接入网设备中的CU可以通过部署的RLC协议实体处理MAC SDU格式的上行数据,再将处理后的上行数据依次送至PDCP、SDAP实体中进行处理,无需与DU进行频繁的交互,从而降低处理时延。
可以理解的是,本申请实施例中涉及的消息名称只是为了描述方便,在具体实现中还可以是其他的消息名称,本申请实施例中所例举的各种信息,可以是同时发送,比如在一条消息中发送,也可以不同时发送,比如在不同的消息中发送。
上述图2、图4至图11各个方法实施例中,是以接入网设备和终端为例进行说明,可以理解的是,上述各个方法实施例中由接入网设备实现的方法和功能也可以通过可用于接入网设备的芯片实现,由终端实现的方法和功能也可以通过可用于终端的芯片实现。
上述主要从不同网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是,网络侧设备(包括但不限于第一接入网设备和第二接入网设备)和终端为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。结合本申请中所公开的实施例描述的各示例的单元及算法步骤,本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能,但是这种实现不应认为超出本申请实施例的技术方案的范围。
本申请实施例可以根据上述方法示例对网络侧设备和终端等进行功能单元的划分,例如,可以对应各个功能划分各个功能单元,也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式 实现。需要说明的是,本申请实施例中对单元的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
图12示出了本申请实施例中提供的通信装置的一种示意性框图。该通信装置1200可以以软件的形式存在,也可以为终端,还可以为可用于终端的芯片。装置1200包括:处理单元1202和通信单元1203。例如,处理单元1202可以用于支持装置1200执行图2中的S201,图5中的S503,和/或用于本文所描述的方案的其它过程。通信单元1203用于支持装置1200和其他网元(例如网络侧设备)之间的通信。
可选的,通信装置1200还可以包括存储单元1201,用于存储装置1200的程序代码和数据,数据可以包括不限于原始数据或者中间数据等。
一种可能的方式中,处理单元1202可以是处理器或控制器,例如可以是中央处理器(Central Processing Unit,CPU),通用处理器,数字信号处理(Digital Signal Processing,DSP),应用专用集成电路(Application Specific Integrated Circuit,ASIC),现场可编程门阵列(Field-Programmable Gate Array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信单元1203可以是收发器、收发电路或通信接口等。存储单元1201可以是存储器。
一种可能的方式中,当处理单元1202为处理器,通信单元1203为收发器,存储单元1201为存储器时,本申请实施例所涉及的终端可以为图13所示的终端。
图13示出了本申请实施例中所涉及的终端的一种可能的设计结构的简化示意图。所述终端1300包括发射器1301,接收器1302和处理器1303。其中,处理器1303也可以为控制器,图13中表示为“控制器/处理器1303”。可选的,所述终端1300还可以包括调制解调处理器1305,其中,调制解调处理器1305可以包括编码器1306、调制器1307、解码器1308和解调器1309。
在一个示例中,发射器1301调节(例如,模拟转换、滤波、放大和上变频等)该输出采样并生成上行链路信号,该上行链路信号经由天线发射给上述实施例中所述的基站。在下行链路上,天线接收上述实施例中基站发射的下行链路信号。接收器1302调节(例如,滤波、放大、下变频以及数字化等)从天线接收的信号并提供输入采样。在调制解调处理器1305中,编码器1306接收要在上行链路上发送的业务数据和信令消息,并对业务数据和信令消息进行处理(例如,格式化、编码和交织)。调制器1307进一步处理(例如,符号映射和调制)编码后的业务数据和信令消息并提供输出采样。解调器1309处理(例如,解调)该输入采样并提供符号估计。解码器1308处理(例如,解交织和解码)该符号估计并提供发送给终端1300的已解码的数据和信令消息。编码器1306、调制器1307、解调器1309和解码器1308可以由合成的调制解调处理器1305来实现。这些单元根据无线接入网采用的无线接入技术(例如,LTE及其他演进***的接入技术)来进行处理。需要说明的是,当终端1300不包括调制解调处理器1305时,调制解调处理器1305的上述功能也可以由处理器1303完成。
处理器1303对终端1300的动作进行控制管理,用于执行上述本申请实施例中由终端1300进行的处理过程。例如,处理器1303还用于执行图2、图4至图6所示方法中涉及 终端的处理过程和/或本申请所描述的技术方案的其他过程。
进一步的,终端1300还可以包括存储器1304,存储器1304用于存储用于终端1300的程序代码和数据。
图14示出了本申请实施例中所涉及的另一种通信装置的一种可能的示例性框图,该装置1400可以以软件的形式存在,也可以为网络侧设备,例如基站,还可以为可以用于网络侧设备的芯片。装置1400包括:处理单元1402和通信单元1403。处理单元1402用于对装置1400的动作进行控制管理,例如,若该装置为第一接入网设备,处理单元1402用于支持装置1400执行图2中的S203,图4中的S405、S406,和/或用于本文所描述的技术的其它过程。若该装置为第二接入网设备,处理单元1402用于支持装置1400执行图5中的S504、S505、S507,图7中的S701,和/或用于本文所描述的技术的其它过程。通信单元1403用于支持装置1400与其他网络实体(例如终端)的通信。装置1400还可以包括存储单元1401,用于存储装置1400的程序代码和数据。
其中,处理单元1402可以是处理器或控制器,例如可以是CPU,通用处理器,DSP,ASIC,FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信单元1403可以是通信接口、收发器或收发电路等,其中,该通信接口是统称,在具体实现中,该通信接口可以包括多个接口,例如可以包括:基站和终端之间的接口和/或其他接口。存储单元1401可以是存储器。
当处理单元1402为处理器,通信单元1403为通信接口,存储单元1401为存储器时,本申请实施例所涉及的装置1400可以为图15所示的基站。
参阅图15所示,该基站1500包括:处理器1502、通信接口1503、存储器1501。可选的,基站1500还可以包括总线1504。其中,通信接口1503、处理器1502以及存储器1501可以通过总线1504相互连接;总线1504可以是外设部件互连标准(Peripheral Component Interconnect,简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture,简称EISA)总线等。所述总线1504可以分为地址总线、数据总线、控制总线等。为便于表示,图15中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
本领域普通技术人员可以理解:在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质,(例 如,软盘、硬盘、磁带)、光介质(例如,数字视频光盘(Digital Video Disc,DVD))、或者半导体介质(例如固态硬盘(Solid State Disk,SSD))等。
在本申请所提供的几个实施例中,应该理解到,所揭露的***,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络设备上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个功能单元独立存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用硬件加软件功能单元的形式实现。
通过以上的实施方式的描述,所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在可读取的存储介质中,如计算机的软盘,硬盘或光盘等,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述的方法。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,在本申请揭露的技术范围内的变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。
Claims (30)
- 一种通信方法,其特征在于,包括:从第一接入网设备接收第一消息,所述第一消息用于指示终端进入无线资源控制RRC去激活态,所述第一消息中携带所述终端在RRC去激活态下的标识以及无线接入网通知区RNA信息;释放或挂起配置的专用信令无线承载SRB,以及复位配置的数据无线承载DRB对应的协议实体。
- 根据权利要求1所述的方法,其特征在于,所述DRB对应的协议实体包括分组数据汇聚协议PDCP实体、无线链路控制RLC实体和公共的介质访问控制MAC实体,或者,所述DRB对应的协议实体包括PDCP实体、RLC实体、公共的MAC实体和业务数据匹配协议SDAP实体。
- 根据权利要求2所述的方法,其特征在于,所述释放或挂起配置的专用SRB,以及复位配置的DRB对应的协议实体,包括:若在接收到所述第一消息后的预设时长内未收到调度信息,则在所述预设时长后释放或挂起配置的专用SRB及对应的协议层实体、复位配置的专用DRB及对应的协议层实体。
- 根据权利要求2或3所述的方法,其特征在于,所述释放或挂起配置的专用SRB及对应的协议层实体、复位配置的专用DRB及对应的协议层实体,包括:在接收到所述第一消息后,执行小区重选操作;若在预设时长内重选至第一小区,则释放或挂起配置的专用SRB,以及复位配置的DRB对应的协议实体;所述第一小区属于所述RNA信息所指示的小区,且不同于接收所述第一消息所在的小区。
- 根据权利要求3或4所述的方法,其特征在于,所述第一消息中携带定时信息,所述定时信息用于指示所述预设时长。
- 根据权利要求1至5任一项所述的方法,其特征在于,所述方法还包括:若存在待传输上行数据,则通过所述上行数据对应的DRB传输所述上行数据;或若存在待传输上行信令,则通过公共信令无线承载传输所述上行信令。
- 根据权利要求1至6任一项所述的方法,其特征在于,在所述释放或挂起配置的专用SRB及对应的协议层实体、复位配置的专用DRB及对应的协议层实体之后,所述方法还包括:若重选至第二接入网设备所覆盖的小区且存在待传输上行信息,则向所述第二接入网设备发送第二消息,所述第二消息中携带所述终端在所述RRC去激活态下的标识以及触发发送第二消息的原因的信息;其中,所述重选的小区属于所述RNA信息所指示的小区;其中,所述终端在所述RRC去激活态下的标识与第一接入网设备以及第一接入网 设备的架构关联。
- 一种通信方法,其特征在于,包括:第一接入网设备向终端发送第一消息,所述第一消息用于指示所述终端进入无线资源控制RRC去激活态,所述第一消息中携带所述终端在所述RRC去激活态下的标识以及无线接入网通知区RNA信息;所述第一接入网设备释放或挂起与所述终端对应配置的专用信令无线承载SRB、以及复位所述终端对应配置的数据无线承载DRB对应的协议实体。
- 根据权利要求8所述的方法,其特征在于,所述DRB对应的协议实体包括分组数据汇聚协议PDCP实体、无线链路控制RLC实体和公共的介质访问控制MAC实体,或者,所述DRB对应的协议实体包括PDCP实体、RLC实体、公共的MAC实体和业务数据匹配协议SDAP实体。
- 根据权利要求9所述的方法,其特征在于,所述第一接入网设备释放或挂起与所述终端对应配置的专用SRB、以及复位所述终端对应配置的DRB对应的协议实体,包括:若在发送所述第一消息后的预设时长内未向所述终端发送调度信息,则在所述预设时长后释放或挂起与所述终端对应配置的专用SRB、以及复位所述终端对应配置的DRB对应的协议实体。
- 根据权利要求9或10所述的方法,其特征在于,若所述第一接入网设备包括集中单元CU和分布单元DU;所述第一接入网设备向终端发送第一消息,包括:所述第一接入网设备通过所述DU向所述终端发送第一消息。
- 根据权利要求11所述的方法,其特征在于,所述方法还包括:所述第一接入网设备中的CU向所述DU发送第三消息,其中,所述第三消息包括所述终端在RRC连接态下的标识,所述第三消息用于指示所述DU将所述终端转移至去激活态;所述第一接入网设备的DU释放或挂起与所述终端对应的所述配置的SRB及所述配置的SRB在所述DU中对应的协议实体、释放或挂起与所述终端对应的所述配置的DRB对应的无线链路控制RLC协议实体以及复位公共MAC层的实体;所述第一接入网设备的CU释放或挂起所述配置的SRB及所述配置的SRB在所述CU中对应的协议实体、复位所述配置的DRB及所述配置的DRB在所述CU中对应的协议实体、生成所述DRB对应RLC协议实体。
- 根据权利要求12所述的方法,其特征在于,在所述第一接入网设备的DU释放或挂起与所述终端对应的所述配置的SRB及所述配置的SRB在所述DU中对应的协议实体、释放或挂起与所述终端对应的所述配置的DRB对应的RLC协议实体以及复位公共MAC层的实体之后,所述方法还包括:所述第一接入网设备的DU向所述CU发送所述第三消息的响应消息。
- 根据权利要求8至13任一项所述的方法,其特征在于,所述方法还包括:所述第一接入网设备接收第二接入网设备转发的所述终端的上行信息,所述上行信息中携带所述终端在所述RRC去激活态下的标识;所述第一接入网设备通过与所述终端的上行信息对应的协议实体处理所述上行信息。
- 根据权利要求14所述的方法,其特征在于,所述上行信息中携带所述终端对应的验证信息;在所述第一接入网设备通过所述协议实体处理所述上行信息之前,所述方法还包括:所述第一接入网设备根据所述验证信息对所述终端进行身份验证;验证通过后,所述第一接入网设备通过所述协议实体处理所述上行信息。
- 根据权利要求14或15所述的方法,其特征在于,所述上行信息中携带原因信息;所述方法还包括:所述第一接入网设备根据所述原因信息确定是否更新所述终端对应的接入层安全密钥。
- 根据权利要求8至13任一项所述的方法,其特征在于,所述方法还包括:所述第一接入网设备接收第二接入网设备发送的获取终端上下文的请求消息,所述请求消息中携带所述终端在所述RRC去激活态下的标识;所述第一接入网设备向所述第二接入网设备发送所述终端的上下文信息。
- 根据权利要求17所述的方法,其特征在于,在所述第一接入网设备接收第二接入网设备发送的获取终端上下文的请求消息之前,所述方法还包括:所述第一接入网设备向第二接入网设备发送架构指示信息,所述架构指示信息用于指示所述第一接入网设备是否为CU/DU架构类型的接入网设备。
- 一种通信方法,其特征在于,包括:第二接入网设备接收终端发送的第二消息,所述第二消息中携带所述终端在无线资源控制RRC去激活态下的标识以及触发发送第二消息的原因的信息;若所述第二接入网设备根据所述触发发送第二消息的原因的信息确定触发将所述终端在所述核心网的入口由第一接入网设备迁移至第二接入网设备,则所述第二接入网设备向所述第一接入网设备发送获取所述终端上下文信息的请求消息;所述第二接入网设备接收所述第一接入网设备发送的所述终端的上下文信息。
- 根据权利要求19所述的方法,其特征在于,在所述第二接入网设备接收所述第一接入网设备发送的所述终端的上下文信息之后,所述方法还包括:所述第二接入网设备根据所述终端的上下文信息生成所述终端的数据无线承载DRB对应的协议实体。
- 根据权利要求20所述的方法,其特征在于,所述DRB对应的协议实体包括分组数据汇聚协议PDCP实体、无线链路控制RLC实体和公共的介质访问控制MAC实体;或者,所述DRB对应的协议实体包括PDCP实体、RLC实体、公共的MAC实体和业务数据匹配协议SDAP实体。
- 根据权利要求19至21任一项所述的方法,其特征在于,所述方法还包括:所述第二接入网设备确定所述第一接入网设备是否为集中单元CU/分布单元DU架构;若所述第一接入网设备为CU/DU架构,则触发将所述终端在所述核心网的入口由第一接入网设备迁移至第二接入网设备。
- 根据权利要求22所述的方法,其特征在于,所述第二接入网设备确定所述第一接入网设备是否为CU/DU架构,包括:所述第二接入网设备接收所述第一接入网设备发送的架构指示信息;所述第二接入网设备根据所述架构指示信息确定所述第一接入网设备是否为CU/DU架构;或所述第二接入网设备根据所述终端在所述RRC去激活态下的标识确定所述第一接入网设备是否为CU/DU架构。
- 根据权利要求19至23任一项所述的方法,其特征在于,所述方法还包括:若所述第二接入网设备根据所述原因信息确定不触发将所述终端在所述核心网的入口由第一接入网设备迁移至第二接入网设备,则所述第二接入网设备向所述第一接入网设备发送所述上行信息。
- 一种通信装置,其特征在于,用于支持如权利要求1至7中任一项所述的方法的执行。
- 一种通信装置,其特征在于,用于支持如权利要求8至18中任一项所述的方法的执行。
- 一种通信装置,其特征在于,用于支持如权利要求19至24中任一项所述的方法的执行。
- 一种可读存储介质,其特征在于,包括程序或指令,当所述程序或指令被执行时,如权利要求1至7中任一项所述的方法被实现。
- 一种可读存储介质,其特征在于,包括程序或指令,当所述程序或指令被执行时,如权利要求8至18中任一项所述的方法被实现。
- 一种可读存储介质,其特征在于,包括程序或指令,当所述程序或指令被执行时,如权利要求19至24中任一项所述的方法被实现。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP19760077.8A EP3751954A1 (en) | 2018-03-01 | 2019-04-12 | Communication method and apparatus |
US17/003,086 US11510175B2 (en) | 2018-03-01 | 2020-08-26 | Method and device for sending uplink data by an inactive terminal |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201810172450.7 | 2018-03-01 | ||
CN201810172450.7A CN110225600B (zh) | 2018-03-01 | 2018-03-01 | 通信方法及装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/003,086 Continuation US11510175B2 (en) | 2018-03-01 | 2020-08-26 | Method and device for sending uplink data by an inactive terminal |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019166032A1 true WO2019166032A1 (zh) | 2019-09-06 |
Family
ID=67805657
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/082443 WO2019166032A1 (zh) | 2018-03-01 | 2019-04-12 | 通信方法及装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US11510175B2 (zh) |
EP (1) | EP3751954A1 (zh) |
CN (2) | CN113891353A (zh) |
WO (1) | WO2019166032A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112911641A (zh) * | 2019-12-03 | 2021-06-04 | 华为技术有限公司 | 通信处理方法和通信处理装置 |
WO2021164287A1 (zh) * | 2020-02-21 | 2021-08-26 | 华为技术有限公司 | 一种通信方法及装置 |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112584550B (zh) * | 2019-09-27 | 2023-12-15 | 华为技术有限公司 | 一种双连接管理方法和通信装置 |
EP4025007A4 (en) * | 2019-09-29 | 2022-09-14 | Huawei Technologies Co., Ltd. | COMMUNICATION METHOD AND COMMUNICATION DEVICE |
WO2021062676A1 (zh) * | 2019-09-30 | 2021-04-08 | 华为技术有限公司 | 通信方法和装置 |
CN112839329B (zh) * | 2019-11-06 | 2022-07-22 | ***通信有限公司研究院 | 一种验证方法、装置、设备及计算机可读存储介质 |
CN114258151A (zh) * | 2020-09-21 | 2022-03-29 | 华为技术有限公司 | 一种计算数据传输方法及装置 |
CN114390633B (zh) * | 2020-10-16 | 2024-05-14 | ***通信有限公司研究院 | 一种信号中继传输方法、装置、设备及可读存储介质 |
CN114499795A (zh) * | 2020-11-12 | 2022-05-13 | ***通信有限公司研究院 | 一种pdcp复制功能的确定方法、装置和存储介质 |
EP4247104A1 (en) * | 2020-12-10 | 2023-09-20 | Shanghai Langbo Communication Technology Company Limited | Method and apparatus of communication node used for radio communication |
CN114630341A (zh) * | 2020-12-11 | 2022-06-14 | 华为技术有限公司 | 通信方法、装置及*** |
CN114697990A (zh) * | 2020-12-31 | 2022-07-01 | 华为技术有限公司 | 一种通信方法及装置 |
CN117693004A (zh) * | 2022-03-18 | 2024-03-12 | 上海朗帛通信技术有限公司 | 一种被用于无线通信的通信节点中的方法和装置 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102340886A (zh) * | 2010-07-22 | 2012-02-01 | 大唐移动通信设备有限公司 | 一种重建立rrc连接的方法、装置及*** |
US20120069728A1 (en) * | 2009-06-01 | 2012-03-22 | Sung Hoon Jung | Apparatus and method for processing failure of component carrier in multiple carrier system |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101115292B (zh) * | 2006-07-27 | 2011-06-08 | 华为技术有限公司 | 寻呼并连接终端的方法及快速激活数据传输的终端和*** |
CA2832067C (en) * | 2011-04-01 | 2019-10-01 | Interdigital Patent Holdings, Inc. | Method and apparatus for controlling connectivity to a network |
WO2014185702A1 (en) * | 2013-05-15 | 2014-11-20 | Lg Electronics Inc. | Method for performing a drx operation in a wireless communication system and a device therefor |
WO2017173586A1 (zh) * | 2016-04-05 | 2017-10-12 | 华为技术有限公司 | 一种用户终端的管理方法及相关设备 |
EP3244672B1 (en) | 2016-05-09 | 2020-12-09 | HTC Corporation | Handling state change of radio resource control |
EP3459277B1 (en) * | 2016-05-18 | 2021-08-18 | Telefonaktiebolaget LM Ericsson (publ) | Methods of resuming a radio bearer and related wireless terminals and network nodes |
CN107645779B (zh) * | 2016-07-22 | 2019-12-13 | 电信科学技术研究院 | 一种数据发送、传输方法及装置 |
US10820363B2 (en) * | 2016-07-28 | 2020-10-27 | Lg Electronics Inc. | Method for performing RRC connection re-establishment procedure and device supporting the same |
US10484931B2 (en) * | 2016-12-23 | 2019-11-19 | Ofinno, Llc | Licensed assisted access radio link failure |
US11109286B2 (en) * | 2017-01-05 | 2021-08-31 | Nec Corporation | Radio terminal, base station, and methods and non-transitory computer-readable media therefor |
CN106714315B (zh) * | 2017-01-13 | 2019-02-15 | 北京小米移动软件有限公司 | 信息反馈方法、装置、基站和用户设备 |
US20180352601A1 (en) * | 2017-05-31 | 2018-12-06 | Electronics And Telecommunications Research Institute | Method for communicating in mobile communication system and apparatus for the same |
EP4156783A1 (en) * | 2018-04-05 | 2023-03-29 | Samsung Electronics Co., Ltd. | Method and apparatus for operating protocol layer of terminal in inactive mode in next-generation mobile communication system |
KR102684275B1 (ko) * | 2018-09-18 | 2024-07-12 | 삼성전자 주식회사 | 차세대 이동 통신 시스템에서 rrc 비활성화 모드 단말의 선택된 plmn을 보고하는 방법 및 장치 |
-
2018
- 2018-03-01 CN CN202111081604.XA patent/CN113891353A/zh active Pending
- 2018-03-01 CN CN201810172450.7A patent/CN110225600B/zh active Active
-
2019
- 2019-04-12 EP EP19760077.8A patent/EP3751954A1/en not_active Withdrawn
- 2019-04-12 WO PCT/CN2019/082443 patent/WO2019166032A1/zh unknown
-
2020
- 2020-08-26 US US17/003,086 patent/US11510175B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120069728A1 (en) * | 2009-06-01 | 2012-03-22 | Sung Hoon Jung | Apparatus and method for processing failure of component carrier in multiple carrier system |
CN102340886A (zh) * | 2010-07-22 | 2012-02-01 | 大唐移动通信设备有限公司 | 一种重建立rrc连接的方法、装置及*** |
Non-Patent Citations (2)
Title |
---|
HUAWEI: "Discussion on Inactive Mode for E-UTRA connected to 5GC", 3GPP TSG-RAN WG2 MEETING #99, R2-1708552, 25 August 2017 (2017-08-25), XP051318404 * |
HUAWEI: "The content of AS context for inactive UE", 3GPP TSG-RAN WG2#101, R2-1803268, 15 February 2018 (2018-02-15), XP051399745 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112911641A (zh) * | 2019-12-03 | 2021-06-04 | 华为技术有限公司 | 通信处理方法和通信处理装置 |
WO2021164287A1 (zh) * | 2020-02-21 | 2021-08-26 | 华为技术有限公司 | 一种通信方法及装置 |
Also Published As
Publication number | Publication date |
---|---|
CN113891353A (zh) | 2022-01-04 |
US20200389867A1 (en) | 2020-12-10 |
CN110225600B (zh) | 2021-09-07 |
CN110225600A (zh) | 2019-09-10 |
EP3751954A1 (en) | 2020-12-16 |
US11510175B2 (en) | 2022-11-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019166032A1 (zh) | 通信方法及装置 | |
US11405922B2 (en) | Method for reconfiguring data radio bearer and user equipment | |
US10999880B2 (en) | Method for reconfiguring data radio bearer and user equipment | |
EP3017636B1 (en) | User plane idle mode buffering within software defined network architecture | |
CN113475109A (zh) | 随着rrc恢复完成之类的消息的早期测量报告 | |
WO2014169748A1 (zh) | 一种双连接的实现方法及基站 | |
WO2014198133A1 (zh) | 一种数据无线承载drb的资源分配方法及装置 | |
JPWO2018066702A1 (ja) | 無線通信システム、ネットワーク装置及び無線通信方法 | |
WO2014106396A1 (zh) | 集群登记的方法及装置 | |
WO2018202131A1 (zh) | 通信方法、装置及*** | |
CN111586735B (zh) | 一种通信方法及装置 | |
JP6754900B2 (ja) | 無線通信システム、ユーザ装置、無線基地局及び無線通信方法 | |
CN114467361A (zh) | 在多无线电双连接中恢复无线电连接 | |
WO2017166223A1 (zh) | 无线承载管理方法、装置及*** | |
WO2022206393A1 (zh) | 通信方法及装置 | |
WO2021189496A1 (zh) | 用于网络切片的数据传输方法及设备 | |
WO2017166291A1 (zh) | 一种通信方法、终端、基站和移动性管理设备 | |
WO2023226647A1 (zh) | 数据传输方法、网络设备及计算机可读存储介质 | |
WO2024138295A1 (zh) | 用于传输数据的方法、终端设备以及网络设备 | |
WO2023226649A1 (zh) | 网络配置方法、用户设备、网络设备及计算机存储介质 | |
WO2018201973A1 (zh) | 一种消息传输的方法及装置 | |
WO2014198175A1 (zh) | 一种业务释放方法、基站及终端 | |
WO2021026114A1 (en) | Network-triggered paging for multi-radio dual connectivity |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19760077 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019760077 Country of ref document: EP Effective date: 20200909 |