Trigger message processing method, device, equipment, medium and program product

Abstract

The present application provides a method, apparatus, device, medium and program product for processing a trigger message, the method comprising: the NF obtains the access and mobility user data of the RedCap UE, determines the validity of the trigger message according to the length of the extended idle state DRX cycle and the effective duration of the trigger message to be sent to the RedCap UE, and executes the application triggering service process according to the trigger message when the trigger message is valid. The validity is used to predict whether the trigger message can be successfully sent to the RedCap UE, execute the application triggering service process when the trigger message is determined to be valid, and stop executing the subsequent application triggering service process when the trigger message is determined to be invalid. The application triggering service process is used to deliver the trigger message to the RedCap UE, reducing invalid resource occupation and signaling overhead, and improving the processing efficiency and the success rate of trigger message sending.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, apparatus, device, medium, and program product for processing a trigger message. Background Art

[0002] The Protocol Data Unit (PDU) session establishment includes the PDU session establishment process initiated by the User Equipment (UE), the PDU session handover initiated by the UE from the Evolved Packet System (EPS) to the 5G System (5GS), and the PDU session establishment process triggered by the network. When the PDU session establishment process is triggered by the network, the Application Function (AF) on the network side needs to request the network to send a trigger message to the application on the UE side, so that the application on the UE side triggers the PDU session establishment process based on the above trigger message.

[0003] Currently, for energy conservation reasons, the 3rd Generation Partnership Project (3GPP) has specified that lightweight (RedCap) UEs can support extended discontinuous reception (eDRX) in idle and inactive states during network-triggered PDU session establishment. DRX stands for extended discontinuous reception (DRX). The DRX mechanism involves discontinuously receiving signals, allowing the UE to remain in a dormant state for most of the time, thereby saving power.

[0004] However, in the prior art, when the eDRX cycle exceeds the validity period (Validity Period) of the triggering message, there are problems such as failure to trigger the RedCap UE and invalid resource occupation and signaling overhead. Summary of the Invention

[0005] The present application provides a trigger message processing method, apparatus, device, medium and program product to solve the problems of failure in triggering RedCap UE, invalid resource occupation and signaling overhead in the prior art.

[0006] In a first aspect, an embodiment of the present application provides a method for processing a trigger message, including:

[0007] Obtaining access and mobility user data of a RedCap UE, where the access and mobility user data is used to indicate an extended idle state DRX cycle length configured for the RedCap UE;

[0008] Determining the validity of the trigger message according to the extended idle state DRX cycle length and the valid duration of the trigger message to be sent to the RedCap UE, where the validity is used to predict whether the trigger message can be successfully sent to the RedCap UE;

[0009] When the trigger message is valid, an application trigger service process is executed according to the trigger message, and the application trigger service process is used to deliver the trigger message to the RedCap UE.

[0010] In a possible design of the first aspect, judging the validity of the trigger message according to the extended idle state DRX cycle length and the valid duration of the trigger message to be sent to the RedCap UE includes:

[0011] If the valid duration is greater than the extended idle state DRX cycle length, determining that the trigger message is valid;

[0012] If the valid duration is less than or equal to the extended idle state DRX cycle length, it is determined that the trigger message is invalid.

[0013] Optionally, after determining the validity of the trigger message according to the extended idle DRX cycle length and the valid duration of the trigger message to be sent to the RedCap UE, the method further includes:

[0014] When the trigger message is invalid, a prediction result is output, where the prediction result includes a cause value, where the cause value is used to indicate a reason why the trigger message cannot be successfully sent to the RedCap UE.

[0015] Optionally, the cause value includes the extended idle state DRX cycle length.

[0016] In another possible design of the first aspect, obtaining access and mobility user data of the RedCap UE includes:

[0017] Determine, according to the UDM policy, the type of identifier used when triggering the RedCap UE to perform the PDU session establishment process;

[0018] The GPSI of the RedCap UE is parsed according to the identifier type to obtain the identifier.

[0019] Access and mobility subscription data of the RedCap UE is retrieved based on the identifier.

[0020] Optionally, obtaining access and mobility user data of the RedCap UE includes:

[0021] Before sending the trigger message to the RedCap UE, obtaining access and mobility user data of the RedCap UE according to the identifier;

[0022] or,

[0023] When the trigger message is not successfully delivered to the RedCap UE, access and mobility user data of the RedCap UE is acquired according to the identifier.

[0024] In yet another possible design of the first aspect, before obtaining access and mobility user data of the RedCap UE, the method further includes:

[0025] receiving a trigger request sent by an AF, where the trigger request is used to request that the trigger message be delivered to the RedCap UE;

[0026] It is determined whether the AF has the right to send the trigger message according to the trigger request, so as to obtain the access and mobility user data of the RedCap UE after determining that the AF has the right.

[0027] In a second aspect, an embodiment of the present application provides a trigger message processing device, including:

[0028] An acquisition module, configured to acquire access and mobility user data of a RedCap UE, wherein the access and mobility user data is used to indicate an extended idle state DRX cycle length configured for the RedCap UE;

