Terminal device triggering method, apparatus, device, and storage medium

Abstract

The application provides a terminal device triggering method, device, equipment and storage medium, the method comprises: UDM retrieves the corresponding RAT type and the extended idle state DRX cycle length according to the identifier of the RedCap UE to be received trigger message, determines the first validity of the trigger message according to the RAT type and the extended idle state DRX cycle length, when determining that the trigger message is valid according to the first validity, according to the trigger message, application trigger business process is executed.In the embodiment of the application, the first validity is used to indicate whether the trigger message can be sent to the RedCap UE within the delay tolerance of the trigger message, and when it is determined that the trigger message is valid according to the first validity, the application trigger business process is executed according to the trigger message, which can effectively ensure that the trigger message is sent to the RedCap UE within the delay tolerance.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and particularly relates to a terminal device triggering method and device, equipment and a storage medium. BACKGROUND

[0002] In order to enable the network to identify the user equipment (UE) traffic accessed by the new radio (NR) reduced capability (RedCap) to enable charging differentiation processing, etc., the 3rd generation partnership project (3GPP) defines the NR RedCap UE differentiation function. Through this function, it can be identified whether the radio access technology (RAT) type of the UE is NR RedCap, thereby achieving the above purpose.

[0003] At the same time, in the process of data transmission between the network and the RedCap UE, the 3GPP explicitly supports the extended discontinuous reception (eDRX) operation of the RedCap UE in the idle state and the inactive state for the purpose of energy saving. Among them, DRX is the extended discontinuous reception (DRX), and the DRX mechanism refers to discontinuously receiving signals, so that the UE can be in a sleep state most of the time to achieve the purpose of power saving.

[0004] However, in the prior art, when the delay tolerance of the service data sent by the application on the network side to the RedCap UE is low, if the RedCap UE has enabled the eDRX mechanism, there is a problem that the service data cannot be sent to the RedCap UE within the delay tolerance. SUMMARY

[0005] The present application provides a terminal device triggering method, device, equipment and storage medium to solve the problem that the service data cannot be sent to the RedCap UE within the delay tolerance in the prior art.

[0006] In a first aspect, an embodiment of the present application provides a terminal device triggering method, applied to a UDM, and the method comprises the following steps:

[0007] retrieving a corresponding RAT type and an extended idle state DRX cycle length according to an identifier of a RedCap UE to receive the trigger message, the RAT type and the extended idle state DRX cycle length being acquired in a RedCap UE registration procedure;

[0008] determining a first validity of the trigger message according to the RAT type and the extended idle state DRX cycle length, the first validity indicating whether the trigger message can be sent to the RedCap UE within a delay tolerance of the trigger message;

[0009] performing an application trigger service procedure according to the trigger message when the trigger message is determined to be valid according to the first validity, the application trigger service procedure being used to deliver the trigger message to the RedCap UE.

[0010] In a possible design of the first aspect, before the retrieving a corresponding RAT type and an extended idle state DRX cycle length according to an identifier of a RedCap UE to receive the trigger message, the method further includes:

[0011] receiving a registration request sent by an AMF, the registration request carrying an NR RedCap indication, the NR RedCap indication indicating a device type of the RedCap UE;

[0012] registering the RedCap UE according to the registration request;

[0013] determining a RAT type of the RedCap UE as NR RedCap according to the NR RedCap indication;

[0014] receiving a notification sent by the AMF, and storing an extended idle state DRX cycle length of the RedCap UE carried in the notification.

[0015] Optionally, the determining a first validity of the trigger message according to the RAT type and the extended idle state DRX cycle length includes:

[0016] determining whether the trigger message can be sent to the RedCap UE within a delay tolerance of the trigger message according to the extended idle state DRX cycle length and the delay tolerance of the trigger message;

[0017] if yes, confirming that the first validity is valid;

[0018] if no, confirming that the first validity is invalid.

[0019] Optionally, when the trigger message is determined to be invalid according to the first validity, the method further comprises:

[0020] returning a first prediction result to the AF triggering the RedCap UE, the first prediction result comprising a first reason value indicating a reason why the trigger message cannot be sent to the RedCap UE, the first reason value comprising the extended idle state DRX cycle length.

[0021] Optionally, determining the RAT type of the RedCap UE as NR RedCap according to the NR RedCap indication comprises:

[0022] setting a value of a UE RAT type field of the RedCap UE as NR RedCap according to the NR RedCap indication.

[0023] Optionally, retrieving the corresponding RAT type and the extended idle state DRX cycle length according to the identifier of the RedCap UE to be received with the trigger message comprises:

[0024] parsing the GPSI of the RedCap UE to obtain the identifier;

[0025] retrieving the RAT type and the extended idle state DRX cycle length of the RedCap UE according to the identifier.

[0026] Optionally, after retrieving the corresponding RAT type and the extended idle state DRX cycle length according to the identifier of the RedCap UE to be received with the trigger message, the method further comprises:

[0027] determining a second validity of the trigger message according to the extended idle state DRX cycle length and a validity duration of the trigger message, the second validity being used to predict whether the trigger message is successfully sent to the RedCap UE;

[0028] when the trigger message is determined to be valid according to the second validity, performing an application trigger service process according to the trigger message;

[0029] when the trigger message is determined to be invalid according to the second validity, returning a second prediction result to the AF, the second prediction result comprising a second reason value indicating a reason why the trigger message cannot be successfully sent to the RedCap UE, the second reason value comprising the extended idle state DRX cycle length.

[0030] Secondly, embodiments of this application provide a triggering method for a terminal device, applied to a terminal, the method comprising:

[0031] During the RRC connection establishment process initiated to the gNB, an NR RedCap indication is sent to the gNB, and the NR RedCap indication is used to indicate the device type of the RedCap UE;

[0032] After establishing an RRC connection with the gNB, a request is sent to the gNB; wherein the request is used to request registration of the RedCap UE and to request the activation of the extended idle state DRX mechanism, so that the gNB interacts with the corresponding AMF according to the request and the NR RedCap indication, registers the RedCap UE in the UDM through the AMF, and determines the extended idle state DRX period length of the RedCap UE, wherein the UDM is used in the method described in any of the first aspects;

[0033] The system receives feedback information returned by the gNB and enables the extended idle state DRX mechanism based on the feedback information, wherein the feedback information includes the extended idle state DRX cycle length.

[0034] In one possible design of the second aspect, the request includes a registration sub-request, requested DRX parameters, and extended idle state DRX parameters; wherein the registration sub-request is used to request registration of the RedCap UE, and the extended idle state DRX parameters include the extended idle state DRX period length.

[0035] Optionally, the feedback information may also include: accepted DRX parameters, parameters of the extended idle state DRX, and PTW, wherein the accepted DRX parameters are determined based on the requested DRX parameters.

[0036] Thirdly, embodiments of this application provide a triggering device for a terminal device, applied to a UDM, the device comprising:

[0037] The retrieval module is used to retrieve the corresponding RAT type and extended idle state DRX cycle length based on the identifier of the RedCap UE to receive the trigger message. The RAT type and extended idle state DRX cycle length are obtained during the RedCap UE registration process.

[0038] The determination module is used to determine the first validity of the trigger message based on the RAT type and the extended idle state DRX period length. The first validity is used to indicate whether the trigger message can be sent to the RedCap UE within the delay tolerance of the trigger message.

[0039] The execution module is configured to execute an application triggering service process according to the trigger message when it is determined that the trigger message is valid according to the first validity, and the application triggering service process is configured to deliver the trigger message to the RedCap UE.

