Communication method, and apparatus

Abstract

The present application relates to the field of communications. Provided in the embodiments are a communication method and an apparatus, which can prevent a terminal device from being unable to receive data of an emergency session in a timely manner due to being in a sleep state and being unable to be restored to a connected state. In the method, when determining that there is a first-type session, a mobility management network element can send second information to an access network device, so as to trigger the access network device to configure a void inactive-state discontinuous reception parameter for the terminal device, or not configure an inactive-state discontinuous reception parameter for the terminal device. Thus, when determining that there is the first-type session, the terminal device does not use the inactive-state discontinuous reception when entering an inactive state, such that the terminal device can be restored from the inactive state to the connected state in a timely manner, so as to receive or send data related to the first-type session.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202510058124.3, filed on January 13, 2025, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to communication methods and apparatus. Background Technology

[0003] When a terminal device transitions from Radio Resource Control (RRC) connected state (RRC_CONNECTED) to RRC idle state (RRC_IDLE), or from RRC connected state to RRC inactive state (RRC_INACTIVE), the network configures the terminal device to monitor paging for a period of time and then enter sleep mode for a period of time to save power. However, when there is an emergency service, the terminal device in sleep mode cannot promptly resume RRC connected state, which will result in the terminal device being unable to receive data related to the emergency service in a timely manner. Summary of the Invention

[0004] This application provides a communication method and apparatus that can prevent terminal devices from being unable to promptly resume connection due to being in a sleep state and thus unable to receive emergency session data in a timely manner.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a communication method is provided. This method can be executed by a mobility management network element (MLE), a component of the MLE, such as a processor, chip, or chip system of the MLE, or a logic module or software capable of implementing all or part of the MLE. Taking the application of this method to a MLE as an example, in this method: it is determined that the terminal device has a first type of session, which is used for the terminal device's emergency services; first information is sent to the access network device, which is used to trigger the access network device not to configure inactive discontinuous reception parameters to the terminal device, or to trigger the access network device to configure the inactive discontinuous reception parameters to be empty to the terminal device.

[0007] In this communication method, when the mobility management network element determines that a first type of session exists, it can send second information to the access network device to trigger the access network device to configure empty inactive discontinuous reception parameters for the terminal device, or not configure inactive discontinuous reception parameters for the terminal device. This allows the terminal device to not use inactive discontinuous reception when it enters the inactive state in the presence of the first type of session, thereby enabling the terminal device to promptly recover from the inactive state to the connected state to receive or send data related to the first type of session.

[0008] The first piece of information is used to trigger the access network device not to configure inactive discontinuous reception parameters to the terminal device. This information can refer to information used to trigger the configuration of the terminal device to disable, delete, or update inactive discontinuous reception. In this embodiment, the first type of session can also be called an emergency session, an emergency service session, etc., without limitation.

[0009] In this embodiment, the non-active state discontinuous reception parameter may include or be ran-ExtendedPagingCycle, eDRX parameter in RRC-INACTIVE, eDRX cycle in RRC-INACTIVE, RRC-INACTIVE eDRX parameter, or RRC-INACTIVE eDRX cycle, and there is no limitation thereto.

[0010] In one possible design, the first information can be the first RRC Inactive auxiliary information corresponding to the terminal device, which does not include idle-mode discontinuous reception parameters. In this embodiment, the idle-mode discontinuous reception parameters are used by the access network device to determine the inactive-mode discontinuous reception parameters. The mobility management network element does not configure idle-mode discontinuous reception parameters for the access network device, preventing the access network device from configuring inactive-mode discontinuous reception parameters for the terminal device. Therefore, when the first type of session exists, the terminal device does not use inactive-mode discontinuous reception when entering the inactive state, enabling the terminal device to promptly recover from the inactive state to the connected state to receive or send data related to the first type of session. For example, the idle-mode discontinuous reception parameters include extended idle mode DRX parameters.

[0011] In one possible design, the method may further include: when the first type of session of the terminal device is released, sending second RRC Inactive assistance information corresponding to the terminal device to the access network device, the second RRC Inactive assistance information including idle-state discontinuous reception parameters. That is, when the first type of session is released, the mobility management network element can reconfigure the idle-state discontinuous reception parameters for the access network device, so that the access network device configures the inactive-state discontinuous reception parameters for the terminal device based on the idle-state discontinuous reception parameters. This allows the terminal device to be configured to use inactive-state discontinuous reception when there is no first type of session and it enters an inactive state, thereby reducing the power consumption or energy consumption of the terminal device.

[0012] In one possible design, the first information may include: indication information for instructing the access network device to configure the terminal device to disable inactive discontinuous reception; or, indication information for instructing the access network device to delete the idle discontinuous reception parameters and / or the inactive discontinuous reception parameters of the terminal device; or, indication information for indicating that the terminal device has a first type of session. Disabling inactive discontinuous reception may indicate that the terminal device does not use, invalidates, or stops using inactive discontinuous reception when entering the inactive state; deleting idle discontinuous reception parameters and / or inactive discontinuous reception parameters may indicate that the access network device deletes locally stored idle discontinuous reception parameters and / or inactive discontinuous reception parameters, so that the access network device will not configure inactive discontinuous reception parameters for the terminal device, or that the access network device instructs the terminal device to delete inactive discontinuous reception parameters; indicating that the terminal device has a first type of session may enable the access network device to detect the existence of a first type of session, thereby instructing the terminal device to disable or delete inactive discontinuous reception parameters, or configuring the inactive discontinuous reception parameters of the terminal device to be empty. In this design, the first information can also be RRC Inactive auxiliary information.

[0013] In some implementations, the first information may include idle discontinuous reception with empty parameters, or it may include indication information for instructing the access network device to configure the terminal device to update the inactive discontinuous reception parameters to be empty. Therefore, the access network device can configure the terminal device to receive inactive discontinuous reception with empty parameters, or instruct the terminal device to update the inactive discontinuous reception parameters to be empty, based on the first information.

[0014] Therefore, the access network device can configure the terminal device not to use inactive discontinuous reception when a first type of session exists and the terminal device enters an inactive state, based on the first information, so that the terminal device can promptly recover from the inactive state to the connected state to receive or send data related to the first type of session.

[0015] In one possible design, sending the first information to the access network device may include: sending the first information to the access network device when the first type of session is inactive. Thus, when the mobility management element determines that the terminal device has a first type of session, it can further determine whether the first type of session is active. If it determines that the first type of session is inactive, although the first type of session is not active, it has not been released, and the mobility management element can send the first information to the access network device. This ensures the reliability of the inactive terminal device in receiving or sending data related to the first type of session in a timely manner.

[0016] In one possible design, the method may further include: receiving a service request from a terminal device, wherein the service request requests activation of a session that does not include a first type of session; and determining, based on the service request, that the first type of session of the terminal device is in an inactive state. Thus, the mobility management network element can determine whether the first type of session is activated based on a service request initiated by a terminal device in an idle state, such as determining that the first type of session is in an inactive state.

[0017] In one possible design, sending the first information to the access network device may include: sending the first information to the access network device when the first type of session is in an active state. Thus, if it is determined that the first type of session exists and is in an active state, the mobility management network element can also send the first information to the access network device. The activation of the first type of session indicates the existence of data transmission related to the first type of session. This allows for more accurate configuration of the terminal device to avoid using inactive discontinuous reception when the first type of session exists and it enters an inactive state, ensuring timely reception or transmission of data related to the first type of session.

[0018] In one possible design, the method may further include: receiving a service request from a terminal device, wherein the service request requests activation of a session including a first type of session; and determining, based on the service request, that the first type of session of the terminal device is in an active state. Thus, the mobility management network element can determine whether the first type of session is active based on a service request initiated by a terminal device in an idle state. If it is determined that the first type of session is active, the terminal device can then determine whether a first type of session exists and choose whether to request activation of the first type of session in the service request.

[0019] In one possible design, determining whether a terminal device has a first-type session can include receiving a session establishment request message from the terminal device, the session establishment request message being used to request the establishment of a first-type session. Therefore, the mobility management network element can also determine whether the terminal device has a first-type session based on the session establishment request message initiated by the terminal device.

[0020] In one possible design, the session establishment request message may include at least one of the following: an emergency request, an emergency data network name, or a network slice identifier corresponding to the first type of session. The emergency request is used to request the first type of session and can identify the established session as a first type of session.

[0021] In one possible design, sending the first information to the access network device may include: sending a configuration update message or an N2 request message to the access network device, wherein the configuration update message or N2 request message includes the first information.

[0022] Secondly, a communication method is provided, which can be applied to the network side, such as access network equipment on the network side, modules (e.g., circuits, processors, chips, or chip systems) in the access network equipment, or logical nodes, logical modules, or software that can implement all or part of the functions of the access network equipment. Taking the application of this method to an access network equipment as an example, in this method: receiving second information, the second information is used to trigger the access network equipment not to configure inactive discontinuous reception parameters to the terminal equipment, or to trigger the access network equipment to configure inactive discontinuous reception parameters to be empty to the terminal equipment; according to the second information, configuring inactive discontinuous reception parameters to be empty to the terminal equipment, or not configuring inactive discontinuous reception parameters to the terminal equipment; or, when the condition for the terminal equipment to enter the inactive state is met, not instructing the terminal equipment to enter the inactive state according to the second information.

[0023] In this communication method, the access network device can configure the terminal device not to use inactive discontinuous reception when a first type of session exists and the terminal device enters an inactive state, based on the received second information. This enables the terminal device to promptly recover from the inactive state to the connected state to receive or send data related to the first type of session.

[0024] In one possible design, configuring the inactive discontinuous reception parameters of the terminal device to be empty may include: sending a first message to the terminal device, the first message being used to trigger the terminal device to enter the inactive state, the first message carrying the inactive discontinuous reception parameters, which are empty. Thus, the access network device can configure the terminal device to have empty inactive discontinuous reception parameters to update or replace locally existing inactive discontinuous reception parameters that are not empty.

[0025] In one possible design, the non-active state discontinuous reception parameters may include a ran-Extended Paging Cycle.

[0026] In one possible design, the second information includes the first information. Receiving the second information may include receiving the first information from a mobility management network element. The first information is used to trigger the access network device not to configure inactive discontinuous reception parameters to the terminal device, or to trigger the access network device to configure the inactive discontinuous reception parameters to be empty to the terminal device. Therefore, the access network device can configure the terminal device not to use inactive discontinuous reception when a first type of session exists and the device enters an inactive state, based on the triggering of the mobility management network element.

[0027] In one possible design, the method may further include: determining, based on first information, that the terminal device has a first type of session, the first type of session being used for the terminal device's emergency services. Therefore, the access network device can also detect the existence of the first type of session on the terminal device based on the first information.

[0028] In one possible design, the first information may include: indication information for instructing the access network device to configure the terminal device to disable inactive discontinuous reception; or, indication information for instructing the access network device to delete the idle discontinuous reception parameters and / or the inactive discontinuous reception parameters of the terminal device; or, indication information for indicating that the terminal device has a first type of session, the first type of session being used for the terminal device's emergency services.

[0029] In one possible design, the first information can be the first RRC Inactive auxiliary information corresponding to the terminal device, which does not include idle discontinuous reception parameters.

[0030] In one possible design, the method may further include: receiving second RRC Inactive assistance information corresponding to the terminal device from the mobility management network element, wherein the second RRC Inactive assistance information includes idle state discontinuous reception parameters.

[0031] In one possible design, the second information includes third information. Receiving the second information may include receiving the third information from the terminal device. The third information is used to trigger the access network device to configure the terminal device to have empty inactive discontinuous reception parameters. Therefore, the access network device can configure the terminal device not to use inactive discontinuous reception when a first type of session exists and the device enters an inactive state, based on the triggering of the terminal device.

[0032] In one possible design, the method may further include: determining, based on third information, that the terminal device has a first type of session, whereby the first type of session is used for the terminal device's emergency services. Thus, the access network device can also detect the existence of a first type of session on the terminal device based on the third information.

[0033] In one possible design, the third information may include: indication information for indicating that the first inactive discontinuous reception parameters sent by the access network device are refused; or, indication information for indicating that there is a first type of session, the first type of session being used for emergency services of the terminal device; or, indication information for indicating that the access network device configures the inactive discontinuous reception parameters to be empty for the terminal device.

[0034] The technical effects of the second aspect can be found in the description of the technical effects of the method described in the first aspect above, and will not be repeated here.

[0035] Thirdly, a communication method is provided, which can be applied to the terminal device side, such as the terminal device or the communication module in the terminal device, or the circuit or chip in the terminal device responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core). Taking the application of this method to a terminal device as an example, in this method: a first inactive discontinuous reception parameter is received from the access network device, the first inactive discontinuous reception parameter being non-empty; when the terminal device has a first type of session, and the first type of session is used to serve the terminal device's emergency services, a third message is sent to the access network device, the third message being used to trigger the access network device to configure the inactive discontinuous reception parameter of the terminal device to be empty.

[0036] In this communication method, if a first type of session is determined to exist, the terminal device may not use the non-empty first inactive discontinuous reception parameters configured by the access network device, but instead send third information to the access network device to instruct the access network device to configure the inactive discontinuous reception parameters to be empty. Thus, when a first type of session exists and the terminal device enters the inactive state, it will not use inactive discontinuous reception, thereby ensuring that it can receive or send data related to the first type of session in a timely manner.

[0037] In one possible design, the third information may include: indication information for indicating that the first inactive discontinuous reception parameter is refused to be enabled; or, indication information for indicating that the terminal device has a first type of session; or, indication information for indicating that the access network device configures the inactive discontinuous reception parameter to be empty to the terminal device.

[0038] In one possible design, receiving the first inactive state discontinuous reception parameters from the access network device may include: receiving a first message, which triggers the terminal device to enter an inactive state, and the first message carries the first inactive state discontinuous reception parameters; and third information including indication information for indicating rejection of entering the inactive state. Thus, when the access network device triggers its entry into the inactive state and receives the non-empty first inactive state discontinuous reception parameters, the terminal device can determine whether a first type of session exists. If a first type of session exists, it will refuse to enter the inactive state and use the first inactive state discontinuous reception.

[0039] In one possible design, the method may further include: receiving a second inactive state discontinuous reception parameter from the access network device, wherein the second inactive state discontinuous reception parameter is empty; and disabling inactive state discontinuous reception based on the second inactive state discontinuous reception parameter. Thus, after the terminal device refuses to use the first inactive state discontinuous reception, the access network device can reconfigure the terminal device with an empty parameter for inactive state discontinuous reception, so that the terminal device uses the empty parameter inactive state discontinuous reception when entering the inactive state. Therefore, the terminal device does not use inactive state discontinuous reception when a first type of session exists and when entering the inactive state, ensuring timely reception or transmission of data related to the first type of session.

[0040] Fourthly, a communication method is provided. This method can be executed by a mobility management network element (MLE), a component of the MLE, such as a processor, chip, or chip system of the MLE, or a logic module or software capable of implementing all or part of the MLE. Taking the application of this method to a MLE as an example, in this method: it is determined that the terminal device has a first type of session, which is used for the terminal device's emergency services; first information is sent to the access network device, which is used to configure the period length of the terminal device's inactive discontinuous reception. The first information includes the period length of the first idle discontinuous reception, which is less than a first threshold.

