A communication method and device

Abstract

The application relates to a communication method and device. An access network device receives a first period from a core network device, the first period is a maximum eDRX period that can be configured for a first terminal device, and the first period is used by the first terminal device when in an RRC inactive state. The access network device determines a second period according to the first period, the second period is an eDRX period configured for the first terminal device, and the second period is used by the first terminal device when in the RRC inactive state, the length of the second period is less than or equal to the length of the first period. The access network device sends a second message to the core network device, the second message comprising the second period. The second period determined by the access network device according to the first period meets the requirements of the core network device, the core network device sends a NAS message according to the second period, and the first terminal device can normally receive the NAS message according to the second period, thereby improving the probability of the terminal device receiving the NAS message.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese patent application filed on October 9, 2020, with application number 202011075522.X, entitled "A Communication Method for UE2NW Relay, UE and Network Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and device. Background Technology

[0004] Discontinuous reception (DRX) saves power by allowing the user equipment (UE) to remain in sleep mode most of the time through discontinuous signal reception. Since packet-based data streams are generally bursty, power consumption can be reduced by shutting down the UE's receive circuitry when there is no data transmission. Extended discontinuous reception (eDRX) is an extended version of DRX. In each eDRX cycle, the UE can only receive downlink data during a set paging time window (PTW). Outside of the PTW, the UE remains in sleep mode.

[0005] Currently, only UEs with enhanced machine-type communication (eMTC) can use the eDRX mechanism when in an inactive state of radio resource control (RRC). Other UEs, such as long-term evolution (LTE) UEs or new radio (NR) UEs, cannot use the eDRX mechanism when in an inactive state of RRC. Furthermore, narrowband internet of things (NB-IoT) UEs do not have an inactive state of RRC, therefore, it is not true that they cannot use the eDRX mechanism when in an inactive state of RRC.

[0006] Currently, reduced capability UEs (redcap UEs) have been proposed, which are a type of UE with lower capabilities compared to legacy UEs. Redcap UEs belong to NR UEs, but for energy saving, it is currently being discussed that redcap UEs can use the eDRX mechanism even when RRC is inactive.

[0007] For eMTC UEs, the currently specified maximum supported eDRX period length is 10.24 seconds (s) when in RRC inactive state. If redcap UEs also use the eDRX mechanism in RRC inactive state, the maximum supported eDRX period length may exceed 10.24 seconds. If the base station configures the eDRX period for redcap UEs to be too long in RRC inactive state, the redcap UE may fail to receive non-access stratum (NAS) messages sent by the core network equipment due to the excessively long eDRX period. This is a problem that needs to be addressed. Summary of the Invention

[0008] This application provides a communication method and device to improve the probability of a UE successfully receiving NAS messages.

[0009] Firstly, a communication method is provided, comprising: when a first terminal device is in an RRC idle state, if a core network device obtains downlink data from the first terminal device, the core network device sends a paging message to an access network device, the paging message being used to page the first terminal device, and the paging message further including an eDRX period used by the first terminal device when in the RRC idle state; the access network device receives the paging message, determines a first period based on the eDRX period used by the first terminal device when in the RRC idle state carried in the paging message, the first period being an eDRX period expected to be configured for the first terminal device, and the first period being used by the first terminal device when in an RRC inactive state; the access network device sends the paging message to the first terminal device; the first terminal device receives the paging message and establishes an RRC connection with the access network device based on the paging message; and upon the establishment of the RRC connection... After successful completion, the access network device sends an initial UE message to the core network device, the initial UE message including the first cycle; the core network device determines a second cycle based on the first cycle and NAS timing information, the second cycle being the eDRX cycle determined by the core network device for the first terminal device, and the second cycle being used by the first terminal device when it is in the RRC inactive state; the core network device sends an initial context establishment request message to the access network device, the initial context establishment request message including the second cycle; when the access network device does not detect UE data transmission, the access network device starts an RRC connection release timer; when the RRC connection release timer expires, the access network device sends an RRC connection release message to the first terminal device, the RRC connection release message including the second cycle; when the first terminal device is in the RRC inactive state, the first terminal device listens for paging according to the second cycle.

[0010] In this embodiment, the access network device and the core network device can negotiate to determine a second period, which is the eDRX period that can be configured for the first terminal device to use in the RRC inactive state. In this way, a more reasonable eDRX period can be determined based on the specific circumstances of the access network device and the core network device. Therefore, if the core network device needs to send NAS messages to the first terminal device, it can send them according to the second period. Thus, regardless of whether the second period is less than or equal to 10.24s or greater than 10.24s, the first terminal device can normally receive NAS messages from the core network device according to the second period, increasing the probability of the terminal device receiving NAS messages, reducing the packet loss rate of NAS messages, and correspondingly reducing the transmission latency of NAS messages.

[0011] Secondly, a second communication method is provided, which can be executed by an access network device or by a chip system capable of implementing the functions of the access network device. Exemplarily, the access network device is a base station. The method includes: the access network device sending a first message to a core network device, the first message including a first period, the first period being an eDRX period expected to be configured for a first terminal device, and the first period being used by the first terminal device when it is in an RRC inactive state; the access network device receiving a second message from the core network device, the second message including a second period, the second period being an eDRX period determined by the core network device for the first terminal device, and the second period being used by the first terminal device when it is in the RRC inactive state, the length of the second period being the same as or different from the first period.

[0012] In this embodiment, the access network device and the core network device can negotiate to determine a second period, which is the eDRX period that can be configured for the first terminal device to use in the RRC inactive state. In this way, a more reasonable eDRX period can be determined based on the specific circumstances of the access network device and the core network device. Therefore, if the core network device needs to send NAS messages to the first terminal device, it can send them according to the second period. Thus, regardless of whether the second period is less than or equal to 10.24s or greater than 10.24s, the first terminal device can normally receive NAS messages from the core network device according to the second period, increasing the probability of the terminal device receiving NAS messages, reducing the packet loss rate of NAS messages, and correspondingly reducing the transmission latency of NAS messages.

[0013] In conjunction with the second aspect, in a first optional implementation of the second aspect, if 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, if 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 based on the NAS timing information.

[0014] The first threshold is determined based on either the unadjusted NAS timing information or the adjusted NAS timing information. By adjusting the NAS timing information, the core network equipment can increase the acceptable duration, allowing for a longer eDRX cycle configured for the UE and more flexible configuration. The first threshold can be considered the acceptable duration for the core network equipment; if this duration is exceeded, it becomes unacceptable. Therefore, based on the first threshold and the first cycle, the length of the second cycle can be determined, ensuring it remains within the acceptable range for the core network equipment.

[0015] In conjunction with the first optional implementation of the second aspect, in the second optional implementation of the second aspect, the NAS timing information includes the minimum retransmission interval of the NAS message and / or the maximum number of retransmissions of the NAS message.

[0016] For example, NAS timing information includes the minimum retransmission interval of NAS messages, or the maximum number of retransmissions of NAS messages, or both the minimum retransmission interval and the maximum number of retransmissions of NAS messages.

[0017] In conjunction with the second aspect or the first optional implementation of the second aspect or the second optional implementation of the second aspect, in the third optional implementation of the second aspect, the first message is an initial UE message.

[0018] Access network devices can send the first cycle to core network devices via the initial UE message. For example, by adding an IE to the initial UE message, the first cycle can be carried by this newly added IE. Sending the first cycle to the access network device using existing messages eliminates the need for additional messages, saving signaling overhead. Alternatively, access network devices can also send the first cycle to core network devices via other messages.

[0019] In conjunction with any of the optional embodiments of the second aspect or the first to third optional embodiments of the second aspect, in the fourth optional embodiment of the second aspect, the second message is an initial context establishment request message.

[0020] The core network equipment can also send the second cycle to the access network equipment using existing messages, such as an Initial Context Establishment Request message. This Initial Context Establishment Request message may include the UE Radio Capability for Paging IE, which may also include UE radio paging information. The UE radio paging information includes some blank fields, and the second cycle is carried, for example, through one or more of these blank fields, thus making reasonable use of the blank fields.

[0021] In conjunction with any of the optional embodiments of the second aspect or the first to fourth optional embodiments of the second aspect, in the fifth optional embodiment of the second aspect, the method further includes: the access network device receiving first information from the core network device, the first information including the eDRX cycle used by the first terminal device when it is in the RRC idle state; the access network device determining the first cycle based on the eDRX cycle used by the first terminal device when it is in the RRC idle state.

[0022] The core network equipment can send the eDRX cycle used by the first terminal equipment when it is in the RRC idle state to the access network equipment, so that the access network equipment can determine the first cycle based on the eDRX cycle.

[0023] In conjunction with the fifth alternative implementation of the second aspect, in the sixth alternative implementation of the second aspect, the first information is included in the paging message.

[0024] The core network equipment can send the first information to the access network equipment through a paging message. This paging message is a core network paging message, for example, the paging message is used to page the first terminal equipment.

[0025] In conjunction with any of the optional embodiments of the second aspect or the first to sixth optional embodiments of the second aspect, in the seventh optional embodiment of the second aspect, the method further includes: the access network device sending the third message to the first terminal device, the third message including the second cycle.

[0026] After the access network device determines the second cycle, it can configure the second cycle to the first terminal device, so that the first terminal device can use the second cycle after entering the RRC inactive state.

[0027] In conjunction with the seventh optional implementation of the second aspect, in the eighth optional implementation of the second aspect, the access network device sends the second cycle to the first terminal device, including: the third message is an RRC connection release message, the RRC connection release message being used to release the first terminal device to the RRC inactive state.

[0028] The RRC connection release message is used to release the first terminal device into the RRC inactive state. The second cycle is also used by the first terminal device when it is in the RRC inactive state. Therefore, sending the second cycle to the first terminal device via the RRC connection release message ensures its timely application. Furthermore, the RRC connection release message can both release the first terminal device into the RRC inactive state and configure the second cycle for it, improving message utilization. Since no additional message needs to be sent to configure the second cycle for the first terminal device, transmission overhead is also reduced.

[0029] In conjunction with any of the optional embodiments of the second aspect or the first to the eighth optional embodiments of the second aspect, in the ninth optional embodiment of the second aspect, the first terminal device is a redcap UE.

[0030] The first terminal device can be any terminal device served by the access network device, such as a redcap UE. For other redcap UEs besides the first terminal device, if the eDRX period supported in the RRC inactive state is greater than 10.24s, then the technical solution of this application embodiment can also be applied. That is, through the technical solution of this application embodiment, suitable eDRX periods can be configured for different redcap UEs, so that the configured eDRX not only meets the terminal device's requirement to receive NAS messages, but also better meets the actual service requirements of the terminal device.

[0031] Thirdly, a third communication method is provided. This method can be executed by a core network device or by a chip system capable of implementing the functions of the core network device. For example, the core network device is an AMF (Advanced Management Function). The method includes: the core network device receiving a first message from an access network device, the first message including a first period, the first period being an eDRX period that the access network device expects to configure for a first terminal device, and the first period being used by the first terminal device when it is in an RRC (Remote Reduction Control) inactive state; the core network device sending a second message to the access network device, the second message including a second period, the first period being an eDRX period that the access network device expects to configure for the first terminal device, and the first period being used by the first terminal device when it is in an RRC inactive state, wherein the second period is determined based on the first period and NAS (Non-Standard Access Memory) timing information, and the length of the second period may be the same as or different from the first period.

[0032] In conjunction with the third aspect, in a first optional implementation of the third aspect, the second period is determined based on the first period and NAS timing information, including: when the length of the first period is less than or equal to a 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 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 based on the NAS timing information.

[0033] In conjunction with the first optional implementation of the third aspect, in the second optional implementation of the third aspect, the NAS timing information includes the minimum retransmission time interval of the NAS message and / or the maximum number of retransmissions of the NAS message.

[0034] In conjunction with the third aspect or the first optional implementation of the third aspect or the second optional implementation of the third aspect, in the third optional implementation of the third aspect, the first message is an initial UE message.

[0035] In conjunction with any of the optional embodiments of the third aspect or the first to the third optional embodiments of the third aspect, in the fourth optional embodiment of the third aspect, the second message is an initial context establishment request message.

[0036] In conjunction with the third aspect, or the first optional implementation of the third aspect, or the fourth optional implementation of the third aspect, in the fifth optional implementation of the third aspect, the method further includes: the core network device sending first information to the access network device, the first information being used to determine the first period, wherein the first information includes the eDRX period used by the first terminal device when it is in the RRC idle state.

[0037] In conjunction with the fifth alternative implementation of the third aspect, in the sixth alternative implementation of the third aspect, the first information is included in the paging message.

[0038] In conjunction with any of the optional embodiments of the third aspect or the first to sixth optional embodiments of the third aspect, in the seventh optional embodiment of the third aspect, the method further includes: the core network device receiving an RRC inactive state transition report from the access network device, the RRC inactive state transition report being used to indicate that the first terminal device enters the RRC inactive state; the core network device sending a NAS message to the first terminal device according to the second cycle.

[0039] In conjunction with any of the optional embodiments of the third aspect or the first to seventh optional embodiments of the third aspect, in the eighth optional embodiment of the third aspect, the first terminal device is a redcap UE.

[0040] For information on the technical effects of the third aspect or its various alternative implementations, please refer to the description of the technical effects of the second aspect or its corresponding implementations.

[0041] Fourthly, a fourth communication method is provided, which can be executed by a first terminal device or by a chip system capable of implementing the functions of the first terminal device. The method includes: the first terminal device receiving a third message from an access network device, the third message including a second period, the second period being an eDRX period configured for the first terminal device, and the second period being used by the first terminal device when it is in an RRC inactive state, wherein the second period is determined through negotiation between the access network device and the core network device; when the first terminal device is in an RRC inactive state, the first terminal device listens for paging according to the second period.

[0042] In conjunction with the fourth aspect, in a first optional implementation of the fourth aspect, the second message is an RRC connection release message, which is used to release the first terminal device to the RRC inactive state.

[0043] In conjunction with the fourth aspect or the first optional implementation of the fourth aspect, in the second optional implementation of the fourth aspect, the first terminal device is a redcap UE.

[0044] For the technical effects of the fourth aspect or various alternative implementations of the fourth aspect, please refer to the description of the technical effects of the second aspect or corresponding implementations, or refer to the description of the technical effects of the third aspect or corresponding implementations.

[0045] Fifthly, a fifth communication method is provided, comprising: a core network device determining a first period based on NAS timing information, wherein the first period is the maximum eDRX period that can be configured for a first terminal device, and the first period is used by the first terminal device when it is in an 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, the initial context establishment request message including context information of the first terminal device, and the initial context request message also including the first period; the access network device receiving the initial context establishment request message, determining a second period based on the first period carried in the initial context establishment request message, wherein the second period is the eDRX period configured for the first terminal device, and... The second cycle is used by the first terminal device when it is in an 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 device sends an initial context establishment response message to the core network device, and the initial context establishment response message includes the second cycle. When the first terminal device has completed registration and the access network device has not detected data transmission from the first terminal device, the access network device starts an RRC connection release timer. 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 cycle. When the first terminal device is in an RRC inactive state, the first terminal device listens for paging according to the second cycle.

[0046] In this embodiment, the core network device first notifies the access network device of the upper limit value it can accept. This allows the access network device to configure the eDRX period for the first terminal device in the RRC inactive state more accurately, reducing the process of the access network device re-determining the eDRX period for the first terminal device. The access network device also informs the core network device of the final determined second period. Therefore, if the core network device needs to send a NAS message to the first terminal device, it can send it according to the second period. This ensures that the first terminal device can normally receive the NAS message from the core network device according to the second period, regardless of whether the second period is greater than or less than 10.24s. The method in this embodiment increases the probability of the terminal device receiving the NAS message and reduces the packet loss rate of the NAS message. Furthermore, the core network device does not need to page the first terminal device due to NAS message transmission failure, and the first terminal device does not need to enter the RRC idle state before initiating random access, reducing service transmission latency and saving transmission resources. Furthermore, in this embodiment, the core network device can take NAS timing information into account when determining the first cycle, without having to consider the eDRX cycle used by the first terminal device in the RRC idle state. This makes the determination of the first cycle more flexible, allowing for a longer first cycle, and also meets the requirements of the core network device.