[0040] In a possible design of the third aspect, before the identifier of the RedCap UE to be received, the corresponding RAT type and the extended idle state DRX cycle length are retrieved, the apparatus further includes:

[0041] The receiving module is configured to receive a registration request sent by an AMF, and the registration request carries an NR RedCap indication, and the NR RedCap indication is configured to indicate a device type of the RedCap UE.

[0042] The registration module is configured to register the RedCap UE according to the registration request.

[0043] The determining module is further configured to determine, according to the NR RedCap indication, a RAT type of the RedCap UE as an NR RedCap.

[0044] The receiving module is further configured to receive a notification sent by the AMF, and store an extended idle state DRX cycle length of the RedCap UE carried in the notification.

[0045] Optionally, the determining module is specifically configured to:

[0046] determine, according to the extended idle state DRX cycle length and a delay tolerance of the trigger message, whether the trigger message can be sent to the RedCap UE within the delay tolerance;

[0047] if yes, confirm that the first validity is valid;

[0048] if no, confirm that the first validity is invalid.

[0049] Optionally, when it is determined that the trigger message is invalid according to the first validity, the apparatus further includes:

[0050] return a first prediction result to an AF triggering the RedCap UE, and the first prediction result includes a first reason value, the first reason value is configured to indicate a reason why the trigger message cannot be sent to the RedCap UE, and the first reason value includes the extended idle state DRX cycle length.

[0051] Optionally, the determining module is specifically configured to:

[0052] According to the NR RedCap indication, a value of a UE RAT type field of the RedCap UE is set to NR RedCap.

[0053] Optionally, the retrieval module is specifically configured to:

[0054] The GPSI of the RedCap UE is parsed to obtain the identifier.

[0055] The RAT type and the extended idle state DRX cycle length of the RedCap UE are retrieved according to the identifier.

[0056] Optionally, after the corresponding RAT type and the extended idle state DRX cycle length are retrieved according to the identifier of the RedCap UE to be received, the trigger message, the determination module is further configured to determine a second validity of the trigger message according to the extended idle state DRX cycle length and a valid duration of the trigger message, the second validity being used to predict whether the trigger message is successfully sent to the RedCap UE.

[0057] The execution module is further configured to execute an application trigger service process according to the trigger message when the trigger message is determined to be valid according to the second validity.

[0058] The return module is further configured to return a second prediction result to the AF when the trigger message is determined to be invalid according to the second validity, the second prediction result including a second reason value, the second reason value being used to indicate a reason why the trigger message cannot be successfully sent to the RedCap UE, and the second reason value including the extended idle state DRX cycle length.

[0059] In a fourth aspect, an embodiment of the present application provides a terminal device trigger apparatus applied to a terminal device, the apparatus comprising:

[0060] The sending module is configured to send an NR RedCap indication to the gNB in the RRC connection establishment process initiated to the gNB, the NR RedCap indication being used to indicate a device type of the RedCap UE.

[0061] The sending module is further configured to send a request to the gNB after establishing an RRC connection with the gNB; the request is used to request registration of the RedCap UE and to request enabling of the extended idle state DRX mechanism, so that the gNB interacts with a corresponding AMF according to the request and the NR RedCap indication, registers the RedCap UE in a UDM through the AMF, and determines an extended idle state DRX cycle length of the RedCap UE, and the UDM is used to implement the method of any one of the first aspect.

[0062] The receiving module is further configured to receive feedback information returned by the gNB, and enable the extended idle state DRX mechanism based on the feedback information, wherein the feedback information includes an extended idle state DRX cycle length.

[0063] In a possible design of the fourth aspect, the request includes a registration sub-request, a requested DRX parameter, and an extended idle state DRX parameter; the registration sub-request is used to request registration of the RedCap UE, and the extended idle state DRX parameter includes the extended idle state DRX cycle length.

[0064] Optionally, the feedback information further includes an accepted DRX parameter, the extended idle state DRX parameter, and a PTW; the accepted DRX parameter is determined according to the requested DRX parameter.

[0065] In the fifth aspect, an embodiment of the present application provides a UDM, including a processor, a memory, and computer program instructions stored in the memory and executable on the processor, and the processor is configured to implement the method provided in the first aspect and possible designs.

[0066] In the sixth aspect, an embodiment of the present application provides a terminal, including a transceiver, a processor, a memory, and computer program instructions stored in the memory and executable on the processor, and the processor is configured to implement the method provided in the second aspect and possible designs.

[0067] In the seventh aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium stores computer execution instructions, and the computer execution instructions are executed by a processor to implement the method provided in the first aspect, the second aspect, and possible designs.

[0068] In the eighth aspect, an embodiment of the present application provides a computer program product, including a computer program, and the computer program is executed by a processor to implement the method provided in the first aspect, the second aspect, and possible designs.

[0069] The terminal device triggering method, device, equipment and storage medium provided by the embodiments of the present application, the UDM retrieves the corresponding RAT type and extended idle state DRX cycle length according to the identifier of the RedCap UE to be received the triggering message, determines the first validity of the triggering message according to the RAT type and the extended idle state DRX cycle length, and executes the application triggering business process according to the triggering message when it is determined that the triggering message is valid according to the first validity. In the embodiments of the present application, the first validity is used to indicate whether the triggering message can be sent to the RedCap UE within the delay tolerance of the triggering message, and the application triggering business process is executed according to the triggering message when it is determined that the triggering message is valid according to the first validity, which can effectively ensure that the triggering message is sent to the RedCap UE within the delay tolerance. BRIEF DESCRIPTION OF DRAWINGS

[0070] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate embodiments consistent with the present application and, together with the description, further serve to explain the principles of the application.

[0071] Figure 1 A structural schematic diagram of a communication system provided by the embodiments of the present application is provided.

[0072] Figure 2 A flowchart of the terminal device triggering method embodiment one provided by the embodiments of the present application is provided.

[0073] Figure 3 A flowchart of the terminal device triggering method embodiment two provided by the embodiments of the present application is provided.

[0074] Figure 4 A flowchart of the terminal device triggering method embodiment three provided by the embodiments of the present application is provided.

[0075] Figure 5 A flowchart of the terminal device triggering method embodiment four provided by the embodiments of the present application is provided.

[0076] Figure 6 A structural schematic diagram of the terminal device triggering device embodiment one provided by the embodiments of the present application is provided.

[0077] Figure 7 A structural schematic diagram of the terminal device triggering device embodiment two provided by the embodiments of the present application is provided.

[0078] Figure 8 A structural schematic diagram of the UDM provided by the embodiments of the present application is provided.

[0079] Figure 9 A structural schematic diagram of the terminal device provided by the embodiments of the present application is provided.

[0080] The specific embodiments of the present application have been shown and described in the above drawings and text, and will be described in more detail below. These drawings and text are not intended to limit the scope of the present application concept in any way, but to illustrate the present application concept to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0081] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of protection of the present application.

[0082] Before introducing the embodiments of the present application, the terms involved in the embodiments of the present application are first explained:

[0083] DRX mechanism: through discontinuous reception of signals, the UE can be in a sleep state most of the time to achieve the purpose of power saving. Because the packet-based data flow is generally bursty, when there is no data transmission, the receiving circuit of the UE can be turned off to reduce power consumption.

[0084] eDRX: extended DRX, 3GPP stipulates that only the UE of enhanced Machine Type Communication (eMTC) can use the eDRX mechanism when in the Radio Resource Control (RRC) inactive state, while other UEs, such as Long Term Evolution (LTE) UE or New Radio (NR) UE, etc., cannot use the eDRX mechanism when in the RRC Inactive state.