[0041] In this communication method, when the mobility management network element determines that there is a first type of session, it can send first information to the access network device to configure the period length of the inactive discontinuous reception of the terminal device to be less than or equal to a first threshold. This triggers the access network device to configure the period length of the inactive discontinuous reception of the terminal device to be less than or equal to the first threshold. This ensures that the inactive discontinuous reception used by the terminal device when entering the inactive state will not keep the terminal device in a sleep state for a long time. As a result, when there is data transmission related to the first type of session, it can ensure that the terminal device can quickly resume the connected state from the sleep state and receive or send data related to the first type of session.

[0042] In one possible design, the first information can be the first RRC inactive auxiliary information corresponding to the terminal device.

[0043] In one possible design, sending the first information to the access network device may include: sending the first information to the access network device when the first type of session is inactive.

[0044] In one possible design, the method may further include: receiving a service request from a terminal device, wherein the service request requests activation of a session that does not include a first type of session; and determining, based on the service request, that the first type of session of the terminal device is in an inactive state.

[0045] In one possible design, sending the first information to the access network device may include: sending the first information to the access network device when the first type of session is in an active state.

[0046] In one possible design, the method may further include: receiving a service request from a terminal device, wherein the service request requests activation of a session including a first type of session; and determining, based on the service request, that the first type of session of the terminal device is in an active state.

[0047] In one possible design, determining that the terminal device has a first type of session may include: receiving a session establishment request message from the terminal device, the session establishment request message being used to request the establishment of a first type of session.

[0048] In one possible design, the session establishment request message may include at least one of the following: an emergency request, an emergency data network name, or a network slice identifier corresponding to the first type of session, wherein the emergency request is used to request the first type of session.

[0049] In one possible design, sending the first information to the access network device may include: sending a configuration update message or an N2 request message to the access network device, wherein the configuration update message or N2 request message includes the first information.

[0050] Fifthly, a communication method is provided, which can be applied to the terminal device side, such as the terminal device or the communication module in the terminal device, or the circuit or chip in the terminal device responsible for communication functions (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core). Taking the application of this method to a terminal device as an example, in this method: it is determined that there is a first type of session, which is used for emergency services of the terminal device; a service request is sent to the mobility management network element, wherein the session requested to be activated in the service request includes the first type of session.

[0051] Sixthly, a communication method is provided, which can be applied to the terminal device side, such as the terminal device or the communication module in the terminal device, or the circuit or chip in the terminal device responsible for communication functions (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core). Taking the application of this method to a terminal device as an example, in this method: a first message is received, which is used to trigger the terminal device to enter an inactive state; when the terminal device has a first type of session, and the first type of session is used to serve the terminal device's emergency services, discontinuous reception in the inactive state is disabled.

[0052] In this communication method, if the terminal device determines that there is a first type of session, then when the terminal device enters the inactive state, the terminal device does not use or enable the non-empty inactive discontinuous reception parameters configured by the access network device in the local storage, that is, it disables inactive discontinuous reception. In this way, the terminal device can not enter the sleep state after entering the inactive state, and when there is data transmission related to the first type of session, it can promptly recover from the inactive state to the connected state to receive or send the data related to the first type of session.

[0053] In a seventh aspect, a communication apparatus is provided for implementing the various methods described above. This communication apparatus may be a mobility management network element as described in the first aspect, or may include a mobility management network element as described in the first aspect, or a device, such as a chip, included in a mobility management network element as described in the first aspect. The communication apparatus includes corresponding modules, units, or means for implementing the methods described in the first aspect. These modules, units, or means may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0054] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module determines that the terminal device has a first type of session, which is used for the terminal device's emergency services. The transceiver module sends first information to the access network device, which triggers the access network device to either not configure inactive discontinuous reception parameters for the terminal device or to configure the inactive discontinuous reception parameters for the terminal device to be empty.

[0055] In one possible design, the first information can be the first RRC Inactive auxiliary information corresponding to the terminal device, which does not include idle discontinuous reception parameters.

[0056] In one possible design, when the first type of session of the terminal device is released, the transceiver module is also used to send the second RRC Inactive auxiliary information corresponding to the terminal device to the access network device. The second RRC Inactive auxiliary information includes idle state discontinuous reception parameters.

[0057] In one possible design, the first information may include: indication information for instructing the access network device to configure the terminal device to disable inactive discontinuous reception; or, indication information for instructing the access network device to delete the idle discontinuous reception parameters and / or the inactive discontinuous reception parameters of the terminal device; or, indication information for indicating that the terminal device has a first type of session.

[0058] In one possible design, the transceiver module, used to send first information to the access network device, may include: when the first type of session is inactive, the transceiver module is used to send the first information to the access network device.

[0059] In one possible design, the transceiver module is further configured to receive a service request from the terminal device, wherein the session requested for activation in the service request does not include the first type of session; the processing module is further configured to determine, based on the service request, that the first type of session of the terminal device is inactive.

[0060] In one possible design, the transceiver module, used to send first information to the access network device, may include: when the first type of session is in an active state, the transceiver module is used to send the first information to the access network device.

[0061] In one possible design, the transceiver module is further configured to receive a service request from the terminal device, wherein the session requested for activation in the service request includes a first type of session; the processing module is further configured to determine, based on the service request, that the first type of session of the terminal device is in an active state.

[0062] In one possible design, the processing module, used to determine that the terminal device has a first type of session, may include: a processing module used to control the transceiver module to receive a session establishment request message from the terminal device, the session establishment request message being used to request the establishment of a first type of session.

[0063] In one possible design, the session establishment request message may include at least one of the following: an emergency request, an emergency data network name, or a network slice identifier corresponding to the first type of session, wherein the emergency request is used to request the first type of session.

[0064] In one possible design, the transceiver module, used to send first information to the access network device, may include: the transceiver module, used to send a configuration update message or an N2 request message to the access network device, wherein the configuration update message or N2 request message includes the first information.

[0065] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device, and the receiving module implements the receiving function of the communication device.

[0066] In one possible design, the communication device may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the first aspect.

[0067] Eighthly, a communication apparatus is provided for implementing the various methods described above. This communication apparatus may be, or include, the access network device described in the second aspect, or a device, such as a chip, included in the access network device described in the second aspect. The communication apparatus includes corresponding modules, units, or means for implementing the methods described in the second aspect. These modules, units, or means may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0068] In some possible designs, the communication device includes a processing module and a transceiver module. The transceiver module is used to receive second information, which triggers the access network device to either not configure inactive discontinuous reception parameters to the terminal device or to trigger the access network device to configure the inactive discontinuous reception parameters to be empty to the terminal device. The processing module is used to, based on the second information, configure the inactive discontinuous reception parameters to be empty to the terminal device or not configure the inactive discontinuous reception parameters to the terminal device; or, if the condition for the terminal device to enter the inactive state is met, the processing module is used to, based on the second information, not instruct the terminal device to enter the inactive state.

[0069] In one possible design, the transceiver module, used to configure the terminal device to have empty inactive discontinuous reception parameters, may include: a transceiver module used to send a first message to the terminal device, the first message being used to trigger the terminal device to enter an inactive state, the first message carrying inactive discontinuous reception parameters, the inactive discontinuous reception parameters being empty.

[0070] In one possible design, the non-active state discontinuous reception parameters may include a ran-Extended Paging Cycle.

[0071] In one possible design, the second information includes the first information. A transceiver module for receiving the second information may include: a transceiver module for receiving the first information from a mobility management network element; wherein the first information is used to trigger the access network device not to configure inactive discontinuous reception parameters to the terminal device, or to trigger the access network device to configure the inactive discontinuous reception parameters to be empty to the terminal device.

[0072] In one possible design, the processing module is further configured to determine, based on the first information, that the terminal device has a first type of session, which is used for the terminal device's emergency services.

[0073] In one possible design, the first information may include: indication information for instructing the access network device to configure the terminal device to disable inactive discontinuous reception; or, indication information for instructing the access network device to delete the idle discontinuous reception parameters and / or the inactive discontinuous reception parameters of the terminal device; or, indication information for indicating that the terminal device has a first type of session, the first type of session being used for the terminal device's emergency services.

[0074] In one possible design, the first information can be the first RRC Inactive auxiliary information corresponding to the terminal device, which does not include idle discontinuous reception parameters.

[0075] In one possible design, the transceiver module is further configured to receive second RRC Inactive auxiliary information corresponding to the terminal device from the mobility management network element. The second RRC Inactive auxiliary information includes idle-state discontinuous reception parameters.

[0076] In one possible design, the second information includes the third information. The transceiver module, used to receive the second information, may include: a transceiver module used to receive the third information from the terminal device; wherein the third information is used to trigger the access network device to configure the inactive discontinuous reception parameters to be empty to the terminal device.

[0077] In one possible design, the processing module is further configured to determine, based on third information, that the terminal device has a first type of session, which is used for the terminal device's emergency services.

[0078] In one possible design, the third information may include: indication information for indicating that the first inactive discontinuous reception parameters sent by the access network device are refused; or, indication information for indicating that there is a first type of session, the first type of session being used for emergency services of the terminal device; or, indication information for indicating that the access network device configures the inactive discontinuous reception parameters to be empty for the terminal device.

[0079] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device, and the receiving module implements the receiving function of the communication device.

[0080] In one possible design, the communication device may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the second aspect.

[0081] Ninthly, a communication device is provided for implementing the various methods described above. This communication device may be a terminal device as described in the third aspect, or may include a terminal device as described in the third aspect, or a device, such as a chip, included in a terminal device as described in the third aspect. The communication device includes corresponding modules, units, or means for implementing the methods described in the third aspect, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0082] In some possible designs, the communication device includes a processing module and a transceiver module. The transceiver module is used to receive first inactive discontinuous reception parameters from the access network device, wherein the first inactive discontinuous reception parameters are not empty. If the processing module determines that a first type of session exists and that the first type of session is used for emergency services of the terminal device, the transceiver module is further used to send third information to the access network device, wherein the third information triggers the access network device to configure the inactive discontinuous reception parameters of the terminal device to be empty.

[0083] In one possible design, the third information may include: indication information for indicating that the first inactive discontinuous reception parameter is refused to be enabled; or, indication information for indicating that the terminal device has a first type of session; or, indication information for indicating that the access network device configures the inactive discontinuous reception parameter to be empty to the terminal device.

[0084] In one possible design, the transceiver module, used to receive first inactive discontinuous reception parameters from the access network device, may include: a transceiver module used to receive a first message, the first message being used to trigger the terminal device to enter an inactive state, the first message carrying the first inactive discontinuous reception parameters; and third information including indication information for indicating rejection of entering the inactive state.

[0085] In one possible design, the transceiver module is further configured to receive a second inactive discontinuous reception parameter from the access network device, wherein the second inactive discontinuous reception parameter is empty; the processing module is further configured to disable inactive discontinuous reception based on the second inactive discontinuous reception parameter.

[0086] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device, and the receiving module implements the receiving function of the communication device.

[0087] In one possible design, the communication device may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the third aspect.

[0088] In a tenth aspect, a communication apparatus is provided for implementing the various methods described above. This communication apparatus may be a mobility management network element as described in the fourth aspect, or may include a mobility management network element as described in the fourth aspect, or a device, such as a chip, included in a mobility management network element as described in the third aspect. The communication apparatus includes corresponding modules, units, or means for implementing the methods described in the fourth aspect, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0089] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module is used to determine that the terminal device has a first type of session, which is used for emergency services of the terminal device. The transceiver module is used to send first information to the access network device. The first information is used to configure the period length of inactive discontinuous reception of the terminal device. The first information includes the period length of first idle discontinuous reception, which is less than a first threshold. For a related description of the communication device described in the tenth aspect, please refer to the communication method described in the fourth aspect above.

[0090] Eleventhly, a communication device is provided for implementing the various methods described above. This communication device may be a terminal device as described in the fifth aspect, or may include a terminal device as described in the fifth aspect, or a device, such as a chip, included in a terminal device as described in the fifth aspect. The communication device includes corresponding modules, units, or means for implementing the methods described in the fifth aspect. These modules, units, or means may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0091] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module is used to determine if a first type of session exists, which is used for emergency services of the terminal device. The transceiver module is used to send a service request to the mobility management network element, wherein the service request requests activation of a session including the first type of session.

[0092] In a twelfth aspect, a communication device is provided for implementing the various methods described above. This communication device may be a terminal device as described in the sixth aspect, or may include a terminal device as described in the sixth aspect, or a device, such as a chip, included in a terminal device as described in the sixth aspect. The communication device includes corresponding modules, units, or means for implementing the methods described in the sixth aspect, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0093] In some possible designs, the communication device includes a processing module and a transceiver module. The transceiver module is used to receive a first message, which triggers the terminal device to enter an inactive state. If the terminal device has a first type of session, and the first type of session is used to serve the terminal device's emergency services, the processing module is used to disable discontinuous reception in the inactive state.

[0094] In a thirteenth aspect, a communication device is provided (e.g., the communication device may be a chip or a chip system). The communication device includes a processor for implementing the functions involved in any of the preceding aspects.

[0095] In one possible design, the communication device may further include a memory for storing necessary program instructions and data. A processor is coupled to the memory and is used to execute the computer program or instructions stored in the memory, causing the communication device to perform the method described in any of the possible implementations of the first to sixth aspects.

[0096] In one possible design, the communication device described in aspect thirteen may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in aspect thirteen and other communication devices.

[0097] In one possible design, the processor can be integrated with the memory.

[0098] In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.

[0099] In a fourteenth aspect, a communication device is provided, the communication device including a processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices outside the communication device and transmit them to the processor or to send signals from the processor to other communication devices outside the communication device, the processor being configured to implement the method as described in any one of the possible implementations of the first to sixth aspects via logic circuits or execution code instructions.

[0100] It is understood that when the communication device provided in either the thirteenth or fourteenth aspect is a chip, the aforementioned transmitting action / function can be understood as an output, and the aforementioned receiving action / function can be understood as an input.

[0101] In a fifteenth aspect, a computer-readable storage medium is provided, which stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in any one of the first to sixth aspects.

[0102] In a sixteenth aspect, a computer program product including instructions is provided, comprising computer program code, which, when executed on a communication device, enables the communication device to perform the method described in any one of the first to sixth aspects.

[0103] In a seventeenth aspect, a communication system is provided, comprising: a mobility management network element for implementing the method described in the first aspect, and an access network device for implementing the method described in the second aspect. Alternatively, it may comprise: an access network device for implementing the method described in the second aspect and a terminal device for implementing the method described in the third aspect.

[0104] Eighteenthly, a communication chip is provided, wherein instructions are stored that, when the chip is operated on a communication device, cause the method described in any one of the first to sixth aspects above to be implemented. Attached Figure Description

[0105] Figure 1 is a schematic diagram of a 5G system network architecture;

[0106] Figure 2 is a schematic diagram of a service request triggered by a terminal device;