[0047] A sixth aspect provides a sixth communication method, which can be executed by an access network device or by a chip system capable of implementing the functions of the access network device. Exemplarily, the access network device is a base station. The method includes: the access network device receiving a first message from a core network device, the first message including a first period, the first period being a maximum eDRX period configurable for a first terminal device, and the first period being used by the first terminal device when it is in an RRC inactive state; the access network device determining a second period based on the first period, the second period being an eDRX period configured for the first terminal device, and the second period being used by the first terminal device when it is in an RRC inactive state, the length of the second period being less than or equal to the length of the first period; the access network device sending a second message to the core network device, the second message including the second period.

[0048] In this embodiment, the core network device first notifies the access network device of the upper limit value it can accept. This allows the access network device to configure the eDRX period for the first terminal device in the RRC inactive state more accurately, reducing the process of the access network device re-determining the eDRX period for the first terminal device. The access network device also informs the core network device of the final determined second period. Therefore, if the core network device needs to send a NAS message to the first terminal device, it can send it according to the second period. This ensures that the first terminal device can normally receive the NAS message from the core network device according to the second period, regardless of whether the second period is greater than or less than 10.24s. The method in this embodiment increases the probability of the terminal device receiving the NAS message and reduces the packet loss rate of the NAS message. Furthermore, the core network device does not need to page the first terminal device due to NAS message transmission failure, and the first terminal device does not need to enter the RRC idle state before initiating random access, reducing service transmission latency and saving transmission resources. Furthermore, in this embodiment, the core network device can take NAS timing information into account when determining the first cycle, without having to consider the eDRX cycle used by the first terminal device in the RRC idle state. This makes the determination of the first cycle more flexible, allowing for a longer first cycle, and also meets the requirements of the core network device.

[0049] In conjunction with the sixth aspect, in the first alternative implementation of the sixth aspect,

[0050] The first message is an initial context establishment request message; and / or,

[0051] The second message is an initial context establishment response message, or the second message is an RRC inactive state transition report.

[0052] 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 can be sent using existing messages without adding any additional messages, thus enabling the technical solution of this application embodiment to be better compatible with existing technologies. Alternatively, the first or second cycle can also be sent using other messages, such as newly added dedicated messages, to minimize the impact on the functionality of existing messages.

[0053] In conjunction with the sixth aspect or the first optional implementation of the sixth aspect, in the second optional implementation of the sixth aspect, the method further includes: the access network device sending a third message to the first terminal device, the third message including the second period.

[0054] After the access network device determines the second cycle, it can configure the second cycle to the first terminal device, so that the first terminal device can use the second cycle after entering the RRC inactive state.

[0055] In conjunction with the second optional implementation of the sixth aspect, in the third optional implementation of the second aspect, the third message is an RRC connection release message, which is used to release the first terminal device to the RRC inactive state.

[0056] The RRC connection release message is used to release the first terminal device into the RRC inactive state. The second cycle is also used by the first terminal device when it is in the RRC inactive state. Therefore, sending the second cycle to the first terminal device via the RRC connection release message ensures its timely application. Furthermore, the RRC connection release message can both release the first terminal device into the RRC inactive state and configure the second cycle for it, improving message utilization. Since no additional message needs to be sent to configure the second cycle for the first terminal device, transmission overhead is also reduced.

[0057] In conjunction with any of the sixth aspect or the first to third optional embodiments of the sixth aspect, in the fourth optional embodiment of the second aspect, the access network device configures different lengths of the eDRX period used by different terminal devices when in the RRC inactive state according to the first period.

[0058] For example, the access network device can determine the second period based on the first period and the capabilities of the first UE, so that the second period can meet the capabilities of the first UE; or, the access network device can determine the second period based on the first period and the service requirements of the first UE, so that the second period can meet the service requirements of the first UE; or, the access network device can determine the second period based on the first period, the capabilities of the first UE, and the service requirements of the first UE, etc. There are no restrictions on the factors used by the access network device to determine the second period. Given that the access network device can configure the eDRX period for the UE based on its actual situation (e.g., service requirements or capabilities), the eDRX period determined by the access network device for different UEs and used in the RRC inactive state may be the same or different.

[0059] In conjunction with any of the optional embodiments of the sixth aspect or the first to fourth optional embodiments of the sixth aspect, in the fifth optional embodiment of the second aspect, the first terminal device is a redcap UE.

[0060] The first terminal device can be any terminal device served by the access network device, such as a redcap UE. For other redcap UEs besides the first terminal device, if the eDRX period supported in the RRC inactive state is greater than 10.24s, then the technical solution of this application embodiment can also be applied. That is, through the technical solution of this application embodiment, suitable eDRX periods can be configured for different redcap UEs, so that the configured eDRX not only meets the terminal device's requirement to receive NAS messages, but also better meets the actual service requirements of the terminal device.

[0061] A seventh aspect provides a seventh communication method, which can be executed by a core network device or by a chip system capable of implementing the functions of the core network device. Exemplarily, the core network device is an AMF (Advanced Feature Controller). The method includes: the core network device sending a first message to an access network device, the first message including a first period, the first period being a maximum eDRX period configurable for a first terminal device, and the first period being used by the first terminal device when it is in an RRC (Remote Reduction Control) inactive state; the core network device receiving a second message from the access network device, the second message including a second period, the second period being an eDRX period configured for the first terminal device, and the second period being used by the first terminal device when it is in the RRC inactive state, the length of the second period being less than or equal to the length of the first period.

[0062] In conjunction with the seventh aspect, in a first optional implementation of the seventh aspect, the first period is determined based on NAS timing information, which includes the minimum retransmission time interval of NAS messages and / or the maximum number of retransmissions of NAS messages.

[0063] For example, core network equipment can determine the first period based on NAS timing information. Compared to determining the first period based on the eDRX period used by the first terminal device in RRC idle state, determining the first period based on NAS timing information allows for a longer duration, giving access network equipment greater flexibility in configuring the first terminal device, and the first period also meets the requirements of the core network equipment. Alternatively, core network equipment can consider other factors besides NAS timing information when determining the first period. For example, the core network equipment can determine the first period based on NAS timing information and the service requirements of the first terminal device. This ensures that the first period not only meets the first terminal device's need to receive NAS messages but also satisfies its service requirements.

[0064] In conjunction with the seventh aspect or the first optional implementation of the seventh aspect, in the second optional implementation of the seventh aspect,

[0065] The first message is an initial context establishment request message; and / or,

[0066] The second message is either an initial context establishment response message or an RRC inactive state transition report.

[0067] In conjunction with the seventh aspect, or the first optional implementation of the seventh aspect, or the second optional implementation of the seventh aspect, in the third optional implementation of the seventh aspect, the method further includes: the core network device receiving an RRC inactive state transition report from the access network device, the RRC inactive state transition report being used to indicate that the first terminal device enters the RRC inactive state; the core network device sending a NAS message to the first terminal device according to the second cycle.

[0068] In conjunction with any of the optional embodiments of the seventh aspect or the first to third optional embodiments of the seventh aspect, in the fourth optional embodiment of the seventh aspect, the first terminal device is a redcap UE.

[0069] For the technical effects of the seventh aspect or the various alternative implementations of the seventh aspect, please refer to the description of the technical effects of the sixth aspect or the corresponding implementation.

[0070] Eighthly, an eighth communication method is provided, which can be executed by a first terminal device or by a chip system capable of implementing the functions of the first terminal device. The method includes: the first terminal device receiving a third message from an access network device, the third message including a second period, the second period being an eDRX period configured for the first terminal device, and the second period being used by the first terminal device when it is in an RRC inactive state, wherein the second period is determined by the access network device based on a first period, the first period being the maximum eDRX period that the core network device can configure for the first terminal device, and the first period being used by the first terminal device when it is in an RRC inactive state, and the length of the second period being less than or equal to the length of the first period; when the first terminal device is in an RRC inactive state, the first terminal device listens for paging according to the second period.

[0071] In conjunction with the eighth aspect, in a first optional implementation of the eighth aspect, the second message is an RRC connection release message, which is used to release the first terminal device to the RRC inactive state.

[0072] In conjunction with the eighth aspect or the first optional implementation of the eighth aspect, in the second optional implementation of the eighth aspect, the first terminal device is a redcap UE.

[0073] For the technical effects of the eighth aspect or the various alternative implementations of the eighth aspect, please refer to the description of the technical effects of the sixth aspect or the corresponding implementation, or refer to the description of the technical effects of the seventh aspect or the corresponding implementation.

[0074] A ninth aspect provides a ninth communication method, which can be executed by an access network device or by a chip system capable of implementing the functions of the access network device. Exemplarily, the access network device is a base station. The method includes: the access network device receiving a first message from a core network device, the first message including a first period, the first period being a maximum eDRX period configurable for a terminal device, and the first period being used by the first terminal device when it is in an RRC inactive state; the access network device determining a second period based on the first period, the second period being a maximum eDRX period configurable for the terminal device, and the second period being used by the terminal device when it is in the RRC inactive state, the length of the second period being less than or equal to the length of the first period; the access network device sending a second message to the core network device, the second message including the second period.

[0075] In this embodiment, the core network device first notifies the access network device of the upper limit value it can accept. This allows the access network device to configure the eDRX period for multiple terminal devices in the RRC inactive state more accurately, reducing the process of re-determining the eDRX period for multiple terminal devices. The access network device also informs the core network device of the final determined second period. Therefore, if the core network device wants to send a NAS message to any of the multiple terminal devices, it can send it according to the second period, ensuring that all terminal devices can normally receive the NAS message from the core network device. Regardless of whether the second period is greater than or less than 10.24s, the method in this embodiment increases the probability of terminal devices receiving NAS messages and reduces the packet loss rate of NAS messages. The core network device also does not need to page the terminal device due to NAS message transmission failure, and the terminal device does not need to enter the RRC idle state before initiating random access, reducing service transmission latency and saving transmission resources. Moreover, the core network device can send NAS messages according to the second cycle for any of these terminal devices, without having to maintain different eDRX cycles for different terminal devices, which simplifies the implementation process of the core network device.

[0076] In conjunction with the ninth aspect, in a first optional implementation of the ninth aspect, the first message is an AMF configuration update message and the second message is an AMF configuration update confirmation message; or, the first message is an NG interface establishment response message.

[0077] 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 can be sent using existing messages without adding any additional messages, thus enabling the technical solution of this application embodiment to be better compatible with existing technologies. Alternatively, the first or second cycle can also be sent using other messages, such as newly added dedicated messages, to minimize the impact on the functionality of existing messages.

[0078] In conjunction with the ninth aspect or the first optional implementation of the ninth aspect, in the second optional implementation of the ninth aspect, the method further includes: the access network device sending a third message to a first terminal device among the terminal devices, the third message including a third period, the length of the third period being less than or equal to the length of the second period, the third period being an eDRX period configured for the first terminal device, and the third period being used by the first terminal device when it is in the RRC inactive state; the access network device sending a fourth message to a second terminal device among the terminal devices, the fourth message including a fourth period, the length of the fourth period being less than or equal to the length of the second period, the fourth period being an eDRX period configured for the second terminal device, and the third period being used by the first terminal device when it 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.

[0079] The second period determined by the access network device is the upper limit of the eDRX period that can be configured for multiple terminal devices. Furthermore, the access network device can configure different eDRX periods for use in the RRC inactive state for different terminal devices among the multiple terminal devices based on the second period and other factors. For example, for one of these terminal devices, the access network device can determine the eDRX period used by that terminal device in the RRC inactive state based on the second period, a relatively simple determination method; or, the access network device can determine the eDRX period used by that terminal device in the RRC inactive state based on the second period and the terminal device's services, thus ensuring that the configured eDRX period meets both the terminal device's needs for receiving NAS messages and its service transmission needs, and so on. Since different terminal devices have different circumstances (e.g., capabilities or service requirements), the eDRX periods determined by the access network device for different terminal devices in the RRC inactive state may be the same or different. 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 cycle configured by the access network device when in the RRC inactive state.

[0080] In conjunction with the ninth aspect, or the first optional implementation of the ninth aspect, or the second optional implementation of the ninth aspect, in the third optional implementation of the ninth aspect, the access network device determines the length of the second period differently depending on the first period being for different terminal devices.

[0081] In conjunction with the ninth aspect or the first optional implementation of the ninth aspect or the second optional implementation of the ninth aspect or the third optional implementation of the ninth aspect, in the fourth optional implementation of the ninth aspect, the terminal device is a redcap UE.

[0082] The technical solution of this application embodiment can configure appropriate eDRX periods for different redcap UEs, so that the configured eDRX not only meets the terminal device's need to receive NAS messages, but also better meets the actual service needs of the terminal device.

[0083] A tenth aspect provides a tenth communication method, which can be executed by a core network device or by a chip system capable of implementing the functions of the core network device. Exemplarily, the core network device is an AMF (Advanced Feature Controller). The method includes: the core network device sending a first message to an access network device, the first message including a first period, the first period being a maximum eDRX period configurable for a terminal device, and the first period being used by the terminal device when it is in an RRC (Remote Reduction Control) inactive state; the core network device receiving a second message from the access network device, the second message including a second period, the second period being a maximum eDRX period configurable for the terminal device, and the second period being used by the terminal device when it is in the RRC inactive state, the length of the second period being less than or equal to the length of the first period.

[0084] In conjunction with the tenth aspect, in a first optional implementation of the tenth aspect, the first period is determined based on NAS timing information, which includes the minimum retransmission time interval of NAS messages and / or the maximum number of retransmissions of NAS messages.

[0085] In conjunction with the tenth aspect or the first optional implementation of the tenth aspect, in the second optional implementation of the tenth aspect, the first message is an AMF configuration update message and the second message is an AMF configuration update confirmation message; or, the first message is an NG interface establishment response message.

[0086] In conjunction with the tenth aspect, or the first optional implementation of the tenth aspect, or the second optional implementation of the tenth aspect, in the third optional implementation of the tenth aspect, the method further includes: the core network device receiving an RRC inactive state transition report from the access network device, the RRC inactive state transition report being used to indicate that the first terminal device enters the RRC inactive state; the core network device sending a NAS message to the first terminal device among the terminal devices according to the second period, the first terminal device being any terminal device covered by the access network device.

[0087] In conjunction with the tenth aspect, or the first optional implementation of the tenth aspect, or the second optional implementation of the tenth aspect, or the third optional implementation of the tenth aspect, in the fourth optional implementation of the tenth aspect, the terminal device is a redcap UE.

[0088] For the technical effects of the tenth aspect or various alternative embodiments of the tenth aspect, please refer to the description of the technical effects of the ninth aspect or corresponding embodiments, or refer to the description of the technical effects of the seventh aspect or corresponding embodiments.

[0089] Eleventhly, an eleventh communication method is provided, which can be executed by a first terminal device or by a chip system capable of implementing the functions of the first terminal device. The method includes: the first terminal device receiving a third message from an access network device, the third message including a third period, the third period being an eDRX period configured for the first terminal device, and the third period being used by the first terminal device when it is in an RRC inactive state, wherein the third period is determined by the access network device based on a first period and a second period, the first period being the maximum eDRX period that the core network device can configure for multiple terminal devices, and the first period being used by the multiple terminal devices when they are in an RRC inactive state, the second period being the maximum eDRX period configured by the access network device for the multiple terminal devices, and the second period being used by the multiple terminal devices when they are in an RRC inactive state, the second period being determined based on the first period, the length of the second period being less than or equal to the length of the first period, and the multiple terminal devices including the first terminal device; when the first terminal device is in an RRC inactive state, the first terminal device listens for paging according to the third period.

[0090] In conjunction with the eleventh aspect, in the first optional implementation of the eleventh aspect, the third message is an RRC connection release message, which is used to release the first terminal device to the RRC inactive state.

