WO2022073395A1 - 一种通信方法及设备 - Google Patents

一种通信方法及设备 Download PDF

Info

Publication number
WO2022073395A1
WO2022073395A1 PCT/CN2021/114558 CN2021114558W WO2022073395A1 WO 2022073395 A1 WO2022073395 A1 WO 2022073395A1 CN 2021114558 W CN2021114558 W CN 2021114558W WO 2022073395 A1 WO2022073395 A1 WO 2022073395A1
Authority
WO
WIPO (PCT)
Prior art keywords
cycle
network device
message
terminal device
period
Prior art date
Application number
PCT/CN2021/114558
Other languages
English (en)
French (fr)
Inventor
孔繁华
邝奕如
徐海博
薛丽霞
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21876915.6A priority Critical patent/EP4210429A4/en
Priority to US18/248,109 priority patent/US20230403757A1/en
Publication of WO2022073395A1 publication Critical patent/WO2022073395A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • 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 present application relates to the field of communication technologies, and in particular, to a communication method and device.
  • the discontinuous reception (DRX) mechanism enables the user equipment (UE) to sleep most of the time by receiving signals discontinuously to save power. Because packet-based data streams are generally bursty, when there is no data transmission, power consumption can be reduced by turning off the UE's receiving circuit.
  • Extended discontinuous reception (eDRX) is an extended DRX. In each eDRX cycle, the UE can only receive downlink data in the set paging time window (PTW), and the rest of the time outside the PTW time, the UE is in a dormant state.
  • UEs with enhanced machine type communication can use the eDRX mechanism when they are in the inactive state of radio resource control (RRC), while other UEs, such as long-term An evolution (long term evolution, LTE) UE or a new radio (new radio, NR) UE, etc., cannot use the eDRX mechanism when the RRC is in an inactive state.
  • RRC radio resource control
  • UEs with enhanced machine type communication eMTC
  • LTE long-term evolution
  • NR new radio
  • redcap UE is a type of UE with lower capability compared to a legacy UE.
  • the redcap UE belongs to the NR UE, but in order to save energy for the redcap UE, it is currently discussed that the redcap UE can also use the eDRX mechanism when the RRC is inactive.
  • the currently specified maximum eDRX cycle length that can be supported is 10.24 seconds (s). If the redcap UE also uses the eDRX mechanism when the RRC is inactive, the maximum eDRX cycle length that the redcap UE can support may be greater than 10.24s. However, if the eDRX period configured by the base station for the redcap UE to be used in the RRC inactive state is too long, if the core network device sends a non-access stratum (NAS) message to the redcap UE, the redcap UE may fail due to eDRX The cycle is too long and cannot be received, which is a problem that needs to be solved at present.
  • NAS non-access stratum
  • Embodiments of the present application provide a communication method and device, which are used to improve the probability that a UE successfully receives a NAS message.
  • a first aspect provides a communication method, the method comprising: when a first terminal device is in an RRC idle state, if a core network device obtains downlink data of the first terminal device, sending the core network device to The access network device sends a paging message, where the paging message is used to page the first terminal device, and the paging message further includes the eDRX cycle used by the first terminal device when it is in the RRC idle state;
  • the access network device receives the paging message, and determines a first cycle according to the eDRX cycle used by the first terminal device in the RRC idle state carried in the paging message, where the first cycle is expected
  • the eDRX cycle configured for the first terminal device, and the first cycle is used by the first terminal device when it is in the RRC inactive state; the access network device sends the first terminal device the eDRX cycle.
  • the first terminal device receives the paging message, and establishes an RRC connection with the access network device based on the paging message; after the RRC connection is successfully established, the access network
  • the device sends an initial UE message to the core network device, where the initial UE message includes the first cycle; the core network device determines a second cycle according to the first cycle and the NAS timing information, and the second cycle is The core network device is the eDRX cycle determined by the first terminal device, and the second cycle is used by the first terminal device when the RRC is in the inactive state; the core network device reports to the The access network device sends an initial context establishment request message, where the initial context establishment request message includes the second period; when the access network device does not detect the data transmission of the UE, the access network device starts the RRC connection release timing when the RRC connection release timer expires, the access network device sends an RRC connection release message to the first terminal device, and the RRC connection release message includes the second period; in the first terminal device When the terminal device
  • the access network device and the core network device can negotiate to determine the second cycle, where the second cycle is an eDRX cycle that can be configured for the first terminal device to use in the RRC inactive state.
  • the second cycle is an eDRX cycle that can be configured for the first terminal device to use in the RRC inactive state.
  • a reasonable eDRX cycle can be given based on the conditions of the access network device and the core network device, so that if the core network device wants to send a NAS message to the first terminal device, it can send it according to the second cycle, so that , no matter whether the second period is less than or equal to 10.24s or greater than 10.24s, the first terminal device can normally receive the NAS message from the core network device according to the second period, which improves the probability of the terminal device receiving the NAS message and reduces the The packet loss rate of the NAS message also reduces the transmission delay of the NAS message accordingly.
  • a second communication method is provided, and the method can be executed by an access network device, or executed by a chip system, and the chip system can realize the functions of the access network device.
  • the access network device is a base station.
  • the method includes: an access network device sends a first message to a core network device, the first message includes a first cycle, the first cycle is an eDRX cycle expected to be configured for the first terminal device, and the first cycle is used by the first terminal device in the RRC inactive state; the access network device receives a second message from the core network device, the second message includes a second period, the second period is the eDRX cycle determined by the core network device for the first terminal device, and the second cycle is used by the first terminal device in the RRC inactive state, and the length of the second cycle Same as or different from the first period.
  • the access network device and the core network device can negotiate to determine the second cycle, where the second cycle is an eDRX cycle that can be configured for the first terminal device to use in the RRC inactive state.
  • the second cycle is an eDRX cycle that can be configured for the first terminal device to use in the RRC inactive state.
  • a reasonable eDRX cycle can be given based on the conditions of the access network device and the core network device, so that if the core network device wants to send a NAS message to the first terminal device, it can send it according to the second cycle, so that , no matter whether the second period is less than or equal to 10.24s or greater than 10.24s, the first terminal device can normally receive the NAS message from the core network device according to the second period, which improves the probability of the terminal device receiving the NAS message and reduces the The packet loss rate of the NAS message also reduces the transmission delay of the NAS message accordingly.
  • the length of the second period when the length of the first period is less than or equal to the first threshold, the length of the second period is the same as the length of the first period.
  • the lengths of the periods are the same; or, where the length of the first period is greater than the first threshold, the length of the second period is less than the length of the first period, and the length of the second period is less than or equal to the first threshold; wherein, the first threshold is determined according to the NAS timing information.
  • the first threshold is determined according to unadjusted NAS timing information, or is determined according to adjusted NAS timing information.
  • the core network device can increase the time length that the core network device can accept, so that the time length of the eDRX cycle configured for the UE is longer and the configuration is more flexible. It can be considered that the first threshold is the length of time acceptable to the core network device, and if the first threshold exceeds the first threshold, the core network device cannot accept it. Therefore, according to the first threshold and the first period, the length of the second period can be determined, so that the length of the second period can be within the acceptance range of the core network device.
  • the NAS timing information includes a minimum retransmission time interval of the NAS message, and/or, the NAS message The maximum number of retransmissions.
  • the NAS timing information includes the minimum retransmission interval of the NAS message, or the NAS timing information includes the maximum number of retransmissions of the NAS message, or the NAS timing information includes the minimum retransmission interval of the NAS message and the maximum retransmission of the NAS message. frequency.
  • the first The message is the initial UE message.
  • the access network device may send the first cycle to the core network device through the initial UE message, for example, adding an IE in the initial UE message, and the first cycle may be carried by the newly added IE.
  • the first cycle is sent to the access network device through the existing message, and no additional message is needed, which can save signaling overhead.
  • the access network device may also send the first cycle to the core network device through other messages.
  • the second message is an initial context establishment request message.
  • the core network device may also send the second cycle to the access network device through an existing message, for example, the second cycle may be sent to the access network device through an initial context establishment request message.
  • the initial context establishment request message may include UE Radio Capability for Paging IE, and may also include UE radio paging information in UE Radio Capability for Paging IE.
  • Some blank fields are included in the UE radio paging information, and the second period is carried, for example, by one or more blank fields included in the UE radio paging information, so that the blank fields can be reasonably utilized.
  • the method further includes: receiving, by the access network device, first information from the core network device, where the first information includes the information used by the first terminal device when in the RRC idle state. eDRX cycle; the access network device determines the first cycle according to the eDRX cycle used by the first terminal device in the RRC idle state.
  • the core network device may send the eDRX cycle used by the first terminal device in the RRC idle state to the access network device, so that the access network device may determine the first cycle according to the eDRX cycle.
  • the first information is included in the paging message.
  • the core network device may send the first information to the access network device through a paging message, where the paging message is a core network paging message, for example, the paging message is used to page the first terminal device.
  • the paging message is a core network paging message, for example, the paging message is used to page the first terminal device.
  • the method further includes: the access network device sending the third message to the first terminal device, where the third message includes the second period.
  • the second cycle may be configured to the first terminal device, so that the first terminal device can use the second cycle after entering the RRC inactive state.
  • the access network device sends the second period to the first terminal device, including :
  • the third message is an RRC connection release message, and the RRC connection release message is used to release the first terminal device to the RRC inactive state.
  • the RRC connection release message is used to release the first terminal device to the RRC inactive state, and the second cycle is also used by the first terminal device in the RRC inactive state, so the second cycle is sent to the first terminal device through the RRC connection release message.
  • a terminal device can enable the second cycle to be applied in a timely manner.
  • the RRC connection release message can not only release the first terminal device to the RRC inactive state, but also configure a second period for the first terminal device, which improves the utilization rate of the message, and because there is no need to send an additional message for the first terminal device The device configures the second cycle, which also reduces the transmission overhead.
  • the first terminal device is a redcap UE.
  • the first terminal device may be any terminal device served by the access network device, for example, the first terminal device is a redcap UE.
  • the first terminal device is a redcap UE.
  • the technical solutions of the embodiments of the present application can also be applied. That is, through the technical solutions of the embodiments of the present application, suitable eDRX cycles can be configured for different redcap UEs respectively, so that the configured eDRX not only meets the requirements of the terminal equipment for receiving NAS messages, but also more closely meets the actual service requirements of the terminal equipment.
  • a third communication method is provided.
  • the method can be performed by core network equipment, or performed by a chip system, and the chip system can realize the functions of the core network equipment.
  • the core network device is an AMF.
  • the method includes: a core network device receives a first message from an access network device, the first message includes a first cycle, and the first cycle is an eDRX cycle that the access network device expects to configure for the first terminal device , and the first period is used when the first terminal device is in the RRC inactive state; the core network device sends a second message to the access network device, and the second message includes the second period , the first cycle is the eDRX cycle that the access network device expects to configure for the first terminal device, and the first cycle is used when the first terminal device is in the RRC inactive state, wherein the The second period is determined according to the first period and the NAS timing information, and the length of the second period is the same as or different from that of the first period.
  • the second period is determined according to the first period and NAS timing information, including: when the length of the first period is less than or equal to the first threshold, the length of the second period is the same as the length of the first period; or, when the length of the first period is greater than the first threshold, the length of the second period is The length is less than the length of the first period, and the length of the second period is less than or equal to the first threshold; wherein the first threshold is determined according to the NAS timing information.
  • the NAS timing information includes a minimum retransmission time interval of the NAS message, and/or, the NAS message The maximum number of retransmissions.
  • the first The message is the initial UE message.
  • the fourth optional embodiment of the third aspect can be In an optional implementation manner, the second message is an initial context establishment request message.
  • the method further Including: the core network device sends first information to the access network device, where the first information is used to determine the first period, wherein the first information includes that the first terminal device is in an RRC eDRX cycle used in idle state.
  • the first information is included in the paging message.
  • the method further includes: the core network device receives an RRC inactive state transition report from the access network device, where the RRC inactive state transition report is used to indicate the first terminal device Entering the RRC inactive state; the core network device sends a NAS message to the first terminal device according to the second period.
  • the first terminal device is a redcap UE.
  • a fourth communication method is provided, and the method can be executed by the first terminal device, or executed by a chip system, and the chip system can realize the function of the first terminal device.
  • the method includes: a first terminal device receiving a third message from an access network device, the third message including a second cycle, the second cycle being an eDRX cycle configured for the first terminal device, and the The second period is used when the first terminal device is in the RRC inactive state, wherein the second period is determined through negotiation between the access network device and the core network device; in the first When the terminal device is in the RRC inactive state, the first terminal device monitors the paging according to the second period.
  • the second message is an RRC connection release message
  • the RRC connection release message is used to release the first terminal device to the RRC inactive state.
  • the first terminal device is a redcap UE.
  • a fifth aspect provides a fifth communication method, the method comprising: a core network device determining a first cycle according to NAS timing information, where the first cycle is a maximum eDRX cycle that can be configured for a first terminal device, and the first cycle The period is used when the first terminal device is in the RRC inactive state; during the registration process of the first terminal device, the core network device sends an initial context establishment request message to the access network device, and the initial context establishment request message including the context information of the first terminal device, and the initial context request message further includes the first period; the access network device receives the initial context establishment request message, and according to the initial context establishment request message The carried first cycle determines a second cycle, where the second cycle is the eDRX cycle configured for the first terminal device, and the second cycle is when the first terminal device is in the RRC inactive state used, the length of the second period is less than or equal to the length of the first period; the access network device sends an initial context establishment response message to the core network device, and the initial context establishment response message includes the The
  • the core network device first notifies the access network device of the upper limit value acceptable to the core network device, so that the access network device configures the first terminal device with the eDRX cycle used in the RRC inactive state
  • the time can be more accurate, and the process of re-determining the eDRX cycle configured for the first terminal device by the access network device is reduced.
  • the access network device will also notify the core network device of the second cycle that is finally determined, so that if the core network device wants to send the NAS message to the first terminal device, it can send it according to the second cycle, so that the first terminal device can send the NAS message according to the second cycle.
  • the NAS message from the core network device can be normally received, no matter whether the second period is greater than 10.24s or less than 10.24s, the method of the embodiment of the present application can improve the probability of the terminal device receiving the NAS message and reduce the packet loss of the NAS message Rate.
  • the core network device does not need to page the first terminal device because the NAS message fails to be sent, and the first terminal device does not need to enter the RRC idle state and then initiate random access, which reduces service transmission delay and saves transmission resources.
  • the core network device may consider the NAS timing information as a factor when determining the first cycle, without considering the eDRX cycle used by the first terminal device in the RRC idle state. It is more flexible, the determined first period can be made longer, and it also meets the requirements of core network equipment.
  • a sixth communication method is provided, and the method can be executed by an access network device, or executed by a chip system, and the chip system can realize the functions of the access network device.
  • the access network device is a base station.
  • the method includes: the access network device receives a first message from the core network device, the first message includes a first cycle, the first cycle is a maximum eDRX cycle that can be configured for the first terminal device, and the first cycle A cycle is used when the first terminal device is in the RRC inactive state; the access network device determines a second cycle according to the first cycle, and the second cycle is configured for the first terminal device eDRX cycle, and the second cycle is used when the first terminal equipment is in the RRC inactive state, and the length of the second cycle is less than or equal to the length of the first cycle; the access network The device sends a second message to the core network device, where the second message includes the second period.
  • the core network device first notifies the access network device of the upper limit value acceptable to the core network device, so that the access network device configures the first terminal device with the eDRX cycle used in the RRC inactive state
  • the time can be more accurate, and the process of re-determining the eDRX cycle configured for the first terminal device by the access network device is reduced.
  • the access network device will also notify the core network device of the second cycle that is finally determined, so that if the core network device wants to send the NAS message to the first terminal device, it can send it according to the second cycle, so that the first terminal device can send the NAS message according to the second cycle.
  • the NAS message from the core network device can be normally received, no matter whether the second period is greater than 10.24s or less than 10.24s, the method of the embodiment of the present application can improve the probability of the terminal device receiving the NAS message and reduce the packet loss of the NAS message Rate.
  • the core network device does not need to page the first terminal device because the NAS message fails to be sent, and the first terminal device does not need to enter the RRC idle state and then initiate random access, which reduces service transmission delay and saves transmission resources.
  • the core network device may consider the NAS timing information as a factor when determining the first cycle, without considering the eDRX cycle used by the first terminal device in the RRC idle state. It is more flexible, the determined first period can be made longer, and it also meets the requirements of core network equipment.
  • the first message is an initial context establishment request message; and/or,
  • the second message is an initial context establishment response message, or the second message is an RRC inactive state transition report.
  • the core network device sends the first cycle to the access network device, and the access network device sends the second cycle to the core network device, both of which can be sent through existing messages, without adding other messages, so that the technical solutions of the embodiments of the present application can be more Compatible well with existing technologies.
  • the first period or the second period may also be sent through other messages, for example, may be sent through a newly added dedicated message, so as to reduce the impact on the function of the existing message.
  • the method further includes: the access network device reporting to the first The terminal device sends a third message, and the third message includes the second period.
  • the second cycle may be configured to the first terminal device, so that the first terminal device can use the second cycle after entering the RRC inactive state.
  • the third message is an RRC connection release message, and the RRC connection release message is used to The first terminal device is released to the RRC inactive state.
  • the RRC connection release message is used to release the first terminal device to the RRC inactive state, and the second cycle is also used by the first terminal device in the RRC inactive state, so the second cycle is sent to the first terminal device through the RRC connection release message.
  • a terminal device can enable the second cycle to be applied in a timely manner.
  • the RRC connection release message can not only release the first terminal device to the RRC inactive state, but also configure a second period for the first terminal device, which improves the utilization rate of the message, and because there is no need to send an additional message for the first terminal device The device configures the second cycle, which also reduces the transmission overhead.
  • the fourth optional embodiment of the second aspect can be In an optional embodiment, the access network device has different lengths of eDRX cycles configured for different terminal devices when the access network device is in the RRC inactive state according to the first cycle.
  • the access network device may determine the second cycle according to the first cycle and the capability of the first UE, so that the second cycle can conform to the capability of the first UE; or, the access network device may determine the second cycle according to the first cycle and the capability of the first UE.
  • the service requirements determine the second period, so that the second period can meet the service requirements of the first UE; or, the access network device may determine the second period according to the first period, the capabilities of the first UE, and the service requirements of the first UE, etc. etc., the factors used by the access network device to determine the second period are not limited.
  • the access network device can configure the eDRX cycle for the UE according to the actual situation of the UE (such as service requirements or capabilities, etc.), the eDRX cycle used in the RRC inactive state determined by the access network device for different UEs may be the same , may also be different.
  • the first terminal device is a redcap UE.
  • the first terminal device may be any terminal device served by the access network device, for example, the first terminal device is a redcap UE.
  • the first terminal device is a redcap UE.
  • the technical solutions of the embodiments of the present application can also be applied. That is, through the technical solutions of the embodiments of the present application, suitable eDRX cycles can be configured for different redcap UEs, respectively, so that the configured eDRX not only meets the needs of the terminal equipment for receiving NAS messages, but also meets the actual service requirements of the terminal equipment.
  • a seventh communication method is provided, and the method can be executed by a core network device, or executed by a chip system, and the chip system can realize the functions of the core network device.
  • the core network device is an AMF.
  • the method includes: the core network device sends a first message to the access network device, the first message includes a first cycle, the first cycle is a maximum eDRX cycle that can be configured for the first terminal device, and the first cycle The period is used when the first terminal device is in the RRC inactive state; the core network device receives a second message from the access network device, the second message includes a second period, the second The period is the eDRX period configured for the first terminal equipment, and the second period is used by the first terminal equipment when it is in the RRC inactive state, and the length of the second period is less than or equal to the Describe the length of the first cycle.
  • the first period is determined according to NAS timing information
  • the NAS timing information includes a minimum retransmission time interval of the NAS message and/or Maximum number of retransmissions for NAS messages.
  • the core network device can determine the first cycle according to the NAS timing information. Compared with the method of determining the first cycle according to the eDRX cycle used by the first terminal device in the RRC idle state, the first cycle can be determined according to the NAS timing information. , the time length of the determined first period can be longer, so that the access network equipment has higher flexibility when configuring the first terminal equipment, and the first period also meets the requirements of the core network equipment.
  • the core network device may also consider other factors when determining the first cycle. For example, the core network device determines the first cycle according to the NAS timing information and the service requirements of the first terminal device. In this way, the first period can not only meet the requirements of the first terminal device for receiving the NAS message, but also meet the service requirements of the first terminal device.
  • the first message is an initial context establishment request message; and/or,
  • the second message is an initial context establishment response message, or the second message is an RRC inactive state transition report.
  • the method further including: the core network device receives an RRC inactive state transition report from the access network device, where the RRC inactive state transition report is used to instruct the first terminal device to enter the RRC inactive state; the The core network device sends a NAS message to the first terminal device according to the second period.
  • the fourth optional embodiment of the seventh aspect can be In an optional embodiment, the first terminal device is a redcap UE.
  • an eighth communication method is provided, and the method can be executed by the first terminal device, or executed by a chip system, and the chip system can realize the function of the first terminal device.
  • the method includes: a first terminal device receiving a third message from an access network device, the third message including a second cycle, the second cycle being an eDRX cycle configured for the first terminal device, and the The second period is used when the first terminal device is in the RRC inactive state, where the second period is determined by the access network device according to the first period, and the first period is the core
  • the second message is an RRC connection release message
  • the RRC connection release message is used to release the first terminal device to the RRC inactive state.
  • the first terminal device is a redcap UE.
  • a ninth communication method is provided, and the method can be executed by an access network device, or executed by a chip system, and the chip system can realize the functions of the access network device.
  • the access network device is a base station.
  • the method includes: the access network device receives a first message from the core network device, the first message includes a first cycle, the first cycle is a maximum eDRX cycle that can be configured for the terminal device, and the first cycle is used by the first terminal equipment when it is in the RRC inactive state; the access network equipment determines a second period according to the first period, and the second period is the maximum eDRX period configured for the terminal equipment, and The second period is used by the terminal device in the RRC inactive state, and the length of the second period is less than or equal to the length of the first period; the access network equipment reports to the core The network device sends a second message, where the second message includes the second period.
  • the core network device first notifies the access network device of the upper limit value acceptable to the core network device, so that the access network device configures the eDRX cycle used in the RRC inactive state for multiple terminal devices It can be more accurate, and the process of re-determining the eDRX cycles configured for multiple terminal devices by the access network device is reduced.
  • the access network device will also notify the core network device of the second cycle that is finally determined, so that if the core network device wants to send a NAS message to any one of the multiple terminal devices, it can be sent according to the second cycle, so that this Multiple terminal devices can normally receive NAS messages from core network devices, no matter whether the second period is greater than 10.24s or less than 10.24s, the method of the embodiments of the present application can improve the probability that the terminal devices receive NAS messages, and reduce the Packet loss rate for NAS messages.
  • the core network device does not need to page the terminal device because the NAS message fails to be sent, and the terminal device does not need to enter the RRC idle state and then initiate random access, which reduces service transmission delay and saves transmission resources.
  • the core network device can send the NAS message according to the second cycle, and there is no need to maintain different eDRX cycles for different terminal devices, which simplifies the implementation process of the core network device.
  • the first message is an AMF configuration update message
  • the second message is an AMF configuration update confirmation message; or, the first message Build a response message for the NG interface.
  • the core network device sends the first cycle to the access network device, and the access network device sends the second cycle to the core network device, both of which can be sent through existing messages, without adding other messages, so that the technical solutions of the embodiments of the present application can be more Compatible well with existing technologies.
  • the first period or the second period may also be sent through other messages, for example, may be sent through a newly added dedicated message, so as to reduce the impact on the function of the existing message.
  • the method further includes: the access network device reporting to the terminal device The first terminal device in sends a third message, the third message includes a third period, the length of the third period is less than or equal to the length of the second period, and the third period is the first period
  • the eDRX cycle configured by the terminal device, and the third cycle is used by the first terminal device when it is in the RRC inactive state
  • the access network device sends the second terminal device among the terminal devices a fourth message, where the fourth message includes a fourth period, the length of the fourth period is less than or equal to the length of the second period, and the fourth period is the eDRX period configured for the second terminal device,
  • the third period is used when the first terminal device is in the RRC inactive state; wherein the length of the third period is the same as or different from the length of the fourth period.
  • the second cycle determined by the access network device is the upper limit value of the eDRX cycle that can be configured for multiple terminal devices. Further, the access network device may separately configure an eDRX cycle for use in the RRC inactive state for different terminal devices in the multiple terminal devices according to the second cycle and some other factors.
  • the access network device may determine the eDRX cycle used by the terminal device in the RRC inactive state according to the second cycle, and the determination method is relatively simple; or, the access network device
  • the eDRX cycle used by the terminal device in the RRC inactive state can be determined according to the second cycle and the service of the terminal device, so that the configured eDRX cycle can not only meet the needs of the terminal device to receive NAS messages, but also meet the needs of the terminal device.
  • the access network device can send the eDRX cycle configured for each terminal device to be used when in the RRC inactive state to the corresponding terminal device, so that the terminal device can use the eDRX configured by the access network device when it is in the RRC inactive state. cycle.
  • the access The length of the second cycle determined by the network device for different terminal devices according to the first cycle is different.
  • the terminal device is a redcap UE.
  • suitable eDRX cycles can be configured for different redcap UEs respectively, so that the configured eDRX not only meets the requirements of the terminal equipment for receiving NAS messages, but also better meets the actual service requirements of the terminal equipment.
  • a tenth communication method is provided, and the method can be executed by a core network device, or executed by a chip system, and the chip system can realize the functions of the core network device.
  • the core network device is an AMF.
  • the method includes: the core network device sends a first message to the access network device, the first message includes a first cycle, the first cycle is a maximum eDRX cycle that can be configured for the terminal device, and the first cycle is Used by the terminal device when it is in the RRC inactive state; the core network device receives a second message from the access network device, the second message includes a second period, and the second period is for the terminal
  • the maximum eDRX cycle configured by the device, and the second cycle is used when the terminal device is in the RRC inactive state, and the length of the second cycle is less than or equal to the length of the first cycle.
  • the first period is determined according to NAS timing information
  • the NAS timing information includes a minimum retransmission time interval of the NAS message and/or Maximum number of retransmissions for NAS messages.
  • the first message is an AMF configuration update message
  • the second message is AMF configuration update confirmation message
  • the first message is an NG interface setup response message.
  • the method further including: the core network device receives an RRC inactive state transition report from the access network device, where the RRC inactive state transition report is used to instruct the first terminal device to enter the RRC inactive state; the The core network device sends a NAS message to a first terminal device in the terminal devices according to the second period, where the first terminal device is any terminal device covered by the access network device.
  • the terminal device is a redcap UE.
  • an eleventh communication method is provided, and the method can be executed by the first terminal device, or executed by a chip system, and the chip system can realize the function of the first terminal device.
  • the method includes: a first terminal device receiving a third message from an access network device, the third message including a third cycle, the third cycle being an eDRX cycle configured for the first terminal device, and the The third period is used when the first terminal device is in the RRC inactive state, wherein the third period is determined by the access network equipment according to the first period and the second period, and the first period is the maximum eDRX cycle that the core network device can configure for multiple terminal devices, and the first cycle is used by the multiple terminal devices when they are in the RRC inactive state, and the second cycle is the eDRX cycle.
  • the maximum eDRX cycle configured by the network access device for the multiple terminal devices, and the second cycle is used when the multiple terminal devices are in the RRC inactive state, and the second cycle is based on the first cycle. If the period is determined, the length of the second period is less than or equal to the length of the first period, and the plurality of terminal equipment includes the first terminal equipment; when the first terminal equipment is in the RRC inactive state Next, the first terminal device monitors the paging according to the third period.
  • the third message is an RRC connection release message
  • the RRC connection release message is used to release the first terminal device to the The RRC is in an inactive state.
  • the first terminal device is a redcap UE.
  • a twelfth communication method is provided, and the method can be executed by an access network device, or executed by a chip system, and the chip system can realize the functions of the access network device.
  • the access network device is a base station.
  • the method includes: the access network device receives a first message from the core network device, the first message includes a first cycle, the first cycle is a maximum eDRX cycle that can be configured for the terminal device, and the first cycle It is used by the terminal equipment when it is in the RRC inactive state; the access network equipment determines a second period according to the first period, and the second period is configured for the first terminal equipment in the terminal equipment and the second period is used by the first terminal device in the RRC inactive state, and the length of the second period is less than or equal to the length of the first period; the The access network device sends a second message to the first terminal device, where the second message includes the second period.
  • the core network device notifies the access network device of the upper limit value acceptable to the core network device, and the access network device can configure the eDRX cycle for different UEs according to the upper limit value, so that the access network device When configuring the eDRX cycles used in the RRC inactive state for multiple UEs, it can be more accurate, which reduces the process of the access network device re-determining the eDRX cycles configured for multiple UEs. If the core network device wants to send a NAS message to any one of the multiple UEs, it can send it according to the first cycle, so that these multiple UEs can normally receive the NAS message from the core network device, regardless of whether the first cycle is greater than or equal to the first cycle.
  • 10.24s is still less than 10.24s.
  • the core network device also does not need to page the first UE because the NAS message fails to be sent, and the first UE does not need to enter the RRC idle state and then initiate random access, which reduces service transmission delay and saves transmission resources.
  • the core network device can send the NAS message according to the second cycle, and there is no need to maintain different eDRX cycles for different UEs, which simplifies the implementation process of the core network device.
  • the first message is an AMF configuration update message, or the first message is an NG interface setup response message.
  • the method further includes: the access network device according to the The first cycle determines a third cycle, where the third cycle is the maximum eDRX cycle configured for the second terminal device among the terminal devices, and the third cycle is when the second terminal device is in the RRC Used in the inactive state, the length of the third period is less than or equal to the length of the first period; the access network device sends a third message to the second terminal device, and the third message includes the The third period; wherein, the length of the second period is the same as or different from the length of the third period.
  • the third optional embodiment of the twelfth aspect In combination with the twelfth aspect or the first optional embodiment of the twelfth aspect or the second optional embodiment of the twelfth aspect, in the third optional embodiment of the twelfth aspect, the lengths of the eDRX cycles determined by the access network device for different terminal devices according to the first cycle are different.
  • the terminal device is a redcap UE.
  • a thirteenth communication method is provided, and the method can be executed by a core network device, or executed by a chip system, and the chip system can realize the functions of the core network device.
  • the core network device is an AMF.
  • the method includes: a core network device determines a first cycle, where the first cycle is a maximum eDRX cycle that can be configured for a terminal device, and the first cycle is used by the terminal device when the terminal device is in an RRC inactive state; the core The network device sends a first message to the access network device, where the first message includes the first period.
  • the first period is determined according to NAS timing information
  • the NAS timing information includes a minimum retransmission time interval of the NAS message and / or the maximum number of retransmissions of NAS messages.
  • the first message is an AMF configuration update message, or all The first message is an NG interface setup response message.
  • the method further includes: the core network device receives an RRC inactive state transition report from the access network device, where the RRC inactive state transition report is used to instruct a first terminal device of the terminal devices to enter the RRC inactive state transition report. the RRC inactive state; the core network device sends a NAS message to the first terminal device according to the first period.
  • the terminal device is a redcap UE.
  • a fourteenth communication method is provided, and the method can be executed by the first terminal device, or executed by a chip system, and the chip system can realize the function of the first terminal device.
  • the method includes: a first terminal device receiving a second message from an access network device, the second message including a second cycle, the second cycle being an eDRX cycle configured for the first terminal device, and the The second period is used when the first terminal device is in the RRC inactive state, where the second period is determined by the access network device according to the first period, and the first period is the core
  • the maximum eDRX cycle that the network device can configure for multiple terminal devices and the first cycle is used by the multiple terminal devices when they are in the RRC inactive state, and the length of the second cycle is less than or equal to the first cycle.
  • the length of one cycle, the multiple terminal devices include the first terminal device; when the first terminal device is in the RRC inactive state, the first terminal device monitors paging according to the second cycle .
  • the second message is an RRC connection release message
  • the RRC connection release message is used to release the first terminal device to The RRC is in an inactive state.
  • the terminal device is a redcap UE.
  • a fifteenth aspect provides a communication device.
  • the communication apparatus may comprise a module for performing the method in the second aspect or any optional implementation manner of the second aspect, for example comprising a transceiving unit and a processing unit.
  • a storage unit may also be included.
  • a sixteenth aspect provides a communication device.
  • the communication device may include a module for performing the method in the third aspect or any optional implementation manner of the third aspect, for example including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a seventeenth aspect provides a communication device.
  • the communication device may include a module for performing the method in the fourth aspect or any optional implementation manner of the fourth aspect, for example including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • An eighteenth aspect provides a communication device.
  • the communication device may include a module for performing the method in the sixth aspect or any optional implementation manner of the sixth aspect, for example including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a nineteenth aspect provides a communication device.
  • the communication apparatus may include a module for performing the method in the seventh aspect or any optional implementation manner of the seventh aspect, for example, including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a twentieth aspect provides a communication device.
  • the communication device may include modules for performing the method in the eighth aspect or any optional implementation manner of the eighth aspect, for example including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a twenty-first aspect provides a communication device.
  • the communication apparatus may include a module for performing the method in the ninth aspect or any optional implementation manner of the ninth aspect, for example including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a twenty-second aspect provides a communication device.
  • the communication apparatus may include a module for performing the method in the tenth aspect or any optional implementation manner of the tenth aspect, for example, including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a twenty-third aspect provides a communication device.
  • the communication apparatus may include a module for performing the method in the eleventh aspect or any optional implementation manner of the eleventh aspect, for example, including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a twenty-fourth aspect provides a communication device.
  • the communication device may include a module for performing the method in the twelfth aspect or any optional implementation manner of the twelfth aspect, for example including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a twenty-fifth aspect provides a communication device.
  • the communication device may include a module for performing the method in the thirteenth aspect or any optional implementation manner of the thirteenth aspect, for example including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a twenty-sixth aspect provides a communication device.
  • the communication device may include a module for performing the method in the fourteenth aspect or any optional implementation manner of the fourteenth aspect, for example including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a twenty-seventh aspect provides a chip system, the chip system includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used for implementing the above-mentioned second aspect or the second A method provided by any optional embodiment of the aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the second aspect or any one of the optional aspects of the second aspect. The method provided by the embodiment.
  • a chip system includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used to implement the third aspect or the third A method provided by any optional embodiment of the aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the third aspect or any one of the options of the third aspect. The method provided by the embodiment.
  • a chip system includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used for implementing the above-mentioned fourth aspect or the fourth aspect A method provided by any optional embodiment of the aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the fourth aspect or any one of the optional aspects of the fourth aspect. The method provided by the embodiment.
  • a chip system includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used for implementing the above sixth aspect or the sixth aspect
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the sixth aspect or any one of the options of the sixth aspect. The method provided by the embodiment.
  • a chip system includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used for implementing the seventh aspect or the seventh aspect A method provided by any optional embodiment of the aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the seventh aspect or any one of the optional aspects of the seventh aspect. The method provided by the embodiment.
  • a thirty-second aspect provides a chip system, the chip system includes one or more processors, and includes a communication interface, the processor is coupled with the communication interface, and is used for implementing the eighth aspect or the eighth above A method provided by any optional embodiment of the aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the eighth aspect or any one of the optional eighth aspects. The method provided by the embodiment.
  • a chip system includes one or more processors, and includes a communication interface, the processor is coupled with the communication interface, and is used for implementing the above ninth aspect or ninth A method provided by any optional embodiment of the aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the ninth aspect or any one of the optional aspects of the ninth aspect. The method provided by the embodiment.
  • a thirty-fourth aspect provides a chip system, the chip system includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used for implementing the tenth aspect or tenth above A method provided by any optional embodiment of the aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the tenth aspect or any one of the options of the tenth aspect. The method provided by the embodiment.
  • a thirty-fifth aspect provides a chip system, the chip system includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used for implementing the eleventh aspect or the first The method provided by any one of the optional embodiments of the eleventh aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement any one of the eleventh aspect or the eleventh aspect above. Methods provided by selected embodiments.
  • a thirty-sixth aspect provides a chip system, the chip system includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used to implement the above-mentioned twelfth aspect or the first The method provided by any one of the optional embodiments of the twelve aspects.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the twelfth aspect or any one of the twelfth aspects. Methods provided by selected embodiments.
  • a thirty-seventh aspect provides a chip system, the chip system includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used for implementing the above-mentioned thirteenth aspect or the first The method provided by any one of the optional embodiments of the thirteenth aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement any one of the thirteenth aspect or the thirteenth aspect. Methods provided by selected embodiments.
  • a thirty-eighth aspect provides a chip system, the chip system includes one or more processors, and includes a communication interface, the processor is coupled with the communication interface, and is used for implementing the above-mentioned fourteenth aspect or the first The method provided by any one of the optional implementation manners of the fourteenth aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement the above fourteenth aspect or any one of the fourteenth aspects. Methods provided by selected embodiments.
  • a thirty-ninth aspect provides a first communication system.
  • the first communication system includes the communication device of the fifteenth aspect or the chip system of the twenty-seventh aspect, the communication device of the sixteenth aspect or the chip system of the twenty-eighth aspect, and includes the first The communication device of the seventeenth aspect or the chip system of the twenty-ninth aspect.
  • the first communication system includes the core network device, the access network device, and the first terminal device described in the first aspect.
  • a second communication system includes the communication device of the eighteenth aspect or the chip system of the thirtieth aspect, the communication device of the nineteenth aspect or the chip system of the thirty-first aspect, and includes the second The communication device of the tenth aspect or the chip system of the thirty-second aspect.
  • the second communication system includes the core network device, the access network device, and the first terminal device described in the fifth aspect.
  • a third communication system includes the communication device of the twenty-first aspect or the chip system of the thirty-third aspect, the communication device of the twenty-second aspect or the chip system of the thirty-fourth aspect, and The communication device of the twenty-third aspect or the chip system of the thirty-fifth aspect is included.
  • a fourth communication system includes the communication device of the twenty-fourth aspect or the chip system of the thirty-sixth aspect, the communication device of the twenty-fifth aspect or the chip system of the thirty-seventh aspect, and It includes the communication device of the twenty-sixth aspect or the chip system of the thirty-eighth aspect.
  • a fifteenth communication method is provided, and the method can be executed by an access network device, or executed by a chip system, and the chip system can realize the functions of the access network device.
  • the access network device is a base station.
  • the method includes: the access network device receives a first message from the core network device, the first message includes a first cycle, the first cycle is a maximum eDRX cycle that can be configured for the first terminal device, and the first cycle A cycle is used when the first terminal device is in the RRC inactive state; the access network device determines a second cycle according to the first cycle, and the second cycle is configured for the first terminal device eDRX cycle, and the second cycle is used when the first terminal equipment is in the RRC inactive state, and the length of the second cycle is less than or equal to the length of the first cycle; the access network The device sends a second message to the first terminal device, the second message including the second period.
  • the core network device first notifies the access network device of the upper limit value acceptable to the core network device, so that when the access network device configures the eDRX cycle used in the RRC inactive state for the first UE It can be more accurate, and the process of re-determining the eDRX cycle configured for the first UE by the access network device is reduced.
  • the access network device will configure the eDRX cycle for the first UE according to the first cycle. If the core network device wants to send the NAS message to the first UE, it can send it according to the first cycle, so that the first UE can follow the eDRX configured by the access network device.
  • the period can normally receive the NAS message from the core network device, no matter whether the second period is greater than 10.24s or less than 10.24s, the method of the embodiment of the present application can improve the probability of the UE receiving the NAS message and reduce the packet loss of the NAS message Rate.
  • the access network device does not need to notify the core network device of the eDRX cycle determined for the first UE, which reduces signaling overhead.
  • the core network device does not need to page the first UE because the NAS message fails to be sent, and the first UE does not need to enter the RRC idle state and then initiate random access, which reduces the transmission delay of the NAS message and saves transmission resources.
  • the core network device may take the NAS timing information as a consideration factor to give the upper limit value of the eDRX cycle (for example, the first cycle) for the access network device as a reference, without having to let the access network device consider
  • the eDRX cycle used by the first UE in the RRC idle state is used to configure the eDRX cycle used in the RRC inactive state for the first UE, so that the manner of configuring the eDRX cycle for the UE is more flexible.
  • the first message is an initial context establishment request message.
  • the second message is an RRC connection release message
  • the RRC connection release message is used to release the first terminal device to the RRC inactive state.
  • the first terminal device is a redcap UE.
  • a sixteenth communication method is provided, and the method can be executed by a core network device, or executed by a chip system, and the chip system can realize the functions of the core network device.
  • the core network device is an AMF.
  • the method includes: the core network device determines a first cycle, the first cycle is a maximum eDRX cycle that can be configured for the first terminal device, and the first cycle is when the first terminal device is in an RRC inactive state used; the core network device sends a first message to the access network device, where the first message includes the first period.
  • the first period is determined according to NAS timing information
  • the NAS timing information includes a minimum retransmission time of the NAS message Interval and/or maximum number of retransmissions of NAS messages.
  • the first message is an initial context establishment request message .
  • the method further includes: the core network device receives an RRC inactive state transition report from the access network device, where the RRC inactive state transition report is used to instruct the first terminal device to enter the RRC inactive state transition report. the RRC inactive state; the core network device sends a NAS message to the first terminal device according to the first period.
  • the first terminal device is a redcap UE.
  • a seventeenth communication method is provided, and the method can be executed by the first terminal device, or executed by a chip system, and the chip system can realize the function of the first terminal device.
  • the method includes: a first terminal device receiving a second message from an access network device, the second message including a second cycle, the second cycle being an eDRX cycle configured for the first terminal device, and the The second period is used when the first terminal device is in the RRC inactive state, where the second period is determined by the access network device according to the first period, and the first period is the core
  • the second message is an RRC connection release message, and the RRC connection release message is used to released to the RRC inactive state.
  • the first terminal device is a redcap UE.
  • a communication device in a forty-sixth aspect, may include modules for performing the method in the forty-third aspect or any optional implementation manner of the forty-third aspect, for example, including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a communication device may include a module for performing the method in the forty-fourth aspect or any optional implementation manner of the forty-fourth aspect, for example, including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a communication device in a forty-eighth aspect, may include modules for performing the method in the forty-fifth aspect or any optional implementation manner of the forty-fifth aspect, for example, including a transceiver unit and a processing unit.
  • a storage unit may also be included.
  • a forty-ninth aspect provides a chip system, the chip system includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used for implementing the above forty-third aspect or The method provided by any optional implementation manner of the forty-third aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement any one of the forty-third aspect or the forty-third aspect above The method provided by an alternative embodiment.
  • a fiftieth aspect provides a chip system, the chip system includes one or more processors, and includes a communication interface, the processor is coupled with the communication interface, and is used for implementing the above forty-fourth aspect or the first The method provided by any optional implementation manner of the forty-fourth aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement any one of the forty-fourth aspect or the forty-fourth aspect above The method provided by an alternative embodiment.
  • a chip system in a fifty-first aspect, includes one or more processors, and includes a communication interface, the processor is coupled to the communication interface, and is used for implementing the above forty-fifth aspect or A method provided by any optional implementation manner of the forty-fifth aspect.
  • the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory, so as to implement any one of the forty-fifth aspect or the forty-fifth aspect above The method provided by an alternative embodiment.
  • a fifth communication system in a fifty-second aspect, includes the communication device of the forty-sixth aspect or the chip system of the forty-ninth aspect, the communication device of the forty-seventh aspect or the chip system of the fiftieth aspect, and includes The communication device of the forty-eighth aspect or the chip system of the fifty-first aspect.
  • a computer-readable storage medium is provided, the computer-readable storage medium is used for storing a computer program, and when the computer program is executed on a computer, the computer is made to execute any one of the above aspects. Methods.
  • a fifty-fourth aspect provides a computer program product comprising instructions, the computer program product is used to store a computer program, and when the computer program is run on a computer, the computer is made to execute any one of the above-mentioned aspects. method.
  • Fig. 1 is a kind of schematic diagram of eDRX cycle
  • Fig. 2 is the flow chart of configuring the eDRX cycle of RRC inactive state for eMTC UE;
  • FIG. 3 is a schematic diagram of an application scenario of an embodiment of the present application.
  • FIG. 4 is a flowchart of a first communication method provided by an embodiment of the present application.
  • FIG. 5 is a flowchart of a second communication method provided by an embodiment of the present application.
  • FIG. 6 is a flowchart of a third communication method provided by an embodiment of the present application.
  • FIG. 7 is a flowchart of a fourth communication method provided by an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of still another communication apparatus provided by an embodiment of the present application.
  • a terminal device is a device with a wireless transceiver function, which may be a fixed device, a mobile device, a handheld device, a wearable device, a vehicle-mounted device, or a wireless device (for example, a communication module or a wireless device) built into the above-mentioned device. system-on-chip, etc.).
  • the terminal device is used to connect people, things, machines, etc., and can be widely used in various scenarios, such as but not limited to the following scenarios: cellular communication, device-to-device communication (device-to-device, D2D), vehicle-to-everything (vehicle to everything, V2X), machine-to-machine/machine-type communications (M2M/MTC), Internet of things (internet of things, IoT), virtual reality (virtual reality, VR) , Augmented reality (AR), industrial control (industrial control), unmanned driving (self driving), telemedicine (remote medical), smart grid (smart grid), smart furniture, smart office, smart wear, smart transportation , terminal equipment for smart city, drone, robot and other scenarios.
  • cellular communication device-to-device communication
  • vehicle-to-everything vehicle to everything, V2X
  • M2M/MTC machine-to-machine/machine-type communications
  • IoT Internet of things
  • virtual reality virtual reality
  • AR Augmented reality
  • the terminal device may sometimes be referred to as a UE, a terminal, an access station, a UE station, a remote station, a wireless communication device, or a user equipment, etc.
  • the terminal device is described by taking the UE as an example in the embodiments of the present application. .
  • redcap UE the UE involved in the various embodiments of this application is, for example, a redcap UE.
  • redcap UE The reason why it is called redcap UE is that compared with the existing ordinary NR UE, redcap UE equipment usually only supports lower bandwidth, such as 20MHz, and supports fewer transceiver antennas, such as only 1T1R or 1T2R.
  • redcap UE includes three types of low-capability UEs: wearable products, video surveillance equipment and industrial sensor equipment.
  • the technical solutions of the various embodiments of the present application can also be applied to other UEs, for example, to a UE that is not sensitive (or less demanding) to delay, such as an eMTC UE.
  • the introduction is mainly made by taking the technical solutions provided by the various embodiments of this application applied to the redcap UE as an example.
  • the network devices in the embodiments of the present application include, for example, access network devices and/or core network devices.
  • the access network device is a device with a wireless transceiver function, and is used to communicate with the terminal device.
  • the access network equipment includes but is not limited to the base station (BTS, Node B, eNodeB/eNB, or gNodeB/gNB), the transmission reception point (TRP) in the above-mentioned communication system, the base station of the subsequent evolution of 3GPP, and the WiFi system. access nodes, wireless relay nodes, wireless backhaul nodes, etc.
  • the base station may be: a macro base station, a micro base station, a pico base station, a small base station, a relay station, and the like.
  • Multiple base stations may support the aforementioned networks of the same access technology, or may support the aforementioned networks of different access technologies.
  • a base station may contain one or more co-sited or non-co-sited transmission reception points.
  • the network device may also be a wireless controller, a centralized unit (centralized unit, CU), and/or a distributed unit (distributed unit, DU) in a cloud radio access network (cloud radio access network, CRAN) scenario.
  • the network device can also be a server, a wearable device, or a vehicle-mounted device.
  • a network device in the V2X technology may be a road side unit (RSU).
  • RSU road side unit
  • the multiple network devices in the communication system may be the same type of base station, or may be different types of base stations.
  • the base station can communicate with the terminal equipment, and can also communicate with the terminal equipment through the relay station.
  • a terminal device can communicate with multiple base stations in different access technologies.
  • the core network equipment is used to implement functions such as mobility management, data processing, session management, policy and charging.
  • the names of devices implementing core network functions in systems with different access technologies may be different, which are not limited in this application.
  • the core network equipment may include an access and mobility management function (AMF), a session management function (SMF), or a user plane function (UPF) Wait.
  • the core network equipment may include a mobility management entity and the like.
  • the apparatus for implementing the function of the network device may be the network device, or may be an apparatus capable of supporting the network device to implement the function, such as a chip system, and the apparatus may be installed in the network device.
  • the technical solutions provided by the embodiments of the present application are described by taking the device for realizing the function of the network device being a network device as an example.
  • the number of nouns means “singular nouns or plural nouns", that is, “one or more”. "At least one” means one or more, and “plurality” means two or more. "And/or”, which describes the relationship of the associated objects, indicates that there can be three kinds of relationships, for example, A and/or B, it can indicate that A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/" generally indicates that the associated objects are an "or” relationship. For example, A/B, means: A or B.
  • At least one item(s) below or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c Can be single or multiple.
  • ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the size, content, order, and timing of multiple objects , priority or importance, etc.
  • the first period and the second period may be the same period (for example, the period of the period is the same) or different periods (for example, the period of the period is different), and this name does not mean The two periods are different in time length, priority or importance.
  • the DRX mechanism achieves the purpose of saving power by receiving signals discontinuously, so that the UE can be in a sleep state most of the time. Because packet-based data streams are generally bursty, when there is no data transmission, power consumption can be reduced by turning off the UE's receiving circuit.
  • eDRX is an extended DRX. In each eDRX cycle, the UE can only receive downlink data in the set PTW, and the UE is in a dormant state during the rest of the time outside the PTW. There is one PTW in each eDRX cycle, and the UE monitors the paging channel according to the DRX cycle in the PTW. If the eDRX period is configured to be larger, the UE can have a larger power consumption gain, but at the same time, the service transmission delay is also increased.
  • the eDRX working mode please refer to Figure 1.
  • LTE UE Long Term Evolution UE
  • eMTC UE eMTC UE
  • NB-IoT UE or NR UE etc.
  • different types of UEs have different service requirements, so different types of UEs have different application conditions for the eDRX mechanism and DRX mechanism.
  • Table 1. For this, please refer to Table 1. .
  • both LTE UEs and NR UEs currently only support the DRX mechanism, but not the eDRX mechanism.
  • the maximum DRX cycles that can be supported in the RRC idle state and the RRC inactive state are both 2.56s.
  • the maximum eDRX period that can be supported is about 44 minutes, and when the RRC is in the inactive state, the maximum eDRX period that can be supported is 10.24s.
  • the NB-IoT UE has no RRC inactive state. When the NB-IoT UE is in the RRC idle state, the maximum eDRX period that can be supported is about 3 hours.
  • redcap UE At present, the working time requirements for each application scenario of redcap UE are proposed. For example, for industrial wireless sensor devices in redcap UE, it needs to work for several years; for wearable devices in redcap UE, the work time is 1 to 2 weeks. Because eDRX is not currently configured for NR UEs, but in order to meet the above working time requirements, it is proposed to study the eDRX of redcap UEs in RRC idle state and RRC inactive state to achieve the purpose of reducing power consumption.
  • the eDRX cycle used when the UE is in the RRC idle state is configured by the core network equipment through the NAS message in the UE registration process; for the eMTC UE, the eDRX cycle used in the RRC inactive state is determined by The base station is configured through the RRC connection release (RRC connection release) message.
  • RRC connection release RRC connection release
  • the eDRX cycle used when the UE is in the RRC idle state that is, the core network paging cycle (core network paging cycle) configured by the core network device for the UE
  • the eDRX cycle used when the UE is in the RRC inactive state that is, the base station is The radio access network (RAN) paging cycle configured by the UE.
  • RAN radio access network
  • the core network device sends the core network assistance information for RRC inactive state (core network assistance information for RRC inactive) to the base station, and the base station receives the core network assistance information for RRC inactive state from the core network device.
  • the core network assistance information for RRC inactive is an information element (information element, IE), and the IE is included in the initial context setup request (initial context setup request) message, for example.
  • the core network assistance information for RRC inactive may include UE-specific DRX (UE-specific DRX) cycles, as well as paging eDRX information.
  • the paging eDRX information is the eDRX cycle used by the UE when the UE is in the RRC idle state.
  • the base station sends an RRC connection release message to the UE, and the UE receives the RRC connection release message from the base station.
  • the base station refers to the paging eDRX information in the core network assistance information for RRC inactive, and determines the eDRX cycle used in the RRC inactive state configured for the UE.
  • the time length of the eDRX cycle used in the RRC inactive state configured by the base station for the UE is less than or equal to the time length of the eDRX cycle corresponding to the paging eDRX information.
  • the base station can send the eDRX cycle to the UE through the RRC connection release message, so that the UE can use the eDRX cycle to monitor after entering the RRC inactive state. paging.
  • the minimum retransmission time interval of NAS messages in mobility management is 6s, and the maximum number of retransmissions is 4 times.
  • the eMTC UE When the eMTC UE is connected to the 5G core network (5GC), it can be in the RRC inactive state.
  • the UE When the UE is in the RRC inactive state, since the base station still retains the context of the UE and connects with the next generation (NG) interface of the core network , so the core network equipment thinks that the UE is in the RRC connected (connected) state, but both the base station and the UE know that the UE is actually in the RRC inactive state.
  • NG next generation
  • the base station will page the UE after receiving the NAS message from the core network device, and send the NAS message after the UE responds to the paging to the UE, and after the UE responds to the paging, the access network device sends the feedback information corresponding to the NAS message to the core network device. Because the minimum retransmission interval of the NAS message is 6s and the maximum number of retransmissions is 4, the core network device needs to receive the feedback information for the NAS message within 30s, otherwise the core network device will consider the NAS message transmission. fail.
  • the core network device If the core network device considers that the transmission of the NAS message fails, the core network device will paging the UE. If the UE receives a paging message from the core network device, the UE needs to enter the RRC idle state, and then initiate a call in the RRC idle state. random access.
  • the base station when the base station configures the eDRX cycle in the RRC inactive state for the UE, it will refer to the paging eDRX information in the core network assistance information for RRC inactive.
  • the eDRX cycle will not affect the UE's reception of NAS messages.
  • the redcap UE can also support the eDRX mechanism in the RRC inactive state, the eDRX period in the RRC inactive state of the redcap UE is not necessarily less than or equal to 10.24s, and may be greater than 10.24s.
  • the increase in the time length of the eDRX cycle will reduce the number of times the UE receives NAS messages, and even the UE cannot receive any NAS message within one eDRX cycle. Then, when the number of retransmissions of the NAS message exceeds 4 times, the core network device will consider that the transmission of the NAS message fails, and the core network device will page the UE. If the UE receives the paging message from the core network device, the The UE needs to enter the RRC idle state, and then initiate random access in the RRC idle state. Obviously, this process will bring a large delay and consume more transmission resources.
  • the access network device and the core network device can negotiate to determine the second cycle, where the second cycle is an eDRX cycle that can be configured for the first terminal device to use in the RRC inactive state.
  • a reasonable eDRX cycle can be given based on the conditions of the access network device and the core network device, so that if the core network device wants to send a NAS message to the first terminal device, it can send it according to the second cycle, so that , no matter whether the second period is less than or equal to 10.24s or greater than 10.24s, the first terminal device can normally receive the NAS message from the core network device according to the second period, which improves the probability of the terminal device receiving the NAS message and reduces the The packet loss rate of the NAS message also reduces the transmission delay of the NAS message accordingly.
  • the technical solutions provided in the embodiments of this application can be applied to 4G systems, such as LTE systems, or can be applied to 5G systems, such as NR systems, or can also be applied to next-generation mobile communication systems or other similar communication systems. No restrictions.
  • FIG. 3 is an application scenario of the embodiment of the present application.
  • FIG. 3 includes access network equipment, core network equipment and UE.
  • the access network device for example, works in the Evolved UMTS terrestrial radio access (E-UTRA) system, or works in the NR system, or works in the next generation communication system or other communication systems middle.
  • the access network device is, for example, a base station.
  • the access network equipment corresponds to different equipment in different systems, for example, in a 4G system, it may correspond to an eNB, and in a 5G system, it corresponds to an access network equipment in 5G, such as a gNB.
  • FIG. 3 takes the access network device being a base station as an example.
  • the access network device may also be a device such as an RSU.
  • the UE in FIG. 3 takes a mobile phone as an example.
  • the UE in the embodiment of the present application is not limited to the mobile phone.
  • each of the embodiments to be introduced later is taken as an example to be applied to the architecture shown in FIG. 3 .
  • the access network devices described in the following embodiments are, for example, the access network devices in the network architecture shown in FIG. 3
  • the core network devices described in the following embodiments are, for example, those shown in FIG. 3 .
  • the core network device in the network architecture the UE described in each of the following embodiments may be the UE in the network architecture shown in FIG. 3 .
  • the core network device described in the following embodiments is, for example, an AMF, or may also be other devices located on the core network side.
  • FIG. 4 is a flowchart of the method.
  • the core network device sends the first information, and correspondingly, the access network device receives the first information from the core network device.
  • the first information includes, for example, the eDRX cycle used by the first UE when it is in the RRC idle state.
  • the first information may further include information such as a UE-specific DRX cycle.
  • the first UE is in the RRC idle state, if the core network device obtains the downlink data of the first UE (for example, the core network device receives the downlink data from other devices, or the core network device generates the downlink data), the core network device A core network paging message for paging the first UE may be sent, and the first information may be included in the core network paging message.
  • the core network paging message includes a paging eDRX cycle information element (paging eDRX information IE), and the eDRX cycle used by the first UE in the RRC idle state may be included in the information element (information element, IE).
  • the UE-specific DRX cycle may be included in the paging DRX IE in the core network paging message. If the first information is included in the core network paging message, after receiving the core network paging message, the first UE may initiate random access to the access network device to enter the RRC connected state from the RRC idle state.
  • the core network device may also send the first information to the access network device through other messages, as long as the message is a message related to the first UE (for example, the message includes the identifier of the first UE), for the message
  • the type is not limited.
  • the access network device determines a first cycle, where the first cycle is an eDRX cycle that the access network device expects to configure for the first UE, and the first cycle is used when the first UE is in an RRC inactive state.
  • the access network device may determine the first cycle according to the first information, for example, the access network device may determine the first cycle according to the eDRX cycle used by the first UE in the RRC idle state. For example, the time length of the first cycle determined by the access network device may be less than or equal to the time length of the eDRX cycle used by the first UE when it is in the RRC idle state.
  • the access network device sends the first message to the core network device, and correspondingly, the core network device receives the first message from the access network device.
  • the first message includes the first period.
  • the access network device can send the paging message to the first UE in addition to determining the first period.
  • the first UE receives the paging message from the access network device .
  • the first UE may initiate an RRC connection establishment procedure to the access network device based on the paging message, so as to establish an RRC connection with the access network device.
  • the first uplink NAS message initiated by the first UE may be sent to the core network device through an initial UE message (initial UE message).
  • the initial UE message may include information such as attach request, user location information, RRC establishment cause, and authenticated indication.
  • the attach request may include information included in the NAS message from the first UE.
  • the first period may be included in the initial UE message, that is, the initial UE message may be used as the first message.
  • an IE is added in the initial UE message, for example, called the first IE, and the first period may be borne by the first IE.
  • the access network device may also send the first period to the core network device through other messages, that is, the first message may also be other messages than the initial UE message.
  • the core network device sends the second message to the access network device, and correspondingly, the access network device receives the second message from the core network device.
  • the second message includes the second period.
  • the core network device may determine the second cycle, where the second cycle is an eDRX cycle determined by the core network device to be used by the first UE when the RRC is in an inactive state. For example, the core network device may determine whether the first cycle can be configured for the first UE, or, in other words, whether the core network device can accept the first cycle as the eDRX cycle used by the first UE in the RRC inactive state. If the core network device determines that the first period can be configured for the first UE, the second period and the first period are the same period, for example, the time length of the second period is equal to the time length of the first period.
  • the core network device determines that the first cycle cannot be configured for the first UE, the core network device can re-determine a second cycle acceptable to the core network device for the first UE.
  • the second cycle and the first cycle are different eDRX Periods, eg, the second period has a time length that is not equal to the first period.
  • the core network device may determine whether the first period can be configured for the first UE according to the NAS timing information, or the core network device may determine the second period according to the NAS timing information and the first period. For example, if the core network device determines that the first cycle can be adapted to the current NAS timing information, the core network device determines that the first cycle can be accepted by the first UE, then the time length of the second cycle is equal to the time length of the first cycle; or , if the core network device determines that the current NAS timing information cannot be adapted for the first cycle, but if the NAS timing information is adjusted so that the first cycle can be adapted to the adjusted NAS timing information, the core network device determines that it can accept the use of the first UE.
  • the first cycle then the time length of the second cycle is equal to the time length of the first cycle; or, if the core network device determines that the first cycle cannot be adapted to the current NAS information, and even if the NAS timing information is adjusted, the first cycle cannot be Adapt the adjusted NAS timing information (because the core network equipment is not unlimited for the adjustment of NAS timing information, it may not be able to adjust after a certain level of adjustment, so even if the NAS timing information is adjusted, it may not be able to adapt to the first cycle), the core network device determines that the first cycle cannot be accepted by the first UE, then the time length of the second cycle is not equal to the time length of the first cycle, for example, the time length of the second cycle is less than the time length of the first cycle, but The time length of the second period may be equal to the maximum time length determined from the NAS timing information.
  • the NAS timing information may include the minimum retransmission time interval of the NAS message, or the maximum number of retransmissions of the NAS message, or the minimum retransmission time interval of the NAS message and the maximum number of retransmissions of the NAS message. If the NAS timing information includes the minimum retransmission time interval of the NAS message, the core network device adjusting the NAS timing information refers to adjusting the minimum retransmission time interval of the NAS message. For example, the minimum retransmission time interval of the NAS message can be increased or adjusted. Small, in order to make the eDRX cycle configured for the UE more flexible, generally, the minimum retransmission time interval of the NAS message can be increased.
  • the core network equipment has restrictions on acceptance, so the minimum retransmission time interval of NAS messages cannot be increased indefinitely, but has an upper limit.
  • the core network device adjusting the NAS timing information refers to adjusting the maximum number of retransmissions of the NAS message.
  • the maximum number of retransmissions of the NAS message can be adjusted to be larger or smaller.
  • the maximum number of retransmissions of the NAS message can be increased.
  • the core network equipment has restrictions on acceptance, so the maximum number of retransmissions of NAS messages cannot be increased indefinitely, but there is an upper limit for adjustment.
  • the core network device adjusts the NAS timing information, which may include adjusting the minimum retransmission time interval of the NAS message, or including adjusting the NAS message's minimum retransmission time interval. Maximum number of retransmissions, or adjust both the minimum retransmission interval of NAS messages and the maximum number of retransmissions of NAS messages.
  • the core network device can determine the first threshold according to the NAS timing information.
  • the first threshold is, for example, the maximum time length corresponding to the NAS timing information, or the first threshold is acceptable to the core network device and is a terminal device The configured maximum eDRX cycle.
  • the first threshold may be determined according to unadjusted NAS timing information, or may also be determined according to adjusted NAS timing information. If the first threshold is determined according to the adjusted NAS timing information, for example, the first threshold is determined according to the NAS timing information adjusted according to the maximum adjustment range, that is, the first threshold can be regarded as the capability of the core network device the maximum value that can be accepted.
  • the core network device determines that the first cycle can be accepted.
  • the second cycle and the first cycle may be the same cycle, for example, the time of the second cycle The length is the same as the time length of the first cycle. If the time length of the first cycle is greater than the first threshold, the core network device determines that the first cycle cannot be accepted. In this case, the core network device can determine the second cycle that the core network device can accept, then the second cycle The time length of the second period can be smaller than the time length of the first period, but the second period needs to meet the requirements of the core network equipment, so the length of the second period can be less than or equal to the first threshold.
  • the core network device may determine according to the NAS timing information that it can accept the first UE to use the first cycle. In this case, The core network device can accept that the first UE uses the first cycle, and the time length of the second cycle determined by the core network device may be equal to the time length of the first cycle. For another example, the time length of the first cycle is relatively long. For example, the time length of the first cycle is greater than 10.24s, such as 20.48s. The core network device can adjust the NAS timing information.
  • the adjusted NAS timing information can be adapted to the 20.48s eDRX cycle
  • the core network device can accept that the first UE uses the first cycle
  • the time length of the second cycle determined by the core network device may be equal to the time length of the first cycle.
  • the time length of the first cycle is relatively long, for example, the time length of the first cycle is greater than 10.24s, such as 40.96s
  • the core network device determines that even if the NAS timing information is adjusted according to the maximum adjustment range (for example, the minimum value of the NAS message
  • the retransmission time interval is adjusted to the maximum value acceptable to the core network equipment, and/or the maximum number of retransmissions of NAS messages is adjusted to the maximum value acceptable to the core network equipment), and the adjusted NAS timing information also cannot be adapted.
  • the core network device cannot accept that the first UE uses the first cycle, and the time length of the second cycle determined by the core network device may be smaller than the time length of the first cycle.
  • the core network device may send the second cycle to the access network device through a second message.
  • the core network device sends an initial context establishment request message to the access network device, and the initial context establishment request message may be used as the second message.
  • the initial context establishment request message includes the second IE
  • the second IE is, for example, the UE Radio Capability for Paging IE of the paging information element.
  • the second IE may further include other IEs, for example, the second IE further includes a third IE, and the third IE is, for example, a UE radio paging information element (UE radio paging information).
  • the second period is carried, for example, by the first field included in the third IE, and the first field is, for example, a spare field.
  • the third IE includes one or more blank fields, and the first field may be one of them.
  • UE radio paging information is defined as follows:
  • spare1 to spare7 represent seven blank fields, and the first field may include one or more of the seven blank fields.
  • the initial context establishment request message includes core network assistance information for RRC inactive, for example, an IE is added to the core network assistance information for RRC inactive, for example, called the fourth IE, and the fourth IE can carry the second cycle.
  • an IE is added to the core network assistance information for RRC inactive, for example, called the fourth IE, and the fourth IE can carry the second cycle.
  • the core network device may also send the second period to the access network device through other messages, as long as the message is related to the first UE (for example, the message includes the identifier of the first UE).
  • the access network device and the core network device have completed the negotiation of the eDRX cycle in the RRC inactive state of the first UE, and the second cycle is the first UE determined through the negotiation in the RRC inactive state.
  • the eDRX cycle used.
  • the access network device sends the third message to the first UE, and correspondingly, the first UE receives the third message from the access network device.
  • the third message includes the second period.
  • the access network device receives the second cycle from the core network device, because the second cycle is acceptable to the core network device, the core network device will send the NAS message to the first UE according to the second cycle, so the access network device will The second period is used as the final value configured to the first UE.
  • the access network device can send the second cycle to the first UE through the third message, that is, configure the second cycle to the first UE, so that the first UE can use the second cycle to monitor after entering the RRC inactive state paging.
  • the access network device may start the RRC connection release timer. If the RRC connection release timer expires, the access network device may send an RRC connection release message to the first UE to release the first UE to the RRC inactive state.
  • the first UE is a mobile phone. If the user does not use the mobile phone temporarily and the mobile phone enters the standby state, there may be no data transmission between the mobile phone and the access network device. After receiving the uplink data from the mobile phone, and the access network device has no downlink data to send to the terminal device, the access network device can release the mobile phone to the RRC inactive state.
  • the access network device when sending the RRC connection release message to the first UE, includes the second period in the RRC connection release message and sends it to the first UE, that is, the RRC connection release message can be used as the third message.
  • the RRC connection release message is used to release the first UE to the RRC inactive state, and the second cycle is also used by the first UE when it is in the RRC inactive state, so the second cycle is sent to the first UE through the RRC connection release message , so that the second cycle can be applied in a timely manner.
  • the RRC connection release message can not only release the first UE to the RRC inactive state, but also configure the second period for the first UE, which improves the utilization rate of the message, and because there is no need to send an additional message to configure the first UE for the first UE Two cycles also reduce the transmission overhead.
  • the access network device may also send the second cycle to the first UE through other messages, for example, the access network device may also send the second cycle to the first UE through other messages before sending the RRC connection release message to the first UE. a UE.
  • the access network device sends an RRC inactive transition report (RRC inactive transition report) to the core network device, and correspondingly, the core network device receives the RRC inactive transition report from the access network device.
  • RRC inactive transition report RRC inactive transition report
  • the RRC inactive state transition report may indicate that the first UE has entered the RRC inactive state.
  • the core network device sends the NAS message to the first UE according to the second period, and correspondingly, the first UE monitors the paging according to the second period to receive the NAS message.
  • the core network device may send a NAS message to the first UE when the first UE is in the RRC inactive state. After receiving the NAS message, the access network device will page the first UE. If the first UE monitors the paging according to the second period, the first UE may receive a paging message from an access network device, where the paging message is an access network paging message. After receiving the paging message, the first UE may respond to the paging message to the access network device. After receiving the response from the first UE, the access network device sends the NAS message to the first UE, so that the first UE obtains the NAS message.
  • the first UE receives a paging message from the access network device, it can initiate random access to the access network device, and the access network device receives the random access preamble (preamble) from the first UE, and then It is considered that the response of the first UE has been received. After the random access is successful, the access network device may send the NAS message to the first UE. Alternatively, if the first UE receives the paging message from the access network device, it may not initiate random access, but respond to the access network device in other ways. In addition, after receiving the response from the first UE, the access network device may also send feedback information to the core network device.
  • the access network device may also send feedback information to the core network device.
  • the core network device can perform the time specified by the NAS timing information. After receiving the feedback information, the core network device will consider that the NAS message is sent successfully, and there is no need to page the first UE through the core network paging message, and the first UE does not need to enter the RRC idle state and then initiate random access, reducing the NAS The transmission delay of the message also reduces the transmission overhead.
  • the first UE may be any UE served by the access network device, for example, the first UE is a redcap UE.
  • the technical solutions of the embodiments of the present application can be applied. That is, through the technical solutions of the embodiments of the present application, appropriate eDRX cycles can be configured for different redcap UEs respectively, so that the configured eDRX not only meets the requirements of the UE for receiving NAS messages, but also more closely meets the actual service requirements of the UE.
  • S41 , S42 , S46 and S47 are all optional steps and are not required to be performed.
  • a relatively reasonable eDRX cycle can be given to the first UE based on the conditions of the access network device and the core network device, so that if the core network device wants to send a NAS message to the first UE, it can follow the The second cycle is sent, so that the first UE can normally receive the NAS message from the core network device according to the second cycle.
  • the method of the embodiment of the present application can improve the UE The probability of receiving NAS messages reduces the packet loss rate of NAS messages.
  • the core network device does not need to page the first UE because the NAS message fails to be sent, and the first UE does not need to enter the RRC idle state and then initiate random access, which reduces the transmission delay of the NAS message and saves transmission resources.
  • the embodiment of the present application provides a second communication method. Please refer to FIG. 5 , which is a flowchart of the method.
  • the core network device sends the first message to the access network device, and correspondingly, the access network device receives the first message from the core network device.
  • the first message includes the first period.
  • the first period is an eDRX period determined by the core network device for the first UE, and the first period is used when the first UE is in an RRC inactive state.
  • the core network device may first determine the first cycle that the core network device can accept, and send the first cycle to the access network device. For example, the core network device may determine the first period according to the NAS timing information. For the content included in the NAS timing information, reference may be made to the introduction of the embodiment shown in FIG. 4 .
  • the core network device determines the first period according to the NAS timing information.
  • the first period may be determined according to the unadjusted NAS timing information. That is, the core network equipment does not make any adjustment to the NAS timing information, and determines the first period according to the unadjusted NAS timing information. .
  • the time length of the first period may be less than or equal to the first threshold corresponding to the unadjusted NAS timing information.
  • the core network device may also adjust the NAS timing information, and determine the first period according to the adjusted NAS timing information.
  • the time length of the first period may be less than or equal to the first threshold corresponding to the adjusted NAS timing information.
  • the core network device adjusts the NAS timing information according to the maximum adjustment range (for example, adjusts the minimum retransmission time interval of the NAS message to the maximum value acceptable to the core network device, and/or adjusts the maximum retransmission time interval of the NAS message
  • the number of times is adjusted to the maximum value acceptable to the core network equipment), and the first period is determined according to the adjusted NAS timing information, so that the time length of the first period determined in this way is longer, so that the access network equipment is performing for the first UE. More flexibility in configuration.
  • the first threshold reference may be made to the embodiment shown in FIG. 4 .
  • the core network device may determine the first period according to the NAS timing information and the service requirement of the first UE. That is to say, the core network device may also consider the service requirements of the first UE when determining the first period, so that the determined first period is more suitable for the application of the first UE. For example, the core network device may determine the first period according to the unadjusted NAS timing information and the service requirements of the first UE; or, the core network device may also adjust the NAS timing information, and determine the first period according to the adjusted NAS timing information and the first UE. The service requirements of the UE determine the first period. For information on how the core network device adjusts the NAS timing information, please refer to the previous introduction.
  • the core network device may determine the first period according to the NAS timing information and the capability of the first UE. That is, the core network device may also consider the capability of the first UE when determining the first period, so that the determined first period is more in line with the capability of the first UE. For example, the core network device may determine the first cycle according to the unadjusted NAS timing information and the capability of the first UE; alternatively, the core network device may also adjust the NAS timing information, and determine the first period according to the adjusted NAS timing information and the first UE The ability to determine the first cycle. For information on how the core network device adjusts the NAS timing information, please refer to the previous introduction.
  • the core network device may determine the first period according to the NAS timing information, the capability of the first UE, and the service requirements of the first UE, and so on.
  • the embodiments of the present application do not limit the factors considered when the core network device determines the first period.
  • the core network device may send an initial context establishment request message corresponding to the first UE to the access network device, and include the first period in the initial context establishment request message.
  • the initial context establishment request message includes core network assistance information for RRC inactive.
  • an IE is added to the core network assistance information for RRC inactive, and the IE can carry the first cycle.
  • the initial context establishment request message may include the UE Radio Capability for Paging IE, and may also include UE radio paging information in the UE Radio Capability for Paging IE.
  • the second period is carried, for example, by the first field included in the UE radio paging information, and the first field is, for example, a blank field.
  • the UE radio paging information includes one or more blank fields, and the first field may be one of them.
  • UE radio paging information reference may be made to the introduction of the embodiment shown in FIG. 4 .
  • the core network device may also send the first cycle to the access network device through other messages.
  • the access network device determines the second period according to the first period.
  • the access network device may determine, according to the first cycle, the eDRX cycle to be configured for the first UE and used by the first UE in the RRC inactive state, for example, the cycle determined by the access network device is called the eDRX cycle. for the second cycle.
  • the time length of the second cycle determined by the access network device needs to be within the acceptable range of the core network device, so the time length of the second cycle may be less than or equal to the time length of the first cycle. From this perspective, the first cycle can be considered as the maximum eDRX cycle that can be accepted by the core network device and is configured for the first UE and used in the RRC inactive state.
  • the access network device may determine the second cycle according to the first cycle and the capability of the first UE, so that the second cycle can conform to the capability of the first UE; or, the access network device may determine the second cycle according to the first cycle and the capability of the first UE.
  • the service requirements determine the second period, so that the second period can meet the service requirements of the first UE; or, the access network device may determine the second period according to the first period, the capabilities of the first UE, and the service requirements of the first UE, etc. etc., the factors used by the access network device to determine the second period are not limited.
  • the access network device can configure the eDRX cycle for the UE according to the actual situation of the UE (such as service requirements or capabilities, etc.), the eDRX cycle used in the RRC inactive state determined by the access network device for different UEs may be the same , may also be different.
  • the access network device sends the second message to the core network device, and correspondingly, the core network device receives the second message from the access network device.
  • the second message includes the second period.
  • the access network device After the access network device determines the second cycle, it can send the second cycle to the core network device through a second message, so that the core network device knows the second cycle actually configured for the first UE, so that the core network device can follow the second cycle.
  • the period is that the first UE in the RRC inactive state sends a NAS message.
  • the access network device sends an initial context establishment response message to the core network device, and includes the second period in the initial context establishment response message, that is, the initial context establishment response message can be used as the second message.
  • the initial context establishment response message can be used as the second message.
  • an IE is added to the initial context establishment response message, and the IE can carry the second period.
  • the access network device sends the third message to the first UE, and correspondingly, the first UE receives the third message from the access network device.
  • the third message includes the second period.
  • the access network device configures the second cycle for the first UE, then the access network device can send the second cycle to the first UE through a third message, that is, configure the second cycle to the first UE, so that the first UE After entering the RRC inactive state, the second period may be used to monitor paging.
  • S45 For more content of S54, reference may be made to S45 in the embodiment shown in FIG. 4 .
  • the access network device sends an RRC inactive state transition report to the core network device, and correspondingly, the core network device receives the RRC inactive state transition report from the access network device.
  • the RRC inactive state transition report may indicate that the first UE has entered the RRC inactive state.
  • the access network device may not send the second cycle to the core network device through the initial context establishment response message, but send the second cycle to the core network device by including the second cycle in the RRC inactive state transition report.
  • the core network device sends the NAS message to the first UE according to the second period, and correspondingly, the first UE monitors the paging according to the second period to receive the NAS message.
  • the first UE may be any UE served by the access network device, for example, the first UE is a redcap UE.
  • the core network device may determine the first cycle for a UE according to the NAS timing information and the service requirements of the UE. If the service requirements of different UEs are different, the first cycle determined by the core network device for different UEs may be different.
  • the second period configured by the access network equipment for different UEs may also be different; for another example, the core network equipment can determine the first period for the UE according to the NAS timing information and the capability of a UE, then the If the capabilities are different, the first period determined by the core network device for different UEs may be different, and correspondingly, the second period configured by the access network device for different UEs may also be different.
  • the access network device may determine the second period according to the first period and the capability of the UE, or may determine the second period according to the first period and the service requirements of the UE, etc. , the second period configured by the access network device for different UEs may also be different.
  • an appropriate eDRX cycle can be configured for each UE, so that the configured eDRX not only meets the requirements of the UE for receiving NAS messages, but also better meets the actual service requirements of the UE.
  • the access network device does not need to send the second cycle to the core network device, and the access network device only needs to configure the second cycle for the first UE according to the first cycle, and configure the second cycle Just give it to the first UE.
  • the message sent by the access network device to the first UE in S54 may be referred to as a second message, and the second message may be, for example, an RRC connection release message, or may also be other messages.
  • S56 may be replaced with: the core network device sends the NAS message to the first UE according to the first period, and correspondingly, the first UE still monitors the paging according to the second period.
  • the core network device sends the NAS message according to the first cycle, and the first UE can monitor it during the eDRX cycle, which will not affect the first UE's ability to Reception of NAS messages.
  • S53, S55 and S56 are all optional steps, and are not required to be performed.
  • the core network device first notifies the access network device of the upper limit value acceptable to the core network device, so that when the access network device configures the eDRX cycle used in the RRC inactive state for the first UE It can be more accurate, and the process of re-determining the eDRX cycle configured for the first UE by the access network device is reduced.
  • the access network device will also notify the core network device of the second cycle that is finally determined, so that if the core network device wants to send the NAS message to the first UE, it can send it according to the second cycle, so that the first UE can normally follow the second cycle.
  • the method of the embodiment of the present application can improve the probability of the UE receiving the NAS message and reduce the packet loss rate of the NAS message.
  • the core network device does not need to page the first UE because the NAS message fails to be sent, and the first UE does not need to enter the RRC idle state and then initiate random access, which reduces the transmission delay of the NAS message and saves transmission resources.
  • the core network device may take the NAS timing information as a consideration factor to give the upper limit value of the eDRX cycle (for example, the first cycle) for the access network device as a reference, without having to let the access network device consider
  • the eDRX cycle used by the first UE in the RRC idle state is used to configure the eDRX cycle used in the RRC inactive state for the first UE, so that the manner of configuring the eDRX cycle for the UE is more flexible.
  • This embodiment of the present application provides a third communication method. Please refer to FIG. 6 , which is a flowchart of the method.
  • the core network device sends the first message to the access network device, and correspondingly, the access network device receives the first message from the core network device.
  • the first message includes the first period.
  • the first cycle is the maximum eDRX cycle determined by the core network device for the multiple UEs, and the first cycle is the eDRX cycle used by the multiple UEs when they are in the RRC inactive state. It can be understood that the eDRX cycles configured by the final access network device for the multiple UEs may be the same or different, but all need to be less than or equal to the first cycle.
  • the first period in this embodiment of the present application corresponds to multiple UEs, for example, the multiple UEs are all redcap UEs.
  • the multiple UEs may include all redcap UEs served by the core network device and the access network device, or may include some redcap UEs served by the core network device and the access network device.
  • the core network device may determine the first period according to the NAS timing information.
  • content such as how the core network equipment determines the first period according to the NAS timing information, reference may be made to the introduction of the embodiment shown in FIG. 5 .
  • the core network device is an AMF
  • the AMF can send an AMF configuration update (AMF configuration update) message to the access network device, and include the first period in the AMF configuration update message, that is, the AMF configuration update message can be used as the first message .
  • AMF configuration update AMF configuration update
  • a first IE is added to the AMF configuration update message, and the first IE can be used to carry the first period.
  • the access network device may send an NG interface setup request (NG setup request) message to the core network device to request to establish an NG interface connection with the core network device.
  • NG setup request NG interface setup request
  • the core network device can send an NG interface setup response (NG setup response) message to the access network device to establish the NG interface connection with the access network device.
  • the core network device may also include the first period in the NG interface establishment response message and send it to the access network device, that is, the NG interface establishment response message may be used as the first message.
  • a second IE is added to the NG interface establishment response message, and the second IE may be used to carry the first period.
  • the core network device may also send the first cycle to the access network device through other messages, because the first cycle in this embodiment of the present application corresponds to multiple UEs, or does not specifically correspond to one or several UEs. Therefore, the message for sending the first cycle may not be related to a specific UE (eg, the message does not include the identity of any UE).
  • the access network device determines the second period according to the first period.
  • the access network device may determine, according to the first cycle, the maximum eDRX cycles to be configured for the multiple UEs and used by the multiple UEs in the RRC inactive state. For example, the access network device determines the maximum eDRX cycle.
  • the cycle is called the second cycle.
  • the time length of the second cycle determined by the access network device needs to be within the acceptable range of the core network device, so the time length of the second cycle may be less than or equal to the time length of the first cycle. That is to say, the core network device determines an upper limit value of the eDRX cycle (that is, the first cycle) for the multiple UEs, and the access network device can determine the eDRX cycle actually configured for the multiple UEs according to the first cycle. Upper limit value (ie, the second period).
  • the access network device may determine the second cycle according to the first cycle, and the determination method is relatively simple; or, the access network device may determine the second cycle according to the first cycle and the service requirements of the multiple UEs, so that the second cycle is both It can meet the needs of multiple UEs to receive NAS messages, and can also meet the service needs of these multiple UEs; or, the access network device can determine the second cycle according to the first cycle and the capabilities of the multiple UEs, so that the second cycle is both It can meet the needs of multiple UEs to receive NAS messages, and can also meet the actual capabilities of these multiple UEs; alternatively, the access network equipment can also be determined according to the first period, the service requirements of the multiple UEs, and the capabilities of the multiple UEs Second cycle, and so on.
  • the access network device sends the second message to the core network device, and correspondingly, the core network device receives the second message from the access network device.
  • the second message includes the second period.
  • the access network device After the access network device determines the second cycle, it can send the second cycle to the core network device through the second message, so that the core network device knows the second cycle actually configured for the multiple UEs, so that the For any UE, when the UE is in the RRC inactive state, if the core network device wants to send the NAS message to the UE, the core network device can send the NAS message according to the second cycle. It can be seen that, in the embodiment of the present application, no matter which UE among the multiple UEs is concerned, the core network device only needs to send a NAS message to the UE in the RRC inactive state according to one eDRX cycle (ie, the second cycle). , the core network equipment does not need to maintain different NAS messages for each UE, which simplifies the implementation of the core network equipment.
  • the access network device sends an AMF configuration update acknowledgement (AMF configuration update acknowledge) message to the core network device, and includes the second period in the AMF configuration update acknowledge message, that is, the AMF configuration update message can be used as the second message.
  • AMF configuration update acknowledge AMF configuration update acknowledge
  • the access network device may also send the second cycle to the core network device through other messages. For example, after the access network device and the core network device establish a connection with the NG interface, the access network device may send the core network device through the NG interface to the core network device. The device sends a corresponding message and includes the second period in the message.
  • the message used to send the second period may be irrelevant to the UEs, for example, the message does not include the UEs 's identification.
  • the access network device sends the third message to the first UE, and correspondingly, the first UE receives the third message from the access network device.
  • the third message includes the third period.
  • the second cycle determined by the access network device is an upper limit value of the eDRX cycle that can be configured for multiple UEs. Further, the access network device may separately configure eDRX cycles used in the RRC inactive state for different UEs in the plurality of UEs according to the second cycle and some other factors. The eDRX cycles configured by the access network device for different UEs among the multiple UEs and used in the RRC inactive state may have the same time length or different time lengths.
  • the access network device may determine the eDRX cycle used by the UE in the RRC inactive state according to the second cycle, and the determination method is relatively simple; The second cycle and the service of the UE determine the eDRX cycle used by the UE in the RRC inactive state, so that the configured eDRX cycle can meet the requirements of the UE for receiving NAS messages and the service transmission requirements of the UE; or , the access network device can determine the eDRX cycle used by the UE in the RRC inactive state according to the second cycle and the capability of the UE, so that the determined eDRX cycle can not only meet the needs of multiple UEs to receive NAS messages, but also meet the The actual capability of the UE; alternatively, the access network device may also determine the eDRX cycle used by the UE in the RRC inactive state according to the second cycle, the service requirements of the UE, and the capability of the UE, and so on.
  • the first UE is one of multiple UEs.
  • the access network device configures a third period for the first UE according to one of the above configuration methods, and the third period is used when the first UE is in the RRC inactive state. eDRX cycle.
  • the access network device can send the third cycle to the first UE through the third message, that is, configure the third cycle to the first UE, so that the first UE can use the third cycle to monitor after entering the RRC inactive state paging.
  • the time length of the third cycle is less than or equal to the time length of the second cycle.
  • S64 For more content of S64, such as what kind of message the third message can use to implement, etc., reference may be made to S45 in the embodiment shown in FIG. 4 .
  • the access network device sends a fourth message to the second UE, and correspondingly, the second UE receives the fourth message from the access network device.
  • the fourth message includes the fourth cycle.
  • the second UE is one of the plurality of UEs, and the first UE and the second UE are different UEs.
  • the access network device configures a fourth period for the second UE, and the fourth period is an eDRX period used by the second UE when the RRC is in an inactive state.
  • the access network device can send the fourth period to the second UE through the fourth message, that is, configure the fourth period to the second UE, so that the second UE can use the fourth period to monitor after entering the RRC inactive state paging.
  • the time length of the fourth cycle is less than or equal to the time length of the second cycle.
  • the time length of the third cycle and the time length of the fourth cycle may be the same or different.
  • S65 For more content of S65, such as how the access network device determines the fourth period and what kind of message the fourth message can be implemented through, reference may be made to S45 in the embodiment shown in FIG. 4 .
  • the access network device may also configure eDRX cycles for the other UEs respectively, and the configuration methods are similar, and will not be repeated here.
  • the access network device sends an RRC inactive state transition report to the core network device, and correspondingly, the core network device receives the RRC inactive state transition report from the access network device.
  • the RRC inactive state transition report may indicate that the first UE has entered the RRC inactive state.
  • different UEs may enter the RRC inactive state at the same time or at different times, and the embodiments of the present application only take the first UE entering the RRC inactive state as an example for description.
  • S66 may occur before S65, or S66 may occur simultaneously with S65, or S66 may occur after S65.
  • the core network device sends the NAS message to the first UE according to the second cycle, and correspondingly, the first UE monitors the paging according to the third cycle, thereby receiving the NAS message.
  • the core network device sends the NAS message according to the second period when sending the NAS message to the UE, so that the core network device does not need to maintain different lengths for different UEs.
  • the eDRX cycle can simplify the implementation of core network equipment.
  • the third period is configured by the access network equipment according to the second period and the service requirements of the first UE. Then, since the time length of the third period is less than or equal to the time length of the second period, if the core network equipment according to the second period After sending the NAS message, the first UE can monitor the paging from the access network device in the third period, so that the NAS message can be received correctly, and the receiving requirement of the NAS message can be met. In addition, since the third period is related to the service requirements of the first UE, the first UE monitors the paging according to the third period, which can also meet the service transmission requirements of the first UE.
  • the second UE will also use the RRC connection release message to release the second UE to the RRC inactive state.
  • the access network device will also send an RRC inactive state transition report corresponding to the second UE to the core network device, indicating that the second UE has entered the RRC inactive state. If the core network device needs to send the NAS message to the second UE in the RRC inactive state, it will send the NAS message according to the second cycle, and the second UE will monitor the paging according to the fourth cycle. Because the process is similar, it will not be repeated here.
  • both S66 and S67 are optional steps, and are not required to be performed.
  • the core network device first notifies the access network device of the upper limit value acceptable to the core network device, so that when the access network device configures the eDRX cycle used in the RRC inactive state for multiple UEs It can be more accurate, and the process of re-determining the eDRX cycles configured for multiple UEs by the access network device is reduced.
  • the access network device will also notify the core network device of the second cycle that is finally determined, so that if the core network device wants to send a NAS message to any one of the multiple UEs, it can send it according to the second cycle, so that these multiple
  • the UE can normally receive the NAS message from the core network device, no matter whether the second period is greater than 10.24s or less than 10.24s, the method of the embodiment of the present application can improve the probability of the UE receiving the NAS message and reduce the loss of the NAS message. package rate.
  • the core network device also does not need to page the first UE because the NAS message fails to be sent, and the first UE does not need to enter the RRC idle state and then initiate random access, which reduces service transmission delay and saves transmission resources.
  • the core network device can send the NAS message according to the second cycle, and there is no need to maintain different eDRX cycles for different UEs, which simplifies the implementation process of the core network device.
  • Embodiments of the present application provide a fourth communication method. Please refer to FIG. 7 , which is a flowchart of the method.
  • the core network device sends the first message to the access network device, and correspondingly, the access network device receives the first message from the core network device.
  • the first message includes the first period.
  • the first cycle is the maximum eDRX cycle determined by the core network device for the multiple UEs, and the first cycle is the eDRX cycle used by the multiple UEs when they are in the RRC inactive state. It can be understood that the eDRX cycles configured by the final access network device for the multiple UEs may be the same or different, but all need to be less than or equal to the first cycle.
  • the access network device determines a second period for the first UE according to the first period.
  • the access network device may determine the eDRX cycle used in the RRC inactive state for different UEs according to the first cycle.
  • the access network device may, according to the first cycle and some other factors, separately configure eDRX cycles used in the RRC inactive state for different UEs among the multiple UEs.
  • the eDRX cycles configured by the access network device for different UEs among the multiple UEs and used in the RRC inactive state may have the same time length or different time lengths.
  • the access network device may determine the eDRX cycle used by the UE in the RRC inactive state according to the first cycle, and the determination method is relatively simple; A cycle and the service of the UE determine the eDRX cycle used by the UE in the RRC inactive state, so that the configured eDRX cycle can meet the requirements of the UE for receiving NAS messages and the service transmission requirements of the UE; or , the access network device can determine the eDRX cycle used by the UE in the RRC inactive state according to the first cycle and the capability of the UE, so that the determined eDRX cycle can not only meet the needs of multiple UEs to receive NAS messages, but also meet the The actual capability of the UE; alternatively, the access network device may also determine the eDRX cycle used by the UE in the RRC inactive state according to the first cycle, the service requirements of the UE, and the capability of the UE, and so on.
  • the first UE is one of multiple UEs.
  • the access network device configures a second period for the first UE according to one of the above configuration methods, and the second period is used when the first UE is in the RRC inactive state. eDRX cycle.
  • the access network device sends the second message to the first UE, and correspondingly, the first UE receives the second message from the access network device.
  • the second message includes the second period.
  • the access network device can send the second cycle to the first UE through the second message, that is, configure the second cycle to the first UE, so that the first UE can use the second cycle to monitor after entering the RRC inactive state paging.
  • the time length of the second cycle is less than or equal to the time length of the first cycle.
  • S73 For more content of S73, for example, what kind of message the second message can be implemented through, etc., reference may be made to S45 in the embodiment shown in FIG. 4 .
  • the access network device determines a third period for the second UE according to the first period.
  • the second UE is one of multiple UEs.
  • the access network device configures a third period for the second UE according to one of the above configuration methods, and the third period is used when the second UE is in the RRC inactive state. eDRX cycle.
  • S74 For more content of S74, such as how the access network device determines the third period, etc., please refer to the introduction of S72.
  • the access network device sends a third message to the second UE, and correspondingly, the second UE receives the third message from the access network device.
  • the third message includes the third period.
  • the access network device can send the third period to the second UE through the third message, that is, configure the third period to the second UE, so that the second UE can use the third period to monitor after entering the RRC inactive state paging.
  • the time length of the third cycle is less than or equal to the time length of the first cycle.
  • S75 For more content of S75, such as what kind of message the third message can be implemented through, etc., reference may be made to S45 in the embodiment shown in FIG. 4 .
  • the access network device may also configure eDRX cycles for the other UEs respectively, and the configuration methods are similar, and will not be repeated here.
  • the access network device sends an RRC inactive state transition report to the core network device, and correspondingly, the core network device receives the RRC inactive state transition report from the access network device.
  • the RRC inactive state transition report may indicate that the first UE has entered the RRC inactive state.
  • different UEs may enter the RRC inactive state at the same time or at different times.
  • the embodiments of the present application only take the first UE entering the RRC inactive state as an example for description.
  • the core network device sends the NAS message to the first UE according to the first period, and correspondingly, the first UE monitors the paging according to the second period, so as to receive the NAS message.
  • the core network device sends the NAS message according to the first cycle when sending the NAS message to the UE, so that the core network device does not need to maintain different eDRX for different UEs.
  • the eDRX cycle can simplify the implementation of core network equipment.
  • the second period is configured by the access network equipment according to the first period and the service requirements of the first UE. Then, since the time length of the second period is less than or equal to the time length of the first period, if the core network equipment follows the first period After sending the NAS message, the first UE can monitor the paging from the access network device in the second period, so that the NAS message can be received correctly, and the receiving requirement of the NAS message can be met. In addition, since the second period is related to the service requirements of the first UE, the first UE monitors the paging according to the second period, which can also meet the service transmission requirements of the first UE.
  • the second UE will also use the RRC connection release message to release the second UE to the RRC inactive state.
  • the access network device will also send an RRC inactive state transition report corresponding to the second UE to the core network device, indicating that the second UE has entered the RRC inactive state.
  • the core network device needs to send the NAS message to the second UE in the RRC inactive state, it will also send the NAS message according to the first cycle, and the second UE will monitor the paging according to the third cycle. Because the process is similar, it will not be repeated here.
  • both S76 and S77 are optional steps, and are not required to be performed.
  • the core network device notifies the access network device of the upper limit value acceptable to the core network device, and the access network device can configure the eDRX cycle for different UEs according to the upper limit value, so that the access network device When configuring the eDRX cycles used in the RRC inactive state for multiple UEs, it can be more accurate, which reduces the process of the access network device re-determining the eDRX cycles configured for multiple UEs. If the core network device wants to send a NAS message to any one of the multiple UEs, it can send it according to the first cycle, so that these multiple UEs can normally receive the NAS message from the core network device, regardless of whether the first cycle is greater than or equal to the first cycle.
  • 10.24s is still less than 10.24s.
  • the core network device also does not need to page the first UE because the NAS message fails to be sent, and the first UE does not need to enter the RRC idle state and then initiate random access, which reduces service transmission delay and saves transmission resources.
  • the core network device can send the NAS message according to the second cycle, and there is no need to maintain different eDRX cycles for different UEs, which simplifies the implementation process of the core network device.
  • FIG. 8 is a schematic block diagram of a communication apparatus 800 according to an embodiment of the present application.
  • the communication apparatus 800 is, for example, a terminal device or a network device.
  • the communication apparatus 800 can implement the functions of the first terminal device described in the embodiment shown in FIG. 4 , the embodiment shown in FIG. 5 , the embodiment shown in FIG. 6 , or the embodiment shown in FIG. 7 .
  • the communication apparatus 800 can implement the functions of the access network device described in the embodiment shown in FIG. 4 , the embodiment shown in FIG. 5 , the embodiment shown in FIG. 6 , or the embodiment shown in FIG. 7 .
  • the communication apparatus 800 can implement the functions of the core network device described in the embodiment shown in FIG. 4 , the embodiment shown in FIG. 5 , the embodiment shown in FIG. 6 , or the embodiment shown in FIG. 7 .
  • the communication device 800 includes a transceiving unit 820 and a processing unit 810 .
  • the communication apparatus 800 may further include a storage unit, and the storage unit can communicate with the processing unit 810, which is not shown in FIG. 7 .
  • the communication apparatus 800 may not include the storage unit, and the storage unit may also be located outside the communication apparatus 800 .
  • the communication apparatus 800 may be the first terminal equipment, or may be a chip applied in the first terminal equipment or other combined devices, components, etc. having the functions of the above-mentioned first terminal equipment, or the communication apparatus 800 may be a network
  • the device eg, access network device or core network device
  • the processing unit 810 may include a processor, such as a baseband processor, and the baseband processor may include one or more central processing units (CPUs); a transceiver unit 820 may be a transceiver, and the transceiver may include an antenna, a radio frequency circuit, and the like.
  • the transceiver may include a transmitter and a receiver, and the transceiver may implement the functions of the transmitter and the receiver, or the transmitter and the receiver may also be two function modules deployed separately, but the embodiment of the present application uses these two functions.
  • transceivers When the communication apparatus 800 is a component having the function of the above-mentioned first terminal device or network device, the transceiver unit 820 may be a radio frequency unit, and the processing unit 810 may be a processor, such as a baseband processor. When the communication device 800 is a chip system, the transceiver unit 820 may be an input/output interface of a chip (eg, a baseband chip), and the processing unit 810 may be a processor of the chip system, which may include one or more central processing units.
  • a chip eg., a baseband chip
  • the processing unit 810 may be a processor of the chip system, which may include one or more central processing units.
  • processing unit 810 in this embodiment of the present application may be implemented by a processor or a circuit component related to the processor, and the transceiver unit 820 may be implemented by a transceiver or a circuit component related to the transceiver.
  • the processing unit 810 may be used to execute the first terminal device in the embodiment shown in FIG. 4 All operations performed by a terminal device other than transceiving operations, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all receive operations and transmit operations performed by the first terminal device in the embodiment shown in FIG. 4 , such as S45 and S47 , and/or other processes for supporting the techniques described herein.
  • the communication apparatus 800 when used to implement the function of the access network device described in the embodiment shown in FIG. All operations performed by the network device except for transceiving operations, eg, S42, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all reception operations and transmission operations performed by the access network device in the embodiment shown in FIG. 4, such as S41 and S43-S47, and/or other operations used to support the techniques described herein process.
  • the processing unit 810 may be used to execute the core network device in the embodiment shown in FIG. 4 All operations performed other than transceiving operations, such as determining the second cycle, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be used to perform all receiving operations and sending operations performed by the core network equipment in the embodiment shown in FIG. other processes of technology.
  • the processing unit 810 may be used to execute the first terminal device in the embodiment shown in FIG. All operations performed by a terminal device other than transceiving operations, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all receive operations and transmit operations performed by the first terminal device in the embodiment shown in FIG. 5 , such as S54 and S56 , and/or other processes for supporting the techniques described herein.
  • the communication apparatus 800 when used to implement the function of the access network device described in the embodiment shown in FIG. All operations performed by the network device except transceiving operations, eg, S52, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all reception operations and transmission operations performed by the access network device in the embodiment shown in FIG. 5, such as S51 and S53-S56, and/or other operations used to support the techniques described herein process.
  • the processing unit 810 may be used to execute the core network device in the embodiment shown in FIG. 5 All operations performed other than transceiving operations, such as determining the first cycle, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all receive operations and transmit operations performed by the core network equipment in the embodiment shown in FIG. other processes.
  • the processing unit 810 may be used to execute the first terminal device in the embodiment shown in FIG. 6 All operations performed by a terminal device other than transceiving operations, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all receive operations and transmit operations performed by the first terminal device in the embodiment shown in FIG. 6 , such as S64 and S67 , and/or other processes for supporting the techniques described herein.
  • the communication apparatus 800 when used to implement the function of the access network device described in the embodiment shown in FIG. All operations performed by the network device except for transceiving operations, eg, S62, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all receiving operations and sending operations performed by the access network device in the embodiment shown in FIG. 6, such as S61 and S63-S67, and/or other operations used to support the techniques described herein process.
  • the processing unit 810 may be used to execute the core network equipment in the embodiment shown in FIG. 6 All operations performed other than transceiving operations, such as determining the first cycle, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all receiving operations and sending operations performed by the core network device in the embodiment shown in FIG. 6, such as S61, S63, S66 and S67, and/or for supporting the techniques described herein other processes.
  • the processing unit 810 may be used to execute the first terminal device in the embodiment shown in FIG. 7 All operations performed by a terminal device other than transceiving operations, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all receive operations and transmit operations performed by the first terminal device in the embodiment shown in FIG. 7 , such as S73 and S77 , and/or other processes for supporting the techniques described herein.
  • the communication apparatus 800 when used to implement the function of the access network device described in the embodiment shown in FIG. All operations performed by the network device except transceiving operations, eg, S72 and S74, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all receiving operations and sending operations performed by the access network device in the embodiment shown in FIG. 7, such as S71, S73, and S75-S77, and/or to support the techniques described herein other processes.
  • the processing unit 810 may be used to execute the core network equipment in the embodiment shown in FIG. 7 All operations performed other than transceiving operations, such as determining the first cycle, and/or other processes used to support the techniques described herein.
  • the transceiver unit 820 may be configured to perform all receive operations and transmit operations performed by the core network device in the embodiment shown in FIG. 7, such as S71, S76, and S77, and/or other processes used to support the techniques described herein .
  • the transceiver unit 820 may be a functional module, which can perform both sending and receiving operations.
  • the transceiver unit 820 may be used to execute the embodiment shown in FIG. 4 or the embodiment or diagram shown in FIG. 5 . All sending operations and receiving operations performed by the first terminal device or network device (eg, core network device or access network device) in the embodiment shown in 6 or the embodiment shown in FIG. 7 .
  • the transceiving unit 820 when performing a receiving operation, can be considered as a receiving unit, and when performing a transmitting operation, the transceiving unit 820 can be considered as a transmitting unit.
  • the transceiver unit 820 may also be two functional modules, and the transceiver unit 820 may be regarded as a general term for the two functional modules.
  • the two functional modules include a receiving unit and a sending unit.
  • the sending unit is used to complete the sending operation, for example, the sending unit It can be used to perform all sending operations performed by the first terminal device or the network device in the embodiment shown in FIG. 4 or the embodiment shown in FIG. 5 or the embodiment shown in FIG. 6 or the embodiment shown in FIG. 7 ;
  • the receiving unit is used to complete the receiving operation, for example, the receiving unit may be used to execute the embodiment shown in FIG. 4 or the embodiment shown in FIG. 5 or the embodiment shown in FIG. 6 or the embodiment shown in FIG. All receive operations performed by a terminal device or network device.
  • processing unit 810 and the transceiver unit 820 can implement, refer to the embodiment shown in FIG. 4 or the embodiment shown in FIG. 5 or the embodiment shown in FIG. 6 or the embodiment shown in FIG.
  • the processing unit 810 and the transceiver unit 820 can implement, refer to the embodiment shown in FIG. 4 or the embodiment shown in FIG. 5 or the embodiment shown in FIG. 6 or the embodiment shown in FIG.
  • the terminal device or referring to the embodiment shown in FIG. 4 or the embodiment shown in FIG. 5 or the embodiment shown in FIG. 6 or the embodiment shown in FIG.
  • the introduction of the operations performed by the network access device or core network device will not be repeated here.
  • An embodiment of the present application further provides a communication apparatus, where the communication apparatus may be a terminal device or a circuit.
  • the communication apparatus may be configured to perform the actions performed by the terminal device in each of the foregoing method embodiments.
  • FIG. 9 shows a schematic structural diagram of a simplified terminal device.
  • the terminal device takes a mobile phone as an example.
  • the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input and output device.
  • the processor is mainly used to process communication protocols and communication data, control terminal equipment, execute software programs, and process data of software programs.
  • the memory is mainly used to store software programs and data.
  • the radio frequency circuit is mainly used for the conversion of the baseband signal and the radio frequency signal and the processing of the radio frequency signal.
  • Antennas are 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 data input by users and output data to users. It should be noted that some types of terminal equipment may not have input and output devices.
  • the processor When data needs to be sent, 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 performs radio frequency processing on the baseband signal and sends the radio frequency signal through the antenna in the form of electromagnetic waves.
  • 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, which converts the baseband signal into data and processes the data.
  • FIG. 9 only one memory and processor are shown in FIG. 9 . In an actual end device product, there may be one or more processors and one or more memories.
  • the memory may also be referred to as a storage medium or a storage device or the like.
  • the memory may be set independently of the processor, or may be integrated with the processor, which is not limited in this embodiment of the present application.
  • the antenna and the radio frequency circuit with the transceiver function may be regarded as the transceiver unit of the terminal device (the transceiver unit may be a functional unit, and the function unit can realize the sending function and the receiving function; alternatively, the transceiver unit may also be It includes two functional units, namely a receiving unit capable of realizing a receiving function and a transmitting unit capable of realizing a transmitting function), and a processor with a processing function is regarded as a processing unit of the terminal device. As shown in FIG. 9 , the terminal device includes a transceiver unit 910 and a processing unit 920 .
  • the transceiving unit may also be referred to as a transceiver, a transceiver, a transceiving device, or the like.
  • the processing unit may also be referred to as a processor, a processing single board, a processing module, a processing device, and the like.
  • the device used for implementing the receiving function in the transceiver unit 910 may be regarded as a receiving unit, and the device used for implementing the transmitting function in the transceiver unit 910 may be regarded as a sending unit, that is, the transceiver unit 910 includes a receiving unit and a sending unit.
  • the transceiver unit may also sometimes be referred to as a transceiver, a transceiver, or a transceiver circuit.
  • the receiving unit may also sometimes be referred to as a receiver, receiver, or receiving circuit, or the like.
  • the transmitting unit may also sometimes be referred to as a transmitter, a transmitter, or a transmitting circuit, or the like.
  • the transceiver unit 910 is configured to perform the sending operation and receiving on the terminal device side in the embodiment shown in FIG. 4 or the embodiment shown in FIG. 5 or the embodiment shown in FIG. 6 or the embodiment shown in FIG. 7 .
  • the processing unit 920 is configured to perform the above-mentioned embodiment shown in FIG. 4 or the embodiment shown in FIG. 5 or the embodiment shown in FIG. 6 or the embodiment shown in FIG. other operations.
  • the device may include a transceiver unit and a processing unit.
  • the transceiver unit may be an input/output circuit and/or a communication interface;
  • the processing unit may be an integrated processor, a microprocessor or an integrated circuit.
  • processors mentioned in the embodiments of the present application may be a CPU, and may also be other general-purpose processors, digital signal processors (digital signal processors, DSPs), application specific integrated circuits (application specific integrated circuits, ASICs), ready-made Field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGA Field programmable gate array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module
  • memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned computer-readable storage medium can be any available medium that can be accessed by a computer.
  • the computer-readable medium may include random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), Erasable programmable read only memory (erasable PROM, EPROM), electrically erasable programmable read only memory (electrically erasable programmable read only memory, EEPROM), compact disc read-only memory (compact disc read-only memory, CD- ROM), universal serial bus flash disk, removable hard disk, or other optical disk storage, magnetic disk storage medium, or other magnetic storage device, or capable of carrying or storing desired data in the form of instructions or data structures program code and any other medium that can be accessed by a computer.
  • RAM random access memory
  • ROM read-only memory
  • PROM programmable read-only memory
  • EPROM Erasable programmable read only memory
  • EEPROM electrically erasable programmable read only memory
  • compact disc read-only memory compact disc read-only memory
  • CD- ROM compact disc read-only memory
  • universal serial bus flash disk removable hard disk,
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM

Landscapes

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

Abstract

本申请涉及一种通信方法及设备。接入网设备接收来自核心网设备的第一周期，第一周期是能够为第一终端设备配置的最大eDRX周期，且第一周期是第一终端设备在处于RRC非激活态时使用的。所述接入网设备根据第一周期确定第二周期，第二周期是为第一终端设备配置的eDRX周期，且第二周期是第一终端设备在处于RRC非激活态时使用的，第二周期的长度小于或等于第一周期的长度。接入网设备向核心网设备发送第二消息，第二消息包括第二周期。接入网设备根据第一周期确定的第二周期符合核心网设备的要求，核心网设备按照第二周期发送NAS消息，第一终端设备按照第二周期能正常接收NAS消息，提高了终端设备接收NAS消息的概率。

Description

一种通信方法及设备
相关申请的交叉引用
本申请要求在2020年10月09日提交中国国家知识产权局、申请号为202011075522.X、申请名称为“一种UE2NW relay的通信方法方法、UE及网络设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中；本申请要求在2020年10月23日提交中国国家知识产权局、申请号为202011148865.4、申请名称为“一种通信方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及设备。
背景技术
非连续接收(discontinuous reception，DRX)机制通过不连续地接收信号，使得用户设备(user equipment，UE)能够大部分时间处于休眠状态，来达到省电的目的。因为基于包的数据流一般都是突发性的，在没有数据传输的时候，就可以通过关闭UE的接收电路来降低功耗。扩展的非连续接收(extended discontinuous reception，eDRX)是扩展的DRX，在每个eDRX周期里，UE只在设置的寻呼时间窗口(paging time window，PTW)可以接收下行数据，在PTW外的其余时间，UE处于休眠状态。
当前规定，只有增强机器类型通信(enhanced machine type communication，eMTC)的UE，在处于无线资源控制(radio resource control，RRC)非激活(inactive)态时能够使用eDRX机制，而其他的UE，例如长期演进(long term evolution，LTE)UE或新无线(new radio，NR)UE等，在处于RRC非激活态时都不能使用eDRX机制。另外窄带物联网(narrowband internet of things，NB-IoT)UE没有RRC非激活态，因此也谈不上在处于RRC非激活态时都不能使用eDRX机制。
目前又提出了能力缩减UE(reduced capability UE，redcap UE)，是相对于传统(legacy)UE来说能力较低的一类UE。redcap UE属于NR UE，但为了redcap UE的节能，目前讨论，可以使得redcap UE在RRC非激活态时也使用eDRX机制。
对于eMTC UE来说，在处于RRC非激活态时，当前规定的能够支持的最大eDRX周期长度为10.24秒(s)。如果redcap UE在RRC非激活态时也使用eDRX机制，则redcap UE能够支持的最大eDRX周期长度可能会大于10.24s。而如果基站为redcap UE配置的在RRC非激活态时使用的eDRX周期过长，则核心网设备如果向redcap UE发送非接入层(non-access stratum，NAS)消息，redcap UE就可能因为eDRX周期过长而导致无法接收到，这就是目前的一个需要解决的问题。
发明内容
本申请实施例提供一种通信方法及设备，用于提高UE成功接收NAS消息的概率。
第一方面，提供一种通信方法，该方法包括：在第一终端设备处于RRC空闲态的情 况下，若核心网设备获得了所述第一终端设备的下行数据，则所述核心网设备向接入网设备发送寻呼消息，所述寻呼消息用于寻呼所述第一终端设备，且所述寻呼消息还包括所述第一终端设备在处于RRC空闲态时使用的eDRX周期；所述接入网设备接收所述寻呼消息，根据所述寻呼消息中携带的所述第一终端设备在处于RRC空闲态时使用的eDRX周期确定第一周期，所述第一周期是期望为所述第一终端设备配置的eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；所述接入网设备向所述第一终端设备发送所述寻呼消息；所述第一终端设备接收所述寻呼消息，并基于所述寻呼消息与所述接入网设备建立RRC连接；在所述RRC连接建立成功之后，所述接入网设备向所述核心网设备发送初始UE消息，所述初始UE消息包括所述第一周期；所述核心网设备根据所述第一周期以及NAS定时信息确定第二周期，所述第二周期是所述核心网设备为所述第一终端设备确定的eDRX周期，且所述第二周期是所述第一终端设备在处于所述RRC非激活态时使用的；所述核心网设备向所述接入网设备发送初始上下文建立请求消息，所述初始上下文建立请求消息包括所述第二周期；在接入网设备未检测到UE的数据传输时，所述接入网设备启动RRC连接释放定时器；在所述RRC连接释放定时器超时时，所述接入网设备向所述第一终端设备发送RRC连接释放消息，所述RRC连接释放消息包括所述第二周期；在所述第一终端设备处于RRC非激活态的情况下，所述第一终端设备按照所述第二周期监听寻呼。
在本申请实施例中，接入网设备与核心网设备能够进行协商，以确定第二周期，第二周期就是能够配置给第一终端设备在RRC非激活态下使用的eDRX周期。通过这样的方式，可以基于接入网设备和核心网设备的自身情况给出较为合理的eDRX周期，从而核心网设备如果要向第一终端设备发送NAS消息，可以按照第二周期来发送，这样，无论第二周期是小于或等于10.24s还是大于10.24s，都能使得第一终端设备按照第二周期正常接收来自核心网设备的NAS消息，提高了终端设备接收NAS消息的概率，减小了NAS消息的丢包率，也相应减小了NAS消息的传输时延。
第二方面，提供第二种通信方法，该方法可由接入网设备执行，或由芯片系统执行，该芯片系统能够实现接入网设备的功能。示例性地，接入网设备为基站。该方法包括：接入网设备向核心网设备发送第一消息，所述第一消息包括第一周期，所述第一周期是期望为第一终端设备配置的eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；所述接入网设备接收来自所述核心网设备的第二消息，所述第二消息包括第二周期，所述第二周期是所述核心网设备为所述第一终端设备确定的eDRX周期，且所述第二周期是所述第一终端设备在处于所述RRC非激活态时使用的，所述第二周期的长度与所述第一周期相同或不同。
在本申请实施例中，接入网设备与核心网设备能够进行协商，以确定第二周期，第二周期就是能够配置给第一终端设备在RRC非激活态下使用的eDRX周期。通过这样的方式，可以基于接入网设备和核心网设备的自身情况给出较为合理的eDRX周期，从而核心网设备如果要向第一终端设备发送NAS消息，可以按照第二周期来发送，这样，无论第二周期是小于或等于10.24s还是大于10.24s，都能使得第一终端设备按照第二周期正常接收来自核心网设备的NAS消息，提高了终端设备接收NAS消息的概率，减小了NAS消息的丢包率，也相应减小了NAS消息的传输时延。
结合第二方面，在第二方面的第一种可选的实施方式中，在所述第一周期的长度小于 或等于第一阈值的情况下，所述第二周期的长度与所述第一周期的长度相同；或者，在所述第一周期的长度大于第一阈值的情况下，所述第二周期的长度小于所述第一周期的长度，以及所述第二周期的长度小于或等于所述第一阈值；其中，所述第一阈值是根据所述NAS定时信息确定的。
第一阈值是根据未调整的NAS定时信息确定的，或者是根据调整后的NAS定时信息确定的。核心网设备通过调整NAS定时信息，可以增大核心网设备能够接受的时间长度，使得为UE配置的eDRX周期的时间长度更长，配置更为灵活。可以认为，第一阈值是核心网设备所能接受的时间长度，如果超过第一阈值，则核心网设备不能接受。因此，根据第一阈值和第一周期，就能确定第二周期的长度，使得第二周期的长度能够在核心网设备的接受范围之内。
结合第二方面的第一种可选的实施方式，在第二方面的第二种可选的实施方式中，所述NAS定时信息包括NAS消息的最小重传时间间隔，和/或，NAS消息的最大重传次数。
例如，NAS定时信息包括NAS消息的最小重传时间间隔，或者，NAS定时信息包括NAS消息的最大重传次数，或者，NAS定时信息包括NAS消息的最小重传时间间隔和NAS消息的最大重传次数。
结合第二方面或第二方面的第一种可选的实施方式或第二方面的第二种可选的实施方式，在第二方面的第三种可选的实施方式中，所述第一消息为初始UE消息。
接入网设备可以通过初始UE消息将第一周期发送给核心网设备，例如，在初始UE消息中新增IE，第一周期可以通过该新增的IE承载。通过现有的消息将第一周期发送给接入网设备，无需额外增加其他的消息，能够节省信令开销。或者，接入网设备也可以通过其他消息将第一周期发送给核心网设备。
结合第二方面或第二方面的第一种可选的实施方式至第二方面的第三种可选的实施方式中的任一种可选的实施方式，在第二方面的第四种可选的实施方式中，所述第二消息为初始上下文建立请求消息。
核心网设备也可以通过现有的消息将第二周期发送给接入网设备，例如可通过初始上下文建立请求消息将第二周期发送给接入网设备。该初始上下文建立请求消息可以包括UE Radio Capability for Paging IE，在UE Radio Capability for Paging IE内还可以包括UE radio paging information。在UE radio paging information内包括一些空白字段，第二周期例如通过UE radio paging information包括的其中一个或多个空白字段承载，从而使得空白字段得到合理利用。
结合第二方面或第二方面的第一种可选的实施方式至第二方面的第四种可选的实施方式中的任一种可选的实施方式，在第二方面的第五种可选的实施方式中，所述方法还包括：所述接入网设备接收来自所述核心网设备的第一信息，所述第一信息包括所述第一终端设备在处于RRC空闲态时使用的eDRX周期；所述接入网设备根据所述第一终端设备在处于RRC空闲态时使用的eDRX周期确定所述第一周期。
核心网设备可以将第一终端设备在处于RRC空闲态时使用的eDRX周期发送给接入网设备，从而接入网设备可根据该eDRX周期确定第一周期。
结合第二方面的第五种可选的实施方式，在第二方面的第六种可选的实施方式中，所述第一信息包括在寻呼消息中。
核心网设备可通过寻呼消息将第一信息发送给接入网设备，该寻呼消息是核心网寻呼 消息，例如该寻呼消息用于寻呼第一终端设备。
结合第二方面或第二方面的第一种可选的实施方式至第二方面的第六种可选的实施方式中的任一种可选的实施方式，在第二方面的第七种可选的实施方式中，所述方法还包括：所述接入网设备向所述第一终端设备发送所述第三消息，所述第三消息包括所述第二周期。
接入网设备确定第二周期后，可以将第二周期配置给第一终端设备，使得第一终端设备在进入RRC非激活态后能够使用第二周期。
结合第二方面的第七种可选的实施方式，在第二方面的第八种可选的实施方式中，所述接入网设备向所述第一终端设备发送所述第二周期，包括：所述第三消息为RRC连接释放消息，所述RRC连接释放消息用于将所述第一终端设备释放到所述RRC非激活态。
RRC连接释放消息用于将第一终端设备释放到RRC非激活态，而第二周期也是第一终端设备在处于RRC非激活态时使用的，因此通过RRC连接释放消息将第二周期发送给第一终端设备，可以使得第二周期能够得到较为及时地应用。而且RRC连接释放消息既可以将第一终端设备释放到RRC非激活态，也可以为第一终端设备配置第二周期，提高了消息的利用率，且因为无需发送额外的消息来为第一终端设备配置第二周期，也减少了传输开销。
结合第二方面或第二方面的第一种可选的实施方式至第二方面的第八种可选的实施方式中的任一种可选的实施方式，在第二方面的第九种可选的实施方式中，所述第一终端设备为redcap UE。
第一终端设备可以是该接入网设备服务的任一个终端设备，例如第一终端设备为redcap UE。对于除第一终端设备外的其他的redcap UE，如果在处于RRC非激活态时能够支持的eDRX周期大于10.24s，则也都可以适用本申请实施例的技术方案。即，通过本申请实施例的技术方案，可以为不同的redcap UE分别配置合适的eDRX周期，使得所配置的eDRX既满足终端设备接收NAS消息的需求，也更为符合终端设备的实际业务需求。
第三方面，提供第三种通信方法。该方法可由核心网设备执行，或由芯片系统执行，该芯片系统能够实现核心网设备的功能。示例性地，核心网设备为AMF。该方法包括：核心网设备接收来自接入网设备的第一消息，所述第一消息包括第一周期，所述第一周期是所述接入网设备期望为第一终端设备配置的eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；所述核心网设备向所述接入网设备发送第二消息，所述第二消息包括第二周期，所述第一周期是所述接入网设备期望为第一终端设备配置的eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的，其中，所述第二周期是根据所述第一周期和NAS定时信息确定的，所述第二周期的长度与所述第一周期相同或不同。
结合第三方面，在第三方面的第一种可选的实施方式中，所述第二周期是根据所述第一周期和NAS定时信息确定的，包括：在所述第一周期的长度小于或等于第一阈值的情况下，所述第二周期的长度与所述第一周期的长度相同；或者，在所述第一周期的长度大于第一阈值的情况下，所述第二周期的长度小于所述第一周期的长度，以及所述第二周期的长度小于或等于所述第一阈值；其中，所述第一阈值是根据所述NAS定时信息确定的。
结合第三方面的第一种可选的实施方式，在第三方面的第二种可选的实施方式中，所述NAS定时信息包括NAS消息的最小重传时间间隔，和/或，NAS消息的最大重传次数。
结合第三方面或第三方面的第一种可选的实施方式或第三方面的第二种可选的实施方式，在第三方面的第三种可选的实施方式中，所述第一消息为初始UE消息。
结合第三方面或第三方面的第一种可选的实施方式至第三方面的第三种可选的实施方式中的任一种可选的实施方式，在第三方面的第四种可选的实施方式中，所述第二消息为初始上下文建立请求消息。
结合第三方面或第三方面的第一种可选的实施方式或第三方面的第四种可选的实施方式，在第三方面的第五种可选的实施方式中，所述方法还包括：所述核心网设备向所述接入网设备发送第一信息，所述第一信息用于确定所述第一周期，其中，所述第一信息包括所述第一终端设备在处于RRC空闲态时使用的eDRX周期。
结合第三方面的第五种可选的实施方式，在第三方面的第六种可选的实施方式中，所述第一信息包括在寻呼消息中。
结合第三方面或第三方面的第一种可选的实施方式至第三方面的第六种可选的实施方式中的任一种可选的实施方式，在第三方面的第七种可选的实施方式中，所述方法还包括：所述核心网设备接收来自所述接入网设备的RRC非激活态转换报告，所述RRC非激活态转换报告用于指示所述第一终端设备进入所述RRC非激活态；所述核心网设备按照所述第二周期向所述第一终端设备发送NAS消息。
结合第三方面或第三方面的第一种可选的实施方式至第三方面的第七种可选的实施方式中的任一种可选的实施方式，在第三方面的第八种可选的实施方式中，所述第一终端设备为redcap UE。
关于第三方面或第三方面的各种可选的实施方式所带来的技术效果，可参考对于第二方面或相应的实施方式的技术效果的介绍。
第四方面，提供第四种通信方法，该方法可由第一终端设备执行，或者由芯片系统执行，该芯片系统能够实现第一终端设备的功能。该方法包括：第一终端设备接收来自接入网设备的第三消息，所述第三消息包括第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于RRC非激活态时使用的，其中，其中，所述第二周期是所述接入网设备与核心网设备通过协商确定的；在所述第一终端设备处于RRC非激活态的情况下，所述第一终端设备按照所述第二周期监听寻呼。
结合第四方面，在第四方面的第一种可选的实施方式中，所述第二消息为RRC连接释放消息，所述RRC连接释放消息用于将所述第一终端设备释放到所述RRC非激活态。
结合第四方面或第四方面的第一种可选的实施方式，在第四方面的第二种可选的实施方式中，所述第一终端设备为redcap UE。
关于第四方面或第四方面的各种可选的实施方式所带来的技术效果，可参考对于第二方面或相应的实施方式的技术效果的介绍，或者可参考对于第三方面或相应的实施方式的技术效果的介绍。
第五方面，提供第五种通信方法，该方法包括：核心网设备根据NAS定时信息确定第一周期，所述第一周期是能够为第一终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；在第一终端设备的注册过程中，核心网设备向接入网设备发送初始上下文建立请求消息，所述初始上下文建立请求消息包括所述第一终端设备的上下文信息，以及，所述初始上下文请求消息还包括所述第一周期；所述接入网设备接收所述初始上下文建立请求消息，根据所述初始上下文建立请求消息携 带的所述第一周期确定第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；所述接入网设备向所述核心网设备发送初始上下文建立响应消息，所述初始上下文建立响应消息包括所述第二周期；在所述第一终端设备注册完毕，且所述接入网设备未检测到所述第一终端设备的数据传输时，所述接入网设备启动RRC连接释放定时器；在所述RRC连接释放定时器超时时，所述接入网设备向所述第一终端设备发送RRC连接释放消息，所述RRC连接释放消息包括所述第二周期；在所述第一终端设备处于RRC非激活态的情况下，所述第一终端设备按照所述第二周期监听寻呼。
在本申请实施例中，核心网设备先将核心网设备所能接受的上限值通知接入网设备，从而接入网设备在为第一终端设备配置在RRC非激活态下使用的eDRX周期时可以更为准确，减少了接入网设备重新确定为第一终端设备配置的eDRX周期的过程。接入网设备也会将最终确定的第二周期告知核心网设备，从而核心网设备如果要向第一终端设备发送NAS消息，可以按照第二周期来发送，使得第一终端设备按照第二周期能够正常接收来自核心网设备的NAS消息，无论第二周期是大于10.24s还是小于10.24s，通过本申请实施例的方法，都能提高终端设备接收NAS消息的概率，减小NAS消息的丢包率。而且核心网设备也不必因为NAS消息发送失败而寻呼第一终端设备，第一终端设备也不必进入RRC空闲态后再发起随机接入，减小了业务传输时延，也节省了传输资源。而且在本申请实施例中，核心网设备可以在确定第一周期时刻将NAS定时信息作为考虑因素，而不必考虑第一终端设备在RRC空闲态下使用的eDRX周期，对于第一周期的确定方式更为灵活，可以使得所确定的第一周期更长，且也符合核心网设备的要求。
第六方面，提供第六种通信方法，该方法可由接入网设备执行，或由芯片系统执行，该芯片系统能够实现接入网设备的功能。示例性地，接入网设备为基站。该方法包括：接入网设备接收来自核心网设备的第一消息，所述第一消息包括第一周期，所述第一周期是能够为第一终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；所述接入网设备根据所述第一周期确定第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；所述接入网设备向所述核心网设备发送第二消息，所述第二消息包括所述第二周期。
在本申请实施例中，核心网设备先将核心网设备所能接受的上限值通知接入网设备，从而接入网设备在为第一终端设备配置在RRC非激活态下使用的eDRX周期时可以更为准确，减少了接入网设备重新确定为第一终端设备配置的eDRX周期的过程。接入网设备也会将最终确定的第二周期告知核心网设备，从而核心网设备如果要向第一终端设备发送NAS消息，可以按照第二周期来发送，使得第一终端设备按照第二周期能够正常接收来自核心网设备的NAS消息，无论第二周期是大于10.24s还是小于10.24s，通过本申请实施例的方法，都能提高终端设备接收NAS消息的概率，减小NAS消息的丢包率。而且核心网设备也不必因为NAS消息发送失败而寻呼第一终端设备，第一终端设备也不必进入RRC空闲态后再发起随机接入，减小了业务传输时延，也节省了传输资源。而且在本申请实施例中，核心网设备可以在确定第一周期时刻将NAS定时信息作为考虑因素，而不必考虑第一终端设备在RRC空闲态下使用的eDRX周期，对于第一周期的确定方式更为灵活，可以使得所确定的第一周期更长，且也符合核心网设备的要求。
结合第六方面，在第六方面的第一种可选的实施方式中，
所述第一消息为初始上下文建立请求消息；和/或，
所述第二消息为初始上下文建立响应消息，或，所述第二消息为RRC非激活态转换报告。
核心网设备向接入网设备发送第一周期，接入网设备向核心网设备发送第二周期，都可以通过现有的消息发送，无需增加其他消息，使得本申请实施例的技术方案能够更好地与现有的技术兼容。或者，第一周期或第二周期也可以通过其他消息发送，例如可通过新增的专用消息发送，以减小对现有消息的功能的影响。
结合第六方面或第六方面的第一种可选的实施方式，在第六方面的第二种可选的实施方式中，所述方法还包括：所述接入网设备向所述第一终端设备发送第三消息，所述第三消息包括所述第二周期。
接入网设备确定第二周期后，可以将第二周期配置给第一终端设备，使得第一终端设备在进入RRC非激活态后能够使用第二周期。
结合第六方面的第二种可选的实施方式，在第二方面的第三种可选的实施方式中，所述第三消息为RRC连接释放消息，所述RRC连接释放消息用于将所述第一终端设备释放到所述RRC非激活态。
RRC连接释放消息用于将第一终端设备释放到RRC非激活态，而第二周期也是第一终端设备在处于RRC非激活态时使用的，因此通过RRC连接释放消息将第二周期发送给第一终端设备，可以使得第二周期能够得到较为及时地应用。而且RRC连接释放消息既可以将第一终端设备释放到RRC非激活态，也可以为第一终端设备配置第二周期，提高了消息的利用率，且因为无需发送额外的消息来为第一终端设备配置第二周期，也减少了传输开销。
结合第六方面或第六方面的第一种可选的实施方式至第六方面的第三种可选的实施方式中的任一种可选的实施方式，在第二方面的第四种可选的实施方式中，所述接入网设备根据所述第一周期为不同的终端设备配置的在处于所述RRC非激活态时使用的eDRX周期的长度不同。
例如，接入网设备可根据第一周期和第一UE的能力确定第二周期，使得第二周期能够符合第一UE的能力；或者，接入网设备可根据第一周期和第一UE的业务需求确定第二周期，使得第二周期能够符合第一UE的业务需求；或者，接入网设备可根据第一周期、第一UE的能力和第一UE的业务需求确定第二周期，等等，对于接入网设备用于确定第二周期的因素不做限制。鉴于接入网设备能够根据UE的实际情况(例如业务需求或能力等)为该UE配置eDRX周期，因此接入网设备为不同的UE所确定的在RRC非激活态下使用的eDRX周期可能相同，也可能不同。
结合第六方面或第六方面的第一种可选的实施方式至第六方面的第四种可选的实施方式中的任一种可选的实施方式，在第二方面的第五种可选的实施方式中，所述第一终端设备为redcap UE。
第一终端设备可以是该接入网设备服务的任一个终端设备，例如第一终端设备为redcap UE。对于除第一终端设备外的其他的redcap UE，如果在处于RRC非激活态时能够支持的eDRX周期大于10.24s，则也都可以适用本申请实施例的技术方案。即，通过本申请实施例的技术方案，可以为不同的redcap UE分别配置合适的eDRX周期，使得所配置 的eDRX既满足终端设备接收NAS消息的需求，也更为符合终端设备的实际业务需求。
第七方面，提供第七种通信方法，该方法可由核心网设备执行，或由芯片系统执行，该芯片系统能够实现核心网设备的功能。示例性地，核心网设备为AMF。该方法包括：核心网设备向接入网设备发送第一消息，所述第一消息包括第一周期，所述第一周期是能够为第一终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；所述核心网设备接收来自所述接入网设备的第二消息，所述第二消息包括第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于所述RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度。
结合第七方面，在第七方面的第一种可选的实施方式中，所述第一周期是根据NAS定时信息确定的，所述NAS定时信息包括NAS消息的最小重传时间间隔和/或NAS消息的最大重传次数。
例如，核心网设备可根据NAS定时信息确定第一周期，相较于根据第一终端设备在RRC空闲态下使用的eDRX周期来确定第一周期的方式来说，根据NAS定时信息确定第一周期，可以使得所确定的第一周期的时间长度更长，使得接入网设备在为第一终端设备进行配置时灵活度更高，而且第一周期也符合核心网设备的要求。另外可选的，核心网设备在确定第一周期时除了考虑NAS定时信息外，还可以考虑其他因素，例如核心网设备根据NAS定时信息和第一终端设备的业务需求确定第一周期，这样可以使得第一周期除了能满足第一终端设备接收NAS消息的需求外，还能满足第一终端设备的业务需求。
结合第七方面或第七方面的第一种可选的实施方式，在第七方面的第二种可选的实施方式中，
所述第一消息为初始上下文建立请求消息；和/或，
所述第二消息为初始上下文建立响应消息，或所述第二消息为RRC非激活态转换报告。
结合第七方面或第七方面的第一种可选的实施方式或第七方面的第二种可选的实施方式，在第七方面的第三种可选的实施方式中，所述方法还包括：所述核心网设备接收来自所述接入网设备的RRC非激活态转换报告，所述RRC非激活态转换报告用于指示所述第一终端设备进入所述RRC非激活态；所述核心网设备按照所述第二周期向所述第一终端设备发送NAS消息。
结合第七方面或第七方面的第一种可选的实施方式至第七方面的第三种可选的实施方式中的任一种可选的实施方式，在第七方面的第四种可选的实施方式中，所述第一终端设备为redcap UE。
关于第七方面或第七方面的各种可选的实施方式所带来的技术效果，可参考对于第六方面或相应的实施方式的技术效果的介绍。
第八方面，提供第八种通信方法，该方法可由第一终端设备执行，或者由芯片系统执行，该芯片系统能够实现第一终端设备的功能。该方法包括：第一终端设备接收来自接入网设备的第三消息，所述第三消息包括第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于RRC非激活态时使用的，其中，所述第二周期是所述接入网设备根据第一周期确定的，所述第一周期是所述核心网设备能够为所述第一终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设 备在处于RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；在所述第一终端设备处于RRC非激活态的情况下，所述第一终端设备按照所述第二周期监听寻呼。
结合第八方面，在第八方面的第一种可选的实施方式中，所述第二消息为RRC连接释放消息，所述RRC连接释放消息用于将所述第一终端设备释放到所述RRC非激活态。
结合第八方面或第八方面的第一种可选的实施方式，在第八方面的第二种可选的实施方式中，所述第一终端设备为redcap UE。
关于第八方面或第八方面的各种可选的实施方式所带来的技术效果，可参考对于第六方面或相应的实施方式的技术效果的介绍，或者可参考对于第七方面或相应的实施方式的技术效果的介绍。
第九方面，提供第九种通信方法，该方法可由接入网设备执行，或由芯片系统执行，该芯片系统能够实现接入网设备的功能。示例性地，接入网设备为基站。该方法包括：接入网设备接收来自核心网设备的第一消息，所述第一消息包括第一周期，所述第一周期是能够为终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；所述接入网设备根据所述第一周期确定第二周期，所述第二周期是为终端设备配置的最大eDRX周期，且所述第二周期是所述终端设备在处于所述RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；所述接入网设备向所述核心网设备发送第二消息，所述第二消息包括所述第二周期。
在本申请实施例中，核心网设备先将核心网设备所能接受的上限值通知接入网设备，从而接入网设备在为多个终端设备配置在RRC非激活态下使用的eDRX周期时可以更为准确，减少了接入网设备重新确定为多个终端设备配置的eDRX周期的过程。接入网设备也会将最终确定的第二周期告知核心网设备，从而核心网设备如果要向多个终端设备中的任一个终端设备发送NAS消息，都可以按照第二周期来发送，使得这多个终端设备都能正常接收来自核心网设备的NAS消息，无论第二周期是大于10.24s还是小于10.24s，通过本申请实施例的方法，都能提高终端设备接收NAS消息的概率，减小NAS消息的丢包率。核心网设备也不必因为NAS消息发送失败而寻呼终端设备，终端设备也不必进入RRC空闲态后再发起随机接入，减小了业务传输时延，也节省了传输资源。而且对于这多个终端设备中的任一个终端设备，核心网设备都可以按照第二周期发送NAS消息，无需为不同的终端设备维护不同的eDRX周期，简化了核心网设备的实现过程。
结合第九方面，在第九方面的第一种可选的实施方式中，所述第一消息为AMF配置更新消息，所述第二消息为AMF配置更新确认消息；或，所述第一消息为NG接口建立响应消息。
核心网设备向接入网设备发送第一周期，接入网设备向核心网设备发送第二周期，都可以通过现有的消息发送，无需增加其他消息，使得本申请实施例的技术方案能够更好地与现有的技术兼容。或者，第一周期或第二周期也可以通过其他消息发送，例如可通过新增的专用消息发送，以减小对现有消息的功能的影响。
结合第九方面或第九方面的第一种可选的实施方式，在第九方面的第二种可选的实施方式中，所述方法还包括：所述接入网设备向所述终端设备中的第一终端设备发送第三消息，所述第三消息包括第三周期，所述第三周期的长度小于或等于所述第二周期的长度，所述第三周期是为所述第一终端设备配置的eDRX周期，且所述第三周期是所述第一终端 设备在处于所述RRC非激活态时使用的；所述接入网设备向所述终端设备中的第二终端设备发送第四消息，所述第四消息包括第四周期，所述第四周期的长度小于或等于所述第二周期的长度，所述第四周期是为所述第二终端设备配置的eDRX周期，且所述第三周期是所述第一终端设备在处于所述RRC非激活态时使用的；其中，所述第三周期的长度与所述第四周期的长度相同或不同。
接入网设备确定的第二周期，是能够配置给多个终端设备的eDRX周期的上限值。进一步的，接入网设备可根据第二周期以及其他一些因素，为多个终端设备中的不同的终端设备分别配置用于在RRC非激活态时使用的eDRX周期。例如对于这多个终端设备中的一个终端设备来说，接入网设备可以根据第二周期确定该终端设备在RRC非激活态时使用的eDRX周期，确定方式较为简单；或者，接入网设备可根据第二周期以及该终端设备的业务确定该终端设备在RRC非激活态时使用的eDRX周期，从而使得所配置的eDRX周期既能满足该终端设备接收NAS消息的需求，也能满足该终端设备的业务传输需求，等等。由于不同的终端设备的情况(例如能力或业务需求等)有所不同，因此接入网设备为不同的终端设备所确定的在处于RRC非激活态时使用的eDRX周期可能相同，也可能不同。接入网设备可将为各个终端设备配置的在处于RRC非激活态时使用的eDRX周期发送给相应的终端设备，从而终端设备在处于RRC非激活态时能够使用接入网设备所配置的eDRX周期。
结合第九方面或第九方面的第一种可选的实施方式或第九方面的第二种可选的实施方式，在第九方面的第三种可选的实施方式中，所述接入网设备根据所述第一周期为不同的终端设备确定的所述第二周期的长度不同。
结合第九方面或第九方面的第一种可选的实施方式或第九方面的第二种可选的实施方式或第九方面的第三种可选的实施方式，在第九方面的第四种可选的实施方式中，所述终端设备为redcap UE。
通过本申请实施例的技术方案，可以为不同的redcap UE分别配置合适的eDRX周期，使得所配置的eDRX既满足终端设备接收NAS消息的需求，也更为符合终端设备的实际业务需求。
第十方面，提供第十种通信方法，该方法可由核心网设备执行，或由芯片系统执行，该芯片系统能够实现核心网设备的功能。示例性地，核心网设备为AMF。该方法包括：核心网设备向接入网设备发送第一消息，所述第一消息包括第一周期，所述第一周期是能够为终端设备配置的最大eDRX周期，且所述第一周期是所述终端设备在处于RRC非激活态时使用的；所述核心网设备接收来自所述接入网设备的第二消息，所述第二消息包括第二周期，所述第二周期是为终端设备配置的最大eDRX周期，且所述第二周期是所述终端设备在处于所述RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度。
结合第十方面，在第十方面的第一种可选的实施方式中，所述第一周期是根据NAS定时信息确定的，所述NAS定时信息包括NAS消息的最小重传时间间隔和/或NAS消息的最大重传次数。
结合第十方面或第十方面的第一种可选的实施方式，在第十方面的第二种可选的实施方式中，所述第一消息为AMF配置更新消息，所述第二消息为AMF配置更新确认消息；或，所述第一消息为NG接口建立响应消息。
结合第十方面或第十方面的第一种可选的实施方式或第十方面的第二种可选的实施方式，在第十方面的第三种可选的实施方式中，所述方法还包括：所述核心网设备接收来自所述接入网设备的RRC非激活态转换报告，所述RRC非激活态转换报告用于指示所述第一终端设备进入所述RRC非激活态；所述核心网设备按照所述第二周期向所述终端设备中的第一终端设备发送NAS消息，所述第一终端设备是所述接入网设备覆盖的任一个终端设备。
结合第十方面或第十方面的第一种可选的实施方式或第十方面的第二种可选的实施方式或第十方面的第三种可选的实施方式，在第十方面的第四种可选的实施方式中，所述终端设备为redcap UE。
关于第十方面或第十方面的各种可选的实施方式所带来的技术效果，可参考对于第九方面或相应的实施方式的技术效果的介绍，或者，可参考对于第七方面或相应的实施方式的技术效果的介绍。
第十一方面，提供第十一种通信方法，该方法可由第一终端设备执行，或者由芯片系统执行，该芯片系统能够实现第一终端设备的功能。该方法包括：第一终端设备接收来自接入网设备的第三消息，所述第三消息包括第三周期，所述第三周期是为所述第一终端设备配置的eDRX周期，且所述第三周期是所述第一终端设备在处于RRC非激活态时使用的，其中，所述第三周期是所述接入网设备根据第一周期和第二周期确定的，所述第一周期是所述核心网设备能够为多个终端设备配置的最大eDRX周期，且所述第一周期是所述多个终端设备在处于RRC非激活态时使用的，所述第二周期是所述接入网设备为所述多个终端设备配置的最大eDRX周期，且所述第二周期是所述多个终端设备在处于RRC非激活态时使用的，所述第二周期是根据所述第一周期确定的，所述第二周期的长度小于或等于所述第一周期的长度，所述多个终端设备包括所述第一终端设备；在所述第一终端设备处于RRC非激活态的情况下，所述第一终端设备按照所述第三周期监听寻呼。
结合第十一方面，在第十一方面的第一种可选的实施方式中，所述第三消息为RRC连接释放消息，所述RRC连接释放消息用于将所述第一终端设备释放到所述RRC非激活态。
结合第十一方面或第十一方面的第一种可选的实施方式，在第十一方面的第一种可选的实施方式中，所述第一终端设备为redcap UE。
关于第十一方面或第十一方面的各种可选的实施方式所带来的技术效果，可参考对于第九方面或相应的实施方式的技术效果的介绍，或者可参考对于第十方面或相应的实施方式的技术效果的介绍。
第十二方面，提供第十二种通信方法，该方法可由接入网设备执行，或由芯片系统执行，该芯片系统能够实现接入网设备的功能。示例性地，接入网设备为基站。该方法包括：接入网设备接收来自核心网设备的第一消息，所述第一消息包括第一周期，所述第一周期是能够为终端设备配置的最大eDRX周期，且所述第一周期是所述终端设备在处于RRC非激活态时使用的；所述接入网设备根据所述第一周期确定第二周期，所述第二周期是为所述终端设备中的第一终端设备配置的最大eDRX周期，且所述第二周期是所述第一终端设备在处于所述RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；所述接入网设备向所述第一终端设备发送第二消息，所述第二消息包括所述第二周期。
在本申请实施例中，核心网设备将核心网设备所能接受的上限值通知接入网设备，接入网设备可根据该上限值为不同的UE配置eDRX周期，从而接入网设备在为多个UE配置在RRC非激活态下使用的eDRX周期时可以更为准确，减少了接入网设备重新确定为多个UE配置的eDRX周期的过程。核心网设备如果要向多个UE中的任一个UE发送NAS消息，都可以按照第一周期来发送，使得这多个UE都能正常接收来自核心网设备的NAS消息，无论第一周期是大于10.24s还是小于10.24s，通过本申请实施例的方法，都能提高UE接收NAS消息的概率，减小NAS消息的丢包率。核心网设备也不必因为NAS消息发送失败而寻呼第一UE，第一UE也不必进入RRC空闲态后再发起随机接入，减小了业务传输时延，也节省了传输资源。而且对于这多个UE中的任一个UE，核心网设备都可以按照第二周期发送NAS消息，无需为不同的UE维护不同的eDRX周期，简化了核心网设备的实现过程。
结合第十二方面，在第十二方面的第一种可选的实施方式中，所述第一消息为AMF配置更新消息，或，所述第一消息为NG接口建立响应消息。
结合第十二方面或第十二方面的第一种可选的实施方式，在第十二方面的第二种可选的实施方式中，所述方法还包括：所述接入网设备根据所述第一周期确定第三周期，所述第三周期是为所述终端设备中的第二终端设备配置的最大eDRX周期，且所述第三周期是所述第二终端设备在处于所述RRC非激活态时使用的，所述第三周期的长度小于或等于所述第一周期的长度；所述接入网设备向所述第二终端设备发送第三消息，所述第三消息包括所述第三周期；其中，所述第二周期的长度与所述第三周期的长度相同或不同。
结合第十二方面或第十二方面的第一种可选的实施方式或第十二方面的第二种可选的实施方式，在第十二方面的第三种可选的实施方式中，所述接入网设备根据所述第一周期为不同的终端设备确定的eDRX周期的长度不同。
结合第十二方面或第十二方面的第一种可选的实施方式或第十二方面的第二种可选的实施方式或第十二方面的第三种可选的实施方式，在第十二方面的第四种可选的实施方式中，所述终端设备为redcap UE。
关于第十二方面或第十二方面的各种可选的实施方式所带来的技术效果，可参考对于第九方面或相应的实施方式的技术效果的介绍。
第十三方面，提供第十三种通信方法，该方法可由核心网设备执行，或由芯片系统执行，该芯片系统能够实现核心网设备的功能。示例性地，核心网设备为AMF。该方法包括：核心网设备确定第一周期，所述第一周期是能够为终端设备配置的最大eDRX周期，且所述第一周期是所述终端设备在处于RRC非激活态时使用的；核心网设备向接入网设备发送第一消息，所述第一消息包括所述第一周期。
结合第十三方面，在第十三方面的第一种可选的实施方式中，所述第一周期是根据NAS定时信息确定的，所述NAS定时信息包括NAS消息的最小重传时间间隔和/或NAS消息的最大重传次数。
结合第十三方面或第十三方面的第一种可选的实施方式，在第十三方面的第二种可选的实施方式中，所述第一消息为AMF配置更新消息，或，所述第一消息为NG接口建立响应消息。
结合第十三方面或第十三方面的第一种可选的实施方式或第十三方面的第二种可选的实施方式，在第十三方面的第三种可选的实施方式中，所述方法还包括：所述核心网设 备接收来自所述接入网设备的RRC非激活态转换报告，所述RRC非激活态转换报告用于指示所述终端设备中的第一终端设备进入所述RRC非激活态；所述核心网设备按照所述第一周期向所述第一终端设备发送NAS消息。
结合第十三方面或第十三方面的第一种可选的实施方式或第十三方面的第二种可选的实施方式或第十三方面的第三种可选的实施方式，在第十三方面的第四种可选的实施方式中，所述终端设备为redcap UE。
关于第十三方面或第十三方面的各种可选的实施方式所带来的技术效果，可参考对于第十二方面或相应的实施方式的技术效果的介绍。
第十四方面，提供第十四种通信方法，该方法可由第一终端设备执行，或者由芯片系统执行，该芯片系统能够实现第一终端设备的功能。该方法包括：第一终端设备接收来自接入网设备的第二消息，所述第二消息包括第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于RRC非激活态时使用的，其中，所述第二周期是所述接入网设备根据第一周期确定的，所述第一周期是所述核心网设备能够为多个终端设备配置的最大eDRX周期，且所述第一周期是所述多个终端设备在处于RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度，所述多个终端设备包括所述第一终端设备；在所述第一终端设备处于RRC非激活态的情况下，所述第一终端设备按照所述第二周期监听寻呼。
结合第十四方面，在第十四方面的第一种可选的实施方式中，所述第二消息为RRC连接释放消息，所述RRC连接释放消息用于将所述第一终端设备释放到所述RRC非激活态。
结合第十四方面或第十四方面的第一种可选的实施方式，在第十四方面的第二种可选的实施方式中，所述终端设备为redcap UE。
关于第十四方面或第十四方面的各种可选的实施方式所带来的技术效果，可参考对于第十二方面或相应的实施方式的技术效果的介绍。
第十五方面，提供一种通信装置。所述通信装置可以包括用于执行第二方面或第二方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第十六方面，提供一种通信装置。所述通信装置可以包括用于执行第三方面或第三方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第十七方面，提供一种通信装置。所述通信装置可以包括用于执行第四方面或第四方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第十八方面，提供一种通信装置。所述通信装置可以包括用于执行第六方面或第六方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第十九方面，提供一种通信装置。所述通信装置可以包括用于执行第七方面或第七方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第二十方面，提供一种通信装置。所述通信装置可以包括用于执行第八方面或第八方 面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第二十一方面，提供一种通信装置。所述通信装置可以包括用于执行第九方面或第九方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第二十二方面，提供一种通信装置。所述通信装置可以包括用于执行第十方面或第十方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第二十三方面，提供一种通信装置。所述通信装置可以包括用于执行第十一方面或第十一方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第二十四方面，提供一种通信装置。所述通信装置可以包括用于执行第十二方面或第十二方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第二十五方面，提供一种通信装置。所述通信装置可以包括用于执行第十三方面或第十三方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第二十六方面，提供一种通信装置。所述通信装置可以包括用于执行第十四方面或第十四方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第二十七方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第二方面或第二方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第二方面或第二方面的任一种可选的实施方式所提供的方法。
第二十八方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第三方面或第三方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第三方面或第三方面的任一种可选的实施方式所提供的方法。
第二十九方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第四方面或第四方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第四方面或第四方面的任一种可选的实施方式所提供的方法。
第三十方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第六方面或第六方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第六方面或第六方面的任一种可选的实施方式所提供的方法。
第三十一方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第七方面或第七方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第七方面或第七方面的任一种可选的实施方式所提供的方法。
第三十二方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第八方面或第八方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第八方面或第八方面的任一种可选的实施方式所提供的方法。
第三十三方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第九方面或第九方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第九方面或第九方面的任一种可选的实施方式所提供的方法。
第三十四方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第十方面或第十方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第十方面或第十方面的任一种可选的实施方式所提供的方法。
第三十五方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第十一方面或第十一方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第十一方面或第十一方面的任一种可选的实施方式所提供的方法。
第三十六方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第十二方面或第十二方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第十二方面或第十二方面的任一种可选的实施方式所提供的方法。
第三十七方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第十三方面或第十三方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第十三方面或第十三方面的任一种可选的实施方式所提供的方法。
第三十八方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第十四方面或第十四方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第十四方面或第十四方面的任一种可选的实施方式所提供的方法。
第三十九方面，提供第一通信系统。所述第一通信系统包括第十五方面所述的通信装置或第二十七方面所述的芯片系统，第十六方面的通信装置或第二十八方面所述的芯片系统，以及包括第十七方面的通信装置或第二十九方面所述的芯片系统。或者，所述第一通信系统包括第一方面所述的核心网设备、接入网设备以及第一终端设备。
第四十方面，提供第二通信系统。所述第二通信系统包括第十八方面所述的通信装置或第三十方面所述的芯片系统，第十九方面的通信装置或第三十一方面所述的芯片系统，以及包括第二十方面的通信装置或第三十二方面所述的芯片系统。或者，所述第二通信系统包括第五方面所述的核心网设备、接入网设备以及第一终端设备。
第四十一方面，提供第三通信系统。所述第三通信系统包括第二十一方面所述的通信装置或第三十三方面所述的芯片系统，第二十二方面的通信装置或第三十四方面所述的芯片系统，以及包括第二十三方面的通信装置或第三十五方面所述的芯片系统。
第四十二方面，提供第四通信系统。所述第四通信系统包括第二十四方面所述的通信装置或第三十六方面所述的芯片系统，第二十五方面的通信装置或第三十七方面所述的芯片系统，以及包括第二十六方面的通信装置或第三十八方面所述的芯片系统。
第四十三方面，提供第十五种通信方法，该方法可由接入网设备执行，或由芯片系统执行，该芯片系统能够实现接入网设备的功能。示例性地，接入网设备为基站。该方法包括：接入网设备接收来自核心网设备的第一消息，所述第一消息包括第一周期，所述第一周期是能够为第一终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；所述接入网设备根据所述第一周期确定第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；所述接入网设备向所述第一终端设备发送第二消息，所述第二消息包括所述第二周期。
在本申请实施例中，核心网设备先将核心网设备所能接受的上限值通知接入网设备，从而接入网设备在为第一UE配置在RRC非激活态下使用的eDRX周期时可以更为准确，减少了接入网设备重新确定为第一UE配置的eDRX周期的过程。接入网设备会根据第一周期为第一UE配置eDRX周期，核心网设备如果要向第一UE发送NAS消息，可以按照第一周期来发送，使得第一UE按照接入网设备配置的eDRX周期能够正常接收来自核心网设备的NAS消息，无论第二周期是大于10.24s还是小于10.24s，通过本申请实施例的方法，都能提高UE接收NAS消息的概率，减小NAS消息的丢包率。且接入网设备无需将为第一UE确定的eDRX周期通知核心网设备，减少了信令开销。而且核心网设备也不必因为NAS消息发送失败而寻呼第一UE，第一UE也不必进入RRC空闲态后再发起随机接入，减小了NAS消息的传输时延，也节省了传输资源。而且在本申请实施例中，核心网设备可将NAS定时信息作为考虑因素而给出eDRX周期上限值(例如，第一周期)让接入网设备作为参考，而不必让接入网设备考虑第一UE在RRC空闲态下使用的eDRX周期来为第一UE配置在RRC非激活态时使用的eDRX周期，使得为UE配置eDRX周期的方式更为灵活。
结合第四十三方面，在第四十三方面的第一种可选的实施方式中，所述第一消息为初始上下文建立请求消息。
结合第四十三方面或第四十三方面的第一种可选的实施方式，在第四十三方面的第二种可选的实施方式中，所述第二消息为RRC连接释放消息，所述RRC连接释放消息用于 将所述第一终端设备释放到所述RRC非激活态。
结合第四十三方面或第四十三方面的第一种可选的实施方式或第四十三方面的第二种可选的实施方式，在第四十三方面的第三种可选的实施方式中，所述第一终端设备为redcap UE。
关于第四十三方面的一些可选的实施方式所带来的技术效果，可参考对于第六方面或相应的实施方式的技术效果的介绍。
第四十四方面，提供第十六种通信方法，该方法可由核心网设备执行，或由芯片系统执行，该芯片系统能够实现核心网设备的功能。示例性地，核心网设备为AMF。该方法包括：核心网设备确定第一周期，所述第一周期是能够为第一终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；所述核心网设备向接入网设备发送第一消息，所述第一消息包括所述第一周期。
结合第四十四方面，在第四十四方面的第一种可选的实施方式中，所述第一周期是根据NAS定时信息确定的，所述NAS定时信息包括NAS消息的最小重传时间间隔和/或NAS消息的最大重传次数。
结合第四十四方面或第四十四方面的第一种可选的实施方式，在第四十四方面的第二种可选的实施方式中，所述第一消息为初始上下文建立请求消息。
结合第四十四方面或第四十四方面的第一种可选的实施方式或第四十四方面的第二种可选的实施方式，在第四十四方面的第三种可选的实施方式中，所述方法还包括：所述核心网设备接收来自所述接入网设备的RRC非激活态转换报告，所述RRC非激活态转换报告用于指示所述第一终端设备进入所述RRC非激活态；所述核心网设备按照所述第一周期向所述第一终端设备发送NAS消息。
结合第四十四方面或第四十四方面的第一种可选的实施方式或第四十四方面的第二种可选的实施方式或第四十四方面的第三种可选的实施方式，在第四十四方面的第四种可选的实施方式中，所述第一终端设备为redcap UE。
关于第四十四方面或第四十四方面的各种可选的实施方式所带来的技术效果，可参考对于第四十三方面或相应的实施方式的技术效果的介绍。
第四十五方面，提供第十七种通信方法，该方法可由第一终端设备执行，或者由芯片系统执行，该芯片系统能够实现第一终端设备的功能。该方法包括：第一终端设备接收来自接入网设备的第二消息，所述第二消息包括第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于RRC非激活态时使用的，其中，所述第二周期是所述接入网设备根据第一周期确定的，所述第一周期是所述核心网设备能够为所述第一终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；在所述第一终端设备处于RRC非激活态的情况下，所述第一终端设备按照所述第二周期监听寻呼。
结合第四十五方面，在第四十五方面的第一种可选的实施方式中，所述第二消息为RRC连接释放消息，所述RRC连接释放消息用于将所述第一终端设备释放到所述RRC非激活态。
结合第四十五方面或第四十五方面的第一种可选的实施方式，在第四十五方面的第二种可选的实施方式中，所述第一终端设备为redcap UE。
关于第四十五方面或第四十五方面的各种可选的实施方式所带来的技术效果，可参考对于第四十三方面或相应的实施方式的技术效果的介绍。
第四十六方面，提供一种通信装置。所述通信装置可以包括用于执行第四十三方面或第四十三方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第四十七方面，提供一种通信装置。所述通信装置可以包括用于执行第四十四方面或第四十四方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第四十八方面，提供一种通信装置。所述通信装置可以包括用于执行第四十五方面或第四十五方面的任一可选的实施方式中的方法的模块，例如包括收发单元和处理单元。可选的，还可以包括存储单元。
第四十九方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第四十三方面或第四十三方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第四十三方面或第四十三方面的任一种可选的实施方式所提供的方法。
第五十方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第四十四方面或第四十四方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第四十四方面或第四十四方面的任一种可选的实施方式所提供的方法。
第五十一方面，提供一种芯片系统，所述芯片系统包括一个或多个处理器，以及包括通信接口，所述处理器与所述通信接口耦合，用于实现上述第四十五方面或第四十五方面的任一种可选的实施方式所提供的方法。可选的，所述芯片系统还可以包括存储器，例如，所述处理器可以读取并执行所述存储器所存储的软件程序，以实现上述第四十五方面或第四十五方面的任一种可选的实施方式所提供的方法。
第五十二方面，提供第五通信系统。所述第五通信系统包括第四十六方面所述的通信装置或第四十九方面所述的芯片系统，第四十七方面的通信装置或第五十方面所述的芯片系统，以及包括第四十八方面的通信装置或第五十一方面所述的芯片系统。
第五十三方面，提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述任意一个方面所提供的方法。
第五十四方面，提供一种包含指令的计算机程序产品，所述计算机程序产品用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行上述任意一个方面所提供的方法。
附图说明
图1为eDRX周期的一种示意图；
图2是为eMTC UE配置RRC非激活态的eDRX周期的流程图；
图3为本申请实施例的一种应用场景示意图；
图4为本申请实施例提供的第一种通信方法的流程图；
图5为本申请实施例提供的第二种通信方法的流程图；
图6为本申请实施例提供的第三种通信方法的流程图；
图7为本申请实施例提供的第四种通信方法的流程图；
图8为本申请实施例提供的一种通信装置的一种示意性框图；
图9为本申请实施例提供的又一种通信装置的一种示意性框图。
具体实施方式
为了使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施例作进一步地详细描述。
以下，对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
本申请实施例中，终端设备是一种具有无线收发功能的设备，可以是固定设备，移动设备、手持设备、穿戴设备、车载设备，或内置于上述设备中的无线装置(例如，通信模块或芯片系统等)。所述终端设备用于连接人，物，机器等，可广泛用于各种场景，例如包括但不限于以下场景：蜂窝通信、设备到设备通信(device-to-device，D2D)、车到一切(vehicle to everything，V2X)、机器到机器/机器类通信(machine-to-machine/machine-type communications，M2M/MTC)、物联网(internet of things，IoT)、虚拟现实(virtual reality，VR)、增强现实(augmented reality，AR)、工业控制(industrial control)、无人驾驶(self driving)、远程医疗(remote medical)、智能电网(smart grid)、智能家具、智能办公、智能穿戴、智能交通，智慧城市(smart city)、无人机、机器人等场景的终端设备。所述终端设备有时可称为UE、终端、接入站、UE站、远方站、无线通信设备、或用户装置等等，为描述方便，本申请实施例中将终端设备以UE为例进行说明。
例如，本申请的各个实施例涉及的UE例如为redcap UE。之所以称为redcap UE，是因为与现有的普通NR UE相比，redcapUE设备通常只支持更低的带宽，例如20MHz，且支持更少的收发天线数，例如只支持1T1R或者1T2R。按照现有课题的研究内容，redcap UE包括三类低能力的UE：可穿戴产品、视频监控设备和工业传感器设备。当然除了redcap UE之外，本申请的各个实施例的技术方案还可以应用于其他UE，例如应用于对时延不敏感(或者说要求不高)的UE，例如eMTC UE等。在后文中，主要以将本申请的各个实施例提供的技术方案应用于redcap UE为例来介绍。
本申请实施例中的网络设备，例如包括接入网设备，和/或核心网设备。所述接入网设备为具有无线收发功能的设备，用于与所述终端设备进行通信。所述接入网设备包括但不限于上述通信系统中的基站(BTS,Node B,eNodeB/eNB，或gNodeB/gNB)、收发点(transmission reception point,TRP)，3GPP后续演进的基站，WiFi系统中的接入节点，无线中继节点，无线回传节点等。所述基站可以是：宏基站，微基站，微微基站，小站，中继站等。多个基站可以支持上述提及的同一种接入技术的网络，也可以支持上述提及的不同接入技术的网络。基站可以包含一个或多个共站或非共站的传输接收点。网络设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、集中单元(centralized unit，CU)，和/或分布单元(distributed unit，DU)。网络设备还可以是服务器，可穿戴设备，或车载设备等。例如，V2X技术中的网络设备可以为路侧单元(road side unit，RSU)。以下对接入网设备以为基站为例进行说明。所述通信系统中的多个网络设备可以为 同一类型的基站，也可以为不同类型的基站。基站可以与终端设备进行通信，也可以通过中继站与终端设备进行通信。终端设备可以与不同接入技术中的多个基站进行通信。所述核心网设备用于实现移动管理，数据处理，会话管理，策略和计费等功能。不同接入技术的系统中实现核心网功能的设备名称可以不同，本申请并不对此进行限定。以5G系统为例，所述核心网设备可包括访问和移动管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)、或用户面功能(user plane function，UPF)等。以4G系统为例，所述核心网设备可包括移动性管理实体(mobility management entity)等。
本申请实施例中，用于实现网络设备的功能的装置可以是网络设备，也可以是能够支持网络设备实现该功能的装置，例如芯片系统，该装置可以被安装在网络设备中。在本申请实施例提供的技术方案中，以用于实现网络设备的功能的装置是网络设备为例，描述本申请实施例提供的技术方案。
本申请实施例中，对于名词的数目，除非特别说明，表示“单数名词或复数名词”，即"一个或多个”。“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。例如，A/B，表示：A或B。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，表示：a,b,c,a和b,a和c,b和c,或a和b和c，其中a,b,c可以是单个，也可以是多个。
以及，除非有相反的说明，本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分，不用于限定多个对象的大小、内容、顺序、时序、优先级或者重要程度等。例如，第一周期和第二周期，可以是同一个周期(例如，周期的时间长度相同)，也可以是不同的周期(例如，周期的时间长度不同)，且，这种名称也并不是表示这两个周期的时间长度、优先级或者重要程度等的不同。
前文介绍了本申请实施例所涉及到的一些名词概念，下面介绍本申请实施例涉及的技术特征。
DRX机制通过不连续地接收信号，使得UE能够大部分时间处于休眠状态，来达到省电的目的。因为基于包的数据流一般都是突发性的，在没有数据传输的时候，就可以通过关闭UE的接收电路来降低功耗。eDRX是扩展的DRX，在每个eDRX周期里，UE只在设置的PTW可以接收下行数据，在PTW外的其余时间，UE处于休眠状态。其中，每个eDRX周期内有一个PTW，UE在PTW内按照DRX周期监听寻呼信道。如果eDRX周期配置的较大，则UE可以有更大的功耗增益，但也同时增大了业务传输时延。关于eDRX工作模式可参考图1。
由于LTE UE、eMTC UE、NB-IoT UE或NR UE等，不同类型的UE有不同的业务要求，因此不同类型的UE对于eDRX机制和DRX机制的适用情况也是不同的，对此可参考表1。
表1
Figure PCTCN2021114558-appb-000001
Figure PCTCN2021114558-appb-000002
根据表1可知，目前LTE UE和NR UE都只支持DRX机制，而不支持eDRX机制，对于这两类UE，在处于RRC空闲态和处于RRC非激活态时，能够支持的最大DRX周期都是2.56s。eMTC UE在处于RRC空闲态时，能够支持的最大eDRX周期约为44分钟，在处于RRC非激活态时，能够支持的最大eDRX周期为10.24s，而eMTC UE也是这几类UE中唯一在处于RRC非激活态时能够支持eDRX机制的UE。NB-IoT UE没有RRC非激活态，当NB-IoT UE处于RRC空闲态时，能够支持的最大eDRX周期约为3小时。
目前中提出了redcap UE各应用场景下的工作时间要求。例如，对于redcap UE中的工业无线传感器设备，需要工作几年的时间；对于redcap UE中的可穿戴设备，要求工作时间为1～2周。因为目前没有针对NR UE配置eDRX，但为了满足上述的工作时间要求，提出需要研究redcap UE在处于RRC空闲态和RRC非激活态下的eDRX，以达到降低功耗的目的。
UE处于RRC空闲态时使用的eDRX周期，是由核心网设备通过UE注册(registration)过程中的NAS消息配置下来的；对于eMTC UE来说，处于RRC非激活态时使用的eDRX周期，是由基站通过RRC连接释放(RRC connection release)消息配置下来的。其中，UE处于RRC空闲态时使用的eDRX周期，也就是核心网设备为UE配置的核心网寻呼周期(core network paging cycle)，UE处于RRC非激活态时使用的eDRX周期，也就是基站为UE配置的无线接入网(radio access network，RAN)paging cycle。目前仅eMTC UE能够配置RRC非激活态的eDRX周期(即，在RRC非激活态下使用的eDRX周期)，其配置流程可参考图2。
S21、核心网设备向基站发送RRC非激活态的核心网辅助信息(core network assistance information for RRC inactive)，基站接收来自核心网设备的RRC非激活态的核心网辅助信息。其中，core network assistance information for RRC inactive是一个信息单元(information element，IE)，该IE例如包括在初始上下文建立请求(initial context setup request)消息中。
core network assistance information for RRC inactive可以包括UE专用DRX(UE specific DRX)周期，以及包括寻呼(paging)eDRX information。其中，该paging eDRX information是UE在处于RRC空闲态时使用的eDRX周期。
S22、基站向UE发送RRC连接释放消息，UE接收来自基站的RRC连接释放消息。
基站参考core network assistance information for RRC inactive中的paging eDRX information，确定为该UE配置的在RRC非激活态时使用的eDRX周期。其中，基站为该UE配置的在RRC非激活态时使用的eDRX周期的时间长度，小于或等于paging eDRX information对应的eDRX周期的时间长度。基站在确定为该UE配置的在RRC非激活态时使用的eDRX周期后，可通过RRC连接释放消息将该eDRX周期发送给UE，从而该UE进入RRC非激活态后，可以使用该eDRX周期监听寻呼。
目前定义，移动性管理(mobility management)中NAS消息的最小重传时间间隔为6s，最大重传次数为4次。eMTC UE连接5G核心网(5GC)时可以处于RRC非激活态，当UE处于RRC非激活态时，由于基站还保留着该UE的上下文和与核心网的下一代(next generation，NG)接口连接，所以核心网设备认为该UE是处于RRC连接(connected)态，但基站和该UE都知道该UE实际处于RRC非激活态，此时就出现对UE的状态认知不一致的异常场景。如果核心网设备在UE处于RRC非激活态时向该UE发送NAS消息，则基站会在接收来自核心网设备的NAS消息后寻呼该UE，并在该UE响应寻呼后将该NAS消息发送给UE，且在UE响应寻呼后，接入网设备向核心网设备发送对应于该NAS消息的反馈信息。因为已经规定NAS消息的最小重传时间间隔为6s，最大重传次数为4次，所以核心网设备需要在30s内接收到对于该NAS消息的反馈信息，否则核心网设备就会认为NAS消息传输失败。如果核心网设备认为NAS消息传输失败，则核心网设备会寻呼该UE，该UE如果接收了来自核心网设备的寻呼消息，则该UE需要进入RRC空闲态，再在RRC空闲态下发起随机接入。
根据前文的介绍可知，基站为UE配置RRC非激活态下的eDRX周期时，会参考core network assistance information for RRC inactive中的paging eDRX information。对于eMTC UE，因为已经规定了RRC非激活态下的eDRX周期的最大值为10.24s，因此该eDRX周期不会对UE接收NAS消息产生影响。但是如果redcap UE也能支持RRC非激活态下的eDRX机制，则redcap UE的RRC非激活态下的eDRX周期不一定小于或等于10.24s，有可能会大于10.24s。eDRX周期的时间长度增加，就会减少UE接收NAS消息的次数，甚至UE在一个eDRX周期内无法接收任一个NAS消息。那么，当NAS消息的重传次数超过4次后，核心网设备会认为NAS消息传输失败，则核心网设备会寻呼该UE，该UE如果接收了来自核心网设备的寻呼消息，则该UE需要进入RRC空闲态，再在RRC空闲态下发起随机接入。显然，该过程会带来较大的时延，而且会耗费较多传输资源。
鉴于此，提供本申请实施例的方法。在本申请实施例中，接入网设备与核心网设备能够进行协商，以确定第二周期，第二周期就是能够配置给第一终端设备在RRC非激活态下使用的eDRX周期。通过这样的方式，可以基于接入网设备和核心网设备的自身情况给出较为合理的eDRX周期，从而核心网设备如果要向第一终端设备发送NAS消息，可以按照第二周期来发送，这样，无论第二周期是小于或等于10.24s还是大于10.24s，都能使得第一终端设备按照第二周期正常接收来自核心网设备的NAS消息，提高了终端设备接收NAS消息的概率，减小了NAS消息的丢包率，也相应减小了NAS消息的传输时延。
本申请实施例提供的技术方案可以应用于4G系统中，例如LTE系统，或可以应用于5G系统中，例如NR系统，或者还可以应用于下一代移动通信系统或其他类似的通信系统，具体的不做限制。
请参见图3，为本申请实施例的一种应用场景。图3包括接入网设备、核心网设备和UE。该接入网设备例如工作在演进的通用移动通信系统陆地无线接入(evolved UMTS terrestrial radio access，E-UTRA)系统中，或者工作在NR系统中，或者工作在下一代通信系统或其他通信系统中。该接入网设备例如为基站。其中，接入网设备在不同的系统对应不同的设备，例如在4G系统中可以对应eNB，在5G系统中对应5G中的接入网设备，例如gNB。当然本申请实施例所提供的技术方案也可以应用于未来的移动通信系统中，因此图3中的接入网设备也可以对应未来的移动通信系统中的网络设备。图3以接入网设备 是基站为例，实际上参考前文的介绍，接入网设备还可以是RSU等设备。另外，图3中的UE以手机为例，实际上根据前文对于UE的介绍可知，本申请实施例的UE不限于手机。
另外，为了便于介绍，后文将要介绍的各个实施例均以应用在图3所示的架构为例。例如，后文的各个实施例所述的接入网设备例如为图3所示的网络架构中的接入网设备，后文的各个实施例所述的核心网设备例如为图3所示的网络架构中的核心网设备，后文的各个实施例所述的UE可以是图3所示的网络架构中的UE。且后文的各个实施例所述的核心网设备，例如为AMF，或者也可以是其他的位于核心网侧的设备。
下面结合附图介绍本申请实施例所提供的方法。在本申请的各个实施例对应的附图中，凡是用虚线表示的步骤均为可选的步骤。
本申请实施例提供第一种通信方法，请参见图4，为该方法的流程图。
S41、核心网设备发送第一信息，相应的，接入网设备接收来自核心网设备的第一信息。
第一信息例如包括第一UE在处于RRC空闲态时使用的eDRX周期。可选的，第一信息还可以包括UE专用DRX周期等信息。
例如第一UE处于RRC空闲态，如果核心网设备获得了第一UE的下行数据(例如，核心网设备接收来自其他设备的该下行数据，或，核心网设备生成该下行数据)，核心网设备可以发送用于寻呼第一UE的核心网寻呼消息，第一信息可以包括在该核心网寻呼消息中。例如，核心网寻呼消息包括寻呼eDRX周期信息信息单元(paging eDRX information IE)，第一UE在处于RRC空闲态时使用的eDRX周期可包括在该信息单元(information element，IE)中。另外，如果第一信息还包括UE专用DRX周期，则UE专用DRX周期可以包括在核心网寻呼消息内的paging DRX IE中。如果第一信息包括在核心网寻呼消息中，则第一UE接收该核心网寻呼消息后，可以向接入网设备发起随机接入，以从RRC空闲态进入RRC连接态。
或者，核心网设备也可以通过其他消息将第一信息发送给接入网设备，只要该消息是与第一UE相关的消息即可(例如，该消息包括第一UE的标识)，对于该消息的类型不做限制。
S42、接入网设备确定第一周期，第一周期为接入网设备期望为第一UE配置的eDRX周期，且第一周期是用于第一UE在处于RRC非激活态时使用。
接入网设备在接收第一信息后，可以根据第一信息确定第一周期，例如，接入网设备可以根据第一UE在处于RRC空闲态时使用的eDRX周期确定第一周期。例如，接入网设备所确定的第一周期的时间长度可以小于或等于第一UE在处于RRC空闲态时使用的eDRX周期的时间长度。
S43、接入网设备向核心网设备发送第一消息，相应的，核心网设备接收来自接入网设备的第一消息。第一消息包括第一周期。
例如，接入网设备在接收该寻呼消息后，除了可以确定第一周期外，还可以向第一UE发送该寻呼消息，相应的，第一UE接收来自接入网设备的寻呼消息。第一UE接收该寻呼消息后，可以基于该寻呼消息向接入网设备发起RRC连接建立流程，以与接入网设备建立RRC连接。在第一UE与接入网设备建立RRC连接成功后，第一UE发起的第一个上行NAS消息可以通过初始UE消息(initial UE message)发送给核心网设备。例如初始UE消息中可以包括附着请求(attach request)、用户定位信息(user location information)、 RRC建立原因(RRC establishment cause)以及认证指示(authenticated indication)等信息。其中，附着请求可包括来自第一UE的NAS消息所包括的信息。在本申请实施例中，可以将第一周期包括在该初始UE消息中，即，初始UE消息可以作为第一消息。
例如，在初始UE消息中新增IE，例如称为第一IE，第一周期可以通过第一IE承载。或者，接入网设备也可以通过其他消息将第一周期发送给核心网设备，即，第一消息也可以是除初始UE消息外的其他消息。
S44、核心网设备向接入网设备发送第二消息，相应的，接入网设备接收来自核心网设备的第二消息。第二消息包括第二周期。
核心网设备接收第一周期后，可以确定第二周期，第二周期是核心网设备确定的第一UE在处于RRC非激活态时使用的eDRX周期。例如，核心网设备可以确定是否能为第一UE配置第一周期，或者说，确定核心网设备是否能够接受将第一周期作为第一UE在RRC非激活态下使用的eDRX周期。如果核心网设备确定能为第一UE配置第一周期，那么第二周期与第一周期就是同一个周期，例如第二周期的时间长度等于第一周期的时间长度。而如果核心网设备确定不能为第一UE配置第一周期，则核心网设备可以重新为第一UE确定核心网设备能够接受的第二周期，此时第二周期与第一周期就是不同的eDRX周期，例如第二周期的时间长度与第一周期的时间长度不相等。
作为一种可选的实施方式，核心网设备可以根据NAS定时信息确定是否能为第一UE配置第一周期，或者说，核心网设备可以根据NAS定时信息和第一周期确定第二周期。例如，如果核心网设备确定第一周期能够适配当前的NAS定时信息，则核心网设备确定能够接受第一UE使用第一周期，那么第二周期的时间长度等于第一周期的时间长度；或者，如果核心网设备确定第一周期不能适配当前的NAS定时信息，但如果调整NAS定时信息，可以使得第一周期适配调整后的NAS定时信息，则核心网设备确定能够接受第一UE使用第一周期，那么第二周期的时间长度等于第一周期的时间长度；或者，如果核心网设备确定第一周期不能适配当前的NAS信息，且即使调整NAS定时信息，也无法使得第一周期适配调整后的NAS定时信息(因为核心网设备对于NAS定时信息的调整也不是无限制的，可能调整到一定程度后就不能再调整，因此即使调整NAS定时信息，也可能无法适配第一周期)，则核心网设备确定无法接受第一UE使用第一周期，那么第二周期的时间长度不等于第一周期的时间长度，例如第二周期的时间长度小于第一周期的时间长度，但第二周期的时间长度可以等于根据NAS定时信息所确定的最大时间长度。
NAS定时信息可以包括NAS消息的最小重传时间间隔，或者包括NAS消息最大重传次数，或者包括NAS消息最小重传时间间隔和NAS消息的最大重传次数。如果NAS定时信息包括NAS消息的最小重传时间间隔，则核心网设备调整NAS定时信息，就是指调整NAS消息的最小重传时间间隔，例如可以将NAS消息的最小重传时间间隔调大或调小，为了使得为UE配置的eDRX周期更为灵活，一般来说可以将NAS消息的最小重传时间间隔调大。但核心网设备是有接受限制的，因此NAS消息的最小重传时间间隔也不能无限调大，而是有调整上限。或者，如果NAS定时信息包括NAS消息的最大重传次数，则核心网设备调整NAS定时信息，就是指调整NAS消息的最大重传次数，例如可以将NAS消息的最大重传次数调大或调小，为了使得为UE配置的eDRX周期更为灵活，一般来说可以将NAS消息的最大重传次数调大。但核心网设备是有接受限制的，因此NAS消息的最大重传次数也不能无限调大，而是有调整上限。或者，如果NAS定时信息包括NAS消 息最小重传时间间隔和NAS消息的最大重传次数，则核心网设备调整NAS定时信息，可以包括调整NAS消息的最小重传时间间隔，或者包括调整NAS消息的最大重传次数，或者既调整NAS消息的最小重传时间间隔也调整NAS消息的最大重传次数。
为了方便理解，可以认为，核心网设备根据NAS定时信息可以确定第一阈值，第一阈值例如为NAS定时信息对应的最大时间长度，或者，第一阈值是核心网设备能够接受的、为终端设备配置的最大eDRX周期。其中，第一阈值可以是根据未调整的NAS定时信息确定的，或者也可以是根据调整后的NAS定时信息确定的。如果第一阈值是根据调整后的NAS定时信息确定的，那么例如，第一阈值是根据按照最大调整幅度所调整后的NAS定时信息确定的，即，第一阈值可以认为是核心网设备的能力所能够接受的最大值。那么，如果第一周期的时间长度小于或等于第一阈值，则核心网设备确定能够接受第一周期，此时，第二周期与第一周期可以是相同的周期，例如，第二周期的时间长度与第一周期的时间长度相同。而如果第一周期的时间长度大于第一阈值，则核心网设备确定无法接受第一周期，在这种情况下，核心网设备可以确定核心网设备所能接受的第二周期，那么第二周期的时间长度就可以小于第一周期的时间长度，但第二周期需要符合核心网设备的要求，因此第二周期的长度可以小于或等于第一阈值。
例如，第一周期的时间长度较短，例如第一周期的时间长度小于或等于10.24s，则核心网设备可能根据NAS定时信息确定能够接受第一UE使用第一周期，在这种情况下，核心网设备能够接受第一UE使用第一周期，核心网设备所确定的第二周期的时间长度可以等于第一周期的时间长度。又例如，第一周期的时间长度较长，例如第一周期的时间长度大于10.24s，例如为20.48s，核心网设备可以调整NAS定时信息，例如调整后的NAS定时信息能够适配20.48s的eDRX周期，则核心网设备能够接受第一UE使用第一周期，核心网设备所确定的第二周期的时间长度可以等于第一周期的时间长度。再例如，第一周期的时间长度较长，例如第一周期的时间长度大于10.24s，例如为40.96s，核心网设备确定，即使按照最大调整幅度调整NAS定时信息(例如，将NAS消息的最小重传时间间隔调整到核心网设备所能接受的最大值，和/或，将NAS消息的最大重传次数调整到核心网设备所能接受的最大值)，调整后的NAS定时信息也无法适配40.96的eDRX周期，则核心网设备无法接受第一UE使用第一周期，核心网设备所确定的第二周期的时间长度可以小于第一周期的时间长度。
核心网设备在确定第二周期后，可以通过第二消息将第二周期发送给接入网设备。例如，核心网设备向接入网设备发送初始上下文建立请求消息，该初始上下文建立请求消息可以作为第二消息。
例如，该初始上下文建立请求消息包括第二IE，第二IE例如为寻呼信息单元的UE无线能力信息单元(UE Radio Capability for Paging IE)。第二IE内还可以包括其他IE，例如第二IE内还包括第三IE，第三IE例如为UE无线寻呼信息信息单元(UE radio paging information)。第二周期例如通过第三IE包括的第一字段承载，第一字段例如为空白(spare)字段。例如，第三IE内包括一个或多个空白字段，第一字段可以是其中的一个。例如，UE radio paging information定义如下：
Figure PCTCN2021114558-appb-000003
Figure PCTCN2021114558-appb-000004
可以看到，其中的spare1～spare7表示7个空白字段，第一字段可以包括这7个空白字段中的一个或多个。
或者，该初始上下文建立请求消息中包括core network assistance information for RRC inactive，例如在该core network assistance information for RRC inactive中新增IE，例如称为第四IE，第四IE可承载第二周期。
或者，核心网设备也可以通过其他消息将第二周期发送给接入网设备，只要该消息与第一UE相关(例如，该消息包括第一UE的标识)即可。
通过如上的步骤，接入网设备与核心网设备就完成了对于第一UE的RRC非激活态的eDRX周期的协商，第二周期就是通过协商所确定的第一UE在RRC非激活态下能够使用的eDRX周期。
S45、接入网设备向第一UE发送第三消息，相应的，第一UE接收来自接入网设备的第三消息。第三消息包括第二周期。
接入网设备接收了来自核心网设备的第二周期，因为第二周期是核心网设备能够接受的，核心网设备会按照第二周期来向第一UE发送NAS消息，因此接入网设备将第二周期作为配置给第一UE的最终值。接入网设备可以通过第三消息将第二周期发送给第一UE，也就是将第二周期配置给第一UE，从而第一UE在进入RRC非激活态后，可以使用第二周期来监听寻呼。
例如，在接入网设备未检测到第一UE的数据传输时，接入网设备可启动RRC连接释放定时器。如果RRC连接释放定时器超时，则接入网设备可以向第一UE发送RRC连接释放消息，以将第一UE释放到RRC非激活态。例如第一UE为手机，如果用户暂时没有使用手机，手机进入了待机状态，那么手机与接入网设备之间可能暂时没有数据传输，在这种情况下，接入网设备在一段时间内未接收来自该手机的上行数据，而接入网设备也没有需要向该终端设备发送的下行数据，接入网设备就可以将该手机释放到RRC非激活态。可选的，接入网设备在向第一UE发送RRC连接释放消息时，将第二周期包括在该RRC连接释放消息中发送给第一UE，即，RRC连接释放消息可以作为第三消息。RRC连接释放消息用于将第一UE释放到RRC非激活态，而第二周期也是第一UE在处于RRC非激活态时使用的，因此通过RRC连接释放消息将第二周期发送给第一UE，可以使得第二周期能够得到较为及时地应用。而且RRC连接释放消息既可以将第一UE释放到RRC非激活态，也可以为第一UE配置第二周期，提高了消息的利用率，且因为无需发送额外的消息来为第一UE配置第二周期，也减少了传输开销。
或者，接入网设备也可以通过其他消息将第二周期发送给第一UE，例如接入网设备 也可以在向第一UE发送RRC连接释放消息之前就通过其他消息将第二周期发送给第一UE。
S46、接入网设备向核心网设备发送RRC非激活态转换报告(RRC inactive transition report)，相应的，核心网设备接收来自接入网设备的RRC非激活态转换报告。
RRC非激活态转换报告可以指示第一UE进入了RRC非激活态。
S47、核心网设备按照第二周期向第一UE发送NAS消息，相应的，第一UE按照第二周期监听寻呼，从而接收该NAS消息。
核心网设备在第一UE处于RRC非激活态时，可以向第一UE发送NAS消息。接入网设备接收该NAS消息后，会寻呼第一UE。第一UE按照第二周期监听寻呼，则第一UE可以接收来自接入网设备的寻呼消息，该寻呼消息为接入网寻呼消息。第一UE接收该寻呼消息后，可以向接入网设备响应该寻呼消息。接入网设备接收来自第一UE的响应后，将该NAS消息发送给第一UE，这样第一UE就获得了该NAS消息。例如，第一UE如果接收了来自接入网设备的寻呼消息，可以向接入网设备发起随机接入，接入网设备接收了来自第一UE的随机接入前导码(preamble)，就视为接收了第一UE的响应。在随机接入成功后，接入网设备可以将该NAS消息发送给第一UE。或者，第一UE如果接收了来自接入网设备的寻呼消息，也可以不发起随机接入，而是通过其他方式响应接入网设备。另外，接入网设备在接收来自第一UE的响应后，也可以向核心网设备发送反馈信息，由于第二周期是核心网设备能够支持的，因此核心网设备能够在NAS定时信息规定的时间内接收该反馈信息，则核心网设备会认为NAS消息发送成功，无需通过核心网寻呼消息寻呼第一UE，第一UE也无需进入RRC空闲态后再发起随机接入，减小了NAS消息的传输时延，也减少了传输开销。
可选的，第一UE可以是该接入网设备服务的任一个UE，例如第一UE为redcap UE。对于其他的redcap UE，如果在处于RRC非激活态时能够支持的eDRX周期大于10.24s，则都可以适用本申请实施例的技术方案。即，通过本申请实施例的技术方案，可以为不同的redcap UE分别配置合适的eDRX周期，使得所配置的eDRX既满足UE接收NAS消息的需求，也更为符合UE的实际业务需求。
其中，在图4所示的实施例中，S41、S42、S46和S47都是可选的步骤，不是必须执行的。
通过本申请实施例提供的方法，可以基于接入网设备和核心网设备的自身情况为第一UE给出较为合理的eDRX周期，从而核心网设备如果要向第一UE发送NAS消息，可以按照第二周期来发送，使得第一UE按照第二周期能够正常接收来自核心网设备的NAS消息，无论第二周期是大于10.24s还是小于10.24s，通过本申请实施例的方法，都能提高UE接收NAS消息的概率，减小NAS消息的丢包率。而且核心网设备也不必因为NAS消息发送失败而寻呼第一UE，第一UE也不必进入RRC空闲态后再发起随机接入，减小了NAS消息的传输时延，也节省了传输资源。
本申请实施例提供第二种通信方法，请参考图5，为该方法的流程图。
S51、核心网设备向接入网设备发送第一消息，相应的，接入网设备接收来自核心网设备的第一消息。第一消息包括第一周期。第一周期是核心网设备为第一UE确定的eDRX周期，第一周期供第一UE在处于RRC非激活态时使用。
在本申请实施例中，核心网设备可以先确定核心网设备能够接受的第一周期，并将第 一周期发送给接入网设备。例如，核心网设备可根据NAS定时信息确定第一周期，关于NAS定时信息所包括的内容，可参考图4所示的实施例的介绍。
核心网设备根据NAS定时信息确定第一周期，例如可根据未调整的NAS定时信息确定第一周期，即，核心网设备不对NAS定时信息做任何调整，根据未调整的NAS定时信息确定第一周期。例如，第一周期的时间长度可以小于或等于未调整的NAS定时信息对应的第一阈值。或者，核心网设备也可以对NAS定时信息进行调整，并根据调整后的NAS定时信息确定第一周期。例如，第一周期的时间长度可以小于或等于调整后的NAS定时信息对应的第一阈值。例如，核心网设备按照最大调整幅度对NAS定时信息进行调整(例如，将NAS消息的最小重传时间间隔调整到核心网设备所能接受的最大值，和/或，将NAS消息的最大重传次数调整到核心网设备所能接受的最大值)，并根据调整后的NAS定时信息确定第一周期，这样确定的第一周期的时间长度更长，使得接入网设备在为第一UE进行配置时灵活度更高。关于第一阈值的介绍，可参考图4所示的实施例。
或者，核心网设备可根据NAS定时信息和第一UE的业务需求确定第一周期。也就是说，核心网设备在确定第一周期时也可以考虑第一UE的业务需求，从而使得所确定的第一周期更符合第一UE的应用。例如，核心网设备可根据未调整的NAS定时信息和第一UE的业务需求确定第一周期；或者，核心网设备也可以对NAS定时信息进行调整，并根据调整后的NAS定时信息和第一UE的业务需求确定第一周期。关于核心网设备调整NAS定时信息的方式，可参考前文的介绍。
或者，核心网设备可根据NAS定时信息和第一UE的能力确定第一周期。也就是说，核心网设备在确定第一周期时也可以考虑第一UE的能力，从而使得所确定的第一周期更符合第一UE的能力。例如，核心网设备可根据未调整的NAS定时信息和第一UE的能力确定第一周期；或者，核心网设备也可以对NAS定时信息进行调整，并根据调整后的NAS定时信息和第一UE的能力确定第一周期。关于核心网设备调整NAS定时信息的方式，可参考前文的介绍。
或者，核心网设备可根据NAS定时信息、第一UE的能力和第一UE的业务需求确定第一周期，等等。关于核心网设备确定第一周期时所考虑的因素，本申请实施例不做限制。
例如，在第一UE的注册过程中，核心网设备可以向接入网设备发送对应于第一UE的初始上下文建立请求消息，并将第一周期包括在该初始上下文建立请求消息中。该初始上下文建立请求消息中包括core network assistance information for RRC inactive，例如在该core network assistance information for RRC inactive中新增IE，该IE可承载第一周期。或者，该初始上下文建立请求消息可以包括UE Radio Capability for Paging IE，在UE Radio Capability for Paging IE内还可以包括UE radio paging information。第二周期例如通过UE radio paging information包括的第一字段承载，第一字段例如为空白字段。例如，UE radio paging information内包括一个或多个空白字段，第一字段可以是其中的一个。关于UE radio paging information，可参考图4所示的实施例的介绍。
或者，核心网设备也可以通过其他消息将第一周期发送给接入网设备。
S52、接入网设备根据第一周期确定第二周期。
接入网设备接收第一周期后，可以根据第一周期确定要为第一UE配置的、供第一UE在RRC非激活态下使用的eDRX周期，例如将接入网设备所确定的周期称为第二周期。其中，接入网设备所确定的第二周期的时间长度需要在核心网设备能够接受的范围之内， 因此第二周期的时间长度可以小于或等于第一周期的时间长度。从该角度来看，第一周期可以认为是核心网设备能够接受的、为第一UE配置的在RRC非激活态下使用的最大eDRX周期。
例如，接入网设备可根据第一周期和第一UE的能力确定第二周期，使得第二周期能够符合第一UE的能力；或者，接入网设备可根据第一周期和第一UE的业务需求确定第二周期，使得第二周期能够符合第一UE的业务需求；或者，接入网设备可根据第一周期、第一UE的能力和第一UE的业务需求确定第二周期，等等，对于接入网设备用于确定第二周期的因素不做限制。鉴于接入网设备能够根据UE的实际情况(例如业务需求或能力等)为该UE配置eDRX周期，因此接入网设备为不同的UE所确定的在RRC非激活态下使用的eDRX周期可能相同，也可能不同。
S53、接入网设备向核心网设备发送第二消息，相应的，核心网设备接收来自接入网设备的第二消息。第二消息包括第二周期。
接入网设备确定第二周期后，可通过第二消息将第二周期发送给核心网设备，以使得核心网设备获知实际为第一UE配置的第二周期，从而核心网设备可按照第二周期为处于RRC非激活态的第一UE发送NAS消息。
例如，接入网设备向核心网设备发送初始上下文建立响应消息，并将第二周期包括在该初始上下文建立响应消息中，即，该初始上下文建立响应消息可作为第二消息。例如在初始上下文建立响应消息中新增IE，该IE可承载第二周期。
S54、接入网设备向第一UE发送第三消息，相应的，第一UE接收来自接入网设备的第三消息。第三消息包括第二周期。
接入网设备为第一UE配置了第二周期，则接入网设备可以通过第三消息将第二周期发送给第一UE，也就是将第二周期配置给第一UE，从而第一UE在进入RRC非激活态后，可以使用第二周期来监听寻呼。
关于S54的更多内容，可参考图4所示的实施例中的S45。
S55、接入网设备向核心网设备发送RRC非激活态转换报告，相应的，核心网设备接收来自接入网设备的RRC非激活态转换报告。
RRC非激活态转换报告可以指示第一UE进入了RRC非激活态。
可选的，接入网设备也可以不通过初始上下文建立响应消息将第二周期发送给核心网设备，而是将第二周期包括在该RRC非激活态转换报告中发送给核心网设备。
S56、核心网设备按照第二周期向第一UE发送NAS消息，相应的，第一UE按照第二周期监听寻呼，从而接收该NAS消息。
关于S56的更多内容，可参考图4所示的实施例中的S47。
可选的，第一UE可以是该接入网设备服务的任一个UE，例如第一UE为redcap UE。对于其他的redcap UE，如果在处于RRC非激活态时能够支持的eDRX周期大于10.24s，则都可以适用本申请实施例的技术方案。例如，核心网设备可根据NAS定时信息和一个UE的业务需求为该UE确定第一周期，那么不同的UE的业务需求不同，则核心网设备为不同的UE确定的第一周期可能不同，相应的，接入网设备为不同的UE所配置的第二周期也就可能不同；又例如，核心网设备可根据NAS定时信息和一个UE的能力为该UE确定第一周期，那么不同的UE的能力不同，则核心网设备为不同的UE确定的第一周期可能不同，相应的，接入网设备为不同的UE所配置的第二周期也就可能不同。或者，即使 核心网设备为不同的UE所确定的第一周期相同(例如，核心网设备仅根据NAS定时信息确定第一周期，那么核心网设备为不同的UE所确定的第一周期可能相同)，但接入网设备在为一个UE确定第二周期时，可根据第一周期和该UE的能力确定第二周期，或者可根据第一周期和该UE的业务需求确定第二周期等，这样，接入网设备为不同的UE所配置的第二周期也可能不同。可见，通过本申请实施例的技术方案，可以为每个UE分别配置合适的eDRX周期，使得所配置的eDRX既满足UE接收NAS消息的需求，也更为符合UE的实际业务需求。
或者，也可以不必执行S53，即，接入网设备无需将第二周期发送给核心网设备，接入网设备只需根据第一周期为第一UE配置第二周期，并将第二周期配置给第一UE即可。如果是这种情况，则接入网设备在S54中发送给第一UE的消息可以称为第二消息，第二消息例如为RRC连接释放消息，或者也可以是其他消息。在这种情况下，则S56可以替换为：核心网设备按照第一周期向第一UE发送NAS消息，相应的，第一UE还是按照第二周期监听寻呼。通过这种方式，减少了接入网设备与核心网设备之间的交互过程，节省了信令开销。而且由于第二周期的时间长度小于或等于第一周期的时间长度，因此核心网设备按照第一周期发送NAS消息，第一UE是能够在eDRX周期内监听到的，不会影响第一UE对于NAS消息的接收。
其中，在图5所示的实施例中，S53、S55和S56都是可选的步骤，不是必须执行的。
在本申请实施例中，核心网设备先将核心网设备所能接受的上限值通知接入网设备，从而接入网设备在为第一UE配置在RRC非激活态下使用的eDRX周期时可以更为准确，减少了接入网设备重新确定为第一UE配置的eDRX周期的过程。接入网设备也会将最终确定的第二周期告知核心网设备，从而核心网设备如果要向第一UE发送NAS消息，可以按照第二周期来发送，使得第一UE按照第二周期能够正常接收来自核心网设备的NAS消息，无论第二周期是大于10.24s还是小于10.24s，通过本申请实施例的方法，都能提高UE接收NAS消息的概率，减小NAS消息的丢包率。而且核心网设备也不必因为NAS消息发送失败而寻呼第一UE，第一UE也不必进入RRC空闲态后再发起随机接入，减小了NAS消息的传输时延，也节省了传输资源。而且在本申请实施例中，核心网设备可将NAS定时信息作为考虑因素而给出eDRX周期上限值(例如，第一周期)让接入网设备作为参考，而不必让接入网设备考虑第一UE在RRC空闲态下使用的eDRX周期来为第一UE配置在RRC非激活态时使用的eDRX周期，使得为UE配置eDRX周期的方式更为灵活。
本申请实施例提供第三种通信方法，请参考图6，为该方法的流程图。
S61、核心网设备向接入网设备发送第一消息，相应的，接入网设备接收来自核心网设备的第一消息。第一消息包括第一周期。第一周期是核心网设备为多个UE确定的最大eDRX周期，且第一周期是这多个UE在处于RRC非激活态时使用的eDRX周期。可理解为，最终接入网设备为这多个UE配置的eDRX周期可以相同也可以不同，但都需要小于或等于第一周期。
本申请实施例中的第一周期是对应于多个UE的，例如这多个UE都是redcap UE。这多个UE可以包括该核心网设备和该接入网设备服务的全部redcap UE，也可以包括该核心网设备和该接入网设备服务的部分redcap UE。例如，核心网设备可根据NAS定时信息确定第一周期，关于核心网设备如何根据NAS定时信息确定第一周期等内容，可参考图5所示的实施例的介绍。
例如核心网设备为AMF，AMF可以向接入网设备发送AMF配置更新(AMF configuration update)消息，并将第一周期包括在该AMF配置更新消息中，即，AMF配置更新消息可作为第一消息。例如在该AMF配置更新消息中新增第一IE，第一IE可用来承载第一周期。
或者，在接入网设备与核心网设备尚未建立连接时，接入网设备可以向核心网设备发送NG接口建立请求(NG setup request)消息，以请求与核心网设备建立NG接口的连接。核心网设备接收来自接入网设备的NG接口建立请求消息后，可以向接入网设备发送NG接口建立响应(NG setup response)消息，以与接入网设备建立NG接口的连接。那么可选的，核心网设备也可以将第一周期包括在该NG接口建立响应消息中发送给接入网设备，即，NG接口建立响应消息可作为第一消息。例如在该NG接口建立响应消息中新增第二IE，第二IE可用来承载第一周期。
或者，核心网设备也可以通过其他消息将第一周期发送给接入网设备，因为本申请实施例中第一周期是对应于多个UE的，或者说并不特定对应于某一个或某几个UE，因此用于发送第一周期的消息可以与具体的UE无关(例如，该消息不包括任一个UE的标识)。
S62、接入网设备根据第一周期确定第二周期。
接入网设备接收第一周期后，可以根据第一周期确定要为这多个配置的、供这多个UE在RRC非激活态下使用的最大eDRX周期，例如将接入网设备所确定的周期称为第二周期。其中，接入网设备所确定的第二周期的时间长度需要在核心网设备能够接受的范围之内，因此第二周期的时间长度可以小于或等于第一周期的时间长度。也就是说，核心网设备对于这多个UE确定了一个eDRX周期上限值(即，第一周期)，接入网设备根据第一周期，可以确定实际为这多个UE配置的eDRX周期的上限值(即，第二周期)。
至于第二周期的时间长度究竟是等于第一周期的长度还是小于第一周期的长度，或者究竟比第一周期的时间长度小多少，取决于接入网设备的实现。例如，接入网设备可以根据第一周期确定第二周期，确定方式较为简单；或者，接入网设备可以根据第一周期以及这多个UE的业务需求确定第二周期，使得第二周期既能满足多个UE接收NAS消息的需求，也能满足这多个UE的业务需求；或者，接入网设备可以根据第一周期以及这多个UE的能力确定第二周期，使得第二周期既能满足多个UE接收NAS消息的需求，也能符合这多个UE的实际能力；或者，接入网设备也可以根据第一周期、这多个UE的业务需求以及这多个UE的能力确定第二周期，等等。
S63、接入网设备向核心网设备发送第二消息，相应的，核心网设备接收来自接入网设备的第二消息。第二消息包括第二周期。
接入网设备确定第二周期后，可通过第二消息将第二周期发送给核心网设备，以使得核心网设备获知实际为多个UE配置的第二周期，从而对于这多个UE中的任一个UE来说，在该UE处于RRC非激活态时，如果核心网设备要向该UE发送NAS消息，则核心网设备都可按照第二周期来发送。可见，在本申请实施例中，无论对于这多个UE中的哪个UE，核心网设备只需按照一种eDRX周期(即，第二周期)来向处于RRC非激活态的该UE发送NAS消息，核心网设备无需为每个UE分别维护不同的NAS消息，简化了核心网设备的实现。
例如，接入网设备向核心网设备发送AMF配置更新确认(AMF configuration update acknowledge)消息，并将第二周期包括在该AMF配置更新确认消息中，即，AMF配置更 新消息可作为第二消息。或者，接入网设备也可以通过其他消息将第二周期发送给核心网设备，例如在接入网设备与核心网设备建立NG接口的连接后，接入网设备可通过该NG接口向核心网设备发送相应的消息，并将第二周期包括在该消息中。由于本申请实施例的技术方案对应于多个UE，或者说，并不特定针对某个或某几个UE，因此用于发送第二周期的消息可以与UE无关，例如，该消息不包括UE的标识。
S64、接入网设备向第一UE发送第三消息，相应的，第一UE接收来自接入网设备的第三消息。第三消息包括第三周期。
接入网设备确定的第二周期，是能够配置给多个UE的eDRX周期的上限值。进一步的，接入网设备可根据第二周期以及其他一些因素，为多个UE中的不同的UE分别配置用于在RRC非激活态时使用的eDRX周期。接入网设备为这多个UE中的不同的UE所配置的用于在RRC非激活态时使用的eDRX周期，其时间长度可以相同，也可以不同。
例如对于这多个UE中的一个UE来说，接入网设备可以根据第二周期确定该UE在RRC非激活态时使用的eDRX周期，确定方式较为简单；或者，接入网设备可根据第二周期以及该UE的业务确定该UE在RRC非激活态时使用的eDRX周期，从而使得所配置的eDRX周期既能满足该UE接收NAS消息的需求，也能满足该UE的业务传输需求；或者，接入网设备可以根据第二周期以及该UE的能力确定该UE在RRC非激活态时使用的eDRX周期，使得所确定的eDRX周期既能满足多个UE接收NAS消息的需求，也能符合该UE的实际能力；或者，接入网设备也可以根据第二周期、该UE的业务需求以及该UE的能力确定该UE在RRC非激活态时使用的eDRX周期，等等。
第一UE是多个UE中的一个，例如接入网设备根据如上配置方式中的一种为第一UE配置了第三周期，第三周期是供第一UE在处于RRC非激活态时使用的eDRX周期。接入网设备可以通过第三消息将第三周期发送给第一UE，也就是将第三周期配置给第一UE，从而第一UE在进入RRC非激活态后，可以使用第三周期来监听寻呼。其中，第三周期的时间长度小于或等于第二周期的时间长度。
关于S64的更多内容，例如第三消息可通过何种消息实现等，可参考图4所示的实施例中的S45。
S65、接入网设备向第二UE发送第四消息，相应的，第二UE接收来自接入网设备的第四消息。第四消息包括第四周期。
第二UE是多个UE中的一个，第一UE与第二UE是不同的UE。例如接入网设备为第二UE配置了第四周期，第四周期是供第二UE在处于RRC非激活态时使用的eDRX周期。接入网设备可以通过第四消息将第四周期发送给第二UE，也就是将第四周期配置给第二UE，从而第二UE在进入RRC非激活态后，可以使用第四周期来监听寻呼。其中，第四周期的时间长度小于或等于第二周期的时间长度。且第三周期的时间长度与第四周期的时间长度可以相同，也可以不同。
关于S65的更多内容，例如接入网设备如何确定第四周期，以及第四消息可通过何种消息实现等，可参考图4所示的实施例中的S45。
另外，如果这多个UE除了包括第一UE和第二UE外还包括其他UE，那么接入网设备也可以分别为所述其他UE配置eDRX周期，配置方式都是类似的，不多赘述。
S66、接入网设备向核心网设备发送RRC非激活态转换报告，相应的，核心网设备接收来自接入网设备的RRC非激活态转换报告。
RRC非激活态转换报告可以指示第一UE进入了RRC非激活态。这多个UE中，不同的UE进入RRC非激活态的时间可能相同也可能不同，本申请实施例这里只是以其中的第一UE进入了RRC非激活态为例进行说明。
其中，S66可以发生在S65之前，或者S66可以与S65同时发生，或者S66可以发生在S65之后。
S67、核心网设备按照第二周期向第一UE发送NAS消息，相应的，第一UE按照第三周期监听寻呼，从而接收该NAS消息。
在本申请实施例中，无论接入网设备为UE配置何种长度的eDRX，核心网设备在向UE发送NAS消息时都按照第二周期来发送，从而核心网设备无需为不同的UE维护不同的eDRX周期，能够简化核心网设备的实现。
例如第三周期是接入网设备根据第二周期和第一UE的业务需求配置的，那么，由于第三周期的时间长度小于或等于第二周期的时间长度，如果核心网设备按照第二周期发送NAS消息，第一UE就能够在第三周期内监听到来自接入网设备的寻呼，从而能够正确接收该NAS消息，能够满足NAS消息的接收需求。另外，由于第三周期与第一UE的业务需求有关，因此第一UE按照第三周期监听寻呼，也能满足第一UE的业务传输需求。
关于S67的更多内容，可参考图4所示的实施例中的S47。
另外，如果接入网设备是通过RRC连接释放消息将第四周期发送给第二UE，该RRC连接释放消息用于将第二UE释放到RRC非激活态，那么第二UE也会根据该RRC连接释放消息进入RRC非激活态，则接入网设备也会向核心网设备发送对应于第二UE的RRC非激活态转换报告，指示第二UE进入了RRC非激活态。如果核心网设备需要向处于RRC非激活态的第二UE发送NAS消息，就会按照第二周期来发送，而第二UE会按照第四周期监听寻呼。因为过程都是类似的，因此不多赘述。
其中，在图6所示的实施例中，S66和S67都是可选的步骤，不是必须执行的。
在本申请实施例中，核心网设备先将核心网设备所能接受的上限值通知接入网设备，从而接入网设备在为多个UE配置在RRC非激活态下使用的eDRX周期时可以更为准确，减少了接入网设备重新确定为多个UE配置的eDRX周期的过程。接入网设备也会将最终确定的第二周期告知核心网设备，从而核心网设备如果要向多个UE中的任一个UE发送NAS消息，都可以按照第二周期来发送，使得这多个UE都能正常接收来自核心网设备的NAS消息，无论第二周期是大于10.24s还是小于10.24s，通过本申请实施例的方法，都能提高UE接收NAS消息的概率，减小NAS消息的丢包率。核心网设备也不必因为NAS消息发送失败而寻呼第一UE，第一UE也不必进入RRC空闲态后再发起随机接入，减小了业务传输时延，也节省了传输资源。而且对于这多个UE中的任一个UE，核心网设备都可以按照第二周期发送NAS消息，无需为不同的UE维护不同的eDRX周期，简化了核心网设备的实现过程。
本申请实施例提供第四种通信方法，请参考图7，为该方法的流程图。
S71、核心网设备向接入网设备发送第一消息，相应的，接入网设备接收来自核心网设备的第一消息。第一消息包括第一周期。第一周期是核心网设备为多个UE确定的最大eDRX周期，且第一周期是这多个UE在处于RRC非激活态时使用的eDRX周期。可理解为，最终接入网设备为这多个UE配置的eDRX周期可以相同也可以不同，但都需要小于或等于第一周期。
关于S71的更多内容，可参考图6所示的实施例中对于S61的介绍。
S72、接入网设备根据第一周期为第一UE确定第二周期。
接入网设备接收第一周期后，可以根据第一周期分别为不同的UE确定在RRC非激活态时使用的eDRX周期。可选的，接入网设备可根据第一周期以及其他一些因素，为多个UE中的不同的UE分别配置用于在RRC非激活态时使用的eDRX周期。接入网设备为这多个UE中的不同的UE所配置的用于在RRC非激活态时使用的eDRX周期，其时间长度可以相同，也可以不同。
例如对于这多个UE中的一个UE来说，接入网设备可以根据第一周期确定该UE在RRC非激活态时使用的eDRX周期，确定方式较为简单；或者，接入网设备可根据第一周期以及该UE的业务确定该UE在RRC非激活态时使用的eDRX周期，从而使得所配置的eDRX周期既能满足该UE接收NAS消息的需求，也能满足该UE的业务传输需求；或者，接入网设备可以根据第一周期以及该UE的能力确定该UE在RRC非激活态时使用的eDRX周期，使得所确定的eDRX周期既能满足多个UE接收NAS消息的需求，也能符合该UE的实际能力；或者，接入网设备也可以根据第一周期、该UE的业务需求以及该UE的能力确定该UE在RRC非激活态时使用的eDRX周期，等等。
第一UE是多个UE中的一个，例如接入网设备根据如上配置方式中的一种为第一UE配置了第二周期，第二周期是供第一UE在处于RRC非激活态时使用的eDRX周期。
S73、接入网设备向第一UE发送第二消息，相应的，第一UE接收来自接入网设备的第二消息。第二消息包括第二周期。
接入网设备可以通过第二消息将第二周期发送给第一UE，也就是将第二周期配置给第一UE，从而第一UE在进入RRC非激活态后，可以使用第二周期来监听寻呼。其中，第二周期的时间长度小于或等于第一周期的时间长度。
关于S73的更多内容，例如第二消息可通过何种消息实现等，可参考图4所示的实施例中的S45。
S74、接入网设备根据第一周期为第二UE确定第三周期。
第二UE是多个UE中的一个，例如接入网设备根据如上配置方式中的一种为第二UE配置了第三周期，第三周期是供第二UE在处于RRC非激活态时使用的eDRX周期。关于S74的更多内容，例如接入网设备如何确定第三周期等，可参考S72的介绍。
S75、接入网设备向第二UE发送第三消息，相应的，第二UE接收来自接入网设备的第三消息。第三消息包括第三周期。
接入网设备可以通过第三消息将第三周期发送给第二UE，也就是将第三周期配置给第二UE，从而第二UE在进入RRC非激活态后，可以使用第三周期来监听寻呼。其中，第三周期的时间长度小于或等于第一周期的时间长度。
关于S75的更多内容，例如第三消息可通过何种消息实现等，可参考图4所示的实施例中的S45。
另外，如果这多个UE除了包括第一UE和第二UE外还包括其他UE，那么接入网设备也可以分别为所述其他UE配置eDRX周期，配置方式都是类似的，不多赘述。
S76、接入网设备向核心网设备发送RRC非激活态转换报告，相应的，核心网设备接收来自接入网设备的RRC非激活态转换报告。
RRC非激活态转换报告可以指示第一UE进入了RRC非激活态。这多个UE中，不同 的UE进入RRC非激活态的时间可能相同也可能不同，本申请实施例这里只是以其中的第一UE进入了RRC非激活态为例进行说明。
S77、核心网设备按照第一周期向第一UE发送NAS消息，相应的，第一UE按照第二周期监听寻呼，从而接收该NAS消息。
在本申请实施例中，无论接入网设备为UE配置何种长度的eDRX，核心网设备在向UE发送NAS消息时都按照第一周期来发送，从而核心网设备无需为不同的UE维护不同的eDRX周期，能够简化核心网设备的实现。
例如第二周期是接入网设备根据第一周期和第一UE的业务需求配置的，那么，由于第二周期的时间长度小于或等于第一周期的时间长度，如果核心网设备按照第一周期发送NAS消息，第一UE就能够在第二周期内监听到来自接入网设备的寻呼，从而能够正确接收该NAS消息，能够满足NAS消息的接收需求。另外，由于第二周期与第一UE的业务需求有关，因此第一UE按照第二周期监听寻呼，也能满足第一UE的业务传输需求。
关于S77的更多内容，可参考图4所示的实施例中的S47。
另外，如果接入网设备是通过RRC连接释放消息将第三周期发送给第二UE，该RRC连接释放消息用于将第二UE释放到RRC非激活态，那么第二UE也会根据该RRC连接释放消息进入RRC非激活态，则接入网设备也会向核心网设备发送对应于第二UE的RRC非激活态转换报告，指示第二UE进入了RRC非激活态。如果核心网设备需要向处于RRC非激活态的第二UE发送NAS消息，也会按照第一周期来发送，而第二UE会按照第三周期监听寻呼。因为过程都是类似的，因此不多赘述。
其中，在图7所示的实施例中，S76和S77都是可选的步骤，不是必须执行的。
在本申请实施例中，核心网设备将核心网设备所能接受的上限值通知接入网设备，接入网设备可根据该上限值为不同的UE配置eDRX周期，从而接入网设备在为多个UE配置在RRC非激活态下使用的eDRX周期时可以更为准确，减少了接入网设备重新确定为多个UE配置的eDRX周期的过程。核心网设备如果要向多个UE中的任一个UE发送NAS消息，都可以按照第一周期来发送，使得这多个UE都能正常接收来自核心网设备的NAS消息，无论第一周期是大于10.24s还是小于10.24s，通过本申请实施例的方法，都能提高UE接收NAS消息的概率，减小NAS消息的丢包率。核心网设备也不必因为NAS消息发送失败而寻呼第一UE，第一UE也不必进入RRC空闲态后再发起随机接入，减小了业务传输时延，也节省了传输资源。而且对于这多个UE中的任一个UE，核心网设备都可以按照第二周期发送NAS消息，无需为不同的UE维护不同的eDRX周期，简化了核心网设备的实现过程。
下面结合附图介绍本申请实施例中用来实现上述方法的装置。因此，上文中的内容均可以用于后续实施例中，重复的内容不再赘述。
图8为本申请实施例提供的通信装置800的示意性框图。示例性地，通信装置800例如为终端设备，或者为网络设备。示例性地，通信装置800能够实现图4所示的实施例或图5所示的实施例或图6所示的实施例或图7所示的实施例所述的第一终端设备的功能。或者，通信装置800能够实现图4所示的实施例或图5所示的实施例或图6所示的实施例或图7所示的实施例所述的接入网设备的功能。或者，通信装置800能够实现图4所示的实施例或图5所示的实施例或图6所示的实施例或图7所示的实施例所述的核心网设备的功能。
通信装置800包括收发单元820和处理单元810。可选地，通信装置800还可以包括存储单元，存储单元能够与处理单元810通信，在图7中并未表示出来。或者，通信装置800也可以不包括存储单元，存储单元也可以位于通信装置800外部。示例性地，通信装置800可以是第一终端设备，也可以是应用于第一终端设备中的芯片或者其他具有上述第一终端设备功能的组合器件、部件等，或者，通信装置800可以是网络设备(例如，接入网设备或核心网设备)，也可以是应用于网络设备中的芯片或者其他具有上述网络设备(例如，接入网设备或核心网设备)功能的组合器件、部件等。当通信装置800是第一终端设备或网络设备时，处理单元810可以包括处理器，例如基带处理器，基带处理器中可以包括一个或多个中央处理单元(central processing unit，CPU)；收发单元820可以是收发器，收发器可以包括天线和射频电路等。其中，收发器可包括发射器和接收器，收发器可实现发射器和接收器的功能，或者，发射器和接收器也可以是单独部署的两个功能模块，只是本申请实施例将这两个功能模块统称为收发器。当通信装置800是具有上述第一终端设备或网络设备功能的部件时，收发单元820可以是射频单元，处理单元810可以是处理器，例如基带处理器。当通信装置800是芯片系统时，收发单元820可以是芯片(例如基带芯片)的输入输出接口、处理单元810可以是芯片系统的处理器，可以包括一个或多个中央处理单元。应理解，本申请实施例中的处理单元810可以由处理器或处理器相关电路组件实现，收发单元820可以由收发器或收发器相关电路组件实现。
在一种实施方式中，当通信装置800用于实现图4所示的实施例所述的第一终端设备的功能时，处理单元810可以用于执行图4所示的实施例中由第一终端设备所执行的除了收发操作之外的全部操作，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图4所示的实施例中由第一终端设备所执行的全部接收操作和发送操作，例如S45和S47，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图4所示的实施例所述的接入网设备的功能时，处理单元810可以用于执行图4所示的实施例中由接入网设备所执行的除了收发操作之外的全部操作，例如S42，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图4所示的实施例中由接入网设备所执行的全部接收操作和发送操作，例如S41以及S43～S47，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图4所示的实施例所述的核心网设备的功能时，处理单元810可以用于执行图4所示的实施例中由核心网设备所执行的除了收发操作之外的全部操作，例如确定第二周期的操作，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图4所示的实施例中由核心网设备所执行的全部接收操作和发送操作，例如S41、S43、S44、S46以及S47，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图5所示的实施例所述的第一终端设备的功能时，处理单元810可以用于执行图5所示的实施例中由第一终端设备所执行的除了收发操作之外的全部操作，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图5所示的实施例中由第一终端设备所执行的全部接收操作和发送操作，例如S54和S56，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图5所示的实施例所述的接入网设备的功能时，处理单元810可以用于执行图5所示的实施例中由接入网设备所执行的除了收发 操作之外的全部操作，例如S52，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图5所示的实施例中由接入网设备所执行的全部接收操作和发送操作，例如S51以及S53～S56，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图5所示的实施例所述的核心网设备的功能时，处理单元810可以用于执行图5所示的实施例中由核心网设备所执行的除了收发操作之外的全部操作，例如确定第一周期的操作，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图5所示的实施例中由核心网设备所执行的全部接收操作和发送操作，例如S51、S53、S55以及S56，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图6所示的实施例所述的第一终端设备的功能时，处理单元810可以用于执行图6所示的实施例中由第一终端设备所执行的除了收发操作之外的全部操作，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图6所示的实施例中由第一终端设备所执行的全部接收操作和发送操作，例如S64和S67，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图6所示的实施例所述的接入网设备的功能时，处理单元810可以用于执行图6所示的实施例中由接入网设备所执行的除了收发操作之外的全部操作，例如S62，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图6所示的实施例中由接入网设备所执行的全部接收操作和发送操作，例如S61以及S63～S67，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图6所示的实施例所述的核心网设备的功能时，处理单元810可以用于执行图6所示的实施例中由核心网设备所执行的除了收发操作之外的全部操作，例如确定第一周期的操作，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图6所示的实施例中由核心网设备所执行的全部接收操作和发送操作，例如S61、S63、S66以及S67，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图7所示的实施例所述的第一终端设备的功能时，处理单元810可以用于执行图7所示的实施例中由第一终端设备所执行的除了收发操作之外的全部操作，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图7所示的实施例中由第一终端设备所执行的全部接收操作和发送操作，例如S73和S77，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图7所示的实施例所述的接入网设备的功能时，处理单元810可以用于执行图7所示的实施例中由接入网设备所执行的除了收发操作之外的全部操作，例如S72和S74，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图7所示的实施例中由接入网设备所执行的全部接收操作和发送操作，例如S71、S73以及S75～S77，和/或用于支持本文所描述的技术的其它过程。
在一种实施方式中，当通信装置800用于实现图7所示的实施例所述的核心网设备的功能时，处理单元810可以用于执行图7所示的实施例中由核心网设备所执行的除了收发操作之外的全部操作，例如确定第一周期的操作，和/或用于支持本文所描述的技术的其它过程。收发单元820可以用于执行图7所示的实施例中由核心网设备所执行的全部接收操作和发送操作，例如S71、S76以及S77，和/或用于支持本文所描述的技术的其它过程。
另外，收发单元820可以是一个功能模块，该功能模块既能完成发送操作也能完成接收操作，例如收发单元820可以用于执行图4所示的实施例或图5所示的实施例或图6所示的实施例或图7所示的实施例中由第一终端设备或网络设备(例如，核心网设备或接入网设备)所执行的全部发送操作和接收操作。例如，在执行接收操作时，可以认为收发单元820是接收单元，而在执行发送操作时，可以认为收发单元820是发送单元。或者，收发单元820也可以是两个功能模块，收发单元820可以视为这两个功能模块的统称，这两个功能模块包括接收单元和发送单元，发送单元用于完成发送操作，例如发送单元可以用于执行图4所示的实施例或图5所示的实施例或图6所示的实施例或图7所示的实施例中由第一终端设备或网络设备所执行的全部发送操作；接收单元用于完成接收操作，例如接收单元可以用于执行图4所示的实施例或图5所示的实施例或图6所示的实施例或图7所示的实施例中由第一终端设备或网络设备所执行的全部接收操作。
关于处理单元810和收发单元820所具体能够实现的功能，可参考图4所示的实施例或图5所示的实施例或图6所示的实施例或图7所示的实施例中对于终端设备所执行的操作的介绍，或者参考图4所示的实施例或图5所示的实施例或图6所示的实施例或图7所示的实施例中对于网络设备(例如，接入网设备或核心网设备)所执行的操作的介绍，不多赘述。
本申请实施例还提供一种通信装置，该通信装置可以是终端设备也可以是电路。该通信装置可以用于执行上述各个方法实施例中由终端设备所执行的动作。
当该通信装置为终端设备时，图9示出了一种简化的终端设备的结构示意图。便于理解和图示方便，图9中，终端设备以手机作为例子。如图9所示，终端设备包括处理器、存储器、射频电路、天线以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理，以及对终端设备进行控制，执行软件程序，处理软件程序的数据等。存储器主要用于存储软件程序和数据。射频电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。需要说明的是，有些种类的终端设备可以不具有输入输出装置。
当需要发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。为便于说明，图9中仅示出了一个存储器和处理器。在实际的终端设备产品中，可以存在一个或多个处理器和一个或多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以是独立于处理器设置，也可以是与处理器集成在一起，本申请实施例对此不做限制。
在本申请实施例中，可以将具有收发功能的天线和射频电路视为终端设备的收发单元(收发单元可以是一个功能单元，该功能单元能够实现发送功能和接收功能；或者，收发单元也可以包括两个功能单元，分别为能够实现接收功能的接收单元和能够实现发送功能的发送单元)，将具有处理功能的处理器视为终端设备的处理单元。如图9所示，终端设备包括收发单元910和处理单元920。收发单元也可以称为收发器、收发机、收发装置等。处理单元也可以称为处理器，处理单板，处理模块、处理装置等。可选的，可以将收发单 元910中用于实现接收功能的器件视为接收单元，将收发单元910中用于实现发送功能的器件视为发送单元，即收发单元910包括接收单元和发送单元。收发单元有时也可以称为收发机、收发器、或收发电路等。接收单元有时也可以称为接收机、接收器、或接收电路等。发送单元有时也可以称为发射机、发射器或者发射电路等。
应理解，收发单元910用于执行上述图4所示的实施例或图5所示的实施例或图6所示的实施例或图7所示的实施例中终端设备侧的发送操作和接收操作，处理单元920用于执行上述图4所示的实施例或图5所示的实施例或图6所示的实施例或图7所示的实施例中第一终端设备侧除了收发操作之外的其他操作。
当该通信装置为芯片类的装置或者电路时，该装置可以包括收发单元和处理单元。其中，所述收发单元可以是输入输出电路和/或通信接口；处理单元为集成的处理器或者微处理器或者集成电路。
应理解，本申请实施例中提及的处理器可以是CPU，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现 有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的计算机可读存储介质，可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括随机存取存储器(random access memory，RAM)、只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦可编程只读存储器(electrically erasable programmable read only memory，EEPROM)、紧凑型光盘只读存储器(compact disc read-only memory，CD-ROM)、通用串行总线闪存盘(universal serial bus flash disk)、移动硬盘、或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。另外，通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)或直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
以上所述，仅为本申请的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应所述以权利要求的保护范围为准。