[0107] Figure 3 is a schematic diagram of a service request triggered by a CN.

[0108] Figure 4 is a schematic diagram of a DRX and eDRX;

[0109] Figure 5 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0110] Figures 6 to 11 are schematic flowcharts of the communication method provided in the embodiments of this application;

[0111] Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0112] Figure 13 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0113] This application will present various aspects, embodiments, or features relating to a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches may also be used.

[0114] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communication (GSM), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 4th generation (4G) mobile communication system, such as Long Term Evolution (LTE) system, 5th generation (4G) mobile communication system, such as New Radio (NR) system, and future communication systems.

[0115] To better understand the embodiments of this application, the following points are explained before introducing the embodiments of this application.

[0116] First, in the embodiments of this application, "for indicating" can include both direct and indirect indication. When describing a certain "indication information" for indicating A, it can include whether the indication information directly indicates A or indirectly indicates A, but does not necessarily mean that the indication information carries A.

[0117] The information indicated by the instruction is called the information to be instructed. In the specific implementation process, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the instruction overhead caused by individually indicating the same information.

[0118] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0119] Secondly, in the embodiments of this application, the terms "first," "second," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, "first device" and "second device" are only used to distinguish different devices and do not limit their order. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., are not necessarily different.

[0120] Third, in the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances. They are not time limits, nor do they require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0121] Fourth, in the embodiments of this application, the words "exemplary" or "for example" are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0122] Fifth, in this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "terminal device sending information" can be understood as a terminal device sending information to another device (such as a network device), or it can be understood as logical module 1 in the terminal device sending information to logical module 2 in the terminal device.

[0123] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "terminal device receiving information" can be understood as a terminal device receiving information from another device (such as a network device), or it can be understood as logical module 1 in the terminal device receiving information from logical module 2 in the terminal device.

[0124] Sixth, the phrase "sending information to... (e.g., a terminal device)" in this application, or the relevant illustrations in the accompanying drawings, can be understood as the destination of the information being the terminal device. This can include sending information directly or indirectly to the terminal device. The phrase "receiving information from... (e.g., a terminal device)," or "receiving information from... (e.g., a terminal device)," or the relevant illustrations in the accompanying drawings, can be understood as the source of the information being the terminal device. This can include receiving information directly or indirectly from the terminal device. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood in a similar way, and will not be elaborated further here.

[0125] The technical solutions of this application embodiment can be applied to various communication systems, such as 4th generation (4G) mobile communication systems, such as long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, 5G mobile communication systems, such as new radio (NR) systems, and future communication systems.

[0126] For ease of understanding, the following section will first introduce the relevant technologies, concepts, or architectures that may be involved in the embodiments of this application:

[0127] 1. 5G mobile communication system

[0128] Referring to Figure 1, which is a schematic diagram of a network architecture applicable to an embodiment of this application, the 5G network architecture based on service-based architecture (SBA) in a non-roaming scenario defined during the 3rd generation partnership project (3GPP) standardization process is used as an example. As shown in Figure 1, the 5G system includes terminal equipment, a radio (R) access network (AN), and a core network (CN). The terminal equipment accesses the data network (DN) through the AN and CN.

[0129] Terminal equipment can be a terminal device with transceiver functions, or it can be a chip or chip system installed in the terminal device. This terminal equipment can also be referred to as user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. The terminal devices in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, Internet of Things (IoT) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), smart robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes. The terminal device in this application can be a wireless terminal in the home, an in-vehicle terminal, a roadside unit (RSU) with terminal function, or an aerial device (e.g., an intelligent robot, a hot air balloon, a drone, or an airplane). The terminal device can also be an in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit built into a vehicle as one or more components or units. The terminal device can also be other devices with terminal function; for example, it can be a device that performs terminal function in device-to-device (D2D) communication.

[0130] The embodiments of this application do not limit the device form of the terminal device. The device used to implement the function of the terminal device can be the terminal device itself; it can also be a device that supports the terminal device in implementing the function, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete components.

[0131] An Access Network (AN) is used to implement access-related functions. It can provide network access for authorized users in a specific area and determine different quality transmission links to transmit user data based on user level, service requirements, etc. The AN forwards control signals and user data between the terminal equipment and the Network Controller (CN). The AN may include: access network equipment, also known as access network nodes, radio access network (RAN) nodes, RAN equipment, RAN entities, or access nodes, etc., located on the network side of the aforementioned communication system. It is used to help terminal equipment achieve wireless access and is a device with wireless transceiver capabilities, or a chip or chip system that can be installed in the device.

[0132] The access network equipment includes, but is not limited to: base stations, evolved Node Bs (eNodeBs / eNBs), access points (APs), transmit / receive points (TRPs), next-generation Node Bs (gNBs), base stations in future mobile communication systems, or access nodes in wireless fidelity (Wi-Fi) systems. Access network equipment can be macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, and radio controllers in open radio access networks (ORAN) or centralized radio access networks (CRAN) scenarios. Access network equipment can also be one or a group of antenna panels (including multiple antenna panels) of a 5G base station, or it can be a network node constituting a gNB, TRP, TP, or transmission measurement function (TMF), such as a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), a radio unit (RU), or a roadside unit (RSU) with base station functionality. Optionally, access network equipment can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be an RSU. All or part of the functions of the access network equipment in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network equipment in this application can also be a logical node, logical module, or software capable of implementing all or part of the functions of the access network equipment.

[0133] In this network, CU and DU can be configured separately or included in the same network element, such as a baseband unit (BBU). RU can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that access network equipment can be CU nodes, DU nodes, or equipment including both CU and DU nodes. Furthermore, CUs can be classified as network equipment within the access network RAN ​​or as network equipment within the CN; no restrictions are placed here.

[0134] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0135] In this application embodiment, the form of the access network device is not limited. The device used to implement the function of the access network device can be the access network device itself; it can also be a device that supports the access network device in implementing the function, such as a chip system. The device can be installed in the access network device or used in conjunction with the access network device.

[0136] CN is primarily responsible for maintaining the subscription data of the mobile network and providing terminal devices with functions such as session management, mobility management, policy management, and security authentication. The CN mainly includes the following network elements: User plane function (UPF), Authentication server function (AUSF), Access and mobility management function (AMF), Session management function (SMF), Network slice selection function (NSSF), Network exposure function (NEF), Network function repository function (NRF), Policy control function (PCF), Unified data management (UDM), Application function (AF), Edge application server discovery function (EASDF), Network slice admission control function (NSACF), Service communication proxy (SCP), and Network slice-specific and SNPN authentication and authorization function (NSSAAF).

[0137] The following is a brief explanation of the NF functions included in CN:

[0138] The UPF is primarily responsible for user data processing (forwarding, receiving, billing, etc.). For example, the UPF can receive user data from the DN and forward it to the terminal device through the access network equipment. The UPF can also receive user data from the terminal device through the access network equipment and forward it to the DN. In a Protocol Data Unit (PDU) session, the UPF directly connected to the DN via N6 is also called the Protocol Data Unit Session Anchor (PDU Session Anchor, PSA).

[0139] AUSF is primarily used to perform security authentication for terminal devices.

[0140] AMF is primarily used for mobility management in mobile networks. Examples include user location updates, user network registration, and user handover.

[0141] SMF is primarily used for session management in mobile networks. This includes session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User-Defined Provider) to handle packet forwarding.

[0142] NSSF is primarily used to select network slices for end devices.

[0143] The NEF is primarily used to support the opening of capabilities and events. For example, the NEF can expose some capabilities of the 5G network to third-party applications through application program interfaces (APIs). Third-party applications can obtain some capabilities of the 5G network by calling the APIs provided by the NEF through the AF, enabling them to control certain behaviors of the 5G network and terminal devices.

[0144] NRF is mainly used to provide network element discovery functions. Based on requests from other network elements, it provides network element information corresponding to the network element type. It also provides network element management services, such as network element registration, updating, deregistration, and network element status subscription and push.

[0145] The PCF primarily supports providing a unified policy framework to control network behavior, delivering policy rules to control-layer network functions, and acquiring user subscription information related to policy decisions. The PCF can provide policies to the AMF and SMF, such as Quality of Service (QoS) policies and slice selection policies.

[0146] UDM is primarily used to store user data, such as contract data and authentication / authorization data.

[0147] AF (Application Filter) is a functional network element deployed at a third party to convey application-side requirements to the network side, such as QoS requirements or user state event subscriptions. Its main function is to inform the PCF (Process Control Fund) of the latest business requirements of a particular application from the third party. The PCF then generates corresponding QoS rules to ensure that the network services meet the requirements of the third party.

[0148] EASDF primarily relies on Domain Name System (DNS) messages, including exchanging DNS messages from terminal devices and forwarding DNS messages to central (C)-DNS or local (L)-DNS for DNS queries.

[0149] NSACF primarily monitors and controls the number of registered terminal devices on each network slice and the number of PDU sessions established on each network slice. It provides event-based network slice status notifications and reports to network functions (NFs).

[0150] SCP primarily supports Hypertext Transfer Protocol (HTTP) signaling indirect communication functions, providing signaling message routing and forwarding between NFs in the CN.

[0151] NSSAAF can be used to support slice authentication and authorization, as well as to support access to independent, non-public networks using the credentials of the credential holder.

[0152] It should be understood that the above examples illustrate several core network elements included in the CN. In addition, other core network elements may also be included, such as the unified data repository (UDR), which is mainly used to store structured data. The stored content includes contract data and policy data, externally exposed structured data, and application-related data.

[0153] It is understandable that the aforementioned network elements or functions can be physical entities in hardware devices, software instances running on dedicated hardware, or virtualization functions instantiated on a shared platform (e.g., a cloud platform). Simply put, an NF can be implemented in hardware or software.

[0154] A Data Network (DN) is a network located outside of the carrier's network. A carrier's network can connect to multiple DNs, and various services can be deployed on a DN, providing data and / or voice services to terminal devices. For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can act as terminal devices, and a control server for these sensors is deployed within the DN. The control server provides services to the sensors. Sensors can communicate with the control server, receive instructions from it, and transmit the collected sensor data back to the control server accordingly. Another example is a DN serving as the internal office network of a company. Employees' mobile phones or computers can act as terminal devices, accessing information and data resources on the company's internal office network.

[0155] In Figure 1, Nnef, Nnrf, Npcf, Nudm, Nudr, Nnwdaf, Naf, Nausf, Namf, Nsmf, Ndccf, N1, N2, N3, N4, and N6 are interface sequence numbers. For example, the meanings of these interface sequence numbers can be found in the 3GPP standard protocols, and this application does not limit the meanings of these interface sequence numbers. It should be noted that the interface names between the various network functions in Figure 1 are merely examples; in specific implementations, the interface names of this system architecture may be other names, and this application does not limit them. Furthermore, the names of the messages (or signaling) transmitted between the various network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0156] It should be noted that in the architecture shown in Figure 1, the interface between (R)AN and CN can also be called the NG interface (not shown in Figure 1). (R)AN and CN are connected through the NG interface. The NG interface can include the NG-C interface and the NG-U interface. The NG-C interface is the control plane interface, connecting (R)AN and AMF, and is used to transmit control plane data. The NG-U interface is the user plane interface, connecting (R)AN and UPF, and is used to transmit user plane data.

[0157] It should be understood that AMF, SMF, UPF, NEF, AUSF, NRF, PCF, and UDM shown in Figure 1 can be understood as network elements in the core network used to implement different functions, such as network slices that can be combined as needed. These core network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements. For details, please refer to the relevant description in 3GPP technical specification (TS) 23.501, which will not be elaborated here.

[0158] 2. Three RRC states of terminal devices

[0159] In 5G communication systems, RRC states can include RRC connected state (RRC_CONNECTED), RRC idle state (RRC_IDLE), and RRC inactive state (RRC_INACTIVE). Both the idle and inactive states can be referred to as disconnected states. When the terminal device is not receiving or transmitting signaling and / or service data, it can enter the idle or inactive state to reduce power consumption. The terminal device can switch between these three RRC states.

[0160] When the terminal device is in RRC connected state (RRC_CONNECTED), the network elements in the 5G architecture shown in Figure 1 all serve the terminal device normally. For example, (R)AN, AMF, SMF, UPF, etc. all maintain the context of the terminal device. At this time, the terminal device can perform services normally, such as sending data packets to DN to access services through (R)AN and UPF.

[0161] When the terminal device is in the RRC idle state (RRC_IDLE), all contexts on the (R)AN are released, and the N3, N2, N1, and air interface (between the terminal device and the (R)AN) are disconnected, preventing the terminal device from accessing services. If the terminal device wants to access services, it first needs to initiate a service request process to return to the connected state. If downlink data that the terminal device needs to receive arrives at the UPF (from the DN), the UPF will notify the SMF and AMF. The AMF will then restore the (R)AN context and initiate a paging process. After receiving the paging, the terminal device will initiate a service request process to return to the connected state. The paging triggered by the CN in the idle state can be called CN paging.

[0162] The RRC_INACTIVE state is a special case of the connected state: In the connected state, (R)AN can determine, based on its local logic, to release the terminal device into the RRC_INACTIVE state. At this time, the air interface connection is released, but the N2 and N3 connections remain normal, and the (R)AN still retains the terminal device's context. For core network elements (AMF, SMF, UPF, etc.), the terminal device is still considered to be in the connected state and can be located at any time. In the RRC_INACTIVE state, if the terminal device wants to access services, it can directly restore the RRC connection with (R)AN. If downlink data arrives at the UPF, since the N3 connection still exists, the data will be directly sent to (R)AN. (R)AN determines that the terminal device needs to be restored to the connected state, triggers (R)AN paging, restores the air interface connection with the terminal device, and sends data to the terminal device. This paging initiated by (R)AN in the inactive state can be called (R)AN paging.

[0163] 3. 5G Service Request Process

[0164] Taking the UE as an example, when uplink data transmission occurs, the UE can execute the service request process shown in Figure 2 when it transitions from the idle state to the connected state. This service request process is initiated by the UE. As shown in Figure 2, the service request process includes:

[0165] S201. The UE sends a service request to the (R)AN.

[0166] Accordingly, (R)AN receives service requests from the UE.

[0167] The service request includes information such as the list of PDU sessions to be activated, the list of allowed PDU sessions, and the PDU session status.

[0168] S202, (R)AN sends an N2 message to AMF.

[0169] Correspondingly, the AMF receives the N2 message from (R)AN.

[0170] The N2 message includes a service request.

[0171] Authentication security between S203, AMF, UE and AUSF.

[0172] After receiving a service request, AMF triggers authentication and security procedures for the UE.

[0173] S204. AMF sends a PDU session update session management (SM) context request (Nsmf_PDUSession_UpdateSMContext Request) to SMF.

[0174] Correspondingly, the SMF receives a PDU session update SM context request from the AMF.

[0175] S205b and SMF are used for UPF selection.

[0176] S206a, SMF sends an N4 Session Modification Request to PSA UPF.

[0177] Correspondingly, the PSA UPF receives N4 session modification requests from the SMF.

[0178] S206b: PSA UPF sends an N4 Session Modification Response to SMF.