[0091] In conjunction with the eleventh aspect or the first optional implementation of the eleventh aspect, in the first optional implementation of the eleventh aspect, the first terminal device is a redcap UE.

[0092] For the technical effects of the eleventh aspect or the various alternative embodiments of the eleventh aspect, please refer to the description of the technical effects of the ninth aspect or the corresponding embodiments, or refer to the description of the technical effects of the tenth aspect or the corresponding embodiments.

[0093] In a twelfth aspect, a twelfth communication method is provided, which can be executed by an access network device or by a chip system capable of implementing the functions of the access network device. Exemplarily, the access network device is a base station. The method includes: the access network device receiving a first message from a core network device, the first message including a first period, the first period being a maximum eDRX period configurable for a terminal device, and the first period being used by the terminal device when it is in an RRC inactive state; the access network device determining a second period based on the first period, the second period being a maximum eDRX period configured for a first terminal device among the terminal devices, and the second period being used by the first terminal device when it is in the RRC inactive state, the length of the second period being less than or equal to the length of the first period; the access network device sending a second message to the first terminal device, the second message including the second period.

[0094] In this embodiment, the core network device notifies the access network device of the upper limit value it can accept. The access network device can configure eDRX periods for different UEs based on this upper limit value. This allows the access network device to configure eDRX periods for multiple UEs in the RRC inactive state more accurately, reducing the process of re-determining the eDRX periods for multiple UEs. If the core network device needs to send a NAS message to any of the multiple UEs, it can send it according to the first period, ensuring that all UEs can receive the NAS message from the core network device normally, regardless of whether the first period is greater than or less than 10.24s. The method in this embodiment increases the probability of UE receiving NAS messages and reduces the packet loss rate of NAS messages. The core network device also does not need to page the first UE due to NAS message transmission failure, and the first UE does not need to enter the RRC idle state before initiating random access, reducing service transmission latency and saving transmission resources. Moreover, for any one of these UEs, the core network equipment can send NAS messages according to the second cycle, without having to maintain different eDRX cycles for different UEs, which simplifies the implementation process of the core network equipment.

[0095] In conjunction with the twelfth aspect, in a first alternative implementation of the twelfth aspect, the first message is an AMF configuration update message, or the first message is an NG interface establishment response message.

[0096] In conjunction with the twelfth aspect or the first optional implementation of the twelfth aspect, in the second optional implementation of the twelfth aspect, the method further includes: the access network device determining a third period based on the first period, the third period being the maximum eDRX period configured for the second terminal device in the terminal devices, and the third period being used by the second terminal device when it is in the RRC inactive state, the length of the third period being less than or equal to the length of the first period; the access network device sending a third message to the second terminal device, the third message including the third period; wherein the length of the second period is the same as or different from the length of the third period.

[0097] In conjunction with the twelfth aspect, or the first optional implementation of the twelfth aspect, or the second optional implementation of the twelfth aspect, in the third optional implementation of the twelfth aspect, the length of the eDRX period determined by the access network device for different terminal devices according to the first period.

[0098] In conjunction with the twelfth aspect, or the first optional implementation of the twelfth aspect, or the second optional implementation of the twelfth aspect, or the third optional implementation of the twelfth aspect, in the fourth optional implementation of the twelfth aspect, the terminal device is a redcap UE.

[0099] For the technical effects of the twelfth aspect or its various alternative embodiments, please refer to the description of the technical effects of the ninth aspect or its corresponding embodiments.

[0100] In a thirteenth aspect, a thirteenth communication method is provided, which can be executed by a core network device or by a chip system capable of implementing the functions of the core network device. Exemplarily, the core network device is an AMF (Access Controller Function). The method includes: the core network device determining a first period, the first period being the maximum eDRX period configurable for a terminal device, and the first period being used by the terminal device when it is in an RRC (Remote Redirection Control) inactive state; the core network device sending a first message to an access network device, the first message including the first period.

[0101] In conjunction with the thirteenth aspect, in a first optional implementation of the thirteenth aspect, the first period is determined based on NAS timing information, which includes the minimum retransmission time interval of NAS messages and / or the maximum number of retransmissions of NAS messages.

[0102] In conjunction with the thirteenth aspect or the first optional implementation of the thirteenth aspect, in the second optional implementation of the thirteenth aspect, the first message is an AMF configuration update message, or the first message is an NG interface establishment response message.

[0103] In conjunction with the thirteenth aspect, or the first optional implementation of the thirteenth aspect, or the second optional implementation of the thirteenth aspect, in the third optional implementation of the thirteenth aspect, the method further includes: the core network device receiving an RRC inactive state transition report from the access network device, the RRC inactive state transition report being used to indicate that a first terminal device in the terminal devices enters the RRC inactive state; the core network device sending a NAS message to the first terminal device according to the first cycle.

[0104] In conjunction with the thirteenth aspect, or the first optional implementation of the thirteenth aspect, or the second optional implementation of the thirteenth aspect, or the third optional implementation of the thirteenth aspect, in the fourth optional implementation of the thirteenth aspect, the terminal device is a redcap UE.

[0105] For the technical effects of the thirteenth aspect or its various alternative implementations, please refer to the description of the technical effects of the twelfth aspect or its corresponding implementations.

[0106] Fourteenth aspect, a fourteenth communication method is provided, which can be executed by a first terminal device or by a chip system capable of implementing the functions of the first terminal device. The method includes: the first terminal device receiving a second message from an access network device, the second message including a second period, the second period being an eDRX period configured for the first terminal device, and the second period being used by the first terminal device when it is in an RRC inactive state, wherein the second period is determined by the access network device based on a first period, the first period being the maximum eDRX period that the core network device can configure for multiple terminal devices, and the first period being used by the multiple terminal devices when they are in an RRC inactive state, the length of the second period being less than or equal to the length of the first period, and the multiple terminal devices including the first terminal device; when the first terminal device is in an RRC inactive state, the first terminal device listens for paging according to the second period.

[0107] In conjunction with the fourteenth aspect, in a first optional implementation of the fourteenth aspect, the second message is an RRC connection release message, which is used to release the first terminal device to the RRC inactive state.

[0108] In conjunction with the fourteenth aspect or the first optional implementation of the fourteenth aspect, in the second optional implementation of the fourteenth aspect, the terminal device is a redcap UE.

[0109] For information on the technical effects of the fourteenth aspect or its various alternative embodiments, please refer to the description of the technical effects of the twelfth aspect or its corresponding embodiments.

[0110] In a fifteenth aspect, a communication device is provided. The communication device may include modules for performing the methods of the second aspect or any optional embodiment of the second aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0111] In a sixteenth aspect, a communication device is provided. The communication device may include modules for performing the methods of the third aspect or any optional embodiment of the third aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0112] In a seventeenth aspect, a communication device is provided. The communication device may include modules for performing the methods of the fourth aspect or any optional embodiment of the fourth aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0113] Eighteenthly, a communication device is provided. The communication device may include modules for performing the methods of the sixth aspect or any optional embodiment of the sixth aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0114] In a nineteenth aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the seventh aspect or any optional embodiment of the seventh aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0115] In a twentieth aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the eighth aspect or any optional embodiment of the eighth aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0116] In a twenty-first aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the ninth aspect or any optional embodiment of the ninth aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0117] In a twenty-second aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the tenth aspect or any optional embodiment of the tenth aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0118] In a twenty-third aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the eleventh aspect or any optional embodiment of the eleventh aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0119] In a twenty-fourth aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the twelfth aspect or any optional embodiment of the twelfth aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0120] In a twenty-fifth aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the thirteenth aspect or any optional embodiment of the thirteenth aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0121] In a twenty-sixth aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the fourteenth aspect or any optional embodiment of the fourteenth aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0122] In a twenty-seventh aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the second aspect or any optional embodiment of the second aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the second aspect or any optional embodiment of the second aspect.

[0123] In a twenty-eighth aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the third aspect or any optional embodiment of the third aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the third aspect or any optional embodiment of the third aspect.

[0124] In a twenty-ninth aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the fourth aspect or any optional embodiment of the fourth aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the fourth aspect or any optional embodiment of the fourth aspect.

[0125] In a thirtieth aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the sixth aspect or any optional embodiment of the sixth aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the sixth aspect or any optional embodiment of the sixth aspect.

[0126] In a thirty-first aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the seventh aspect or any optional embodiment of the seventh aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the seventh aspect or any optional embodiment of the seventh aspect.

[0127] In a thirty-second aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the eighth aspect or any optional embodiment of the eighth aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the eighth aspect or any optional embodiment of the eighth aspect.

[0128] In a thirty-third aspect, a chip system is provided, the chip system including one or more processors and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the ninth aspect or any optional embodiment of the ninth aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the ninth aspect or any optional embodiment of the ninth aspect.

[0129] In a thirty-fourth aspect, a chip system is provided, the chip system including one or more processors and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the tenth aspect or any optional embodiment of the tenth aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the tenth aspect or any optional embodiment of the tenth aspect.

[0130] In a thirty-fifth aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the method provided by the eleventh aspect or any optional embodiment of the eleventh aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the method provided by the eleventh aspect or any optional embodiment of the eleventh aspect.

[0131] In a thirty-sixth aspect, a chip system is provided, the chip system including one or more processors, and a communication interface coupled to the communication interface for implementing the methods provided in the twelfth aspect or any optional embodiment of the twelfth aspect. Optionally, the chip system may further include a memory, for example, the processor can read and execute software programs stored in the memory to implement the methods provided in the twelfth aspect or any optional embodiment of the twelfth aspect.

[0132] In a thirty-seventh aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the thirteenth aspect or any optional embodiment of the thirteenth aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the thirteenth aspect or any optional embodiment of the thirteenth aspect.

[0133] In a thirty-eighth aspect, a chip system is provided, the chip system including one or more processors and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the fourteenth aspect or any optional embodiment of the fourteenth aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the fourteenth aspect or any optional embodiment of the fourteenth aspect.

[0134] In a thirty-ninth aspect, a first communication system is provided. The first communication system includes the communication device described in the fifteenth aspect or the chip system described in the twenty-seventh aspect, the communication device described in the sixteenth aspect or the chip system described in the twenty-eighth aspect, and includes the communication device described in the seventeenth aspect or the chip system described in the twenty-ninth aspect. Alternatively, the first communication system includes the core network equipment, access network equipment, and first terminal equipment described in the first aspect.

[0135] In a fortieth aspect, a second communication system is provided. The second communication system includes the communication device described in the eighteenth aspect or the chip system described in the thirtieth aspect, the communication device described in the nineteenth aspect or the chip system described in the thirty-first aspect, and includes the communication device described in the twentieth aspect or the chip system described in the thirty-second aspect. Alternatively, the second communication system includes the core network equipment, access network equipment, and first terminal equipment described in the fifth aspect.

[0136] In the forty-first aspect, a third communication system is provided. The third communication system includes the communication device described in the twenty-first aspect or the chip system described in the thirty-third aspect, the communication device described in the twenty-second aspect or the chip system described in the thirty-fourth aspect, and a system including the communication device described in the twenty-third aspect or the chip system described in the thirty-fifth aspect.

[0137] In a forty-second aspect, a fourth communication system is provided. The fourth communication system includes the communication device described in the twenty-fourth aspect or the chip system described in the thirty-sixth aspect, the communication device described in the twenty-fifth aspect or the chip system described in the thirty-seventh aspect, and a system including the communication device described in the twenty-sixth aspect or the chip system described in the thirty-eighth aspect.

[0138] In a forty-third aspect, a fifteenth communication method is provided, which can be executed by an access network device or by a chip system capable of implementing the functions of the access network device. Exemplarily, the access network device is a base station. The method includes: the access network device receiving a first message from a core network device, the first message including a first period, the first period being a maximum eDRX period configurable for a first terminal device, and the first period being used by the first terminal device when it is in an RRC inactive state; the access network device determining a second period based on the first period, the second period being an eDRX period configured for the first terminal device, and the second period being used by the first terminal device when it is in an RRC inactive state, the length of the second period being less than or equal to the length of the first period; the access network device sending a second message to the first terminal device, the second message including the second period.

[0139] In this embodiment, the core network device first notifies the access network device of the upper limit value it can accept. This allows the access network device to configure the eDRX period for the first UE in the RRC inactive state more accurately, reducing the process of the access network device re-determining the eDRX period configured for the first UE. The access network device configures the eDRX period for the first UE according to the first period. If the core network device needs to send a NAS message to the first UE, it can send it according to the first period, ensuring that the first UE can normally receive the NAS message from the core network device according to the eDRX period configured by the access network device. Regardless of whether the second period is greater than or less than 10.24s, the method of this embodiment can improve the probability of the UE receiving the NAS message and reduce the packet loss rate of the NAS message. Furthermore, the access network device does not need to notify the core network device of the eDRX period determined for the first UE, reducing signaling overhead. Moreover, the core network device does not need to page the first UE due to NAS message transmission failure, and the first UE does not need to enter the RRC idle state before initiating random access, reducing the transmission latency of the NAS message and saving transmission resources. Furthermore, in this embodiment, the core network device can take NAS timing information as a factor to give an upper limit value of the eDRX period (e.g., the first period) for the access network device to refer to, instead of having the access network device consider the eDRX period used by the first UE in the RRC idle state to configure the eDRX period used by the first UE in the RRC inactive state, making the way to configure the eDRX period for the UE more flexible.

[0140] In conjunction with aspect 43, in a first alternative implementation of aspect 43, the first message is an initial context establishment request message.

[0141] In conjunction with aspect 43 or the first optional implementation of aspect 43, in the second optional implementation of aspect 43, the second message is an RRC connection release message, which is used to release the first terminal device to the RRC inactive state.

[0142] In conjunction with aspect 43, or the first optional implementation of aspect 43, or the second optional implementation of aspect 43, in the third optional implementation of aspect 43, the first terminal device is a redcap UE.

[0143] For the technical effects of some optional implementations of aspect 43, please refer to the description of the technical effects of aspect 6 or the corresponding implementations.

[0144] In a forty-fourth aspect, a sixteenth communication method is provided, which can be executed by a core network device or by a chip system capable of implementing the functions of the core network device. Exemplarily, the core network device is an AMF (Access Controller Function). The method includes: the core network device determining a first period, the first period being a maximum eDRX period configurable for a first terminal device, and the first period being used by the first terminal device when it is in an RRC (Remote Redirect Control) inactive state; the core network device sending a first message to an access network device, the first message including the first period.

[0145] In conjunction with aspect 44, in a first optional implementation of aspect 44, the first period is determined based on NAS timing information, which includes the minimum retransmission time interval of NAS messages and / or the maximum number of retransmissions of NAS messages.

[0146] In conjunction with aspect 44 or the first optional implementation of aspect 44, in the second optional implementation of aspect 44, the first message is an initial context establishment request message.

[0147] In conjunction with aspect 44, or the first optional implementation of aspect 44, or the second optional implementation of aspect 44, in the third optional implementation of aspect 44, the method further includes: the core network device receiving an RRC inactive state transition report from the access network device, the RRC inactive state transition report being used to indicate that the first terminal device enters the RRC inactive state; the core network device sending a NAS message to the first terminal device according to the first period.

[0148] In conjunction with the forty-fourth aspect, or the first optional implementation of the forty-fourth aspect, or the second optional implementation of the forty-fourth aspect, or the third optional implementation of the forty-fourth aspect, in the fourth optional implementation of the forty-fourth aspect, the first terminal device is a redcap UE.

[0149] For the technical effects of aspect 44 or its various alternative embodiments, please refer to the description of the technical effects of aspect 43 or its corresponding embodiments.

[0150] A forty-fifth aspect provides a seventeenth communication method, which can be executed by a first terminal device or by a chip system capable of implementing the functions of the first terminal device. The method includes: the first terminal device receiving a second message from an access network device, the second message including a second period, the second period being an eDRX period configured for the first terminal device, and the second period being used by the first terminal device when it is in an RRC inactive state, wherein the second period is determined by the access network device based on a first period, the first period being the maximum eDRX period that the core network device can configure for the first terminal device, and the first period being used by the first terminal device when it is in an RRC inactive state, and the length of the second period being less than or equal to the length of the first period; when the first terminal device is in an RRC inactive state, the first terminal device listens for paging according to the second period.