Claims (32)

  1. 一种通信方法，其特征在于，包括：
    核心网设备根据非接入层NAS定时信息确定第一周期，所述第一周期是能够为第一终端设备配置的最大扩展的非连续接收eDRX周期，且所述第一周期是所述第一终端设备在处于无线资源控制RRC非激活态时使用的；
    在第一终端设备的注册过程中，核心网设备向接入网设备发送初始上下文建立请求消息，所述初始上下文建立请求消息包括所述第一终端设备的上下文信息，以及，所述初始上下文请求消息还包括所述第一周期；
    所述接入网设备接收所述初始上下文建立请求消息，根据所述初始上下文建立请求消息携带的所述第一周期确定第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；
    所述接入网设备向所述核心网设备发送初始上下文建立响应消息，所述初始上下文建立响应消息包括所述第二周期；
    在所述第一终端设备注册完毕，且所述接入网设备未检测到所述第一终端设备的数据传输时，所述接入网设备启动RRC连接释放定时器；
    在所述RRC连接释放定时器超时时，所述接入网设备向所述第一终端设备发送RRC连接释放消息，所述RRC连接释放消息包括所述第二周期；
    在所述第一终端设备处于RRC非激活态的情况下，所述第一终端设备按照所述第二周期监听寻呼。
  2. 一种通信方法，其特征在于，包括：
    接入网设备接收来自核心网设备的第一消息，所述第一消息包括第一周期，所述第一周期是能够为第一终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；
    所述接入网设备根据所述第一周期确定第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；
    所述接入网设备向所述核心网设备发送第二消息，所述第二消息包括所述第二周期。
  3. 根据权利要求2所述的方法，其特征在于，
    所述第一消息为初始上下文建立请求消息；和/或，
    所述第二消息为初始上下文建立响应消息，或，所述第二消息为RRC非激活态转换报告。
  4. 根据权利要求2或3所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向所述第一终端设备发送第三消息，所述第三消息包括所述第二周期。
  5. 根据权利要求4所述的方法，其特征在于，所述第三消息为RRC连接释放消息，所述RRC连接释放消息用于将所述第一终端设备释放到所述RRC非激活态。
  6. 根据权利要求1～5任一项所述的方法，其特征在于，所述接入网设备根据所述第一周期为不同的终端设备配置的在处于所述RRC非激活态时使用的eDRX周期的长度不同。
  7. 根据权利要求1～6任一项所述的方法，其特征在于，所述第一终端设备为redcap UE。
  8. 一种通信方法，其特征在于，包括：
    核心网设备向接入网设备发送第一消息，所述第一消息包括第一周期，所述第一周期是能够为第一终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的；
    所述核心网设备接收来自所述接入网设备的第二消息，所述第二消息包括第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于所述RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度。
  9. 根据权利要求8所述的方法，其特征在于，所述第一周期是根据NAS定时信息确定的，所述NAS定时信息包括NAS消息的最小重传时间间隔和/或NAS消息的最大重传次数。
  10. 根据权利要求8或9所述的方法，其特征在于，
    所述第一消息为初始上下文建立请求消息；和/或，
    所述第二消息为初始上下文建立响应消息，或所述第二消息为RRC非激活态转换报告。
  11. 根据权利要求8～10任一项所述的方法，其特征在于，所述方法还包括：
    所述核心网设备接收来自所述接入网设备的RRC非激活态转换报告，所述RRC非激活态转换报告用于指示所述第一终端设备进入所述RRC非激活态；
    所述核心网设备按照所述第二周期向所述第一终端设备发送NAS消息。
  12. 根据权利要求8～11任一项所述的方法，其特征在于，所述第一终端设备为redcap UE。
  13. 一种通信方法，其特征在于，包括：
    第一终端设备接收来自接入网设备的第三消息，所述第三消息包括第二周期，所述第二周期是为所述第一终端设备配置的eDRX周期，且所述第二周期是所述第一终端设备在处于RRC非激活态时使用的，其中，所述第二周期是所述接入网设备根据第一周期确定的，所述第一周期是所述核心网设备能够为所述第一终端设备配置的最大eDRX周期，且所述第一周期是所述第一终端设备在处于RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；
    在所述第一终端设备处于RRC非激活态的情况下，所述第一终端设备按照所述第二周期监听寻呼。
  14. 根据权利要求13所述的方法，其特征在于，所述第二消息为RRC连接释放消息，所述RRC连接释放消息用于将所述第一终端设备释放到所述RRC非激活态。
  15. 根据权利要求13或14所述的方法，其特征在于，所述第一终端设备为redcap UE。
  16. 一种通信方法，其特征在于，包括：
    接入网设备接收来自核心网设备的第一消息，所述第一消息包括第一周期，所述第一周期是能够为终端设备配置的最大eDRX周期，且所述第一周期是所述终端设备在处于RRC非激活态时使用的；
    所述接入网设备根据所述第一周期确定第二周期，所述第二周期是为终端设备配置的最大eDRX周期，且所述第二周期是所述终端设备在处于所述RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度；
    所述接入网设备向所述核心网设备发送第二消息，所述第二消息包括所述第二周期。
  17. 根据权利要求16所述的方法，其特征在于，所述第一消息为AMF配置更新消息，所述第二消息为AMF配置更新确认消息；或，所述第一消息为NG接口建立响应消息。
  18. 根据权利要求16或17所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向所述终端设备中的第一终端设备发送第三消息，所述第三消息包括第三周期，所述第三周期的长度小于或等于所述第二周期的长度，所述第三周期是为所述第一终端设备配置的eDRX周期，且所述第三周期是所述第一终端设备在处于所述RRC非激活态时使用的；
    所述接入网设备向所述终端设备中的第二终端设备发送第四消息，所述第四消息包括第四周期，所述第四周期的长度小于或等于所述第二周期的长度，所述第四周期是为所述第二终端设备配置的eDRX周期，且所述第三周期是所述第一终端设备在处于所述RRC非激活态时使用的；
    其中，所述第三周期的长度与所述第四周期的长度相同或不同。
  19. 根据权利要求16～18任一项所述的方法，其特征在于，所述接入网设备根据所述第一周期为不同的终端设备确定的所述第二周期的长度不同。
  20. 根据权利要求16～19任一项所述的方法，其特征在于，所述终端设备为redcap UE。
  21. 一种通信方法，其特征在于，包括：
    核心网设备向接入网设备发送第一消息，所述第一消息包括第一周期，所述第一周期是能够为终端设备配置的最大eDRX周期，且所述第一周期是所述终端设备在处于RRC非激活态时使用的；
    所述核心网设备接收来自所述接入网设备的第二消息，所述第二消息包括第二周期，所述第二周期是为终端设备配置的最大eDRX周期，且所述第二周期是所述终端设备在处于所述RRC非激活态时使用的，所述第二周期的长度小于或等于所述第一周期的长度。
  22. 根据权利要求21所述的方法，其特征在于，所述第一周期是根据NAS定时信息确定的，所述NAS定时信息包括NAS消息的最小重传时间间隔和/或NAS消息的最大重传次数。
  23. 根据权利要求21或22所述的方法，其特征在于，所述第一消息为AMF配置更新消息，所述第二消息为AMF配置更新确认消息；或，所述第一消息为NG接口建立响应消息。
  24. 根据权利要求21～23任一项所述的方法，其特征在于，所述方法还包括：
    所述核心网设备接收来自所述接入网设备的RRC非激活态转换报告，所述RRC非激活态转换报告用于指示所述第一终端设备进入所述RRC非激活态；
    所述核心网设备按照所述第二周期向所述终端设备中的第一终端设备发送NAS消息，所述第一终端设备是所述接入网设备覆盖的任一个终端设备。
  25. 根据权利要求21～24任一项所述的方法，其特征在于，所述终端设备为redcap UE。
  26. 一种通信方法，其特征在于，包括：
    第一终端设备接收来自接入网设备的第三消息，所述第三消息包括第三周期，所述第三周期是为所述第一终端设备配置的eDRX周期，且所述第三周期是所述第一终端设备在处于RRC非激活态时使用的，其中，所述第三周期是所述接入网设备根据第一周期和第二周期确定的，所述第一周期是所述核心网设备能够为多个终端设备配置的最大eDRX周期，且所述第一周期是所述多个终端设备在处于RRC非激活态时使用的，所述第二周期 是所述接入网设备为所述多个终端设备配置的最大eDRX周期，且所述第二周期是所述多个终端设备在处于RRC非激活态时使用的，所述第二周期是根据所述第一周期确定的，所述第二周期的长度小于或等于所述第一周期的长度，所述多个终端设备包括所述第一终端设备；
    在所述第一终端设备处于RRC非激活态的情况下，所述第一终端设备按照所述第三周期监听寻呼。
  27. 根据权利要求26所述的方法，其特征在于，所述第三消息为RRC连接释放消息，所述RRC连接释放消息用于将所述第一终端设备释放到所述RRC非激活态。
  28. 根据权利要求26或27所述的方法，其特征在于，所述第一终端设备为redcap UE。
  29. 一种网络设备，其特征在于，包括：
    一个或多个处理器；
    一个或多个存储器；
    以及一个或多个计算机程序，其中所述一个或多个计算机程序被存储在所述一个或多个存储器中，所述一个或多个计算机程序包括指令，当所述指令被所述网络设备的一个或多个处理器执行时，使得所述网络设备执行如权利要求1中由接入网设备或核心网设备所执行的方法，或使得所述网络设备执行如权利要求2～7中任一项所述的方法，或使得所述网络设备执行如权利要求8～12中任一项所述的方法，或使得所述网络设备执行如权利要求16～20中任一项所述的方法，或使得所述网络设备执行如权利要求21～25中任一项所述的方法。
  30. 一种终端设备，其特征在于，包括：
    一个或多个处理器；
    一个或多个存储器；
    以及一个或多个计算机程序，其中所述一个或多个计算机程序被存储在所述一个或多个存储器中，所述一个或多个计算机程序包括指令，当所述指令被所述终端设备的一个或多个处理器执行时，使得所述终端设备执行如权利要求1中由第一终端设备所执行的方法，或使得所述终端设备执行如权利要求13～15中任一项任一所述的方法，或使得所述终端设备执行如权利要求26～28中任一项任一所述的方法。
  31. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1所述的方法，或使得所述计算机执行如权利要求2～7中任一项所述的方法，或者使得所述计算机执行如权利要求8～12中任一项所述的方法，或者使得所述计算机执行如权利要求13～15中任一项所述的方法，或者使得所述计算机执行如权利要求16～20中任一项所述的方法，或者使得所述计算机执行如权利要求21～25中任一项所述的方法，或者使得所述计算机执行如权利要求26～28中任一项所述的方法。
  32. 一种芯片，其特征在于，包括一个或多个处理器和通信接口，所述一个或多个处理器用于读取指令，以执行权利要求1所述的方法，或者执行权利要求2～7中任一项所述的方法，或者执行权利要求8～12中任一项所述的方法，或者执行权利要求13～15中任一项所述的方法，或者执行权利要求16～20中任一项所述的方法，或者执行权利要求21～25中任一项所述的方法，或者执行权利要求26～28中任一项所述的方法。