[0029] a judgment module, configured to judge the validity of the trigger message according to the length of the extended idle state DRX cycle and the effective duration of the trigger message to be sent to the RedCap UE, wherein the validity is used to predict whether the trigger message can be successfully sent to the RedCap UE;

[0030] An execution module is configured to execute an application triggering service process according to the triggering message when the triggering message is valid, wherein the application triggering service process is configured to deliver the triggering message to the RedCap UE.

[0031] In a possible design of the second aspect, the judgment module is specifically configured to:

[0032] If the valid duration is greater than the extended idle state DRX cycle length, determining that the trigger message is valid;

[0033] If the valid duration is less than or equal to the extended idle state DRX cycle length, it is determined that the trigger message is invalid.

[0034] Optionally, after determining the validity of the trigger message according to the extended idle state DRX cycle length and the valid duration of the trigger message to be sent to the RedCap UE, the apparatus further includes:

[0035] The output module is used to output a prediction result when the trigger message is invalid, wherein the prediction result includes a cause value, and the cause value is used to indicate the reason why the trigger message cannot be successfully sent to the RedCap UE.

[0036] Optionally, the cause value includes the extended idle state DRX cycle length.

[0037] In another possible design of the second aspect, the acquisition module is specifically configured to:

[0038] Determine, according to the UDM policy, the type of identifier used when triggering the RedCap UE to perform the PDU session establishment process;

[0039] The GPSI of the RedCap UE is parsed according to the identifier type to obtain the identifier.

[0040] Access and mobility subscription data of the RedCap UE is retrieved based on the identifier.

[0041] Optionally, the acquisition module is specifically configured to:

[0042] Before sending the trigger message to the RedCap UE, obtaining access and mobility user data of the RedCap UE according to the identifier;

[0043] or,

[0044] When the trigger message is not successfully delivered to the RedCap UE, access and mobility user data of the RedCap UE is acquired according to the identifier.

[0045] In yet another possible design of the second aspect, before obtaining the access and mobility user data of the RedCap UE, the apparatus further includes:

[0046] A receiving module, configured to receive a trigger request sent by an AF, wherein the trigger request is used to request that the trigger message be delivered to the RedCap UE;

[0047] The judging module is configured to judge whether the AF has the right to send the trigger message according to the trigger request, so as to obtain the access and mobility user data of the RedCap UE after determining that the AF has the right.

[0048] In a third aspect, an embodiment of the present application provides a NF, comprising: a processor, a memory, and computer program instructions stored in the memory and executable on the processor, wherein the processor executes the computer program instructions to implement the methods provided in the first aspect and various possible designs.

[0049] In a fourth aspect, an embodiment of the present application may provide a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the first aspect and the methods provided by various possible designs.

[0050] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the first aspect and the methods provided by various possible designs.

[0051] The trigger message processing method, apparatus, device, medium and program product provided in the embodiments of the present application, NF obtains the access and mobility user data of RedCap UE, and judges the validity of the trigger message according to the length of the extended idle state DRX cycle and the effective duration of the trigger message to be sent to the RedCap UE, and executes the application trigger business process according to the trigger message when the trigger message is valid. The validity is used to predict whether the trigger message can be successfully sent to the RedCap UE. In this technical solution, the validity of the trigger message can be judged according to the length of the extended idle state DRX cycle and the effective duration of the trigger message, and the application trigger business process is executed when the trigger message is judged to be valid. When the trigger message is judged to be invalid, the subsequent application trigger business process is stopped. The application trigger business process is used to pass the trigger message to the RedCap UE, which reduces invalid resource occupation and signaling overhead, and improves the processing efficiency and the success rate of trigger message sending. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0053] Figure 1 A schematic diagram of the structure of a communication system provided in an embodiment of the present application;

[0054] Figure 2 A flowchart of a first embodiment of a method for processing a trigger message provided in an embodiment of the present application;

[0055] Figure 3 A flowchart of a second embodiment of a method for processing a trigger message provided in an embodiment of the present application;

[0056] Figure 4 A flowchart of a third embodiment of a method for processing a trigger message provided in an embodiment of the present application;

[0057] Figure 5 A schematic diagram of the structure of a trigger message processing device provided in an embodiment of the present application;

[0058] Figure 6 A schematic diagram of the structure of the NF provided in the embodiment of this application.

[0059] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0060] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

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

[0062] The DRX mechanism allows the UE to remain in a dormant state for most of the time, saving power by discontinuously receiving signals. Because packet-based data flows are typically bursty, power consumption can be reduced by shutting down the UE's receiving circuitry when no data is being transmitted.

[0063] eDRX: Extended DRX. 3GPP stipulates that only enhanced Machine Type Communication (eMTC) UEs can use the eDRX mechanism when they are in the Radio Resource Control (RRC) inactive state. Other UEs, such as Long Term Evolution (LTE) UEs or New Radio (NR) UEs, cannot use the eDRX mechanism when they are in the RRC Inactive state.

[0064] Next, the application background of this application is explained:

[0065] Currently, when the PDU session establishment process is triggered by the network, the network-side AF needs to call the Nnef_Trigger service to request that the network send a trigger message to the target application on the UE. The payload of this trigger message contains information indicating the target application on the UE that is expected to trigger the PDU session establishment request. After receiving the trigger message, the UE triggers the PDU session establishment process through the target application indicated by this information.

[0066] During the network-triggered PDU session establishment process, if the UE is a RedCap UE, it can support eDRX operations in idle and inactive states. For the idle state, the RedCap UE supports upper-layer configuration of terminal-specific eDRX cycles; for the inactive state, the RedCap UE supports RRC and upper-layer configuration of terminal-specific eDRX cycles. 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, the paging time window (PTW) mechanism is used to send paging messages.

[0067] However, the existing technology has the following problems:

[0068] (1) When the eDRX cycle exceeds the validity period of the trigger message, the RedCap UE can only receive downlink data within the set PTW. During the rest of the time outside the PTW, the RedCap UE is in a dormant state, resulting in a problem of failure to trigger the RedCap UE.

[0069] (2) Based on the above problem (1), if the triggering of RedCap UE fails and the validity period of the triggering message is not set to 0, the network side will add the message to the waiting list and try to redeliver the trigger message later, which will cause invalid resource occupation and signaling overhead.

[0070] The embodiments of the present application address the problems of failure to trigger RedCap UE, invalid resource occupancy, and signaling overhead in the prior art, and provide a method for processing a trigger message. The method can obtain the extended idle state DRX cycle length of the RedCap UE to receive the trigger message, and judge the validity of the trigger message based on the extended idle state DRX cycle length. The validity is used to predict whether the trigger message can be successfully sent to the RedCap UE. When the trigger message is determined to be valid, the application triggering service process is executed. When the trigger message is determined to be invalid, the subsequent application triggering service process is stopped. The application triggering service process is used to deliver the trigger message to the RedCap UE, thereby reducing invalid resource occupancy and signaling overhead and improving processing efficiency.

[0071] For example, the trigger message processing method provided in the embodiment of the present application can be applied to a communication system. Figure 1 This is a schematic diagram of the structure of a communication system provided in an embodiment of the present application. Figure 1 As shown, the communication system may include: a first network function (NF) 11, a second NF 12, a third NF 13, and a RedCap UE 14. The first NF 11 may be wirelessly connected to the second NF 12, the second NF 12 may be respectively connected to the first NF 11 and the third NF 13, and the third NF 13 may be respectively connected to the second NF 12 and the RedCap UE 14.

[0072] In an embodiment of the present application, when the first NF 11 confirms that it needs to trigger the RedCap UE 14 to execute the PDU session establishment process, it may send a trigger request carrying a trigger message to the second NF 12. The first NF 11 may pre-store the contact information of the second NF 12 so as to communicate and interact with the second NF 12 using the contact information. Alternatively, the first NF 11 may perform NF discovery and selection services to determine the contact information of the second NF 12 from an NF contact information list so as to communicate and interact with the second NF 12.

[0073] After receiving the trigger request sent by the first NF11, the second NF12 determines the validity of the trigger message according to the extended idle DRX cycle length of the RedCap UE14 and the valid duration of the trigger message, so that when the trigger message is determined to be valid, the application trigger service process is executed through the third NF13, and when the trigger message is determined to be invalid, the subsequent application trigger service process is stopped.

[0074] Optionally, the logical functions of the first NF11 can be integrated into the AF; the logical functions of the second NF12 can be integrated into the Unified Data Management (UDM) or the Network Exposure Function (NEF), or part of the logical functions can be integrated into the UDM and part of the logical functions into the NEF; the logical functions of the third NF13 can be integrated into the Short Message Service-Service Center (SMS-SC). It should be understood that the above physical device types used to integrate the logical functions of each NF (i.e., the above-mentioned AF, UDM, NEF, and SMS-SC) are only examples, and the embodiments of this application do not limit the above-mentioned physical device types.

[0075] It is understandable that Figure 1 This is just a schematic diagram of a communication system. The communication system may also include other network devices, such as core network devices, wireless relay devices, and wireless backhaul devices, and may also include other NFs. The embodiments of the present application do not impose specific restrictions on this.

[0076] The system architecture and business scenarios described in the embodiments of the present application are intended 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 in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0077] The technical solution of the present application is described in detail below through specific embodiments.

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

[0079] Figure 2 Schematic diagram of the process of trigger message processing embodiment 1 provided in the present application. Figure 2 As shown, the method for processing the trigger message may include the following steps:

[0080] S201. Obtain access and mobility user data of RedCap UE.

[0081] The execution subject of the embodiment of the present application is NF, which can be NEF, AF, or UDM, and there is no specific limitation on this.

[0082] The access and mobility user data is used to indicate the extended idle state DRX cycle length configured for the RedCap UE.

[0083] Optionally, the access and mobility user data of the RedCap UE may be determined according to the GPSI of the RedCap UE, wherein the GPSI of the RedCap UE may be obtained through a trigger message.