[0151] In conjunction with aspect 45, in a first optional implementation of aspect 45, the second message is an RRC connection release message, which is used to release the first terminal device to the RRC inactive state.

[0152] In conjunction with aspect 45 or the first optional implementation of aspect 45, in the second optional implementation of aspect 45, the first terminal device is a redcap UE.

[0153] For the technical effects of aspect 45 or its various alternative embodiments, please refer to the description of the technical effects of aspect 43 or its corresponding embodiments.

[0154] In a forty-sixth aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the forty-third aspect or any optional embodiment of the forty-third aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0155] In a forty-seventh aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the forty-fourth aspect or any optional embodiment of the forty-fourth aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0156] In a forty-eighth aspect, a communication apparatus is provided. The communication apparatus may include modules for performing the methods of the forty-fifth aspect or any optional embodiment of the forty-fifth aspect, such as a transceiver unit and a processing unit. Optionally, a storage unit may also be included.

[0157] In a forty-ninth aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the forty-third aspect or any optional embodiment of the forty-third aspect. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in the forty-third aspect or any optional embodiment of the forty-third aspect.

[0158] In a fiftieth aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in the forty-fourth aspect or any optional embodiment of the forty-fourth aspect. Optionally, the chip system may further include a memory, for example, the processors being able to read and execute software programs stored in the memory to implement the methods provided in the forty-fourth aspect or any optional embodiment of the forty-fourth aspect.

[0159] In a fifty-first aspect, a chip system is provided, the chip system including one or more processors, and a communication interface, the processors being coupled to the communication interface for implementing the methods provided in aspect forty-fif or any optional embodiment of aspect forty-fifth. Optionally, the chip system may further include a memory, for example, the processors may read and execute software programs stored in the memory to implement the methods provided in aspect forty-fifth or any optional embodiment of aspect forty-fifth.

[0160] In aspect 52, a fifth communication system is provided. The fifth communication system includes the communication device described in aspect 46 or the chip system described in aspect 49, the communication device described in aspect 47 or the chip system described in aspect 50, and includes the communication device described in aspect 48 or the chip system described in aspect 51.

[0161] In a fifty-third aspect, a computer-readable storage medium is provided for storing a computer program that, when run on a computer, causes the computer to perform the methods provided in any of the preceding aspects.

[0162] In a fifty-fourth aspect, a computer program product comprising instructions is provided, the computer program product being used to store a computer program that, when the computer program is run on a computer, causes the computer to perform the method provided in any of the preceding aspects. Attached Figure Description

[0163] Figure 1A schematic diagram of the eDRX cycle;

[0164] Figure 2 This is a flowchart for configuring an eDRX cycle in the RRC inactive state for an eMTC UE;

[0165] Figure 3 This is a schematic diagram illustrating an application scenario according to an embodiment of this application;

[0166] Figure 4 A flowchart illustrating the first communication method provided in this application embodiment;

[0167] Figure 5 A flowchart illustrating the second communication method provided in this application embodiment;

[0168] Figure 6 A flowchart illustrating the third communication method provided in the embodiments of this application;

[0169] Figure 7 A flowchart illustrating the fourth communication method provided in this application embodiment;

[0170] Figure 8 A schematic block diagram of a communication device provided in an embodiment of this application;

[0171] Figure 9 This is a schematic block diagram of another communication device provided in the embodiments of this application. Detailed Implementation

[0172] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0173] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0174] In this embodiment, the terminal device is a device with wireless transceiver capabilities, which can be a fixed device, mobile device, handheld device, wearable device, vehicle-mounted device, or a wireless device (e.g., a communication module or chip system) built into the aforementioned devices. The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios, including but not limited to the following: cellular communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine / machine-type communication (M2M / MTC) communication, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical care, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, and other scenarios. The terminal device may sometimes be referred to as UE, terminal, access station, UE station, remote station, wireless communication device, or user equipment, etc. For ease of description, the terminal device in this application embodiment will be described using UE as an example.

[0175] For example, the UE involved in the various embodiments of this application is, for instance, a redcap UE. It is called a redcap UE because, compared to existing ordinary NR UEs, redcap UE devices typically only support lower bandwidths, such as 20MHz, and fewer transmit / receive antennas, such as only 1T1R or 1T2R. According to existing research, redcap UEs include three types of low-capability UEs: wearable products, video surveillance equipment, and industrial sensor equipment. Of course, besides redcap UEs, the technical solutions of the various embodiments of this application can also be applied to other UEs, such as UEs that are not sensitive to latency (or have low requirements), such as eMTC UEs. In the following text, the application of the technical solutions provided by the various embodiments of this application to redcap UEs will be used as an example.

[0176] The network devices in this application embodiment include, for example, access network devices and / or core network devices. The access network device is a device with wireless transceiver capabilities, used to communicate with the terminal device. The access network device includes, but is not limited to, base stations (BTS, Node B, eNodeB / eNB, or gNodeB / gNB), transmission reception points (TRPs), 3GPP subsequent evolution base stations, access nodes, wireless relay nodes, and wireless backhaul nodes in WiFi systems. The base station can be: macro base station, micro base station, pico base station, small cell, relay station, etc. Multiple base stations can support networks using the same access technology mentioned above, or they can support networks using different access technologies mentioned above. A base station can contain one or more co-located or non-co-located transmission and reception points. The network device can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario. The network device can also be a server, wearable device, or vehicle-mounted device, etc. For example, network devices in V2X technology can be roadside units (RSUs). The following description of access network devices uses a base station as an example. Multiple network devices in the communication system can be base stations of the same type or different types. Base stations can communicate with terminal devices or via relay stations. Terminal devices can communicate with multiple base stations in different access technologies. The core network devices are used to implement functions such as mobility management, data processing, session management, policy and charging. The names of devices implementing core network functions may differ in systems using different access technologies; this application does not limit this. Taking a 5G system as an example, the core network devices may include access and mobility management functions (AMF), session management functions (SMF), or user plane functions (UPF), etc. Taking a 4G system as an example, the core network devices may include mobility management entities, etc.

[0177] In this application embodiment, the device for implementing the function of the network device can be the network device itself, or it can be a device capable of supporting the network device in implementing that function, such as a chip system, which can be installed in the network device. In the technical solutions provided in this application embodiment, the example of a network device being used to implement the function of the network device is used to describe the technical solutions provided in this application embodiment.

[0178] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, 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, and c can be single or multiple.

[0179] Furthermore, unless otherwise stated, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, the first period and the second period can be the same period (e.g., the same length of time) or different periods (e.g., different lengths of time), and such names do not indicate that the two periods are different in length, priority, or importance.

[0180] The preceding text introduced some terms and concepts involved in the embodiments of this application. The following text introduces the technical features involved in the embodiments of this application.

[0181] The DRX mechanism saves power by allowing the UE to remain in sleep mode most of the time through discontinuous signal reception. Since packet-based data streams are generally bursty, power consumption can be reduced by shutting down the UE's receiving circuitry when there is no data transmission. eDRX is an extended DRX. In each eDRX cycle, the UE can only receive downlink data during a designated PTW (Paging Threshold Warp). Outside of the PTW, the UE remains in sleep mode. Each eDRX cycle has one PTW, during which the UE listens for the paging channel according to the DRX cycle. A larger eDRX cycle allows for greater power consumption gain for the UE, but also increases service transmission latency. For more information on eDRX operating modes, please refer to [link to relevant documentation]. Figure 1 .

[0182] Since different types of UEs, such as LTE UE, eMTC UE, NB-IoT UE, or NR UE, have different service requirements, the applicability of eDRX and DRX mechanisms also varies for different types of UEs. Please refer to Table 1 for details.

[0183] Table 1

[0184]

[0185] As shown in Table 1, currently LTE and NR UEs only support the DRX mechanism, not the eDRX mechanism. For these two types of UEs, the maximum supported DRX period is 2.56s when in RRC idle state and RRC inactive state. eMTC UEs can support a maximum eDRX period of approximately 44 minutes when in RRC idle state and 10.24s when in RRC inactive state. eMTC UEs are also the only UE among these types that can support the eDRX mechanism when in RRC inactive state. NB-IoT UEs do not have an RRC inactive state; when an NB-IoT UE is in RRC idle state, the maximum supported eDRX period is approximately 3 hours.

[0186] Currently, the required operating time for redcap UEs in various application scenarios has been proposed. For example, industrial wireless sensor devices in redcap UEs need to operate for several years; wearable devices in redcap UEs are required to operate for 1-2 weeks. Since there is currently no eDRX configuration for NR UEs, in order to meet the above operating time requirements, it is proposed to study eDRX in redcap UEs in RRC idle and RRC inactive states to reduce power consumption.

[0187] The eDRX cycle used by a UE in RRC idle mode is configured by the core network equipment through the NAS message during UE registration. For eMTC UEs, the eDRX cycle used in RRC inactive mode is configured by the base station through the RRC connection release message. Specifically, the eDRX cycle used by the UE in RRC idle mode is the core network paging cycle configured by the core network equipment for the UE, while the eDRX cycle used by the UE in RRC inactive mode is the radio access network (RAN) paging cycle configured by the base station for the UE. Currently, only eMTC UEs can have their RRC inactive mode eDRX cycle configured (i.e., the eDRX cycle used in RRC inactive mode). The configuration process can be found in [reference needed]. Figure 2 .

[0188] S21. The core network equipment sends core network assistance information for RRC inactive to the base station, and the base station receives the core network assistance information for RRC inactive from the core network equipment. The core network assistance information for RRC inactive is an information element (IE), which may be included, for example, in an initial context setup request message.

[0189] Core network assistance information for RRC inactive may include UE-specific DRX cycles and paging eDRX information. The paging eDRX information refers to the eDRX cycles used by the UE when it is in RRC idle mode.

[0190] S22. 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.

[0191] The base station refers to the paging eDRX information in the core network assistance information for RRC inactive to determine the eDRX period configured for the UE to use in the RRC inactive state. The duration of the eDRX period configured by the base station for the UE in the RRC inactive state is less than or equal to the duration of the eDRX period corresponding to the paging eDRX information. After determining the eDRX period configured for the UE in the RRC inactive state, the base station can send the eDRX period to the UE via an RRC connection release message. Thus, after the UE enters the RRC inactive state, it can use this eDRX period to listen for paging.

[0192] Currently, the minimum retransmission interval for NAS messages in mobility management is defined as 6 seconds, and the maximum number of retransmissions is 4. When an eMTC UE connects to the 5G core network (5GC), it can be in an RRC inactive state. When the UE is in an RRC inactive state, because the base station still retains the UE's context and the connection to the next-generation (NG) interface of the core network, the core network device considers the UE to be in an RRC connected state. However, both the base station and the UE know that the UE is actually in an RRC inactive state, which leads to an abnormal scenario of inconsistent perception of the UE's state. If the core network device sends a NAS message to the UE when the UE is in an RRC inactive state, the base station will page the UE after receiving the NAS message from the core network device, and send the NAS message back to the UE after the UE responds to the paging. After the UE responds to the paging, the access network device sends feedback information corresponding to the NAS message to the core network device. Because the minimum retransmission interval for NAS messages is specified as 6 seconds, and the maximum number of retransmissions is 4, the core network device needs to receive feedback information for the NAS message within 30 seconds; otherwise, the core network device will consider the NAS message transmission to have failed. If the core network device considers the NAS message transmission to have failed, it will page the UE. If the UE receives the paging message from the core network device, it needs to enter the RRC idle state and then initiate random access in the RRC idle state.

[0193] As mentioned earlier, when configuring the eDRX period for the UE in RRC inactive state, the base station refers to the paging eDRX information in the corenetwork assistance information for RRC inactive. For eMTC UEs, since the maximum eDRX period in RRC inactive state is specified as 10.24s, this eDRX period will not affect the UE's reception of NAS messages. However, if the redcap UE also supports the eDRX mechanism in RRC inactive state, the eDRX period for the redcap UE in RRC inactive state may not be less than or equal to 10.24s, and may be greater than 10.24s. Increasing the eDRX period length reduces the number of times the UE receives NAS messages, and the UE may even fail to receive any NAS messages within an eDRX period. Therefore, when the number of NAS message retransmissions exceeds four, the core network equipment will consider the NAS message transmission to have failed, and will page the UE. If the UE receives the paging message from the core network equipment, it needs to enter the RRC idle state and then initiate random access in the RRC idle state. Obviously, this process will result in significant latency and consume a lot of transmission resources.

[0194] Therefore, a method according to an embodiment of this application is provided. In this embodiment, the access network device and the core network device can negotiate to determine a second period, which is the eDRX period that can be configured for the first terminal device to use in the RRC inactive state. In this way, a more reasonable eDRX period can be given based on the own situation of the access network device and the core network device. Thus, if the core network device wants to send a NAS message to the first terminal device, it can send it according to the second period. In this way, regardless of whether the second period is less than or equal to 10.24s or greater than 10.24s, the first terminal device can receive the NAS message from the core network device normally according to the second period, which increases the probability of the terminal device receiving the NAS message, reduces the packet loss rate of the NAS message, and correspondingly reduces the transmission latency of the NAS message.

[0195] The technical solutions provided in this application can be applied to 4G systems, such as LTE systems, or to 5G systems, such as NR systems, or to next-generation mobile communication systems or other similar communication systems, without any specific limitations.

[0196] Please see Figure 3 This is one application scenario of an embodiment of this application. Figure 3This includes access network equipment, core network equipment, and UE. The access network equipment operates, for example, in an evolved UMTS terrestrial radio access (E-UTRA) system, an NR system, a next-generation communication system, or other communication systems. The access network equipment is, for example, a base station. The access network equipment corresponds to different devices in different systems; for example, in a 4G system it may correspond to an eNB, and in a 5G system it may correspond to a 5G access network device, such as a gNB. Of course, the technical solutions provided in this application embodiment can also be applied to future mobile communication systems. Figure 3 The access network equipment in this context can also correspond to the network equipment in future mobile communication systems. Figure 3 Taking a base station as an example of access network equipment, as mentioned earlier, access network equipment can also include devices such as RSUs (Remote Units). Furthermore, Figure 3 The UE in this application is a mobile phone, but as can be seen from the previous introduction of the UE, the UE in this application is not limited to mobile phones.

[0197] Furthermore, for ease of explanation, the various embodiments described below will all be applied to... Figure 3 The architecture shown is an example. For instance, the access network devices described in the various embodiments below are, for example, Figure 3 The access network devices in the network architecture shown, and the core network devices described in the various embodiments below, are, for example, the following. Figure 3 The core network equipment in the network architecture shown, and the UEs described in the various embodiments below, can be... Figure 3 The UE in the network architecture shown. And the core network equipment described in the various embodiments below, such as the AMF, or other equipment located on the core network side.

[0198] The method provided in the embodiments of this application is described below with reference to the accompanying drawings. In the accompanying drawings corresponding to the various embodiments of this application, all steps indicated by dashed lines are optional steps.

[0199] This application provides a first communication method, please refer to [link to relevant documentation]. Figure 4 Here is a flowchart of the method.

[0200] S41. The core network device sends the first information, and correspondingly, the access network device receives the first information from the core network device.

[0201] The first information may include, for example, the eDRX cycle used by the first UE when it is in RRC idle state. Optionally, the first information may also include information such as the UE-specific DRX cycle.

[0202] For example, if the first UE is in RRC idle state, and the core network device obtains downlink data from the first UE (e.g., the core network device receives the downlink data from another device, or the core network device generates the downlink data), the core network device can send a core network paging message for paging the first UE. First information can be included in this core network paging message. For example, the core network paging message includes a paging eDRX information element (IE), and the eDRX cycle used by the first UE in RRC idle state can be included in this information element (IE). Additionally, if the first information also includes a UE-specific DRX cycle, then the UE-specific DRX cycle can be included in the paging DRX IE within 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 can initiate random access to the access network device to enter the RRC connected state from the RRC idle state.