PCT/CN2021/114558 2020-10-09 2021-08-25 一种通信方法及设备 WO2022073395A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21876915.6A EP4210429A4 (en) 2020-10-09 2021-08-25 COMMUNICATION METHOD AND DEVICE
US18/248,109 US20230403757A1 (en) 2020-10-09 2021-08-25 Communication Method and Device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202011075522 2020-10-09
CN202011075522.X 2020-10-09
CN202011148865.4A CN114340043A (zh) 2020-10-09 2020-10-23 一种通信方法及设备
CN202011148865.4 2020-10-23

Publications (1)

Publication Number Publication Date
WO2022073395A1 true WO2022073395A1 (zh) 2022-04-14

Family

ID=81031845

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/114558 WO2022073395A1 (zh) 2020-10-09 2021-08-25 一种通信方法及设备

Country Status (4)

Country Link
US (1) US20230403757A1 (zh)
EP (1) EP4210429A4 (zh)
CN (1) CN114340043A (zh)
WO (1) WO2022073395A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117641624A (zh) * 2022-08-09 2024-03-01 华为技术有限公司 一种通信方法和通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014071551A1 (zh) * 2012-11-06 2014-05-15 华为技术有限公司 寻呼ue的方法、基站及ue
US20180263011A1 (en) * 2016-04-27 2018-09-13 Telefonaktiebolaget Lm Ericsson (Publ) Method and device for handling paging extension
CN110149680A (zh) * 2018-02-11 2019-08-20 北京三星通信技术研究有限公司 省电处理方法、服务器、基站及终端设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140041305A (ko) * 2012-09-27 2014-04-04 삼성전자주식회사 사용자 단말에서 데이터 송수신 장치 및 방법
WO2018063467A1 (en) * 2016-09-30 2018-04-05 Intel IP Corporation Configuration of discontinuous reception (drx) parameters in light connection
CN109041269B (zh) * 2018-08-02 2020-09-11 中国联合网络通信集团有限公司 一种确定eDRX周期的方法及通信装置
CN110913506B (zh) * 2018-09-14 2022-04-01 大唐移动通信设备有限公司 一种下行数据的缓存方法、upf实体及amf实体
CN115086987A (zh) * 2021-03-12 2022-09-20 华为技术有限公司 通信方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014071551A1 (zh) * 2012-11-06 2014-05-15 华为技术有限公司 寻呼ue的方法、基站及ue
US20180263011A1 (en) * 2016-04-27 2018-09-13 Telefonaktiebolaget Lm Ericsson (Publ) Method and device for handling paging extension
CN110149680A (zh) * 2018-02-11 2019-08-20 北京三星通信技术研究有限公司 省电处理方法、服务器、基站及终端设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Discussion on REDCAP eDRX cycles", 3GPP DRAFT; R3-212060, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-meeting; 20210517 - 20210528, 7 May 2021 (2021-05-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052002297 *
See also references of EP4210429A4 *