[0084] In the application scenario where the NF is an NEF, the NEF can send an information acquisition request to the UDM to obtain the access and mobility user data of the RedCap UE. After receiving the information acquisition request, the UDM determines the access and mobility user data of the RedCap UE based on the GPSI of the RedCap UE and returns it. The NEF then receives the access and mobility user data of the RedCap UE from the UDM.

[0085] Optionally, the above information acquisition request may be implemented through Nudm_SDM_Get, and the UDM may return the access and mobility user data of the RedCap UE to the NEF through Nudm_SDM_Get.

[0086] S202: Determine the validity of the trigger message according to the extended idle-state DRX cycle length and the valid duration of the trigger message to be sent to the RedCap UE.

[0087] The validity of the trigger message is used to predict whether the trigger message can be successfully sent to the RedCap UE. In other words, if the trigger message is valid, it is predicted that the trigger message can be successfully delivered to the RedCap UE, and if the trigger message is invalid, it is predicted that the trigger message cannot be successfully delivered to the RedCap UE.

[0088] The trigger message is used to trigger the RedCap UE to execute the PDU session establishment process.

[0089] S203: When the trigger message is valid, execute the application triggering business process according to the trigger message.

[0090] The application triggering service process is used to transmit the triggering message to the RedCap UE.

[0091] Optionally, when the trigger message is invalid, the subsequent application triggering business process is not executed.

[0092] Optionally, the application triggering business process may include the following steps:

[0093] The SMSF identifier of the RedCap UE and the target SMS-SC are determined, and a trigger message is sent to the target SMS-SC. Upon receiving the trigger message, the SMS-SC executes the Mobile Terminated (MT) Short Message Service (SMS) delivery process to deliver the trigger message to the RedCap UE. The trigger message may include the RedCap UE's GPSI, a trigger reference number, validity period, priority, SMSF identifier, SMS application port ID, trigger payload, and trigger indication.

[0094] The trigger message processing method provided in the embodiment of the present application is that the NF obtains the access and mobility user data of the RedCap UE, and judges the validity of the trigger message according to the extended idle state DRX cycle length and the effective duration of the trigger message to be sent to the RedCap UE, and executes the application trigger service process according to the trigger message when the trigger message is valid. In this technical solution, the validity of the trigger message can be judged according to the extended idle state DRX cycle length and the effective duration of the trigger message, and the application trigger service process is executed when the trigger message is judged to be valid. When the trigger message is judged to be 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, and when the trigger message is invalid, subsequent redundant processing is reduced, thereby reducing invalid resource occupation and signaling overhead, and improving processing efficiency and the success rate of trigger message sending.

[0095] Optionally, in some embodiments, combined Figure 2 In the embodiment shown, S202 may be implemented by the following steps:

[0096] If the valid duration is greater than the extended idle state DRX cycle length, the trigger message is determined to be valid; if the valid duration is less than or equal to the extended idle state DRX cycle length, the trigger message is determined to be invalid.

[0097] Optionally, when the valid duration is not set to 0 and the valid duration is less than or equal to the extended idle state DRX cycle length, the trigger message is determined to be invalid; otherwise, the trigger message is determined to be valid.

[0098] Since the sending result of the trigger message (successful sending or failed sending) is closely related to the effective duration and the length of the extended idle state DRX cycle, in this embodiment, whether the trigger message can be successfully sent to the RedCap UE is predicted in advance based on the effective duration and the length of the extended idle state DRX cycle, so as to decide whether to send and process the trigger message subsequently, thereby improving the success rate of trigger message sending.

[0099] Optionally, in some embodiments, combined Figure 2 In the embodiment shown, after S202, the trigger message processing method may further include the following steps:

[0100] When the trigger message is invalid, a prediction result is output, where the prediction result includes a cause value, where the cause value is used to indicate the reason why the trigger message cannot be successfully sent to the RedCap UE.

[0101] Optionally, the cause value includes an extended idle state DRX cycle length.

[0102] Optionally, outputting the prediction result may be implemented by sending the prediction result to the AF that generates the trigger message, wherein the prediction result may be fed back to the AF via Nnef_Trigger_Delivery.

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

[0104] Discard the trigger message, adjust the validity period of the trigger message, and adjust the sending time of the trigger message.

[0105] Optionally, in some embodiments, combined Figure 2 In the embodiment shown, S201 may be implemented by the following steps:

[0106] According to the UDM policy, determine the type of identifier used to trigger the RedCap UE to perform the PDU session establishment process. Then, parse the GPSI of the RedCap UE according to the identifier type to obtain the identifier. Finally, retrieve the access and mobility user data of the RedCap UE based on the identifier.

[0107] Optionally, the type of the identifier may be a Subscription Permanent Identifier (SUPI) or a Mobile Station International ISDN Number (MSISDN).

[0108] Optionally, in some embodiments, combined Figure 2 In the embodiment shown, S201 may be implemented by the following steps:

[0109] Before sending a trigger message to the RedCap UE, the access and mobility user data of the RedCap UE is obtained according to the identifier.

[0110] or,