[0179] Correspondingly, the SMF receives the N4 session modification response from the PSA UPF.

[0180] S206c, SMF sends an N4 Session Establishment Request to the new intermediate-UPF (I-UPF).

[0181] Correspondingly, the new I-UPF receives the N4 session establishment request from the SMF.

[0182] S206d, the new I-UPF sends an N4 Session Establishment Response to the SMF.

[0183] Accordingly, the SMF receives an N4 session establishment response from the new I-UPF.

[0184] S207a, SMF sends an N4 Session Modification Request to PSA UPF.

[0185] Correspondingly, the PSA UPF receives N4 session modification requests from the SMF.

[0186] S207b: The PSA UPF sends an N4 Session Modification Response to the SMF.

[0187] Correspondingly, the SMF receives the N4 session modification response from the PSA UPF.

[0188] S208a, SMF sends an N4 Session Modification Request to the old I-UPF.

[0189] Correspondingly, the old I-UPF receives N4 session modification requests from the SMF.

[0190] S208b: The old I-UPF sends an N4 Session Modification Response to the SMF.

[0191] Correspondingly, the SMF receives the N4 session modification response from the old I-UPF.

[0192] S209. Old I-UPF forwards buffered downlink (DL) data to new I-UPF.

[0193] S210, Buffered DL data forwarding from old I-UPF to PSA UPF.

[0194] S211. The SMF sends a PDU session update SM context response (Nsmf_PDUSession_UpdateSMContext Response) to the AMF.

[0195] Correspondingly, the AMF receives a PDU session update SM context response from the SMF.

[0196] S212, AMF sends an N2 request to (R)AN.

[0197] Correspondingly, (R)AN receives N2 requests from AMF.

[0198] S213, (R)AN sends an RRC connection reconfiguration to the UE.

[0199] Accordingly, the UE receives an RRC connection reconfiguration from (R)AN.

[0200] Therefore, the UE recovers from the idle state to the connected state, and the UE sends uplink (UL) data to the PSA UPF.

[0201] In the service request process shown in Figure 2 above, the UE initiates a service request. After the AMF receives the service request through the (R)AN, it instructs the SMF to restore the UE's user plane connection (i.e., the N3 connection between the UPF and the (R)AN). After receiving the AMF's instruction, the SMF configures the UPF to restore the N3 connection and notifies the AMF after the connection is restored.

[0202] AMF instructs the UE to accept the service request, and at the same time, (R)AN reconfigures the air interface connection for service connection-mode service access. The UE is restored to the connection state through RRC connection reconfiguration. The UE can send UL data to the PSA UPF through (R)AN, or the UE can send UL data to the PSA UPF through (R)AN and I-UPF.

[0203] A session is the path (i.e., UE-(R)AN-UPF) for a UE to access services in 5G. Each UE can have multiple sessions (e.g., for different network slices, accessing different data networks, etc.). Each session can also have active and deactivated states.

[0204] Session activation and deactivation are the states of a 5G session. When a session is deactivated, its air interface and N3 connection are released, and the context related to this session on the (R)AN is deleted, leaving only the control plane context on the UE and SMF (i.e., proving that the session still exists). When a deactivated session receives a corresponding data packet, it is necessary to activate the session through a service request procedure, rebuild the user plane connection, and send the data packet.

[0205] When downlink data transmission is present, the service request process for the UE to transition from idle state to connected state can be initiated by the network, as shown in Figure 3. This service request process includes:

[0206] S301, UPF receives DL data.

[0207] S302a, UPF sends data notification to SMF.

[0208] Correspondingly, the SMF receives data notifications from the UPF.

[0209] S302b and SMF send a data notification ACK to UPF.

[0210] Correspondingly, the UPF receives a data notification response from the SMF.

[0211] S302c and UPF send DL data to SMF.

[0212] Correspondingly, the SMF receives DL data from the UPF.

[0213] S303a, SMF sends a communication N1N2 message transfer to AMF.

[0214] Correspondingly, the SMF receives communication N1N2 message transmissions from the AMF.

[0215] S303b, AMF sends a communication N1N2 message transfer response to SMF.

[0216] Correspondingly, the SMF receives the communication N1N2 message transmission response from the AMF.

[0217] S303c and SMF send a failure indication to UPF.

[0218] Correspondingly, the UPF receives a failure indication from the SMF.

[0219] S304a, UP reactivation (Connected) between AMF and UE.

[0220] S304b, AMF sends a paging message to (R)AN.

[0221] S304b and (R)AN send paging messages to the UE.

[0222] S304c and AMF send a non-access stratum (NAS) notification to the UE.

[0223] Correspondingly, the UE receives a NAS notification from the AMF.

[0224] S305, AMF sends a communication N1N2 transfer failure notification (Namf_Communicator_N1N2TransferFailure Notification) to SMF.

[0225] Correspondingly, the SMF receives a communication N1N2 transmission failure notification from the AMF.

[0226] S306. Service Request Procedure between UE and UPF.

[0227] S306a, AMF sends a communication N1N2 transfer failure notification (Namf_Communicator_N1N2TransferFailure Notification) to SMF.

[0228] Correspondingly, the SMF receives a communication N1N2 transmission failure notification from the AMF.

[0229] S307. UE Configuration Update Procedure between UE and UPF.

[0230] S308 and UPF send DL data to UE via (R)AN.

[0231] In the service request flow shown in Figure 3, triggered by the CN, when downlink data arrives at the UPF, the UPF finds that the session does not have an N3 tunnel and notifies the SMF. If the UE is in idle state, the SMF instructs the AMF to page the UE. If the UE is in connected state, but the session is not active, steps S303-S305 are not required (the UE does not need to be paged), and S306 is executed directly.

[0232] The SMF restores the user plane N3 connection, and the RAN also restores the corresponding air interface connection. After the connection is restored, downlink data is transmitted normally.

[0233] For details on the specific implementation process of the service requests shown in Figures 2 and 3, please refer to the relevant description in 3GPP TS23.502, which will not be elaborated here.

[0234] 4. Extended Discontinuous Reception (eDRX) mode

[0235] To reduce the power consumption of terminal devices, 3GPP introduced Discontinuous Reception (DRX). DRX allows terminal devices to periodically enter a sleep mode. During this sleep mode, the terminal device does not monitor the physical downlink control channel (PDCCH) and shuts down its transceiver unit, thereby reducing power consumption. For details, please refer to the relevant descriptions in 3GPP TS23.501 and 38.300, which will not be elaborated upon here.

[0236] As shown in Figure 4(a), a DRX cycle includes a paging occasion (PO) and a sleep period. When the terminal device is in idle state (RRC_IDLE), the access network device configures DRX for the terminal device. The terminal device then monitors paging messages on the PO and enters a sleep state during the sleep period. That is, when the terminal device is in idle state, it does not continuously monitor paging messages, but rather periodically monitors paging at certain times and sleeps at other times.

[0237] To further reduce the power consumption of terminal devices, eDRX was introduced. eDRX functions similarly to DRX, both reducing power consumption by periodically putting the terminal device into a sleep state at certain times. Compared to DRX, eDRX allows the terminal device to enter a sleep state for a longer period. During this time, the terminal device can stop monitoring paging; this period is called the deep sleep period, which can last up to several tens of minutes. As shown in Figure 4(b), an eDRX cycle includes PTW and the deep sleep period. PTW consists of multiple DRX cycles. When the terminal device is idle, it monitors paging on the PO within the PTW; at other times, it enters a sleep state.

[0238] When a terminal device initiates registration, it negotiates with the AMF to determine the eDRX parameters to be used when entering the idle state. At this time, both the terminal device and the AMF are locally configured with the eDRX parameters to be used when entering the idle state. After the AN Release procedure is performed between the AMF and the terminal device, the terminal device enters the idle state using the corresponding eDRX. When the terminal device in the idle state has uplink data transmission, it can initiate a service request procedure as shown in Figure 2 above. After completing the service request procedure, or when there is downlink data transmission, the CN triggers the execution of the service request procedure as shown in Figure 3 above, and the terminal device returns from the idle state to the connected state.

[0239] In addition to configuring the eDRX used by the terminal device to enter the idle state (RRC_IDLE), (R)AN can also obtain the eDRX parameters used by the terminal device when entering the idle state from the AMF, determine the eDRX parameters used by the terminal device to enter the inactive state (RRC_INACTIVE) based on the eDRX parameters used by the terminal device when entering the idle state, and configure them for use when the terminal device enters the active state.

[0240] Currently, when a terminal device has an emergency session (or emergency service), the standard restricts that the AMF and the terminal device cannot use eDRX when entering idle state. That is, when there is an emergency session, the AMF and the terminal device are aware of this information, and will not use eDRX when entering idle state. This prevents the terminal device from being in sleep state when emergency session data arrives, thus being unable to be paged and unable to resume connection state, and thus missing the emergency message.

[0241] However, when the emergency session of the terminal device is not activated, the access network device will not be aware of the emergency session (no context). Therefore, when configuring the terminal device to change from connected state to inactive state, the access network device may still configure the terminal device to use eDRX to enter the inactive state, causing the terminal device to be in a deep sleep state. As a result, the terminal device cannot receive paging in time to restore the connected state, thus failing to receive emergency session data in time.

[0242] Therefore, this application provides a communication method and apparatus that can prevent terminal devices from being unable to receive emergency session data in a timely manner when they enter an inactive state because they are in a sleep state and cannot be restored to a connected state in time.

[0243] It should be understood that the “session” in the embodiments of this application usually refers to a PDU session, such as an emergency PDU session.

[0244] Referring to Figure 5, which is a schematic diagram of the architecture of a communication system provided in an embodiment of this application, it can be applied to the 5G network architecture shown in Figure 1 above. As shown in Figure 5, the communication system includes a terminal device, an access network device, and a mobility management network element, and communication between each other is not limited. For example, the terminal device can communicate with the mobility management network element through the access network device.

[0245] For a detailed description of the terminal equipment and access network equipment, please refer to the relevant descriptions of the terminal equipment and access network equipment shown in Figure 1 above, which will not be repeated here.

[0246] A mobility management network element (AMF) is a device deployed in the core network to provide services to terminal devices, enabling access management and mobility management of these devices. For example, it is responsible for maintaining the state of the terminal devices, managing their reachability, forwarding NAS messages (non-mobility management, MM), and forwarding SM N2 messages. For instance, when the method of this embodiment is applied to the 5G system shown in Figure 1, the AMF can be an AMF in the 5G system. As another example, when the method of this embodiment is applied to an LTE system, the AMF can be a mobility management entity (MME).

[0247] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0248] The communication method provided in the embodiments of this application will be described in detail below with reference to Figures 6-11.

[0249] For example, Figure 6 is a flowchart illustrating a communication method provided in an embodiment of this application. The communication method is illustrated using the communication between the mobility management network element, the access network device, and the terminal device shown in Figure 5 as an example.

[0250] As shown in Figure 6, the communication method includes:

[0251] S601, The mobility management network element determines that the terminal device has a first type of session.

[0252] The first type of session is used for emergency services of the service terminal device, or the first type of session is a session that provides emergency services. In this embodiment, the first type of session may also be called an emergency session, an emergency service session, an emergency service session, a session with emergency services, etc., and there is no limitation in this regard. For example, the emergency services corresponding to the first type of session include emergency calls such as 110, 119, and 120, earthquake notification messages, etc.

[0253] The statement that a terminal device has a Type I session can be understood as: the terminal device exists a Type I session, the terminal device maintains a Type I session, the terminal device has established a Type I session, or the sessions established by the terminal device or the sessions serving the terminal device include Type I sessions. No further limitation is imposed on this statement.

[0254] In one possible design, the mobility management network element (MLE) can determine whether the terminal device has established a first-type session based on a session establishment request message initiated by the terminal device. In this design, the terminal device sends a session establishment request message to the MLE, and the MLE receives the session establishment request message from the terminal device. The session establishment request message is used to request the establishment of a first-type session. Therefore, the MLE can determine whether the terminal device has a first-type session based on this session establishment request message.

[0255] The session establishment request message may include at least one of the following information to identify a first-type session: an emergency request, an emergency data network name (Emergency DNN), or a network slice identifier corresponding to the first-type session. Specifically, the emergency request is used to request a first-type session; the emergency data network name (Emergency DNN) indicates the data network accessed by the first-type session; and the network slice identifier corresponding to the first-type session indicates the network slice accessed by the first-type session. This network slice identifier corresponds to the first-type session, and the established session can be determined based on the network slice identifier, such as the single network slice selection assistance information (S-NSSAI) corresponding to the emergency session. It should be understood that this session establishment request message can also be used to establish other types of sessions.

[0256] In other words, when a terminal device establishes a session, the mobility management network element will sense what types of sessions the terminal device is establishing and establish a corresponding session context. Or, the mobility management network element can also determine whether the terminal device has a Type I session based on the terminal device's context.

[0257] In a possible design, if the mobility management network element determines that the terminal device has a first-type session, it can further determine whether the first-type session is active. If the first-type session is active, step S602 is executed. The active state of the first-type session can be understood as requiring data transmission related to the first-type session. This allows for more accurate control of the access network device to prevent it from configuring discontinuous reception for the terminal device when entering an inactive state, thus avoiding situations where the terminal device cannot receive or send data related to the first-type session in a timely manner.

[0258] In this design scheme, one possible implementation is that the mobility management network element (MLE) can determine whether a first-type session is activated based on a service request initiated by the terminal device. In this scheme, the terminal device sends a service request to the MLE, and the MLE receives the service request from the terminal device. The service request includes session information requesting activation, which can be indicated in list form, for example, a list of PDU session(s) to be activated. Therefore, the MLE can determine whether a first-type session is activated based on the session information requested in the service request. If the service request includes a first-type session, the MLE can determine that the first-type session is active; if it does not, it can determine that the first-type session is inactive. In another possible implementation, the MLE can store the active and inactive sessions of the terminal device in the terminal device's context, thereby determining whether a first-type session is active or inactive based on the terminal device's context.

[0259] For a terminal device, before initiating a service request, it can determine whether there is a first-type session. If there is, the session to be activated in the service request includes the first-type session; if not, the session to be activated in the service request does not include the first-type session.

[0260] Therefore, when it is determined that the terminal device has a first type of session, or when the first type of session is in an active state, in order to prevent the terminal device from entering a sleep state due to inactive discontinuous reception and being unable to receive or send data related to the first type of session in a timely manner, the following S602 is executed. Optionally, the mobility management network element also executes the following S602 when the first type of session is inactive, and there is no limitation on this.

[0261] Optionally, before sending the second information, the mobility management network element may also determine whether idle discontinuous reception has been configured for the access network device, or whether the access network device has been configured with idle discontinuous reception.

[0262] If an access network device is configured to perform idle-state discontinuous reception, it can be assumed that the access network device has previously sent an idle-state discontinuous reception message to the access network device. For example, the mobility management element can determine whether an idle-state discontinuous reception message has been previously sent to the access network device based on the context between the mobility management element and the access network device (e.g., the context of the terminal device, or the context of the terminal device between the mobility management network and the access network device).