[0085] Next, the application background of the present application is explained:

[0086] 3GPP defines a NR RedCap UE differentiation function, which is used to indicate a NR RedCap UE using NR to provide a NR RedCap indication to a Next Generation-Radio Access Network (NG-RAN) during a RRC connection establishment procedure. Further, the NG-RAN provides the NR RedCap indication to an Authentication Management Function (AMF) in an Initial UE message. When the AMF receives the NR RedCap indication from the NG-RAN in the Initial UE message, it stores the NR RedCap indication in the context of the UE and considers the RAT type of the UE as NR RedCap.

[0087] Meanwhile, in the process of data transmission between the network and the RedCap UE, the RedCap UE supports the upper layer to configure the terminal-specific eDRX cycle for energy saving; for the inactive state, the RedCap UE supports the RRC and the upper layer to configure the terminal-specific eDRX cycle. The eDRX cycle in the idle state can be extended to a maximum of 10485.76 seconds (2.91 hours) and a minimum of 2.56 seconds; the eDRX cycle in the inactive state can be extended to a maximum of 10.24 seconds and a minimum of 2.56 seconds. When the eDRX cycle is greater than 10.24 seconds, a Paging Time Window (PTW) mechanism is used to send a paging message.

[0088] However, when the network side application using the extended idle state DRX is used, when sending service data with lower delay tolerance (such as Mobile Terminated (MT) data, Short Message Service (SMS), or trigger messages, etc.) to the RedCap UE, it cannot be determined whether the RedCap UE supports the eDRX mechanism in the idle state and the inactive state, and whether the eDRX mechanism is enabled. When the RedCap UE enables the eDRX mechanism, there is a problem that the service data cannot be sent to the RedCap UE within the delay tolerance.

[0089] Based on the above problems, the application concept is as follows: in the existing process of 3GPP, since the NR RedCap indication or RAT type is not explicitly delivered to the UDM, and the user subscription data type for storing the NR RedCap indication (or RAT type) is also not defined in the local user subscription data of the UDM, when the application on the network side initiates a service data with low delay tolerance, the NR RedCap UE cannot be correctly identified, and the RedCap UE enables the eDRX mechanism. Therefore, the application provides a terminal device triggering method, which can deliver the NR RedCap indication and the extended idle state DRX cycle length to the UDM for storage when the RedCap UE is registered. In this way, when the application on the network side sends a triggering message to the RedCap UE, the UDM can determine whether the triggering message can be sent to the RedCap UE within the delay tolerance of the triggering message according to the pre-stored NR RedCap indication and the extended idle state DRX cycle length, thereby solving the above technical problems.

[0090] For example, the terminal device triggering method provided by the embodiments of the application can be applied to a communication system, as shown in the schematic diagram. Figure 1 A structural schematic diagram of a communication system provided by the embodiments of the application is shown in the figure. Figure 1 As shown in the figure, the communication system includes an application function entity (Application Function, AF), a unified data management entity (Unified Data Management, UDM), an authentication management function (Authentication Management Function, AMF), a network exposure function entity (Network Exposure Function, NEF), a base station (gNB), a short message service-service center (Short Message Service-Service Center, SMS-SC), and a RedCap UE.

[0091] Among them, the NEF communicates and interacts with the AF, the UDM and the SMS-SC through wireless means, the AMF communicates and interacts with the UDM and the gNB through wireless means, and the RedCap UE communicates and interacts with the gNB and the SMS-SC through wireless means.

[0092] Among them, the NEF can pre-store the contact information of the UDM, so as to communicate and interact with the UDM through the contact information, and can also perform the discovery and selection service of the UDM, so as to determine the contact information of the UDM from the UDM contact information list, and communicate and interact with the UDM.

[0093] In actual application, the RedCap UE can send the NR RedCap indication and the cycle length of the extended idle state DRX to the UDM through the gNB and the AMF to complete the registration process and enable the DRX.

[0094] Further, when the AF confirms that the RedCap UE needs to be triggered to perform the PDU session establishment process, the NEF can send a trigger request carrying a trigger message to the UDM. The UDM can determine whether the trigger message can be sent to the RedCap UE within the delay tolerance according to the NR RedCap indication and the cycle length of the extended idle state DRX stored in advance in the RedCap UE registration process. If so, the UDM performs the application trigger service process through the SMS-SC to deliver the trigger message to the RedCap UE. If not, the UDM returns a prediction result to the AF, so that the AF can timely adjust the trigger message or the cycle length of the extended idle state DRX.

[0095] It can be understood that, Figure 1 The communication system shown is only a schematic diagram of the communication system, which can also include other network devices or network entities, such as core network devices, wireless relay devices and wireless backhaul devices, and the embodiments of the present application do not specifically limit this.

[0096] The system architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. It can be known by those skilled in the art that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0097] In the following, the technical solutions of the present application are described in detail through specific embodiments.

[0098] It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes can not be described in some embodiments.

[0099] Figure 2 The flowchart of the terminal device triggering method embodiment provided by the embodiments of the present application is shown in FIG. 1. As shown in FIG. 1, the terminal device triggering method is applied to the UDM, and the terminal device triggering method can include the following steps: Figure 2

[0100] S201, according to the identifier of the RedCap UE to be received, the trigger message is retrieved corresponding to the RAT type and the extended idle state DRX cycle length.

[0101] ​The RAT type and the extended idle state DRX cycle length are obtained in a RedCap UE registration process.

[0102] Optionally, the identifier, the RAT type, and the extended idle state DRX cycle length have a mapping relationship, which can be represented by Table 1.

[0103] Table 1

[0104] Number Identifier RAT Type Extended Idle State DRX Cycle Length Number 1 Identifier 1 RAT Type 1 Extended Idle State DRX Cycle Length 1 Number 2 Identifier 2 RAT Type 2 Extended Idle State DRX Cycle Length 2 Number 3 Identifier 3 RAT Type 3 Extended Idle State DRX Cycle Length 3

[0105] As shown in Table 1, the identifier of the RedCap UE can be searched in the mapping relationship shown in Table 1 to obtain the RAT type corresponding to the identifier of the RedCap UE and the extended idle state DRX cycle length. Assuming that the identifier of the RedCap UE is identifier 2, the identifier 2 is searched in Table 2 to obtain the RAT type corresponding to the identifier 2, which is RAT type 2, and the extended idle state DRX cycle length corresponding to the identifier 2, which is extended idle state DRX cycle length 2.

[0106] Optionally, the identifier can be a subscription permanent identifier (SUPI) or a mobile station international ISDN number (MSISDN), which can be determined according to actual conditions, and the type of the identifier is not specifically limited in the embodiments of the application.

[0107] S202, determining a first validity of the trigger message according to the RAT type and the extended idle state DRX cycle length.

[0108] The first validity is obtained according to the extended idle state DRX cycle length and the delay tolerance of the trigger message after it is determined that the RedCap UE starts the extended DRX according to the RAT type and the extended idle state DRX cycle length.

[0109] Optionally, the delay tolerance is used to represent the maximum delay tolerance of the trigger message.

[0110] The first validity is used to indicate whether the trigger message can be sent to the RedCap UE within the delay tolerance of the trigger message. That is, when the first validity is valid, it indicates that the trigger message can be sent to the RedCap UE within the delay tolerance of the trigger message; and when the first validity is invalid, it indicates that the trigger message cannot be sent to the RedCap UE within the delay tolerance of the trigger message.