[0111] When the trigger message is not successfully delivered to the RedCap UE, the access and mobility user data of the RedCap UE is obtained according to the identifier.

[0112] In the above embodiment, obtaining the RedCap UE's access and mobility user data and determining the validity of the trigger message before sending a trigger message to the RedCap UE can reduce subsequent redundant processing when the trigger message is invalid, greatly saving processing resources and improving processing efficiency. However, obtaining the RedCap UE's access and mobility user data and determining the validity of the trigger message when the trigger message is not successfully delivered to the RedCap UE requires less modification to the existing trigger message sending process and is easier to implement through modification of the existing trigger message sending process.

[0113] Optionally, in some embodiments, combined Figure 2 In the embodiment shown, before S201, the trigger message processing method may further include the following steps:

[0114] Receive a trigger request from the AF and determine whether the AF is authorized to send a trigger message based on the trigger request, so as to obtain the access and mobility user data of the RedCap UE after determining that the AF is authorized. The trigger request is used to request that the trigger message be delivered to the RedCap UE;

[0115] Optionally, determining whether the AF has the right to send a trigger message may include the following aspects: whether the AF has the authority to send a trigger 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.

[0116] In combination with the trigger message processing method in each of the above embodiments, the method is illustrated below through two specific examples.

[0117] Example 1: Before sending the trigger message to the RedCap UE, the validity of the trigger message is determined.

[0118] Figure 3 A flowchart of Example 2 of the method for processing trigger messages provided in an embodiment of the present application.

[0119] S301. When confirming that the RedCap UE needs to be triggered to execute the PDU session establishment process, the AF determines the contact information of the NEF.

[0120] The contact information may be pre-stored by the AF, or may be determined from the NEF contact information list by performing discovery and selection services of the NEF.

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

[0122] S302: The AF sends a trigger request to the NEF according to the contact information of the NEF.

[0123] Optionally, the trigger request carries a trigger message, which is used to request that the trigger message be delivered to the RedCap UE.

[0124] Optionally, this step can be implemented by calling Nnef_Trigger_Delivery.

[0125] Correspondingly, for the NEF, it receives the trigger request sent by the AF.

[0126] S303: The NEF determines whether the AF has the right to send a trigger message according to the trigger request.

[0127] S304: When it is determined that the AF has the authority, the NEF sends an information acquisition request to the UDM.

[0128] The information acquisition request is used to obtain access and mobility user data of the RedCap UE.

[0129] Optionally, this step can be implemented by calling Nudm_SDM_Get.

[0130] Correspondingly, for the UDM, it receives the information acquisition request sent by the NEF.

[0131] S305. The UDM returns the identifier of the RedCap UE and access and mobility user data to the NEF according to the information acquisition request.

[0132] Among them, according to the UDM policy, the type of identifier used when triggering the RedCap UE to execute the PDU session establishment process is determined, the GPSI of the RedCap UE is parsed according to the identifier type to obtain the identifier, the access and mobility user data of the RedCap UE is retrieved according to the identifier, and the access and mobility user data and identifier are returned to the NEF.

[0133] Optionally, the access and mobility user data includes a field "IDLE STATE DRX CYCLE LENGTH" for indicating an extended IDLE STATE DRX CYCLE LENGTH configured for the RedCap UE.

[0134] Optionally, this step may return the access and mobility user data and identifier to the NEF via a Nudm_SDM_Get response.

[0135] Optionally, the UDM may also call the Nudr_DM_Query service to retrieve the AF list that is allowed to trigger the UE.

[0136] Correspondingly, NEF receives the access and mobility user data and identifier returned by UDM.

[0137] S306: If the valid duration of the trigger message is not set to zero and the valid duration is less than or equal to the extended idle state DRX cycle length configured for the RedCap UE, the NEF feeds back the prediction result to the AF.

[0138] The prediction result includes a cause value, and the cause value is used to indicate the reason why the trigger message cannot be successfully sent to the RedCap UE.

[0139] Optionally, the cause value includes an extended idle state DRX cycle length.

[0140] Optionally, the NEF may feed back the prediction result to the AF through the Nnef_Trigger_Delivery response.

[0141] It should be understood that after the prediction result is fed back to the AF, the other steps are stopped. That is, the following S307 to S315 are steps executed when the effective duration of the trigger message is greater than the extended idle DRX cycle length configured by the RedCap UE.

[0142] S307: If the effective duration of the trigger message is greater than the extended idle DRX cycle length configured for the RedCap UE, the NEF sends an SMSF identity acquisition request to the UDM.

[0143] Optionally, NEF can cache the service node information of RedCap UE. However, when the cached service node information expires, the possibility of triggering message delivery failure increases.

[0144] The SMSF identity acquisition request is used to obtain the SMSF identity of the RedCap UE.

[0145] Optionally, this step can be implemented by calling Nudm_UECM_Get.

[0146] Correspondingly, for UDM, an SMSF identification acquisition request is received.

[0147] S308. The UDM retrieves the SMSF identity of the RedCap UE according to the SMSF identity acquisition request, and returns the retrieved SMSF identity of the RedCap UE to the NEF.