[0203] Alternatively, the core network device may send the first information 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), and there are no restrictions on the type of the message.

[0204] S42. The access network device determines the first cycle, which is the eDRX cycle that the access network device expects to configure for the first UE, and the first cycle is used by the first UE when it is in the RRC inactive state.

[0205] After receiving the first information, the access network device can determine the first period based on the first information. For example, the access network device can determine the first period based on the eDRX period used by the first UE when it is in the RRC idle state. For example, the duration of the first period determined by the access network device can be less than or equal to the duration of the eDRX period used by the first UE when it is in the RRC idle state.

[0206] S43. The access network device sends a 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 a first cycle.

[0207] For example, after receiving the paging message, the access network device can not only determine the first cycle but also send the paging message to the first UE. Correspondingly, the first UE receives the paging message from the access network device. After receiving the paging message, the first UE can initiate an RRC connection establishment procedure with the access network device based on the paging message to establish an RRC connection. After the first UE successfully establishes an RRC connection with the access network device, the first uplink NAS message initiated by the first UE can be sent to the core network device through an initial UE message. For example, the initial UE message may include information such as an 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. In this embodiment, the first cycle can be included in the initial UE message; that is, the initial UE message can be used as the first message.

[0208] For example, an IE can be added to the initial UE message, such as being called the first IE, and the first cycle can be carried through the first IE. Alternatively, the access network device can also send the first cycle to the core network device through other messages; that is, the first message can also be a message other than the initial UE message.

[0209] S44. The core network device sends a 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 a second cycle.

[0210] After receiving the first cycle, the core network equipment can determine the second cycle. The second cycle is the eDRX cycle used by the first UE when it is in the RRC inactive state, as determined by the core network equipment. For example, the core network equipment can determine whether it can configure the first cycle for the first UE, or in other words, whether it can accept the first cycle as the eDRX cycle used by the first UE in the RRC inactive state. If the core network equipment determines that it can configure the first cycle for the first UE, then the second cycle is the same as the first cycle; for example, the duration of the second cycle is equal to the duration of the first cycle. However, if the core network equipment determines that it cannot configure the first cycle for the first UE, then it can re-determine a second cycle that it can accept. In this case, the second cycle and the first cycle are different eDRX cycles; for example, the duration of the second cycle is not equal to the duration of the first cycle.