[0111] The trigger message is used to trigger the RedCap UE to perform a PDU session establishment procedure.

[0112] S203, when it is determined according to the first validity that the trigger message is valid, performing an application trigger service procedure according to the trigger message.

[0113] The application trigger service procedure is used to deliver the trigger message to the RedCap UE.

[0114] Optionally, when it is determined according to the first validity that the trigger message is invalid, the subsequent application trigger service procedure is not performed.

[0115] Optionally, the application trigger service procedure can include the following steps:

[0116] The Short Message Service Function (SMSF) identifier of the RedCap UE and a target Short Message Service-Service Center (SMS-SC) are determined, and the trigger message is sent to the target SMS-SC. After receiving the trigger message, the target SMS-SC performs an MT Short Message Service (SMS) transfer procedure to deliver the trigger message to the RedCap UE. The trigger message can include the GPSI of the RedCap UE, a trigger reference number, a validity period, a priority, an SMSF identifier, an SMS application port ID, a trigger payload, and a trigger indication.

[0117] The terminal device trigger method provided in the embodiments of the present application includes: a UDM retrieves a corresponding RAT type and an extended idle state DRX cycle length according to an identifier of a RedCap UE to be received by a trigger message; the UDM determines a first validity of the trigger message according to the RAT type and the extended idle state DRX cycle length; and when it is determined according to the first validity that the trigger message is valid, the UDM performs an application trigger service procedure according to the trigger message. In the embodiments of the present application, the first validity is used to indicate whether the trigger message can be sent to the RedCap UE within a delay tolerance of the trigger message, and when it is determined according to the first validity that the trigger message is valid, the application trigger service procedure is performed according to the trigger message, which can effectively ensure that the trigger message is sent to the RedCap UE within the delay tolerance. The successful execution of the RedCap UE trigger service is ensured, and the system performance is guaranteed.

[0118] Optionally, in the embodiments shown in FIG. 8, before S201, the terminal device trigger method further includes: Figure 2

[0119] ​receive the registration request sent by the AMF, register the RedCap UE according to the registration request, further, determine the RAT type of the RedCap UE as NR RedCap according to the NR RedCap indication, and receive the notification sent by the AMF, and store the extended idle state DRX cycle length of the RedCap UE carried in the notification.

[0120] The registration request carries the NR RedCap indication, and the NR RedCap indication is used to indicate the device type of the RedCap UE.

[0121] Optionally, the notification is sent to the UDM through the AMF when the RedCap UE requests to start the extended DRX.

[0122] In the above embodiment, during the registration process of the RedCap UE, the RAT type of the RedCap UE can be stored as NR RedCap according to the NR RedCap indication sent by the RedCap UE, and when the RedCap UE applies to start the extended DRX, the extended idle state DRX cycle length of the RedCap UE is stored, which lays a foundation for subsequent determination of the first validity of the trigger message.

[0123] Optionally, in some embodiments, S202 can be implemented by the following steps:

[0124] According to the extended idle state DRX cycle length and the delay tolerance of the trigger message, it is determined whether the trigger message can be sent to the RedCap UE within the delay tolerance, if yes, it is confirmed that the first validity is valid, and if not, it is confirmed that the first validity is invalid.

[0125] Since the duration of sending the trigger message to the RedCap UE is closely related to the extended idle state DRX cycle length, in this embodiment, before sending the trigger message, it can be predicted according to the delay tolerance of the trigger message and the extended idle state DRX cycle length whether the trigger message can be sent to the RedCap UE within the delay tolerance, so as to determine whether to send the trigger message for subsequent processing, thereby ensuring the timeliness of sending the trigger message and avoiding invalid sending operation of the trigger message when the first validity is invalid.

[0126] Optionally, in some embodiments, when it is determined that the trigger message is invalid according to the first validity, the triggering method of the terminal device can further include the following steps:

[0127] The first prediction result is returned to the AF triggering the RedCap UE. The first prediction result includes a first cause value indicating a reason why the triggering message cannot be sent to the RedCap UE, and the first cause value includes an extended idle state DRX cycle length.

[0128] In the above embodiment, when the first validity is invalid, it indicates that the triggering message cannot be sent to the RedCap UE within the delay tolerance. By returning the first prediction result to the AF, the AF can adjust the extended idle state DRX cycle length of the triggering message or the RedCap UE according to the first prediction result, thereby avoiding the problem of long delay time of sending the triggering message.

[0129] Optionally, in some embodiments, the above step of determining the RAT type of the RedCap UE as NR RedCap according to the NR RedCap indication can be implemented by the following steps:

[0130] According to the NR RedCap indication, the value of the UE RAT type field of the RedCap UE is set to NR RedCap.

[0131] In the above embodiment, by setting the value of the UE RAT type field of the RedCap UE to NR RedCap, the RAT type of the RedCap UE is stored, which lays a foundation for subsequent determination of the first validity of the triggering message.

[0132] Optionally, in some embodiments, the above step of retrieving the corresponding RAT type and the extended idle state DRX cycle length according to the identifier of the RedCap UE to be received can be implemented by the following steps:

[0133] The GPSI of the RedCap UE is parsed to obtain the identifier, and the RAT type and the extended idle state DRX cycle length of the RedCap UE are retrieved according to the identifier.

[0134] Optionally, the type of the identifier used when the RedCap UE performs the PDU session establishment process can be determined according to the UDM policy, then the GPSI of the RedCap UE is parsed according to the type of the identifier to obtain the identifier, and finally the access and mobility user data of the RedCap UE is retrieved according to the identifier.

[0135] Optionally, in some embodiments, after the above step of retrieving the corresponding RAT type and the extended idle state DRX cycle length according to the identifier of the RedCap UE to be received, the triggering method of the terminal device can further include the following steps:

[0136] According to the extended idle state DRX cycle length and the valid time length of the trigger message, a second validity of the trigger message is determined, and when it is determined according to the second validity that the trigger message is valid, an application trigger service process is performed according to the trigger message; when it is determined according to the second validity that the trigger message is invalid, a second prediction result is returned to the AF.

[0137] The second validity is used to predict whether the trigger message is successfully sent to the RedCap UE, and the second prediction result includes a second cause value, the second cause value is used to indicate a reason why the trigger message cannot be successfully sent to the RedCap UE, and the second cause value includes the extended idle state DRX cycle length.

[0138] Optionally, after receiving the second prediction result, the AF can also perform any one of the following processing on the trigger message:

[0139] Discarding the trigger message, adjusting the valid time length of the trigger message, and adjusting the sending time of the trigger message.

[0140] In the above embodiment, the second validity of the trigger message can be determined according to the extended idle state DRX cycle length and the valid time length of the trigger message, and when it is determined according to the second validity that the trigger message is valid, the application trigger service process is performed, and when it is determined according to the second validity that the trigger message is invalid, the subsequent application trigger service process is stopped, the application trigger service process is used to deliver the trigger message to the RedCap UE, the invalid resource occupation and signaling overhead are reduced, and the processing efficiency and the success rate of the trigger message sending are improved.

[0141] Figure 3 A flowchart of a second embodiment of a terminal device triggering method provided by the embodiments of the present application is shown in FIG. 6. Figure 3 As shown in FIG. 6, the terminal device triggering method is applied to a terminal device, and the terminal device triggering method can include the following steps:

[0142] S301, in the process of initiating RRC connection establishment to the gNB, a NR RedCap indication is sent to the gNB.