[0148] Optionally, Nudr_DM_Query may be called to retrieve the SMSF identity of the RedCap UE, and the retrieved SMSF identity of the RedCap UE may be returned to the NEF via a Nudm_UECM_Get response.

[0149] Correspondingly, for NEF, the SMSF identifier of the RedCap UE is received.

[0150] S309. The NEF selects a suitable SMS-SC based on the configuration information and sends a trigger message to the SMS-SC.

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

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

[0153] Correspondingly, for SMS-SC, a trigger message is received.

[0154] S310. SMS-SC sends a trigger submission confirmation message to NEF.

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

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

[0157] The message waiting list includes the addresses of the SMS-SCs waiting to send the trigger message again.

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

[0159] S311. NEF forwards the trigger submission confirmation message to AF.

[0160] Optionally, this can be achieved via the Nnef_Trigger_Delivery response.

[0161] Correspondingly, AF receives a trigger submission confirmation message.

[0162] S312. SMS-SC executes the MT SMS transmission process.

[0163] Optionally, the SMS-SC may provide the SMSF identifier to the Short Message Service-Gateway MSC (SMS-GMSC) to avoid UDM query.

[0164] Optionally, the SMS-SC may store the payload of the trigger message instead of the SMSF identity, and if the trigger message fails to be delivered and is attempted again, a UDM query will be performed.

[0165] If the trigger message delivery fails and the validity period 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.

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

[0167] S313. SMS-SC sends a message delivery report to NEF.

[0168] The message delivery report is used to indicate whether the trigger message delivery fails, the trigger message delivery succeeds, or is unknown. Unknown indicates that it is impossible to determine whether the trigger message is successfully delivered to the RedCap UE.

[0169] Optionally, when the triggered message delivery fails, the message delivery report may further include the reason for the failure.

[0170] Optionally, the failure reason may be that the validity period of the trigger message has expired.

[0171] Correspondingly, for NEF, a message delivery report is received.

[0172] S314. The NEF sends a message delivery report to the AF.

[0173] Optionally, this can be achieved through the Nnef_Trigger_DeliveryNotify message.

[0174] Correspondingly, for AF, a message delivery report is received.

[0175] S315. When the trigger message is successfully delivered, the RedCap UE takes a specific action to respond to the trigger message according to the payload of the trigger message.

[0176] The specific action includes initiating communication with the AF immediately or at a later time.

[0177] Example 2: determining the validity of the trigger message when the trigger message is not successfully delivered to the RedCap UE.

[0178] Figure 4 A flowchart of Example 3 of the method for processing trigger messages provided in an embodiment of the present application.

[0179] S401. When confirming that the RedCap UE needs to be triggered to execute the PDU session establishment process, the AF determines the contact information of the NEF.

[0180] It should be understood that the implementation principle of this step can refer to S301 and will not be repeated here.

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

[0182] S402: The AF sends a trigger request to the NEF according to the contact information of the NEF.

[0183] It should be understood that the implementation principle of this step can refer to S302 and will not be repeated here.

[0184] Correspondingly, for the NEF, it receives the trigger request sent by the AF.

[0185] S403: The NEF determines whether the AF has the right to send a trigger message according to the trigger request.

[0186] It should be understood that the implementation principle of this step can refer to S303 and will not be repeated here.

[0187] S404: When it is determined that the AF has the right, the NEF sends an identifier acquisition request to the UDM.

[0188] The identifier acquisition request is used to obtain the identifier of the RedCap UE.

[0189] Correspondingly, for the UDM, it receives the identifier acquisition request sent by the NEF.

[0190] S405. The UDM returns the identifier of the RedCap UE to the NEF according to the identifier acquisition request.

[0191] According to the UDM policy, the type of identifier used when triggering the RedCap UE to execute the PDU session establishment process is determined, and the GPSI of the RedCap UE is parsed according to the identifier type to obtain the identifier.

[0192] Correspondingly, for NEF, it receives the identifier returned by UDM.

[0193] S406. The NEF sends an SMSF identity acquisition request to the UDM.

[0194] It should be understood that the implementation principle of this step can refer to S307 and will not be repeated here.

[0195] Correspondingly, for UDM, an SMSF identification acquisition request is received.

[0196] S407. The UDM retrieves the SMSF identity of the RedCap UE according to the SMSF identity acquisition request, and returns the retrieved SMSF identity of the RedCap UE to the NEF.

[0197] It should be understood that the implementation principle of this step can refer to S308 and will not be repeated here.

[0198] Correspondingly, for NEF, the SMSF identifier of the RedCap UE is received.

[0199] S408. The NEF selects a suitable SMS-SC based on the configuration information and sends a trigger message to the SMS-SC.

[0200] It should be understood that the implementation principle of this step can refer to S309 and will not be repeated here.

[0201] Correspondingly, for SMS-SC, a trigger message is received.

[0202] S409. SMS-SC sends a trigger submission confirmation message to NEF.

[0203] It should be understood that the implementation principle of this step can refer to S310 and will not be repeated here.

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