[0211] As an optional implementation, the core network device can determine whether a first cycle can be configured for the first UE based on the NAS timing information, or in other words, the core network device can determine a second cycle based on the NAS timing information and the first cycle. For example, if the core network device determines that the first cycle can adapt to the current NAS timing information, then the core network device determines that it can accept the first UE using the first cycle, and the duration of the second cycle is equal to the duration of the first cycle; or, if the core network device determines that the first cycle cannot adapt to the current NAS timing information, but if the NAS timing information is adjusted so that the first cycle can adapt to the adjusted NAS timing information, then the core network device determines that it can accept the first UE using the first cycle, and the duration of the second cycle is equal to the duration of the first cycle; or, if the core network device determines that the first cycle cannot adapt to the current NAS information, and even if the NAS timing information is adjusted, it cannot adapt the first cycle to the adjusted NAS timing information (because the core network device's adjustment of the NAS timing information is not unlimited, it may be adjusted to a certain extent and then cannot be adjusted further, so even if the NAS timing information is adjusted, it may not be able to adapt to the first cycle), then the core network device determines that it cannot accept the first UE using the first cycle, and the duration of the second cycle is not equal to the duration of the first cycle, for example, the duration of the second cycle is less than the duration of the first cycle, but the duration of the second cycle can be equal to the maximum duration determined according to the NAS timing information.

[0212] NAS timing information can include the minimum retransmission interval of NAS messages, the maximum number of retransmissions for NAS messages, or both. If the NAS timing information includes the minimum retransmission interval, then adjusting the NAS timing information by the core network device means adjusting the minimum retransmission interval. For example, the minimum retransmission interval can be increased or decreased. Generally, to make the eDRX period configured for the UE more flexible, the minimum retransmission interval can be increased. However, core network devices have acceptance limits, so the minimum retransmission interval cannot be increased indefinitely; there is an adjustment cap. Alternatively, if the NAS timing information includes the maximum number of retransmissions for NAS messages, then adjusting the NAS timing information by the core network device means adjusting the maximum number of retransmissions for NAS messages. For example, the maximum number of retransmissions can be increased or decreased. Generally, to make the eDRX period configured for the UE more flexible, the maximum number of retransmissions can be increased. However, core network devices have acceptance limits, so the maximum number of retransmissions cannot be increased indefinitely; there is an adjustment cap. Alternatively, if the NAS timing information includes the minimum retransmission interval and the maximum number of retransmissions for NAS messages, then adjusting the NAS timing information by the core network device may include adjusting the minimum retransmission interval of NAS messages, or adjusting the maximum number of retransmissions for NAS messages, or both.

[0213] For ease of understanding, it can be assumed that the core network device can determine a first threshold based on the NAS timing information. This first threshold could be, for example, the maximum duration corresponding to the NAS timing information, or the maximum eDRX cycle that the core network device can accept for the terminal device. The first threshold can be determined based on unadjusted NAS timing information or adjusted NAS timing information. If the first threshold is determined based on adjusted NAS timing information, for example, it could be based on NAS timing information adjusted to the maximum adjustment range; that is, the first threshold can be considered the maximum value that the core network device can accept. If the duration of the first cycle is less than or equal to the first threshold, the core network device determines that it can accept the first cycle. In this case, the second cycle can be the same as the first cycle, for example, the duration of the second cycle is the same as the duration of the first cycle. However, if the duration of the first cycle is greater than the first threshold, the core network device determines that it cannot accept the first cycle. In this case, the core network device can determine the second cycle that it can accept. Therefore, the duration of the second cycle can be less than the duration of the first cycle, but the second cycle must meet the requirements of the core network device; therefore, the duration of the second cycle can be less than or equal to the first threshold.

[0214] For example, if the first cycle is short, such as less than or equal to 10.24 seconds, the core network device may determine, based on the NAS timing information, that it can accept the first UE using the first cycle. In this case, the core network device can accept the first UE using the first cycle, and the length of the second cycle determined by the core network device can be equal to the length of the first cycle. Conversely, if the first cycle is long, such as greater than 10.24 seconds (e.g., 20.48 seconds), the core network device can adjust the NAS timing information. For example, if the adjusted NAS timing information can adapt to the 20.48-second eDRX cycle, the core network device can accept the first UE using the first cycle, and the length of the second cycle determined by the core network device can be equal to the length of the first cycle. For example, if the first cycle is long, such as 40.96 seconds (greater than 10.24 seconds), the core network equipment determines that even if the NAS timing information is adjusted by the maximum adjustment range (e.g., adjusting the minimum retransmission interval of the NAS message to the maximum value acceptable to the core network equipment, and / or adjusting the maximum number of retransmissions of the NAS message to the maximum value acceptable to the core network equipment), the adjusted NAS timing information still cannot adapt to the 40.96-second eDRX cycle. Therefore, the core network equipment cannot accept the first UE using the first cycle, and the length of the second cycle determined by the core network equipment can be shorter than the length of the first cycle.

[0215] After determining the second cycle, the core network device can send the second cycle to the access network device via a second message. For example, the core network device can send an Initial Context Establishment Request message to the access network device, and this Initial Context Establishment Request message can serve as the second message.

[0216] For example, the initial context establishment request message includes a second IE, which is, for example, a UE Radio Capability for Paging IE. The second IE may also include other IEs, such as a third IE, which is, for example, a UE radio paging information IE. The second period is carried, for example, by a first field included in the third IE, which is, for example, a spare field. For example, the third IE may include one or more spare fields, and the first field may be one of them. For example, UE radio paging information is defined as follows:

[0217]

[0218] As you can see, spare1 to spare7 represent seven blank fields, and the first field can include one or more of these seven blank fields.

[0219] Alternatively, the initial context establishment request message may include core network assistance information for RRC inactive, for example, by adding an IE to the core network assistance information for RRC inactive, such as calling it the fourth IE, which can carry the second cycle.

[0220] Alternatively, the core network equipment may send the second cycle to the access network equipment via other messages, as long as the message is related to the first UE (e.g., the message includes the identifier of the first UE).

[0221] Through the above steps, the access network equipment and the core network equipment have completed the negotiation of the eDRX cycle for the first UE in the RRC inactive state. The second cycle is the eDRX cycle that the first UE can use in the RRC inactive state, which is determined through negotiation.

[0222] S45. The access network device sends a third message to the first UE, and correspondingly, the first UE receives the third message from the access network device. The third message includes a second cycle.

[0223] The access network device receives the second cycle from the core network device. Because the second cycle is acceptable to the core network device, it will send NAS messages to the first UE according to the second cycle. Therefore, the access network device uses the second cycle as the final value configured for the first UE. The access network device can send the second cycle to the first UE through a third message, that is, configure the second cycle for the first UE. Thus, after the first UE enters the RRC inactive state, it can use the second cycle to listen for paging.

[0224] For example, when the access network device does not detect data transmission from the first UE, it can start an RRC connection release timer. If the RRC connection release timer expires, the access network device can send an RRC connection release message to the first UE to release it into an RRC inactive state. For example, if the first UE is a mobile phone, and the user is not using the phone temporarily, and the phone is in standby mode, there may be no data transmission between the phone and the access network device. In this case, the access network device does not receive uplink data from the phone for a period of time, and the access network device also does not have downlink data to send to the terminal device, so the access network device can release the phone into an RRC inactive state. Optionally, when sending the RRC connection release message to the first UE, the access network device can include a second cycle in the RRC connection release message and send it to the first UE; that is, the RRC connection release message can be used as a third message. The RRC connection release message is used to release the first UE into an RRC inactive state, and the second cycle is also used by the first UE when it is in an RRC inactive state. Therefore, sending the second cycle to the first UE through the RRC connection release message allows the second cycle to be used more promptly. Moreover, the RRC connection release message can both release the first UE to the RRC inactive state and configure the second cycle for the first UE, which improves message utilization. Furthermore, since there is no need to send an additional message to configure the second cycle for the first UE, it also reduces transmission overhead.

[0225] Alternatively, the access network device may send the second cycle to the first UE through other messages. For example, the access network device may send the second cycle to the first UE through other messages before sending the RRC connection release message to the first UE.

[0226] S46. The access network device sends an RRC inactive transition report to the core network device, and the core network device receives the RRC inactive transition report from the access network device.

[0227] The RRC inactive state transition report can indicate that the first UE has entered the RRC inactive state.

[0228] S47. The core network equipment sends a NAS message to the first UE according to the second cycle. Correspondingly, the first UE listens for paging according to the second cycle and thus receives the NAS message.

[0229] When the first UE is in the RRC inactive state, the core network device can send a NAS message to the first UE. Upon receiving this NAS message, the access network device will page the first UE. The first UE listens for paging according to the second cycle, and can then receive a paging message from the access network device; this paging message is an access network paging message. After receiving this paging message, the first UE can respond to the access network device. Upon receiving the response from the first UE, the access network device sends the NAS message back to the first UE, thus the first UE obtains the NAS message. For example, if the first UE receives a paging message from the access network device, it can initiate random access. The access network device receiving the random access preamble from the first UE is considered to have received the first UE's response. After successful random access, the access network device can send the NAS message back to the first UE. Alternatively, if the first UE receives a paging message from the access network device, it can choose not to initiate random access but instead respond to the access network device through other means. In addition, after receiving the response from the first UE, the access network device can also send feedback information to the core network device. Since the second cycle is supported by the core network device, the core network device can receive the feedback information within the time specified by the NAS timing information. The core network device will then consider the NAS message to have been sent successfully, without needing to page the first UE through the core network paging message. The first UE also does not need to enter the RRC idle state before initiating random access, which reduces the transmission latency of the NAS message and also reduces transmission overhead.

[0230] Optionally, the first UE can be any UE served by the access network device, such as a redcap UE. For other redcap UEs, if the eDRX period that can be supported when in the RRC inactive state is greater than 10.24s, then the technical solution of this application embodiment can be applied. That is, through the technical solution of this application embodiment, appropriate eDRX periods can be configured for different redcap UEs, so that the configured eDRX not only meets the UE's requirement to receive NAS messages, but also better meets the UE's actual service requirements.

[0231] Among them, Figure 4 In the illustrated embodiment, steps S41, S42, S46, and S47 are optional and not mandatory.

[0232] The method provided in this application embodiment can provide a more reasonable eDRX period for the first UE based on the characteristics of the access network device and the core network device. Therefore, if the core network device needs to send a NAS message to the first UE, it can send it according to the second period, ensuring that the first UE can normally receive the NAS message from the core network device according to the second period. Regardless of whether the second period is greater than or less than 10.24s, the method in this application embodiment can improve the probability of the UE receiving the NAS message and reduce the packet loss rate of the NAS message. Furthermore, the core network device does not need to page the first UE due to NAS message transmission failure, and the first UE does not need to enter the RRC idle state before initiating random access, reducing the transmission latency of the NAS message and saving transmission resources.

[0233] This application provides a second communication method, please refer to the embodiments therein. Figure 5 Here is a flowchart of the method.

[0234] S51. The core network device sends a 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 a first period. The first period is the eDRX period determined by the core network device for the first UE, and the first period is used by the first UE when it is in the RRC inactive state.

[0235] In this embodiment, the core network device can first determine a first cycle that it can accept and send the first cycle to the access network device. For example, the core network device can determine the first cycle based on NAS timing information. For details regarding the content of the NAS timing information, please refer to... Figure 4 Description of the illustrated embodiments.

[0236] The core network equipment determines the first period based on NAS timing information. For example, it can determine the first period based on unadjusted NAS timing information; that is, the core network equipment does not make any adjustments to the NAS timing information and determines the first period based on the unadjusted NAS timing information. For example, the length of the first period can be less than or equal to the first threshold corresponding to the unadjusted NAS timing information. Alternatively, the core network equipment can also adjust the NAS timing information and determine the first period based on the adjusted NAS timing information. For example, the length of the first period can be less than or equal to the first threshold corresponding to the adjusted NAS timing information. For example, the core network equipment can adjust the NAS timing information by the maximum adjustment range (e.g., adjusting the minimum retransmission interval of NAS messages to the maximum value acceptable to the core network equipment, and / or adjusting the maximum number of retransmissions of NAS messages to the maximum value acceptable to the core network equipment), and determine the first period based on the adjusted NAS timing information. This results in a longer first period, giving the access network equipment greater flexibility when configuring the first UE. For an introduction to the first threshold, please refer to [link to relevant documentation]. Figure 4 The example shown.

[0237] Alternatively, the core network equipment can determine the first period based on the NAS timing information and the service requirements of the first UE. In other words, the core network equipment can also consider the service requirements of the first UE when determining the first period, thus making the determined first period more suitable for the first UE's application. For example, the core network equipment can determine the first period based on the unadjusted NAS timing information and the service requirements of the first UE; or, the core network equipment can adjust the NAS timing information and determine the first period based on the adjusted NAS timing information and the service requirements of the first UE. For information on how the core network equipment adjusts the NAS timing information, please refer to the previous section.

[0238] Alternatively, the core network equipment can determine the first period based on the NAS timing information and the capabilities of the first UE. In other words, the core network equipment can also consider the capabilities of the first UE when determining the first period, thus making the determined first period more consistent with the capabilities of the first UE. For example, the core network equipment can determine the first period based on the unadjusted NAS timing information and the capabilities of the first UE; or, the core network equipment can adjust the NAS timing information and determine the first period based on the adjusted NAS timing information and the capabilities of the first UE. For details on how the core network equipment adjusts the NAS timing information, please refer to the previous section.

[0239] Alternatively, the core network equipment may determine the first cycle based on NAS timing information, the capabilities of the first UE, and the service requirements of the first UE, etc. This application embodiment does not limit the factors considered by the core network equipment when determining the first cycle.

[0240] For example, during the registration process of the first UE, the core network device can send an initial context establishment request message corresponding to the first UE to the access network device, and include the first cycle in the initial context establishment request message. This initial context establishment request message includes core network assistance information for RRC inactive, for example, adding an IE to the core network assistance information for RRC inactive, which can carry the first cycle. Alternatively, the initial context establishment request message may include a UE Radio Capability for Paging IE, which may also include UE radio paging information. The second cycle is carried, for example, through a first field included in the UE radio paging information, which may be a blank field. For example, the UE radio paging information includes one or more blank fields, and the first field may be one of them. For more information on UE radio paging information, please refer to [reference needed]. Figure 4 Description of the illustrated embodiments.

[0241] Alternatively, the core network equipment can send the first cycle to the access network equipment via other messages.

[0242] S52. The access network equipment determines the second cycle based on the first cycle.

[0243] After receiving the first cycle, the access network device can determine the eDRX cycle to be configured for the first UE for use in the RRC inactive state, based on the first cycle. For example, the cycle determined by the access network device can be referred to as the second cycle. The duration of the second cycle determined by the access network device must be within the acceptable range for the core network device; therefore, the duration of the second cycle can be less than or equal to the duration of the first cycle. From this perspective, the first cycle can be considered the maximum eDRX cycle that the core network device can accept for use by the first UE in the RRC inactive state.

[0244] For example, the access network device can determine the second period based on the first period and the capabilities of the first UE, so that the second period can meet the capabilities of the first UE; or, the access network device can determine the second period based on the first period and the service requirements of the first UE, so that the second period can meet the service requirements of the first UE; or, the access network device can determine the second period based on the first period, the capabilities of the first UE, and the service requirements of the first UE, etc. There are no restrictions on the factors used by the access network device to determine the second period. Given that the access network device can configure the eDRX period for the UE based on its actual situation (e.g., service requirements or capabilities), the eDRX period determined by the access network device for different UEs and used in the RRC inactive state may be the same or different.

[0245] S53. The access network device sends a 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 a second cycle.

[0246] 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 that the second cycle is actually configured for the first UE. Thus, the core network device can send NAS messages to the first UE in the RRC inactive state according to the second cycle.

[0247] For example, an access network device sends an initial context establishment response message to a core network device, and includes a second cycle in this initial context establishment response message; that is, the initial context establishment response message can serve as a second message. For instance, an IE can be added to the initial context establishment response message, and this IE can carry the second cycle.

[0248] S54. The access network device sends a third message to the first UE, and correspondingly, the first UE receives the third message from the access network device. The third message includes a second cycle.

[0249] If the access network device configures a second cycle for the first UE, the access network device can send the second cycle to the first UE through a third message, that is, configure the second cycle for the first UE. Thus, after the first UE enters the RRC inactive state, it can use the second cycle to listen for paging.

[0250] For more information about S54, please refer to [link / reference]. Figure 4 S45 in the illustrated embodiment.

[0251] S55. The access network device sends an RRC inactive state transition report to the core network device, and the core network device receives the RRC inactive state transition report from the access network device accordingly.

[0252] The RRC inactive state transition report can indicate that the first UE has entered the RRC inactive state.

[0253] Optionally, the access network device may also send the second cycle to the core network device without sending the initial context establishment response message, but instead include the second cycle in the RRC inactive state transition report and send it to the core network device.

[0254] S56. The core network equipment sends a NAS message to the first UE according to the second cycle. Correspondingly, the first UE listens for paging according to the second cycle and thus receives the NAS message.

[0255] For more information about S56, please refer to [link / reference]. Figure 4 S47 in the illustrated embodiment.

[0256] Optionally, the first UE can be any UE served by the access network device, such as a redcap UE. For other redcap UEs, if the eDRX period they can support when in the RRC inactive state is greater than 10.24s, then the technical solutions of the embodiments of this application can be applied. For example, the core network device can determine the first period for the UE based on NAS timing information and the service requirements of a UE. Since different UEs have different service requirements, 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. As another example, the core network device can determine the first period for the UE based on NAS timing information and the capabilities of a UE. Since different UEs have different capabilities, 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. Alternatively, even if the core network equipment determines the same first period for different UEs (for example, if the core network equipment determines the first period only based on NAS timing information, then the first period determined by the core network equipment for different UEs may be the same), the access network equipment, when determining the second period for a UE, may determine the second period based on the first period and the UE's capabilities, or it may determine the second period based on the first period and the UE's service requirements, etc. Thus, the second period configured by the access network equipment for different UEs may also be different. Therefore, through the technical solution of the embodiments of this application, a suitable eDRX period can be configured for each UE, so that the configured eDRX not only meets the UE's requirement to receive NAS messages, but also better meets the UE's actual service requirements.

[0257] Alternatively, S53 can be omitted. That is, the access network device does not need to send the second cycle to the core network device. The access network device only needs to configure the second cycle for the first UE according to the first cycle and then configure the second cycle for the first UE. In this case, the message sent by the access network device to the first UE in S54 can be called the second message, such as an RRC connection release message, or other messages. In this case, S56 can be replaced by: the core network device sending a NAS message to the first UE according to the first cycle, and correspondingly, the first UE still listens for paging according to the second cycle. This reduces the interaction process between the access network device and the core network device, saving signaling overhead. Moreover, since the duration of the second cycle is less than or equal to the duration of the first cycle, the first UE can listen for the NAS message sent by the core network device according to the first cycle within the eDRX cycle, without affecting the first UE's reception of the NAS message.

[0258] Among them, Figure 5 In the illustrated embodiment, steps S53, S55, and S56 are optional and not mandatory.

[0259] In this embodiment, the core network device first notifies the access network device of the upper limit value it can accept. This allows the access network device to configure the eDRX period for the first UE in the RRC inactive state more accurately, reducing the process of the access network device re-determining the eDRX period configured for the first UE. The access network device also informs the core network device of the final determined second period. Therefore, if the core network device needs to send a NAS message to the first UE, it can send it according to the second period, ensuring that the first UE can normally receive the NAS message from the core network device according to the second period. Regardless of whether the second period is greater than or less than 10.24s, the method of this embodiment increases the probability of the UE receiving the NAS message and reduces the packet loss rate of the NAS message. Furthermore, the core network device does not need to page the first UE due to NAS message transmission failure, and the first UE does not need to enter the RRC idle state before initiating random access, reducing the transmission latency of the NAS message and saving transmission resources. Furthermore, in this embodiment, the core network device can take NAS timing information as a factor to give an upper limit value of the eDRX period (e.g., the first period) for the access network device to refer to, instead of having the access network device consider the eDRX period used by the first UE in the RRC idle state to configure the eDRX period used by the first UE in the RRC inactive state, making the way to configure the eDRX period for the UE more flexible.

[0260] This application provides a third communication method; please refer to [reference needed]. Figure 6 Here is a flowchart of the method.

[0261] S61. The core network device sends a 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 a first period. The first period is the maximum eDRX period determined by the core network device for multiple UEs, and the first period is the eDRX period used by these multiple UEs when they are in the RRC inactive state. It can be understood that the eDRX period configured by the access network device for these multiple UEs can be the same or different, but it must be less than or equal to the first period.

[0262] In this embodiment, the first period corresponds to multiple UEs, such as all of them being redcap UEs. These multiple UEs may include all redcap UEs served by the core network device and the access network device, or they may include only some of the redcap UEs served by the core network device and the access network device. For example, the core network device can determine the first period based on NAS timing information. For details on how the core network device determines the first period based on NAS timing information, please refer to [reference needed]. Figure 5 Description of the illustrated embodiments.

[0263] For example, if the core network device is an AMF (Advanced Management Function), the AMF can send an AMF configuration update message to the access network device, including the first cycle in this AMF configuration update message. That is, the AMF configuration update message can serve as the first message. For instance, a first IE (Intermediate Internet Explorer) can be added to this AMF configuration update message; the first IE can then be used to carry the first cycle.

[0264] Alternatively, before a connection is established between the access network device and the core network device, the access network device can send an NG interface setup request message to the core network device to request the establishment of an NG interface connection. After receiving the NG interface setup request message from the access network device, the core network device can send an NG interface setup response message to the access network device to establish the NG interface connection. Optionally, the core network device can also include the first cycle in the NG interface setup response message and send it to the access network device; that is, the NG interface setup response message can be used as the first message. For example, a second IE can be added to the NG interface setup response message, which can then be used to carry the first cycle.

[0265] Alternatively, the core network device may send the first cycle to the access network device through other messages. In this embodiment of the application, the first cycle corresponds to multiple UEs, or in other words, it does not specifically correspond to one or several UEs. Therefore, the message used to send the first cycle may be unrelated to a specific UE (for example, the message does not include the identifier of any UE).

[0266] S62. The access network equipment determines the second cycle based on the first cycle.

[0267] After receiving the first cycle, the access network device can determine the maximum eDRX cycle to be configured for these multiple UEs in the RRC inactive state, based on the first cycle. For example, the cycle determined by the access network device can be called the second cycle. The duration of the second cycle determined by the access network device must be within the acceptable range for the core network device; therefore, the duration of the second cycle can be less than or equal to the duration of the first cycle. In other words, the core network device determines an upper limit for the eDRX cycle (i.e., the first cycle) for these multiple UEs, and the access network device, based on the first cycle, can determine the upper limit for the actual eDRX cycle configured for these multiple UEs (i.e., the second cycle).

[0268] Whether the length of the second period is equal to, shorter than, or significantly shorter than the length of the first period depends on the implementation of the access network equipment. For example, the access network equipment can determine the second period based on the first period, a relatively simple method; alternatively, it can determine the second period based on the first period and the service requirements of the multiple UEs, ensuring that the second period satisfies both the UEs' need to receive NAS messages and their service requirements; or, it can determine the second period based on the first period and the capabilities of the multiple UEs, ensuring that the second period satisfies both the UEs' need to receive NAS messages and their actual capabilities; or, it can also determine the second period based on the first period, the UEs' service requirements, and their capabilities, and so on.

[0269] S63. The access network device sends a 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 a second cycle.

[0270] After the access network device determines the second cycle, it can send the second cycle to the core network device via a second message. This allows the core network device to know the second cycle actually configured for multiple UEs. Therefore, for any one of these UEs in the RRC inactive state, if the core network device needs to send a NAS message to that UE, it can do so according to the second cycle. Thus, in this embodiment, regardless of which UE is in the RRC inactive state, the core network device only needs to send the NAS message according to one eDRX cycle (i.e., the second cycle). The core network device does not need to maintain different NAS messages for each UE, simplifying the implementation of the core network device.

[0271] For example, the access network device sends an AMF configuration update acknowledge message to the core network device, including the second cycle in the AMF configuration update acknowledge message; that is, the AMF configuration update message can be used as the second message. Alternatively, the access network device can 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 via the NG interface, the access network device can send a corresponding message to the core network device through the NG interface, including the second cycle in that message. Since the technical solutions of this application embodiment correspond to multiple UEs, or in other words, are not specifically targeted at one or several UEs, the message used to send the second cycle can be unrelated to the UE; for example, the message may not include the UE's identifier.

[0272] S64. The access network device sends a third message to the first UE, and correspondingly, the first UE receives the third message from the access network device. The third message includes a third cycle.

[0273] The second period determined by the access network device is the upper limit of the eDRX periods that can be configured for multiple UEs. Furthermore, the access network device can configure eDRX periods for different UEs among the multiple UEs to be used in the RRC inactive state, based on the second period and other factors. The duration of the eDRX periods configured by the access network device for different UEs among these multiple UEs for use in the RRC inactive state can be the same or different.

[0274] For example, for one of these multiple UEs, the access network device can determine the eDRX period used by the UE in the RRC inactive state based on the second period, which is a relatively simple method; or, the access network device can determine the eDRX period used by the UE in the RRC inactive state based on the second period and the UE's services, so that the configured eDRX period can meet both the UE's need to receive NAS messages and the UE's service transmission needs; or, the access network device can determine the eDRX period used by the UE in the RRC inactive state based on the second period and the UE's capabilities, so that the determined eDRX period can meet the needs of multiple UEs to receive NAS messages and also conform to the actual capabilities of the UE; or, the access network device can also determine the eDRX period used by the UE in the RRC inactive state based on the second period, the UE's service requirements, and the UE's capabilities, and so on.

[0275] The first UE is one of multiple UEs. For example, the access network device configures a third cycle for the first UE according to one of the configuration methods described above. The third cycle is an eDRX cycle used by the first UE when it is in the RRC inactive state. The access network device can send the third cycle to the first UE through a third message, that is, configure the third cycle for the first UE. Thus, after entering the RRC inactive state, the first UE can use the third cycle to listen for paging. The duration of the third cycle is less than or equal to the duration of the second cycle.

[0276] For more information on S64, such as what types of messages can be used to implement a third message, please refer to [link / reference]. Figure 4 S45 in the illustrated embodiment.

[0277] S65. 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 a fourth cycle.

[0278] The second UE is one of multiple UEs, and the first UE and the second UE are different UEs. For example, the access network device configures a fourth cycle for the second UE. This fourth cycle is an eDRX cycle used by the second UE when it is in the RRC inactive state. The access network device can send the fourth cycle to the second UE through a fourth message, that is, configure the fourth cycle for the second UE. Thus, after entering the RRC inactive state, the second UE can use the fourth cycle to listen for paging. The duration of the fourth cycle is less than or equal to the duration of the second cycle. The duration of the third cycle can be the same as or different from the duration of the fourth cycle.

[0279] For more information on S65, such as how access network devices determine the fourth cycle and what messages can be used to implement the fourth message, please refer to [link / reference]. Figure 4 S45 in the illustrated embodiment.

[0280] In addition, if these multiple UEs include other UEs besides the first and second UEs, the access network device can also configure eDRX cycles for the other UEs respectively. The configuration methods are similar and will not be elaborated further.

[0281] S66. The access network device sends an RRC inactive state transition report to the core network device, and the core network device receives the RRC inactive state transition report from the access network device accordingly.

[0282] The RRC inactive state transition report can indicate that the first UE has entered the RRC inactive state. Among these multiple UEs, the time when different UEs enter the RRC inactive state may be the same or different. This embodiment of the application only takes the entry of the first UE into the RRC inactive state as an example for illustration.

[0283] S66 can occur before S65, or S66 can occur simultaneously with S65, or S66 can occur after S65.

[0284] S67. The core network equipment sends a NAS message to the first UE according to the second cycle. Correspondingly, the first UE listens for paging according to the third cycle and thus receives the NAS message.

[0285] In this embodiment, regardless of the eDRX length configured for the UE by the access network device, the core network device sends NAS messages to the UE according to the second cycle. Thus, the core network device does not need to maintain different eDRX cycles for different UEs, which simplifies the implementation of the core network device.

[0286] For example, if the third cycle is configured by the access network device based on the second cycle and the service requirements of the first UE, then, since the duration of the third cycle is less than or equal to the duration of the second cycle, if the core network device sends NAS messages according to the second cycle, the first UE can listen for paging from the access network device within the third cycle, thus correctly receiving the NAS message and meeting the NAS message reception requirements. Furthermore, since the third cycle is related to the service requirements of the first UE, listening for paging according to the third cycle also meets the service transmission requirements of the first UE.

[0287] For more information about the S67, please refer to [link / reference]. Figure 4 S47 in the illustrated embodiment.

[0288] Additionally, if the access network device sends the fourth cycle to the second UE via an RRC connection release message, which releases the second UE into the RRC inactive state, then the second UE will also enter the RRC inactive state according to this message. The access network device will then 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 a NAS message to the second UE in the RRC inactive state, it will send it according to the second cycle, while the second UE will listen for paging according to the fourth cycle. Since the process is similar, it will not be elaborated further.

[0289] Among them, Figure 6 In the illustrated embodiment, steps S66 and S67 are optional and not mandatory.

[0290] In this embodiment, the core network device first notifies the access network device of the upper limit value it can accept. This allows the access network device to configure the eDRX period for multiple UEs in the RRC inactive state more accurately, reducing the process of re-determining the eDRX period for multiple UEs. The access network device also informs the core network device of the final determined second period. Therefore, if the core network device wants to send a NAS message to any of the multiple UEs, it can send it according to the second period, ensuring that all UEs can normally receive the NAS message from the core network device. Regardless of whether the second period is greater than or less than 10.24s, the method in this embodiment increases the probability of UEs receiving NAS messages and reduces the packet loss rate of NAS messages. The core network device also does not need to page the first UE due to NAS message transmission failure, and the first UE does not need to enter the RRC idle state before initiating random access, reducing service transmission latency and saving transmission resources. Moreover, for any one of these UEs, the core network equipment can send NAS messages according to the second cycle, without having to maintain different eDRX cycles for different UEs, which simplifies the implementation process of the core network equipment.

[0291] This application provides a fourth communication method, please refer to the embodiments. Figure 7 Here is a flowchart of the method.

[0292] S71. The core network device sends a 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 a first period. The first period is the maximum eDRX period determined by the core network device for multiple UEs, and the first period is the eDRX period used by these multiple UEs when they are in the RRC inactive state. It can be understood that the eDRX period configured by the access network device for these multiple UEs can be the same or different, but it must be less than or equal to the first period.

[0293] For more information about the S71, please refer to [link / reference]. Figure 6 The embodiment shown describes S61.

[0294] S72. The access network equipment determines the second cycle for the first UE based on the first cycle.

[0295] After receiving the first cycle, the access network device can determine the eDRX cycle to be used in the RRC inactive state for different UEs based on the first cycle. Optionally, the access network device can configure the eDRX cycle to be used in the RRC inactive state for different UEs among multiple UEs based on the first cycle and other factors. The duration of the eDRX cycle configured by the access network device for different UEs among these multiple UEs for use in the RRC inactive state can be the same or different.

[0296] For example, for one of these multiple UEs, the access network device can determine the eDRX period used by the UE in the RRC inactive state based on the first period, which is a relatively simple method; or, the access network device can determine the eDRX period used by the UE in the RRC inactive state based on the first period and the UE's services, so that the configured eDRX period can meet both the UE's need to receive NAS messages and the UE's service transmission needs; or, the access network device can determine the eDRX period used by the UE in the RRC inactive state based on the first period and the UE's capabilities, so that the determined eDRX period can meet the needs of multiple UEs to receive NAS messages and also conform to the actual capabilities of the UE; or, the access network device can also determine the eDRX period used by the UE in the RRC inactive state based on the first period, the UE's service requirements, and the UE's capabilities, and so on.

[0297] The first UE is one of multiple UEs. For example, the access network device configures a second cycle for the first UE according to one of the above configuration methods. The second cycle is the eDRX cycle used by the first UE when it is in the RRC inactive state.

[0298] S73. The access network device sends a second message to the first UE, and correspondingly, the first UE receives the second message from the access network device. The second message includes a second cycle.

[0299] The access network device can send the second cycle to the first UE via the second message, that is, configure the second cycle for the first UE. Thus, after the first UE enters the RRC inactive state, it can use the second cycle to listen for paging. The duration of the second cycle is less than or equal to the duration of the first cycle.

[0300] For more information about S73, such as what kind of messages can be used to implement the second message, please refer to [link / reference]. Figure 4 S45 in the illustrated embodiment.

[0301] S74. The access network equipment determines the third cycle for the second UE based on the first cycle.

[0302] The second UE is one of multiple UEs. For example, the access network device configures a third cycle for the second UE according to one of the configuration methods described above. The third cycle is the eDRX cycle used by the second UE when it is in the RRC inactive state. For more information about S74, such as how the access network device determines the third cycle, please refer to the introduction in S72.

[0303] S75. 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 a third cycle.

[0304] The access network device can send the third cycle to the second UE via a third message, that is, configure the third cycle for the second UE. Thus, after the second UE enters the RRC inactive state, it can use the third cycle to listen for paging. The duration of the third cycle is less than or equal to the duration of the first cycle.

[0305] For more information about S75, such as what kind of messages can be used to implement a third message, please refer to [link / reference]. Figure 4 S45 in the illustrated embodiment.

[0306] In addition, if these multiple UEs include other UEs besides the first and second UEs, the access network device can also configure eDRX cycles for the other UEs respectively. The configuration methods are similar and will not be elaborated further.

[0307] S76. The access network device sends an RRC inactive state transition report to the core network device, and the core network device receives the RRC inactive state transition report from the access network device accordingly.

[0308] The RRC inactive state transition report can indicate that the first UE has entered the RRC inactive state. Among these multiple UEs, the time when different UEs enter the RRC inactive state may be the same or different. This embodiment of the application only takes the entry of the first UE into the RRC inactive state as an example for illustration.

[0309] S77. The core network equipment sends a NAS message to the first UE according to the first cycle. Correspondingly, the first UE listens for paging according to the second cycle and thus receives the NAS message.

[0310] In this embodiment, regardless of the eDRX length configured for the UE by the access network device, the core network device sends NAS messages to the UE according to the first cycle. Thus, the core network device does not need to maintain different eDRX cycles for different UEs, which simplifies the implementation of the core network device.

[0311] For example, if the second cycle is configured by the access network device based on the first cycle and the service requirements of the first UE, then, since the duration of the second cycle is less than or equal to the duration of the first cycle, if the core network device sends NAS messages according to the first cycle, the first UE can listen for paging from the access network device within the second cycle, thus correctly receiving the NAS message and meeting the NAS message reception requirements. Furthermore, since the second cycle is related to the service requirements of the first UE, listening for paging according to the second cycle also meets the service transmission requirements of the first UE.

[0312] For more information about the S77, please refer to [link / reference]. Figure 4 S47 in the illustrated embodiment.

[0313] Additionally, if the access network device sends the third cycle to the second UE via an RRC connection release message, which releases the second UE into the RRC inactive state, then the second UE will also enter the RRC inactive state according to this message. The access network device will then 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 a NAS message to the second UE in the RRC inactive state, it will also send it according to the first cycle, and the second UE will listen for paging according to the third cycle. Since the process is similar, it will not be elaborated further.

[0314] Among them, Figure 7 In the illustrated embodiment, S76 and S77 are optional steps and are not mandatory.

[0315] In this embodiment, the core network device notifies the access network device of the upper limit value it can accept. The access network device can configure eDRX periods for different UEs based on this upper limit value. This allows the access network device to configure eDRX periods for multiple UEs in the RRC inactive state more accurately, reducing the process of re-determining the eDRX periods for multiple UEs. If the core network device needs to send a NAS message to any of the multiple UEs, it can send it according to the first period, ensuring that all UEs can receive the NAS message from the core network device normally, regardless of whether the first period is greater than or less than 10.24s. The method in this embodiment increases the probability of UE receiving NAS messages and reduces the packet loss rate of NAS messages. The core network device also does not need to page the first UE due to NAS message transmission failure, and the first UE does not need to enter the RRC idle state before initiating random access, reducing service transmission latency and saving transmission resources. Moreover, for any one of these UEs, the core network equipment can send NAS messages according to the second cycle, without having to maintain different eDRX cycles for different UEs, which simplifies the implementation process of the core network equipment.

[0316] The apparatus used to implement the above method in the embodiments of this application is described below with reference to the accompanying drawings. Therefore, the content above can be used in subsequent embodiments, and repeated content will not be described again.

[0317] Figure 8 This is a schematic block diagram of a communication device 800 provided in an embodiment of this application. Exemplarily, the communication device 800 is, for example, a terminal device or a network device. Exemplarily, the communication device 800 is capable of implementing... Figure 4 The illustrated embodiments or Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiments or Figure 7 The illustrated embodiment describes the function of the first terminal device. Alternatively, the communication device 800 can achieve the following: Figure 4 The illustrated embodiments or Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiments or Figure 7 The illustrated embodiment describes the function of the access network device. Alternatively, the communication device 800 can implement... Figure 4 The illustrated embodiments or Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiments or Figure 7 The core network equipment described in the illustrated embodiment has the following functions.

[0318] The communication device 800 includes a transceiver unit 820 and a processing unit 810. Optionally, the communication device 800 may further include a storage unit, which is capable of communicating with the processing unit 810. Figure 7 This is not shown in the text. Alternatively, the communication device 800 may not include a storage unit, or the storage unit may be located outside the communication device 800. For example, the communication device 800 may be a first terminal device, or a chip or other combination device or component with the functions of the first terminal device applied in the first terminal device, or the communication device 800 may be a network device (e.g., an access network device or a core network device), or a chip or other combination device or component with the functions of the network device (e.g., an access network device or a core network device) applied in the network device. When the communication device 800 is a first terminal device or a network device, the processing unit 810 may include a processor, such as a baseband processor, which may include one or more central processing units (CPUs); the transceiver unit 820 may be a transceiver, which may include an antenna and radio frequency circuits, etc. The transceiver may include a transmitter and a receiver, and the transceiver can implement the functions of a transmitter and a receiver, or the transmitter and receiver may be two separately deployed functional modules, but in this embodiment, these two functional modules are collectively referred to as a transceiver. When the communication device 800 is a component having the functions of the first terminal device or network device described above, the transceiver unit 820 can be a radio frequency unit, and the processing unit 810 can be a processor, such as a baseband processor. When the communication device 800 is a chip system, the transceiver unit 820 can be the input / output interface of a chip (e.g., a baseband chip), and the processing unit 810 can be the processor of the chip system, which may include one or more central processing units. It should be understood that the processing unit 810 in the embodiments of this application can be implemented by a processor or processor-related circuit components, and the transceiver unit 820 can be implemented by a transceiver or transceiver-related circuit components.

[0319] In one implementation, when the communication device 800 is used to implement Figure 4 When the first terminal device described in the illustrated embodiment performs its functions, the processing unit 810 can be used to execute... Figure 4 In the illustrated embodiment, the first terminal device performs all operations other than the transmit / receive operations, and / or other processes used to support the techniques described herein. The transmit / receive unit 820 can be used to perform... Figure 4 The embodiments shown include all receive and transmit operations performed by the first terminal device, such as S45 and S47, and / or other processes used to support the techniques described herein.

[0320] In one implementation, when the communication device 800 is used to implement Figure 4 When performing the functions of the access network device described in the illustrated embodiment, the processing unit 810 can be used to execute... Figure 4The embodiments shown include all operations performed by the access network device other than the transmit / receive operation, such as S42, and / or other processes used to support the techniques described herein. The transmit / receive unit 820 can be used to perform... Figure 4 The embodiments shown include all receive and transmit operations performed by the access network device, such as S41 and S43-S47, and / or other processes used to support the techniques described herein.

[0321] In one implementation, when the communication device 800 is used to implement Figure 4 When performing the core network device functions as described in the illustrated embodiment, the processing unit 810 can be used to execute... Figure 4 In the illustrated embodiment, all operations performed by the core network equipment other than transmit / receive operations, such as determining the second cycle, and / or other processes used to support the techniques described herein, are included. The transmit / receive unit 820 can be used to perform... Figure 4 The embodiments shown include all receive and transmit operations performed by the core network equipment, such as S41, S43, S44, S46, and S47, and / or other processes used to support the techniques described herein.

[0322] In one implementation, when the communication device 800 is used to implement Figure 5 When the first terminal device described in the illustrated embodiment performs its functions, the processing unit 810 can be used to execute... Figure 5 In the illustrated embodiment, the first terminal device performs all operations other than the transmit / receive operations, and / or other processes used to support the techniques described herein. The transmit / receive unit 820 can be used to perform... Figure 5 The embodiments shown include all receive and transmit operations performed by the first terminal device, such as S54 and S56, and / or other processes used to support the techniques described herein.

[0323] In one implementation, when the communication device 800 is used to implement Figure 5 When performing the functions of the access network device described in the illustrated embodiment, the processing unit 810 can be used to execute... Figure 5 In the illustrated embodiment, all operations performed by the access network device other than the transmit / receive operation, such as S52, and / or other processes used to support the technology described herein, are included. The transmit / receive unit 820 can be used to perform... Figure 5 The embodiments shown include all receive and transmit operations performed by the access network device, such as S51 and S53-S56, and / or other processes used to support the technology described herein.

[0324] In one implementation, when the communication device 800 is used to implement Figure 5When performing the core network device functions as described in the illustrated embodiment, the processing unit 810 can be used to execute... Figure 5 In the illustrated embodiment, all operations performed by the core network equipment other than transmit / receive operations, such as determining the first cycle, and / or other processes used to support the techniques described herein, are included. The transmit / receive unit 820 can be used to perform... Figure 5 The embodiments shown include all receive and transmit operations performed by the core network equipment, such as S51, S53, S55, and S56, and / or other processes used to support the techniques described herein.

[0325] In one implementation, when the communication device 800 is used to implement Figure 6 When the first terminal device described in the illustrated embodiment performs its functions, the processing unit 810 can be used to execute... Figure 6 In the illustrated embodiment, the first terminal device performs all operations other than the transmit / receive operations, and / or other processes used to support the techniques described herein. The transmit / receive unit 820 can be used to perform... Figure 6 The embodiments shown include all receive and transmit operations performed by the first terminal device, such as S64 and S67, and / or other processes used to support the techniques described herein.

[0326] In one implementation, when the communication device 800 is used to implement Figure 6 When performing the functions of the access network device described in the illustrated embodiment, the processing unit 810 can be used to execute... Figure 6 The embodiments shown include all operations performed by the access network device other than the transmit / receive operation, such as S62, and / or other processes used to support the techniques described herein. The transmit / receive unit 820 can be used to perform... Figure 6 The embodiments shown include all receive and transmit operations performed by the access network device, such as S61 and S63-S67, and / or other processes used to support the technology described herein.

[0327] In one implementation, when the communication device 800 is used to implement Figure 6 When performing the core network device functions as described in the illustrated embodiment, the processing unit 810 can be used to execute... Figure 6 In the illustrated embodiment, all operations performed by the core network equipment other than transmit / receive operations, such as determining the first cycle, and / or other processes used to support the techniques described herein, are included. The transmit / receive unit 820 can be used to perform... Figure 6 The embodiments shown include all receive and transmit operations performed by the core network equipment, such as S61, S63, S66, and S67, and / or other processes used to support the techniques described herein.

[0328] In one implementation, when the communication device 800 is used to implement Figure 7 When the first terminal device described in the illustrated embodiment performs its functions, the processing unit 810 can be used to execute... Figure 7 In the illustrated embodiment, the first terminal device performs all operations other than the transmit / receive operations, and / or other processes used to support the techniques described herein. The transmit / receive unit 820 can be used to perform... Figure 7 The embodiments shown include all receive and transmit operations performed by the first terminal device, such as S73 and S77, and / or other processes used to support the techniques described herein.

[0329] In one implementation, when the communication device 800 is used to implement Figure 7 When performing the functions of the access network device described in the illustrated embodiment, the processing unit 810 can be used to execute... Figure 7 The embodiments shown include all operations performed by the access network device other than the transmit / receive operations, such as S72 and S74, and / or other processes used to support the techniques described herein. The transmit / receive unit 820 can be used to perform... Figure 7 The embodiments shown include all receive and transmit operations performed by the access network device, such as S71, S73, and S75-S77, and / or other processes used to support the technology described herein.

[0330] In one implementation, when the communication device 800 is used to implement Figure 7 When performing the core network device functions as described in the illustrated embodiment, the processing unit 810 can be used to execute... Figure 7 In the illustrated embodiment, all operations performed by the core network equipment other than transmit / receive operations, such as determining the first cycle, and / or other processes used to support the techniques described herein, are included. The transmit / receive unit 820 can be used to perform... Figure 7 The embodiments shown include all receive and transmit operations performed by the core network equipment, such as S71, S76, and S77, and / or other processes used to support the techniques described herein.

[0331] Additionally, the transceiver unit 820 can be a functional module that can perform both sending and receiving operations. For example, the transceiver unit 820 can be used to perform... Figure 4 The illustrated embodiments or Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiments or Figure 7The illustrated embodiment represents all transmission and reception operations performed by the first terminal device or network device (e.g., core network device or access network device). For example, when performing a reception operation, the transceiver unit 820 can be considered a receiving unit, and when performing a transmission operation, it can be considered a transmitting unit. Alternatively, the transceiver unit 820 can also be two functional modules, which can be considered a collective term for these two functional modules, including a receiving unit and a transmitting unit. The transmitting unit is used to complete the transmission operation; for example, the transmitting unit can be used to perform... Figure 4 The illustrated embodiments or Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiments or Figure 7 In the illustrated embodiment, all sending operations are performed by the first terminal device or network device; the receiving unit is used to complete the receiving operation, for example, the receiving unit can be used to perform... Figure 4 The illustrated embodiments or Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiments or Figure 7 The embodiments shown depict all receiving operations performed by the first terminal device or network device.

[0332] For details on the specific functions that the processing unit 810 and the transceiver unit 820 can achieve, please refer to [reference needed]. Figure 4 The illustrated embodiments or Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiments or Figure 7 The illustrated embodiments describe the operations performed by the terminal device, or refer to... Figure 4 The illustrated embodiments or Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiments or Figure 7 The description of the operations performed by network devices (e.g., access network devices or core network devices) in the illustrated embodiments will not be elaborated further.

[0333] This application also provides a communication device, which can be a terminal device or a circuit. This communication device can be used to perform the actions performed by the terminal device in the various method embodiments described above.

[0334] When the communication device is a terminal device Figure 9 A simplified schematic diagram of a terminal device is shown. This is for ease of understanding and illustration. Figure 9 In this context, the terminal device is taken as a mobile phone. For example... Figure 9As shown, the terminal device includes a processor, memory, radio frequency (RF) circuitry, antenna, and input / output devices. The processor is primarily used for processing communication protocols and data, controlling the terminal device, executing software programs, and processing software program data. The memory is mainly used to store software programs and data. The RF circuitry is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user. It should be noted that some types of terminal devices may not have input / output devices.

[0335] 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 (RF) circuit. The RF circuit then processes the baseband signal and transmits it outward as electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts it into a baseband signal, and outputs the baseband signal to the processor. The processor then converts the baseband signal back into data and processes it. For ease of explanation, Figure 9 Only one memory and processor are shown in the illustration. In actual terminal device products, there may be one or more processors and one or more memories. Memory may also be referred to as storage medium or storage device, etc. Memory may be set up independently of the processor or integrated with the processor; this application does not limit this.

[0336] In this embodiment, the antenna and radio frequency circuit with transceiver functions can be regarded as the transceiver unit of the terminal device (the transceiver unit can be a single functional unit capable of transmitting and receiving functions; or, the transceiver unit can include two functional units, namely a receiving unit capable of receiving and a transmitting unit capable of transmitting), and the processor with processing functions can be regarded as the processing unit of the terminal device. Figure 9 As shown, the terminal device includes a transceiver unit 910 and a processing unit 920. The transceiver unit can also be called a transceiver, transceiver machine, transceiver device, etc. The processing unit can also be called a processor, processing board, processing module, processing device, etc. Optionally, the device in the transceiver unit 910 used to implement the receiving function can be considered as a receiving unit, and the device in the transceiver unit 910 used to implement the transmitting function can be considered as a transmitting unit; that is, the transceiver unit 910 includes both a receiving unit and a transmitting unit. The transceiver unit can sometimes also be called a transceiver, transceiver, or transceiver circuit, etc. The receiving unit can sometimes be called a receiver, receiver, or receiving circuit, etc. The transmitting unit can sometimes be called a transmitter, transmitter, or transmitting circuit, etc.

[0337] It should be understood that the transceiver unit 910 is used to perform the above-mentioned tasks. Figure 4 The illustrated embodiments or Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiments or Figure 7 In the embodiment shown, the processing unit 920 performs the sending and receiving operations on the terminal device side. Figure 4 The illustrated embodiments or Figure 5 The illustrated embodiments or Figure 6 The illustrated embodiments or Figure 7 The embodiments shown include operations on the first terminal device side other than sending and receiving operations.

[0338] When the communication device is a chip-based device or circuit, it 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, microprocessor, or integrated circuit.

[0339] It should be understood that the processor mentioned in the embodiments of this application can be a CPU, or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0340] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) is integrated into the processor.