[0143] The NR RedCap indication is used to indicate the device type of the RedCap UE.

[0144] S302, after establishing the RRC connection with the gNB, a request is sent to the gNB.

[0145] The request is used to request registration of the RedCap UE, and to request enabling of the extended idle state DRX mechanism, so that the gNB interacts with the corresponding AMF according to the request and the NR RedCap indication, registers the RedCap UE in the UDM through the AMF, and determines the extended idle state DRX cycle length of the RedCap UE. The UDM is used to perform the method shown in any of the above embodiments.

[0146] Optionally, the request includes a registration sub-request, requested DRX parameters, and extended idle state DRX parameters. The registration sub-request is used to request registration of the RedCap UE, and the extended idle state DRX parameters include the extended idle state DRX cycle length.

[0147] S303, receiving feedback information returned by the gNB, and enabling the extended idle state DRX mechanism based on the feedback information.

[0148] The feedback information includes the extended idle state DRX cycle length.

[0149] Optionally, in some embodiments, the feedback information further includes accepted DRX parameters, extended idle state DRX parameters, and a paging time window (PTW). The accepted DRX parameters are determined according to the requested DRX parameters, that is, after the UDM receives the requested DRX parameters, the requested DRX parameters can be stored, and the stored DRX parameters (that is, the accepted DRX parameters) are returned to the RedCap UE through the AMF and the gNB. At this time, the accepted DRX parameters are the same as the requested DRX parameters.

[0150] The terminal device triggering method provided by the embodiments of the present application is as follows: the RedCap UE sends an NR RedCap indication to the gNB in the RRC connection establishment process initiated to the gNB, sends a request to the gNB after establishing an RRC connection with the gNB, receives feedback information returned by the gNB, and enables the extended idle state DRX mechanism based on the feedback information. In this technical solution, the RedCap UE sends the NR RedCap indication and the request to the gNB, so that the UDM stores the RAT type and the extended idle state DRX cycle length of the RedCap UE, which lays a foundation for the UDM to calculate the first validity of the triggering message for triggering the RedCap UE in the future.

[0151] Based on the above multiple embodiments, the terminal device triggering method is specifically described through two specific examples.

[0152] Example 1: registration process.

[0153] Figure 4 The flowchart of the third embodiment of the terminal device triggering method provided by the embodiments of the present application is shown. As shown in the figure, the terminal device triggering method comprises the following steps: Figure 4

[0154] S401. The RedCap UE delivers the NR RedCap indication to the gNB in the initiated RRC connection establishment process.

[0155] S402. After the RedCap UE establishes the RRC connection with the gNB, the RedCap UE sends a request to the gNB.

[0156] The request can be sent to the gNB in the form of an access network (AN) message.

[0157] Optionally, the request includes a registration sub-request, a requested DRX parameter, and a parameter for extending the idle state DRX.

[0158] Correspondingly, the gNB receives the request.

[0159] S403. After the gNB receives the request, the gNB selects an AMF for the RedCap UE according to the NR RedCap indication, and sends an initial UE message (Initial UE Message) to the AMF.

[0160] Optionally, the initial UE message includes a registration sub-request, an NR RedCap indication, a requested DRX parameter, and a parameter for extending the idle state DRX.

[0161] Correspondingly, the AMF receives the initial UE message.

[0162] S404. The AMF stores the information carried in the initial UE message in the UE context.

[0163] Optionally, the information includes an NR RedCap indication, a DRX parameter specified by the RedCap UE (i.e., the requested DRX parameter), and a parameter for extending the idle state DRX.

[0164] S405. The AMF authenticates the RedCap UE, and after passing, sends a registration request to the UDM.

[0165] Optionally, the AMF can call Nudm_UECM_Registration to send the registration request to the UDM.

[0166] Correspondingly, the UDM receives the registration request sent by the AMF.

[0167] ​S406, the UDM registers the RedCap UE according to the registration request, and sets the value of the UE RAT type field in the access and mobility subscription data of the RedCap UE to NR RedCap after the registration is successful.

[0168] S407, the AMF sends a notification to the UDM.

[0169] The notification carries the extended idle state DRX cycle length of the RedCap UE.

[0170] Optionally, the AMF can call Nudm_SDM_Subscribe to send the notification to the UDM.

[0171] Correspondingly, for the UDM, the notification sent by the AMF is received.

[0172] S408, the UDM sets the value of the extended idle state DRX cycle length field in the access and mobility subscription data of the RedCap UE according to the accepted extended idle state DRX parameters.

[0173] S409, the AMF sends a registration acceptance message to the UE through the gNB to complete the registration process.

[0174] The registration acceptance message includes the accepted DRX parameters, the extended idle state DRX parameters, and the PTW, and is the feedback information.

[0175] Correspondingly, for the RedCap UE, the registration acceptance message is received.

[0176] S410, the RedCap UE starts the extended idle state DRX mechanism based on the received extended idle state DRX cycle length and PTW.

[0177] Example two: trigger process.

[0178] Figure 5 The flowchart of the fourth embodiment of the terminal device trigger method provided by the embodiments of the present application is shown in FIG. 8. Figure 5 As shown in the figure, the terminal device trigger method includes the following steps:

[0179] S501, when it is confirmed that the RedCap UE needs to be triggered to perform the PDU session establishment process, the AF determines the contact information of the NEF.

[0180] The contact information can be pre-stored by the AF, or can be determined from the NEF contact information list by performing a discovery and selection service of the NEF.

[0181] Optionally, the NEF contact information list includes contact information of multiple NEFs.

[0182] S502, the AF sends a trigger request to the NEF according to the contact information of the NEF.

[0183] Optionally, the trigger request carries a trigger message, which is used to request the delivery of the trigger message to the RedCap UE.

[0184] Optionally, this step can call Nnef_Trigger_Delivery.

[0185] Correspondingly, for the NEF, the trigger request sent by the AF is received.

[0186] S503, the NEF determines whether the AF has the right to send the trigger message according to the trigger request.

[0187] Optionally, determining whether the AF has the right to send the trigger message can include the following aspects: whether the AF has the right to trigger the message to the RedCap UE, whether the trigger message sent by the AF to the RedCap UE via the NF exceeds the trigger message submission quota, and whether the trigger message sent by the AF to the RedCap UE via the NF exceeds the preset trigger message submission frequency.

[0188] S504, when it is determined that the AF has the right, the NEF sends an information acquisition request to the UDM.

[0189] Optionally, the information acquisition request is used to acquire the UE RAT type and the extended idle state DRX cycle length of the RedCap UE.

[0190] Optionally, this step can call Nudm_SDM_Get.

[0191] Correspondingly, for the UDM, the information acquisition request sent by the NEF is received.

[0192] S505, the UDM returns the identifier of the RedCap UE, the UE RAT type and the extended idle state DRX cycle length to the NEF according to the information acquisition request.

[0193] Optionally, this step can be implemented by Nudm_SDM_Get response.

[0194] Correspondingly, for the NEF, the identifier of the RedCap UE, the UE RAT type and the extended idle state DRX cycle length returned by the UDM are received.

[0195] S506, the NEF determines validity of the trigger message according to the RAT type and the extended idle mode DRX cycle length.

[0196] Optionally, the validity includes a first validity and a second validity. The first validity is determined according to the RAT type and the extended idle mode DRX cycle length, and the second validity is determined according to the extended idle mode DRX cycle length and a validity duration of the trigger message.

[0197] Optionally, if the AF is not allowed to send the trigger message to the RedCap UE or the user does not have valid subscription information, the trigger message is invalid.