[0263] In other words, the mobility management network element can determine whether it has sent idle discontinuous reception to the access network device before sending the second information. If it has not sent idle discontinuous reception to the access network device, then the second information may not include the idle discontinuous reception parameter. In this way, the access network device will not generate inactive discontinuous reception for the terminal device based on idle discontinuous reception. If it has sent idle discontinuous reception to the access network device, then the mobility management network element can trigger the access network device not to configure inactive discontinuous reception parameters for the terminal device, or trigger the access network device to configure inactive discontinuous reception parameters to be empty for the terminal device, through the following second information.

[0264] Alternatively, the mobility management network element can negotiate with the access network equipment whether to configure idle-state discontinuous reception. For example, if the mobility management network element does not send idle-state discontinuous reception parameters, the access network equipment will not generate inactive-state discontinuous reception parameters for the terminal equipment.

[0265] S602. The mobility management network element sends the second information to the access network equipment.

[0266] Correspondingly, the access network device receives the second information from the mobility management network element.

[0267] The second piece of information can be used to trigger the access network device not to configure inactive, discontinuous reception parameters to the terminal device.

[0268] Triggering the access network device to not configure inactive discontinuous reception parameters to the terminal device can mean that the access network device does not send inactive discontinuous reception parameters to the terminal device, causing the terminal device to disable, delete, or update the stored inactive discontinuous reception (where updating inactive discontinuous reception can mean updating the inactive discontinuous reception parameters to be empty, and causing the terminal device to disable, delete, or update the stored inactive discontinuous reception can be as follows: the access network device instructs the terminal device to disable, delete, or update the stored inactive discontinuous reception according to the second information), or the access network device sends inactive discontinuous reception parameters to the terminal device to be empty, or instructs the terminal device not to enter the inactive state. Therefore, when there is a first type of session, the terminal device will not use inactive discontinuous reception while in the inactive state and will enter a sleep state.

[0269] Optionally, after receiving the second information, the access network device does not generate inactive discontinuous reception parameters for the terminal device. Alternatively, the access network device updates its stored inactive discontinuous reception parameters to empty.

[0270] Among them, disabling inactive discontinuous reception parameters can refer to invalidating, not using, not starting, or stopping the use of inactive discontinuous reception parameters. Disabling, deleting, or updating inactive discontinuous reception parameters can be sent by the access network device to the terminal device before receiving the second information.

[0271] In this embodiment, the non-active state discontinuous reception parameter may include or be ran-ExtendedPagingCycle, eDRX parameter in RRC-INACTIVE, eDRX cycle in RRC-INACTIVE, RRC-INACTIVE eDRX parameter, or RRC-INACTIVE eDRX cycle, and there is no limitation thereto.

[0272] In one possible implementation, not sending or configuring inactive discontinuous reception parameters to the terminal device could mean that the access network device does not include the `ran-ExtendedPagingCycle` parameter in the RRC Release message sent to the terminal device. This `ran-ExtendedPagingCycle` parameter represents the inactive discontinuous reception parameter. For example, omitting this parameter defaults to the terminal device not enabling inactive discontinuous reception; alternatively, omitting this parameter defaults to the terminal device deleting the stored inactive discontinuous reception parameters; or, omitting this parameter defaults to the terminal device updating the stored inactive discontinuous reception parameters to be empty.

[0273] In other words, the second piece of information can be used to trigger the access network equipment to configure the terminal equipment to disable, delete, or update inactive discontinuous reception.

[0274] In some possible scenarios, the access network device may also determine, based on the second information, whether it sent inactive discontinuous reception parameters to the terminal device before receiving the second information.

[0275] For example, if the access network device has not sent any non-empty inactive discontinuous reception parameters to the terminal device before receiving the second information, then after receiving the second information, the access network device will not generate inactive discontinuous reception parameters for the terminal device (regardless of whether the parameters are empty), and therefore will not send inactive discontinuous reception parameters to the terminal device. Optionally, the inactive discontinuous reception parameters will not be sent to the terminal device until a new indication message (e.g., an indication that a first-type session has been released) is received from the mobility management network element.

[0276] If the access network device has sent non-empty inactive discontinuous reception parameters to the terminal device before receiving the second information, then after receiving the second information, the access network device will no longer generate inactive discontinuous reception parameters for the terminal device (regardless of whether the parameters are empty). Instead, it will configure the terminal device to disable, delete, or update the stored inactive discontinuous reception, or instruct the terminal device not to enter the inactive state until the first type of session is released, and then configure the terminal device to use the inactive discontinuous reception parameters.

[0277] Alternatively, the second piece of information can be used to trigger the access network device to configure the terminal device to have empty inactive discontinuous reception parameters.

[0278] An empty inactive discontinuous reception parameter can be understood as the inactive discontinuous reception parameter existing but with an empty value. Triggering the access network device to configure the inactive discontinuous reception parameter to be empty to the terminal device means that the access network device sends the inactive discontinuous reception parameter to the terminal device, but the sent inactive discontinuous reception parameter is empty. Even if the terminal device has previously stored non-empty inactive discontinuous reception parameters configured by the access network device, the empty inactive discontinuous reception parameter configured by the access network device to the terminal device can overwrite, update, or replace the previously stored non-empty inactive discontinuous reception parameter. When the terminal device receives an empty inactive discontinuous reception parameter, it is equivalent to not enabling inactive discontinuous reception, or having no inactive discontinuous reception at all. When there is a first-type session, this ensures that the terminal device will not enter a sleep state due to the use of inactive discontinuous reception when entering the inactive state.

[0279] In one possible implementation, sending or configuring the inactive discontinuous reception parameter to the terminal device to be empty can be achieved by the access network device sending the ran-ExtendedPagingCycle parameter in the RRC message to the terminal device, but this parameter is empty (e.g., the field is all 0).

[0280] Different connection states of the terminal device correspond to discontinuous reception, which can be DRX or eDRX as described in related technology 4 above. Specifically, inactive discontinuous reception refers to the discontinuous reception used when the terminal device enters an inactive state, or the discontinuous reception used for the inactive state of the terminal device. When the terminal device enters an inactive state, it enables this inactive discontinuous reception, monitoring paging for a period during the period of the inactive discontinuous reception, and then entering a sleep state for a period of time. Inactive discontinuous reception parameters are used to configure inactive discontinuous reception. These parameters can include the period of inactive discontinuous reception, the duration of the sleep period, etc. For example, inactive discontinuous reception is inactive eDRX, and the inactive eDRX parameters include ran-ExtendedPagingCycle.

[0281] Idle-mode discontinuous reception refers to the discontinuous reception used by the terminal device when entering the idle state, or the discontinuous reception used by the terminal device in the idle state. When the terminal device enters the idle state, it enables this discontinuous reception, monitoring for paging for a period during the discontinuous reception period, and then entering a sleep state for a period of time. Idle-mode discontinuous reception parameters are used to configure it. These parameters may include the period of discontinuous reception, the duration of the sleep period, etc. For example, if discontinuous reception is an inactive eDRX, the eDRX parameters include extended idle mode DRX parameters. These parameters are negotiated and determined by the terminal device and the mobility management network element.

[0282] Optionally, the inactive discontinuous reception parameters are related to the idle discontinuous reception parameters. Specifically, the access network device determines the inactive discontinuous reception parameters based on the idle discontinuous reception parameters sent by the mobility management network element. For example, the period length of the inactive discontinuous reception is less than or equal to the period length of the idle discontinuous reception.

[0283] In this embodiment, the timing of the access network device generating the inactive discontinuous reception parameters is not limited. For example, the access network device may determine the inactive discontinuous reception parameters based on the idle discontinuous reception parameters when triggering the terminal device to enter the inactive state, and send them to the terminal device. Alternatively, the access network device may determine the inactive discontinuous reception parameters upon receiving the idle discontinuous reception parameters and send them to the terminal device before triggering the terminal device to enter the inactive state; this is not limited.

[0284] In this application embodiment, idle-state discontinuous reception can also be called idle-mode discontinuous reception (such as extended idle mode DRX, idle mode eDRX, etc.), and inactive-state discontinuous reception can also be called inactive-mode discontinuous reception (such as eDRX in RRC-INACTIVE, RRC-INACTIVE eDRX, etc.), and there is no limitation on this.

[0285] In some possible scenarios, the second information includes the first information. The first information is used to trigger the access network device not to configure the inactive discontinuous reception parameters to the terminal device, or to trigger the access network device to configure the inactive discontinuous reception parameters to be empty to the terminal device, or to trigger the access network device to configure the terminal device to disable inactive discontinuous reception. In some implementations, the second information is the same as the first information.

[0286] The mobility management network element sending second information to the access network device may include: the mobility management network element sending first information to the access network device. Correspondingly, the access network device receiving the second information from the mobility management network element may include: the access network device receiving the first information from the mobility management network element.

[0287] For example, the first information can be carried in a configuration update message or an N2 request message. For instance, the configuration update message is called a RAN configuration update, and the N2 request message is called an N2 message. That is, the mobility management network element sends a configuration update message or an N2 request message to the access network device, and the configuration update message or N2 request message includes the first information.

[0288] In one possible design, the access network device can also determine that the terminal device has a first type of session based on the first information. At this time, the access network device can sense that the terminal device has a first type of session and further determine whether to configure the inactive discontinuous reception parameters to the terminal device as empty or not to configure the inactive discontinuous reception parameters to the terminal device.

[0289] For the first piece of information, the following two possible designs are given as examples:

[0290] Design 1: The first information can be the first RRC Inactive Assistance Information corresponding to the terminal device. The first RRC Inactive Assistance Information does not include idle discontinuous reception parameters.

[0291] At this time, after receiving the first RRC Inactive assistance information, the access network device can determine that the inactive discontinuous reception parameters sent to the terminal device are empty, or that it does not configure inactive discontinuous reception parameters for the terminal device, based on the fact that the first RRC Inactive assistance information does not include idle-state discontinuous reception parameters. This allows the access network device to instruct the terminal device to disable, delete, or update the stored inactive discontinuous reception parameters. Optionally, if the access network device locally stores idle-state discontinuous reception parameters previously sent by the mobility management network element, then the access network device deletes, disables, or updates the locally stored idle-state discontinuous reception parameters based on the first RRC Inactive assistance information that does not include idle-state discontinuous reception parameters.

[0292] Design 2: The first information may include any of the following types of instruction information:

[0293] (1) The first information includes indication information for instructing the access network equipment to configure the terminal equipment to disable inactive discontinuous reception.

[0294] For example, the indication information used to instruct the access network device to configure the terminal device to disable inactive discontinuous reception can be indicated by 1 bit. When the bit value is 1, it is used to instruct the access network device to configure the terminal device to disable inactive discontinuous reception. When the bit value is 0, it is used to instruct the access network device to configure the terminal device to not disable inactive discontinuous reception. The reverse is also true, and there is no limitation on this.

[0295] For example, after receiving the first information, the access network device can determine whether it has already sent inactive discontinuous reception parameters to the terminal device based on the indication information in the first information (regardless of whether the parameters are empty or not). If it is determined that the terminal device has sent inactive discontinuous reception parameters, that is, the terminal device has stored inactive discontinuous reception parameters locally, then the access network device can send an indication message to the terminal device to instruct the terminal device to disable inactive discontinuous reception, or not send inactive discontinuous reception parameters to the terminal device, or send inactive discontinuous reception parameters to the terminal device that are empty, or instruct the terminal device not to enter the inactive state, etc. Alternatively, the access network device may not be certain whether it has already sent inactive discontinuous reception to the terminal device, and directly send an indication message to the terminal device to instruct the terminal device to disable inactive discontinuous reception, or not send inactive discontinuous reception parameters to the terminal device, or send inactive discontinuous reception parameters to the terminal device that are empty, or instruct the terminal device not to enter the inactive state, etc., based on the first information. Therefore, the terminal device can avoid using inactive discontinuous reception when entering the inactive state.

[0296] (2) The first information includes indication information for instructing the access network device to delete the idle-state discontinuous reception parameters and / or the inactive-state discontinuous reception parameters of the terminal device. Alternatively, the first information includes indication information for instructing the access network device to delete the idle-state discontinuous reception parameters of the terminal device and / or the inactive-state discontinuous reception parameters of the terminal device.

[0297] For example, indication information used to instruct the access network device to delete idle-state discontinuous reception parameters and / or inactive-state discontinuous reception parameters of the terminal device can be indicated by 2 bits. One bit is used to indicate whether the access network device should delete the idle-state discontinuous reception parameters of the terminal device; a bit value of 1 indicates that the access network device should delete the idle-state discontinuous reception parameters of the terminal device, and a bit value of 0 indicates that the access network device should not delete the idle-state discontinuous reception parameters of the terminal device, and vice versa. The other bit is used to indicate whether the access network device should delete the inactive-state discontinuous reception parameters of the terminal device; a bit value of 1 indicates that the access network device should delete the inactive-state discontinuous reception parameters of the terminal device, and a bit value of 0 indicates that the access network device should not delete the inactive-state discontinuous reception parameters of the terminal device, and vice versa.

[0298] If the first information includes an instruction to the access network device to delete the idle state discontinuous reception parameters of the terminal device, then after receiving the first information, the access network device can delete the locally stored idle state discontinuous reception parameters of the terminal device according to the first information. As a result, the access network device will no longer generate the inactive state discontinuous reception parameters of the terminal device, nor will it send inactive state discontinuous reception parameters to the terminal device, or send empty inactive state discontinuous reception parameters to the terminal device, or instruct the terminal device not to enter the inactive state, etc.

[0299] At this point, the access network device can still determine, based on the first information, whether it sent inactive discontinuous reception parameters to the terminal device before receiving the first information. If inactive discontinuous reception parameters were sent to the terminal device, the access network device can also, based on the first information, send an indication message to the terminal device instructing it to disable, delete, or update inactive discontinuous reception, or send an empty inactive discontinuous reception parameter to the terminal device, or instruct the terminal device not to enter the inactive state, etc. If inactive discontinuous reception parameters were not sent to the terminal device, then after deleting the locally stored idle discontinuous reception parameters of the terminal device based on the first information and before the release of the first type of session, the access network device will not configure inactive discontinuous reception parameters for the terminal device, or send an empty inactive discontinuous reception parameter to the terminal device, or instruct the terminal device not to enter the inactive state, etc.

[0300] Optionally, the access network device sends an indication message to the terminal device to instruct it to delete the idle-state discontinuous reception parameters stored locally.

[0301] If the first information includes an instruction to the access network device to delete the inactive discontinuous reception parameters of the terminal device, then the access network device can, based on the first information, send to the terminal device an instruction to disable, delete, or update the inactive discontinuous reception, or send to the terminal device an empty inactive discontinuous reception parameter, or instruct the terminal device not to enter the inactive state, etc. Optionally, the access network device can, based on the first information, delete the locally stored inactive discontinuous reception parameters of the terminal device.