[0341] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0342] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0343] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0344] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0346] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0347] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions 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 this application. The aforementioned computer-readable storage medium can be any available medium that a computer can access. For example, but not limited to: computer-readable media may include random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), universal serial bus flash disk, portable hard disk, or other optical disc storage, magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code having the form of instructions or data structures and accessible by a computer. Additionally, by way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), or direct rambus RAM (DR RAM).

[0348] The above description is merely a specific embodiment of this application, but the protection scope of the embodiments of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the embodiments of this application should be included within the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of this application should be determined by the protection scope of the claims.

Claims

1. A communication method, characterized in that, include: The core network device determines a first period based on the maximum eDRX period that the core network device can accept. The first period is the maximum extended discontinuous reception eDRX period that can be configured for the first terminal device, and the first period is used by the first terminal device when it is in the Radio Resource Control (RRC) inactive state. The first period is less than or equal to the maximum eDRX period, wherein the maximum eDRX period is determined based on NAS timing information, which includes the minimum retransmission interval of NAS messages and / or the maximum number of retransmissions of NAS messages. 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. The initial context establishment request message includes the context information of the first terminal device, and the initial context request message also includes the first cycle. The access network device receives the initial context establishment request message and determines a second period based on the first period carried in the initial context establishment request message and the capabilities and / or service requirements of the first terminal device. The second period is the eDRX period configured for the first terminal device and is used by the first terminal device when it is in the RRC inactive state. 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, the initial context establishment response message including the second cycle; When the first terminal device has completed registration and the access network device has not detected data transmission from the first terminal device, the access network device starts the RRC connection release timer. When the RRC connection release timer expires, the access network device sends an RRC connection release message to the first terminal device, the RRC connection release message including the second period; When the first terminal device is in the RRC inactive state, the first terminal device listens for paging according to the second cycle.