[0198] S507, the NEF returns a prediction message to the AF when the trigger message is invalid.

[0199] The prediction message can be returned to the AF through a Nnef_Trigger_Delivery response.

[0200] It should be understood that if the trigger message is invalid, the subsequent steps are not executed after S507 is executed.

[0201] S508, the NEF sends an SMSF identity obtaining request to the UDM when the trigger message is valid.

[0202] Optionally, the NEF can cache service node information of the RedCap UE. However, when the cached service node information expires, the possibility of failure of the trigger message delivery is increased.

[0203] The SMSF identity obtaining request is used to obtain the SMSF identity of the RedCap UE.

[0204] Optionally, this step can be implemented by invoking Nudm_UECM_Get.

[0205] Correspondingly, the UDM receives the SMSF identity obtaining request.

[0206] S509, the UDM retrieves the SMSF identity of the RedCap UE according to the SMSF identity obtaining request, and returns the retrieved SMSF identity of the RedCap UE to the NEF.

[0207] Optionally, the SMSF identity of the RedCap UE can be retrieved by invoking Nudr_DM_Query, and the retrieved SMSF identity of the RedCap UE can be returned to the NEF through a Nudm_UECM_Get response.

[0208] Correspondingly, the NEF receives the SMSF identity of the RedCap UE.

[0209] S510, the NEF selects a suitable SMS-SC based on the configuration information and sends a trigger message to the SMS-SC.

[0210] In this step, the NEF is mainly used as a Machine Type Communication-Inter Working Function (MTC-IWF).

[0211] Optionally, the trigger message can include GPSI, SUPI, AF identifier, trigger reference number, validity period, priority, SMSF identifier, SMS application port ID, trigger payload, and trigger indication.

[0212] Correspondingly, the SMS-SC receives the trigger message.

[0213] S511, the SMS-SC sends a trigger submission confirmation message to the NEF.

[0214] The trigger submission confirmation message is used to confirm that the SMS-SC has accepted the submission of the trigger message.

[0215] Optionally, if the NEF receives an indication of an "absent user" from the UDM, the SMS-SC does not send the trigger submission confirmation message, but directly stores and sends the routing information of the Short Message Service (SMS) containing the SMS-SC address to request the UDM to add the SMS-SC address to the message waiting list.

[0216] The message waiting list includes the SMS-SC addresses waiting to resend the trigger message.

[0217] Correspondingly, the NEF receives the trigger submission confirmation message sent by the SMS-SC.

[0218] S512, the NEF forwards the trigger submission confirmation message to the AF.

[0219] Optionally, it can be implemented through a Nnef_Trigger_Delivery response.

[0220] Correspondingly, the AF receives the trigger submission confirmation message.

[0221] S513, the SMS-SC performs an MT SMS transmission process.

[0222] Optionally, the SMS-SC can provide the SMSF identity to the Short Message Service-Gateway MSC (SMS-GMSC) to avoid UDM interrogation.

[0223] Optionally, the SMS-SC can store the payload of the trigger message without storing the SMSF identity, and if the trigger message delivery fails and a retry is attempted, UDM interrogation will be performed.

[0224] If the trigger message delivery fails and the validity duration of the trigger message is not set to zero, the SMS-SC will send an SM message delivery status report containing the SMS-SC address to request the UDM to add the SMS-SC address to the message waiting list.

[0225] When the message delivery is later retried, the SMS-GMSC will perform a new UDM interrogation using the SUPI or MSISDN. In response to the SMS-GMSC, the UDM can include up to four serving node identities (MSC or MME, SGSN, IP-SM-GW, AMF).

[0226] S514, the SMS-SC sends a message delivery report to the NEF.

[0227] The message delivery report is used to indicate that the trigger message delivery fails, the trigger message delivery succeeds, and unknown, which means that it cannot be determined whether the trigger message is successfully delivered to the RedCap UE.

[0228] Optionally, the message delivery report can also include a failure cause when the trigger message delivery fails.

[0229] Optionally, the failure cause can be the expiration of the validity duration of the trigger message.

[0230] Correspondingly, for the NEF, the message delivery report is received.

[0231] S515, the NEF sends the message delivery report to the AF.

[0232] Optionally, it can be implemented through the Nnef_Trigger_DeliveryNotify message.

[0233] Correspondingly, for the AF, the message delivery report is received.

[0234] S516, when the trigger message delivery succeeds, the RedCap UE takes a specific action in response to the trigger message according to the payload of the trigger message.

[0235] The specific action includes initiating communication with the AF immediately or later.

[0236] The following is an apparatus embodiment of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the apparatus embodiments of the present application, please refer to the method embodiments of the present application.

[0237] Figure 6 The structure diagram of the terminal device triggering device embodiment one provided by the present application is shown in FIG. 1. As shown in FIG. 1, the terminal device triggering device is applied to a UDM, and the terminal device triggering device comprises: Figure 6

[0238] The retrieval module 61 is configured to retrieve the corresponding RAT type and extended idle state DRX cycle length according to the identifier of the RedCap UE to be received the triggering message, wherein the RAT type and the extended idle state DRX cycle length are obtained in the RedCap UE registration process;

[0239] The determination module 62 is configured to determine the first validity of the triggering message according to the RAT type and the extended idle state DRX cycle length, wherein the first validity is used to indicate whether the triggering message can be sent to the RedCap UE within the delay tolerance of the triggering message;

[0240] The execution module 63 is configured to execute the application triggering service process according to the triggering message when it is determined that the triggering message is valid according to the first validity, wherein the application triggering service process is used to deliver the triggering message to the RedCap UE.

[0241] In a possible design of the present application, before the corresponding RAT type and the extended idle state DRX cycle length are retrieved according to the identifier of the RedCap UE to be received the triggering message, the apparatus further comprises:

[0242] The receiving module is configured to receive the registration request sent by the AMF, wherein the registration request carries the NR RedCap indication, and the NR RedCap indication is used to indicate the device type of the RedCap UE;

[0243] The registration module is configured to register the RedCap UE according to the registration request;

[0244] The determination module 62 is further configured to determine the RAT type of the RedCap UE as the NR RedCap according to the NR RedCap indication.

[0245] The receiving module is further configured to receive the notification sent by the AMF and store the extended idle state DRX cycle length of the RedCap UE carried by the notification.

[0246] Optionally, the determination module 62 is specifically configured to:

[0247] ​determine whether the trigger message can be sent to the RedCap UE within the delay tolerance according to the extended idle state DRX cycle length and the delay tolerance of the trigger message;

[0248] if yes, confirm that the first validity is valid;

[0249] if no, confirm that the first validity is invalid.

[0250] Optionally, when it is determined that the trigger message is invalid according to the first validity, the apparatus further comprises:

[0251] return the first prediction result to the AF triggering the RedCap UE, the first prediction result comprising a first reason value, the first reason value being used to indicate a reason why the trigger message cannot be sent to the RedCap UE, and the first reason value comprising the extended idle state DRX cycle length.

[0252] Optionally, the determining module 62 is specifically configured to:

[0253] set a value of a UE RAT type field of the RedCap UE to the NR RedCap according to the indication of the NR RedCap.

[0254] Optionally, the retrieving module 61 is specifically configured to:

[0255] analyze the GPSI of the RedCap UE to obtain an identifier;

[0256] retrieve the RAT type and the extended idle state DRX cycle length of the RedCap UE according to the identifier.