[0302] If the first information includes an instruction to the access network device to delete the idle state discontinuous reception parameters and the inactive state discontinuous reception parameters of the terminal device, then the access network device can delete the locally stored idle state discontinuous reception parameters and inactive state discontinuous reception parameters according to the first information. As a result, the access network device will no longer generate inactive state discontinuous reception parameters of the terminal device, nor will it send inactive state discontinuous reception parameters to the terminal device, or send empty inactive state discontinuous reception parameters to the terminal device, or instruct the terminal device not to enter the inactive state, etc.

[0303] At this time, the access network device can still determine, based on the first information, whether it sent inactive discontinuous reception parameters to the terminal device before receiving the first information. If it sent inactive discontinuous reception parameters to the terminal device, the access network device can also send, based on the first information, an instruction to the terminal device to disable, delete, or update inactive discontinuous reception, or send an empty inactive discontinuous reception parameter to the terminal device, or instruct the terminal device not to enter the inactive state, etc.

[0304] Optionally, the access network device sends an indication message to the terminal device to instruct it to delete the idle-state discontinuous reception parameters stored locally.

[0305] (3) The first information includes indication information used to indicate that the terminal device has a first type of session.

[0306] For example, the indication information used to indicate that the terminal device has a first type of session is indicated by 1 bit. A bit value of 1 indicates that the terminal device has a first type of session, and a bit value of 0 indicates that the terminal device does not have a first type of session, and vice versa. There is no limitation on this.

[0307] After receiving the first information, the access network device can determine that the terminal device currently has a first type of session based on the indication information in the first information that indicates that the terminal device has a first type of session. Then, it can send an empty inactive discontinuous reception to the terminal device, or not configure inactive discontinuous reception parameters to the terminal device, such as instructing the terminal device to disable, delete or update the stored inactive discontinuous reception, or instructing the terminal device not to enter the inactive state.

[0308] (4) The first information includes idle state discontinuous reception with empty parameters.

[0309] After receiving the first information, the access network device can update the locally stored idle discontinuous reception parameters to be empty or replace the locally stored idle discontinuous reception parameters based on the empty idle discontinuous reception parameters in the first information. This allows it to determine whether to send empty inactive discontinuous reception parameters to the terminal device or not to configure inactive discontinuous reception parameters to the terminal device. For example, it can instruct the terminal device to disable, delete, or update the stored inactive discontinuous reception, or instruct the terminal device not to enter the inactive state.

[0310] (5) The first information includes indication information for instructing the access network equipment to configure the terminal equipment to update the inactive discontinuous reception parameters to be empty.

[0311] After receiving the first information, the access network device can send an indication message to the terminal device to instruct the terminal device to update the inactive discontinuous reception parameters to be empty, or send empty inactive discontinuous reception parameters to the terminal device, or instruct the terminal device not to enter the inactive state, etc., according to the indication information in the first information.

[0312] For Design 2, optionally, the first information is also RRC Inactive auxiliary information.

[0313] In some implementations, S602 can be replaced by: the mobility management element sending first information to the access network device. Correspondingly, the access network device receives the first information from the mobility management element.

[0314] Therefore, after receiving the second information, the access network device can execute S603A, S603B, or S603C according to the second information.

[0315] S603A: The access network equipment configures the inactive discontinuous reception parameters to be empty according to the second information.

[0316] For example, configuring the inactive discontinuous reception parameters to be empty for the terminal device can include: the access network device generating empty inactive discontinuous reception parameters for the terminal device and sending the empty inactive discontinuous reception parameters to the terminal device. Therefore, after receiving the empty inactive discontinuous reception parameters, the terminal device updates its locally stored inactive discontinuous reception parameters to be empty, thus preventing the terminal device from entering a sleep state when the access network device triggers it to enter an inactive state.

[0317] In one possible design, empty inactive discontinuous reception parameters are carried in a first message, which is used to trigger the terminal device to enter the inactive state. For example, the first message is an RRC Release message. That is, the access network device sends the first message to the terminal device, and the terminal device receives the first message from the access network device. The first message, which triggers the terminal device to enter the inactive state, carries inactive discontinuous reception parameters, and these parameters are empty.

[0318] The specific implementation of how the access network device determines to configure the inactive discontinuous reception parameters to be empty to the terminal device based on the second information can be found in the relevant description in S602 above, and will not be repeated here.

[0319] S603B: Based on the second information, the access network equipment does not configure inactive discontinuous reception parameters for the terminal equipment.

[0320] For example, the access network device may not configure inactive discontinuous reception parameters to the terminal device, which may include any of the following:

[0321] The access network device sends an indication message to the terminal device to instruct the terminal device to disable inactive, discontinuous reception; or,

[0322] The access network device sends an instruction message to the terminal device, instructing the terminal device to delete inactive, discontinuous reception parameters; or,

[0323] The access network device sends an indication message to the terminal device instructing the terminal device to update the inactive discontinuous reception parameters to be empty. Optionally, the indication message instructing the terminal device to update the inactive discontinuous reception parameters to be empty includes empty inactive discontinuous reception parameters; or,

[0324] The messages sent from the access network device to the terminal device do not include inactive, discontinuous reception parameters.

[0325] In one possible design, the aforementioned indication information can be carried in an RRC message, such as an RRC Release message.

[0326] The specific implementation of how the access network device determines not to configure inactive discontinuous reception parameters to the terminal device based on the second information can be found in the relevant description in S602 above, and will not be repeated here.

[0327] S603C: When the conditions for the terminal device to enter the inactive state are met, the access network device does not instruct the terminal device to enter the inactive state based on the second information.

[0328] For example, the conditions for a terminal device to enter an inactive state may include that there is no data transmission on the terminal device within a preset time period.

[0329] The access network device does not instruct the terminal device to enter the inactive state based on the second information, which may include: the access network device does not send a message to the terminal device to trigger the terminal device to enter the inactive state, such as the first message mentioned above, based on the second information.

[0330] In other words, after receiving the second information, the access network device can directly instruct the terminal device not to enter the inactive state, and not to configure the terminal device with empty inactive discontinuous reception parameters, or instruct the terminal device to disable, delete, or update the inactive discontinuous reception parameters. This way, regardless of whether the terminal device stores the inactive discontinuous reception parameters, it will not be triggered to use them. Not instructing the terminal device to enter the inactive state can be understood as disabling the inactive discontinuous reception parameters stored locally on the terminal device.

[0331] Furthermore, when the first type of session of the terminal device is released, the mobility management network element can also send non-empty idle-state discontinuous reception parameters to the access network device, so that the access network device can configure non-empty inactive-state discontinuous reception parameters for the terminal device to save power consumption of the terminal device. For example, the mobility management network element can send the second RRC Inactive assistance information corresponding to the terminal device to the access network device, and correspondingly, the access network device receives the second RRC Inactive assistance information corresponding to the terminal device from the mobility management network element. The second RRC Inactive assistance information includes non-empty idle-state discontinuous reception parameters. This triggers the access network device to send non-empty inactive-state discontinuous reception parameters (such as ran-ExtendedPagingCycle) to the terminal device in a message used to trigger the terminal device to enter the inactive state (such as an RRC Release message), configuring inactive-state discontinuous reception for the terminal device.

[0332] In the communication method shown in Figure 6, when the mobility management network element determines that a first-type session exists, it can send second information to the access network device to trigger the access network device to configure empty inactive discontinuous reception parameters for the terminal device, or not configure inactive discontinuous reception parameters for the terminal device, such as instructing the terminal device to disable, delete, or update the inactive discontinuous reception parameters. This ensures that when the first-type session exists, the terminal device does not use inactive discontinuous reception when entering the inactive state, thus enabling the terminal device to promptly recover from the inactive state to the connected state to receive or send data related to the first-type session. Alternatively, the access network device may be triggered not to instruct the terminal device to enter the inactive state, so that regardless of whether the terminal device stores inactive discontinuous reception parameters, it will not be triggered to use them and will remain in the connected state.

[0333] In the embodiments of this application, the descriptions "idle / inactive discontinuous reception", "idle / inactive discontinuous reception parameters", and "idle / inactive discontinuous reception period" can be used interchangeably. For example, configuring inactive discontinuous reception can refer to configuring inactive discontinuous reception parameters or configuring inactive discontinuous reception period, and there is no limitation on this.

[0334] The communication method shown in Figure 6 will be illustrated below with reference to the 5G network architecture shown in Figure 1 above.

[0335] Taking the mobility management network element as AMF, the access network equipment as (R)AN, the terminal equipment as UE, discontinuous reception as eDRX, and the first type of session as an emergency PDU session as an example, as shown in Figure 7, this communication method includes:

[0336] S701, the UE sends a registration request to the AMF.

[0337] Accordingly, the AMF receives registration requests from the UE.

[0338] The registration request includes the eDRX parameter requested or requested by the UE.

[0339] S702, AMF sends a Registration Accept message to UE.

[0340] Accordingly, the UE receives a registration acceptance message from the AMF.

[0341] The registration acceptance message includes the accepted eDRX parameter.

[0342] That is, in S701 and S702, the UE and AMF negotiate to determine the eDRX parameters. These eDRX parameters are used by the UE to enter the idle state, namely the idle state eDRX parameters (corresponding to the aforementioned idle state discontinuous reception parameters), and are stored locally by each of them.

[0343] S703, the UE sends a PDU Session Establishment Request to the AMF.

[0344] Accordingly, the AMF receives a PDU session establishment request from the UE.

[0345] The PDU session establishment request is used to request the establishment of an emergency PDU session. This PDU session establishment request includes information such as S-NSSAI and emergency DNN corresponding to the emergency PDU session.

[0346] The PDU session establishment request corresponds to the session establishment request mentioned above.

[0347] S704 and AMF determine that the UE has an emergency PDU session based on the PDU session establishment request.

[0348] S705 and AMF send an N1 message to the UE.

[0349] Correspondingly, the UE receives the N1 message from the AMF.

[0350] The N1 message includes the PDU session establishment acceptance message.

[0351] An AN Release Procedure is performed between S706, UE, and AMF.

[0352] After passing through S706, the UE changes from the RRC connected state to the RRC idle state. The specific implementation of the AN release procedure can be found in the relevant existing technologies, which will not be elaborated here.

[0353] S707, the UE sends a service request to the (R)AN.

[0354] Accordingly, (R)AN receives service requests from the UE.

[0355] The service request includes a list of PDU session(s) to be activated, which includes emergency PDU sessions.

[0356] In other words, when a UE initiates a service request to restore from the RRC idle state to the connected state, it can determine whether there is an emergency PDU session. If there is an emergency PDU session, it requests to activate the emergency PDU session.

[0357] S708 and (R)AN send an N2 message to the AMF.

[0358] Correspondingly, the AMF receives the N2 message from (R)AN.

[0359] The N2 message includes the service request mentioned in S707 above.

[0360] After receiving a service request, AMF can determine whether an existing emergency PDU session is active based on the service request.

[0361] S709, AMF sends an N2 request to (R)AN.

[0362] Correspondingly, (R)AN receives N2 requests from AMF.

[0363] The N2 request includes RRC Inactive Assistance Information (corresponding to the first information mentioned above). The RRC Inactive Assistance Information includes empty idle state eDRX parameters, or indication information used to instruct the (R)AN to configure the UE to disable inactive state eDRX parameters, or indication information used to instruct the (R)AN to delete the UE's inactive state eDRX parameters.

[0364] When AMF determines that the UE has an active emergency PDU session, it configures the UE's idle-state eDRX parameter to be empty in the (R)AN, or configures an indication message to instruct the (R)AN to disable the UE's inactive-state eDRX parameter, or configures an indication message to instruct the (R)AN to delete the UE's inactive-state eDRX parameter, and instructs the (R)AN to do so through the RRC inactive auxiliary information.

[0365] Accordingly, after receiving the idle-state eDRX parameter, the (R)AN can determine that the inactive-state eDRX parameter is empty based on the idle-state eDRX parameter when triggering the UE to enter the RRC inactive state, and send it to the UE; or, before triggering the UE to enter the RRC inactive state, it can determine that the inactive-state eDRX parameter is empty based on the idle-state eDRX parameter and send it to the UE. The following example demonstrates how the inactive-state eDRX parameter is determined based on the idle-state eDRX parameter and sent to the UE when triggering the UE to enter the RRC inactive state.

[0366] S710 and (R)AN send RRC connection reconfiguration to the UE.

[0367] Accordingly, the UE receives an RRC connection reconfiguration from (R)AN.

[0368] The UE returns to the connected state from the idle state.

[0369] S711, (R)AN sends an RRC Release message to the UE.

[0370] Accordingly, the UE receives an RRC release message from (R)AN.

[0371] The RRC release message is used to instruct the UE to release from the RRC connected state to the RRC inactive state, corresponding to the first message mentioned above.

[0372] The RRC release message may include an empty inactive eDRX parameter, or it may not include an inactive eDRX parameter. In other words, after receiving the RRC inactive assistance information, the (R)AN can determine whether to generate an empty inactive eDRX parameter for the UE based on whether the idle eDRX parameter is empty, or whether the (R)AN is instructed to configure the UE to disable the inactive eDRX parameter, or whether the (R)AN is instructed to delete the UE's inactive eDRX parameter. This empty inactive eDRX parameter will then be included in the RRC release message and sent to the UE. Alternatively, the inactive eDRX parameter may not be included in the RRC release message.

[0373] In one possible design, the RRC inactivity auxiliary information includes a non-empty idle-state eDRX parameter, and indication information for instructing the (R)AN to configure the UE to disable the inactive-state eDRX parameter, or for instructing the (R)AN to delete the UE's inactive-state eDRX parameter. In this case, the RRC release message includes either a non-empty inactive-state eDRX parameter and indication information for instructing the UE to disable the inactive-state eDRX parameter, or a non-empty inactive-state eDRX parameter and indication information for instructing the UE to delete the inactive-state eDRX parameter. In other words, after receiving the RRC inactive assistance information, the (R)AN can still configure non-empty inactive eDRX parameters for the UE, and determine the indication information for instructing the UE to disable the inactive eDRX parameters or the indication information for instructing the (R)AN to delete the inactive eDRX parameters, based on the indication information used to instruct the (R)AN to configure the UE not to use inactive eDRX when entering the RRC inactive state.

[0374] Therefore, after receiving the RRC release message, the UE will not use the inactive eDRX when entering the RRC inactive state. As a result, when there is data transmission related to an emergency PDU session, the UE can promptly recover from the RRC inactive state to the RRC connected state to receive data.

[0375] It should be understood that Figure 7 provides an example of some processes that may be involved in this solution. Other interactive steps may also be included in the above registration process, session establishment process, and service request process. There may also be other interactive steps between the registration process, session establishment process, and service request process. This is not limited.

[0376] As exemplarily shown in Figure 8, the communication method includes:

[0377] S801, the UE sends a PDU session establishment request to the AMF.

[0378] Accordingly, the AMF receives a PDU session establishment request from the UE.

[0379] The PDU session establishment request is used to request the establishment of an emergency PDU session. This PDU session establishment request includes information such as S-NSSAI and emergency DNN corresponding to the emergency PDU session.

[0380] The PDU session establishment request corresponds to the session establishment request mentioned above.

[0381] S802 and AMF determine that the UE has an emergency PDU session based on the PDU session establishment request.