Also Published As

Publication number Publication date
EP4210429A4 (en) 2024-06-05
US20230403757A1 (en) 2023-12-14
CN114340043A (zh) 2022-04-12
EP4210429A1 (en) 2023-07-12

Similar Documents

Publication Publication Date Title
WO2019232732A1 (zh) 一种寻呼消息传输方法和相关设备
WO2018137284A1 (zh) 一种传输寻呼消息的方法及装置
CN112514528B (zh) 用于5g蜂窝物联网的用户平面优化
US20220361284A1 (en) Communication method and apparatus
WO2021180098A1 (zh) 无线通信方法和通信装置
WO2020191781A1 (zh) 一种数据传输方法及装置
US20240314696A1 (en) Communication method and communication apparatus
WO2018112871A1 (zh) 数据发送/接收装置、方法以及通信系统
EP4009691A1 (en) Communication method, method for establishing slrb, and communication apparatus
CN111919465B (zh) 用于早期传输数据的传输块大小选择
US20230038417A1 (en) Data transmission method and apparatus
US20240349367A1 (en) Communication method and communication apparatus
WO2022188751A1 (zh) 通信方法及装置
US20240236946A1 (en) Communication method and device
CN108430070A (zh) 一种无线资源控制连接方法及设备、计算机存储介质
WO2022078321A1 (zh) 上行信息发送方法及相关产品
WO2022073395A1 (zh) 一种通信方法及设备
US20230337319A1 (en) Methods, devices, and systems for configuring sidelink drx
CN111683414A (zh) 一种连接配置的实现方法、用户设备和存储介质
EP4383930A2 (en) Methods, devices, and systems for configuring sidelink drx
WO2022063186A1 (zh) 传输链路的切换方法及相关产品
WO2021207899A1 (zh) 信息发送方法、用户设备、基站设备及计算机存储介质
WO2024093531A1 (zh) 通信方法及相关装置
WO2023103958A1 (zh) 一种通信方法及装置
WO2022257796A1 (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: 21876915

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021876915

Country of ref document: EP

Effective date: 20230406

NENP Non-entry into the national phase

Ref country code: DE