2. The method according to claim 1, characterized in that, The access network device configures different terminal devices for the length of the eDRX period when they are in the RRC inactive state, based on the first period.

3. The method according to claim 1 or 2, characterized in that, The first terminal device is redcap UE.

4. A communication method, characterized in that, include: The access network device receives a first message from the core network device. The first message includes a first period, which is the maximum eDRX period that can be configured for the first terminal device. The first period is used by the first terminal device when it is in an RRC inactive state. The first period is determined based on the maximum eDRX period that the core network device can accept. The first period is less than or equal to the maximum eDRX period. The maximum eDRX period is determined based on NAS timing information, which includes the minimum retransmission interval of NAS messages and / or the maximum number of retransmissions of NAS messages. The access network device determines a second period based on the first period and the capabilities and / or service requirements of the first terminal device. The second period is an eDRX period configured for the first terminal device, and the second period is used by the first terminal device when it is in the RRC inactive state. The length of the second period is less than or equal to the length of the first period. The access network device sends a second message to the core network device, the second message including the second cycle.

5. The method according to claim 4, characterized in that, 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.

6. The method according to claim 4 or 5, characterized in that, The method further includes: The access network device sends a third message to the first terminal device, the third message including the second cycle.

7. The method according to claim 6, characterized in that, The third message is an RRC connection release message, which is used to release the first terminal device to the RRC inactive state.

8. The method according to claim 6, characterized in that, The access network device configures different terminal devices for the length of the eDRX period when they are in the RRC inactive state, based on the first period.

9. The method according to claim 6, characterized in that, The first terminal device is redcap UE.

10. A communication method, characterized in that, include: The core network device sends a first message to the access network device. The first message includes a first period, which is the maximum eDRX period that can be configured for the first terminal device. The first period is used by the first terminal device when it is in an RRC inactive state. The first period is determined based on the maximum eDRX period that the core network device can accept. The first period is less than or equal to the maximum eDRX period. The maximum eDRX period is determined based on NAS timing information, which includes the minimum retransmission interval of NAS messages and / or the maximum number of retransmissions of NAS messages. The core network device receives a second message from the access network device. The second message includes a second period, which is an eDRX period configured for the first terminal device. The second period is used by the first terminal device when it is in the RRC inactive state. The length of the second period is less than or equal to the length of the first period. The second period is determined based on the first period and the capabilities and / or service requirements of the first terminal device.

11. The method according to claim 10, characterized in that, The first message is an initial context establishment request message; and / or, The second message is either an initial context establishment response message or an RRC inactive state transition report.

12. The method according to claim 10, characterized in that, The method further includes: The core network device receives an RRC inactive state transition report from the access network device, the RRC inactive state transition report being used to indicate that the first terminal device enters the RRC inactive state; The core network device sends NAS messages to the first terminal device according to the second cycle.

13. The method according to claim 10, characterized in that, The first terminal device is redcap UE.

14. A communication method, characterized in that, include: A first terminal device receives a third message from an access network device. The third message includes a second period, which is an eDRX period configured for the first terminal device and is used by the first terminal device when it is in an RRC inactive state. The second period is determined by the access network device based on a first period and the capabilities and / or service requirements of the first terminal device. The first period is the maximum eDRX period that the core network device can configure for the first terminal device and is used by the first terminal device when it is in an RRC inactive state. The length of the second period is less than or equal to the length of the first period. The first period is determined based on the maximum eDRX period that the core network device can accept. The first period is less than or equal to the maximum eDRX period. The maximum eDRX period is determined based on NAS timing information, which includes the minimum retransmission interval of NAS messages and / or the maximum number of retransmissions of NAS messages. When the first terminal device is in the RRC inactive state, the first terminal device listens for paging according to the second cycle.

15. The method according to claim 14, characterized in that, The third message is an RRC connection release message, which is used to release the first terminal device to the RRC inactive state.

16. The method according to claim 14 or 15, characterized in that, The first terminal device is redcap UE.

17. A communication method, characterized in that, include: The access network device receives a first message from the core network device. The first message includes a first period, which is the maximum eDRX period that can be configured for the terminal device. The first period is used by the terminal device when it is in an RRC inactive state. The first period is determined based on the maximum eDRX period that the core network device can accept. The first period is less than or equal to the maximum eDRX period. The maximum eDRX period is determined based on NAS timing information, which includes the minimum retransmission interval of NAS messages and / or the maximum number of retransmissions of NAS messages. The access network device determines a second period based on the first period and the capabilities and / or service requirements of the terminal device. The second period is the maximum eDRX period configured for the terminal device, and the second period is used by the terminal device when it is in the RRC inactive state. The length of the second period is less than or equal to the length of the first period. The access network device sends a second message to the core network device, the second message including the second cycle.

18. The method according to claim 17, characterized in that, The first message is an AMF configuration update message, and the second message is an AMF configuration update confirmation message; or, the first message is an NG interface establishment response message.

19. The method according to claim 17 or 18, characterized in that, The method further includes: The access network device sends a third message to the first terminal device in the terminal devices. The third message includes a third period, the length of which is less than or equal to the length of the second period. The third period is an eDRX period configured for the first terminal device, and the third period is used by the first terminal device when it is in the RRC inactive state. The access network device sends a fourth message to the second terminal device in the terminal devices. The fourth message includes a fourth period, the length of which is less than or equal to the length of the second period. The fourth period is an eDRX period configured for the second terminal device, and the third period is used by the first terminal device when it is in the RRC inactive state. The length of the third cycle may be the same as or different from the length of the fourth cycle.

20. The method according to claim 17 or 18, characterized in that, The length of the second period is different depending on the terminal device for which the first period is different.

21. The method according to claim 17 or 18, characterized in that, The terminal device is redcap UE.

22. A communication method, characterized in that, include: The core network device sends a first message to the access network device. The first message includes a first period, which is the maximum eDRX period that can be configured for the terminal device. The first period is used by the terminal device when it is in the RRC inactive state. The first period is determined based on the maximum eDRX period that the core network device can accept. The first period is less than or equal to the maximum eDRX period. The maximum eDRX period is determined based on NAS timing information, which includes the minimum retransmission interval of NAS messages and / or the maximum number of retransmissions of NAS messages. The core network device receives a second message from the access network device. The second message includes a second period, which is the maximum eDRX period configured for the terminal device and is used by the terminal device when it is in the RRC inactive state. The length of the second period is less than or equal to the length of the first period and is determined based on the first period and the capabilities and / or service requirements of the terminal device.

23. The method according to claim 22, characterized in that, The first message is an AMF configuration update message, and the second message is an AMF configuration update confirmation message; or, the first message is an NG interface establishment response message.

24. The method according to claim 22, characterized in that, The method further includes: The core network device receives an RRC inactive state transition report from the access network device, the RRC inactive state transition report being used to indicate that the first terminal device in the terminal devices enters the RRC inactive state; The core network device sends NAS messages to the first terminal device according to the second cycle, where the first terminal device is any terminal device covered by the access network device.

25. The method according to claim 22, characterized in that, The terminal device is redcap UE.

26. A communication method, characterized in that, include: A first terminal device receives a third message from an access network device. The third message includes a third period, which is an eDRX period configured for the first terminal device and used by the first terminal device when it is in an RRC inactive state. The third period is determined by the access network device based on a first period and a second period. The first period is the maximum eDRX period that the core network device can configure for multiple terminal devices, and is used by the multiple terminal devices when they are in an RRC inactive state. The second period is the maximum eDRX period configured by the access network device for the multiple terminal devices. This is used when the plurality of terminal devices are in the RRC inactive state. The second period is determined based on the first period and the capabilities and / or service requirements of the first terminal device. The length of the second period is less than or equal to the length of the first period. The plurality of terminal devices includes the first terminal device. The first period is determined based on the maximum eDRX period that the core network device can accept. The first period is less than or equal to the maximum eDRX period. The maximum eDRX period is determined based on NAS timing information, which includes the minimum retransmission interval of NAS messages and / or the maximum number of retransmissions of NAS messages. When the first terminal device is in the RRC inactive state, the first terminal device listens for paging according to the third cycle.

27. The method according to claim 26, characterized in that, The third message is an RRC connection release message, which is used to release the first terminal device to the RRC inactive state.

28. The method according to claim 26 or 27, characterized in that, The first terminal device is redcap UE.

29. A network device, characterized in that, include: One or more processors; One or more memory units; And one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, the one or more computer programs including instructions that, when executed by one or more processors of the network device, cause the network device to perform the method performed by an access network device or a core network device as claimed in any one of claims 1 to 3, or cause the network device to perform the method as claimed in any one of claims 4 to 9, or cause the network device to perform the method as claimed in any one of claims 10 to 13, or cause the network device to perform the method as claimed in any one of claims 14 to 21, or cause the network device to perform the method as claimed in any one of claims 22 to 25.

30. A terminal device, characterized in that, include: One or more processors; One or more memory units; And one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, the one or more computer programs including instructions that, when executed by one or more processors of the terminal device, cause the terminal device to perform the method performed by the first terminal device as claimed in any one of claims 1 to 3, or cause the terminal device to perform the method as claimed in any one of claims 14 to 16, or cause the terminal device to perform the method as claimed in any one of claims 26 to 28.

31. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 3, or causes the computer to perform the method as described in any one of claims 4 to 9, or causes the computer to perform the method as described in any one of claims 10 to 13, or causes the computer to perform the method as described in any one of claims 14 to 16, or causes the computer to perform the method as described in any one of claims 17 to 21, or causes the computer to perform the method as described in any one of claims 22 to 25, or causes the computer to perform the method as described in any one of claims 26 to 28.

32. A chip, characterized in that, The device includes one or more processors and a communication interface, wherein the one or more processors are configured to read instructions to execute the method of any one of claims 1 to 3, or the method of any one of claims 4 to 9, or the method of any one of claims 10 to 13, or the method of any one of claims 14 to 16, or the method of any one of claims 17 to 21, or the method of any one of claims 22 to 25, or the method of any one of claims 26 to 28.

Images