[0382] S803, AMF sends an N2 Request or RAN configuration update message to (R)AN.

[0383] Accordingly, (R)AN receives N2 requests or RAN configuration update messages from AMF.

[0384] The N2 request or RAN configuration update message includes RRC Inactive Assistance Information (corresponding to the first information mentioned above), which includes empty idle-state eDRX parameters.

[0385] If AMF determines that the UE has an active emergency PDU session, it configures the UE's idle state eDRX parameter to be empty in (R)AN.

[0386] S804, (R)AN sends an RRC Release message to the UE.

[0387] Accordingly, the UE receives an RRC release message from (R)AN.

[0388] The RRC release message is used to instruct the UE to release from the RRC connected state to the RRC inactive state, corresponding to the first message mentioned above.

[0389] The RRC release message may include an empty inactive eDRX parameter, or it may not include an inactive eDRX parameter. In other words, after receiving the RRC inactive auxiliary information, the (R)AN can determine that the inactive eDRX parameter of the generated UE is empty based on the empty idle eDRX parameter, and send it to the UE in the RRC release message, or it may not carry the inactive eDRX parameter in the RRC release message.

[0390] Therefore, after receiving the RRC release message, the UE will not use the inactive eDRX when entering the RRC inactive state. As a result, when there is data transmission related to an emergency PDU session, the UE can promptly recover from the RRC inactive state to the RRC connected state to receive data.

[0391] In addition, this application embodiment also provides a communication method, which differs from the communication method shown in FIG6 in that the first information is used to configure the period length of the inactive discontinuous reception of the terminal device. As shown in FIG9, the communication method includes:

[0392] S901, the mobility management network element determines that the terminal device has a first type of session.

[0393] The specific implementation process of S901 can be found in the relevant description in S601 above, and will not be repeated here.

[0394] S902, the mobility management network element sends the first information to the access network equipment.

[0395] Correspondingly, the access network device receives the first information from the mobility management network element.

[0396] The first information is used to configure the period length of the inactive discontinuous reception of the terminal device. The first information includes the period length of the first idle discontinuous reception, which is less than a first threshold.

[0397] Optionally, the period length of discontinuous reception being less than the first threshold can be either the sum of the sleep duration and paging duration in a period being less than the first threshold, or the sleep duration in a period being less than the first threshold; there is no limitation on this.

[0398] For detailed descriptions of inactive discontinuous reception and idle discontinuous reception, please refer to the relevant descriptions of inactive discontinuous reception and idle discontinuous reception in S602 above, which will not be repeated here.

[0399] The first threshold ensures that when a terminal device enters an inactive state during a first-type session, the discontinuous reception in the inactive state prevents the terminal device from remaining in a sleep state for an extended period. This allows the terminal device to quickly resume connection from the sleep state and receive or send data related to the first-type session when necessary. The first threshold can be predefined by the protocol or negotiated between the terminal device and the mobility management network element; there are no restrictions on its specific nature.

[0400] In one possible design, the period length of the first idle state discontinuous reception can be negotiated between the mobility management network element and the terminal device during registration.

[0401] For example, the first information may be the RRC Inactive auxiliary information corresponding to the terminal device.

[0402] For example, the first information can be carried in a configuration update message or an N2 request message. For instance, the configuration update message is called a RAN configuration update, and the N2 request message is called an N2 message. That is, the mobility management network element sends a configuration update message or an N2 request message to the access network device, and the configuration update message or N2 request message includes the first information.

[0403] It should be understood that the first information may also include other parameters of the first idle discontinuous reception, such as the sleep period duration of the first idle discontinuous reception.

[0404] S903. The access network device sends inactive discontinuous reception parameters to the terminal device based on the first information.

[0405] Correspondingly, the terminal device receives inactive, discontinuous reception parameters from the access network device.

[0406] After receiving the first information, the access network device can generate the inactive discontinuous reception parameters of the terminal device based on the period length of the first idle discontinuous reception in the first information. The inactive discontinuous reception parameters include the period length of the inactive discontinuous reception, which is less than or equal to the period length of the first idle discontinuous reception.

[0407] Therefore, the access network device can send inactive discontinuous reception parameters to the terminal device so that the terminal device can use inactive discontinuous reception when it enters the inactive state.

[0408] In one possible design, the inactive state discontinuous reception parameters are carried in a first message, which is used to trigger the terminal device to enter the inactive state. For example, the first message is an RRC Release message. That is, the access network device sends the first message to the terminal device, and the terminal device receives the first message from the access network device. The first message, which triggers the terminal device to enter the inactive state, carries inactive state discontinuous reception parameters, and the period length of the inactive state discontinuous reception is less than or equal to the period length of the first idle state discontinuous reception.

[0409] It should be understood that inactive, discontinuous reception parameters can also be carried in other RRC messages and are not restricted in this regard.

[0410] In the communication method shown in Figure 9, when the mobility management network element determines that there is a first type of session, it can send first information to the access network device to configure the period length of the inactive discontinuous reception of the terminal device to be less than or equal to a first threshold. This triggers the access network device to configure the period length of the inactive discontinuous reception of the terminal device to be less than or equal to the first threshold. This ensures that the inactive discontinuous reception used by the terminal device when entering the inactive state will not keep the terminal device in a sleep state for a long time. As a result, when there is data transmission related to the first type of session, it can ensure that the terminal device can quickly resume the connected state from the sleep state and receive or send data related to the first type of session.

[0411] The communication method shown in Figures 6-9 above involves a mobility management network element determining a first type of session to trigger an access network device to configure the terminal device to not remain in a sleep state for an extended period when entering an inactive state. In addition, embodiments of this application also provide a communication method where the terminal device determines the existence of a first type of session and triggers the access network device to configure the parameters for inactive discontinuous reception to be empty, or to disable inactive discontinuous reception when the access network device triggers it to enter an inactive state.

[0412] As shown in Figure 10, the communication method includes:

[0413] S1001, The access network device sends the first inactive state discontinuous reception parameters to the terminal device.

[0414] Accordingly, the terminal device receives the first inactive discontinuous reception parameters from the access network device.

[0415] Among them, the first non-active state discontinuous reception parameter is not empty.

[0416] The access network device obtains the first idle state discontinuous reception parameters from the mobility management network element, generates the first inactive state discontinuous reception parameters based on the first idle state discontinuous reception parameters, and the parameters are not empty, and then sends them to the terminal device.

[0417] For specific descriptions of idle discontinuous reception and inactive discontinuous reception, please refer to the relevant descriptions of inactive discontinuous reception and idle discontinuous reception in S602 above. For specific implementations of the mobility management network element sending the first idle discontinuous reception parameter to the access network device, please refer to the relevant existing implementations, which will not be elaborated here.

[0418] In one possible design, the first inactive state discontinuous reception parameters are carried in a first message, which is used to trigger the terminal device to enter the inactive state. For example, the first message is an RRC Release message. That is, the access network device sends the first message to the terminal device, and correspondingly, the terminal device receives the first message from the access network device, wherein the first message includes non-empty first inactive state discontinuous reception parameters.

[0419] It should be understood that the first inactive state discontinuous reception parameters can also be carried in other RRC messages and are not limited thereto.

[0420] S1002. When the terminal device has a first type session and the first type session is used to serve the terminal device's emergency services, the terminal device sends third information to the access network device.

[0421] Correspondingly, the access network equipment receives third-party information from the terminal equipment.

[0422] The third piece of information is used to trigger the access network device to configure the inactive, discontinuous reception parameters of the terminal device to be empty.

[0423] After receiving the first inactive discontinuous reception parameter, or after receiving the first inactive discontinuous reception parameter and triggering entry into the inactive state, the terminal device determines whether there is a first type of session. If it is determined that there is a first type of session, the terminal device sends third information to the access network device; if it is determined that there is no first type of session, the terminal device uses the first inactive discontinuous reception when entering the inactive state.

[0424] In one possible design, the third information may include one of the following instructions:

[0425] (1) The third information includes indication information for indicating that the first inactive state discontinuous reception parameters are refused to be enabled.

[0426] After determining that there is a first type of session, the terminal device may refuse to enable or use the first inactive state discontinuous reception parameters when entering the inactive state, thereby sending third information to the access network device carrying indication information for refusing to enable the first inactive state discontinuous reception parameters, so as to trigger the access network device to reconfigure the terminal device with empty inactive state discontinuous reception parameters, or not configure inactive state discontinuous reception parameters for the terminal device, or instruct the terminal device not to enter the inactive state, etc.

[0427] (2) The third information includes indication information used to indicate that the terminal device has a first type of session.

[0428] After determining that a first type of session exists, the terminal device can also send an indication message to the access network device to indicate that the terminal device has a first type of session, so that the access network device can determine that a first type of session exists, thereby reconfiguring the terminal device with empty inactive discontinuous reception parameters, or not configuring inactive discontinuous reception parameters for the terminal device, or instructing the terminal device not to enter the inactive state, etc.

[0429] (3) The third information includes indication information used to instruct the access network device to configure the terminal device to have empty inactive discontinuous reception parameters.

[0430] After determining that there is a first type of session, the terminal device may also send an indication message to the access network device to instruct the access network device to configure the inactive discontinuous reception parameters of the terminal device to be empty, so that the access network device may reconfigure the inactive discontinuous reception parameters of the terminal device to be empty, or not configure the inactive discontinuous reception parameters of the terminal device, or instruct the terminal device not to enter the inactive state, etc.

[0431] (4) When the discontinuous reception parameters of the first inactive state are carried in the first message, the third information includes indication information for indicating rejection of entering the inactive state, such as failure information. At this time, the access network device sends the first message to the terminal device, and the terminal device receives the first message from the access network device. The first message is used to trigger the terminal device to enter the inactive state, and the first message carries the discontinuous reception parameters of the first inactive state.

[0432] In other words, when a terminal device is triggered to enter an inactive state by an access network device, if it determines that there is a first type of session and the configured inactive discontinuous reception parameters are not empty, the terminal device can refuse to enter the inactive state, maintain the connected state, and send an indication message to the access network device to indicate that it refuses to enter the inactive state. This allows the access network device to reconfigure the terminal device with empty inactive discontinuous reception parameters, or not to configure inactive discontinuous reception parameters for the terminal device, or to instruct the terminal device not to enter the inactive state.

[0433] In one possible design, the third information can be carried in an RRC message, such as an RRC Resume message.

[0434] After sending the third information, the terminal device can directly disable the inactive discontinuous reception. When the access network device triggers it to enter the inactive state, it will not use the inactive discontinuous reception. Alternatively, it can disable the inactive discontinuous reception according to the inactive discontinuous reception configuration of the access network device, such as by executing S1003A, S1003B, or S1003C as described below.

[0435] S1003A: The access network equipment configures the inactive discontinuous reception parameters to be empty according to the third information.

[0436] Similar to S603A described above, the access network device sends a second inactive state discontinuous reception parameter to the terminal device based on the third information. Correspondingly, the terminal device receives the second inactive state discontinuous reception parameter from the access network device. The second inactive state discontinuous reception parameter is empty.

[0437] After receiving the third information, the access network device can configure the terminal device with empty second inactive discontinuous reception parameters based on the third information.

[0438] Therefore, after receiving the second inactive state discontinuous reception parameters, the terminal device can disable inactive state discontinuous reception based on these parameters. In other words, an empty second inactive state discontinuous reception parameter is equivalent to the absence of second inactive state discontinuous reception, or disabling the first inactive state discontinuous reception and using the second inactive state discontinuous reception. The terminal device can update the first inactive state discontinuous reception parameters to the second inactive state discontinuous reception parameters, and use the second inactive state discontinuous reception when the terminal device enters the inactive state.

[0439] S1003B: Based on third-party information, the access network equipment does not configure inactive, discontinuous reception parameters for the terminal equipment.

[0440] Similar to S603B above, for example, the access network device may not configure inactive discontinuous reception parameters to the terminal device, which may include any of the following:

[0441] The access network device sends an indication message to the terminal device, instructing the terminal device to disable the first inactive state discontinuous reception; or,

[0442] The access network device sends an instruction to the terminal device, instructing the terminal device to delete the first inactive state discontinuous reception parameters; or,

[0443] The access network device sends an indication message to the terminal device instructing the terminal device to update the inactive discontinuous reception parameters to be empty. Optionally, the indication message instructing the terminal device to update the inactive discontinuous reception parameters to be empty includes an empty second inactive discontinuous reception parameter.

[0444] S1003C. When the conditions for the terminal device to enter the inactive state are met, the access network device does not instruct the terminal device to enter the inactive state based on the third information.

[0445] Similar to S603C above, for example, the conditions for a terminal device to enter an inactive state may include that the terminal device does not transmit data within a preset time period. The access network device not instructing the terminal device to enter an inactive state based on the third information may include: the access network device not sending a message to the terminal device to trigger the terminal device to enter an inactive state, such as the first message mentioned above, based on the third information. For a detailed description, please refer to the relevant description in S603C above, which will not be repeated here.

[0446] In one possible design, the access network device can also determine the first type of session with the terminal device based on third information. In this case, the access network device can perceive the first type of session and save the session context.

[0447] In one possible design, the third information is carried within the second information; that is, the second information includes the third information. The aforementioned access network device receiving the third information can be replaced by the access network device receiving the second information, and the access network device relying on the third information can be replaced by the access network device relying on the second information.

[0448] In the communication method shown in Figure 10, the terminal device can determine whether there is a first type session for an urgent service of the terminal device based on the non-empty first inactive discontinuous reception parameters configured by the access network device. If there is a first type session, the terminal device sends third information to the access network device to trigger the access network device to configure the inactive discontinuous reception parameters of the terminal device to be empty. This allows the terminal device to not use inactive discontinuous reception when entering the inactive state, thereby enabling the terminal device to recover from the inactive state to the connected state in a timely manner to receive or send data related to the first type session.

[0449] The communication method shown in Figure 10 will be illustrated below with reference to the 5G network architecture shown in Figure 1.

[0450] Taking the mobility management network element as AMF, the access network equipment as gNB, the terminal equipment as UE, discontinuous reception as eDRX, and the first type of session as emergency PDU session as an example, as shown in Figure 11, this communication method includes:

[0451] S1101, the UE sends a registration request to the AMF.

[0452] Accordingly, the AMF receives registration requests from the UE.

[0453] S1102, AMF sends a Registration Accept message to UE.

[0454] Accordingly, the UE receives a registration acceptance message from the AMF.

[0455] S1101 and S1102 can be found in the relevant descriptions in S701 and S702 above.

[0456] S1103, UE and AMF conduct AN release procedure.

[0457] S1104. The UE sends a service request to the (R)AN.

[0458] Accordingly, (R)AN receives service requests from the UE.

[0459] The service request includes a list of PDU sessions to be activated, which does not include emergency PDU sessions.

[0460] S1105, (R)AN sends an N2 message to AMF.

[0461] Correspondingly, the AMF receives the N2 message from (R)AN.

[0462] The N2 message includes the service request from S1104 above.

[0463] S1106, AMF sends an N2 request to (R)AN.

[0464] Correspondingly, (R)AN receives N2 requests from AMF.

