WO2020135645A1 - 无线通信的方法和装置 - Google Patents

无线通信的方法和装置 Download PDF

Info

Publication number
WO2020135645A1
WO2020135645A1 PCT/CN2019/128923 CN2019128923W WO2020135645A1 WO 2020135645 A1 WO2020135645 A1 WO 2020135645A1 CN 2019128923 W CN2019128923 W CN 2019128923W WO 2020135645 A1 WO2020135645 A1 WO 2020135645A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
information
duration
access device
cell
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/128923
Other languages
English (en)
French (fr)
Inventor
戴明增
石小丽
张宏卓
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to BR112021012796A priority Critical patent/BR112021012796A2/pt
Priority to EP19902336.7A priority patent/EP3890405A4/en
Publication of WO2020135645A1 publication Critical patent/WO2020135645A1/zh
Priority to US17/362,909 priority patent/US12089151B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H04W52/0258—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
    • 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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the embodiments of the present application relate to the field of communication, and more specifically, to a method and apparatus for wireless communication and a communication device.
  • a terminal communication state is known, that is, a radio resource control (radio resource control (RRC) deactivation state, referred to as an inactive state for short).
  • RRC radio resource control
  • the core network device, the access device, and the terminal device all retain the context information of the terminal device.
  • a radio access network Radio Access Network, RAN
  • RAN-based Notification Area RAN-based Notification Area, RNA
  • the RNA is composed of one cell or multiple cells, if multiple It consists of multiple cells.
  • the multiple cells belong to the same base station or different base stations.
  • the different base stations may be base stations of the same radio access type (Radio Access Type, RAT) or base stations of different RATs.
  • the terminal equipment RNA In the inactive state, when the terminal equipment RNA moves internally, it will not feed back the channel quality status to the network side (for example, access equipment or core network equipment), and the network side needs to be notified after the RNA is removed.
  • the network side for example, access equipment or core network equipment
  • the inactive state terminal device #X resides in the base station #Y.
  • the inactive state terminal device #X may communicate with the new serving base station (for example, cell reselection).
  • the base station resides, and is referred to as base station #Z) for downlink synchronization, such as data transmission, RNA update (RNAU), tracking area (TAing) update, registration area (registration area) update, etc., that is, the base station #Z may become the resident base station of terminal device #X.
  • base station #Z needs to reassign RNA to terminal device #X.
  • RNA distribution may cause frequent occurrence of RNAU in the terminal device, resulting in increased signaling overhead, increased power consumption of the terminal device, and affected user experience.
  • the base station will set a timer for the inactive state. Specifically, when the terminal device enters the inactive state, the timer starts. If the timer expires, the terminal device has not yet For data transmission, the base station can further decide the state of the terminal device, for example, the terminal device can be put into an idle (IDLE) state; or, the terminal device can be paged to put the terminal device into a connected state, etc.
  • IDLE idle
  • the terminal device can be paged to put the terminal device into a connected state, etc.
  • the timer may cause the UE to initiate a communication link with the base station shortly after the base station finds the timer and then controls the terminal device to enter the IDLE state, thereby causing an increase in signaling overhead.
  • the setting of the timer duration is unreasonable, it may cause an increase in signaling overhead, increase power consumption of the terminal device, and affect the user experience.
  • the present application provides a method and apparatus for wireless communication and a communication device, which can realize reasonable configuration of relevant parameters in an inactive state, and reduce signaling overhead and power consumption of a terminal device.
  • a method of wireless communication including: determining reference information, the reference information including information of a first duration and/or information of a first cell, the first duration including a terminal device being in a deactivated state
  • the duration of the first cell includes the cell where the terminal device updates the RNAU based on the notification area of the radio access network; and sends the reference information.
  • the terminal device or the source resident access device of the terminal device records the duration of the terminal device in the inactive state, and the target resident access device of the terminal device is based on the duration Configure the terminal for the inactive state timer, which can provide a reference and basis for the timer setting, thereby avoiding the signaling overhead caused by the unreasonable timer setting; or, by making the terminal device or the source of the terminal device reside access
  • the device records the cell where the terminal device was in when the RNAU occurred, and enables the target resident access device of the terminal device to configure RNA for the terminal device based on the cell, so that it can provide a reference and basis for the RNA setting, thereby avoiding the failure of the RNA setting.
  • the signaling overhead caused by reasonableness can reduce the power consumption of the terminal device and improve the user experience.
  • information of the first duration may be understood as related information of the first duration, or information for determining the first duration.
  • the information (or related information) of the first duration may include indication information that can directly indicate the first duration.
  • the information (or related information) of the first duration may include indication information that can indirectly determine the first duration.
  • the information (or related information) of the first duration may include indication information of the start time of the first duration and indication information of the end time of the first duration.
  • the information (or related information) of the first duration may include indication information of the time when the terminal device enters the deactivated state and indication information of the time when the terminal device ends the deactivated state.
  • the method provided in the first aspect may be executed by a first access device, and the receiving end of the reference information may be a second access device.
  • the method provided in the first aspect may be executed by the terminal device, and the receiving end of the reference information may be a second access device.
  • the second access device may be the target access device to which the terminal device needs to be switched
  • the first access device may be the source access device of the terminal device.
  • the first access device may be a primary base station
  • the second access device may be a secondary base station.
  • the first access device may be the original camping base station of the terminal device
  • the second access device may be the new camping base station of the terminal device
  • the terminal device may be in the deactivated state multiple times.
  • the first duration may be multiple.
  • the multiple deactivation states correspond to multiple first durations, that is, one first duration may include the corresponding duration in the deactivation state once.
  • the terminal device updates the RNAU based on the notification area of the radio access network.
  • the first cell may include some or all of the one or more cells.
  • the reference information further includes information of a second cell corresponding to the first duration, and the second cell includes a cell where the terminal device is in a deactivated state corresponding to the first duration.
  • the target camping access device of the terminal device can configure the timer for the inactive state for the terminal device based on the relevant information of the cell corresponding to the first duration, so that the set timer can further match the actual time of the terminal device
  • the communication status further improves the practicability of this application.
  • the reference information further includes information of a deactivation state type corresponding to the first duration, wherein the deactivation state type includes a session deactivation state type, a data radio bearer deactivation state type, or terminal device deactivation Activation status type.
  • the deactivation state type includes a session deactivation state type, a data radio bearer deactivation state type, or terminal device deactivation Activation status type.
  • the deactivation state type corresponding to the first duration can be understood as: if the first duration corresponds to the first deactivation state type, the first duration can include the deactivation of the terminal device in the first deactivation state type The duration of the activation state.
  • the reference information further includes information about the type of RNAU corresponding to the first cell, where the type of RNAU includes the type of RNAU triggered periodically or the type of RNAU triggered by terminal device movement.
  • the "type of RNAU corresponding to the first cell” may be understood as: the type of RNAU occurring in the first cell.
  • the method further includes: recording the reference information in the history information of the terminal device.
  • reference information can be carried based on existing signaling or information, and signaling overhead can be further saved.
  • the method further includes: receiving request information; and the sending the reference information includes sending the reference information according to the request information.
  • the request information includes type indication information
  • the type indication information is used to indicate a first deactivation state type, where the first deactivation state type includes a session deactivation state type and a data radio bearer deactivation state
  • the type or terminal device deactivation state type, and the determination reference information include: information for determining the first duration according to the type indication information.
  • the type of deactivation state corresponding to the first duration determined according to the type indication information is the first type of deactivation state.
  • the target resident access device of the terminal device can configure the terminal device with an inactive state timer for the corresponding deactivation type based on the deactivation type corresponding to the first duration, thereby enabling the set timer to be further matched
  • the actual communication status of the terminal device further improves the practicability of this application.
  • the method further includes: receiving first indication information sent by a third access device, where the first indication information is used to indicate the first duration Or receiving second indication information sent by a third access device, where the second indication information is used to indicate the moment when the terminal device enters the deactivated state and the moment when the terminal device ends the zone activation state; wherein, the The first access device includes a centralized unit CU, the third access device includes a distributed unit DU, or the first access device includes a centralized unit control plane CU-CP entity, and the third access device Including a centralized unit user plane CU-UP entity; wherein, the CU is configured with at least one protocol layer of a packet data convergence layer protocol PDCP layer and a radio resource control RRC layer; the DU is configured with a radio link control RLC layer , Media access control at least one protocol layer of MAC layer and physical PHY layer.
  • the CU is configured with at least one protocol layer of a packet data convergence layer protocol PDCP layer and a radio resource control RRC layer
  • the second indication information is used to indicate the moment when the terminal device enters the deactivated state and the moment when the terminal device ends the zone activation state
  • the second indication information is one
  • the information about the time when the terminal device enters the deactivated state and the information about the time when the terminal device ends the zone activation state are carried in the same second indication information, or that is, the time when the terminal device enters the deactivated state And the information at the time when the terminal device ends the zone activation state can be sent synchronously.
  • the second indication information is used to indicate the moment when the terminal device enters the deactivated state and the moment when the terminal device ends the zone activation state
  • the second indication information is two
  • the terminal The information about the time when the device enters the deactivated state and the information about the time when the terminal device ends the zone activation state are carried in the different second indication information, or the information about the time when the terminal device enters the deactivated state and The information at the time when the terminal device ends the zone activation state may be sent asynchronously.
  • the sending the reference information includes sending the reference information to a second access device , wherein the first access device includes a DU, the second access device includes a CU, or the first access device includes a CU-UP entity, and the second access device includes a CU-CP entity; wherein At least one protocol layer of PDCP layer and RRC layer is configured in the CU; at least one protocol layer of RLC layer, MAC layer and PHY layer is configured in the DU.
  • the method further includes: adjusting the duration of the deactivation timer of the terminal device according to the first duration.
  • the method further includes: configuring a notification area RNA based on a radio access network for the terminal device according to the first cell.
  • a method for wireless communication including: receiving reference information, the reference information including information of a first duration and/or information of a first cell, the first duration including a terminal device being in a deactivated state
  • the duration of the first cell includes the cell where the terminal device updates the RNAU based on the notification area of the radio access network; adjust the duration of the deactivation timer of the terminal device according to the first duration; or
  • a notification area RNA based on a radio access network is configured for the terminal device.
  • the terminal device or the resident access device of the terminal device records the duration of the terminal device in the inactive state, so that the access device configures the terminal device for the inactive state based on the duration
  • the timer can provide a reference and basis for the timer setting, thereby avoiding the signaling overhead caused by the unreasonable timer setting; or, by making the terminal device or the resident access device of the terminal device record the terminal device where the RNAU occurred Cells, and allows the access device to configure RNA for terminal devices based on the cell, thereby providing reference and basis for RNA settings, thereby avoiding signaling overhead caused by unreasonable RNA settings, and in turn, reducing the terminal device’s Power consumption advances to improve user experience.
  • adjusting the duration of the deactivation state timer corresponding to the terminal device according to the first duration may be understood as adjusting the duration of the dedicated timer corresponding to the terminal device according to the first duration.
  • adjusting the duration of the deactivation timer corresponding to the terminal device according to the first duration may be understood as adjusting the common timer corresponding to all terminal devices in the cell where the terminal device is located according to the first duration Duration.
  • adjusting the duration of the deactivation state timer corresponding to the terminal device according to the first duration may be understood as adjusting corresponding to all terminal devices within the coverage of the service access device of the terminal device according to the first duration The duration of the common timer.
  • adjusting the duration of the deactivation timer corresponding to the terminal device according to the first duration may be understood as adjusting all terminal devices in the first terminal device group including the terminal device according to the first duration The duration of the corresponding common timer.
  • configuring the terminal device with a notification area RNA based on a radio access network may be understood as configuring dedicated RNA for the terminal device according to the first cell. And, in this case, the RNA can be sent to the terminal device through professional signaling of the terminal device.
  • configuring the terminal device with a notification area RNA based on a radio access network may be understood as configuring the cell in which the terminal device is located according to the first cell (or the cell Public RNA within all terminal devices). And, in this case, the RNA can be sent to the system information of the cell.
  • configuring the terminal device with a notification area RNA based on a radio access network may be understood as configuring a service access device for the terminal device according to the first cell (or Public RNA of all terminal equipment within the coverage of the service access equipment).
  • configuring the terminal device with a notification area RNA based on a radio access network may be understood as targeting the first terminal device group including the terminal device according to the first cell configuration Of public RNA.
  • information of the first duration may be understood as related information of the first duration, or information for determining the first duration.
  • the information (or related information) of the first duration may include indication information that can directly indicate the first duration.
  • the information (or related information) of the first duration may include indication information that can indirectly determine the first duration.
  • the information (or related information) of the first duration may include indication information of the start time of the first duration and indication information of the end time of the first duration.
  • the information (or related information) of the first duration may include indication information of the time when the terminal device enters the deactivated state and indication information of the time when the terminal device ends the deactivated state.
  • the method provided in the second aspect may be executed by a second access device, and the sending end of the reference information may be the first access device.
  • the method provided in the second aspect may be executed by the second access device, and the sending end of the reference information may be a terminal device.
  • the second access device may be the target access device to which the terminal device needs to be switched
  • the first access device may be the source access device of the terminal device.
  • the first access device may be a primary base station
  • the second access device may be a secondary base station.
  • the first access device may be the original camping base station of the terminal device
  • the second access device may be the new camping base station of the terminal device
  • the terminal device may be in the deactivated state multiple times.
  • the first duration may be multiple.
  • the multiple deactivation states correspond to multiple first durations, that is, one first duration may include the corresponding duration in the deactivation state once.
  • the terminal device updates the RNAU based on the notification area of the radio access network.
  • the first cell may include some or all of the one or more cells.
  • the reference information further includes information of a second cell corresponding to the first duration, and the second cell includes a cell where the terminal device is in a deactivated state corresponding to the first duration.
  • the adjusting the duration of the deactivation timer of the terminal device according to the first duration includes adjusting the duration of the deactivation timer of the terminal device in the third cell according to the first duration Duration, where the third cell corresponds to the second cell.
  • the third cell corresponds to the second cell can be understood as that the third cell and the second cell are the same cell.
  • the third cell corresponds to the second cell may be understood as the similarity of the preset parameter between the third cell and the second cell is greater than or equal to the preset similarity.
  • the reference information further includes information of a deactivation state type corresponding to the first duration, wherein the deactivation state type includes a session deactivation state type, a data radio bearer deactivation state type, or terminal device deactivation Activation status type.
  • the deactivation state type includes a session deactivation state type, a data radio bearer deactivation state type, or terminal device deactivation Activation status type.
  • the adjusting the duration of the deactivation state timer of the terminal device according to the first duration includes adjusting the deactivation corresponding to the first duration of the terminal device according to the first duration The duration of the state type deactivation state timer.
  • the reference information further includes information about the type of RNAU corresponding to the first cell, where the type of RNAU includes the type of RNAU triggered periodically or the type of RNAU triggered by terminal device movement.
  • the "type of RNAU corresponding to the first cell” may be understood as: the type of RNAU occurring in the first cell.
  • the reference information is carried in the history information of the terminal device.
  • the method further includes sending request information, where the request information is used to request the reference information.
  • the request information includes type indication information, and the type indication information is used to indicate a first deactivation state type, where the first deactivation state type includes a session deactivation state type and a data radio bearer deactivation state Type or terminal device deactivation status type.
  • the method is performed by a second access device, and the receiving reference information includes: receiving information of a first duration sent by the first access device, where the first access device includes distributed Unit DU, the second access device includes a centralized unit CU, or the first access device includes a centralized unit user plane CU-UP entity, and the second access device includes a centralized unit control plane CU- CP entity; wherein, at least one layer of PDCP layer and RRC layer is configured in the CU; at least one layer of RLC layer, MAC layer and PHY layer is configured in the DU.
  • an apparatus for wireless communication including: a processing unit for determining reference information, the reference information including information of a first duration and/or information of a first cell, the first duration including a terminal
  • the first cell includes a cell in which the terminal device updates the RNAU based on the notification area of the radio access network; a transceiver unit is used to send the reference information.
  • the apparatus may be configured in or itself is the first access device, and the receiving end of the reference information may be the second access device.
  • the apparatus may be configured in or itself is a terminal device, and the receiving end of the reference information may be a second access device.
  • the second access device may be the target access device to which the terminal device needs to be switched
  • the first access device may be the source access device of the terminal device.
  • the first access device may be a primary base station
  • the second access device may be a secondary base station.
  • the first access device may be the original camping base station of the terminal device
  • the second access device may be the new camping base station of the terminal device
  • the reference information further includes information of a second cell corresponding to the first duration, and the second cell includes a cell where the terminal device is in a deactivated state corresponding to the first duration.
  • the reference information further includes information of a deactivation state type corresponding to the first duration, wherein the deactivation state type includes a session deactivation state type, a data radio bearer deactivation state type, or terminal device deactivation Activation status type.
  • the deactivation state type includes a session deactivation state type, a data radio bearer deactivation state type, or terminal device deactivation Activation status type.
  • the reference information further includes information about the type of RNAU corresponding to the first cell, where the type of RNAU includes the type of RNAU triggered periodically or the type of RNAU triggered by terminal device movement.
  • the target resident access device of the terminal device can configure the terminal device with RNA based on the relevant information of the RNAU type, so that the set RNA can further match the actual communication state of the terminal device, further improving the application Practicality.
  • the processing unit is also used to record the reference information in the history information of the terminal device.
  • the transceiving unit is further used for receiving request information and for sending the reference information according to the request information.
  • the request information includes type indication information, and the type indication information is used to indicate a first deactivation state type, where the first deactivation state type includes a session deactivation state type and a data radio bearer deactivation state Type or terminal device deactivation status type.
  • the processing unit is configured to determine the information of the first duration according to the type indication information, so that the deactivation state type corresponding to the first duration is the first deactivation state type.
  • the transceiver unit is further configured to receive first indication information sent by a third access device, and the first indication information is used to indicate The first duration; or the transceiver unit is further configured to receive second indication information sent by a third access device, where the second indication information is used to indicate the time when the terminal device enters a deactivated state and the terminal The moment when the device ends in the active state; where the first access device includes a centralized unit CU, the third access device includes a distributed unit DU, or the first access device includes a centralized unit control plane CU-CP entity, the third access device includes a centralized unit user plane CU-UP entity; wherein, the CU is configured with a packet data convergence layer protocol PDCP layer, a radio resource control RRC layer; the DU is configured There are radio link control RLC layer, media access control MAC layer and physical PHY layer.
  • the transceiver unit is specifically configured to send the reference to the second access device Information
  • the first access device includes a DU
  • the second access device includes a CU
  • the first access device includes a CU-UP entity
  • the second access device includes a CU-CP entity
  • the CU is configured with a PDCP layer and an RRC layer
  • the DU is configured with an RLC layer, a MAC layer and a PHY layer.
  • each unit in the device is used to execute each step of the above-mentioned first aspect and the communication method in each implementation manner of the first aspect.
  • the device is a communication chip
  • the communication chip may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.
  • the apparatus is a communication device, and the communication device may include a transmitter for sending information or data, and a receiver for receiving information or data.
  • an apparatus for wireless communication including: a transceiver unit configured to receive reference information, the reference information includes information of a first duration and/or information of a first cell, and the first duration includes a terminal Duration of the device in the deactivated state, the first cell includes a cell where the terminal device updates the RNAU based on the notification area of the radio access network; a processing unit is used to adjust the terminal device's time based on the first duration The duration of the deactivation state timer, or used to configure a notification area RNA based on a radio access network for the terminal device according to the first cell.
  • the apparatus may be configured or executed by the second access device itself, and the sending end of the reference information may be the first access device.
  • the apparatus may be configured or executed by the second access device itself, and the sending end of the reference information may be a terminal device.
  • the second access device may be the target access device to which the terminal device needs to be switched
  • the first access device may be the source access device of the terminal device.
  • the first access device may be a primary base station
  • the second access device may be a secondary base station.
  • the first access device may be the original camping base station of the terminal device
  • the second access device may be the new camping base station of the terminal device
  • the reference information further includes information of a second cell corresponding to the first duration, and the second cell includes a cell where the terminal device is in a deactivated state corresponding to the first duration.
  • the reference information further includes information of a deactivation state type corresponding to the first duration, wherein the deactivation state type includes a session deactivation state type, a data radio bearer deactivation state type, or terminal device deactivation Activation status type, and
  • Adjusting the duration of the deactivation timer of the terminal device according to the first duration includes:
  • the duration of the deactivation state timer corresponding to the deactivation state type of the first duration of the terminal device is adjusted according to the first duration.
  • the reference information further includes information about the type of RNAU corresponding to the first cell, where the type of RNAU includes the type of RNAU triggered periodically or the type of RNAU triggered by terminal device movement.
  • the reference information is carried in the history information of the terminal device.
  • the transceiver unit is further used to send request information, and the request information is used to request the reference information.
  • the request information includes type indication information, and the type indication information is used to indicate a first deactivation state type, where the first deactivation state type includes a session deactivation state type and a data radio bearer deactivation state Type or terminal device deactivation status type.
  • the apparatus is configured or executed by itself as a second access device, and the transceiving unit is configured to receive information of a first duration sent by the first access device, wherein the first access device It includes a distributed unit DU, the second access device includes a centralized unit CU, or the first access device includes a centralized unit user plane CU-UP entity, and the second access device includes a centralized unit control A CU-CP entity; wherein, the CU is configured with at least one protocol layer among a PDCP layer and an RRC layer; the DU is configured with at least one protocol layer among an RLC layer, a MAC layer, and a PHY layer.
  • each unit in the device is used to execute each step of the communication method in the second aspect and each implementation manner of the second aspect.
  • the communication device is a communication chip
  • the communication chip may include an input circuit or interface for transmitting information or data, and an output circuit or interface for receiving information or data.
  • the communication device is a communication device
  • the communication chip may include a transmitter for transmitting information or data, and a receiver for receiving information or data.
  • a communication device including a processor and a memory
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program from the memory, so that the communication device performs the first aspect and its Communication methods in various possible implementations.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor are provided separately.
  • the forwarding device further includes a transmitter (transmitter) and a receiver (receiver).
  • a communication device including a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device performs the second aspect and its Communication methods in various implementations.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor are provided separately.
  • the terminal device further includes a transmitter (transmitter) and a receiver (receiver).
  • a communication system the communication device provided in the fifth aspect above and/or the communication device provided in the sixth aspect.
  • the communication system may further include other devices that interact with the communication device in the solutions provided in the embodiments of the present application.
  • a computer program product includes: a computer program (also referred to as code or instructions) that, when the computer program is executed, causes a computer to perform the first aspect or the first Any one of the two possible implementation methods.
  • a computer-readable medium storing a computer program (also may be referred to as code or instructions), which when executed on a computer, causes the computer to perform the first aspect or the above Any one of the two possible implementation methods.
  • a computer program also may be referred to as code or instructions
  • a chip system including a memory and a processor, the memory is used to store a computer program, the processor is used to call and run the computer program from the memory, so that the communication device installed with the chip system executes the above The method in any possible implementation manner of the first aspect or the second aspect.
  • the chip system may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.
  • the terminal device or the source resident access device of the terminal device records the duration of the terminal device in the inactive state, and the target resident access device of the terminal device is based on the duration Configure the terminal for the inactive state timer, which can provide a reference and basis for the timer setting, thereby avoiding the signaling overhead caused by the unreasonable timer setting; or, by making the terminal device or the source of the terminal device reside access
  • the device records the cell where the terminal device was in when the RNAU occurred, and enables the target resident access device of the terminal device to configure RNA for the terminal device based on the cell, so that it can provide a reference and basis for the RNA setting, thereby avoiding the failure of the RNA setting.
  • the signaling overhead caused by reasonableness can reduce the power consumption of the terminal device and improve the user experience.
  • FIG. 1 is a schematic configuration diagram of an example of a communication system of the present application.
  • FIG. 2 is a schematic structural diagram of an example of an access device of the present application.
  • FIG. 3 is a schematic structural diagram of another example of the access device of the present application.
  • FIG. 4 is a schematic configuration diagram of another example of the communication system of the present application.
  • FIG. 5 is a schematic interaction diagram of an example of the wireless communication process of the present application.
  • FIG. 6 is a schematic interaction diagram of another example of the wireless communication process of the present application.
  • FIG. 7 is a schematic interaction diagram of yet another example of the wireless communication process of the present application.
  • FIG. 8 is a schematic interaction diagram of yet another example of the wireless communication process of the present application.
  • FIG. 9 is a schematic block diagram of an example of a wireless communication device of the present application.
  • FIG. 10 is a schematic block diagram of another example of a wireless communication device of the present application.
  • FIG. 11 is a schematic configuration diagram of an example of a terminal device of the present application.
  • FIG. 12 is a schematic structural diagram of an example of an access device of the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • UMTS universal mobile communication system
  • 5G future 5th generation
  • NR new radio
  • the terminal equipment in the embodiments of the present application may also be referred to as: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • access terminal user unit, user station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device may be a device that provides voice/data connectivity to the user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • some examples of terminals are: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, and augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote surgery, and smart grids Wireless terminals, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocols , SIP) telephone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to wireless modem, vehicle Devices, wearable devices, terminal devices in the future 5G network or terminal devices in the public land mobile communication network (PLMN) that will evolve in the future are not limited in the embodiments of the present application.
  • MID mobile
  • the terminal device may also be a wearable device.
  • Wearable devices can also be referred to as wearable smart devices, which is a general term for applying wearable technology to intelligently design everyday wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions that do not rely on smartphones, such as smart watches or smart glasses, and only focus on a certain type of application functions, and need to cooperate with other devices such as smartphones Use, such as various smart bracelets and smart jewelry for sign monitoring.
  • the terminal device may also be a terminal device in an Internet of Things (IoT) system.
  • IoT Internet of Things
  • the IOT technology can achieve mass connection, deep coverage, and terminal power saving through, for example, narrowband NB technology.
  • NB includes only one resource block (resource, bloc, RB), that is, the bandwidth of NB is only 180KB.
  • the terminal must be discrete in access. According to the communication method of the embodiment of the present application, the congestion problem of the IOT technology mass terminal when accessing the network through the NB can be effectively solved.
  • the access device in the embodiment of the present application may be a device for communicating with a terminal device, and the access device may also be referred to as an access network device or a wireless access network device, and may be a global mobile communication system.
  • mobile communications GSM
  • code division multiple access code division multiple access
  • CDMA code division multiple access
  • BTS base transceiver
  • WCDMA wideband code division multiple access
  • a base station NodeB, NB
  • the access device may be a relay station, an access point, an in-vehicle device, a wearable device, an access device in a future 5G network, or an access device in a future evolved PLMN network, etc., and may be an access point in an WLAN (access point, AP), which may
  • the access device is a device in the RAN, or is a RAN node that accesses the terminal device to the wireless network.
  • access devices gNB, transmission reception point (TRP), evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (eg, Home Evolved Node B, or Home Node B, HNB) , Baseband unit (BBU), or wireless fidelity (Wifi) access point (AP), etc.
  • TRP transmission reception point
  • eNB evolved Node B
  • RNC radio network controller
  • Node B Node B
  • BSC Base Station Controller
  • BTS Base Transceiver Station
  • BBU Baseband unit
  • Wi-Fi wireless fidelity
  • a network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node, or a control plane CU node (CU -CP node) and user plane CU node (CU-UP node) and DU node RAN equipment.
  • CU centralized unit
  • DU distributed unit
  • RAN device including a CU node and a DU node, or a control plane CU node (CU -CP node) and user plane CU node (CU-UP node) and DU node RAN equipment.
  • CU -CP node control plane CU node
  • CU-UP node user plane CU node
  • the access device provides services for the cell, and the terminal device communicates with the access device through the transmission resources (eg, frequency domain resources, or spectrum resources) used by the cell, and the cell may be corresponding to the access device (eg, base station)
  • a cell which can belong to a macro base station or a base station corresponding to a small cell (small cell), where the small cell can include: urban cell (metro cell), micro cell (micro cell), pico cell (pico cell), and Femto cells (femto cells), etc.
  • These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • multiple carriers on the carrier in the LTE system or 5G system can work on the same frequency at the same time.
  • the above carrier and cell concepts can also be considered equivalent.
  • CA carrier aggregation
  • the concept of carrier and cell may be considered equivalent, for example, terminal equipment accessing a carrier is equivalent to accessing a cell.
  • FIG. 1 shows a schematic diagram of a network architecture provided by an embodiment of the present application.
  • a terminal device can simultaneously have a communication connection with two access devices and can send and receive data, which can be called a dual link (dual -connectivity, DC).
  • DC dual -connectivity
  • one access device may be responsible for exchanging radio resource control messages with the terminal device and interacting with the core network control plane entity.
  • the access device may be called a master base station (master node, MN), another radio access network device may be called a secondary base station (secondary node, SN).
  • master node master node
  • secondary base station secondary node, SN
  • the terminal device can also have a communication connection with multiple access devices and can send and receive data at the same time, which can be referred to as multi-connection or multi-connectivity (MC).
  • MC multi-connection or multi-connectivity
  • An access device is responsible for exchanging radio resource control messages with the terminal device and for interacting with the core network control plane entity. Then, the access device can be called an MN, and the remaining access devices can be called an SN.
  • the access device may be an eNB base station in LTE mode, or a gNB base station in NR mode, may be a master base station (MN) in a dual link architecture, or may be a secondary base station in a dual link architecture , Which can be MN under multi-link architecture or SN under multi-link.
  • MN master base station
  • FIG. 2 shows a schematic diagram of a network architecture provided by an embodiment of the present application.
  • the access device may include a baseband device and a radio frequency device, where the baseband device may be implemented by one node or multiple nodes, and the radio frequency device may be implemented independently from the baseband device, or integrated with the baseband device In the middle, or part of the remote part is integrated in the baseband device.
  • a RAN device eNB
  • eNB includes a baseband device and a radio frequency device, where the radio frequency device can be remotely arranged relative to the baseband device, such as a remote radio unit (RRU) remotely arranged relative to the BBU .
  • RRU remote radio unit
  • the control plane protocol layer structure may include a radio resource control (radio resource control (RRC) layer, a packet data convergence layer protocol (packet data convergence protocol, PDCP) layer, a radio link control (radio link control (RLC) layer, a media access
  • RRC radio resource control
  • PDCP packet data convergence layer protocol
  • RLC radio link control
  • the functions of protocol layer such as media access (MAC) layer and physical layer.
  • the user plane protocol layer structure may include PDCP layer, RLC layer, MAC layer and physical layer protocol layer functions; in one implementation, the PDCP layer may also include a service data adaptation (service data adaptation (SDAP) layer .
  • SDAP service data adaptation
  • RAN equipment may include a centralized unit (CU) and a distributed unit (DU), Multiple DUs can be centrally controlled by a CU.
  • CU centralized unit
  • DU distributed unit
  • CU and DU can be divided according to the protocol layer of the wireless network.
  • the functions of the PDCP layer and above are set in the CU, and the functions of the protocol layers below PDCP, such as the RLC layer and the MAC layer, are set in the DU.
  • the CU has functions above the PDCP layer (including PDCP, RRC, and SDAP), and the DU has functions below the PDCP layer (including RLC, MAC, and PHY).
  • This division of the protocol layer is only an example, and it can also be divided at other protocol layers, for example, at the RLC layer, the functions of the RLC layer and above are set in the CU, and the functions of the protocol layers below the RLC layer are set in the DU; Or, in a certain protocol layer, for example, some functions of the RLC layer and the functions of the protocol layer above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are set in the DU. In addition, it can also be divided in other ways, for example, according to delay, and the function that the processing time needs to meet the delay requirement is set in the DU, and the function that does not need to meet the delay requirement is set in the CU.
  • the radio frequency device can be remotely located, not placed in the DU, or integrated in the DU, or partly remotely and partially integrated in the DU, without any limitation here.
  • FIG. 3 shows another schematic diagram of a network architecture applicable to an embodiment of the present application.
  • the control plane (CP) and user plane (UP) of the CU can also be separated and implemented into different entities, namely, the control plane CU entity (CU-CP entity) and the user plane CU entity. (CU-UP entity).
  • the signaling generated by the CU can be sent to the terminal device through the DU, or the signaling generated by the terminal device can be sent to the CU through the DU.
  • the DU can transparently transmit to the terminal device or CU through the protocol layer encapsulation without parsing the signaling. If the transmission of such signaling between the DU and the terminal device is involved in the following embodiments, at this time, the DU sends or receives signaling to include this scenario.
  • the signaling of the RRC or PDCP layer will eventually be processed as the signaling of the PHY layer and sent to the terminal device, or it will be converted from the received signaling of the PHY layer.
  • the RRC or PDCP layer signaling can also be considered to be sent by the DU, or sent by the DU and the radio frequency.
  • the CU is divided into network devices on the RAN side.
  • the CU may also be divided into network devices on the CN side, which is not limited herein.
  • the devices in the following embodiments of the present application may be located in a terminal device or a network device according to the functions they implement.
  • the network device may be a CU node, or a DU node, or a RAN device including a CU node and a DU node.
  • FIG. 4 is a schematic diagram of a system 100 that can apply the communication method of the embodiment of the present application.
  • the system 100 includes an access device 102.
  • the access device 102 may include one antenna or multiple antennas, for example, antennas 104, 106, 108, 110, 112, and 114.
  • the access device 102 may additionally include a transmitter chain and a receiver chain, and those of ordinary skill in the art may understand that they can include multiple components related to signal transmission and reception (such as a processor, a modulator, and multiplexing) Device, demodulator, demultiplexer or antenna, etc.).
  • the access device 102 can communicate with multiple terminal devices (eg, terminal device 116 and terminal device 122). However, it is understood that the access device 102 can communicate with any number of terminal devices similar to the terminal device 116 or the terminal device 122.
  • Terminal devices 116 and 122 may be, for example, cellular phones, smart phones, portable computers, handheld communication devices, handheld computing devices, satellite radios, global positioning systems, PDAs, and/or any other suitable devices for communicating on wireless communication system 100 equipment.
  • the terminal device 116 communicates with the antennas 112 and 114, where the antennas 112 and 114 send information to the terminal device 116 through the forward link (also called downlink) 118 and through the reverse link (also Known as the uplink) 120 receives information from the terminal device 116.
  • the terminal device 122 communicates with the antennas 104 and 106, where the antennas 104 and 106 transmit information to the terminal device 122 via the forward link 124 and receive information from the terminal device 122 via the reverse link 126.
  • the forward link 118 may use a different frequency band from the reverse link 120, and the forward link 124 may use a different frequency band from the reverse link 126 Frequency band.
  • FDD frequency division duplex
  • the forward link 118 and the reverse link 120 may use a common frequency band
  • the forward link 124 and the reverse link Link 126 may use a common frequency band.
  • Each antenna (or antenna group consisting of multiple antennas) and/or area designed for communication is called a sector of the access device 102.
  • the antenna group may be designed to communicate with terminal devices in sectors in the coverage area of the access device 102.
  • the access device may transmit signals to all terminal devices in its corresponding sector through a single antenna or multiple antenna transmit diversity.
  • the transmit antenna of the access device 102 can also use beamforming to improve the signal-to-noise of the forward links 118 and 124 ratio.
  • the access device 102 uses beamforming to send signals to randomly distributed terminal devices 116 and 122 in the relevant coverage area At this time, mobile devices in neighboring cells will receive less interference.
  • the access device 102, the terminal device 116, or the terminal device 122 may be a wireless communication transmitting device and/or a wireless communication receiving device.
  • the wireless communication transmitting device may encode the data for transmission.
  • the wireless communication transmitting device may acquire (eg, generate, receive from other communication devices, or store in a memory, etc.) a certain number of data bits to be transmitted to the wireless communication receiving device through the channel.
  • Such data bits may be contained in a transport block (or multiple transport blocks) of data, which may be segmented to produce multiple code blocks.
  • the communication system 100 may be a PLMN network, a D2D network, an M2M network, an IoT network, or other networks.
  • FIG. 4 is only a simplified schematic diagram of an example, and the network may also include other access devices, which are not shown in FIG. 4.
  • the communication system may further include a core network device.
  • the core network device may be connected to multiple access network devices to control the access network devices, and may distribute data received from the network side (for example, the Internet) to Access network equipment.
  • the terminal device or the access device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), memory management unit (MMU), and memory (also called main memory).
  • the operating system may be any one or more computer operating systems that implement business processes through processes, for example, a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of the present application do not specifically limit the specific structure of the execution body of the method provided in the embodiments of the present application, as long as it can run the program that records the code of the method provided by the embodiments of the present application to provide according to the embodiments of the present application
  • the method may be used for communication.
  • the execution body of the method provided in the embodiments of the present application may be a terminal device or a network device, or a functional module in the terminal device or network device that can call a program and execute the program.
  • the term "article of manufacture” as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium.
  • the computer-readable medium may include, but is not limited to: magnetic storage devices (for example, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (for example, compact discs (CDs), digital universal discs (digital discs, digital discs, DVDs)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).
  • various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • machine-readable medium may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
  • the inactive state may include one or more of the following types:
  • Type 1 Session deactivation state type
  • the session deactivation state type can be understood as the session granularity deactivation type.
  • the terminal device when at least one of the M sessions (remember, session #m) satisfies the condition for triggering entry into the session deactivation state (remember, condition 1), it can be determined The terminal device enters the session deactivation state.
  • the core network device, the access device, and the terminal device may retain the context of the session #m.
  • condition 1 may include but not limited to the following conditions:
  • the duration #m may be specified by a communication system or a communication protocol, or the duration #m may be configured by an access device or a core network device, or the duration #m may be configured by an administrator or an operator, This application is not particularly limited.
  • Condition 1 listed above is only an example of the conditions for entering the session deactivation state, and this application is not limited thereto, and other conditions that can be used to determine whether the terminal enters the session deactivation state fall within the scope of protection of this application .
  • the "session” may include, but is not limited to, a protocol data unit (protocol data unit, PDU) session.
  • PDU protocol data unit
  • the bearer deactivation state type can be understood as the bearer granularity deactivation type.
  • the terminal device when at least one of the N bearers (remember, bearer #n) satisfies the condition for triggering to enter the bearer deactivation state (remember, condition 2), it can be determined The terminal device enters the bearer deactivation state.
  • the core network device, the access device, and the terminal device may retain the context of the bearer #n.
  • condition 2 may include but not limited to the following conditions:
  • the duration #n may be specified by a communication system or a communication protocol, or the duration #n may be configured by an access device or a core network device, or the duration #n may be configured by an administrator or an operator, This application is not particularly limited.
  • Condition 2 listed above is only an example of the condition for entering the bearer deactivation state, and this application is not limited thereto, and other conditions that can be used to determine whether the terminal enters the bearer deactivation state fall within the scope of protection of this application .
  • the "bearer” may include, but is not limited to, a data radio bearer (DRB).
  • DRB data radio bearer
  • Type 3 Type of terminal deactivation state
  • the terminal deactivation state type can be understood as the terminal granularity deactivation type.
  • CM connection state is a state maintained by the NAS layer, that is, a NAS signaling connection between the UE and the core network still exists, and a signaling connection between the UE and the RAN No more.
  • the core network device, the access device, and the terminal device After entering the terminal deactivation state, the core network device, the access device, and the terminal device can retain the context of the terminal device, and the access device does not perceive the behavior of the terminal device when the terminal device moves inside the RNA.
  • any one of the following events occurs in the terminal device or the access device, it can be determined that the terminal device ends the inactive state.
  • Event 1 The timer expires (or, timeout)
  • the terminal device when the terminal device enters the inactive state, the terminal device (and/or access device) can start a timer, and, if the timer expires (or, timeout), if the terminal device still has no data transmission, Then, the terminal device (and/or access device) may determine that the terminal device ends the inactive state. And, for example, the terminal device (and/or access device) may determine that the terminal device enters an idle state or a connected state, for example, the access device may initiate paging to the terminal device to make the terminal device enter the connected state Or, the access device initiates an RRC connection release command to the terminal device to make the terminal device enter an idle state.
  • Event 2 Periodic RNAU occurs in the terminal device
  • the access device when the RNAU is detected and the access device detects the RNAU, the access device must notify the source access device of the terminal device's inactive The state is over.
  • Event 3 The terminal device needs to perform data transmission
  • the terminal device after entering the inactive state can end the inactive state if it needs to transmit data (for example, it needs to send uplink data), for example, it can enter the connected state.
  • any one of the following events occurs in the terminal device or the access device, it may be determined that the terminal device ends the inactive state of a session.
  • Event 4 The timer expires (or, timeout)
  • the terminal device when a session of the terminal device enters the inactive state, the terminal device (and/or access device) can start a timer, and, if the timer expires (or, timeout), if the terminal device’s If there is still no data transmission in the session, the terminal device (and/or access device) may determine that the session of the terminal device ends in an inactive state. And, for example, the terminal device (and/or access device) may determine to release the session of the terminal device or activate the session.
  • the timer is an inactive state timer of session granularity (or, session deactivation state type).
  • Event 5 The access device instructs the terminal device to change the status of a session
  • the session may end the inactive state, for example, the terminal device may reactivate the session.
  • Event 6 The terminal device needs to perform data transmission
  • the terminal device after a session enters the inactive state, if the session has services, the inactive state may be ended, for example, the terminal device may actively activate the session.
  • any of the following events occurs in the terminal device or the access device, it may be determined that a bearer of the terminal device ends the inactive state.
  • Event 7 Timer expires (or, timeout)
  • the terminal device when a bearer of the terminal device enters the inactive state, the terminal device (and/or access device) can start a timer, and, if the timer expires (or, timeout), if the terminal device’s If there is still no data transmission on the bearer, the terminal device (and/or access device) may determine that the bearer of the terminal device ends in an inactive state. And, for example, the terminal device (and/or access device) may determine to release the bearer of the terminal device or re-enter to establish the bearer.
  • the timer is an inactive state timer bearing a granularity (or, bearing a deactivation state type).
  • Event 8 The access device instructs a bearer of the terminal device to change the state
  • a terminal device after a bearer enters the inactive state if the indication information sent by the access device is detected, the bearer may end the inactive state, for example, the bearer may be re-established.
  • the access device may configure the wireless network area of the terminal device in the inactive state for the terminal device it serves.
  • the wireless network area may be referred to as a RAN based notification area (RNA).
  • the access device can deliver the RNA information to the terminal device through dedicated signaling.
  • RNA may cover one cell or multiple cells.
  • the access device can provide the terminal device with a clear cell list as RNA.
  • the access device can provide a RAN area ID list for the terminal device as RNA.
  • the RAN area can be a subset of CN Tracking Area or equal to CN Tracking Area.
  • One RAN area corresponds to one RAN area ID, one RAN area consists of TAI and an optional RAN area code.
  • a cell will broadcast its RAN area ID in its system message.
  • the terminal device may not notify the network when reselecting a cell within the RNA in the inactive state, and may notify the network when the terminal device reselects to a cell outside the RNA in the inactive state.
  • the access device when the access device needs to page the terminal device in the inactive state, it can page in the cell in the RNA.
  • RNA renewal (ie, RNAU) may occur.
  • RNAU can be divided into the following types:
  • Type ⁇ RNAU caused by the movement of the terminal device, that is, when the terminal device moves out of the RNA allocated by the access device, the RNAU is required.
  • RNAU that occurs periodically, or RNAU that starts when the RNA timer expires, and the RNA timer may be configured by the base station.
  • RNAU RNAU
  • present application is not limited thereto, and other methods or methods that can classify RNAU fall within the protection scope of the present application.
  • RNAU of the present application may include the following processes.
  • the UE can recover from the inactive state and provide the newly accessed gNB with the I-RNTI allocated by the last serving gNB and the appropriate cause value, such as RAN notification area update.
  • the new access gNB requests the last serving gNB to provide the UE context.
  • the serving gNB provides the UE context.
  • the new access gNB can switch the UE to the RRC_CONNECTED state, or switch the UE back to the RRC_INACTIVE state or switch the UE to the RRC_IDLE state. It should be noted that if the UE is switched to RRC_IDLE, there is no need to perform subsequent steps.
  • the new access gNB provides the last serving gNB with a downlink data forwarding address.
  • the new access gNB performs path switching (sending a path switching request message to the serving AMF).
  • AMF replies with a path switching response message.
  • AMF notifies the last serving gNB to release the UE context.
  • FIG. 5 shows a schematic flowchart of an example of a wireless communication method 200 of the present application, and the method 200 shows an interaction process between an access device #A and an access device #B.
  • the method 200 can be applied to any of the following scenarios:
  • Access device #A may be the primary base station
  • access device #B may be the secondary base station
  • the resident base station of terminal device #A is from another base station (eg, access device #A or other devices of access device #A The secondary base station) is changed to access device #B.
  • Access device #A may be the original camping base station of terminal device #A, and access device #A may be the new camping base station of terminal device #A.
  • terminal device #A may enter the inactive state.
  • the number of times the terminal device #A enters the inactive state may be one time or N times, and N is an integer greater than 1.
  • the process of the terminal device #A entering the inactive state for the i-th time while staying in the access device #A is taken as an example to describe the process of the method 200, where i is greater than Or an integer equal to 1, and i is an integer less than or equal to N.
  • terminal device #A enters the inactive state at the i-th time instant #A.
  • the type of the i-th inactive state may be any one of the types 1 to 3 above, and this application is not particularly limited.
  • terminal device #A ends the i-th inactive state at time #B.
  • the event that triggers the terminal device to end the i-th inactive state may be any one of the above events 1 to 3, and this application is not particularly limited.
  • the access device #A can determine the duration of the i-th inactive state of the terminal device #A (recorded as duration #A), that is, the duration #A can be the time #A to time #B The length of time between.
  • the access device #A may use any one of the following methods to determine the duration #A.
  • the access device #A can learn that the terminal device #A enters the inactive state at time i at time #A, then the access device #A can record the time #A, and if the access device #A can know that terminal device #A ends the i-th inactive state at time #B, then the access device #A can record the time #B, so that the access device #A can be based on the time #A and time # B determines the duration #A.
  • terminal device #A may report the information of time #A and the information of time #B to access device #A, so that access device #A may determine the time #A and time #B, Furthermore, the duration #A is determined based on the time #A and the time #B.
  • the information of #A at this moment may be sent by the terminal device #A immediately after entering the inactive state, or may be sent by the terminal device #A after entering an inactive state for any length of time.
  • This application is not particularly limited.
  • the information of #B at this moment may be sent by terminal device #A immediately after the end of the inactive state, or may be sent by terminal device #A after an arbitrary length of time after the end of the inactive state, and this application is not particularly limited.
  • terminal device #A may report this moment #A and this moment #B to access device #A through other access devices, for example, when terminal device #A enters the inactive state in access device #A, record Time #A, move to other access equipment, then when the UE ends inactive state in other access equipment, then the UE will record time #B, at this time #A and this time #B can be reported to other access first Access device, and then other access devices are sent to access device #A.
  • terminal device #A may report an inactive state start instruction to access device #A at time #C, and terminal device #A may end at time #D after ending inactive Report the inactive status end indication to access device #A.
  • the time interval #1 and the time interval #2 may be the time interval specified by the communication system or the communication protocol, or the time interval configured by the access device #1, which is not particularly limited in this application.
  • the terminal device #A may report the time A and the time B to the access device #A through other access devices.
  • the details are the same as the previous description, and will not be repeated here.
  • terminal device #A may determine the duration #A according to the time #A and the time #B, and send the information of the duration #A to the access device #A, so that the access device #A
  • the duration #A may be determined based on the information of the duration #A.
  • the terminal device #A may report the information of the duration #A to the access device #A through other access devices.
  • the access device (or RAN device) of this application may include CU and DU, and the CU may include CU-CP and CU-UP,
  • the access device #A may include a CU, or the access device #A may include a CU-CP (ie, case #2). For the above two cases, the access device #A determines the duration #A's plan.
  • the access device #C (ie, DU) may (for example, based on any of the above methods 1 to 3) record the time #A and time #B, and send the time to access device #A The information of #A and the information of time #B, so that the access device #A can determine the duration #A according to the time #A and the time #B.
  • the information of #B at this moment may be recorded by other access device #C or other access device #A and sent to access device #A.
  • the access device #C (ie, DU) may (for example, based on any one of the above methods 1 to 4) determine the duration #A and send the duration #A to the access device #A Information, so that the access device #A can determine the duration #A based on the information of the duration #A.
  • the information of the duration #A may be recorded by another access device #C or other access device #A and sent to the access device #A.
  • the above information of the time #A, the information of the time #B, or the information of the duration #A may be carried in the interface message between the CU and the DU, for example, the F1 interface message (for example, the F1 interface goes Activation notification message).
  • access device #A can also send monitoring request #1 to access device #C, which can be used to instruct access device #C to monitor terminal device #A to enter the deactivated state and end The moment of deactivation, or the monitoring request #1 can be used to indicate that the access device #C records the length of time the terminal device #A is in the deactivated state, so that the access device #C can send according to the monitoring request #1 Information at this time #A, information at time #B, or information at duration #A.
  • monitoring request #1 can be used to instruct access device #C to monitor terminal device #A to enter the deactivated state and end The moment of deactivation, or the monitoring request #1 can be used to indicate that the access device #C records the length of time the terminal device #A is in the deactivated state, so that the access device #C can send according to the monitoring request #1 Information at this time #A, information at time #B, or information at duration #A.
  • the access device #D (ie, CU-UP) may (for example, based on any one of the above methods 1 to 3) record the time #A and time #B and send to the access device #A
  • the information of #B at this moment may be recorded by other access device #C or other access device #A and sent to access device #A.
  • the access device #D may (for example, based on any one of the above methods 1 to 4) determine the duration #A, and send the duration # to the access device #A The information of A, so that the access device #A can determine the duration #A according to the information of the duration #A.
  • the information of the duration #A may be recorded by another access device #C or other access device #A and sent to the access device #A.
  • the above information of the time #A, the information of the time #B or the information of the duration #A may be carried in the interface message between the CU-UP and the CU-CP, for example, the E1 interface message (for example , E1 interface deactivation notification message).
  • the E1 interface message for example , E1 interface deactivation notification message.
  • access device #A can also send monitoring request #2 to access device #D, which can be used to instruct access device #D to monitor terminal device #A to enter the deactivated state and end The moment of deactivation, or the monitoring request #2 can be used to indicate that the access device #C records the length of time the terminal device #A is in the deactivated state, so that the access device #D can be sent according to the monitoring request #2 Information at this time #A, information at time #B, or information at duration #A.
  • the access device #A may also determine the type of the i-th inactive state (i.e., any one of the above types 1 to 3).
  • the monitoring request #1 or monitoring request #2 may also carry type indication information #1, which may be used to indicate the type of deactivation state that requires DU monitoring (That is, any one of the above types 1 to 3).
  • the access device #A may send the type indication information #2 to the terminal device #A, and the type indication information #2 may It is used to indicate the type of the deactivation state that needs to be monitored by the terminal device #A (that is, any one of the above types 1 to 3).
  • the access device may also determine cell #A, which is the cell where terminal device #A enters (eg, camps on) the i-th time it enters the inactive state.
  • the access device #A can also record the correspondence between the duration #A and the cell #A.
  • the monitoring request #1 or monitoring request #2 may also carry cell report request information #1, and the cell report request information #1 may be used to request DU monitoring and report terminal equipment # The cell where A was in (eg, camped on) when entering the inactive state.
  • the DU may also actively report the cell where the terminal device #A enters (for example, camps on) when it enters the inactive state.
  • the access device #A may send the cell report request information #2 to the terminal device #A, and the cell report request information # 2 can be used to request the access device #A to monitor and report the cell in the inactive state (for example, camping).
  • the access device may also determine the type #A, which is the type that enters the i-th inactive state.
  • the access device #A can also record the correspondence between the duration #A and the type #A.
  • the access device #A may record the information of the duration #A in the user history information (UE history) of the terminal device #A, or it may also be recorded in a new cell, and this application is here Not limited.
  • UE history user history information
  • the user history information of this application may include the following forms of information:
  • Last visited cell list (last visited cell list)
  • the ECGI may be the ECGI of the cell where the terminal device is in the deactivated state (for example, the above-mentioned cell #A), and optionally, the information element may also be PCI (for example, the above-mentioned cell #A). This cell is optional.
  • the duration refers to the duration in which the terminal device is in the deactivated state (for example, the above-mentioned duration #A).
  • the user history information may also include the type of deactivation state corresponding to the duration (for example, the above-mentioned type #A).
  • the user history information may record the duration corresponding to multiple deactivation states in one cell, or the duration corresponding to multiple deactivation states in different cells.
  • the duration cell may exist in the form of a list, and the specific application is not limited here.
  • the access device #A may send the information of the duration #A to the access device #B.
  • the access device #A may also send the information of the cell #A to the access device #B.
  • the access device #A may also send the access device #B information about the correspondence between the duration #A and the cell #A.
  • the access device #A may also send the type #A information to the access device #B.
  • the access device #A may also send the access device #B information about the type (ie, type #A) of the inactive state (ie, the i-th inactive state) corresponding to the duration #A.
  • the above information may be carried in the history information of terminal device #A.
  • the information of the duration #A may be sent by the access device #A based on the request of the access device #B, that is, at S220, the access device #B may send the duration request information to the access device #A,
  • the duration request information can be used to request the access device #A to send the terminal device #A in the deactivated duration (specifically, the duration request information can be used to request the access device #A to send the terminal device #A to go in one go The duration of the activation state).
  • the duration request information may further include type request information, which may be used to indicate that the access device #B wants the access device #A to provide the type of deactivation state corresponding to the duration, or the type request information It can be used to indicate what type of deactivation time the access device #B wants the access device #A to provide.
  • type request information may be used to indicate that the access device #B wants the access device #A to provide the type of deactivation state corresponding to the duration, or the type request information It can be used to indicate what type of deactivation time the access device #B wants the access device #A to provide.
  • the aforementioned type #A may be determined by the access device #A according to the type request information, or the type #A may be the type indicated by the type request information.
  • the duration request information may be carried in a context request message, and the duration #A information may be carried in a context request response message or other Xn interface message.
  • the context request information may be sent by the access device #B according to a radio resource control (RRC) recovery request message (RRC resume request) sent by the access device #A.
  • RRC radio resource control
  • the information of the duration #A may carry a secondary base station change request message or other EUTRA and NR dual-link (E-UTRA-NR Dual Connectivity, EN-DC) Xn interface message.
  • data or information can be transmitted between the access device #A and the access device #B through the core network device, for example, the access device #A can send the information of the duration #A to the core network Device, and the core network device can forward the information of duration #A to access device #B.
  • the access device #B (ie, the access device where the terminal device #A newly resides) can obtain the information of the duration #A, so that the timer for the inactive state can be configured according to the duration #A ( timer).
  • duration #B the duration of the original timer for the inactive state configured by access device #B.
  • the access device #B can adjust the duration #B according to the duration #A.
  • access device #B may adjust the timer to extend the duration #B.
  • access device #B may adjust the timer to shorten the duration #B.
  • the access device #B may adjust the timer so that the difference between the duration #B and the duration #A is within a preset difference range.
  • the access device #B may also determine the inactive state (ie, type #A) corresponding to the duration #A, and determine the duration of the timer in the inactive state of the type #A as the configuration object (ie, duration # B).
  • the wireless communication method by making the source-resident access device #A of the terminal device #A record the duration #A of the terminal device #A in the inactive state, and make the access device #A change the duration #A
  • the information is sent to the new resident access device #B of terminal device #A, so that access device #B can configure a timer for the inactive state based on the duration #A, that is, according to the wireless communication method provided in this application, it can Provide a reference and basis for the timer setting, so that the signaling overhead due to unreasonable timer setting, that is, the increase in device power consumption, can be avoided, and the signaling overhead and the power consumption of the terminal device can be reduced, thereby improving the user experience.
  • the access device may also reconfigure the duration of the inactive state timer for terminal device #A at time #C (the time after time #B) (remember, duration #C).
  • the access device #A may adjust the timer to extend the duration #C.
  • access device #A may adjust the timer to shorten the duration #C.
  • the access device #A may adjust the timer so that the difference between the duration #C and the duration #A is within a preset difference range.
  • the access device #A may also determine the inactive state (ie, type #A) corresponding to the duration #A, and determine the duration of the timer in the inactive state of the type #A as the configuration object (ie, duration # C).
  • the access device #A can record the duration of each inactive state in the multiple inactive states, and the process of determining, recording, transmitting, and using the duration can be in the i-th time with the terminal device #A
  • the duration of the inactive state ie, duration #A
  • duration #A is similar, and the detailed description is omitted here to avoid omitting.
  • the history information of the terminal device #A may include a duration list, and the duration list may include information on the duration of multiple inactive states of the terminal device #A.
  • FIG. 6 shows a schematic flowchart of an example of a wireless communication method 300 of the present application, and the method 300 shows an interaction process between an access device #1 and an access device #2.
  • the method 300 can be applied to at least one of the following scenarios:
  • terminal device #1 switches from the access device #1 to the access device #2.
  • Access device #1 may be the primary base station
  • access device #2 may be the secondary base station
  • the resident base station of terminal device #1 is from another base station (for example, access device #1 or other devices of access device #1 The secondary base station) is changed to access device #2.
  • Access device #1 may be the original camped base station of terminal device #1, and access device #1 may be the new camped base station of terminal device #1.
  • RNAU may occur in terminal device #1.
  • the number of times that the terminal device #1 generates RNAU may be one time or M times, where M is an integer greater than 1.
  • j is an integer greater than or equal to 1
  • j is an integer less than or equal to M.
  • the type of the jth RNAU may be any one of the above types ⁇ to ⁇ , which is not particularly limited in this application.
  • the access device #1 may determine the cell where the terminal device #1 is located when the jth RNAU occurs (recorded as: cell #1).
  • the access device #1 may use any of the following methods to determine the cell #1.
  • the access device #1 may record the cell where the terminal device #1 is located when the jth RNAU occurs.
  • the terminal device #1 may report the information of the cell #1 to the access device #1.
  • the access device #1 can record the information of the cell #1.
  • the information of the cell #1 may include, but is not limited to, the physical cell identifier PCI (physical cell Identifier, PCI) or the cell global identifier (Cell Global Identifier, CGI) of the cell #1, and so on.
  • PCI physical cell identifier
  • CGI Cell Global Identifier
  • the access device #1 may also determine the type #1, which is the type of the jth occurrence of the RNAU of the terminal device #1.
  • the access device #1 can also record the correspondence between the cell #1 and the type #1.
  • the access device #1 may record the above information in the user history information (UE history) of the terminal device #1, or in a newly defined cell, which is not limited herein.
  • UE history user history information
  • the user history information of this application may include the following forms of information:
  • Last visited cell list (last visited cell list)
  • the ECGI may be the ECGI of the cell (for example, the above-mentioned cell #1) where the terminal device is located when the RNAU occurs.
  • the ECGI may be the ECGI of the cell (for example, the above-mentioned cell #1) where the terminal device is located when the RNAU occurs.
  • it may be the PCI of the cell.
  • the user history information may record the information of the cell corresponding to the RNAU multiple times.
  • the access device #1 may send the information of the cell #1 to the access device #2.
  • the access device #1 may also send the type #1 information to the access device #2.
  • the access device #1 can also send the information of the correspondence relationship between the cell #1 and the type #1 to the access device #2.
  • the above information may be carried in the history information of terminal device #1.
  • the information of the cell #1 may be sent by the access device #1 based on the request of the access device #2, that is, at S320, the access device #2 may send the cell request information to the access device #1,
  • the cell request information may be used to request the access device #1 to inform the terminal device #1 that the RNAU is located in the cell.
  • the cell request information may also include type request information, which may be used to indicate that the access device #2 wants the access device #1 to provide the RNAU type corresponding to the cell, or that the type request information may be used In order to indicate that access device #2 wants access device #1 to provide the cell in which RNAU type occurs.
  • type request information may be used to indicate that the access device #2 wants the access device #1 to provide the RNAU type corresponding to the cell, or that the type request information may be used In order to indicate that access device #2 wants access device #1 to provide the cell in which RNAU type occurs.
  • the aforementioned type #1 may be determined by the access device #1 according to the type request information, or the type #1 may be the type indicated by the type request information.
  • the cell request information may be carried in a context request message, and the information of the cell #1 may be carried in a context request response message or other Xn interface message.
  • the context request information may be sent by the access device #2 according to a radio resource control (RRC) recovery request message (RRC resume request) sent by the access device #1.
  • RRC radio resource control
  • the information of the cell #1 may be carried in the secondary base station change request message or other EN-DC Xn interface messages.
  • data or information may be transmitted between the access device #1 and the access device #2 through the core network device, for example, the access device #1 may send the information of the cell #1 to the core network Device, and the core network device can forward the information of cell #1 to access device #2.
  • the access device #2 ie, the access device where the terminal device #1 is newly camped on
  • the access device #2 can acquire the information of the cell #1, so that the terminal device #1 can be configured with RNA according to the cell #1.
  • access device #2 be the cell included in the RNA configured by terminal device #1 as cell set #X.
  • the access device #2 may adjust the cell set #X, or adjust the cells included in the cell set #X according to the cell #1.
  • the access device #2 may add the cell #1 to the cell set #X.
  • the wireless communication method provided by the present application by making the source-resident access device #1 of the terminal device #1 record the cell #1 where the terminal device #1 was in when the RNAU occurred, and make the access device #1 use the cell #1
  • the information of 1 is sent to the new resident access device #2 of terminal device #1, so that access device #2 can configure RNA for terminal device #1 based on the cell #1, that is, according to the wireless communication method provided in this application , Can provide reference and basis for RNA setting, thus, can avoid the increase of the signaling overhead caused by unreasonable RNA setting, that is, the power consumption of the device, can reduce the signaling overhead and the power consumption of the terminal device, and thereby improve the user experience .
  • access device #1 may also reconfigure RNA for terminal device #A at time #2 (the time after time #1, which is the jth time when RNAU occurs), and set the reconfigured The cells included in the RNA are cell set #Y.
  • the access device #1 may add the cell #1 to the cell set #Y.
  • the access device #A may record the RNAU of the multiple RNAUs.
  • the cell, and the process of determining, recording, transmitting, and using the information of the cell may be similar to the cell of the jth RNAU of the terminal device #1, and a detailed description thereof is omitted here to avoid omitting.
  • the historical information of the terminal device #1 may include a list of cells where RNAU has occurred, and the cell list may include at least one of information of multiple RNAU cells of the terminal device #1 and the type of RNAU.
  • FIG. 7 shows a schematic flowchart of an example of a wireless communication method 400 of the present application, and the method 400 shows an interaction process between a terminal device #x and an access device #y.
  • the method 400 can be applied to at least one of the following scenarios:
  • terminal device #x switches from the access device #x to the access device #y.
  • Access device #x may be the primary base station
  • access device #y may be the secondary base station
  • the resident base station of terminal device #x is from another base station (eg, access device #x or other access device #x) The secondary base station) is changed to access device #y.
  • Access device #x may be the original camping base station of terminal device #x
  • access device #y may be the new camping base station of terminal device #x.
  • terminal device #x may enter the inactive state.
  • the number of times the terminal device #x enters the inactive state may be one time or K times, and K is an integer greater than 1.
  • terminal device #x enters the inactive state at the kth time at time #x.
  • the type of the k-th inactive state may be any one of the types 1 to 3 above, and this application is not particularly limited.
  • the terminal device #x ends the k-th inactive state at time y.
  • the event that triggers the terminal device to end the k-th inactive state may be any one of the above events 1 to 7, and this application is not particularly limited.
  • the terminal device #x may record the duration of the k-th inactive state of the terminal device #x (recorded as, duration #x), that is, the duration #x may be the time #x to the time #y The length of time experienced.
  • the terminal device #x may also determine the type #x, which is the type that enters the k-th inactive state.
  • the terminal device #x can also record the correspondence between the duration #x and the type #x.
  • the terminal device #x may also record a cell #k, which is the cell where the terminal device has been in the k-th inactive state for the kth time, wherein the cell #k may be one or more No, this application is not particularly limited.
  • the terminal device #x may record the information of the duration #x in the user history information (UE history) of the terminal device #x, or may record it in a new cell, which is not limited herein .
  • UE history user history information
  • the user history information of this application may include the following forms of information:
  • Last visited cell list (last visited cell list)
  • the ECGI may be the ECGI of the cell (for example, the above-mentioned cell #k) where the terminal device is in the deactivated state. Alternatively, it may be the PCI of the cell. This cell is optional.
  • the duration refers to the duration in which the terminal device is in the deactivated state (for example, the above-mentioned duration #k).
  • the user history information may also include the type of deactivation state corresponding to the duration (for example, the above-mentioned type #k).
  • the user history information may record the length of time corresponding to multiple deactivation states.
  • the terminal device #x may send the information of the duration #k to the access device #y (or the access device #x).
  • the terminal device #x may also send the information of the cell #k to the access device #y (or access device #x).
  • the terminal device #x may also send the information of the correspondence relationship between the duration #k and the cell #k to the access device #y (or access device #x).
  • the access device #y (or access device #x) may also send information of type #k to the terminal device #x.
  • the access device #y (or access device #x) can also send the type of the inactive state (ie, the k-th inactive state) corresponding to the duration #k to the terminal device #x (ie, type #k )Information.
  • the above information may be carried in the history information of terminal device #A.
  • the information of the duration #k may be sent by the terminal device #x based on the request of the access device #y (or access device #x), that is, at S420, the access device #y (or access device #x) can send duration request information to terminal device #x, the duration request information can be used to request the duration of terminal device #x Send terminal device #x in the deactivated state (specifically, the duration request information can be used to request The length of time that terminal device #x sends terminal device #x in a deactivated state).
  • the duration request information may also include type request information, which may be used to indicate that the access device #y (or access device #x) wants the terminal device #x to provide the deactivation status type corresponding to the duration, In other words, this type of request information can be used to indicate what type of deactivation time the access device #y (or access device #x) wants the terminal device #x to provide.
  • type request information may be used to indicate that the access device #y (or access device #x) wants the terminal device #x to provide the deactivation status type corresponding to the duration.
  • the aforementioned type #k may be determined by the terminal device #x according to the type request information, or the type #k may be the type indicated by the type request information.
  • the access device #y (or access device #x) can obtain the information of the duration #x, so that a timer for the inactive state can be configured for the terminal device #x according to the duration #k .
  • access device #y (or access device #x) be the duration of the original timer for the inactive state configured by terminal device #x as duration #y.
  • the access device #y (or access device #x) can adjust the duration #y according to the duration #x.
  • access device #y may adjust the timer to extend the duration #y.
  • access device #y may adjust the timer to shorten the duration #y.
  • the access device #y may adjust the timer so that the difference between the duration #y and the duration #x is within a preset difference range.
  • the access device #y (or access device #x) can also determine the inactive state (ie, type #x) corresponding to the duration #x, and determine the duration of the timer of the inactive state of the type #x It is a configuration object (ie, duration #y).
  • the access device #x can record the duration of each inactive state in the multiple inactive states, and the process of determining, recording, transmitting, and using the duration can be in the kth time with the terminal device #x
  • the duration of the inactive state ie, duration #A
  • duration #A is similar, and the detailed description is omitted here to avoid omitting.
  • the history information of the terminal device #x may include a duration list, and the duration list may include information on the duration of multiple inactive states of the terminal device #x.
  • the wireless communication method provided by the present application by making the terminal device record the duration of being in the inactive state, and causing the access device to configure the terminal device with a timer for the inactive state based on the duration, that is, according to the wireless communication method provided by the present application, It can provide reference and basis for the timer setting, thereby avoiding the increase of the signaling overhead due to unreasonable timer setting, that is, the power consumption of the device, which can reduce the signaling overhead and the power consumption of the terminal device, thereby improving the user experience.
  • FIG. 8 shows a schematic flow chart of an example of a wireless communication method 500 of the present application, and the method 500 shows a terminal device #z and an access device #w (or access device #z). Interactive process.
  • the method 500 can be applied to at least one of the following scenarios:
  • terminal device #z switches from the access device #z to the access device #w.
  • Access device #z may be the primary base station
  • access device #w may be the secondary base station
  • the resident base station of terminal device #z is from another base station (for example, access device #z or other access device #z The secondary base station) is changed to access device #w.
  • the access device #z may be the original camping base station of the terminal device #z, and the access device #z may be the new camping base station of the terminal device #z.
  • RNAU may occur in terminal device #z.
  • the number of times the terminal device #z generates RNAU may be one time or P times, and P is an integer greater than 1.
  • the type of the p-th RNAU may be any type from the above type ⁇ to type ⁇ , which is not particularly limited in this application.
  • the terminal device #z may determine the cell where the p-th RNAU occurs (recorded as: cell #z).
  • the information of cell #z may include, but is not limited to, PCI or CGI of cell #z, etc.
  • the terminal device #z may also determine the type #z, which is the type of the p-th occurrence of the RNAU of the terminal device #z.
  • the terminal device #z can also record the correspondence between the cell #z and the type #z.
  • the terminal device #z may record the above information in the user history information (UE history) of the terminal device #z.
  • UE history user history information
  • the user history information of this application may include the following forms of information:
  • Last visited cell list (last visited cell list)
  • the ECGI may be the ECGI of the cell (for example, the above-mentioned cell #z) where the terminal device is located when the RNAU occurs.
  • the ECGI may be the ECGI of the cell (for example, the above-mentioned cell #z) where the terminal device is located when the RNAU occurs.
  • it may be the PCI of the cell.
  • the user history information may record the information of the cell corresponding to the RNAU multiple times.
  • the terminal device #z may send the information of the cell #z to the access device #w (or, the access device #z).
  • terminal device #z may also send information of type #z to access device #w (or, access device #z).
  • the terminal device #z may also send information about the correspondence between the cell #z and the type #z to the access device #w (or, access device #z).
  • the above information may be carried in the history information of terminal device #z.
  • the information of the cell #z may be sent by the terminal device #z based on the request of the access device #w (or, access device #z), that is, in S520, the access device #w (or Incoming device #z) can send cell request information to terminal device #z, and the cell request information can be used to request terminal device #z to inform that the occurrence RNAU is in the cell where it is located.
  • the cell request information may also include type request information, which may be used to indicate that the access device #w (or, access device #z) wants the terminal device #z to provide the RNAU type corresponding to the cell, or That is, the type request information can be used to indicate that the access device #w (or, access device #z) wants the terminal device #z to provide the cell in which RNAU type occurs.
  • type request information may be used to indicate that the access device #w (or, access device #z) wants the terminal device #z to provide the cell in which RNAU type occurs.
  • the aforementioned type #z may be determined by the terminal device #z according to the type request information, or the type #z may be the type indicated by the type request information.
  • the access device #w (or, access device #z) can acquire the information of the cell #z, so that the terminal device #z can be configured with RNA according to the cell #z.
  • access device #w (or access device #z) be the cell included in the RNA configured by terminal device #z as cell set #X.
  • the access device #w (or, access device #z) may adjust the cell set #X, or adjust the cell included in the cell set #X according to the cell #z.
  • the access device #w may add the cell #z to the cell set #X.
  • the access device #z may record the RNAU of the multiple RNAUs.
  • the cell, and the process of determining, recording, transmitting, and using the information of the cell may be similar to the cell of the terminal device #z pth RNAU, and the detailed description is omitted here to avoid omitting.
  • the historical information of the terminal device #z may include a list of cells where RNAU occurs, and the cell list may include at least one of the information of the cells of the multiple RNAU of the terminal device #z and the type of RNAU.
  • the terminal device records the cell where the RNAU occurred and sends the information of the cell to the access device, so that the access device can configure RNA for the terminal device based on the cell, that is,
  • the wireless communication method provided by the present application it is possible to provide reference and basis for RNA setting, thereby avoiding the increase in the signalling overhead due to unreasonable RNA setting, that is, the power consumption of the device, and the reduction of the signalling overhead and the terminal equipment. Power consumption advances, which in turn improves the user experience.
  • the method implemented by the terminal device may also be implemented by components (such as chips or circuits) that can be used for the terminal device, and the method implemented by the access device may also be implemented by the device The components of the device (such as chips or circuits) are implemented.
  • FIG. 9 is a schematic diagram of an apparatus 600 for wireless communication provided by an embodiment of the present application.
  • the device 600 may be a terminal device, or may be a chip or a circuit, such as a chip or a circuit that can be installed in the terminal device.
  • the apparatus 600 may be an access device, or may be a chip or a circuit, such as a chip or a circuit that can be provided in the access device.
  • the apparatus 600 may include a processing unit 610 (ie, an example of a processing unit) and a storage unit 620.
  • the storage unit 620 is used to store instructions.
  • the processing unit 610 is used to execute the instructions stored by the storage unit 620, so that the apparatus 600 implements the steps performed by the terminal device (eg, terminal device #x or terminal device #z) in the above method.
  • the terminal device eg, terminal device #x or terminal device #z
  • the processing unit 610 is used to execute the instructions stored by the storage unit 620, so that the apparatus 600 implements the steps performed by the access device (for example, access device #A or access device #1) in the above method.
  • the access device for example, access device #A or access device #1
  • the device 600 may further include an input port 630 (ie, one example of a communication unit) and an output port 640 (ie, another example of a communication unit).
  • the processing unit 610, the storage unit 620, the input port 630, and the output port 640 may communicate with each other through an internal connection channel to transfer control and/or data signals.
  • the storage unit 620 is used to store computer programs, and the processing unit 610 can be used to call and run the calculator program from the storage unit 620 to control the input port 630 to receive signals and the output port 640 to send signals to complete the above method. Steps for terminal equipment.
  • the storage unit 620 may be integrated in the processing unit 610, or may be provided separately from the processing unit 610.
  • the apparatus 600 is a communication device (for example, a network device or a terminal device)
  • the input port 630 is a receiver
  • the output port 640 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 630 is an input interface
  • the output port 640 is an output interface
  • the functions of the input port 630 and the output port 640 may be implemented through a transceiver circuit or a dedicated chip for transceiver.
  • the processing unit 610 may be realized by a dedicated processing chip, a processing circuit, a processing unit, or a general-purpose chip.
  • a general-purpose computer may be considered to implement the communication device (for example, an access device or a terminal device) provided in the embodiments of the present application.
  • the program codes that implement the functions of the processing unit 610, the input port 630, and the output port 640 are stored in the storage unit 620, and the general processing unit implements the functions of the processing unit 610, the input port 630, and the output port 640 by executing the codes in the storage unit 620 .
  • the processing unit 610 is configured to determine reference information, where the reference information includes information on a first duration and/or information on a first cell, and the first duration includes a duration when the terminal device is in a deactivated state,
  • the first cell includes a cell where the terminal device updates the RNAU based on a notification area of a radio access network;
  • the output port 640 is used to send the reference information.
  • the reference information further includes information of a second cell corresponding to the first duration, and the second cell includes a cell where the terminal device is in a deactivated state corresponding to the first duration.
  • the reference information further includes information of a deactivation state type corresponding to the first duration, wherein the deactivation state type includes a session deactivation state type, a data radio bearer deactivation state type, or terminal device deactivation Activation status type.
  • the deactivation state type includes a session deactivation state type, a data radio bearer deactivation state type, or terminal device deactivation Activation status type.
  • the reference information further includes information about the type of RNAU corresponding to the first cell, where the type of RNAU includes the type of RNAU triggered periodically or the type of RNAU triggered by terminal device movement.
  • the processing unit 610 is used to record the reference information in the history information of the terminal device.
  • the input port 630 is used to receive request information and to send the reference information according to the request information.
  • the request information includes type indication information
  • the type indication information is used to indicate a first deactivation state type, where the first deactivation state type includes a session deactivation state type and a data radio bearer deactivation state Type or terminal device deactivation state type, and
  • the processing unit 610 is configured to determine the information of the first duration according to the type indication information, so that the deactivation state type corresponding to the first duration is the first deactivation state type.
  • the functions and actions of the modules or units in the device 600 listed above are only exemplary descriptions.
  • the modules or units in the device 600 may be used to perform the above method
  • Each action or processing procedure performed by the terminal device for example, terminal device #x or terminal device #z
  • each module or unit in the device 600 can be used for
  • Each action or processing procedure performed by the access device for example, access device #A or access device #1
  • the access device for example, access device #A or access device #1
  • FIG. 10 is a schematic diagram of a wireless communication apparatus 700 provided by an embodiment of the present application.
  • the apparatus 700 may be an access device (for example, access device #B, access device #2, access device #y, or access device #w), or may be a chip or a circuit, for example, it can be provided in Into the device's chip or circuit.
  • access device #B access device #B
  • access device #2 access device #y
  • access device #w access device #w
  • a chip or a circuit for example, it can be provided in Into the device's chip or circuit.
  • the apparatus 700 may include a processing unit 710 (ie, an example of a processing unit) and a storage unit 720.
  • the storage unit 720 is used to store instructions.
  • the processing unit 710 is used to execute the instructions stored by the storage unit 720 to enable the apparatus 700 to implement the access device (for example, access device #B, access device #2, access device #y or access Device #w) Steps performed.
  • the access device for example, access device #B, access device #2, access device #y or access Device #w
  • the device 700 may further include an input port 730 (ie, one example of a communication unit) and an output port 740 (ie, another example of a communication unit).
  • the processing unit 710, the storage unit 720, the input port 730, and the output port 740 can communicate with each other through an internal connection channel to transfer control and/or data signals.
  • the storage unit 720 is used to store a computer program.
  • the processing unit 710 can be used to call and run the computer program from the storage unit 720 to control the input port 730 to receive signals and the output port 740 to send signals to complete the above method. Steps for terminal equipment.
  • the storage unit 720 may be integrated in the processing unit 710, or may be provided separately from the processing unit 710.
  • the apparatus 700 is a communication device (for example, an access device)
  • the input port 730 is a receiver
  • the output port 740 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 730 is an input interface
  • the output port 740 is an output interface
  • the functions of the input port 730 and the output port 740 may be implemented through a transceiver circuit or a dedicated chip for transceiver.
  • the processing unit 710 may be realized by a dedicated processing chip, a processing circuit, a processing unit, or a general-purpose chip.
  • a general-purpose computer may be used to implement the communication device (for example, an access device) provided in the embodiments of the present application.
  • the program codes that implement the functions of the processing unit 710, the input port 730, and the output port 740 are stored in the storage unit 720, and the general processing unit implements the functions of the processing unit 710, the input port 730, and the output port 740 by executing the codes in the storage unit 720 .
  • the input port 730 is used to receive reference information, where the reference information includes information of a first duration and/or information of a first cell, and the first duration includes a duration when the terminal device is in a deactivated state,
  • the first cell includes a cell where the terminal device updates the RNAU based on the notification area of the radio access network.
  • the processing unit 710 is configured to adjust the duration of the deactivation timer of the terminal device according to the first duration
  • the processing unit 710 is configured to configure a notification area RNA based on a radio access network for the terminal device according to the first cell.
  • the reference information further includes information of a second cell corresponding to the first duration, and the second cell includes a cell where the terminal device is in a deactivated state corresponding to the first duration.
  • the reference information further includes information of a deactivation state type corresponding to the first duration, wherein the deactivation state type includes a session deactivation state type, a data radio bearer deactivation state type, or terminal device deactivation Activation status type, and
  • the processing unit 710 is configured to adjust the duration of the deactivation state timer corresponding to the deactivation state type of the first duration of the terminal device according to the first duration.
  • the reference information further includes information about the type of RNAU corresponding to the first cell, where the type of RNAU includes the type of RNAU triggered periodically or the type of RNAU triggered by terminal device movement.
  • the reference information is carried in the history information of the terminal device.
  • the output port 740 is used to send request information, and the request information is used to request the reference information.
  • the request information includes type indication information, and the type indication information is used to indicate a first deactivation state type, where the first deactivation state type includes a session deactivation state type and a data radio bearer deactivation state Type or terminal device deactivation status type.
  • the functions and actions of the modules or units in the apparatus 700 listed above are only exemplary descriptions.
  • the modules or units in the apparatus 700 may be used to perform the above method Actions or processing procedures performed by the access device (for example, access device #B, access device #2, access device #y, or access device #w), and here, in order to avoid redundancy, detailed descriptions are omitted .
  • FIG. 11 is a schematic structural diagram of a terminal device 800 provided by the present application.
  • the above apparatus 600 may be configured in the terminal device 800, or the above apparatus 600 may itself be the terminal device 800.
  • the terminal device 800 may perform the actions performed by the terminal device in the above methods 200, 300, 400, or 500.
  • FIG. 11 shows only the main components of the terminal device.
  • the terminal device 800 includes a processor, a memory, a control circuit, an antenna, and input/output devices.
  • the processor is mainly used to process the communication protocol and communication data, and control the entire terminal device, execute a software program, and process the data of the software program, for example, to support the terminal device to execute the above-mentioned transmission precoding matrix instruction method embodiment Described actions.
  • the memory is mainly used to store software programs and data, for example, the codebook described in the above embodiment.
  • the control circuit is mainly used for the conversion of the baseband signal and the radio frequency signal and the processing of the radio frequency signal.
  • the control circuit and the antenna can also be called a transceiver, which is mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, and keyboards, are mainly used to receive user input data and output data to the user.
  • the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program.
  • the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit processes the baseband signal after radio frequency processing, and then sends the radio frequency signal in the form of electromagnetic waves through the antenna.
  • the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor.
  • the processor converts the baseband signal into data and processes the data.
  • FIG. 11 only shows one memory and processor. In an actual terminal device, there may be multiple processors and memories.
  • the memory may also be referred to as a storage medium or a storage device, etc. This embodiment of the present application does not limit this.
  • the processor may include a baseband processor and a central processor.
  • the baseband processor is mainly used to process communication protocols and communication data.
  • the central processor is mainly used to control the entire terminal device, execute software programs, and process software programs. data.
  • the processor in FIG. 11 integrates the functions of the baseband processor and the central processor.
  • the baseband processor and the central processor can also be independent processors, which are interconnected through technologies such as a bus.
  • the terminal device may include multiple baseband processors to adapt to different network standards, the terminal device may include multiple central processors to enhance its processing capability, and various components of the terminal device may be connected through various buses.
  • the baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processor may also be expressed as a central processing circuit or a central processing chip.
  • the function of processing the communication protocol and the communication data may be built in the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.
  • the antenna and the control circuit with the transceiver function may be regarded as the transceiver unit 810 of the terminal device 800, and the processor with the processing function may be regarded as the processing unit 820 of the terminal device 800.
  • the terminal device 800 includes a transceiver unit 810 and a processing unit 820.
  • the transceiver unit may also be called a transceiver, a transceiver, a transceiver device, or the like.
  • the device used to implement the receiving function in the transceiver unit 810 may be regarded as a receiving unit, and the device used to implement the sending function in the transceiver unit 810 may be regarded as a transmitting unit, that is, the transceiver unit includes a receiving unit and a sending unit.
  • the receiving unit may also be referred to as a receiver, receiver, receiving circuit, etc.
  • the transmitting unit may be referred to as a transmitter, transmitter, or transmitting circuit, etc.
  • FIG. 12 is a schematic structural diagram of an access device 900 provided by an embodiment of the present application, and can be used to implement the access device (for example, access device #A, access device #B, access device #1 in the above method) , Access device #2, access device #x, access device #y, access device #z or access device #w).
  • the access device 900 includes one or more radio frequency units, such as a remote radio unit (RRU) 910 and one or more baseband units (BBU) (also called digital units, digital units, DUs) )920.
  • RRU 910 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc.
  • the RRU910 part is mainly used for the transmission and reception of radio frequency signals and the conversion of radio frequency signals and baseband signals, for example, for sending the signaling messages described in the above embodiments to the terminal device.
  • the BBU920 part is mainly used for baseband processing and controlling the base station.
  • the RRU910 and BBU920 may be physically arranged together, or may be physically separated, that is, distributed base stations.
  • the BBU920 is the control center of the base station, and may also be called a processing unit, which is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spread spectrum, and so on.
  • the BBU (processing unit) 920 may be used to control the base station 40 to perform the operation flow on the network device in the above method embodiment.
  • the BBU920 may be composed of one or more boards, and the plurality of boards may jointly support a wireless access network of a single access standard (such as an LTE system or a 5G system), or may support different interfaces. Into the standard wireless access network.
  • the BBU 920 also includes a memory 921 and a processor 922.
  • the memory 921 is used to store necessary instructions and data.
  • the memory 921 stores the codebook and the like in the above embodiment.
  • the processor 922 is used to control the base station to perform necessary actions, for example, to control the base station to execute the operation flow of the network device in the foregoing method embodiment.
  • the memory 921 and the processor 922 may serve one or more single boards. In other words, the memory and processor can be set separately on each board. It is also possible that multiple boards share the same memory and processor. In addition, each board can also be equipped with necessary circuits.
  • SoC system-on-chip
  • all or part of the functions of part 920 and part 910 may be implemented by SoC technology, for example, by a base station function chip
  • the base station functional chip integrates a processor, a memory, an antenna interface, and other devices. Programs for base station related functions are stored in the memory, and the processor executes the programs to implement the base station related functions.
  • the functional chip of the base station can also read the external memory of the chip to implement related functions of the base station.
  • FIG. 12 It should be understood that the structure of the network device illustrated in FIG. 12 is only one possible form, and should not constitute any limitation to the embodiments of the present application. This application does not exclude the possibility of other forms of base station structures that may appear in the future.
  • the embodiment of the present application further provides a communication system, which includes the foregoing access device and one or more terminal devices.
  • the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and dedicated integration Circuit (application specific integrated circuit, ASIC), ready-made programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electronically Erase programmable EPROM (EEPROM) or flash memory.
  • the volatile memory may be a random access memory (random access memory, RAM), which is used as an external cache.
  • random access memory random access memory
  • static random access memory static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access Access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • double data Srate double data Srate
  • DDR SDRAM enhanced synchronous dynamic random access memory
  • ESDRAM synchronous connection dynamic random access memory Take memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).
  • the above embodiments can be implemented in whole or in part by software, hardware, firmware, or any other combination.
  • the above-described embodiments may be fully or partially implemented in the form of computer program products.
  • the computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server or data center Transmission to another website, computer, server or data center via wired (eg infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more collections of 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 DVD), or a semiconductor medium.
  • the semiconductor medium may be a solid state drive.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • the foregoing storage media include various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种无线通信的方法和装置，该方法包括：确定参考信息，该参考信息包括第一时长的信息和/或第一小区的信息，该第一时长包括终端设备处于去激活状态的时长，该第一小区包括该终端设备发生RNAU的小区；发送该参考信息，通过使终端设备或该终端设备的源驻留接入设备记录该终端设备处于去激活状态的时长或该终端设备发生RNAU的小区，并使该终端设备的目标驻留接入设备基于该时长为终端设备配置针对去激活状态的定时器，或者，使该目标驻留接入设备基于该小区为终端设备配置RNA，能够为定时器或RNA的设置提供参考和依据，从而，能够避免因设置不合理而导致的信令开销和功耗。

Description

无线通信的方法和装置
本申请要求于2018年12月29日提交中国专利局、申请号为201811633343.6、申请名称为“无线通信的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及无线通信的方法和装置以及通信设备。
背景技术
目前，已知一种终端通信状态，即，无线资源控制(radio resource control，RRC)去激活状态，简称去激活(inactive)状态。在该inactive状态下，在该inactive状态下，核心网设备、接入设备和终端设备都保留有终端设备的上下文信息。
并且，在该现有技术中，定义了基于无线接入网(Radio Access Network，RAN)的通知区域(RAN based Notification Area，RNA)，其中，RNA由一个小区或者多个小区组成，若由多个小区组成，该多个小区属于同一基站，也可以属于不同的基站，该不同的基站可以是同一无线接入类型(Radio Access Type，RAT)的基站，也可以是不同RAT的基站。
在inactive状态下，终端设备RNA内部移动时，不会向网络侧(例如，接入设备或核心网设备)反馈信道质量状况，并在移出RNA后需要通知网络侧。
例如，设inactive状态的终端设备#X的驻留基站为基站#Y，则当inactive状态的终端设备#X发生移动时，可能会通过例如，小区重选等方式，与新的服务基站(非驻留基站，记做基站#Z)进行下行同步，例如数据传输、RNA更新(RNA update，RNAU)、进行跟踪区(Tracking Area，TA)更新、注册区(registration area)更新等，即，基站#Z可能会成为终端设备#X的驻留基站。此情况下，基站#Z需要为终端设备#X重新分配RNA。
因此，如果RNA分配不合理，可能导致终端设备频繁发生RNAU，造成信令开销增大，并增大终端设备的功耗，影响用户体验。
另外，对于inactive状态的终端，基站会设置一个针对inactive状态的定时器(timer)，具体地说，当终端设备进入于inactive状态时，该timer启动，如果timer到时后，终端设备仍然还没有数据传输，则基站可以进一步决策终端设备的状态，例如，可以使该终端设备进入空闲(IDLE)态；或者，可以寻呼该终端设备，而使终端设备进入连接态等。
例如，如果timer设置过短，可能导致当基站发现timer到时候进而控制终端设备进入IDLE态后没多久，UE又发起了与基站的通信链接，从而，导致信令开销的增加。
因此，如果timer的时长设置不合理，可能导致信令开销增大，并增大终端设备的功耗，影响用户体验。
如何合理配置inactive状态的相关参数，以降低信令开销和终端设备的功耗，成为急需解决的问题。
发明内容
本申请提供一种无线通信的方法和装置以及通信设备，能够实现inactive状态的相关参数的合理配置，降低信令开销和终端设备的功耗。
第一方面，提供了一种无线通信的方法，包括：确定参考信息，所述参考信息包括第一时长的信息和/或第一小区的信息，所述第一时长包括终端设备处于去激活状态的时长，所述第一小区包括所述终端设备发生基于无线接入网的通知区域更新RNAU的小区；发送所述参考信息。
根据本申请提供的无线通信的方法，通过使终端设备或该终端设备的源驻留接入设备记录该终端设备处于inactive状态的时长，并使该终端设备的目标驻留接入设备基于该时长为终端设备配置针对inactive状态的timer，能够为timer设置提供参考和依据，从而，能够避免因timer设置不合理而导致的信令开销；或者，通过使终端设备或终端设备的源驻留接入设备记录终端设备发生RNAU时处于的小区，并使终端设备的目标驻留接入设备基于该小区为终端设备配置RNA，从而，能够为RNA设置提供参考和依据，从而，能够避免因RNA设置不合理而导致的信令开销，进而，能够降低终端设备的功耗进，改善用户体验。
其中，“第一时长的信息”可以理解为第一时长的相关信息，或者，用于确定第一时长的信息。
其中，该第一时长的信息(或者说，相关信息)可以包括能够直接指示该第一时长的指示信息。
或者，该第一时长的信息(或者说，相关信息)可以包括能够间接确定该第一时长的指示信息。
例如，该第一时长的信息(或者说，相关信息)可以包括第一时长的起始时刻的指示信息以及第一时长的结束时刻的指示信息。
再例如，该第一时长的信息(或者说，相关信息)可以包括终端设备进入去激活状态的时刻的指示信息以终端设备结束去激活状态的时刻的指示信息。
其中，该第一方面提供的方法可以由第一接入设备执行，该参考信息的接收端可以为第二接入设备。
或者，该第一方面提供的方法可以由该终端设备执行，该参考信息的接收端可以为第二接入设备。
例如，该第二接入设备可以是该终端设备需要切换至的目标接入设备，该第一接入设备可以是该终端设备的源接入设备。
再例如，该第一接入设备可以为主基站，该第二接入设备可以为辅基站。
再例如，该第一接入设备可以为终端设备的原驻留基站，该第二接入设备可以为终端设备的新驻留基站。
需要说明的是，终端设备可以多次处于去激活状态，此情况下，该第一时长可以为多个。
并且，该多次去激活状态与多个第一时长一一对应，即，一个第一时长可以包括所对应的一次处于去激活状态的时长。
另外，所述终端设备发生基于无线接入网的通知区域更新RNAU的小区可以为一个或多个。
并且，该第一小区可以包括该一个或多个小区中的部分或全部小区。
可选地，所述参考信息还包括所述第一时长对应的第二小区的信息，所述第二小区包括所述终端设备在第一时长对应的去激活状态下所处于的小区。
从而，能够使该终端设备的目标驻留接入设备基于第一时长对应的小区的相关信息，为终端设备配置针对inactive状态的timer，从而，能够使所设定的timer进一步匹配终端设备的实际通信状态，进一步提高本申请的实用性。
可选地，所述参考信息还包括所述第一时长对应的去激活状态类型的信息，其中，所述去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型。
其中，“所述第一时长对应的去激活状态类型”可以理解为：如果该第一时长对应第一去激活状态类型，则该第一时长可以包括终端设备处于第一去激活状态类型的去激活状态的时长。
可选地，所述参考信息还包括所述第一小区对应的RNAU类型的信息，所述RNAU类型包括周期性触发RNAU类型或终端设备移动触发RNAU类型。
其中，“所述第一小区对应的RNAU类型”可以理解为：在该第一小区发生的RNAU的类型。
可选地，所述方法还包括：将所述参考信息记录在所述终端设备的历史信息中。
从而，能够实现基于现有的信令或信息承载参考信息，能够进一步节省信令开销。
可选地，所述方法还包括：接收请求信息；以及所述发送所述参考信息，包括：根据所述请求信息，发送所述参考信息。
可选地，所述请求信息包括类型指示信息，所类型指示信息用于指示第一去激活状态类型，其中，所述第一去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型，以及所述确定参考信息包括：根据所述类型指示信息确定所述第一时长的信息。
其中，根据所述类型指示信息所确定的第一时长对应的去激活状态类型为所述第一去激活状态类型。
从而，能够使该终端设备的目标驻留接入设备基于第一时长对应的去激活类型，为终端设备配置针对相应去激活类型的inactive状态的timer，从而，能够使所设定的timer进一步匹配终端设备的实际通信状态，进一步提高本申请的实用性。
可选地，当所述方法由第一接入设备执行时，所述方法还包括：接收第三接入设备发送的第一指示信息，所述第一指示信息用于指示所述第一时长；或者接收第三接入设备发送的第二指示信息，所述第二指示信息用于指示所述终端设备进入去激活状态的时刻以及所述终端设备结束区激活状态的时刻；其中，所述第一接入设备包括集中式单元CU，所述第三接入设备包括分布式单元DU，或者所述第一接入设备包括集中式单元控制面CU-CP实体，所述第三接入设备包括集中式单元用户面CU-UP实体；其中，所述CU中 配置有分组数据汇聚层协议PDCP层、无线资源控制RRC层的至少一个协议层；所述DU中配置有无线链路控制RLC层、媒体接入控制MAC层和物理PHY层的至少一个协议层。
需要说明的是，“所述第二指示信息用于指示所述终端设备进入去激活状态的时刻以及所述终端设备结束区激活状态的时刻”可以理解为，该第二指示信息为一个，并且，所述终端设备进入去激活状态的时刻的信息以及所述终端设备结束区激活状态的时刻的信息承载于该同一个第二指示信息中，或者说，所述终端设备进入去激活状态的时刻的信息以及所述终端设备结束区激活状态的时刻的信息可以同步发送。
“所述第二指示信息用于指示所述终端设备进入去激活状态的时刻以及所述终端设备结束区激活状态的时刻”可以理解为，该第二指示信息为两个，并且，所述终端设备进入去激活状态的时刻的信息以及所述终端设备结束区激活状态的时刻的信息分别承载于该不同的第二指示信息中，或者说，所述终端设备进入去激活状态的时刻的信息以及所述终端设备结束区激活状态的时刻的信息可以异步发送。
可选地，当所述方法由第一接入设备执行，且所述参考信息包括第一时长的信息时，所述发送所述参考信息，包括：向第二接入设备发送所述参考信息，其中所述第一接入设备包括DU，所述第二接入设备包括CU，或者所述第一接入设备包括CU-UP实体，所述第二接入设备包括CU-CP实体；其中，所述CU中配置有PDCP层和RRC层的至少一个协议层；所述DU中配置有RLC层、MAC层和PHY层的至少一个协议层。
可选地，该方法还包括：根据所述第一时长，调节所述终端设备的去激活状态定时器的时长。
可选地，该方法还包括：根据所述第一小区，为所述终端设备配置基于无线接入网的通知区域RNA。
第二方面，提供了一种无线通信的方法，包括：接收参考信息，所述参考信息包括第一时长的信息和/或第一小区的信息，所述第一时长包括终端设备处于去激活状态的时长，所述第一小区包括所述终端设备发生基于无线接入网的通知区域更新RNAU的小区；根据所述第一时长，调节所述终端设备的去激活状态定时器的时长；或者根据所述第一小区，为所述终端设备配置基于无线接入网的通知区域RNA。
根据本申请提供的无线通信的方法，通过使终端设备或该终端设备的驻留接入设备记录该终端设备处于inactive状态的时长，从而使得接入设备基于该时长为终端设备配置针对inactive状态的timer，能够为timer设置提供参考和依据，从而，能够避免因timer设置不合理而导致的信令开销；或者，通过使终端设备或终端设备的驻留接入设备记录终端设备发生RNAU时处于的小区，并使得接入设备基于该小区为终端设备配置RNA，从而，能够为RNA设置提供参考和依据，从而，能够避免因RNA设置不合理而导致的信令开销，进而，能够降低终端设备的功耗进，改善用户体验。
其中，“根据所述第一时长，调节所述终端设备对应的去激活状态定时器的时长”可以理解为根据第一时长调节终端设备对应的专用定时器的时长。
或者，“根据所述第一时长，调节所述终端设备对应的去激活状态定时器的时长”可以理解为根据第一时长调节该终端设备所处于的小区内的所有终端设备对应的公共定时器的时长。
或者，“根据所述第一时长，调节所述终端设备对应的去激活状态定时器的时长”可 以理解为根据第一时长调节该终端设备的服务接入设备覆盖范围内的所有终端设备对应的公共定时器的时长。
或者，“根据所述第一时长，调节所述终端设备对应的去激活状态定时器的时长”可以理解为根据第一时长调节包括该终端设备在内的第一终端设备组内的所有终端设备对应的公共定时器的时长。
另外，“根据所述第一小区，为所述终端设备配置基于无线接入网的通知区域RNA”可以理解为根据所述第一小区配置针对终端设备的专用RNA。并且，此情况下，可以通过终端设备的专业信令向终端设备发送该RNA。
或者，“根据所述第一小区，为所述终端设备配置基于无线接入网的通知区域RNA”可以理解为根据所述第一小区配置针对该终端设备所处于的小区(或者说，该小区内的所有终端设备)的公共RNA。并且，此情况下，可以通过小区的系统信息向发送该RNA。
或者，“根据所述第一小区，为所述终端设备配置基于无线接入网的通知区域RNA”可以理解为根据所述第一小区配置针对该终端设备的服务接入设备(或者说，该服务接入设备的覆盖范围内的所有终端设备)的公共RNA。
或者，“根据所述第一小区，为所述终端设备配置基于无线接入网的通知区域RNA”可以理解为根据所述第一小区配置针对包括该终端设备在内的第一终端设备组内的公共RNA。
其中，“第一时长的信息”可以理解为第一时长的相关信息，或者，用于确定第一时长的信息。
其中，该第一时长的信息(或者说，相关信息)可以包括能够直接指示该第一时长的指示信息。
或者，该第一时长的信息(或者说，相关信息)可以包括能够间接确定该第一时长的指示信息。
例如，该第一时长的信息(或者说，相关信息)可以包括第一时长的起始时刻的指示信息以及第一时长的结束时刻的指示信息。
再例如，该第一时长的信息(或者说，相关信息)可以包括终端设备进入去激活状态的时刻的指示信息以终端设备结束去激活状态的时刻的指示信息。
其中，该第二方面提供的方法可以由第二接入设备执行，该参考信息的发送端可以为第一接入设备。
或者，该第二方面提供的方法可以由该第二接入设备执行，该参考信息的发送端可以为终端设备。
例如，该第二接入设备可以是该终端设备需要切换至的目标接入设备，该第一接入设备可以是该终端设备的源接入设备。
再例如，该第一接入设备可以为主基站，该第二接入设备可以为辅基站。
再例如，该第一接入设备可以为终端设备的原驻留基站，该第二接入设备可以为终端设备的新驻留基站。
需要说明的是，终端设备可以多次处于去激活状态，此情况下，该第一时长可以为多个。
并且，该多次去激活状态与多个第一时长一一对应，即，一个第一时长可以包括所对 应的一次处于去激活状态的时长。
另外，所述终端设备发生基于无线接入网的通知区域更新RNAU的小区可以为一个或多个。
并且，该第一小区可以包括该一个或多个小区中的部分或全部小区。
可选地，所述参考信息还包括所述第一时长对应的第二小区的信息，所述第二小区包括所述终端设备在第一时长对应的去激活状态下所处于的小区。
例如，所述根据所述第一时长，调节所述终端设备的去激活状态定时器的时长，包括：根据所述第一时长，调节所述终端设备在第三小区的去激活状态定时器的时长，其中，该第三小区与所述第二小区对应。
例如，“第三小区与所述第二小区对应”可以理解为第三小区与所述第二小区为同一小区。
例如，“第三小区与所述第二小区对应”可以理解为第三小区与所述第二小区的预设参数的相似度大于或等于预设相似度。
可选地，所述参考信息还包括所述第一时长对应的去激活状态类型的信息，其中，所述去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型。
此情况下，所述根据所述第一时长，调节所述终端设备的去激活状态定时器的时长，包括：根据所述第一时长，调节所述终端设备所述第一时长对应的去激活状态类型的去激活状态定时器的时长。
可选地，所述参考信息还包括所述第一小区对应的RNAU类型的信息，所述RNAU类型包括周期性触发RNAU类型或终端设备移动触发RNAU类型。
其中，“所述第一小区对应的RNAU类型”可以理解为：在该第一小区发生的RNAU的类型。
可选地，所述参考信息携带于所述终端设备的历史信息中。
可选地，所述方法还包括：发送请求信息，所述请求信息用于请求所述参考信息。
可选地，所述请求信息包括类型指示信息，所类型指示信息用于指示第一去激活状态类型，其中，所述第一去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型。
可选地，所述方法由第二接入设备执行，以及所述接收参考信息，包括：接收第一接入设备发送的第一时长的信息，其中，所述第一接入设备包括分布式单元DU，所述第二接入设备包括集中式单元CU，或者所述第一接入设备包括集中式单元用户面CU-UP实体，所述第二接入设备包括集中式单元控制面CU-CP实体；其中，所述CU中配置有PDCP层和RRC层中的至少一层；所述DU中配置有RLC层、MAC层和PHY层中的至少一层。
第三方面，提供了一种无线通信的装置，包括：处理单元，用于确定参考信息，所述参考信息包括第一时长的信息和/或第一小区的信息，所述第一时长包括终端设备处于去激活状态的时长，所述第一小区包括所述终端设备发生基于无线接入网的通知区域更新RNAU的小区；收发单元，用于发送所述参考信息。
其中，该装置可以配置在或本身即为第一接入设备，该参考信息的接收端可以为第二接入设备。
或者，该装置可以配置在或本身即为终端设备，该参考信息的接收端可以为第二接入设备。
例如，该第二接入设备可以是该终端设备需要切换至的目标接入设备，该第一接入设备可以是该终端设备的源接入设备。
再例如，该第一接入设备可以为主基站，该第二接入设备可以为辅基站。
再例如，该第一接入设备可以为终端设备的原驻留基站，该第二接入设备可以为终端设备的新驻留基站。
可选地，所述参考信息还包括所述第一时长对应的第二小区的信息，所述第二小区包括所述终端设备在第一时长对应的去激活状态下所处于的小区。
可选地，所述参考信息还包括所述第一时长对应的去激活状态类型的信息，其中，所述去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型。
可选地，所述参考信息还包括所述第一小区对应的RNAU类型的信息，所述RNAU类型包括周期性触发RNAU类型或终端设备移动触发RNAU类型。
从而，能够使该终端设备的目标驻留接入设备基于RNAU类型的相关信息，为终端设备配置针对RNA，从而，能够使所设定的RNA进一步匹配终端设备的实际通信状态，进一步提高本申请的实用性。
可选地，所述处理单元还用于将所述参考信息记录在所述终端设备的历史信息中。
可选地，所述收发单元还用于接收请求信息，并用于根据所述请求信息，发送所述参考信息。
可选地，所述请求信息包括类型指示信息，所类型指示信息用于指示第一去激活状态类型，其中，所述第一去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型。
可选地，所述处理单元用于根据所述类型指示信息确定所述第一时长的信息，以使所述第一时长对应的去激活状态类型为所述第一去激活状态类型。
可选地，当所述装置配置在或本身即为第一接入设备时，所述收发单元还用于接收第三接入设备发送的第一指示信息，所述第一指示信息用于指示所述第一时长；或者所述收发单元还用于接收第三接入设备发送的第二指示信息，所述第二指示信息用于指示所述终端设备进入去激活状态的时刻以及所述终端设备结束区激活状态的时刻；其中，所述第一接入设备包括集中式单元CU，所述第三接入设备包括分布式单元DU，或者所述第一接入设备包括集中式单元控制面CU-CP实体，所述第三接入设备包括集中式单元用户面CU-UP实体；其中，所述CU中配置有分组数据汇聚层协议PDCP层、无线资源控制RRC层；所述DU中配置有无线链路控制RLC层、媒体接入控制MAC层和物理PHY层。
可选地，当所述装置配置在或本身即为第一接入设备，且所述参考信息包括第一时长的信息时，所述收发单元具体用于向第二接入设备发送所述参考信息，其中所述第一接入设备包括DU，所述第二接入设备包括CU，或者所述第一接入设备包括CU-UP实体，所述第二接入设备包括CU-CP实体；其中，所述CU中配置有PDCP层和RRC层；所述DU中配置有RLC层、MAC层和PHY层。
其中，该装置中的各单元分别用于执行上述第一方面以及第一方面的各实现方式中的 通信方法的各步骤。
在一种设计中，该装置为通信芯片，通信芯片可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
在另一种设计中，所述装置为通信设备，通信设备可以包括用于发送信息或数据的发射机，以及用于接收信息或数据的接收机。
第四方面，提供了一种无线通信的装置，包括：收发单元，用于接收参考信息，所述参考信息包括第一时长的信息和/或第一小区的信息，所述第一时长包括终端设备处于去激活状态的时长，所述第一小区包括所述终端设备发生基于无线接入网的通知区域更新RNAU的小区；处理单元，用于根据所述第一时长，调节所述终端设备的去激活状态定时器的时长，或者，用于根据所述第一小区，为所述终端设备配置基于无线接入网的通知区域RNA。
其中，该装置可以配置在或本身即为第二接入设备执行，该参考信息的发送端可以为第一接入设备。
或者，该装置可以配置在或本身即为第二接入设备执行，该参考信息的发送端可以为终端设备。
例如，该第二接入设备可以是该终端设备需要切换至的目标接入设备，该第一接入设备可以是该终端设备的源接入设备。
再例如，该第一接入设备可以为主基站，该第二接入设备可以为辅基站。
再例如，该第一接入设备可以为终端设备的原驻留基站，该第二接入设备可以为终端设备的新驻留基站。
可选地，所述参考信息还包括所述第一时长对应的第二小区的信息，所述第二小区包括所述终端设备在第一时长对应的去激活状态下所处于的小区。
可选地，所述参考信息还包括所述第一时长对应的去激活状态类型的信息，其中，所述去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型，以及
根据所述第一时长，调节所述终端设备的去激活状态定时器的时长，包括：
根据所述第一时长，调节所述终端设备所述第一时长对应的去激活状态类型的去激活状态定时器的时长。
可选地，所述参考信息还包括所述第一小区对应的RNAU类型的信息，所述RNAU类型包括周期性触发RNAU类型或终端设备移动触发RNAU类型。
可选地，所述参考信息携带于所述终端设备的历史信息中。
可选地，所述收发单元还用于发送请求信息，所述请求信息用于请求所述参考信息。
可选地，所述请求信息包括类型指示信息，所类型指示信息用于指示第一去激活状态类型，其中，所述第一去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型。
可选地，所述装置配置在或本身即为第二接入设备执行，以及所述收发单元用于接收第一接入设备发送的第一时长的信息，其中，所述第一接入设备包括分布式单元DU，所述第二接入设备包括集中式单元CU，或者所述第一接入设备包括集中式单元用户面CU-UP实体，所述第二接入设备包括集中式单元控制面CU-CP实体；其中，所述CU中 配置有PDCP层和RRC层中的至少一个协议层；所述DU中配置有RLC层、MAC层和PHY层中的至少一个协议层。
其中，该装置中的各单元分别用于执行上述第二方面以及第二方面的各实现方式中的通信方法的各步骤。
在一种设计中，该通信装置为通信芯片，通信芯片可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
在另一种设计中，所述通信装置为通信设备，通信芯片可以包括用于发送信息或数据的发射机，以及用于接收信息或数据的接收机。
第五方面，提供了一种通信设备，包括，处理器，存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该通信设备执行第一方面及其各种可能实现方式中的通信方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
可选的，该转发设备还包括，发射机(发射器)和接收机(接收器)。
第六方面，提供了一种通信设备，包括，处理器，存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该通信设备执行第二方面及其各种实现方式中的通信方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
可选地，该终端设备还包括，发射机(发射器)和接收机(接收器)。
第七方面，提供了一种通信系统，上述第五方面提供的通信设备和/或第六方面提供的通信设备。
在一个可能的设计中，该通信系统还可以包括本申请实施例提供的方案中与通信设备进行交互的其他设备。
第八方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面或第二方面中任一种可能实现方式中的方法。
第九方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面或第二方面中任一种可能实现方式中的方法。
第十方面，提供了一种芯片系统，包括存储器和处理器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得安装有该芯片系统的通信设备执行上述第一方面或第二方面中任一种可能实现方式中的方法。
其中，该芯片系统可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
根据本申请提供的无线通信的方法，通过使终端设备或该终端设备的源驻留接入设备记录该终端设备处于inactive状态的时长，并使该终端设备的目标驻留接入设备基于该时 长为终端设备配置针对inactive状态的timer，能够为timer设置提供参考和依据，从而，能够避免因timer设置不合理而导致的信令开销；或者，通过使终端设备或终端设备的源驻留接入设备记录终端设备发生RNAU时处于的小区，并使终端设备的目标驻留接入设备基于该小区为终端设备配置RNA，从而，能够为RNA设置提供参考和依据，从而，能够避免因RNA设置不合理而导致的信令开销，进而，能够降低终端设备的功耗进，改善用户体验。
附图说明
图1是本申请的通信系统的一例的示意性结构图。
图2是本申请的接入设备的一例的示意性结构图。
图3是本申请的接入设备的另一例的示意性结构图。
图4是本申请的通信系统的另一例的示意性结构图。
图5是本申请的无线通信过程的一例的示意性交互图。
图6是本申请的无线通信过程的另一例的示意性交互图。
图7是本申请的无线通信过程的再一例的示意性交互图。
图8是本申请的无线通信过程的再一例的示意性交互图。
图9是本申请的无线通信的装置的一例的示意性框图。
图10是本申请的无线通信的装置的另一例的示意性框图。
图11是本申请的终端设备的一例的示意性结构图。
图12是本申请的接入设备的一例的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、未来的第五代(5th generation，5G)系统或新无线(new radio，NR)等。
本申请实施例中的终端设备也可以称为：用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧 家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是物联网(internet of things，IoT)系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。
在本申请实施例中，IOT技术可以通过例如窄带(narrow band)NB技术，做到海量连接，深度覆盖，终端省电。例如，NB只包括一个资源块(resource bloc，RB)，即，NB的带宽只有180KB。要做到海量接入，必须要求终端在接入上是离散的，根据本申请实施例的通信方法，能够有效解决IOT技术海量终端在通过NB接入网络时的拥塞问题。
另外，本申请实施例中的接入设备可以是用于与终端设备通信的设备，该接入设备也可以称为接入网设备或无线接入网设备，可以是全球移动通信(global system for mobile communications，GSM)系统或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(evolved NodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该接入设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的接入设备或者未来演进的PLMN网络中的接入设备等，可以是WLAN中的接入点(access point，AP),可以是新型无线系统(new radio，NR)系统中的gNB本申请实施例并不限定。
另外，在本申请实施例中，接入设备是RAN中的设备，或者说，是将终端设备接入到无线网络的RAN节点。例如，作为示例而非限定，作为接入设备，可以列举：gNB、传输接收点(transmission reception point，TRP)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wifi)接入点(access point，AP)等。在一种网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit， DU)节点、或包括CU节点和DU节点的RAN设备、或者控制面CU节点(CU-CP节点)和用户面CU节点(CU-UP节点)以及DU节点的RAN设备。
接入设备为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与接入设备进行通信，该小区可以是接入设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(small cell)对应的基站，这里的小小区可以包括：城市小区(metro cell)、微小区(micro cell)、微微小区(pico cell)、毫微微小区(femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
此外，LTE系统或5G系统中的载波上可以同时有多个小区同频工作，在某些特殊场景下，也可以认为上述载波与小区的概念等同。例如在载波聚合(carrier aggregation，CA)场景下，当为UE配置辅载波时，会同时携带辅载波的载波索引和工作在该辅载波的辅小区的小区标识(cell indentification，Cell ID)，在这种情况下，可以认为载波与小区的概念等同，比如终端设备接入一个载波和接入一个小区是等同的。
图1示出了本申请实施例提供的一种网络架构的示意图，如图1所示，终端设备可以同时与两个接入设备存在通信连接并可收发数据，可以称之为双链接(dual-connectivity，DC)。该两个接入设备之中，可以有一个接入设备负责与该终端设备交互无线资源控制消息，并负责和核心网控制平面实体交互，那么，该接入设备可以称之为主基站(master node，MN)，则另一个无线接入网设备可以称之为辅基站(secondary node，SN)。
类似的，终端设备也可以同时与多个接入设备存在通信连接并可收发数据，可以称之为多连接或者多链接(multi-connectivity，MC)，该多个接入设备之中，可以有一个接入设备负责与该终端设备交互无线资源控制消息，并负责和核心网控制平面实体交互，那么，该接入设备可以称之为MN，则其余的接入设备可以称之为SN。
在本申请中，接入设备可以是LTE制式的eNB基站，也可以是NR制式的gNB基站，可以是双链接架构下的主基站(master node，MN)，可以是双链接架构下的辅基站，可以是多链接架构下的MN，也可以是多链接下的SN。
图2示出了本申请实施例提供的一种网络架构的示意图。如图2所示，接入设备可以包括基带装置和射频装置，其中基带装置可以由一个节点实现，也可以由多个节点实现，射频装置可以从基带装置拉远独立实现，也可以集成基带装置中，或者部分拉远部分集成在基带装置中。例如，在LTE通信系统中，RAN设备(eNB)包括基带装置和射频装置，其中射频装置可以相对于基带装置拉远布置，例如射频拉远单元(remote radio unit，RRU)相对于BBU拉远布置。
RAN设备和终端设备之间的通信遵循一定的协议层结构。例如控制面协议层结构可以包括无线资源控制(radio resource control，RRC)层、分组数据汇聚层协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层等协议层的功能。用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层等协议层的功能；在一种实现中，PDCP层之上还可以包括业务数据适配(service data adaptation protocol，SDAP)层。
这些协议层的功能可以由一个节点实现，或者可以由多个节点实现；例如，在一种演进结构中，RAN设备可以包括集中单元(centralized unit，CU)和分布单元(distributed unit， DU)，多个DU可以由一个CU集中控制。
如图2所示，CU和DU可以根据无线网络的协议层划分，例如PDCP层及以上协议层的功能设置在CU，PDCP以下的协议层，例如RLC层和MAC层等的功能设置在DU。或者说，CU具有PDCP层以上(含PDCP、RRC和SDAP)功能，DU具有PDCP层以下(含RLC、MAC和PHY)功能。
这种协议层的划分仅仅是一种举例，还可以在其它协议层划分，例如在RLC层划分，将RLC层及以上协议层的功能设置在CU，RLC层以下协议层的功能设置在DU；或者，在某个协议层中划分，例如将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。此外，也可以按其它方式划分，例如按时延划分，将处理时间需要满足时延要求的功能设置在DU，不需要满足该时延要求的功能设置在CU。
此外，射频装置可以拉远，不放在DU中，也可以集成在DU中，或者部分拉远部分集成在DU中，在此不作任何限制。
图3示出了适用于本申请实施例的网络架构的又一示意图。相对于图2所示的架构，还可以将CU的控制面(CP)和用户面(UP)分离，分成不同实体来实现，分别为控制面CU实体(CU-CP实体)和用户面CU实体(CU-UP实体)。
在以上网络架构中，CU产生的信令可以通过DU发送给终端设备，或者终端设备产生的信令可以通过DU发送给CU。DU可以不对该信令进行解析而直接通过协议层封装而透传给终端设备或CU。以下实施例中如果涉及这种信令在DU和终端设备之间的传输，此时，DU对信令的发送或接收包括这种场景。例如，RRC或PDCP层的信令最终会处理为PHY层的信令发送给终端设备，或者，由接收到的PHY层的信令转变而来。在这种架构下，该RRC或PDCP层的信令，即也可以认为是由DU发送的，或者，由DU和射频发送的。
在以上实施例中CU划分为RAN侧的网络设备，此外，也可以将CU划分为CN侧的网络设备，在此不做限制。
本申请以下实施例中的装置，根据其实现的功能，可以位于终端设备或网络设备。当采用以上CU-DU的结构时，网络设备可以为CU节点、或DU节点、或包括CU节点和DU节点的RAN设备。
图4是能够适用本申请实施例通信方法的系统100的示意图。如图4所示，该系统100包括接入设备102，接入设备102可包括1个天线或多个天线例如，天线104、106、108、110、112和114。另外，接入设备102可附加地包括发射机链和接收机链，本领域普通技术人员可以理解，它们均可包括与信号发送和接收相关的多个部件(例如处理器、调制器、复用器、解调器、解复用器或天线等)。
接入设备102可以与多个终端设备(例如终端设备116和终端设备122)通信。然而，可以理解，接入设备102可以与类似于终端设备116或终端设备122的任意数目的终端设备通信。终端设备116和122可以是例如蜂窝电话、智能电话、便携式电脑、手持通信设备、手持计算设备、卫星无线电装置、全球定位系统、PDA和/或用于在无线通信系统100上通信的任意其它适合设备。
如图4所示，终端设备116与天线112和114通信，其中天线112和114通过前向链 路(也称为下行链路)118向终端设备116发送信息，并通过反向链路(也称为上行链路)120从终端设备116接收信息。此外，终端设备122与天线104和106通信，其中天线104和106通过前向链路124向终端设备122发送信息，并通过反向链路126从终端设备122接收信息。
例如，在频分双工(frequency division duplex，FDD)系统中，例如，前向链路118可与反向链路120使用不同的频带，前向链路124可与反向链路126使用不同的频带。
再例如，在时分双工(time division duplex，TDD)系统和全双工(full duplex)系统中，前向链路118和反向链路120可使用共同频带，前向链路124和反向链路126可使用共同频带。
被设计用于通信的每个天线(或者由多个天线组成的天线组)和/或区域称为接入设备102的扇区。例如，可将天线组设计为与接入设备102覆盖区域的扇区中的终端设备通信。接入设备可以通过单个天线或多天线发射分集向其对应的扇区内所有的终端设备发送信号。在接入设备102通过前向链路118和124分别与终端设备116和122进行通信的过程中，接入设备102的发射天线也可利用波束成形来改善前向链路118和124的信噪比。此外，与接入设备通过单个天线或多天线发射分集向它所有的终端设备发送信号的方式相比，在接入设备102利用波束成形向相关覆盖区域中随机分散的终端设备116和122发送信号时，相邻小区中的移动设备会受到较少的干扰。
在给定时间，接入设备102、终端设备116或终端设备122可以是无线通信发送装置和/或无线通信接收装置。当发送数据时，无线通信发送装置可对数据进行编码以用于传输。具体地，无线通信发送装置可获取(例如生成、从其它通信装置接收、或在存储器中保存等)要通过信道发送至无线通信接收装置的一定数目的数据比特。这种数据比特可包含在数据的传输块(或多个传输块)中，传输块可被分段以产生多个码块。
此外，该通信系统100可以是PLMN网络、D2D网络、M2M网络、IoT网络或者其他网络，图4只是举例的简化示意图，网络中还可以包括其他接入设备，图4中未予以画出。
应理解，上述图1至图4仅是示例性说明，不应对本申请构成任何限定。例如，通信系统还可以包括核心网设备，核心网设备可以与多个接入网设备连接，用于控制接入网设备，并且，可以将从网络侧(例如，互联网)接收到的数据分发至接入网设备。
在本申请实施例中，终端设备或接入设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备或网络设备，或者，是终端设备或网络设备中能够调用程序并执行程序的功能模块。
另外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技 术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于:磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
下面，对本申请中的inactive状态进行说明。
作为示例而非限定，在本申请中，inactive状态可以包括以下一种或多种类型：
类型1：会话去激活状态类型
具体地说，该会话去激活状态类型可以理解为会话粒度的去激活类型。
即，假设终端设备当前有M个会话，则当该M个会话中的至少一个会话(记做，会话#m)满足触发进入会话去激活状态的条件(记做，条件1)时，可以确定终端设备进入会话去激活状态。
在进入会话去激活状态后，核心网设备、接入设备和终端设备可以保留该会话#m的上下文。
作为示例而非限定，该条件1可以包括但不限于以下条件：
如果会话#m没有数据传输的时长超过预设的时长#m，则判定终端设备进入会话去激活状态。其中，该时长#m可以是通信系统或通信协议规定的，或者，该时长#m可以是接入设备或核心网设备配置的，或者，该时长#m可以是管理员或运营商配置的，本申请并未特别限定。
应理解，以上列举的条件1仅为进入会话去激活状态的条件的一例，本申请并未限定于此，其他能够用于判定终端是否进入会话去激活状态的条件均落入本申请的保护范围。
另外，作为示例而非限定，该“会话”可以包括但不限于协议数据单元(protocol data unit，PDU)会话(session)。
类型2：承载去激活状态类型
具体地说，该承载去激活状态类型可以理解为承载粒度的去激活类型。
即，假设终端设备当前有N个承载，则当该N个承载中的至少一个承载(记做，承载#n)满足触发进入承载去激活状态的条件(记做，条件2)时，可以确定终端设备进入承载去激活状态。
在进入承载去激活状态后，核心网设备、接入设备和终端设备可以保留该承载#n的上下文。
作为示例而非限定，该条件2可以包括但不限于以下条件：
如果承载#n没有数据传输的时长超过预设的时长#n，则判定终端设备进入承载去激活状态。其中，该时长#n可以是通信系统或通信协议规定的，或者，该时长#n可以是接入设备或核心网设备配置的，或者，该时长#n可以是管理员或运营商配置的，本申请并未特别限定。
应理解，以上列举的条件2仅为进入承载去激活状态的条件的一例，本申请并未限定于此，其他能够用于判定终端是否进入承载去激活状态的条件均落入本申请的保护范围。
另外，作为示例而非限定，该“承载”可以包括但不限于数据无线承载(data radio bearer，DRB)。
类型3：终端去激活状态类型
具体地说，该终端去激活状态类型可以理解为终端粒度的去激活类型。
即，终端网络侧只有连接管理(connection management，CM)连接态，所述CM连接态是NAS层维护的状态，即UE与核心网的NAS信令连接还是存在的，UE与RAN的信令连接没有了。
或者，假设终端设备当前有N个承载和M个会话，则当该N个承载中的每个承载满足触发进入承载去激活状态的条件(即，上述条件2)，且该M个会话中的每个会话满足触发进入会话去激活状态的条件(即，上述条件1)，可以确定终端设备#A进入终端去激活状态。
在进入终端去激活状态后，核心网设备、接入设备和终端设备可以保留该终端设备的上下文，并且，终端设备在RNA内部移动时接入设备不感知终端设备的行为。
应理解，以上列举的条件仅为进入终端去激活状态的条件的一例，本申请并未限定于此，其他能够用于判定终端是否进入终端去激活状态的条件均落入本申请的保护范围。
并且，在本申请中，当终端设备进入inactive状态后，终端设备或接入设备发生以下任意一种事件，则可以判定为终端设备结束inactive状态。
事件1：定时器到时(或者说，超时)
具体地说，当终端设备进入inactive状态后，终端设备(和/或接入设备)可以启动定时器，并且，如果定时器到时(或者说，超时)后，如果终端设备仍然没有数据传输，则终端设备(和/或接入设备)可以确定该终端设备结束inactive状态。并且，例如，终端设备(和/或接入设备)可以确定该终端设备进入空闲(idle)状态或者连接状态，例如，接入设备可以向该终端设备发起寻呼，以使终端设备进入连接状态，或者接入设备向该终端设备发起RRC连接释放命令，以使得终端设备进入空闲态。事件2：终端设备发生周期性的RNAU
具体地说，进入inactive状态后的终端设备，如果配置了周期性的RNAU，当进行RNAU的时候，接入设备检测到RNAU的时候，该接入设备要通知源接入设备该终端设备的inactive状态结束。
事件3：终端设备需要进行数据传输
具体地说，进入inactive状态后的终端设备，如果需要传输数据(例如，需要发送上行数据)，则可以结束inactive状态，例如，可以进入连接状态。
或者，在本申请中，当终端设备的某个会话进入inactive状态后，终端设备或接入设备发生以下任意一种事件，则可以判定为终端设备结束某个会话的inactive状态。
事件4：定时器到时(或者说，超时)
具体地说，当终端设备的某个会话进入inactive状态后，终端设备(和/或接入设备)可以启动定时器，并且，如果定时器到时(或者说，超时)后，如果终端设备的所述会话仍然没有数据传输，则终端设备(和/或接入设备)可以确定该终端设备的所述会话结束inactive状态。并且，例如，终端设备(和/或接入设备)可以确定释放该终端设备的所述会话或者激活所述会话。
其中，所述定时器是会话粒度(或者说，会话去激活状态类型)的inactive状态的定时器。
事件5：接入设备指示终端设备的某个会话进行状态变更
具体地说，某个会话进入inactive状态后的终端设备，如果检测到接入设备发送的指示信息，则所述会话可以结束inactive状态，例如，终端设备可以重新激活该会话。
事件6：终端设备需要进行数据传输
具体地说，某个会话进入inactive状态后的终端设备，如果所述会话有业务，则可以结束inactive状态，例如，终端设备可以主动激活该会话。
或者，在本申请中，当终端设备的某个承载进入inactive状态后，终端设备或接入设备发生以下任意一种事件，则可以判定为终端设备的某个承载结束inactive状态。
事件7：定时器到时(或者说，超时)
具体地说，当终端设备的某个承载进入inactive状态后，终端设备(和/或接入设备)可以启动定时器，并且，如果定时器到时(或者说，超时)后，如果终端设备的所述承载仍然没有数据传输，则终端设备(和/或接入设备)可以确定该终端设备的所述承载结束inactive状态。并且，例如，终端设备(和/或接入设备)可以确定释放该终端设备的所述承载或者重进建立所述承载。
其中，所述定时器是承载粒度(或者说，承载去激活状态类型)的inactive状态的定时器。
事件8：接入设备指示终端设备的某个承载进行状态变更
具体地说，某个承载进入inactive状态后的终端设备，如果检测到接入设备发送的指示信息，则所述承载可以结束inactive状态，例如，可以重新建立该承载。
应理解，以上列举的事件仅为触发终端设备结束去激活状态的事件的一例，本申请并未限定于此，其他能够用于触发终端设备结束去激活状态的事件均落入本申请的保护范围。
下面，对本申请中的RNAU进行说明。
具体地说，接入设备可以为其服务的终端设备配置该终端设备在inactive状态下的无线网络区域。该无线网络区域可以称为基于无线接入网的通知区域(RAN basednotification area，RNA)。接入设备可以通过专用信令下发该RNA的信息给终端终端设备。
在本申请中，RNA可以覆盖一个小区或者多个小区。
例如，接入设备(gNB)可以为终端设备提供一个明确的小区列表作为RNA。
再例如，接入设备(gNB)可以为终端设备一个RAN area ID列表作为RNA，这里，RAN area可以是CN Tracking Area的一个子集或者等于CN Tracking Area，一个RAN area对应一个RAN area ID，一个RAN area由TAI和一个可选的RAN area Code组成。
一个小区会在其系统消息广播它的RAN area ID。
当终端设备在inactive状态下重选到该RNA内的小区时可以不通知网络，当终端设备在inactive状态下重选到该RNA外的小区时可以通知网络。
从而，接入设备在需要寻呼inactive状态的终端设备时，可以在RNA内的小区进行寻呼。
在本申请中，可能发生RNA更新(即，RNAU)。
并且，根据RNAU发生的原因不同，可以将RNAU划分为以下多种类型：
类型α：因终端设备移动而导致的RNAU，即，当终端设备移动出接入设备为其分配的RNA时，需要进行RNAU。
类型β：周期性发生的RNAU，或者说，RNA定时器超时而出发的RNAU，所述RNA定时器可以是由基站配置的。
应理解，以上列举的RNAU的类型仅为示例性说明，本申请并未限定于此，其他能够对RNAU进行分类的方法或方式均落入本申请的保护范围内。
作为示例而非限定，本申请的RNAU可以包括以下过程。
1，UE可以从inactive状态恢复，向新接入gNB提供由最后服务gNB分配的I-RNTI和适当的原因值，例如RAN通知区域更新。
2，如果能够解析I-RNTI中包含的gNB身份，则新接入gNB请求最后服务gNB提供UE上下文。
3，最后服务gNB提供UE上下文。
4，新接入gNB可以将UE切到RRC_CONNECTED状态，或者将UE切回RRC_INACTIVE状态或者将UE切到RRC_IDLE状态。需要说明的是，如果UE被切到RRC_IDLE，则不需要执行后续步骤。
5，如果要防止在最后服务gNB中缓冲的下行用户数据的丢失，则新接入gNB给最后服务gNB提供下行数据转发地址。
6，新接入gNB执行路径切换(向服务AMF发路径切换请求消息)。
7，AMF回复路径切换响应消息。
8，AMF通知最后服务gNB释放UE上下文。
图5示出了本申请的无线通信的方法200的一例的示意性流程图，并且，该方法200示出了接入设备#A和接入设备#B之间的交互过程。
作为示例而非限定，该方法200可以应用于以下任意一种场景：
场景1，终端设备#A从该接入设备#A切换至接入设备#B。
场景2，接入设备#A可以为主基站，接入设备#B可以为辅基站，终端设备#A的驻留基站从其他基站(例如，接入设备#A或接入设备#A的其他辅基站)变更为接入设备#B。
场景3，接入设备#A可以是终端设备#A的原驻留基站，接入设备#A可以是终端设备#A的新驻留基站。
作为示例而非限定，在终端设备#A驻留在接入设备#A期间，终端设备#A可能进入inactive状态。并且，在本申请中，终端设备#A进入inactive状态的次数可以为一次也可以为N次，N为大于1的整数。
以下，为了理解和说明，以终端设备#A在驻留在接入设备#A期间，第i次进入inactive状态的处理过程为例，对该方法200的处理过程进行说明，其中，i是大于或等于1的整数，且i是小于或等于N的整数。
假设终端设备#A在时刻#A第i次进入inactive状态。
其中，该第i次inactive状态的类型可以是以上类型1至类型3中的任意一种类型，本申请并未特别限定。
并且，假设终端设备#A在时刻#B结束该第i次inactive状态。
其中，触发终端设备结束该第i次inactive状态的事件可以是以上事件1至事件3中的任意一种事件，本申请并未特别限定。
则，在S210，接入设备#A可以确定该终端设备#A的第i次inactive状态的时长(记做，时长#A)，即，该时长#A可以是该时刻#A至时刻#B之间经历的时长。
作为示例而非限定，在本申请中，接入设备#A可以采用以下任意一种方式，确定时长#A。
方式1
例如，在本申请中，如果接入设备#A能够获知终端设备#A在时刻#A第i次进入inactive状态，则该接入设备#A可以记录该时刻#A，并且，如果接入设备#A能够获知终端设备#A在时刻#B结束该第i次inactive状态，则该接入设备#A可以记录该时刻#B，从而，接入设备#A可以根据该时刻#A和时刻#B确定该时长#A。
方式2
再例如，在本申请中，终端设备#A可以向接入设备#A上报该时刻#A的信息和时刻#B的信息，从而接入设备#A可以确定该时刻#A和时刻#B，进而根据该时刻#A和时刻#B确定该时长#A。需要说明的是，该时刻#A的信息可以是终端设备#A在进入inactive状态之后立即发送，也可以是终端设备#A在进入inactive状态之后经历任意时长后发送，本申请并未特别限定，类似的，该时刻#B的信息可以是终端设备#A在结束inactive状态之后立即发送，也可以是终端设备#A在结束inactive状态之后经历任意时长后发送，本申请并未特别限定。
可选的，终端设备#A可以通过其他接入设备向接入设备#A上报该时刻#A和该时刻#B，例如当终端设备#A在接入设备#A内进入inactive状态后，记录时刻#A，移动至其他接入设备，那么当UE在其他接入设备内结束了inactive状态，那么UE会记录时刻#B，此时该时刻#A和该时刻#B可以先上报给其他接入设备，然后其他接入设备再发送至接入设备#A。
方式3
再例如，在本申请中，终端设备#A在进入inactive之后，可以在时刻#C向接入设备#A上报inactive状态开始指示，并且，终端设备#A在结束inactive之后，可以在时刻#D向接入设备#A上报inactive状态结束指示。其中，该时刻#C与该时刻#A之间具有预设的时间间隔#1，该时刻#D与该时刻#B之间具有预设的时间间隔#2，从而，接入设备#A可以基于该时刻#C和时间间隔#1推算出时刻#A，并且，基于该时刻#D和时间间隔#2推算出时刻#B，从而接入设备#A可以确定改改时刻#A和时刻#B，进而根据该时刻#A和时刻#B确定该时长#A。其中，该时间间隔#1和时间间隔#2可以是通信系统或通信协议规定的时间间隔，也可是接入设备#1配置的时间间隔，本申请并未特别限定。
可选的，终端设备#A可以通过其他接入设备向接入设备#A上报该时刻A和该时刻B。具体同前文描述，这里不再赘述。
方式4
再例如，在本申请中，终端设备#A可以根据该时刻#A和时刻#B确定该时长#A，并向接入设备#A发送该时长#A的信息，从而，接入设备#A可以基于该时长#A的信息，确定该时长#A。
可选的，终端设备#A可以通过其他接入设备向接入设备#A上报该时长#A的信息。
如上所述，本申请的接入设备(或者说，RAN设备)可以包括CU和DU，并且，CU可以包括CU-CP和CU-UP，
即，该接入设备#A可以包括CU，或者，该接入设备#A可以包括CU-CP(即，情况#2)下面，分别对上述2种情况下，接入设备#A确定该时长#A的方案。
情况1
例如，接入设备#C(即，DU)可以(例如，基于上述方式1至方式3中的任意一种方式)记录该时刻#A和时刻#B，并向接入设备#A发送该时刻#A的信息以及时刻#B的信息，从而，接入设备#A可以根据该时刻#A和时刻#B确定该时长#A。可选的，该时刻#B的信息可以是其他接入设备#C或者是其他接入设备#A记录并发送给接入设备#A的。
再例如，接入设备#C(即，DU)可以(例如，基于上述方式1至方式4中的任意一种方式)确定该时长#A，并向接入设备#A发送该时长#A的信息，从而，接入设备#A可以根据该时长#A的信息确定该时长#A。可选的，该时长#A的信息可以是其他接入设备#C或者是其他接入设备#A记录并发送给接入设备#A的。
并且，在情况1下，上述该时刻#A的信息、时刻#B的信息或时长#A的信息可以承载于CU和DU之间的接口消息中，例如，F1接口消息(例如，F1接口去激活通知消息)。
另外，可选地，接入设备#A还可以向接入设备#C发送监控请求#1，该监控请求#1可以用于指示接入设备#C监控终端设备#A进入去激活状态和结束去激活状态的时刻，或者说，该监控请求#1可以用于指示接入设备#C记录终端设备#A处于去激活状态的时长，从而，接入设备#C可以根据该监控请求#1发送该时刻#A的信息、时刻#B的信息或时长#A的信息。
情况2
例如，接入设备#D(即，CU-UP)可以(例如，基于上述方式1至方式3中的任意一种方式)记录该时刻#A和时刻#B，并向接入设备#A发送该时刻#A的信息以及时刻#B的信息，从而，接入设备#A可以根据该时刻#A和时刻#B确定该时长#A。可选的，该时刻#B的信息可以是其他接入设备#C或者是其他接入设备#A记录并发送给接入设备#A的。
再例如，接入设备#D(即，CU-UP)可以(例如，基于上述方式1至方式4中的任意一种方式)确定该时长#A，并向接入设备#A发送该时长#A的信息，从而，接入设备#A可以根据该时长#A的信息确定该时长#A。可选的，该时长#A的信息可以是其他接入设备#C或者是其他接入设备#A记录并发送给接入设备#A的。
并且，在情况2下，上述该时刻#A的信息、时刻#B的信息或时长#A的信息可以承载于CU-UP和CU-CP之间的接口消息中，例如，E1接口消息(例如，E1接口去激活通知消息)。
另外，可选地，接入设备#A还可以向接入设备#D发送监控请求#2，该监控请求#2可以用于指示接入设备#D监控终端设备#A进入去激活状态和结束去激活状态的时刻，或者说，该监控请求#2可以用于指示接入设备#C记录终端设备#A处于去激活状态的时长，从而，接入设备#D可以根据该监控请求#2发送该时刻#A的信息、时刻#B的信息或时长#A的信息。
可选地，该接入设备#A还可以确定该第i次inactive状态的类型(即，上述类型1至 类型3中的任意一种类型)。
例如，在上述情况1或情况2下，该监控请求#1或监控请求#2中还可以携带类型指示信息#1，该类型指示信息#1可以用于指示需要DU监控的去激活状态的类型(即，上述类型1至类型3中的任意一种类型)。
再例如，在基于上述方式2至方式4中的任意一种方式确定时长#A的情况下，接入设备#A可以向终端设备#A发送类型指示信息#2，该类型指示信息#2可以用于指示需要终端设备#A监控的去激活状态的类型(即，上述类型1至类型3中的任意一种类型)。
可选地，接入设备还可以确定小区#A，该小区#A是该终端设备#A第i次进入inactive状态时所处于(例如，驻留)的小区。并且，接入设备#A还可以记录该时长#A与小区#A的对应关系。
例如，在上述情况1或情况2下，该监控请求#1或监控请求#2中还可以携带小区上报请求信息#1，该小区上报请求信息#1可以用于请求DU监控并上报终端设备#A进入inactive状态时所处于(例如，驻留)的小区。
或者，DU也可以主动上报终端设备#A进入inactive状态时所处于(例如，驻留)的小区。
再例如，在基于上述方式2至方式4中的任意一种方式确定时长#A的情况下，接入设备#A可以向终端设备#A发送小区上报请求信息#2，该小区上报请求信息#2可以用于请求接入设备#A监控并上报inactive状态时所处于(例如，驻留)的小区。
可选地，接入设备还可以确定类型#A，该类型#A是该第i次进入inactive状态的类型。并且，接入设备#A还可以记录该时长#A与类型#A的对应关系。
可选地，接入设备#A可以将该时长#A的信息记录在终端设备#A的用户历史信息(UE history information)中，或者也可以记录在一个新的信元中，本申请在此不限定。
作为示例而非限定，本申请的用户历史信息可以包括以下形式的信息：
信息单元(information element，IE)/组(group)名称(name)
最后驻留小区列表(last visited cell list)
>最后驻留小区信息(last visited cell information)
>>终端设备处于去激活状态的最后驻留小区信息(last vsited cell information that UE served in inactive state)
>>>小区全球标识符(E-UTRAN cell global identifier，ECGI)
>>>时长(time spent)
具体地说，该ECGI可以是终端设备处于去激活状态时所处于的小区(例如，上述小区#A)的ECGI，可选的，该信元也可以是PCI(例如，上述小区#A)。该信元可选。
该时长是指终端设备处于去激活状态的时长(例如，上述时长#A)。
应理解，以上列举的用户历史信息的具体形式仅为示例性说明，本申请并未限定于此。
例如，该用户历史信息还可以包括时长对应的去激活状态的类型(例如，上述类型#A)。
再例如，该用户历史信息中可以记录在一个小区内多次去激活状态对应的时长，或者记录在不同的小区内多次去激活状态对应的时长。此时，时长信元可能是以一个列表的形式存在，具体本申请在此不限定。
在S230，接入设备#A可以向接入设备#B发送该时长#A的信息。
可选地，接入设备#A还可以向接入设备#B发送小区#A的信息。
或者说，接入设备#A还可以向接入设备#B发送时长#A与小区#A的对应关系的信息。
可选地，接入设备#A还可以向接入设备#B发送类型#A的信息。
或者说，接入设备#A还可以向接入设备#B发送该时长#A对应的inactive状态(即，该第i次inactive状态)的类型(即，类型#A)的信息。
例如，作为示例而非限定，上述信息可以携带于终端设备#A的历史信息中。
可选地，该时长#A的信息可以是接入设备#A基于接入设备#B的请求发送的，即，在S220，接入设备#B可以向接入设备#A发送时长请求信息，该时长请求信息可以用于请求接入设备#A发送终端设备#A处于去激活状态的时长(具体地说，该时长请求信息可以用于请求接入设备#A发送终端设备#A处于一次去激活状态的时长)。
可选地，该时长请求信息还可以包括类型请求信息，该类型请求信息可以用于指示接入设备#B希望接入设备#A提供时长对应的去激活状态类型，或者说，该类型请求信息可以用于指示接入设备#B希望接入设备#A提供何种去激活类型的时长。
即，上述类型#A可以是接入设备#A根据类型请求信息确定的，或者，该类型#A可以是该类型请求信息指示的类型。
作为示例而非限定，例如，在上述场景1的情况下，该时长请求信息可以携带于上下文请求消息中，并且，该时长#A的信息可以携带于上下文请求响应消息或其他Xn接口消息中。另外，该上下文请求信息可以是接入设备#B根据接入设备#A发送的无线资源控制(radio resource control，RRC)恢复请求消息(RRC resume request)发送的。
再例如，在上述场景2的情况下，该时长#A的信息可以携带辅基站变更请求消息或其他EUTRA和NR的双链接(E-UTRA-NR Dual Connectivity，EN-DC)Xn接口消息中。
再例如，在本申请中，接入设备#A和接入设备#B之间可以通过核心网设备传输数据或信息，例如，接入设备#A可以将该时长#A的信息发送给核心网设备，并且，核心网设备可以将时长#A的信息转发给接入设备#B。
由此，在S240，接入设备#B(即，终端设备#A新驻留的接入设备)可以获取时长#A的信息，从而，可以根据该时长#A配置针对inactive状态的定时器(timer)。
例如，作为示例而非限定，设接入设备#B配置的原始的针对inactive状态的定时器的时长为时长#B。
则该接入设备#B可以根据该时长#A来调节该时长#B。
例如，如果时长#A大于时长#B，则接入设备#B可以调节定时器，以使该时长#B延长。
再例如，如果时长#A小于时长#B，则接入设备#B可以调节定时器，以使该时长#B缩短。
再例如，接入设备#B可以调节定时器，以使该时长#B与时长#A之间的差值在预设的差异范围内。
再例如，接入设备#B还可以确定时长#A对应的inactive状态(即，类型#A)，并将该类型#A的inactive状态的定时器的时长，确定为配置对象(即，时长#B)。
根据本申请提供的无线通信的方法，通过使终端设备#A的源驻留接入设备#A记录终端设备#A处于inactive状态的时长#A，并使接入设备#A将该时长#A的信息发送给终端 设备#A的新驻留接入设备#B，从而，接入设备#B可以基于该时长#A配置针对inactive状态的timer，即，根据本申请提供的无线通信方法，能够为timer设置提供参考和依据，从而，能够避免因timer设置不合理而导致的信令开销即设备功耗的增大，能够降低信令开销和终端设备的功耗进，进而改善用户体验。
应理解，以上列举的时长#A的使用方法仅为示例性说明，本申请并未限定于此。
例如，接入设备还可以在时刻#C(位于时刻#B之后的时刻)，为终端设备#A重新配置inactive状态的定时器的时长(记做，时长#C)。
例如，如果时长#A大于时长#C，则接入设备#A可以调节定时器，以使该时长#C延长。
再例如，如果时长#A小于时长#C，则接入设备#A可以调节定时器，以使该时长#C缩短。
再例如，接入设备#A可以调节定时器，以使该时长#C与时长#A之间的差值在预设的差异范围内。
再例如，接入设备#A还可以确定时长#A对应的inactive状态(即，类型#A)，并将该类型#A的inactive状态的定时器的时长，确定为配置对象(即，时长#C)。
需要说明的是，如上所述终端设备#A在移动至接入设备#B的覆盖范围内之前，或者说，终端设备#A在接入设备#A的覆盖范围内移动时，可能多次处于inactive状态，因此，接入设备#A可以记录该多次inactive状态中每次inactive状态的时长，并且，该时长的确定、记录、传输和使用的过程可以与该终端设备#A第i次处于inactive状态的时长(即，时长#A)相似，这里为了避免省略其详细说明。
即，该终端设备#A的历史信息可以包括时长列表，该时长列表可以包括终端设备#A的多次inactive状态的时长的信息。
图6示出了本申请的无线通信的方法300的一例的示意性流程图，并且，该方法300示出了接入设备#1和接入设备#2之间的交互过程。
作为示例而非限定，该方法300可以应用于以下至少一种场景：
场景1，终端设备#1从该接入设备#1切换至接入设备#2。
场景2，接入设备#1可以为主基站，接入设备#2可以为辅基站，终端设备#1的驻留基站从其他基站(例如，接入设备#1或接入设备#1的其他辅基站)变更为接入设备#2。
场景3，接入设备#1可以是终端设备#1的原驻留基站，接入设备#1可以是终端设备#1的新驻留基站。
作为示例而非限定，在终端设备#1在移动的过程中，终端设备#1可能发生RNAU。并且，在本申请中，终端设备#1发生RNAU的次数可以为一次也可以为M次，M为大于1的整数。
以下，为了理解和说明，以终端设备#1在移动的过程中，第j次发生RNAU的处理过程为例，对该方法300的处理过程进行说明，其中，j是大于或等于1的整数，且j是小于或等于M的整数。
其中，该第j次RNAU的类型可以是以上类型α至类型β中的任意一种类型，本申请并未特别限定。
则，在S310，接入设备#1可以确定该终端设备#1该第j次发生RNAU时所处于的小 区(记做：小区#1)。
作为示例而非限定，在本申请中，接入设备#1可以采用以下任意一种方式，确定小区#1。
方式1
例如，在本申请中，接入设备#1可以自行记录该终端设备#1该第j次发生RNAU时所处于的小区。
方式2
再例如，在本申请中，终端设备#1在发生该第j次发生RNAU时，可以向接入设备#1上报该小区#1的信息。
从而，接入设备#1可以记录该小区#1的信息。
作为示例而非限定，该小区#1的信息可以包括但不限于小区#1的物理小区标识PCI(physical cell Identifier，PCI)或小区全球标识(Cell Global Identifier，CGI)等。
可选地，接入设备#1还可以确定类型#1，该类型#1是该终端设备#1该第j次发生的RNAU的类型。并且，接入设备#1还可以记录该小区#1与类型#1的对应关系。
可选地，接入设备#1可以将上述信息记录在终端设备#1的用户历史信息(UE history information)中，或者在一个新定义的信元中，本申请在此不限定。
作为示例而非限定，本申请的用户历史信息可以包括以下形式的信息：
IE/Group Name
最后驻留小区列表(last visited cell list)
>最后驻留小区信息(last visited cell information)
>>终端设备发生RNAU的最后驻留小区信息(last vsited cell information that UE has RNAU)
>>>小区全球标识符(E-UTRAN cell global identifier，ECGI)
>>>RNAU类型(RNAU type)
具体地说，该ECGI可以是终端设备发生RNAU时所处于的小区(例如，上述小区#1)的ECGI。或者，也可以是小区的PCI。
应理解，以上列举的用户历史信息的具体形式仅为示例性说明，本申请并未限定于此。
例如，该用户历史信息中可以记录多次RNAU对应的小区的信息。
在S330，接入设备#1可以向接入设备#2发送该小区#1的信息。
可选地，接入设备#1还可以向接入设备#2发送类型#1的信息。
或者说，接入设备#1还可以向接入设备#2发送小区#1与类型#1的对应关系的信息。
例如，作为示例而非限定，上述信息可以携带于终端设备#1的历史信息中。
可选地，该小区#1的信息可以是接入设备#1基于接入设备#2的请求发送的，即，在S320，接入设备#2可以向接入设备#1发送小区请求信息，该小区请求信息可以用于请求接入设备#1告知终端设备#1发生RNAU是所处于的小区。
可选地，该小区请求信息还可以包括类型请求信息，该类型请求信息可以用于指示接入设备#2希望接入设备#1提供小区对应的RNAU类型，或者说，该类型请求信息可以用于指示接入设备#2希望接入设备#1提供发生何种RNAU类型时所处于的小区。
即，上述类型#1可以是接入设备#1根据类型请求信息确定的，或者，该类型#1可以 是该类型请求信息指示的类型。
作为示例而非限定，例如，在上述场景1的情况下，该小区请求信息可以携带于上下文请求消息中，并且，该小区#1的信息可以携带于上下文请求响应消息或其他Xn接口消息中。另外，该上下文请求信息可以是接入设备#2根据接入设备#1发送的无线资源控制(radio resource control，RRC)恢复请求消息(RRC resume request)发送的。
再例如，在上述场景2的情况下，该小区#1的信息可以携带辅基站变更请求消息或其他EN-DC Xn接口消息中。
再例如，在本申请中，接入设备#1和接入设备#2之间可以通过核心网设备传输数据或信息，例如，接入设备#1可以将该小区#1的信息发送给核心网设备，并且，核心网设备可以将小区#1的信息转发给接入设备#2。
由此，在S340，接入设备#2(即，终端设备#1新驻留的接入设备)可以获取小区#1的信息，从而，可以根据该小区#1为终端设备#1配置RNA。
例如，作为示例而非限定，设接入设备#2为终端设备#1配置的RNA包括的小区为小区集合#X。
则该接入设备#2可以根据该小区#1来调整小区集合#X，或者说，调整小区集合#X包括的小区。
例如，如果小区#1不属于该小区集合#X，则接入设备#2可以将该小区#1添加至该小区集合#X。
根据本申请提供的无线通信的方法，通过使终端设备#1的源驻留接入设备#1记录终端设备#1发生RNAU时处于的小区#1，并使接入设备#1将该小区#1的信息发送给终端设备#1的新驻留接入设备#2，从而，接入设备#2可以基于该小区#1为终端设备#1配置RNA，即，根据本申请提供的无线通信方法，能够为RNA设置提供参考和依据，从而，能够避免因RNA设置不合理而导致的信令开销即设备功耗的增大，能够降低信令开销和终端设备的功耗进，进而改善用户体验。
应理解，以上列举的小区#1的使用方法仅为示例性说明，本申请并未限定于此。
例如，接入设备#1还可以在时刻#2(位于时刻#1之后的时刻，该时刻#1是第j次发生RNAU的时刻)，为终端设备#A重新配置RNA，设该重新配置的RNA包括的小区为小区集合#Y。
例如，如果小区#1不属于该小区集合#Y，则接入设备#1可以将该小区#1添加至该小区集合#Y。
需要说明的是，如上所述终端设备#1在移动至接入设备#2的覆盖范围内之前，可能多次发生RNAU，因此，接入设备#A可以记录该多次RNAU中每次RNAU的小区，并且，该小区的信息的确定、记录、传输和使用的过程可以与该终端设备#1第j次RNAU的小区相似，这里为了避免省略其详细说明。
即，该终端设备#1的历史信息可以包括发生RNAU的小区列表，该小区列表可以包括终端设备#1的多次RNAU的小区的信息、RNAU的类型中的至少一个。
图7示出了本申请的无线通信的方法400的一例的示意性流程图，并且，该方法400示出了终端设备#x和接入设备#y之间的交互过程。
作为示例而非限定，该方法400可以应用于以下至少一种场景：
场景1，终端设备#x从该接入设备#x切换至接入设备#y。
场景2，接入设备#x可以为主基站，接入设备#y可以为辅基站，终端设备#x的驻留基站从其他基站(例如，接入设备#x或接入设备#x的其他辅基站)变更为接入设备#y。
场景3，接入设备#x可以是终端设备#x的原驻留基站，接入设备#y可以是终端设备#x的新驻留基站。
作为示例而非限定，在终端设备#x驻留在接入设备#x期间，终端设备#x可能进入inactive状态。并且，在本申请中，终端设备#x进入inactive状态的次数可以为一次也可以为K次，K为大于1的整数。
以下，为了理解和说明，以终端设备#x在驻留在接入设备#x期间，第k次进入inactive状态的处理过程为例，对该方法400的处理过程进行说明，其中，k是大于或等于1的整数，且k是小于或等于K的整数。
假设终端设备#x在时刻#x第k次进入inactive状态。
其中，该第k次inactive状态的类型可以是以上类型1至类型3中的任意一种类型，本申请并未特别限定。
并且，假设终端设备#x在时刻y结束该第k次inactive状态。
其中，触发终端设备结束该第k次inactive状态的事件可以是以上事件1至事件7中的任意一种事件，本申请并未特别限定。
则，在S410，终端设备#x可以记录该终端设备#x的第k次inactive状态的时长(记做，时长#x)，即，该时长#x可以是该时刻#x至时刻#y之间经历的时长。
可选地，终端设备#x还可以确定类型#x，该类型#x是该第k次进入inactive状态的类型。并且，终端设备#x还可以记录该时长#x与类型#x的对应关系。
可选地，该终端设备#x还可以记录小区#k，该小区#k是该终端设备第k次处于入inactive状态所处于过的小区，其中，该小区#k可以是一个也可以是多个，本申请并未特别限定。
可选地，终端设备#x可以将该时长#x的信息记录在终端设备#x的用户历史信息(UE history information)中，或者可以记录在一个新的信元中，本申请在此不限定。
作为示例而非限定，本申请的用户历史信息可以包括以下形式的信息：
IE/Group Name
最后驻留小区列表(last visited cell list)
>最后驻留小区信息(last visited cell information)
>>终端设备处于去激活状态的最后驻留小区信息(last vsited cell information that UE served in inactive state)
>>>小区全球标识符(E-UTRAN cell global identifier，ECGI)
>>>时长(time spent)
具体地说，该ECGI可以是终端设备处于去激活状态时所处于的小区(例如，上述小区#k)的ECGI。或者，也可以是小区的PCI。该信元可选。
该时长是指终端设备处于去激活状态的时长(例如，上述时长#k)。
应理解，以上列举的用户历史信息的具体形式仅为示例性说明，本申请并未限定于此。
例如，该用户历史信息还可以包括时长对应的去激活状态的类型(例如，上述类型#k)。
再例如，该用户历史信息中可以记录多次去激活状态对应的时长。
在S430，终端设备#x可以向接入设备#y(或接入设备#x)发送该时长#k的信息。
可选地，终端设备#x还可以向接入设备#y(或接入设备#x)发送小区#k的信息。
或者说，终端设备#x还可以向接入设备#y(或接入设备#x)发送时长#k与小区#k的对应关系的信息。
可选地，接入设备#y(或接入设备#x)还可以向终端设备#x发送类型#k的信息。
或者说，接入设备#y(或接入设备#x)还可以向终端设备#x发送该时长#k对应的inactive状态(即，该第k次inactive状态)的类型(即，类型#k)的信息。
例如，作为示例而非限定，上述信息可以携带于终端设备#A的历史信息中。
可选地，该时长#k的信息可以是终端设备#x基于接入设备#y(或接入设备#x)的请求发送的，即，在S420，接入设备#y(或接入设备#x)可以向终端设备#x发送时长请求信息，该时长请求信息可以用于请求终端设备#x发送终端设备#x处于去激活状态的时长(具体地说，该时长请求信息可以用于请求终端设备#x发送终端设备#x处于一次去激活状态的时长)。
可选地，该时长请求信息还可以包括类型请求信息，该类型请求信息可以用于指示接入设备#y(或接入设备#x)希望终端设备#x提供时长对应的去激活状态类型，或者说，该类型请求信息可以用于指示接入设备#y(或接入设备#x)希望终端设备#x提供何种去激活类型的时长。
即，上述类型#k可以是终端设备#x根据类型请求信息确定的，或者，该类型#k可以是该类型请求信息指示的类型。
由此，在S440，接入设备#y(或接入设备#x)可以获取时长#x的信息，从而，可以根据该时长#k为终端设备#x配置针对inactive状态的定时器(timer)。
例如，作为示例而非限定，设接入设备#y(或接入设备#x)为终端设备#x配置的原始的针对inactive状态的定时器的时长为时长#y。
则该接入设备#y(或接入设备#x)可以根据该时长#x来调节该时长#y。
例如，如果时长#x大于时长#y，则接入设备#y(或接入设备#x)可以调节定时器，以使该时长#y延长。
再例如，如果时长#x小于时长#y，则接入设备#y(或接入设备#x)可以调节定时器，以使该时长#y缩短。
再例如，接入设备#y(或接入设备#x)可以调节定时器，以使该时长#y与时长#x之间的差值在预设的差异范围内。
再例如，接入设备#y(或接入设备#x)还可以确定时长#x对应的inactive状态(即，类型#x)，并将该类型#x的inactive状态的定时器的时长，确定为配置对象(即，时长#y)。
需要说明的是，如上所述终端设备#x在移动至接入设备#y的覆盖范围内之前，或者说，终端设备#x在接入设备#x的覆盖范围内移动时，可能多次处于inactive状态，因此，接入设备#x可以记录该多次inactive状态中每次inactive状态的时长，并且，该时长的确定、记录、传输和使用的过程可以与该终端设备#x第k次处于inactive状态的时长(即，时长#A)相似，这里为了避免省略其详细说明。
即，该终端设备#x的历史信息可以包括时长列表，该时长列表可以包括终端设备#x 的多次inactive状态的时长的信息。
根据本申请提供的无线通信的方法，通过使终端设备记录处于inactive状态的时长，并使接入设备基于该时长为终端设备配置针对inactive状态的timer，即，根据本申请提供的无线通信方法，能够为timer设置提供参考和依据，从而，能够避免因timer设置不合理而导致的信令开销即设备功耗的增大，能够降低信令开销和终端设备的功耗进，进而改善用户体验。
图8示出了本申请的无线通信的方法500的一例的示意性流程图，并且，该方法500示出了终端设备#z和接入设备#w(或接入设备#z)之间的交互过程。
作为示例而非限定，该方法500可以应用于以下至少一种场景：
场景1，终端设备#z从该接入设备#z切换至接入设备#w。
场景2，接入设备#z可以为主基站，接入设备#w可以为辅基站，终端设备#z的驻留基站从其他基站(例如，接入设备#z或接入设备#z的其他辅基站)变更为接入设备#w。
场景3，接入设备#z可以是终端设备#z的原驻留基站，接入设备#z可以是终端设备#z的新驻留基站。
作为示例而非限定，在终端设备#z驻留在接入设备#z期间，终端设备#z可能发生RNAU。并且，在本申请中，终端设备#z发生RNAU的次数可以为一次也可以为P次，P为大于1的整数。
以下，为了理解和说明，以终端设备#z在驻留在接入设备#z期间，第p次发生RNAU的处理过程为例，对该方法300的处理过程进行说明，其中，p是大于或等于1的整数，且p是小于或等于P的整数。
其中，该第p次RNAU的类型可以是以上类型α至类型β中的任意一种类型，本申请并未特别限定。
则，在S510，终端设备#z可以确定该第p次发生RNAU时所处于的小区(记做：小区#z)。
作为示例而非限定，该小区#z的信息可以包括但不限于小区#z的PCI或CGI等
可选地，终端设备#z还可以确定类型#z，该类型#z是该终端设备#z该第p次发生的RNAU的类型。并且，终端设备#z还可以记录该小区#z与类型#z的对应关系。
可选地，终端设备#z可以将上述信息记录在终端设备#z的用户历史信息(UE history information)中。
作为示例而非限定，本申请的用户历史信息可以包括以下形式的信息：
IE/Group Name
最后驻留小区列表(last visited cell list)
>最后驻留小区信息(last visited cell information)
>终端设备发生RNAU的最后驻留小区信息(last vsited cell information that UE has RNAU)
>>小区全球标识符(E-UTRAN cell global identifier，ECGI)
>>RNAU类型(RNAU type)
具体地说，该ECGI可以是终端设备发生RNAU时所处于的小区(例如，上述小区#z)的ECGI。或者，也可以是小区的PCI。
应理解，以上列举的用户历史信息的具体形式仅为示例性说明，本申请并未限定于此。
例如，该用户历史信息中可以记录多次RNAU对应的小区的信息。
在S530，终端设备#z可以向接入设备#w(或者，接入设备#z)发送该小区#z的信息。
可选地，终端设备#z还可以向接入设备#w(或者，接入设备#z)发送类型#z的信息。
或者说，终端设备#z还可以向接入设备#w(或者，接入设备#z)发送小区#z与类型#z的对应关系的信息。
例如，作为示例而非限定，上述信息可以携带于终端设备#z的历史信息中。
可选地，该小区#z的信息可以是终端设备#z基于接入设备#w(或者，接入设备#z)的请求发送的，即，在S520，接入设备#w(或者，接入设备#z)可以向终端设备#z发送小区请求信息，该小区请求信息可以用于请求终端设备#z告知发生RNAU是所处于的小区。
可选地，该小区请求信息还可以包括类型请求信息，该类型请求信息可以用于指示接入设备#w(或者，接入设备#z)希望终端设备#z提供小区对应的RNAU类型，或者说，该类型请求信息可以用于指示接入设备#w(或者，接入设备#z)希望终端设备#z提供发生何种RNAU类型时所处于的小区。
即，上述类型#z可以是终端设备#z根据类型请求信息确定的，或者，该类型#z可以是该类型请求信息指示的类型。
由此，在S540，接入设备#w(或者，接入设备#z)可以获取小区#z的信息，从而，可以根据该小区#z为终端设备#z配置RNA。
例如，作为示例而非限定，设接入设备#w(或者，接入设备#z)为终端设备#z配置的RNA包括的小区为小区集合#X。
则该接入设备#w(或者，接入设备#z)可以根据该小区#z来调整小区集合#X，或者说，调整小区集合#X包括的小区。
例如，如果小区#z不属于该小区集合#X，则接入设备#w(或者，接入设备#z)可以将该小区#z添加至该小区集合#X。
需要说明的是，如上所述终端设备#z在移动至接入设备#w的覆盖范围内之前，可能多次发生RNAU，因此，接入设备#z可以记录该多次RNAU中每次RNAU的小区，并且，该小区的信息的确定、记录、传输和使用的过程可以与该终端设备#z第p次RNAU的小区相似，这里为了避免省略其详细说明。
即，该终端设备#z的历史信息可以包括发生RNAU的小区列表，该小区列表可以包括终端设备#z的多次RNAU的小区的信息、RNAU的类型中的至少一个。
根据本申请提供的无线通信的方法，通过使终端设备记录发生RNAU时处于的小区，将该小区的信息发送给接入设备，从而，接入设备可以基于该小区为终端设备配置RNA，即，根据本申请提供的无线通信方法，能够为RNA设置提供参考和依据，从而，能够避免因RNA设置不合理而导致的信令开销即设备功耗的增大，能够降低信令开销和终端设备的功耗进，进而改善用户体验。
可以理解的是，本申请上述各个实施例中，由终端设备实现的方法也可以由可用于终端设备的部件(例如芯片或者电路)实现，由接入设备实现的方法也可以由可用于接入设备的部件(例如芯片或者电路)实现。
根据前述方法，图9为本申请实施例提供的无线通信的装置600的示意图。
其中，该装置600可以为终端设备，也可以为芯片或电路，比如可设置于终端设备的芯片或电路。
或者，该装置600可以为接入设备，也可以为芯片或电路，比如可设置于接入设备的芯片或电路。该装置600可以包括处理单元610(即，处理单元的一例)和存储单元620。该存储单元620用于存储指令。
该处理单元610用于执行该存储单元620存储的指令，以使装置600实现如上述方法中终端设备，(例如，终端设备#x或终端设备#z)执行的步骤。
或者，该处理单元610用于执行该存储单元620存储的指令，以使装置600实现如上述方法中接入设备(例如，接入设备#A或接入设备#1)执行的步骤。
进一步的，该装置600还可以包括输入口630(即，通信单元的一例)和输出口640(即，通信单元的另一例)。进一步的，该处理单元610、存储单元620、输入口630和输出口640可以通过内部连接通路互相通信，传递控制和/或数据信号。该存储单元620用于存储计算机程序，该处理单元610可以用于从该存储单元620中调用并运行该计算计程序，以控制输入口630接收信号，控制输出口640发送信号，完成上述方法中终端设备的步骤。该存储单元620可以集成在处理单元610中，也可以与处理单元610分开设置。
可选地，若该装置600为通信设备(例如，网络设备或终端设备)，该输入口630为接收器，该输出口640为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该装置600为芯片或电路，该输入口630为输入接口，该输出口640为输出接口。
作为一种实现方式，输入口630和输出口640的功能可以考虑通过收发电路或者收发的专用芯片实现。处理单元610可以考虑通过专用处理芯片、处理电路、处理单元或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的通信设备(例如，接入设备或终端设备)。即将实现处理单元610、输入口630和输出口640功能的程序代码存储在存储单元620中，通用处理单元通过执行存储单元620中的代码来实现处理单元610、输入口630和输出口640的功能。
在一种实现方式中，处理单元610用于确定参考信息，所述参考信息包括第一时长的信息和/或第一小区的信息，所述第一时长包括终端设备处于去激活状态的时长，所述第一小区包括所述终端设备发生基于无线接入网的通知区域更新RNAU的小区；
该输出口640用于发送所述参考信息。
可选地，所述参考信息还包括所述第一时长对应的第二小区的信息，所述第二小区包括所述终端设备在第一时长对应的去激活状态下所处于的小区。
可选地，所述参考信息还包括所述第一时长对应的去激活状态类型的信息，其中，所述去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型。
可选地，所述参考信息还包括所述第一小区对应的RNAU类型的信息，所述RNAU类型包括周期性触发RNAU类型或终端设备移动触发RNAU类型。
可选地，处理单元610用于将所述参考信息记录在所述终端设备的历史信息中。
可选地，该输入口630用于接收请求信息，并用于根据所述请求信息，发送所述参考信息。
可选地，所述请求信息包括类型指示信息，所类型指示信息用于指示第一去激活状态类型，其中，所述第一去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型，以及
处理单元610用于根据所述类型指示信息确定所述第一时长的信息，以使所述第一时长对应的去激活状态类型为所述第一去激活状态类型。
其中，以上列举的装置600中各模块或单元的功能和动作仅为示例性说明，当该装置600配置在或本身即为终端设备时，装置600中各模块或单元可以用于执行上述方法中终端设备(例如，终端设备#x或终端设备#z)所执行的各动作或处理过程；当该装置600配置在或本身即为接入络设备时，装置600中各模块或单元可以用于执行上述方法中接入设备(例如，接入设备#A或接入设备#1)所执行的各动作或处理过程这里，为了避免赘述，省略其详细说明。
该装置600所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
根据前述方法，图10为本申请实施例提供的无线通信的装置700的示意图。
其中，该装置700可以为接入设备(例如，接入设备#B、接入设备#2、接入设备#y或接入设备#w)，也可以为芯片或电路，比如可设置于接入设备的芯片或电路。
该装置700可以包括处理单元710(即，处理单元的一例)和存储单元720。该存储单元720用于存储指令。
该处理单元710用于执行该存储单元720存储的指令，以使装置700实现如上述方法中接入设备(例如，接入设备#B、接入设备#2、接入设备#y或接入设备#w)执行的步骤。
进一步的，该装置700还可以包括输入口730(即，通信单元的一例)和输出口740(即，通信单元的另一例)。进一步的，该处理单元710、存储单元720、输入口730和输出口740可以通过内部连接通路互相通信，传递控制和/或数据信号。该存储单元720用于存储计算机程序，该处理单元710可以用于从该存储单元720中调用并运行该计算计程序，以控制输入口730接收信号，控制输出口740发送信号，完成上述方法中终端设备的步骤。该存储单元720可以集成在处理单元710中，也可以与处理单元710分开设置。
可选地，若该装置700为通信设备(例如，接入设备)，该输入口730为接收器，该输出口740为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该装置700为芯片或电路，该输入口730为输入接口，该输出口740为输出接口。
作为一种实现方式，输入口730和输出口740的功能可以考虑通过收发电路或者收发的专用芯片实现。处理单元710可以考虑通过专用处理芯片、处理电路、处理单元或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的通信设备(例如，接入设备)。即将实现处理单元710、输入口730和输出口740功能的程 序代码存储在存储单元720中，通用处理单元通过执行存储单元720中的代码来实现处理单元710、输入口730和输出口740的功能。
在一种实现方式中，输入口730用于接收参考信息，所述参考信息包括第一时长的信息和/或第一小区的信息，所述第一时长包括终端设备处于去激活状态的时长，所述第一小区包括所述终端设备发生基于无线接入网的通知区域更新RNAU的小区。
处理单元710用于根据所述第一时长，调节所述终端设备的去激活状态定时器的时长；或者
处理单元710用于根据所述第一小区，为所述终端设备配置基于无线接入网的通知区域RNA。
可选地，所述参考信息还包括所述第一时长对应的第二小区的信息，所述第二小区包括所述终端设备在第一时长对应的去激活状态下所处于的小区。
可选地，所述参考信息还包括所述第一时长对应的去激活状态类型的信息，其中，所述去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型，以及
处理单元710用于根据所述第一时长，调节所述终端设备所述第一时长对应的去激活状态类型的去激活状态定时器的时长。
可选地，所述参考信息还包括所述第一小区对应的RNAU类型的信息，所述RNAU类型包括周期性触发RNAU类型或终端设备移动触发RNAU类型。
可选地，所述参考信息携带于所述终端设备的历史信息中。
可选地，输出口740用于发送请求信息，所述请求信息用于请求所述参考信息。
可选地，所述请求信息包括类型指示信息，所类型指示信息用于指示第一去激活状态类型，其中，所述第一去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型。
其中，以上列举的装置700中各模块或单元的功能和动作仅为示例性说明，当该装置700配置在或本身即为接入设备时，装置700中各模块或单元可以用于执行上述方法中接入设备(例如，接入设备#B、接入设备#2、接入设备#y或接入设备#w)所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
该装置700所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
图11为本申请提供的一种终端设备800的结构示意图。上述装置600可以配置在该终端设备800中，或者，上述装置600本身可以即为该终端设备800。或者说，该终端设备800可以执行上述方法200、300、400或500中终端设备执行的动作。
为了便于说明，图11仅示出了终端设备的主要部件。如图11所示，终端设备800包括处理器、存储器、控制电路、天线以及输入输出装置。
处理器主要用于对通信协议以及通信数据进行处理，以及对整个终端设备进行控制，执行软件程序，处理软件程序的数据，例如用于支持终端设备执行上述传输预编码矩阵的指示方法实施例中所描述的动作。存储器主要用于存储软件程序和数据，例如存储上述实施例中所描述的码本。控制电路主要用于基带信号与射频信号的转换以及对射频信号的处理。控制电路和天线一起也可以叫做收发器，主要用于收发电磁波形式的射频信号。输入 输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。
当终端设备开机后，处理器可以读取存储单元中的软件程序，解释并执行软件程序的指令，处理软件程序的数据。当需要通过无线发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。
本领域技术人员可以理解，为了便于说明，图11仅示出了一个存储器和处理器。在实际的终端设备中，可以存在多个处理器和存储器。存储器也可以称为存储介质或者存储设备等，本申请实施例对此不做限制。
例如，处理器可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端设备进行控制，执行软件程序，处理软件程序的数据。图11中的处理器集成了基带处理器和中央处理器的功能，本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独立的处理器，通过总线等技术互联。本领域技术人员可以理解，终端设备可以包括多个基带处理器以适应不同的网络制式，终端设备可以包括多个中央处理器以增强其处理能力，终端设备的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储单元中，由处理器执行软件程序以实现基带处理功能。
示例性的，在本申请实施例中，可以将具有收发功能的天线和控制电路视为终端设备800的收发单元810，将具有处理功能的处理器视为终端设备800的处理单元820。如图11所示，终端设备800包括收发单元810和处理单元820。收发单元也可以称为收发器、收发机、收发装置等。可选的，可以将收发单元810中用于实现接收功能的器件视为接收单元，将收发单元810中用于实现发送功能的器件视为发送单元，即收发单元包括接收单元和发送单元。示例性的，接收单元也可以称为接收机、接收器、接收电路等，发送单元可以称为发射机、发射器或者发射电路等。
图12为本申请实施例提供的一种接入设备900的结构示意图，可以用于实现上述方法中的接入设备(例如，接入设备#A、接入设备#B、接入设备#1、接入设备#2、接入设备#x、接入设备#y、接入设备#z或接入设备#w)的功能。接入设备900包括一个或多个射频单元，如远端射频单元(remote radio unit,RRU)910和一个或多个基带单元(baseband unit，BBU)(也可称为数字单元，digital unit，DU)920。所述RRU910可以称为收发单元、收发机、收发电路、或者收发器等等，其可以包括至少一个天线911和射频单元912。所述RRU910部分主要用于射频信号的收发以及射频信号与基带信号的转换，例如用于向终端设备发送上述实施例中所述的信令消息。所述BBU920部分主要用于进行基带处理，对基站进行控制等。所述RRU910与BBU920可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。
所述BBU920为基站的控制中心，也可以称为处理单元，主要用于完成基带处理功能， 如信道编码，复用，调制，扩频等等。例如该BBU(处理单元)920可以用于控制基站40执行上述方法实施例中关于网络设备的操作流程。
在一个示例中，所述BBU920可以由一个或多个单板构成，多个单板可以共同支持单一接入制式的无线接入网(如LTE系统，或5G系统)，也可以分别支持不同接入制式的无线接入网。所述BBU920还包括存储器921和处理器922。所述存储器921用以存储必要的指令和数据。例如存储器921存储上述实施例中的码本等。所述处理器922用于控制基站进行必要的动作，例如用于控制基站执行上述方法实施例中关于网络设备的操作流程。所述存储器921和处理器922可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
在一种可能的实施方式中，随着片上系统(system-on-chip，SoC)技术的发展，可以将920部分和910部分的全部或者部分功能由SoC技术实现，例如由一颗基站功能芯片实现，该基站功能芯片集成了处理器、存储器、天线接口等器件，基站相关功能的程序存储在存储器中，由处理器执行程序以实现基站的相关功能。可选的，该基站功能芯片也能够读取该芯片外部的存储器以实现基站的相关功能。
应理解，图12示例的网络设备的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的基站结构的可能。
根据本申请实施例提供的方法，本申请实施例还提供一种通信系统，其包括前述的接入设备和一个或多于一个终端设备。
应理解，本申请实施例中，该处理器可以为中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机 程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (26)

  1. 一种无线通信的方法，其特征在于，包括：
    确定参考信息，所述参考信息包括第一时长的信息和/或第一小区的信息，所述第一时长包括终端设备处于去激活状态的时长，所述第一小区包括所述终端设备发生基于无线接入网的通知区域更新RNAU的小区；
    发送所述参考信息。
  2. 根据权利要求1所述的方法，其特征在于，所述参考信息还包括所述第一时长对应的第二小区的信息，所述第二小区包括所述终端设备在第一时长对应的去激活状态下所处于的小区。
  3. 根据权利要求1或2所述的方法，其特征在于，所述参考信息还包括所述第一时长对应的去激活状态类型的信息，其中，所述去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述参考信息还包括所述第一小区对应的RNAU类型的信息，所述RNAU类型包括周期性触发RNAU类型或终端设备移动触发RNAU类型。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    将所述参考信息记录在所述终端设备的历史信息中。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    接收请求信息；以及
    所述发送所述参考信息，包括：
    根据所述请求信息，发送所述参考信息。
  7. 根据权利要求6所述的方法，其特征在于，所述请求信息包括类型指示信息，所类型指示信息用于指示第一去激活状态类型，其中，所述第一去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型，以及
    所述确定参考信息包括：
    根据所述类型指示信息确定所述第一时长的信息，以使所述第一时长对应的去激活状态类型为所述第一去激活状态类型。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，当所述方法的由第一接入设备执行时，所述方法还包括：
    接收第三接入设备发送的第一指示信息，所述第一指示信息用于指示所述第一时长；或者
    接收第三接入设备发送的第二指示信息，所述第二指示信息用于指示所述终端设备进入去激活状态的时刻以及所述终端设备结束区激活状态的时刻；
    其中，所述第一接入设备包括集中式单元CU，所述第三接入设备包括分布式单元DU，或者
    所述第一接入设备包括集中式单元控制面CU-CP实体，所述第三接入设备包括集中式单元用户面CU-UP实体；
    其中，所述CU中配置有分组数据汇聚层协议PDCP层或无线资源控制RRC层中的至少一个协议层；
    所述DU中配置有无线链路控制RLC层、媒体接入控制MAC层或物理PHY层中的至少一个协议层。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，当所述方法由第一接入设备执行，且所述参考信息包括第一时长的信息时，
    所述发送所述参考信息，包括：
    向第二接入设备发送所述参考信息，其中
    所述第一接入设备包括DU，所述第二接入设备包括CU，或者
    所述第一接入设备包括CU-UP实体，所述第二接入设备包括CU-CP实体；
    其中，所述CU中配置有PDCP层或RRC层中的至少一个协议层；
    所述DU中配置有RLC层、MAC层或PHY层中的至少一个协议层。
  10. 一种无线通信的方法，其特征在于，包括：
    接收参考信息，所述参考信息包括第一时长的信息和/或第一小区的信息，所述第一时长包括终端设备处于去激活状态的时长，所述第一小区包括所述终端设备发生基于无线接入网的通知区域更新RNAU的小区；
    根据所述第一时长，调节所述终端设备的去激活状态定时器的时长；或者
    根据所述第一小区，为所述终端设备配置基于无线接入网的通知区域RNA。
  11. 根据权利要求10所述的方法，其特征在于，所述参考信息还包括所述第一时长对应的第二小区的信息，所述第二小区包括所述终端设备在第一时长对应的去激活状态下所处于的小区。
  12. 根据权利要求10或11所述的方法，其特征在于，所述参考信息还包括所述第一时长对应的去激活状态类型的信息，其中，所述去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型，以及
    根据所述第一时长，调节所述终端设备的去激活状态定时器的时长，包括：
    根据所述第一时长，调节所述终端设备所述第一时长对应的去激活状态类型的去激活状态定时器的时长。
  13. 根据权利要求10至12中任一项所述的方法，其特征在于，所述参考信息还包括所述第一小区对应的RNAU类型的信息，所述RNAU类型包括周期性触发RNAU类型或终端设备移动触发RNAU类型。
  14. 根据权利要求10至13中任一项所述的方法，其特征在于，所述参考信息携带于所述终端设备的历史信息中。
  15. 根据权利要求10至14中任一项所述的方法，其特征在于，所述方法还包括：
    发送请求信息，所述请求信息用于请求所述参考信息。
  16. 根据权利要求15所述的方法，其特征在于，所述请求信息包括类型指示信息，所类型指示信息用于指示第一去激活状态类型，其中，所述第一去激活状态类型包括会话去激活状态类型、数据无线承载去激活状态类型或终端设备去激活状态类型。
  17. 根据权利要求10至16中任一项所述的方法，其特征在于，所述方法由第二接入设备执行，以及
    所述接收参考信息，包括：
    接收第一接入设备发送的第一时长的信息，
    其中，所述第一接入设备包括分布式单元DU，所述第二接入设备包括集中式单元CU，或者
    所述第一接入设备包括集中式单元用户面CU-UP实体，所述第二接入设备包括集中式单元控制面CU-CP实体；
    其中，所述CU中配置有分组数据汇聚层协议PDCP层或无线资源控制RRC层中的至少一个协议层；
    所述DU中配置有无线链路控制RLC层、媒体接入控制MAC层或物理PHY层中的至少一个协议层。
  18. 一种无线通信的装置，其特征在于，包括：
    用于执行权利要求1至9中任一项所述的方法的单元；或者
    用于执行权利要求10至17中任一项所述的方法的单元。
  19. 一种通信设备，其特征在于，包括：通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求1至9中任一项所述的方法中，在所述通信设备侧进行信息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求1至9中任一项所述的方法中，在所述通信设备进行的信息处理或控制操作。
  20. 根据权利要求19所述的通信设备，其特征在于，所述通信设备为接入网设备。
  21. 一种通信设备，其特征在于，包括通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求10至17中任一项所述的方法中，在所述通信设备侧进行信息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求10至17中任一项所述的方法中，在所述通信设备侧进行的信息处理或控制操作。
  22. 根据权利要求21所述的通信设备，其特征在于，所述通信设备为接入网设备。
  23. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器，和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求1至9任一项所述的方法，或者，权利要求10至17中任一项所述的方法。
  24. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行权利要求1至9中任一项所述的方法，或者，权利要求10至17中任一项所述的方法。
  25. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1至9中项任一项所述的方法，或者如权利要求10至17中项任一项所述的方法。
  26. 一种通信系统，其特征在于，包括如权利要求19或20所述的通信设备，和/或，如权利要求21或22所述的通信设备。
PCT/CN2019/128923 2018-12-29 2019-12-27 无线通信的方法和装置 Ceased WO2020135645A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
BR112021012796A BR112021012796A2 (pt) 2018-12-29 2019-12-27 Método e aparelho de comunicação sem fio
EP19902336.7A EP3890405A4 (en) 2018-12-29 2019-12-27 WIRELESS COMMUNICATION METHOD AND APPARATUS
US17/362,909 US12089151B2 (en) 2018-12-29 2021-06-29 Wireless communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811633343.6 2018-12-29
CN201811633343.6A CN111385857B (zh) 2018-12-29 2018-12-29 无线通信的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/362,909 Continuation US12089151B2 (en) 2018-12-29 2021-06-29 Wireless communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2020135645A1 true WO2020135645A1 (zh) 2020-07-02

Family

ID=71126889

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/128923 Ceased WO2020135645A1 (zh) 2018-12-29 2019-12-27 无线通信的方法和装置

Country Status (5)

Country Link
US (1) US12089151B2 (zh)
EP (1) EP3890405A4 (zh)
CN (1) CN111385857B (zh)
BR (1) BR112021012796A2 (zh)
WO (1) WO2020135645A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111385857B (zh) * 2018-12-29 2022-12-02 华为技术有限公司 无线通信的方法和装置
WO2021168714A1 (zh) * 2020-02-26 2021-09-02 华为技术有限公司 一种发现应用的方法、装置及系统
US20230354461A1 (en) * 2020-05-26 2023-11-02 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for controlling connection state of terminal device
CN114189921B (zh) * 2020-09-14 2025-02-14 中兴通讯股份有限公司 小区变更的控制方法及装置、存储介质、电子装置
CN112203333B (zh) * 2020-10-22 2023-06-27 Oppo广东移动通信有限公司 连接释放方法、装置、电子设备及存储介质
CN113766488B (zh) * 2021-09-16 2025-01-24 维沃移动通信有限公司 数据传输方法和电子设备
CN117015013A (zh) * 2022-04-29 2023-11-07 大唐移动通信设备有限公司 信号发送方法、通信装置、信号发送装置和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080089290A1 (en) * 2006-10-16 2008-04-17 Motorola, Inc. Method and apparatus for management of inactive connections for service continuity in an agnostic access Internet protocol multimedia communication
CN105228229A (zh) * 2014-06-27 2016-01-06 中兴通讯股份有限公司 用户设备ue资源处理方法、装置、基站及终端
CN108616999A (zh) * 2017-01-04 2018-10-02 电信科学技术研究院 一种数据传输方法、装置及系统
CN108811020A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 一种通信方法及设备

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2621234A1 (en) * 2012-01-30 2013-07-31 Alcatel Lucent Providing information on a mobile terminal to a radio resource management entity of a wireless communication network
CN104412699A (zh) * 2012-07-06 2015-03-11 日本电气株式会社 确定定时器的期满时段的方法、网络节点、和非瞬时计算机可读介质
WO2014054237A1 (ja) * 2012-10-04 2014-04-10 日本電気株式会社 無線アクセスネットワーク装置、コアネットワーク装置、移動端末、並びにこれらの方法及びコンピュータ可読媒体
KR102276839B1 (ko) * 2017-03-17 2021-07-14 삼성전자주식회사 라디오 액세스 네트워크 통지 영역 업데이트 실패
KR102310719B1 (ko) * 2017-03-20 2021-10-08 삼성전자 주식회사 차세대 이동통신에서 대기 모드 동작을 효과적으로 하는 방법 및 장치
CN113163459B (zh) * 2017-04-04 2024-04-09 华为技术有限公司 通信方法及通信设备
CN110167110B (zh) * 2018-02-13 2021-05-18 华为技术有限公司 通信方法和装置
CN110636565B (zh) * 2018-06-21 2021-01-22 电信科学技术研究院有限公司 Rrc非活跃状态下的数据传输方法、装置、终端及设备
WO2020033780A1 (en) * 2018-08-08 2020-02-13 Google Llc Public land mobile network selection by user equipment in an inactive mode at a radio resource control layer
CN111385857B (zh) * 2018-12-29 2022-12-02 华为技术有限公司 无线通信的方法和装置
EP3888411B1 (en) * 2019-01-14 2024-11-13 Nokia Technologies Oy Transmitting data from a user equipment in radio resource control inactive state
ES3041571T3 (en) * 2020-02-20 2025-11-13 Huawei Tech Co Ltd Communication method, device, and system
CN114531720A (zh) * 2020-11-23 2022-05-24 华为技术有限公司 用于终端扫描的方法、系统、装置、电子设备及存储介质
KR20220101874A (ko) * 2021-01-12 2022-07-19 주식회사 아이티엘 무선 통신 시스템에서 drx 동작 방법 및 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080089290A1 (en) * 2006-10-16 2008-04-17 Motorola, Inc. Method and apparatus for management of inactive connections for service continuity in an agnostic access Internet protocol multimedia communication
CN105228229A (zh) * 2014-06-27 2016-01-06 中兴通讯股份有限公司 用户设备ue资源处理方法、装置、基站及终端
CN108616999A (zh) * 2017-01-04 2018-10-02 电信科学技术研究院 一种数据传输方法、装置及系统
CN108811020A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 一种通信方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3890405A4

Also Published As

Publication number Publication date
CN111385857A (zh) 2020-07-07
EP3890405A4 (en) 2022-03-09
EP3890405A1 (en) 2021-10-06
US12089151B2 (en) 2024-09-10
CN111385857B (zh) 2022-12-02
BR112021012796A2 (pt) 2021-11-23
US20210329548A1 (en) 2021-10-21

Similar Documents

Publication Publication Date Title
JP7279773B2 (ja) 無線端末及びその方法
CN111385857B (zh) 无线通信的方法和装置
US20230117911A1 (en) Condition-based secondary node or primary secondary cell change method and device
US12414077B2 (en) Paging message detection method, apparatus, and communication device
EP3629626B1 (en) Communication method and apparatus
US20220369184A1 (en) Cell handover method, terminal device, and network device
US20230086410A1 (en) Communication method and communication apparatus
WO2021051287A1 (zh) 无线通信方法和装置
CN113271685B (zh) 一种添加辅小区组的方法、接入网设备和终端设备
US20210051575A1 (en) System information updating method, terminal device, and network device
WO2025168095A1 (zh) 候选主小区配置信息的处理方法、设备、存储介质及产品
WO2021062770A1 (zh) 无线通信的方法和装置
WO2021062730A1 (zh) 无线通信方法和装置
CN116669119A (zh) 用于小区切换的方法和装置
WO2022198569A1 (zh) 测量配置方法、终端设备、网络设备、芯片和存储介质
EP4044684B1 (en) Communication method and apparatus
WO2020061994A1 (zh) 一种信息传输方法及装置、网络设备
US12425946B2 (en) Terminal device and network device
CN113271583B (zh) 一种多卡终端设备的通信参数测量方法、终端设备和接入网设备
CN114424637B (zh) 寻呼的方法和装置
WO2023065156A1 (zh) 无线通信的方法、终端设备和网络设备
WO2020200038A1 (zh) 准入控制的方法和装置
CN115835397B (zh) 用于无线通信的方法及装置
CN110351744A (zh) 通信方法、网络设备和通信设备

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: 19902336

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112021012796

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2019902336

Country of ref document: EP

Effective date: 20210630

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112021012796

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112021012796

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20210628