[0257] Optionally, after the corresponding RAT type and the extended idle state DRX cycle length are retrieved according to the identifier of the RedCap UE to be received, the determining module 62 is further configured to determine a second validity of the trigger message according to the extended idle state DRX cycle length and a validity duration of the trigger message, the second validity being used to predict whether the trigger message is successfully sent to the RedCap UE;

[0258] the executing module 63 is further configured to execute an application trigger service process according to the trigger message when it is determined that the trigger message is valid according to the second validity;

[0259] the returning module is further configured to return a second prediction result to the AF when it is determined that the trigger message is invalid according to the second validity, the second prediction result comprising a second reason value, the second reason value being used to indicate a reason why the trigger message cannot be successfully sent to the RedCap UE, and the second reason value comprising the extended idle state DRX cycle length.

[0260] The terminal device triggering apparatus provided by the embodiments of the present application can be used to execute the terminal device triggering method on the UDM side in any of the above embodiments, and has similar implementation principles and technical effects, which will not be described here.

[0261] Figure 7 A structural schematic diagram of the second embodiment of the terminal device triggering apparatus provided by the embodiments of the present application is shown in FIG. 7. Figure 7 As shown in FIG. 7, the terminal device triggering apparatus is applied to a terminal device, and the terminal device triggering apparatus comprises:

[0262] The sending module 71 is configured to send an NR RedCap indication to the gNB in the RRC connection establishment process initiated to the gNB, and the NR RedCap indication is used to indicate the device type of the RedCap UE.

[0263] The sending module 71 is further configured to send a request to the gNB after the RRC connection is established with the gNB, wherein the request is used to request the registration of the RedCap UE and to request the enabling of the extended idle state DRX mechanism, so that the gNB interacts with the corresponding AMF according to the request and the NR RedCap indication, registers the RedCap UE in the UDM through the AMF, and determines the extended idle state DRX cycle length of the RedCap UE, and the UDM is used to implement the terminal device triggering method on the UDM side in the above embodiments.

[0264] The receiving module 72 is further configured to receive feedback information returned by the gNB, and enable the extended idle state DRX mechanism based on the feedback information, wherein the feedback information comprises the extended idle state DRX cycle length.

[0265] In a possible design of the embodiments of the present application, the request comprises a registration sub-request, a requested DRX parameter, and an extended idle state DRX parameter; wherein the registration sub-request is used to request the registration of the RedCap UE, and the extended idle state DRX parameter comprises the extended idle state DRX cycle length.

[0266] Optionally, the feedback information further comprises an accepted DRX parameter, an extended idle state DRX parameter, and a PTW, wherein the accepted DRX parameter is determined according to the requested DRX parameter.

[0267] The terminal device triggering apparatus provided by the embodiments of the present application can be used to execute the terminal device triggering method on the terminal device side in any of the above embodiments, and has similar implementation principles and technical effects, which will not be described here.

[0268] It should be noted that the division of each module of the above apparatus is only a logical function division, and all or part of them can be integrated into a physical entity or physically separated when actually implemented. Moreover, all of these modules can be implemented in the form of software invoked by a processing element, or all of them can be implemented in the form of hardware, or some modules are implemented in the form of software invoked by a processing element and some modules are implemented in the form of hardware. In addition, all or part of these modules can be integrated together or implemented independently. The processing element mentioned herein can be an integrated circuit having a signal processing capability. In the implementation process, each step of the above method or each module can be completed by the integrated logic circuit of hardware in the processing element or the instruction in the form of software.

[0269] Figure 8 A structure diagram of the UDM provided by the embodiments of the present application is shown in FIG. 8. As shown in the figure, the UDM can include a processor 81, a memory 82, and computer program instructions stored in the memory 82 and executable on the processor 81, and the processor 81 implements the terminal device triggering method provided by any of the preceding embodiments when executing the computer program instructions. Figure 8

[0270] Optionally, the above various devices of the UDM can be connected through a system bus.

[0271] The memory 82 can be a separate storage unit or a storage unit integrated in the processor. The number of processors is one or more.

[0272] Optionally, the UDM can further include an interface for interacting with other devices.

[0273] The UDM provided by the embodiments of the present application can be used to execute the terminal device triggering method on the UDM side provided by any of the preceding method embodiments, and the implementation principle and technical effects are similar, which will not be described here.

[0274] Figure 9 A structure diagram of the terminal device provided by the embodiments of the present application is shown in FIG. 9. As shown in the figure, the terminal device can include a processor 91, a memory 92, a transceiver 93, and computer program instructions stored in the memory 92 and executable on the processor 91, and the processor 91 implements the terminal device triggering method provided by any of the preceding embodiments when executing the computer program instructions. Figure 9

[0275] Optionally, the above various devices of the terminal device can be connected through a system bus.

[0276] ​​The memory 92 can be a separate storage unit or a storage unit integrated in the processor. The number of processors is one or more.

[0277] Optionally, the terminal device can further include an interface for interacting with other devices.

[0278] The transceiver 93 is configured to communicate with other devices, and the transceiver 93 constitutes a communication interface.

[0279] Optionally, in hardware implementation, the above-mentioned Figure 7 In the embodiment shown, the sending module 71 and the receiving module 72 correspond to the transceiver 93 in the embodiment.

[0280] The terminal device provided by the embodiment of the present application can be used to execute the terminal device triggering method of the terminal device side provided by any one of the above-mentioned method embodiments, and the implementation principle and technical effects are similar, which will not be described here.

[0281] It should be understood that the processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the present application can be directly embodied as hardware processor execution, or executed by a combination of hardware and software modules in the processor.

[0282] The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, only one thick line is shown in the figure, but it does not mean that there is only one bus or only one type of bus. The memory can include a random access memory (RAM) and can also include a non-volatile memory (NVM), such as at least one disk memory.

[0283] All or a part of the steps of each of the above-mentioned method embodiments can be accomplished by program instruction-related hardware. The aforementioned program can be stored in a readable memory. The program, when executed, performs steps including each of the above-mentioned method embodiments; and the aforementioned memory (storage medium) includes a read-only memory (ROM), a RAM, a flash memory, a hard disk, a solid state disk, a magnetic tape, a floppy disk, an optical disc, and any combination thereof.

[0284] The embodiment of the present application provides a computer readable storage medium, and the computer readable storage medium stores computer execution instructions. When the computer execution instructions run on a computer, the computer execution instructions make the computer execute the triggering method of the terminal device.

[0285] The computer readable storage medium described above can be implemented by any type of volatile or nonvolatile storage device or a combination thereof, such as a static random access memory, an electrically erasable programmable read-only memory, an erasable programmable read-only memory, a programmable read-only memory, a read-only memory, a magnetic memory, a flash memory, a magnetic disk or an optical disk. The readable storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0286] Optionally, the readable storage medium is coupled to the processor, so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in the device.

[0287] The embodiment of the present application also provides a computer program product, and the computer program product includes a computer program stored in a computer readable storage medium. At least one processor can read the computer program from the computer readable storage medium, and the at least one processor executes the computer program to implement the triggering method of the terminal device.

[0288] It should be understood that the present application is not limited to the precise construction that has been described above and illustrated in the accompanying drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the application is limited only by the claims that follow.

Claims