[0465] The N2 request includes RRC Inactive Assistance Information (corresponding to the first information mentioned above), which includes idle state eDRX parameters determined through negotiation between S1101 and S1102.

[0466] S1107, (R)AN sends an RRC connection reconfiguration to the UE.

[0467] Accordingly, the UE receives an RRC connection reconfiguration from (R)AN.

[0468] The UE returns to the connected state from the idle state.

[0469] S1108, (R)AN sends the first RRC Release message to the UE.

[0470] Accordingly, the UE receives the first RRC release message from (R)AN.

[0471] The first RRC release message includes an inactive eDRX parameter, which is determined by (R)AN based on the idle eDRX parameter configured by AMF, and the inactive eDRX parameter is not empty.

[0472] S1109, The UE determines that there is an emergency PDU session based on the first RRC release message.

[0473] After receiving the first RRC release message, the UE can determine whether there is an emergency PDU session. If so, the UE can refuse to enable the configured inactive eDRX parameters or refuse to enter the inactive state and inform the (R)AN.

[0474] S1110, The UE sends an indication message to the (R)AN to refuse to enable the inactive eDRX parameter.

[0475] Correspondingly, (R)AN receives indication information from the UE for refusing to enable the inactive eDRX parameter.

[0476] After receiving the indication message for refusing to enable the inactive eDRX parameters, the (R)AN may no longer instruct the UE to enter the inactive state. In this case, the UE can directly disable the inactive eDRX. Alternatively, the (R)AN may instruct the UE to enter the inactive state again and configure the inactive eDRX parameters with empty parameters for the UE, as shown in S1111 below. This is not limited.

[0477] S1111, (R)AN sends a second RRC Release message to the UE.

[0478] Accordingly, the UE receives a second RRC release message from (R)AN.

[0479] The second RRC release message includes an empty, inactive eDRX parameter.

[0480] Therefore, after receiving the RRC release message, the UE will not use the inactive eDRX when entering the RRC inactive state. As a result, when there is emergency PDU session related data transmission, the UE can promptly recover from the RRC inactive state to the RRC connected state to receive data.

[0481] It should be understood that Figure 11 provides an example of some processes that may be involved in this solution. Other interactive steps may also be included in the registration process, service request process, etc., and there may be other interactive steps between the registration process and the service request process. This is not limited.

[0482] In some possible communication methods, the third information in the communication method shown in Figure 10 can be used to trigger the access network device to configure the period length of the inactive discontinuous reception parameters to the terminal device. The third information includes the inactive discontinuous reception parameters having a period length less than a first threshold. Therefore, after receiving the third information, the access network device can configure inactive discontinuous reception parameters with a short period length for the terminal device. This ensures that the inactive discontinuous reception used by the terminal device when entering the inactive state will not keep the terminal device in a sleep state for an extended period. Consequently, when there is data transmission related to the first type of session, it can guarantee that the terminal device can quickly resume connection from the sleep state and receive or send data related to the first type of session.

[0483] In addition to the communication method shown in Figure 10, this application embodiment also provides a communication method in the case that the terminal device locally stores non-empty inactive discontinuous reception parameters configured by the access network device. In this communication method, the terminal device receives a first message from the access network device. The first message is used to trigger the terminal device to enter an inactive state. When the terminal device has a first type of session, and the first type of session is used to serve the terminal device's emergency services, the terminal device disables inactive discontinuous reception. That is, if the terminal device determines that there is a first type of session, then when the terminal device enters the inactive state, the terminal device does not use or enable the non-empty inactive discontinuous reception parameters configured by the access network device that are stored locally, i.e., it disables inactive discontinuous reception. In this way, the terminal device can also avoid entering a sleep state after entering the inactive state, and when there is data transmission related to the first type of session, it can promptly recover from the inactive state to the connected state to receive or send data related to the first type of session.

[0484] It is understood that, in the above embodiments, the methods and / or steps implemented by the mobility management network element can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the mobility management network element; the methods and / or steps implemented by the access network device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the access network device; and the methods and / or steps implemented by the terminal device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the terminal device.

[0485] The foregoing mainly describes the solutions provided in this application. Accordingly, this application also provides a communication device for implementing various methods in the above method embodiments. This communication device can be a mobility management network element in the above method embodiments, or a device containing a mobility management network element, or a component that can be used in a mobility management network element, such as a chip or chip system. Alternatively, the communication device can be an access network device in the above method embodiments, or a device containing an access network device, or a component that can be used in an access network device, such as a chip or chip system. Alternatively, the communication device can be a terminal device in the above method embodiments, or a device containing a terminal device, or a component that can be used in a terminal device, such as a chip or chip system.

[0486] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware 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.

[0487] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0488] Taking the mobility management network element, access network device, or terminal device in the above method embodiments as an example, Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in Figure 12, the communication device 1200 includes a processing module 1201 and a transceiver module 1202. The processing module 1201 is used to execute the processing functions of the mobility management network element, access network device, or terminal device in the above method embodiments. The transceiver module 1202 is used to execute the transceiver functions of the mobility management network element, access network device, or terminal device in the above method embodiments. All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0489] In one possible design, according to this embodiment, the transceiver module 1202 may include a receiving module and a transmitting module (not shown in FIG12). The transmitting module and the receiving module are respectively used to implement the transmitting and receiving functions of the communication device 1200.

[0490] In one possible design, the communication device 1200 may further include a storage module (not shown in FIG. 12) that stores programs or instructions. When the processing module 1201 executes the program or instructions, the communication device 1200 can perform the functions of the mobility management network element, access network device, or terminal device in any of the methods shown in FIG. 6-FIG. 11.

[0491] In some embodiments, the processing module 1201 involved in the communication device 1200 may be implemented by a processor or processor-related circuit components, and may be a processor or processing unit; the transceiver module 1202 may be implemented by a transceiver or transceiver-related circuit components, and may be a transceiver or transceiver unit.

[0492] For example, FIG13 is a schematic diagram of another communication device provided in an embodiment of this application. This communication device can be a mobility management network element, access network device, or terminal device as described in the above method embodiments, or it can be a chip (system) or other component or assembly that can be disposed in a mobility management network element, access network device, or terminal device. As shown in FIG13, the communication device 1300 may include a processor 1301, a bus 1302, a communication interface 1303, and a memory 1304. The processor 1301, the memory 1304, and the communication interface 1303 communicate via the bus 1302. It should be understood that this application does not limit the number of processors and memories in the communication device 1300.

[0493] Bus 1302 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one line is used in Figure 13, but this does not imply that there is only one bus or one type of bus. Bus 1302 can include pathways for transmitting information between various components of communication device 1300 (e.g., memory 1304, processor 1301, communication interface 1303).

[0494] Processor 1301 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0495] The memory 1304 may include volatile memory, such as random access memory (RAM). The processor 1301 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0496] The communication interface 1303 uses transceiver modules such as, but not limited to, network interface cards and transceivers to enable communication between the communication device 1300 and other devices or communication networks.

[0497] The memory 1304 stores executable program code, which the processor 1301 executes to implement the functions of the mobility management network element, access network device, or terminal device in the aforementioned method embodiments. That is, the memory 1304 stores instructions for executing the aforementioned communication methods.

[0498] In another aspect, embodiments of this application also provide a computer program product containing instructions, including computer program code, which, when run on a communication device, enables the communication device to execute the methods described in the above embodiments.

[0499] Furthermore, embodiments of this application also provide a computer-readable storage medium. This computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the methods described in the above embodiments.

[0500] In another aspect, embodiments of this application also provide a communication system, which includes the aforementioned mobility management network element and access network equipment.

[0501] In another aspect, embodiments of this application also provide a communication system, which includes the aforementioned terminal equipment and access network equipment.

[0502] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video disks, DVDs), or semiconductor media (e.g., SSDs), etc.

[0503] 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.

[0504] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0505] 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.

[0506] 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. Furthermore, the functional units in the various embodiments of this application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0507] 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, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0508] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0509] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, Applied to mobility management network elements, the method includes: It is determined that the terminal device has a first type of session, which is used for the terminal device's emergency services. Send a first message to the access network device, the first message being used to trigger the access network device not to configure inactive discontinuous reception parameters to the terminal device, or to trigger the access network device to configure the inactive discontinuous reception parameters to be empty to the terminal device.

2. The method according to claim 1, characterized in that, The first information is the first RRC Inactive auxiliary information corresponding to the terminal device, and the first RRC Inactive auxiliary information does not include idle state discontinuous reception parameters.

3. The method according to claim 2, characterized in that, The method further includes: When the first type of session of the terminal device is released, the terminal device sends the second RRC Inactive assistance information corresponding to the terminal device to the access network device. The second RRC Inactive assistance information includes the idle state discontinuous reception parameters.

4. The method according to claim 1, characterized in that, The first information includes: Instructions for the access network device to configure the terminal device to disable inactive, discontinuous reception; or... Instruction information used to instruct the access network device to delete the idle-state discontinuous reception parameters and / or the inactive-state discontinuous reception parameters of the terminal device; or, Indication information used to indicate that the terminal device has the first type of session.

5. The method according to any one of claims 1-4, characterized in that, Sending the first information to the access network device includes: When the first type of session is inactive, the first information is sent to the access network device.

6. The method according to claim 5, characterized in that, The method further includes: Receive a service request from the terminal device, wherein the session to be activated in the service request does not include the first type of session; Based on the service request, it is determined that the first type of session of the terminal device is in an inactive state.

7. The method according to any one of claims 1-4, characterized in that, Sending the first information to the access network device includes: When the first type of session is active, the first information is sent to the access network device.

8. The method according to claim 7, characterized in that, The method further includes: Receive a service request from the terminal device, wherein the service request requests to activate a session including the first type of session; Based on the service request, it is determined that the first type of session of the terminal device is in an active state.

9. The method according to any one of claims 1-8, characterized in that, The determination that the terminal device has a first type of session includes: Receive a session establishment request message from the terminal device, the session establishment request message being used to request the establishment of the first type of session.

10. The method according to claim 9, characterized in that, The session establishment request message includes at least one of the following: an emergency request, an emergency data network name, or a network slice identifier corresponding to the first type of session, wherein the emergency request is used to request the first type of session.

11. The method according to any one of claims 1-10, characterized in that, Sending the first information to the access network device includes: Send a configuration update message or an N2 request message to the access network device, wherein the configuration update message or N2 request message includes the first information.

12. A communication method, characterized in that, Applied to access network equipment, the method includes: Receive second information, which is used to trigger the access network device not to configure inactive discontinuous reception parameters to the terminal device, or to trigger the access network device to configure the inactive discontinuous reception parameters to be empty to the terminal device; Based on the second information, the terminal device is configured with an empty inactive discontinuous reception parameter, or no inactive discontinuous reception parameter is configured for the terminal device; or... If the conditions for the terminal device to enter the inactive state are met, the terminal device is not instructed to enter the inactive state according to the second information.

13. The method according to claim 12, characterized in that, The step of configuring the inactive, discontinuous reception parameters of the terminal device to be empty includes: A first message is sent to the terminal device. The first message is used to trigger the terminal device to enter an inactive state. The first message carries the inactive state discontinuous reception parameters, which are empty.

14. The method according to claim 12 or 13, characterized in that, The inactive discontinuous reception parameters include the ran-Extended Paging Cycle.

15. The method according to any one of claims 12-14, characterized in that, The second information includes the first information, and receiving the second information includes: Receive the first information from the mobility management network element; The first information is used to trigger the access network device not to configure inactive discontinuous reception parameters to the terminal device, or to trigger the access network device to configure the inactive discontinuous reception parameters to be empty to the terminal device.

16. The method according to claim 15, characterized in that, The method further includes: Based on the first information, it is determined that the terminal device has a first type of session, which is used for the terminal device's emergency services.

17. The method according to claim 15 or 16, characterized in that, The first information includes: Instructions for the access network device to configure the terminal device to disable inactive, discontinuous reception; or... Instruction information used to instruct the access network device to delete the idle-state discontinuous reception parameters and / or the inactive-state discontinuous reception parameters of the terminal device; or, Indication information used to indicate that the terminal device has a first type of session, the first type of session being used for the terminal device's emergency services.

18. The method according to claim 15 or 16, characterized in that, The first information is the first RRC Inactive auxiliary information corresponding to the terminal device, and the first RRC Inactive auxiliary information does not include idle state discontinuous reception parameters.

19. The method according to claim 18, characterized in that, The method further includes: The terminal device receives second RRC Inactive assistance information from the mobility management network element, the second RRC Inactive assistance information including the idle state discontinuous reception parameters.

20. The method according to any one of claims 12-14, characterized in that, The second information includes the third information, and receiving the second information includes: Receive the third information from the terminal device; The third piece of information is used to trigger the access network device to configure the inactive, discontinuous reception parameters to be empty for the terminal device.

21. The method according to claim 20, characterized in that, The method further includes: Based on the third information, it is determined that the terminal device has a first type of session, which is used for the terminal device's emergency services.

22. The method according to claim 20 or 21, characterized in that, The third information includes: Indication information used to indicate that the first inactive discontinuous reception parameters sent by the access network device are refused; or, Indication information used to indicate the presence of a first type of session, the first type of session being used for emergency services of the terminal device; or... This is used to instruct the access network device to configure the terminal device with empty inactive, discontinuous reception parameters.

23. A communication method, characterized in that, Applied to a terminal device, the method includes: Receive a first inactive discontinuous reception parameter from the access network device, wherein the first inactive discontinuous reception parameter is not empty; When the terminal device has a first type of session, and the first type of session is used to serve the terminal device's emergency services, a third message is sent to the access network device. The third message is used to trigger the access network device to configure the terminal device to have an empty inactive discontinuous reception parameter.

24. The method according to claim 23, characterized in that, The third information includes: Indication information used to indicate that the first inactive state discontinuous reception parameter is refused to be enabled; or, Indication information used to indicate that the terminal device has the first type of session; or, This is used to instruct the access network device to configure the terminal device with empty inactive, discontinuous reception parameters.

25. The method according to claim 24, characterized in that, The receiving of the first inactive discontinuous reception parameters from the access network device includes: Receive a first message, the first message being used to trigger the terminal device to enter an inactive state, the first message carrying the first inactive state discontinuous reception parameters; The third information includes indication information for indicating that entry into the inactive state is refused.

26. The method according to any one of claims 23-25, characterized in that, The method further includes: Receive a second inactive discontinuous reception parameter from the access network device, wherein the second inactive discontinuous reception parameter is empty; Based on the second inactive state discontinuous reception parameter, inactive state discontinuous reception is disabled.

27. A communication device, characterized in that, Includes modules for performing the methods as described in any one of claims 1-11, 12-22, or 23-26.

28. A communication device, characterized in that, include: processor; The processor is configured to run computer programs or instructions to enable the implementation of the method as described in any one of claims 1-11, 12-22, or 23-26.

29. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1-11, 12-22, or 23-26.

30. A computer program product, characterized in that, Includes computer program code, which, when run on a communication device, implements the method as described in any one of claims 1-11, 12-22, or 23-26.

Images