[0205] S410. The NEF forwards the trigger submission confirmation message to the AF.

[0206] It should be understood that the implementation principle of this step can refer to S311 and will not be repeated here.

[0207] Correspondingly, AF receives a trigger submission confirmation message.

[0208] S411. SMS-SC executes the MT SMS transmission process.

[0209] Optionally, the SMS-SC may provide the SMSF identifier to the Short Message Service-Gateway MSC (SMS-GMSC) to avoid UDM query.

[0210] Optionally, the SMS-SC may store the payload of the trigger message instead of the SMSF identity, and if the trigger message fails to be delivered and is attempted again, a UDM query will be performed.

[0211] If the trigger message delivery fails and the validity period 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.

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

[0213] In addition, the UDM can also obtain the access and mobility user data of the RedCap UE and, when the effective duration of the trigger message is not set to zero and is less than or equal to the extended idle DRX cycle length configured for the RedCap UE, feedback the prediction result to the AF and execute step S413. The specific principles can be referred to S304 to S306 and will not be repeated here.

[0214] S412. SMS-SC sends a message delivery report to NEF.

[0215] It should be understood that the implementation principle of this step can refer to S313 and will not be repeated here.

[0216] Correspondingly, for NEF, a message delivery report is received.

[0217] S413. The NEF sends a message delivery report to the AF.

[0218] It should be understood that the implementation principle of this step can refer to S314 and will not be repeated here.

[0219] Correspondingly, for AF, a message delivery report is received.

[0220] S414: When the trigger message is successfully delivered, the RedCap UE takes specific actions in response to the trigger message according to the payload of the trigger message.

[0221] It should be understood that the implementation principle of this step can refer to S315 and will not be repeated here.

[0222] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0223] Figure 5 This is a schematic diagram of the structure of the trigger message processing device provided in the embodiment of the present application. Figure 5 As shown, the trigger message processing device includes:

[0224] An acquisition module 51 is configured to acquire access and mobility user data of a RedCap UE, where the access and mobility user data is used to indicate an extended idle state DRX cycle length configured for the RedCap UE;

[0225] The judging module 52 is configured to judge the validity of the trigger message according to the length of the extended idle state DRX cycle and the effective duration of the trigger message to be sent to the RedCap UE, where the validity is used to predict whether the trigger message can be successfully sent to the RedCap UE;

[0226] The execution module 53 is configured to execute an application triggering service process according to the triggering message when the triggering message is valid. The application triggering service process is configured to transmit the triggering message to the RedCap UE.

[0227] In a possible design of an embodiment of the present application, the judgment module 52 is specifically configured to:

[0228] If the valid duration is greater than the extended idle state DRX cycle length, the trigger message is determined to be valid;

[0229] If the valid duration is less than or equal to the extended idle state DRX cycle length, it is determined that the trigger message is invalid.

[0230] Optionally, after determining the validity of the trigger message according to the extended idle state DRX cycle length and the valid duration of the trigger message to be sent to the RedCap UE, the apparatus further includes:

[0231] The output module is used to output a prediction result when the trigger message is invalid. The prediction result includes a reason value, which is used to indicate the reason why the trigger message cannot be successfully sent to the RedCap UE.

[0232] Optionally, the cause value includes an extended idle state DRX cycle length.

[0233] In another possible design of the embodiment of the present application, the acquisition module 51 is specifically configured to:

[0234] Determine the type of identifier used to trigger the RedCap UE to perform the PDU session establishment process based on the UDM policy;

[0235] Parse the GPSI of the RedCap UE according to the identifier type to obtain the identifier.

[0236] Retrieve the access and mobility subscription data of the RedCap UE based on the identifier.

[0237] Optionally, the acquisition module 51 is specifically configured to:

[0238] Before sending a trigger message to the RedCap UE, obtain the access and mobility user data of the RedCap UE based on the identifier;

[0239] or,

[0240] When the trigger message is not successfully delivered to the RedCap UE, the access and mobility user data of the RedCap UE is obtained according to the identifier.

[0241] In another possible design of the embodiment of the present application, before obtaining the access and mobility user data of the RedCap UE, the apparatus further includes:

[0242] A receiving module is used to receive a trigger request sent by the AF, where the trigger request is used to request that a trigger message be delivered to the RedCap UE;

[0243] The judging module 52 is configured to judge whether the AF has the right to send a trigger message according to the trigger request, so as to obtain the access and mobility user data of the RedCap UE after determining that the AF has the right.

[0244] The trigger message processing device provided in the embodiment of the present application can be used to execute the trigger message processing method in any of the above embodiments. Its implementation principle and technical effects are similar and will not be repeated here.

[0245] It should be noted that it should be understood that the division of the various modules of the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, these modules can all be implemented in the form of software called by processing elements; they can also all be implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. In addition, these modules can be fully or partially integrated together or implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by the hardware integrated logic circuit in the processor element or by instructions in the form of software.