1. A method for triggering a terminal device, characterized in that, The method applied to a UDM comprises: According to an identifier of a RedCap UE to be received, a corresponding RAT type and an extended idle state DRX cycle length are retrieved, the RAT type and the extended idle state DRX cycle length being obtained in a RedCap UE registration process; the identifier, the RAT type and the extended idle state DRX cycle length have a mapping relationship; According to the RAT type and the extended idle state DRX cycle length, a first validity of the trigger message is determined, the first validity being used to indicate whether the trigger message can be sent to the RedCap UE within a delay tolerance of the trigger message; When the trigger message is determined to be valid according to the first validity, a second validity of the trigger message is determined according to the extended idle state DRX cycle length and a validity duration of the trigger message, the second validity being used to predict whether the trigger message is successfully sent to the RedCap UE; When the trigger message is determined to be valid according to the second validity, an application trigger service process is executed according to the trigger message; the application trigger service process is used to deliver the trigger message to the RedCap UE; When the trigger message is determined to be invalid according to the second validity, a second prediction result is returned to an application function entity AF, the second prediction result comprising a second reason value, the second reason value being used to indicate a reason why the trigger message cannot be successfully sent to the RedCap UE, and the second reason value comprising the extended idle state DRX cycle length.

2. The method of claim 1, wherein, Before the identifier of the RedCap UE to be received is used to retrieve the corresponding RAT type and the extended idle state DRX cycle length, the method further comprises: A registration request sent by an authentication management function AMF is received, the registration request carrying a new radio NR RedCap indication, the NR RedCap indication being used to indicate a device type of the RedCap UE; The RedCap UE is registered according to the registration request; According to the NR RedCap indication, the RAT type of the RedCap UE is determined as NR RedCap; A notification sent by the AMF is received, and the extended idle state DRX cycle length of the RedCap UE carried by the notification is stored.

3. The method of claim 2, wherein, The first validity of the trigger message is determined according to the RAT type and the extended idle state DRX cycle length, comprising: According to the extended idle state DRX cycle length and a delay tolerance of the trigger message, it is determined whether the trigger message can be sent to the RedCap UE within the delay tolerance; If yes, it is confirmed that the first validity is valid; If not, it is confirmed that the first validity is invalid.

4. The method of claim 3, wherein, When the trigger message is determined to be invalid according to the first validity, the method further comprises: returning a first prediction result to an application function entity (AF) triggering the RedCap UE, the first prediction result including a first cause value indicating a reason for being unable to send the triggering message to the RedCap UE, and the first cause value including the extended idle state DRX cycle length.

5. The method according to claim 3 or 4, characterized in that, The determining of the RAT type of the RedCap UE as the NR RedCap according to the NR RedCap indication includes: The setting of a value of a UE RAT type field of the RedCap UE as the NR RedCap according to the NR RedCap indication.

6. The method of claim 5, wherein, The retrieving of the corresponding RAT type and the extended idle state DRX cycle length according to the identifier of the RedCap UE to be received with the triggering message includes: The parsing of a general public subscriber identifier (GPSI) of the RedCap UE to obtain the identifier; The retrieving of the RAT type and the extended idle state DRX cycle length of the RedCap UE according to the identifier.

7. A method for triggering of a terminal device, characterized in that The method applied to a terminal includes: In a radio resource control (RRC) connection establishment process initiated to a base station (gNB), a new radio (NR) lightweight (RedCap) indication is sent to the gNB, the NR RedCap indication being used to indicate a device type of a RedCap user equipment (UE); After the RRC connection is established with the gNB, a request is sent to the gNB, wherein the request is used to request registration of the RedCap UE and to request enabling of an extended idle state discontinuous reception (DRX) mechanism, so that the gNB interacts with a corresponding authentication management function (AMF) according to the request and the NR RedCap indication, registers the RedCap UE in a unified data management entity (UDM) through the AMF, and determines an extended idle state DRX cycle length of the RedCap UE, and the UDM is used to perform the method of any one of claims 1 to 6; Feedback information returned by the gNB is received, and the extended idle state DRX mechanism is enabled based on the feedback information, and the feedback information includes the extended idle state DRX cycle length.

8. The method of claim 7, wherein, The request includes a registration sub-request, a requested DRX parameter, and an extended idle state DRX parameter, wherein the registration sub-request is used to request registration of the RedCap UE, and the extended idle state DRX parameter includes the extended idle state DRX cycle length.

9. The method of claim 8, wherein, The feedback information further includes an accepted DRX parameter, the extended idle state DRX parameter, and a paging time window (PTW), and the accepted DRX parameter is determined according to the requested DRX parameter.

10. A terminal device trigger apparatus, characterized by comprising: The apparatus applied to a UDM includes: The retrieval module is configured to retrieve, according to an identifier of a lightweight RedCap user equipment (UE) to which a trigger message is to be received, a corresponding radio access technology (RAT) type and an extended idle state discontinuous reception (DRX) cycle length, wherein the RAT type and the extended idle state DRX cycle length are obtained in a RedCap UE registration process; and the identifier, the RAT type and the extended idle state DRX cycle length have a mapping relationship. The determination module is configured to determine, according to the RAT type and the extended idle state DRX cycle length, a first validity of the trigger message, wherein the first validity is used to indicate whether the trigger message can be sent to the RedCap UE within a delay tolerance of the trigger message; and when it is determined that the trigger message is valid according to the first validity, determine a second validity of the trigger message according to the extended idle state DRX cycle length and a valid time length of the trigger message, wherein the second validity is used to predict whether the trigger message is successfully sent to the RedCap UE. The execution module is configured to execute an application trigger service process according to the trigger message when it is determined that the trigger message is valid according to the second validity, wherein the application trigger service process is used to deliver the trigger message to the RedCap UE. The return module is configured to return a second prediction result to an application function (AF) when it is determined that the trigger message is invalid according to the second validity, wherein the second prediction result includes a second cause value, and the second cause value is used to indicate a cause for which the trigger message cannot be successfully sent to the RedCap UE, and the second cause value includes the extended idle state DRX cycle length.

11. A triggering apparatus of a terminal device, characterized by comprising: The device is applied to a terminal equipment and includes: A sending module is configured to send an NR RedCap indication to a base station (gNB) during initiation of a radio resource control (RRC) connection establishment process, wherein the NR RedCap indication is used to indicate a device type of a lightweight RedCap user equipment (UE). The sending module is further configured to send a request to the gNB after establishing an RRC connection with the gNB, wherein the request is used to request registration of the RedCap UE and enable an extended idle state discontinuous reception (DRX) mechanism, so that the gNB interacts with a corresponding authentication management function (AMF) according to the request and the NR RedCap indication, registers the RedCap UE in a unified data management entity (UDM) through the AMF, and determines an extended idle state DRX cycle length of the RedCap UE, wherein the UDM is configured to execute the method of any one of claims 1 to 6. A receiving module is configured to receive feedback information returned by the gNB, and enable the extended idle state DRX mechanism based on the feedback information, wherein the feedback information includes the extended idle state DRX cycle length.

12. A UDM, comprising: A processor, a memory and computer program instructions stored on the memory and executable on the processor, wherein the processor is configured to execute the computer program instructions to implement the trigger method of the terminal equipment according to any one of claims 1 to 6.

13. A terminal comprising: The transceiver, the processor, the memory, and computer program instructions stored on the memory and executable on the processor, wherein the processor, when executing the computer program instructions, is configured to implement the triggering method of the terminal device according to any one of claims 7 to 9.

14. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer execution instructions, and the computer execution instructions, when executed by the processor, are configured to implement the triggering method of the terminal device according to any one of claims 1 to 9.

15. A computer program product comprising a computer program, characterized in that, The computer program, when executed by the processor, is configured to implement the triggering method of the terminal device according to any one of claims 1 to 9.

Images