[0246] Figure 6 This is a schematic diagram of the structure of the NF provided in the embodiment of this application. Figure 6 As shown, the NF may include: a processor 61, a memory 62, and computer program instructions stored in the memory 62 and executable on the processor 61. When the processor 61 executes the computer program instructions, the trigger message processing method provided in any of the aforementioned embodiments is implemented.

[0247] Optionally, the above-mentioned components of the NF may be connected via a system bus.

[0248] The memory 62 may be a separate storage unit or a storage unit integrated in the processor. The number of processors may be one or more.

[0249] Optionally, the NF may also include interfaces for interacting with other devices.

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

[0251] The system bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. System buses can be divided into address buses, data buses, and control buses. For ease of illustration, the diagram uses only a single thick line, but this does not imply a single bus or type of bus. Memory may include random access memory (RAM) and non-volatile memory (NVM), such as at least one disk drive.

[0252] All or part of the steps of the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, it performs the steps of the above-mentioned method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disc, and any combination thereof.

[0253] The NF provided in the embodiment of the present application can be used to execute the trigger message processing method provided in any of the above method embodiments. Its implementation principle and technical effects are similar and will not be repeated here.

[0254] An embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed on a computer, the computer executes the above-mentioned method for processing a trigger message.

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

[0256] Optionally, a readable storage medium is coupled to a 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 an integral part 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 in the device as discrete components.

[0257] An embodiment of the present application also provides a computer program product, which 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 can implement the above-mentioned trigger message processing method when executing the computer program.

[0258] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for processing a trigger message, characterized in that: include: Acquire access and mobility user data of a lightweight RedCap user equipment UE, where the access and mobility user data is used to indicate an idle state extended discontinuous reception (DRX) cycle length configured for the RedCap UE; If the effective duration of the trigger message to be sent to the RedCap UE is greater than the extended idle state DRX cycle length, determining that the trigger message is valid; If the trigger message to be sent to the RedCap UE is not set to zero and the valid duration of the trigger message is less than or equal to the extended idle state DRX cycle length, determining that the trigger message is invalid; When the trigger message is valid, executing an application trigger service process according to the trigger message, wherein the application trigger service process is used to deliver the trigger message to the RedCap UE; When the trigger message is invalid, a prediction result is output, where the prediction result includes a cause value, where the cause value is used to indicate a reason why the trigger message cannot be successfully sent to the RedCap UE.

2. The method according to claim 1, characterized in that The cause value includes the extended idle state DRX cycle length.

3. The method according to any one of claims 1 and 2, characterized in that The obtaining of RedCap UE access and mobility user data includes: Determine, according to the unified data management entity UDM policy, the type of identifier used when triggering the RedCap UE to perform the protocol data unit PDU session establishment process; Parsing the universal public user identifier (GPSI) of the RedCap UE according to the identifier type to obtain the identifier; Access and mobility subscription data of the RedCap UE is retrieved based on the identifier.

4. The method according to claim 3, characterized in that The obtaining of RedCap UE access and mobility user data includes: Before sending the trigger message to the RedCap UE, obtaining access and mobility user data of the RedCap UE according to the identifier; or, When the trigger message is not successfully delivered to the RedCap UE, access and mobility user data of the RedCap UE is acquired according to the identifier.

5. The method according to any one of claims 1 and 2, characterized in that Before obtaining the access and mobility user data of the RedCap UE, the method further includes: receiving a trigger request sent by an application function entity AF, where the trigger request is used to request that the trigger message be delivered to the RedCap UE; It is determined whether the AF has the right to send the trigger message according to the trigger request, so as to obtain the access and mobility user data of the RedCap UE after determining that the AF has the right.

6. A trigger message processing device, characterized in that: include: An acquisition module is used to obtain access and mobility user data of a lightweight RedCap user equipment UE, where the access and mobility user data is used to indicate an idle state extended discontinuous reception (DRX) cycle length configured for the RedCap UE; a judgment module, configured to judge the validity of the trigger message according to the length of the extended idle state DRX cycle and the effective duration of the trigger message to be sent to the RedCap UE, wherein the validity is used to predict whether the trigger message can be successfully sent to the RedCap UE; An execution module, configured to execute an application triggering service process according to the triggering message when the triggering message is valid, wherein the application triggering service process is configured to deliver the triggering message to the RedCap UE; The judgment module is further used for: If the valid duration is greater than the extended idle state DRX cycle length, the trigger message is determined to be valid; if the valid duration is less than or equal to the extended idle state DRX cycle length, the trigger message is determined to be invalid; The execution module is further configured to: When the trigger message is invalid, a prediction result is output, where the prediction result includes a cause value, where the cause value is used to indicate a reason why the trigger message cannot be successfully sent to the RedCap UE, and the cause value includes the extended idle state DRX cycle length.

7. A NF comprising: A processor, a memory, and computer program instructions stored in the memory and executable on the processor, wherein the processor is used to implement the trigger message processing method according to any one of claims 1 to 5 when executing the computer program instructions.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the trigger message processing method according to any one of claims 1 to 7.

9. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, it is used to implement the trigger message processing method according to any one of claims 1 to 7.

Images