Notification method and apparatus, terminal, and network side device

Abstract

The present application relates to the technical field of communications, and discloses a notification method and apparatus, a terminal, and a network side device. The notification method of the embodiments of the present application comprises: an IMS device receives an SIP invitation message, wherein the IMS device serves a first terminal, and the SIP invitation message carries the identifier of a second terminal; and on the basis of the SIP invitation message, the IMS device sends first information to a core network device, wherein the first information comprises at least one of the following: the identifier of the second terminal, the identifier of the second terminal being used for determining whether to use a first notification mode to notify the first terminal; and first indication information, the first indication information being used for indicating the use of or permitted use of the first notification mode to notify the first terminal.

Description

Notification method, apparatus, terminal and network side device

[0001] Cross-reference to Related Applications

[0002] The present application claims priority to the Chinese patent application No. 202410880653.7, filed on July 02, 2024, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application belongs to the field of communication technology, and particularly relates to a notification method, apparatus, terminal and network side device. BACKGROUND

[0004] At present, in the related art, in order to ensure that the terminal can receive the notification in time, the network can directly send the notification to the terminal by using the paging early warning (which can also be referred to as enhanced paging notification or flexible notification) notification mode.

[0005] However, when there is a service that needs to notify the terminal, the network will directly send the notification to the terminal by using the above paging early warning notification mode, thereby causing poor flexibility of the notification. SUMMARY

[0006] The embodiments of the present application provide a notification method, apparatus, terminal and network side device, which can improve the flexibility of the notification.

[0007] In a first aspect, a notification method is provided, which is executed by an Internet Protocol Multimedia Subsystem (IMS) device, and the method comprises: receiving, by the IMS device, a Session initialization Protocol (SIP) invitation message, the IMS device serving a first terminal, and the SIP invitation message carrying an identifier of a second terminal; and sending, by the IMS device, first information to a core network device based on the SIP invitation message, wherein the first information comprises at least one of the following: the identifier of the second terminal, the identifier of the second terminal being used to determine whether to use a first notification mode to notify the first terminal; and first indication information, the first indication information being used to indicate that the first notification mode is used or allowed to be used to notify the first terminal.

[0008] In a second aspect, a notification method is provided, which is performed by a core network device. The method comprises: receiving, by the core network device, first information sent by an IMS device, wherein the IMS device serves a first terminal, and the first information comprises at least one of the following: an identifier of a second terminal, the identifier of the second terminal being used to determine whether the first notification mode is used to notify the first terminal; and first indication information, the first indication information being used to indicate that the first notification mode is used or allowed to notify the first terminal; wherein the first notification mode is a notification mode used or started in a case where the second notification mode fails to notify the terminal.

[0009] In a third aspect, a notification method is provided, which is performed by a terminal. The method comprises: sending, by the first terminal, identifiers of at least one third terminal to a network side device; wherein a session initiated by each third terminal with the first terminal allows the first notification mode to be used, and the network side device comprises at least one of an IMS device and a core network device.

[0010] In a fourth aspect, a notification apparatus is provided, which is applied to an IMS device. The apparatus comprises: a first receiving module and a first sending module; the first receiving module is configured to receive a SIP invitation message, the IMS device serves a first terminal, and the SIP invitation message carries an identifier of a second terminal; and the first sending module is configured to send, based on the SIP invitation message, first information to a core network device; wherein the first information comprises at least one of the following: the identifier of the second terminal, the identifier of the second terminal being used to determine whether the first notification mode is used to notify the first terminal; and first indication information, the first indication information being used to indicate that the first notification mode is used or allowed to notify the first terminal.

[0011] In a fifth aspect, a notification apparatus is provided. The apparatus comprises a second sending module; and the second sending module is configured to receive first information sent by an IMS device, wherein the IMS device serves a first terminal, and the first information comprises at least one of the following: an identifier of a second terminal, the identifier of the second terminal being used to determine whether the first notification mode is used to notify the first terminal; and first indication information, the first indication information being used to indicate that the first notification mode is used or allowed to notify the first terminal; wherein the first notification mode is a notification mode used or started in a case where the second notification mode fails to notify the terminal.

[0012] In a sixth aspect, a notification apparatus is provided. The apparatus comprises a third sending module; and the third sending module is configured to send, to a network side device, identifiers of at least one third terminal; wherein a session initiated by each third terminal with a first terminal allows the first notification mode to be used, and the network side device comprises at least one of an IMS device and a core network device.

[0013] In a seventh aspect, a notification apparatus is provided, which is configured to perform the steps of the method of the first aspect, or implement the steps of the method of the second aspect, or implement the steps of the method of the third aspect.

[0014] In an eighth aspect, a terminal is provided, which comprises a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the method of the third aspect.

[0015] In a ninth aspect, a terminal is provided, which comprises a processor and a communication interface, wherein the communication interface is configured to send an identity of at least one third terminal to a network-side device; wherein a session initiated by each third terminal with the first terminal allows use of a first notification mode, and the network-side device comprises at least one of an IMS device and a core network device.

[0016] In a tenth aspect, a network-side device is provided, which comprises a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the method of the first aspect, or implement the steps of the method of the second aspect.

[0017] In an eleventh aspect, a network-side device is provided, which comprises a processor and a communication interface, wherein the communication interface is configured to receive a SIP INVITE message, the IMS device serving the first terminal, the SIP INVITE message carrying an identity of the second terminal; and send first information to the core network device based on the SIP INVITE message; wherein the first information comprises at least one of the following: the identity of the second terminal, the identity of the second terminal being used to determine whether to notify the first terminal using the first notification mode; first indication information, the first indication information being used to indicate that the first notification mode is used or allowed to notify the first terminal. Alternatively, the communication interface is configured to receive first information sent by the IMS device, wherein the IMS device serves the first terminal, and the first information comprises at least one of the following: the identity of the second terminal, the identity of the second terminal being used to determine whether to notify the first terminal using the first notification mode; first indication information, the first indication information being used to indicate that the first notification mode is used or allowed to notify the first terminal; wherein the first notification mode is a notification mode used or started in a case where the second notification mode fails to notify the terminal.

[0018] In a twelfth aspect, a readable storage medium is provided, which stores programs or instructions, the programs or instructions being executed by a processor to implement the steps of the method of the first aspect, or implement the steps of the method of the second aspect, or implement the steps of the method of the third aspect.

[0019] In a thirteenth aspect, a wireless communication system is provided, comprising: an IMS device, a core network device and a terminal, the IMS device being configured to perform the steps of the method of the first aspect, the core network device being configured to perform the steps of the method of the second aspect, and the terminal being configured to perform the steps of the method of the second aspect.

[0020] In a fourteenth aspect, a chip is provided, comprising a processor and a communication interface, the communication interface being coupled to the processor, and the processor being configured to execute a program or an instruction to implement the method of the first aspect, or to implement the method of the second aspect, or to implement the method of the third aspect.

[0021] In a fifteenth aspect, a computer program / program product is provided, stored in a storage medium, and executed by at least one processor to implement the steps of the method of the first aspect, or to implement the steps of the method of the second aspect, or to implement the steps of the method of the third aspect.

[0022] In the embodiments of the present application, the IMS device receives a SIP INVITE message, the IMS device serves a first terminal, and the SIP INVITE message carries an identifier of a second terminal; the IMS device sends first information to the core network device based on the SIP INVITE message; wherein the first information comprises at least one of the following: the identifier of the second terminal, the identifier of the second terminal being used to determine whether to use the first notification mode to notify the first terminal; first indication information, the first indication information being used to indicate to use or allow to use the first notification mode to notify the first terminal. Through the scheme, since the IMS device can send the first information to the core network device based on the received SIP INVITE message, to be used to determine whether to use the first notification mode to notify the first terminal, or to be used to indicate to use or allow to use the first notification mode to notify the first terminal, therefore, when there is a service to be notified to the first terminal, the network will not directly use the first notification mode to notify the first terminal, but can determine whether to use the first notification mode to notify the first terminal, thereby improving the flexibility of notification. BRIEF DESCRIPTION OF DRAWINGS

[0023] FIG. 1 is a block diagram of a wireless communication system to which embodiments of the present application can be applied;

[0024] FIG. 2 is a flowchart of a notification method according to an embodiment of the present application;

[0025] FIG. 3 is a schematic diagram of a method for an IMS device to obtain an identifier of at least one third terminal in a notification method according to an embodiment of the present application;

[0026] FIG. 4 is a schematic diagram of a method for an IMS device to acquire the identity of at least one third terminal in a notification method according to an embodiment of the present application;

[0027] FIG. 5 is a flowchart of another notification method according to an embodiment of the present application;

[0028] FIG. 6 is a schematic diagram of another notification method according to an embodiment of the present application;

[0029] FIG. 7 is a schematic diagram of another notification method according to an embodiment of the present application;

[0030] FIG. 8 is a schematic diagram of another notification method according to an embodiment of the present application;

[0031] FIG. 8A is a schematic diagram of another notification method according to an embodiment of the present application;

[0032] FIG. 9 is a flowchart of another notification method according to an embodiment of the present application;

[0033] FIG. 10 is a schematic diagram of a method for a first terminal to set the identity of at least one third terminal in another notification method according to an embodiment of the present application;

[0034] FIG. 11 is a schematic diagram of a notification apparatus according to an embodiment of the present application;

[0035] FIG. 12 is a schematic diagram of another notification apparatus according to an embodiment of the present application;

[0036] FIG. 13 is a schematic diagram of another notification apparatus according to an embodiment of the present application;

[0037] FIG. 14 is a schematic diagram of a communication device according to an embodiment of the present application;

[0038] FIG. 15 is a schematic diagram of a hardware structure of a terminal according to an embodiment of the present application;

[0039] FIG. 16 is a schematic diagram of a hardware structure of a network-side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0040] The technical solutions in the embodiments of the present application will be described clearly below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art belong to the scope of protection of the present application.

[0041] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0042] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0043] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems. th

[0044] ​FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a terminal-side device such as a mobile phone, a Tablet Personal Computer, a Laptop Computer, a notebook computer, a Personal Digital Assistant (PDA), a palm computer, a netbook, an Ultra-mobile Personal Computer (UMPC), a Mobile Internet Device (MID), an Augmented Reality (AR) device, a Virtual Reality (VR) device, a robot, a wearable device, a flight vehicle, a Vehicle User Equipment (VUE), a shipboard device, a Pedestrian User Equipment (PUE), a smart home (a home device with a wireless communication function such as a refrigerator, a television, a washing machine, or furniture, etc.), a game console, a Personal Computer (PC), a kiosk, or a self-service machine, etc. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, etc.), a smart wristband, smart clothes, etc. The vehicle-mounted device can also be referred to as a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device, a core network device, or an IMS device. The IMS device is a device with an IMS, and the IMS is a brand-new multimedia service form and an important way to solve the integration of mobile and fixed networks and introduce voice, data, and video triple convergence and other differentiated services. The access network device can also be referred to as a Radio Access Network (RAN) device, a radio access network function, or a radio access network unit. The access network device can include a base station, a Wireless Local Area Network (WLAN) Access Point (AP), or a Wireless Fidelity (WiFi) node, etc.The base station can be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a relay station (RBS), a serving base station (SBS), a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home Node B (HNB), a home evolved Node B, a transmit / receive point (TRP), or some other suitable terminology in the art, and is not limited to a particular technical terminology, provided that the same technical effect is achieved. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0045] The core network device can also be referred to as a core network node, a core network function, or a core network network element, etc., which includes but is not limited to at least one of the following: a mobility management entity (MME), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a policy and charging rules function (PCRF), an edge application server discovery function (EASDF), a unified data management (UDM), a unified data repository (UDR), a home subscriber server (HSS), a centralized network configuration (CNC), a network repository function (NRF), a network exposure function (NEF), a local NEF (L-NEF), a binding support function (BSF), an application function (AF), a location management function (LMF), a gateway mobile location center (GMLC), a network data analytics function (NWDAF), etc. It should be noted that only the core network device in the NR system is taken as an example for introduction in the embodiments of the present application, and the specific type of the core network device is not limited. If the name of the core network device mentioned in the embodiments of the present application changes in the subsequent protocol version (for example, 6G), it is also within the protection scope of the present application.

[0046] Optionally, the core network device can be implemented by one or more function modules in one device, or can be implemented by multiple devices jointly, and the embodiments of the present application do not make a specific limitation in this regard. It can be understood that the above function modules can be network elements in a hardware device, can be software function modules running on a dedicated hardware, or can be virtualized function modules instantiated on a platform (for example, a cloud platform).

[0047] The notification method, apparatus, terminal and network side device provided by the embodiments of the present application will be described in detail below in combination with the accompanying drawings, some embodiments and application scenarios.

[0048] Non Terrestrial Network (NTN) refers to a network or network segment using a satellite or unmanned aerial vehicle system platform for transmission. Compared with a ground communication system, a satellite-based non terrestrial communication system has a more extensive coverage range and is suitable for scenarios where a ground base station cannot be built or a ground base station is damaged, such as continuous coverage in remote mountainous areas, deserts, oceans, forests, or emergency communication when a ground base station is damaged due to natural disasters. The satellite includes a Low Earth Orbiting (LEO) satellite, a Medium Earth Orbiting (MEO) satellite, a Geostationary Earth Orbiting (GEO) satellite, and a Highly Elliptical Orbiting (HEO) satellite.

[0049] In a typical NTN deployment scenario, the link between a UE and a satellite is called a service link (i.e., Service link), and the link between a satellite and a ground gateway is called a feeder link (Feeder link). In some scenarios, due to satellite movement, switching of the Service link and / or the Feeder link occurs. For Service link switching, the serving satellite of all UEs in a cell needs to be switched from one satellite to another satellite. For Feeder link switching, a certain satellite needs to be switched from one ground gateway to another ground gateway.

[0050] The NTN communication system includes two types: a transparent payload-based NTN communication system and a regenerative payload-based NTN communication system. In the transparent payload-based NTN communication system, the terminal, the base station, and the core network device are all deployed on the ground, and the communication data between the terminal and the network device is transferred via the satellite in the air. In this system, the satellite only forwards the data between the base station and the terminal, and does not decode and process the data. For the regenerative payload-based NTN communication system, the satellite has part or all of the base station functions and can decode and process the uplink or downlink data.

[0051] Currently, the IMS registration process is as follows:

[0052] 1. When the user equipment (UE) creates an IMS default bearer, the proxy call session control function (P-CSCF) address is obtained from the message. The UE sends a register message to the P-CSCF through the IMS default bearer.

[0053] 2. The P-CSCF forwards the register message to the interrogating-call session control function (I-CSCF).

[0054] 3. The I-CSCF sends a User Authorization request message to the home subscriber server (HSS) to obtain the S-CSCF. The HSS responds to the User Authorization request message, including the service-call session control function (S-CSCF) capability set.

[0055] 4. The I-CSCF forwards the register message to the S-CSCF.

[0056] 5. The S-CSCF sends a multimedia authentication request message to the HSS to query the authentication parameter set. The HSS sends the authentication parameter set through the multimedia authentication answer message.

[0057] 6. The S-CSCF sends 401 a response message to the I-CSCF, containing authentication parameters, for two-way authentication of the terminal. The I-CSCF sends 401 a response message to the P-CSCF. The P-CSCF sends 401 a response message to the UE. The P-CSCF takes out the AK and CK, and forwards the authentication token (AUTN) and random number (RAND) to the UE.

[0058] 7. The UE performs calculation according to the authentication parameters, and after the network side is authenticated, re-sends a register message, which includes the calculated extended resynchronization (XRES). The P-CSCF forwards the register message to the I-CSCF.

[0059] 8. The I-CSCF sends a User Authorization request to the HSS again. The HSS returns the S-CSCF name through a User Authorization answer message. The I-CSCF forwards the register message to the S-CSCF. The S-CSCF checks the XRES and the consistency of the return from the HSS, and then authenticates.

[0060] 9. The S-CSCF sends a Service assignment request message to the HSS to obtain user subscription data.

[0061] 10. The S-CSCF sends a 200 OK response message to the I-CSCF, which forwards the 200 OK to the P-CSCF, and then to the UE. The UE successfully registers in the IMS domain.

[0062] 11. For a VoLTE user, the S-CSCF also sends a register message to the corresponding AS according to the user subscription data, and the AS returns a 200 OK after successful registration.

[0063] The flow of UE receiving a paging (i.e., paging) is as follows:

[0064] 1. The UPF receives a data packet sent to the UE.

[0065] 2. The UPF sends a data notification message to the SMF.

[0066] 3. The SMF sends a Namf_Communication_N1N2MessageTransfer message to the AMF, for requesting to send downlink data to the UE.

[0067] 4. The AMF sends a paging message to all base stations within the area where the UE is located.

[0068] 5. The base station pages the UE within its coverage.

[0069] For core initiated paging procedure, like UE is in idle state, UE will respond the paging after receiving the paging, trigger NAS connection establishment (corresponding to trigger RRC connection establishment), NAS connection establishment is generally service request procedure or registration update (TAU) procedure. If UE is in RRC inactive, paging is initiated by RAN, called RAN paging, base station sends RAN notification / paging message to UE, UE responds notification / paging to perform RRC resume procedure, etc.

[0070] However, the communication between the satellite and the smartphone usually has very limited power margin, and usually requires line of sight to achieve the best performance. For mobile-originated calls, the user can perceive the channel quality and achieve LOS communication by consciously adjusting the signal transmission or reception point. However, for mobile communication, the user does not know the channel condition and may miss important calls or messages due to poor reception channel conditions. Satellite access is the last choice when the terrestrial network is unavailable, and improving the user accessibility of the satellite access system will help to achieve a better user experience. This requires the satellite access system to notify the user of the missed mobile terminated (MT) communication (such as MMTel) call or message when the user cannot be contacted in the satellite access system, or to notify the user of the failure of the MT communication call or message. This notification method can be called flexible notification. In simple terms, in the context of satellite-to-device communication, the "flexible notification service" refers to a highly reliable and efficient notification mechanism that sends notifications directly to user devices through satellite access. This mechanism ensures that important call notifications can reach users in areas where normal connections have failed or are impaired. It can also be understood as a way to improve the robustness of the paging association process in a satellite communication system and to solve the problem of users missing important calls and messages.

[0071] It should be noted that the above resilient notification (i.e., Resilient Notification) can also be referred to as a paging alert (i.e., Paging Alert) or an enhanced paging notification (i.e., Paging Robust Notification), etc. It is a paging or notification method that can send a notification to a user equipment such as a smart phone in a poor network access condition. It is mainly considered in a poor satellite access condition environment. The poor access condition can be understood as that the existing paging or notification method cannot page or notify the UE. In this case, an enhanced paging or notification method is used. The enhanced paging or notification method can be a new paging message or a paging alert message, using a dedicated paging channel, or triggering a short message to notify the called UE.

[0072] However, in some scenarios, considering unnecessary disturbance, not all phone calls or services are expected by the user to be notified to the UE by the above paging alert method. When there is a service to be notified to the UE, the network directly sends a notification to the UE using the paging alert notification method, which results in poor notification flexibility.

[0073] To solve the above problems, the embodiments of the present application provide a notification method, device, terminal and network side equipment. The notification method provided by the embodiments of the present application can be applied to the scenario of paging alert in a non-terrestrial communication network.

[0074] In the notification method provided by the embodiments of the present application, an IMS device receives a SIP invitation message, the IMS device serves a first terminal, and the SIP invitation message carries an identifier of a second terminal. The IMS device sends first information to a core network device based on the SIP invitation message. The first information includes at least one of the following: the identifier of the second terminal, the identifier of the second terminal being used to determine whether to use a first notification method to notify the first terminal; and first indication information, the first indication information being used to indicate to use or allow to use the first notification method to notify the first terminal. Through the scheme, since the IMS device can send the first information to the core network device based on the received SIP invitation message, to determine whether to use the first notification method to notify the first terminal, or to indicate to use or allow to use the first notification method to notify the first terminal, when there is a service to be notified to the first terminal, the network will not directly use the first notification method to notify the first terminal, but can determine whether to use the first notification method to notify the first terminal, thereby improving the flexibility of notification.

[0075] The embodiments of the present application provide a notification method, and FIG. 2 shows a flowchart of the notification method provided by the embodiments of the present application. As shown in FIG. 2, the notification method provided by the embodiments of the present application can include the following steps 201 and 202.

[0076] Step 201, the IMS device receives a SIP invitation message.

[0077] The IMS device serves a first terminal, and the SIP invitation message carries an identifier of a second terminal.

[0078] Optionally, the SIP invitation message can also carry an identifier of the first terminal.

[0079] It should be noted that the SIP invitation message is a message type in the SIP protocol, which is used to invite the other party to participate in the session. It contains the information of the initiator, the session description and the media negotiation, etc. By sending the SIP invitation message, the initiator can request the other party to establish a communication session and negotiate the session parameters, such as codec, transmission protocol, media type, etc. Optionally, in the embodiment of the present application, the identifier of the terminal can be a telephone number or a mobile integrated services digital network number corresponding to the terminal, etc.

[0080] For example, the identifier of the terminal can include but is not limited to at least one of the following: mobile subscriber international ISDN / PSTN number (MSISDN), subscription concealed identifier (SUCI), subscription permanent identifier (SUPI), globally unique temporary UE identity (GUTI), generic public subscription identifier (GPSI), permanent equipment identifier (PEI), etc.

[0081] It should be noted that the identifier of the terminal in the present application can also be referred to as the identifier of the user, which can be used to identify a user or a terminal, or to identify a terminal or a user of a specific service.

[0082] Optionally, in the embodiment of the present application, the SIP invitation message can be sent by an IMS device serving the second terminal.

[0083] Optionally, in the embodiment of the present application, the IMS device can include at least one of the following: S-CSCF, telephony application server (TAS) and P-CSCF.

[0084] Optionally, in embodiments of the present application, the S-CSCF (or telephone application server) can receive the SIP INVITE message.

[0085] In step 202, the IMS device sends first information to the core network device based on the SIP INVITE message.

[0086] The first information includes at least one of the following:

[0087] The identity of the second terminal, which is used to determine whether to use the first notification method to notify the first terminal;

[0088] The first indication information, which is used to indicate that the first notification method is used or allowed to notify the first terminal;

[0089] The first notification method is a notification method used or started in the case of failure of using the second notification method to notify the terminal.

[0090] Optionally, in embodiments of the present application, the first notification method can be a notification method used or started by the core network device in the case of failure of using the second notification method to notify the terminal.

[0091] Optionally, in embodiments of the present application, the first notification method can also be referred to as a notification method of paging alert (Paging Alert), a notification method of enhanced paging notification (Paging Robust Notification), or a notification method of flexible notification, etc.

[0092] Optionally, in embodiments of the present application, when the first information includes the identity of the second terminal, after the IMS device sends the first information to the core network device, the core network device can determine whether to use the first notification method to notify the first terminal according to the identity of the second terminal.

[0093] Optionally, in embodiments of the present application, the first indication information can also be referred to as a robust notification alert (RNA) indication.

[0094] Optionally, in embodiments of the present application, the first indication information can be determined by the S-CSCF (or telephone application server) based on the identity of the second terminal, and the S-CSCF (or telephone application server) can send the first indication information to the P-CSCF, and the P-CSCF can send the first indication information to the core network device.

[0095] Optionally, in embodiments of the present application, the S-CSCF (or telephone application server) can send the first indication information to the P-CSCF together with the SIP invitation message, or can send the first indication information to the P-CSCF by carrying the first indication information in the SIP invitation message, or can send the first indication information and the SIP invitation message to the P-CSCF respectively.

[0096] Optionally, in embodiments of the present application, in the case that at least one of the first terminal and the second terminal accesses the network through a satellite, the S-CSCF (or telephone application server) can send the first indication information to the P-CSCF; otherwise, in the case that neither of the first terminal and the second terminal accesses the network through a satellite, the S-CSCF (or telephone application server) does not send the first indication information to the P-CSCF.

[0097] Optionally, in embodiments of the present application, the failure to notify the terminal using the second notification mode can include at least one of the following 1.1 to 1.4:

[0098] 1.1, failure to page the terminal;

[0099] 1.2, failure to receive a response from the terminal after paging the terminal N times;

[0100] 1.3, failure to receive a response from the terminal after paging the terminal for a specific time;

[0101] 1.4, failure to receive a response from the terminal after N times of notification or notification for a specific time on a non-3rd Generation Partnership Project (3GPP) access;

[0102] wherein N is a positive integer.

[0103] For a specific description of the failure to notify the terminal using the second notification mode, reference can be made to the related description in the related art, and details are not described herein again to avoid repetition.

[0104] In embodiments of the present application, since the failure to notify the terminal using the second notification mode can include at least one of 1.1 to 1.4, the first notification mode can be used or started in the case of different ways of notifying the terminal of failure, thereby improving the flexibility of using or starting the first notification mode.

[0105] Optionally, in embodiments of the present application, the first notification mode can be used to notify the terminal of at least one of the following 2.1 to 2.3:

[0106] 2.1, failure to notify the terminal using the second notification mode;

[0107] 2.2, an un-received call;

[0108] 2.3, an un-received message.

[0109] Optionally, in embodiments of the present application, the un-received call or message can be a call or message that fails to be notified to the terminal using the second notification manner.

[0110] In embodiments of the present application, since the first notification manner can be used to notify the terminal of at least one of 2.1 to 2.3, the first notification manner can be used or started to notify the terminal of different content, thereby improving the flexibility of notifying the terminal.

[0111] Optionally, in embodiments of the present application, using the first notification manner can include at least one of the following:

[0112] sending a first message to the access network device; wherein the first message includes at least one of the following: a paging message, an N2 or S1 message; the first message carries second indication information, the second indication information being used to indicate that a paging message related to the first notification is sent;

[0113] sending a short message to a short message service function device, the short message being used to indicate that a call of the second terminal is not received, and time information corresponding to the call of the second terminal that is not received.

[0114] Optionally, in embodiments of the present application, the first information includes the first indication information. For example, the step 202 can be implemented by the following step 202a.

[0115] Step 202a, in a case where the identity of the second terminal matches the identity of at least one third terminal, the IMS device sends first indication information to the core network device.

[0116] Each of the at least one third terminal initiates a session with the first terminal, and the session is allowed to use the first notification manner.

[0117] Optionally, in embodiments of the present application, the identity of the at least one third terminal can be an identity in an identity list (or a list). For example, the identity in the identity list can be MSISDN, SUCI or GPS, etc. Each identity in the identity list corresponds to a terminal that initiates a session with the first terminal, and the session is allowed to use the first notification manner.

[0118] Optionally, in embodiments of the present application, the identity of the second terminal matches the identity of the at least one third terminal, which can be understood as that the matching degree between the identity of the second terminal and the identity of any terminal of the at least one third terminal is greater than or equal to a matching degree threshold, or the identity of the second terminal is the same as the identity of any terminal of the at least one third terminal.

[0119] It can be understood that, in the case where the identity of the second terminal matches the identity of the at least one third terminal, the session initiated by the second terminal with the first terminal allows the first notification mode to be used.

[0120] Optionally, in embodiments of the present application, after the IMS device obtains the identity of the second terminal from the SIP INVITE message, the IMS device can compare the identity of the second terminal with the identity of the at least one third terminal, and in the case where the identity of the second terminal matches the identity of the at least one third terminal, the IMS device sends the first indication information to the core network device.

[0121] In embodiments of the present application, since the IMS device sends the first indication information to the core network device in the case where the identity of the second terminal matches the identity of the at least one third terminal, the first indication information can be sent to the core network device to indicate that the first notification mode is used or allowed to be used to notify the first terminal in the case where it is determined that the session initiated by the second terminal with the first terminal allows the first notification mode to be used, so that the accuracy of sending the first indication information can be improved.

[0122] Optionally, in embodiments of the present application, the first indication information can include at least one of the following 3.1 to 3.3:

[0123] 3.1, indication information for indicating that the first notification mode is used;

[0124] 3.2, indication information for indicating that the first notification mode is allowed to be used;

[0125] 3.3, the identity of the second terminal.

[0126] Optionally, in embodiments of the present application, the first indication information includes the identity of the second terminal, which can be understood as that the first indication information is indication information in the form of the identity of the second terminal, and at this time the identity of the second terminal can indicate that the first notification mode is used or allowed to be used to notify the first terminal.

[0127] Optionally, in the embodiments of the present application, when the first indication information comprises the identity of the second terminal, after the IMS device sends the first information to the core network device, the core network device can determine that the session initiated by the second terminal to the first terminal is allowed to use the first notification mode, or make the core network device provide the identity of the second terminal to the first terminal through the first notification mode when it is determined to use the first notification mode.

[0128] In the embodiments of the present application, since the first indication information can comprise at least one of 3.1 to 3.3, the use or permission of using the first notification mode to notify the first terminal can be indicated to the core network device through different contents comprised in the first indication information, thereby improving the flexibility of determining the first indication information.

[0129] Optionally, in the embodiments of the present application, the core network device comprises a first core network device for processing user plane data. For example, the step 202 can be implemented by the following step 202b.

[0130] In step 202b, the IMS device sends downlink data to the first core network device based on the SIP invitation message.

[0131] The downlink data comprises the first information.

[0132] Optionally, in the embodiments of the present application, the first core network device can be a UPF.

[0133] Optionally, in the embodiments of the present application, the downlink data can be sent by the P-CSCF in the IMS device to the first core network device.

[0134] Optionally, in the embodiments of the present application, the downlink data can further comprise the SIP invitation message.

[0135] Optionally, in the embodiments of the present application, when the IMS device sends the downlink data to the first core network device, the identity of the second terminal can be sent to the first core network device.

[0136] Optionally, in the embodiments of the present application, the IMS device performs the step 202 only when at least one of the following conditions is met:

[0137] The call or mobile terminal communication to the first terminal fails;

[0138] The call or mobile terminal communication to the first terminal does not receive a response of the first terminal.

[0139] That is, the IMS device performs a traditional call flow after receiving the IMS invitation message from the IMS device serving the second terminal, and performs step 202 again, i.e., performs the matching of the identity of the second terminal with the at least one third terminal, sends the first information to the core network device, and performs subsequent operations after determining that the call or mobile terminal communication to the first terminal fails or that no response of the first terminal is received for the call or mobile terminal communication to the first terminal.

[0140] In the embodiments of the present application, the IMS device carries the first information in the downlink data in the user plane, so that the first information is effectively transmitted without the need for additional control plane interaction between the IMS device and the core network device.

[0141] Optionally, in the embodiments of the present application, the first information can be at least one of the following 4.1 to 4.4:

[0142] 4.1, information in an Internet Protocol (IP) header of the downlink data;

[0143] 4.2, a specific Differentiated Services Code Point (DSCP) value;

[0144] 4.3, a specific parameter;

[0145] 4.4, specific indication information.

[0146] Optionally, in the embodiments of the present application, the first information can be carried in the IP header of the downlink data.

[0147] Optionally, in the embodiments of the present application, the specific parameter can be any parameter that can indicate or allow the network to use the first notification mode to notify the first terminal.

[0148] In the embodiments of the present application, since the first information can be at least one of 4.1 to 4.4, different forms of first information can be sent to the core network device to indicate or allow the use of the first notification mode to notify the first terminal, thereby improving the flexibility of indicating or allowing the use of the first notification mode to notify the first terminal.

[0149] Optionally, in the embodiments of the present application, the core network device includes a second core network device for policy control. For example, step 202 can be implemented by step 202c.

[0150] Step 202c, the IMS device sends first downlink signaling to the second core network device based on the SIP invitation message.

[0151] The first downlink signaling comprises the first information.

[0152] Optionally, in embodiments of the present application, the second core network device can be a PCF.

[0153] Optionally, in embodiments of the present application, the first downlink signaling can be an Npcf_PolicyAuthorization_Create / update (i.e., npcf_PolicyAuthorization_Create / update) message.

[0154] Optionally, in embodiments of the present application, the IMS device can further send, to the second core network device, at least one of an identity of the second terminal and the SIP invite message, while sending the first downlink signaling to the second core network device.

[0155] In embodiments of the present application, since the IMS device can send the first downlink signaling comprising the first information to the first core network device based on the SIP invite message, the first information can be transmitted to the core network device in a control plane manner, so that the first information can be reliably transmitted.

[0156] Optionally, in embodiments of the present application, the step 202 can be implemented by the following step 202d.

[0157] The IMS device sends first information to the core network device based on a SIP invite message, in a case where a first condition is met.

[0158] The first condition comprises any one of the following:

[0159] A call or mobile terminal communication to the first terminal fails;

[0160] A call or mobile terminal communication to the first terminal does not receive a response of the first terminal.

[0161] Optionally, in embodiments of the present application, the mobile terminal communication can comprise a multimedia phone or a Multi Media Telephony (MMTel) call.

[0162] In embodiments of the present application, since the IMS device sends the first information to the core network device only in a case where the first condition is met, i.e., in a case where a call to a terminal fails or in a case where a paging or call response of a terminal is not received, the first information is sent to the core network device to indicate or allow using the first notification mode to notify the first terminal, so that the first notification mode can be reasonably triggered.

[0163] In the notification method provided by the embodiments of the present application, since the IMS device can send the first information to the core network device based on the received SIP invitation message, for judging whether to use the first notification method to notify the first terminal or for indicating to use or allow to use the first notification method to notify the first terminal, when there is a service to be notified to the first terminal, the network will not directly use the first notification method to notify the first terminal, but can determine whether to use the first notification method to notify the first terminal, thereby improving the flexibility of notification.

[0164] Optionally, the notification method provided by the embodiments of the present application can further include the following step 203.

[0165] Step 203, the IMS device acquires the identity of at least one third terminal.

[0166] Each third terminal initiated session with the first terminal allows the use of the first notification method.

[0167] Optionally, in the embodiments of the present application, the IMS device can first acquire the identity of the at least one third terminal, and then after receiving the SIP invitation message, determine whether the identity of the second terminal in the SIP message matches the identity of the at least one third terminal, thereby determining whether to send the first information to the core network device.

[0168] In the embodiments of the present application, since the IMS device can first acquire the identity of the at least one third terminal, it can facilitate the matching operation after acquiring the identity of the calling terminal, thereby simplifying the process of determining and sending the first indication information.

[0169] Optionally, in the embodiments of the present application, the step 203 can be implemented by the following step 203a, step 203b or step 203c.

[0170] Step 203a, the IMS device receives the SIP message sent by the first terminal.

[0171] The SIP message includes the identity of the at least one third terminal.

[0172] Exemplarily, taking the first terminal as a called UE as an example, as shown in FIG. 3, the process of the IMS device acquiring the identity of the at least one third terminal is as follows:

[0173] Step 1: The called UE sends a SIP message to the IMS device (specifically, S-CSCF / TAS), the SIP message including the identity of the at least one third terminal, for indicating which calling UE is allowed or can use the first notification mode to notify the called UE, the identity of the at least one third terminal can be the ID (such as the phone number MSISDN, GPSI, IP address, etc.) of the UE, and the IMS device stores the identity of the at least one third terminal after receiving the SIP message, for later judging whether the core network device is allowed or uses the first notification mode to notify the UE. Wherein, if it occurs in the IMS registration stage, the SIP message can be a SIP registration message, and if it occurs after the IMS registration, the SIP message can be other SIP messages or special new SIP messages, etc.

[0174] Step 2: The IMS device sends a reply message to the called UE.

[0175] Step 203b: The IMS device receives the subscription information of the first terminal sent by the third core network device.

[0176] Exemplarily, taking the above first terminal as the called UE as an example, as shown in FIG. 4, the process of the IMS device obtaining the identity of the at least one third terminal is as follows:

[0177] Step 1-8: Refer to steps 1-8 of the IMS registration process in the above related art;

[0178] Step 9: The IMS device sends a service assignment request to the HSS or UDM. If the UDM or HSS stores the identity of the at least one third terminal, the UDM or HSS sends the identity of the at least one third terminal to the IMS device, and the IMS device stores the identity of the at least one third terminal, for later judging whether the core network is allowed or uses the first notification mode to notify the called UE. The identity of the at least one third terminal stored in the UDM or HSS can be configured into the UDM or HSS when the called UE subscribes, or can be set or updated in the UDM or HSS by the called UE through the NAS process later.

[0179] Steps 10-11: Refer to steps 10-11 of the IMS registration process in the above related art.

[0180] Wherein, the subscription information includes the identity of the at least one third terminal, and the third core network device is a core network device for managing user subscription data in the core network device.

[0181] Step 203c: The IMS device obtains the identity of the at least one third terminal according to the preconfigured information.

[0182] The pre-configuration information is pre-configured in an IMS system.

[0183] Optionally, in the embodiments of the present application, the identity of the at least one third terminal pre-configured in the IMS system can be understood as specific identities set by some public security departments, which are related to public security (such as 110, 119, etc.). When a public security event occurs, the public security departments notify the IMS system, and the IMS system sets the first information according to the identities, such as setting to use or allow to use the first notification mode in the first information, so that the core network device can use the first notification mode to notify the terminal.

[0184] In the embodiments of the present application, since the IMS device can obtain the identity of the at least one third terminal from the first terminal, the third core network device or according to the local configuration information, the flexibility of obtaining the identity of the at least one third terminal can be improved, and the demand of public security is ensured.

[0185] The embodiments of the present application provide another notification method, and FIG. 5 shows a flowchart of the notification method provided by the embodiments of the present application. As shown in FIG. 5, the notification method provided by the embodiments of the present application can include the following step 501.

[0186] In step 501, the core network device receives the first information sent by the IMS device.

[0187] The IMS device serves the first terminal, and the first information includes at least one of the following:

[0188] The identity of the second terminal, which is used to determine whether to use the first notification mode to notify the first terminal;

[0189] The first indication information, which is used to indicate to use or allow to use the first notification mode to notify the first terminal;

[0190] The first notification mode is a notification mode used or started in the case that the terminal is failed to be notified by using the second notification mode.

[0191] Optionally, in the embodiments of the present application, the terminal is failed to be notified by using the second notification mode can include at least one of the following:

[0192] The terminal is failed to be paged;

[0193] The terminal is failed to be paged for N times without receiving the response of the terminal;

[0194] The terminal is failed to be paged for a specific time without receiving the response of the terminal;

[0195] N times of notification on the non-3GPP access or notification at a specific time, no response of the terminal is received;

[0196] wherein, N is a positive integer.

[0197] Optionally, in the embodiments of the present application, the first notification mode can be used to notify the terminal of at least one of the following:

[0198] Failure in notifying the terminal using the second notification mode;

[0199] Unreceived call;

[0200] Unreceived message.

[0201] Optionally, in the embodiments of the present application, the first indication information can include at least one of the following:

[0202] Indication information for indicating the use of the first notification mode;

[0203] Indication information for indicating the permission of using the first notification mode;

[0204] The identity of the second terminal.

[0205] Optionally, in the embodiments of the present application, the core network device includes a first core network device for processing user plane data. Illustratively, the step 501 can be implemented by the following step 501a.

[0206] Step 501a, the first core network device receives the downlink data sent by the IMS device.

[0207] wherein, the downlink data includes the first information.

[0208] Optionally, in the embodiments of the present application, the first information can be at least one of the following:

[0209] Information in the IP header of the downlink data;

[0210] Specific DSCP value;

[0211] Specific parameter;

[0212] Specific indication information.

[0213] Optionally, in the embodiments of the present application, the core network device further includes a fourth core network device for controlling session management, and a fifth core network device for access and mobility management. Illustratively, after the step 501a, the notification method provided by the embodiments of the present application can further include the following steps A and B.

[0214] Step A, the first core network device sends a downlink data notification to the fourth core network device.

[0215] The downlink data notification includes the first information.

[0216] Optionally, in embodiments of the present application, the fourth core network device can be an SMF.

[0217] Optionally, in embodiments of the present application, if the first core network device further receives an identifier of the second terminal sent by the IMS device, the downlink data notification can further include the identifier of the second terminal.

[0218] Step B, the fourth core network device sends a third downlink signaling to the fifth core network device upon receiving the downlink data notification.

[0219] The third downlink signaling includes the first information.

[0220] Optionally, in embodiments of the present application, the fifth core network device can be an AMF.

[0221] Optionally, in embodiments of the present application, the third downlink signaling can be a Namf_Communication_N1N2messageTransfer message.

[0222] Optionally, in embodiments of the present application, if the fourth core network device further receives the identifier of the second terminal sent by the first core network device, the third downlink signaling can further include the identifier of the second terminal.

[0223] Optionally, in embodiments of the present application, the core network device includes a second core network device for policy control related. Illustratively, the step 501 can be implemented by the following step 501b.

[0224] Step 501b, the second core network device receives a first downlink signaling sent by an IMS device.

[0225] The first downlink signaling includes the first information.

[0226] Optionally, in embodiments of the present application, the core network device further includes a fourth core network device for controlling session management, and a fifth core network device for access and mobility management. Illustratively, after the step 501b, the notification method provided by embodiments of the present application can further include the following steps C and D.

[0227] Step C, the second core network device sends a second downlink signaling to the fourth core network device.

[0228] The second downlink signaling includes the first information.

[0229] Optionally, in the embodiments of the present application, the second core network device can send the second downlink signaling to the fourth core network device by updating a policy control and charging (PCC) rule.

[0230] Optionally, in the embodiments of the present application, the second downlink signaling is an Npcf_SMpolicy_update notify request message.

[0231] Step D, the fourth core network device sends third downlink signaling to a fifth core network device upon receiving the second downlink signaling.

[0232] The third downlink signaling includes the first information.

[0233] Optionally, in the embodiments of the present application, the second core network device can also send the first information to the fifth core network device directly by updating a terminal policy.

[0234] Optionally, in the embodiments of the present application, the second core network device can send an Npcf_UEPolicyControl_Update Request message to the fifth core network device, and the Npcf_UEPolicyControl_Update Request message includes the first information.

[0235] Optionally, the notification method provided by the embodiments of the present application can further include the following step D.

[0236] Step D, the fifth core network device uses the first notification method to notify the first terminal according to the first information upon receiving the third downlink signaling.

[0237] Optionally, in the embodiments of the present application, the fifth core network device can send the first indication information (which can also carry the identifier of the second terminal) to an access network device according to the first information, and the access network device can send a paging alert message (which can also carry the identifier of the second terminal) to the terminal according to the indication of the first indication information after receiving the first indication information, so as to page or notify the first terminal by using the first notification method.

[0238] It should be noted that when paging or notifying the first terminal using the first notification mode, the fifth core network device can also simultaneously page or notify the first terminal using a traditional paging mode, such as alternately sending a paging message and a paging alert message.

[0239] In the embodiment of the application, since the fifth core network device can notify the first terminal using the first notification mode according to the first information in the case of receiving the third downlink signaling, the first notification mode can be flexibly used, and it is ensured that the first terminal will not miss the notification.

[0240] Optionally, in the embodiment of the application, the first information includes the first indication information. For example, the step D can be implemented by the following step D1.

[0241] In the step D1, in the case of receiving the third downlink signaling, if the first terminal fails to be notified using the second notification mode, the fifth core network device notifies the first terminal using the first notification mode according to the first indication information.

[0242] In the embodiment of the application, since the fifth core network device notifies the first terminal using the first notification mode according to the first indication information in the case of receiving the third downlink signaling and if the first terminal fails to be notified using the second notification mode, unnecessary use of the first notification mode can be avoided, and the flexibility of notifying the first terminal using the first notification mode can be improved.

[0243] Optionally, in the embodiment of the application, the first information includes an identifier of the second terminal. For example, the step D can be implemented by the following step D2.

[0244] In the step D2, in the case of receiving the third downlink signaling, if the first terminal fails to be notified using the second notification mode, and the identifier of the second terminal matches the identifier of at least one third terminal, the fifth core network device notifies the first terminal using the first notification mode.

[0245] Each third terminal initiates a session with the first terminal, and the session allows the first notification mode to be used.

[0246] Optionally, in the embodiment of the application, in the case of receiving the third downlink signaling and if the first terminal fails to be notified using the second notification mode, the fifth core network device can use the first notification mode, and provide the identifier of the second terminal to the first terminal when using the first notification mode, so that the first terminal knows which terminal initiates a session with the first terminal that is not received or fails to be received by the first terminal.

[0247] In the embodiment of the present application, since the fifth core network device uses the first notification mode to notify the first terminal in the case that the third downlink signaling is received, the second terminal fails to be notified by using the second notification mode, and the identity of the second terminal matches the identity of at least one third terminal, the first terminal can be notified by using the first notification mode in the case that the second terminal allows the first notification mode to be used, so that unnecessary use of the first notification mode can be further avoided, and the flexibility of notifying the first terminal by using the first notification mode can be improved. Optionally, the step D in the embodiment of the present application can be implemented by the following step D3.

[0248] The step D3 includes: in the case that the third downlink signaling is received, the first information includes the first indication information, and the first indication information includes the indication information of using the first notification mode, the fifth core network device uses the first notification mode to notify the first terminal.

[0249] In the embodiment of the present application, since the fifth core network device uses the first notification mode to notify the first terminal in the case that the third downlink signaling is received and the first information includes the first indication information and the first indication information includes the indication information of using the first notification mode, the first terminal can be notified by using the first notification mode in the case that the indication information is received, so that unnecessary use of the first notification mode can be further avoided, and the flexibility of notifying the first terminal by using the first notification mode can be improved.

[0250] Optionally, before the step D, the notification method provided in the embodiment of the present application can further include the following step E.

[0251] The step E includes: the fifth core network device receives the identity of at least one third terminal sent by the third core network device.

[0252] The third core network device is a core network device for managing user subscription data in the core network device.

[0253] In the notification method provided in the embodiment of the present application, since the core network device can receive the first information sent by the IMS device, whether to notify the first terminal by using the first notification mode or to be instructed to use or allowed to use the first notification mode to notify the first terminal can be determined based on the first information, so that when there is a service to be notified to the first terminal, the network will not directly notify the first terminal by using the first notification mode, but can determine whether to notify the first terminal by using the first notification mode, so that the flexibility of notification can be improved.

[0254] Optionally, in an embodiment of the present application, the core network device comprises a third core network device for managing user subscription data, and a fifth core network device for access and mobility management. By way of example, before step 501, the notification method provided by an embodiment of the present application can further comprise step 502.

[0255] In step 502, the third core network device sends the subscription information of the first terminal to an IMS device or the fifth core network device.

[0256] The subscription information comprises at least one identifier of a third terminal, and a session initiated by each third terminal to the first terminal is allowed to use the first notification method.

[0257] Optionally, in an embodiment of the present application, before step 502, the notification method provided by an embodiment of the present application can further comprise step 503.

[0258] In step 503, the third core network device receives the identifier of the third terminal sent by the first terminal.

[0259] By way of example, taking the first terminal as a called UE and the second terminal as a calling UE, as shown in FIG. 6, the process of the notification method provided by an embodiment of the present application is as follows:

[0260] In step 1, the IMS system (S-CSCF / TAS) of the called UE receives a SIP invitation message, and the SIP invitation message carries the identifier of the calling UE and the called UE, such as a telephone number or MSISDN.

[0261] In step 2, the IMS system (S-CSCF / TAS) determines whether the calling UE is allowed to use the first notification method according to the identifier of the third terminal. The identifier of the third terminal indicates which calling UE is allowed to use the first notification method to notify the called UE.

[0262] In step 3, the S-CSCF / TAS sends the first information to the P-CSCF. The first information can be sent to the P-CSCF together with the SIP invitation message, or the first information is sent to the P-CSCF by being carried in the SIP invitation message, or the first information and the SIP invitation message are sent to the P-CSCF respectively. The first information is determined according to the identifier of the third terminal in step 2, that is, if the ID of the calling UE in the SIP invitation message received in step 1 matches the identifier of the third terminal, the first information is sent to the P-CSCF in this step. Further considering another factor, whether the called UE and / or the calling UE accesses the network through a satellite, if yes, the first information is sent, and if not, the first information is not sent.

[0263] Step 4: P-CSCF receives the first information sent by S-CSCF / TAS in step 3, and / or includes the SIP INVITE message, P-CSCF sends the first information to UPF, which can be an explicit indication, or a specific DSCP value, or a parameter, etc. that can embody the permission or indication of network to use the first notification mode to notify UE. The first information can be sent to UPF as downlink data together with the SIP INVITE message. Optionally, P-CSCF can also send the ID of the calling UE to UPF in this step. The first information and / or the ID of the calling UE can be placed in the IP header of the data sent to UPF.

[0264] Step 5: UPF receives the information provided in step 4 sent by P-CSCF, UPF sends downlink data notification to SMF, which carries the first information, and if the ID of the calling UE is also provided in step 4, the downlink data notification also carries the ID of the calling UE.

[0265] Step 6: SMF receives the downlink data notification in step 5, SMF sends Namf_Communication_N1N2messageTransfer message to AMF, which carries the first information, and if the ID of the calling UE (such as MSISDN) is also carried in step 5, the message also carries the ID of the calling UE (such as MSISDN).

[0266] Step 7: AMF receives the Namf_Communication_N1N2messageTransfer message sent by SMF in step 6, AMF first uses paging (legacy paging), if paging does not get a response from the called UE for a certain number of times, or does not get a response from the called UE within a certain time of paging, or after paging fails, AMF decides to use the first notification mode to page or notify UE.

[0267] Step 8: According to the judgment in step 7, AMF sends paging alert indication or message to the base station, the base station uses the first notification mode to page or notify UE, and the base station sends paging alert message to UE. If the AMF obtains the ID of the calling UE in step 6, the paging alert indication or message sent by the AMF to the base station can also carry the ID of the calling UE, and the paging alert message sent by the base station can also carry the ID of the calling UE.

[0268] It should be noted that there can be another implementation: after the AMF receives the Namf_Communication_N1N2messageTransfer message sent by the SMF in step 6, the AMF directly decides to use the first notification method to notify or page the called UE according to the first information, which includes: the AMF sends a paging alert indication or message to the base station, and the base station uses the first notification method to page or notify the called UE, and the base station sends a paging alert message to the UE. If the AMF obtains the ID of the calling UE in step 6, the paging alert indication or message sent by the AMF to the base station can also carry the ID of the calling UE, and the base station can also carry the ID of the calling UE in the paging alert message sent by the base station.

[0269] Subsequent operation:

[0270] When the called UE receives the paging alert page or notification from the network, the called UE notifies the user that the paging alert has been received, such as sending an alarm sound. The called UE can also notify the user which calling UE's phone or data or information has been received according to the ID of the calling UE; wherein:

[0271] One subsequent operation: the user adjusts the called UE and then receives a normal ringing and establishes a call.

[0272] Another subsequent operation: the user adjusts the called UE and still cannot receive a normal ringing or notification:

[0273] Step 9: After a certain time, the IMS system (S-CSCF / TAS) triggers a short message service platform or function device to send a short message to the called UE, and the content of the short message embodies the missed calling UE ID and time information (i.e. the calling UE ID and time information that the called UE has not received the phone call) ;

[0274] Step 10: The short message service platform or function device sends a short message to the called UE according to the trigger of step 9, indicating the missed calling UE ID and time information (i.e. the calling UE ID and time information that the called UE has not received the phone call).

[0275] For example, the above-mentioned first terminal is the called UE, and the above-mentioned second terminal is the calling UE, as shown in FIG. 7, the process of the notification method provided by the embodiment of the application is as follows:

[0276] Steps 1-3: same as steps 1-3 in the above-mentioned embodiment of FIG. 6.

[0277] Step 4: P-CSCF receives the first information (or the SIP INVITE message) sent by S-CSCF / TAS in step 3, and sends the first information to SMF, which can be sent in the Npcf_PolicyAuthorization_Create / update message to PCF. Optionally, P-CSCF can also carry the ID of the calling UE (such as MSISDN) and the optional SIP INVITE message.

[0278] Step 5: PCF receives the message in step 4, wherein:

[0279] One embodiment: PCF sends the first information and the optional ID of the calling UE to SMF (as shown in step 6). PCF can send the first information and the optional ID of the calling UE to SMF by updating the PCC rule, which is sent to SMF through the Npcf_SMpolicy_updatenotify request message;

[0280] Another embodiment: PCF sends the first information and the optional ID of the calling UE to AMF (directly to step 7), and PCF can send the first information and the optional ID of the calling UE to AMF by updating the UE policy, which is sent to AMF through the Npcf_UEPolicyControl_Update Request message.

[0281] Step 6: SMF receives the first information and the optional ID of the calling UE in step 5, and sends the Namf_communication_N1N2message Transfer message to AMF, which carries the first information and the optional ID of the calling UE.

[0282] Step 7: AMF receives the Npcf_UEPolicyControl_Update Request message from PCF or the Namf_communication_N1N2message Transfer message from SMF, which carries the first information and the optional ID of the calling UE, and then AMF performs step 8 and subsequent operations in the example of FIG. 6.

[0283] For another example, taking the first terminal as the called UE and the second terminal as the calling UE, and taking the first information as an example including the identity of the second terminal, as shown in FIG. 8, the process of the notification method provided by the embodiments of the present application is as follows:

[0284] Step 0: In the registration phase, the AMF obtains the subscription information of the called UE from the UDM, which contains the identity of the at least one third terminal.

[0285] Step 1: The IMS device of the called UE receives the SIP invitation message of the IMS system of the calling UE, which includes the ID of the calling UE.

[0286] Step 2: The IMS device sends downlink data to the UPF, which carries the ID of the calling UE, which can be carried in the IP header of the downlink data, and the downlink data carries the SIP invitation message.

[0287] Step 3: The UPF sends downlink data notification to the SMF, carrying the ID of the calling UE.

[0288] Step 4: The SMF sends the Namf_Communication_N1N2messageTransfer message, carrying the ID of the calling UE.

[0289] Step 5: The AMF performs paging, and if the paging is not responded by the called UE within a certain number of times, or if the paging is not responded by the called UE within a certain time, or if the paging fails, and if the ID of the calling UE matches the calling UE ID in the identity of the at least one third terminal in step 0, it is decided to use the first notification method to notify the called UE.

[0290] Step 6: The AMF sends the paging alert related paging message to notify the called UE, and the related message carries the ID of the calling UE.

[0291] The user terminal rings, and the user can see the information of the calling UE.

[0292] For other descriptions in the embodiments of the present application, and the technical effects achieved by each step, please refer to the related descriptions in the above-mentioned IMS device side method embodiments. In order to avoid repetition, they will not be described here.

[0293] For example, the above-mentioned first terminal is the called UE, and the above-mentioned second terminal is the calling UE, as shown in FIG. 8A, the IMS device can also send the ID of the calling UE to the core network device by the way of transmitting control plane signaling, and then used for core network matching, the specific process is as follows:

[0294] Step 1: IMS device sends the ID of the calling UE to the PCF, and can also carry the SIP invite message to the PCF, the ID of the called UE and the SIP invite message can be carried in the Npcf_PolicyAuthorization_Create / update message.

[0295] Step 2: PCF calls the policy-related signaling, such as Npcf_SMpolicy_update notify request, to send the ID of the UE and the SIP invite in step 1 to the SMF; a real-time method can also be that the PCF sends Namf_communication_N1N2message Transfer to send the ID of the UE and the SIP invite to the AMF (then directly execute step 4).

[0296] Step 3: If the ID of the UE and the SIP invite are sent to the SMF in step 2, the SMF calls Namf_communication_N1N2message Transfer to send the ID of the UE and the SIP invite to the AMF.

[0297] Step 4: If the ID of the calling UE matches the calling UE ID in the identification of at least one third terminal in step 0 in the example of FIG. 8, it is decided to use the first notification method described above to notify the called UE, in which the calling UE ID is provided to the called UE.

[0298] The embodiment of the present application provides another notification method, and a flowchart of the notification method provided by the embodiment of the present application is shown in FIG. 9. As shown in FIG. 9, the notification method provided by the embodiment of the present application can include the following step 901.

[0299] Step 901: The first terminal sends the identification of at least one third terminal to the network side device.

[0300] Wherein, the session initiated by each third terminal with the first terminal allows the use of the first notification method, which is a notification method used or started in the case that the notification of the terminal using the second notification method fails, and the network side device includes at least one of an IMS device and a core network device.

[0301] Optionally, in the embodiment of the present application, the failure of the notification of the terminal using the second notification method can include at least one of the following:

[0302] The paging of the terminal fails;

[0303] The terminal is not received in response to the paging of the terminal N times;

[0304] paging the terminal for a specific time, and no response of the terminal is received;

[0305] paging the terminal for N times or for a specific time on the non-3GPP access, and no response of the terminal is received;

[0306] wherein N is a positive integer.

[0307] Optionally, in the embodiments of the present application, the first notification manner can be used to notify the terminal of at least one of the following:

[0308] the second notification manner fails to notify the terminal;

[0309] an un-received call;

[0310] an un-received message.

[0311] Optionally, in the embodiments of the present application, the network side device comprises an IMS device. Illustratively, the step 901 can be implemented by the following step 901a.

[0312] The step 901a, the first terminal sends an SIP message to the IMS device.

[0313] wherein the SIP message comprises the identity of the at least one third terminal.

[0314] Optionally, in the embodiments of the present application, the network side device comprises a core network device, and the core network device comprises a third core network device for managing user subscription data. Illustratively, the step 901 can be implemented by the following step 901b.

[0315] The step 901b, the first terminal sends a NAS message to the third core network device.

[0316] wherein the NAS message comprises the identity of the at least one third terminal.

[0317] Optionally, in the embodiments of the present application, the core network device further comprises a fifth core network device for access and mobility management. Illustratively, the step 901b can be implemented by the following step 901b1.

[0318] The step 901b1, the first terminal sends the NAS message to the third core network device through the fifth core network device.

[0319] Illustratively, as shown in FIG. 10, the first terminal is a UE, and the specific process of setting the identity of the at least one third terminal through the NAS procedure in the UDM or HSS by the first terminal is as follows:

[0320] Step 0: The IMS system (S-CSCF / TAS) can subscribe the subscription data of the UE to the UDM.

[0321] Step 1: The UE sends the identity of the at least one third terminal to the AMF through a NAS message, which is used to indicate which calling UE is allowed or can use the first notification mode to notify the UE.

[0322] Step 2: The AMF sends the Nudm_parameterProvision_Update message to the UDM, which carries the identity of the at least one third terminal set or updated by the UE.

[0323] Step 3: The AMF sends the response to the UE.

[0324] Step 4: The UDM sends the identity of the at least one third terminal to the IMS system (S-CSCF / TAS).

[0325] Step 5: The IMS system (S-CSCF / TAS) can unsubscribe the subscription data of the UE.

[0326] For other descriptions in the embodiments of the present application, and the technical effects realized by each step, please refer to the related descriptions in the above-mentioned IMS device side and the above-mentioned core network device side method embodiments. In order to avoid repetition, this will not be repeated here.

[0327] In the notification method provided by the embodiments of the present application, the first terminal can send the identity of the at least one third terminal to at least one of the IMS device and the core network device; wherein the session initiated by each third terminal with the first terminal allows the use of the first notification mode, so that the network side device receiving the identity of the at least one third terminal can determine whether to use the first notification mode to notify the terminal based on the identity of the at least one third terminal, rather than directly using the first notification mode to notify the terminal when there is a service that needs to notify the terminal, thereby improving the flexibility of notification.

[0328] The notification method provided by the embodiments of the present application can be executed by a notification device. In the embodiments of the present application, the notification method executed by the notification device is taken as an example to illustrate the notification device provided by the embodiments of the present application.

[0329] The embodiments of the present application provide a notification device. As an example, the notification device can be a communication device or a component in a communication device, such as a chip. The communication device can be a terminal, a network side device or a server, etc. For example, the terminal can include but is not limited to the types of the terminal 11 listed above, the network side device can include but is not limited to the types of the network side device 12 listed above, and the embodiments of the present application are not limited specifically.

[0330] The notification apparatus includes a receiving module, a sending module and a processing module. The receiving module, the sending module and the processing module can be implemented by software or by hardware. When implemented by hardware, the processing module can be implemented by a processor. The processor can include a general-purpose processor, a special-purpose processor, a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), an artificial intelligent (AI) processor, a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a network processor (NP), a field programmable gate array (FPGA) or other programmable logic device, a gate circuit, a transistor, a discrete hardware component, etc. The receiving module and the sending module can be implemented by a communication interface, which can include a transceiver, a pin, a circuit, a bus, a radio frequency unit, etc.

[0331] Specifically, referring to FIG. 11, when the notification apparatus is an IMS device or a component in the IMS device, the notification apparatus 110 includes a first receiving module 111 and a first sending module 112.

[0332] The first receiving module 111 can be configured to receive a SIP INVITE message, and the IMS device serves a first terminal. The SIP INVITE message carries an identifier of a second terminal. The first sending module 112 can be configured to send first information to a core network device based on the SIP INVITE message. The first information includes at least one of the following: the identifier of the second terminal, the identifier of the second terminal being used to determine whether to notify the first terminal by using a first notification manner; and first indication information, the first indication information being used to indicate that the first notification manner is used or allowed to notify the first terminal.

[0333] In a possible implementation, the first notification manner can be used to notify the terminal of at least one of the following: failure of notifying the terminal by using the second notification manner; an un-received call; and an un-received message.

[0334] In a possible implementation, the first information includes the first indication information. The first sending module 112, specifically, can be configured to send the first indication information to the core network device in a case where the identity of the second terminal matches the identity of at least one third terminal, and each session initiated by the third terminal with the first terminal is allowed to use the first notification manner.

[0335] In a possible implementation, the first indication information can include at least one of the following: indication information used to indicate that the first notification manner is used; indication information used to indicate that the first notification manner is allowed to be used; and the identity of the second terminal.

[0336] In a possible implementation, the core network device includes a first core network device used to process user plane data. The first sending module 112, specifically, can be configured to send, based on the SIP INVITE message, downlink data to the first core network device, where the downlink data includes the first information.

[0337] In a possible implementation, the first information can be at least one of the following: information in an IP header of the downlink data; a specific DSCP value; a specific parameter; and specific indication information.

[0338] In a possible implementation, the core network device includes a second core network device used for policy control. The first sending module 112, specifically, can be configured to send, based on the SIP INVITE message, first downlink signaling to the second core network device, where the first downlink signaling includes the first information.

[0339] In a possible implementation, the first sending module 112, specifically, can be configured to send, based on the SIP INVITE message, the first information to the core network device in a case where a first condition is met, and the first condition includes any one of the following: a call or mobile terminal communication to the first terminal fails; or a response of the first terminal is not received for the call or mobile terminal communication to the first terminal.

[0340] In a possible implementation, the notification apparatus 110 can further include an obtaining module. The obtaining module can be configured to obtain the identity of at least one third terminal, and each session initiated by the third terminal with the first terminal is allowed to use the first notification manner.

[0341] In a possible implementation, the obtaining module can be specifically configured to: receive a SIP message sent by the first terminal, the SIP message comprising the identity of the at least one third terminal; or receive subscription information of the first terminal sent by a third core network device, the subscription information comprising the identity of the at least one third terminal, the third core network device being a core network device in the core network devices that is configured to manage user subscription data; or obtain the identity of the at least one third terminal according to preconfigured information, the preconfigured information being preconfigured in the IMS system.

[0342] In the notification apparatus provided in the embodiments of the present application, the notification apparatus can send first information to the core network device based on the received SIP invitation message, so as to determine whether to use the first notification mode to notify the first terminal or to instruct to use or allow to use the first notification mode to notify the first terminal. Therefore, when there is a service that needs to notify the first terminal, the network will not directly use the first notification mode to notify the first terminal, but can determine whether to use the first notification mode to notify the first terminal, thereby improving the flexibility of notification.

[0343] The notification apparatus provided in the embodiments of the present application can implement each process achieved by the IMS device method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein.

[0344] Referring to FIG. 12, when the notification apparatus is a core network device or a component in the core network device, the notification apparatus 120 comprises a second receiving module 121.

[0345] The second receiving module 121 can be configured to receive first information sent by an IMS device, the IMS device serving the first terminal, the first information comprising at least one of the following: an identity of a second terminal, the identity of the second terminal being used to determine whether to use the first notification mode to notify the first terminal; and first indication information, the first indication information being used to instruct to use or allow to use the first notification mode to notify the first terminal; wherein the first notification mode is a notification mode used or started in a case where the second notification mode fails to notify the terminal.

[0346] In a possible implementation, the failure of the second notification mode to notify the terminal can comprise at least one of the following: failure to page the terminal; failure to page the terminal for N times without receiving a response from the terminal; failure to page the terminal for a specific time without receiving a response from the terminal; failure to notify the terminal for N times on a non-3GPP access or for a specific time without receiving a response from the terminal; wherein N is a positive integer.

[0347] In a possible implementation, the first notification mode can be used to notify the terminal of at least one of the following: failure of the second notification mode to notify the terminal; an un-received call; and an un-received message.

[0348] In a possible implementation, the first indication information can include at least one of the following: indication information used to indicate that the first notification manner is used; indication information used to indicate that the first notification manner is allowed to be used; and an identifier of the second terminal.

[0349] In a possible implementation, the core network device includes a first core network device used to process user plane data. The second receiving module 121 can be specifically configured to receive downlink data sent by the IMS device, and the downlink data includes the first information.

[0350] In a possible implementation, the first information can be at least one of the following: information in an IP header of the downlink data; a specific DSCP value; a specific parameter; and specific indication information.

[0351] In a possible implementation, the core network device further includes a fourth core network device used to control session management, and a fifth core network device used to access and mobility management. The notification apparatus 120 can further include a second sending module. The second sending module can be configured to, after the second receiving module 121 receives the downlink data sent by the IMS device, send, to the fourth core network device, downlink data notification including the first information; and in a case where the fourth core network device receives the downlink data notification, send, to the fifth core network device, third downlink signaling including the first information.

[0352] In a possible implementation, the core network device includes a second core network device used for policy control. The second receiving module 121 can be specifically configured to receive first downlink signaling sent by the IMS device, and the first downlink signaling includes the first information.

[0353] In a possible implementation, the core network device further includes a fourth core network device used to control session management, and a fifth core network device used to access and mobility management. The notification apparatus 120 can further include a second sending module. The second sending module can be configured to, after the second receiving module 121 receives the first downlink signaling sent by the IMS device, send, to the fourth core network device, second downlink signaling including the first information; and in a case where the fourth core network device receives the second downlink signaling, send, to the fifth core network device, third downlink signaling including the first information.

[0354] In a possible implementation, the notification apparatus 120 can further include a processing module. The processing module can be configured to, in a case where the third downlink signaling is received, notify the first terminal using the first notification manner according to the first information.

[0355] In a possible implementation, the first information includes the first indication information. The processing module can be specifically configured to, if the first terminal fails to be notified by using the second notification manner, notify the first terminal by using the first notification manner according to the first indication information.

[0356] In a possible implementation, the first information includes an identifier of the second terminal. The processing module can be specifically configured to, if the first terminal fails to be notified by using the second notification manner, and the identifier of the second terminal matches an identifier of at least one third terminal, notify the first terminal by using the first notification manner, where a session initiated by each third terminal to the first terminal allows the first notification manner to be used.

[0357] In a possible implementation, the second receiving module 121 can be further configured to receive the identifier of the at least one third terminal sent by a third core network device before the processing module notifies the first terminal by using the first notification manner, where the third core network device is a core network device for managing user subscription data in the core network devices.

[0358] In a possible implementation, the processing module can be specifically configured to notify the first terminal by using the first notification manner if the first information includes the first indication information, and the first indication information includes indication information of using the first notification manner.

[0359] In a possible implementation, the core network device includes a third core network device for managing user subscription data, and a fifth core network device for access and mobility management. The notification apparatus 120 can further include a second sending module. The second sending module can be configured to send subscription information of the first terminal to an IMS device or the fifth core network device before the second receiving module 121 receives the first information sent by the IMS device, where the subscription information includes an identifier of at least one third terminal, and a session initiated by each third terminal to the first terminal allows the first notification manner to be used.

[0360] In a possible implementation, the second receiving module 121 can be further configured to receive the identifier of the at least one third terminal sent by the first terminal before the second sending module sends the subscription information of the first terminal to the IMS device or the fifth core network device.

[0361] In the notification apparatus provided in the embodiments of the present application, since the notification apparatus can receive the first information sent by the IMS device, whether to use the first notification mode to notify the first terminal or to be instructed to use or allowed to use the first notification mode to notify the first terminal can be determined based on the first information, so that when there is a service to be notified to the first terminal, the network will not directly use the first notification mode to notify the first terminal, but can determine whether to use the first notification mode to notify the first terminal, so as to improve the flexibility of notification.

[0362] The notification apparatus provided in the embodiments of the present application can implement each process implemented by the core network device method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein.

[0363] Referring to FIG. 13, when the notification apparatus is a terminal or a component in a terminal, the notification apparatus 130 includes a third sending module 131.

[0364] The third sending module 131 can be configured to send the identity of at least one third terminal to a network-side device, wherein each session initiated by each third terminal with the first terminal allows the first notification mode to be used, and the network-side device includes at least one of an IMS device and a core network device.

[0365] In a possible implementation, the first notification mode can be used to notify the terminal of at least one of the following: failure of using the second notification mode to notify the terminal; an un-received call; and an un-received message.

[0366] In a possible implementation, the network-side device includes the IMS device. The third sending module 131 can be specifically configured to send a SIP message to the IMS device, and the SIP message includes the identity of the at least one third terminal.

[0367] In a possible implementation, the network-side device includes the core network device, and the core network device includes a third core network device configured to manage user subscription data. The third sending module 131 can be specifically configured to send a NAS message to the third core network device, and the NAS message includes the identity of the at least one third terminal.

[0368] In a possible implementation, the core network device further includes a fifth core network device configured to access and mobility management. The third sending module 131 can be specifically configured to send the NAS message to the third core network device through the fifth core network device.

[0369] In the notification apparatus provided in the embodiments of the present application, the notification apparatus can be used to send the identity of at least one third terminal to at least one of the IMS device and the core network device; wherein the session initiated by each third terminal with the first terminal allows the first notification mode to be used, so that the network side device receiving the identity of the at least one third terminal can determine whether to use the first notification mode to notify the terminal based on the identity of the at least one third terminal, instead of directly using the first notification mode to notify the terminal when there is a service to notify the terminal, thereby improving the flexibility of notification.

[0370] The notification apparatus provided in the embodiments of the present application can implement the various processes implemented by the first terminal side method embodiments and achieve the same technical effects. To avoid repetition, the various processes will not be described here again.

[0371] As shown in FIG. 14, the embodiments of the present application further provide a communication device 100, which includes a processor 101 and a memory 102, and the memory 102 has stored programs or instructions executable on the processor 101. For example, when the communication device 100 is a terminal, the programs or instructions are executed by the processor 101 to implement the various steps of the terminal side method embodiments and achieve the same technical effects. When the communication device 100 is a network side device, the programs or instructions are executed by the processor 101 to implement the various steps of the network side device method embodiments and achieve the same technical effects. To avoid repetition, the various processes will not be described here again.

[0372] The embodiments of the present application further provide a terminal, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run programs or instructions to implement the steps in the terminal side method embodiments. The terminal embodiments correspond to the terminal side method embodiments, and the various implementation processes and implementation manners of the method embodiments can be applied to the terminal embodiments and achieve the same technical effects. The terminal can be the notification apparatus shown in FIG. 13. Specifically, FIG. 15 is a hardware structure diagram of a terminal according to an embodiment of the present application.

[0373] The terminal 1000 includes, but is not limited to, at least part of the following components: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010, etc.

[0374] Those skilled in the art can understand that the terminal 1000 can further include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 1010 through a power management system, so that the power management system can realize the functions of managing charging, discharging and power consumption management. The terminal structure shown in FIG. 15 does not constitute a limitation on the terminal, and the terminal can include more or fewer components than those shown, or combine certain components, or different component arrangements, which will not be described here.

[0375] It should be understood that in the embodiments of the present application, the input unit 1004 can include a graphics processor 10041 and a microphone 10042. The graphics processor 10041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1006 can include a display panel 10061, which can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 1007 includes at least one of a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 can include two parts of a touch detection device and a touch controller. The other input devices 10072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), trackballs, mice, joysticks, which will not be described here.

[0376] In the embodiments of the present application, after the radio frequency unit 1001 receives the downlink data from the network side device, it can be transmitted to the processor 1010 for processing. In addition, the radio frequency unit 1001 can send uplink data to the network side device. Generally, the radio frequency unit 1001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0377] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 can mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) or an instruction, etc. In addition, the memory 1009 can include a volatile memory or a non-volatile memory. The non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM), a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synch link DRAM (SLDRAM), and a Direct Rambus RAM (DRRAM). The memory 1009 in the embodiments of the present application includes but is not limited to these and any other suitable type of memory.

[0378] The processor 1010 can include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and an application program, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 1010.

[0379] The radio frequency unit 1001 can be used to send an identifier of at least one third terminal to a network side device; wherein each session initiated by the third terminal with the first terminal allows the use of the first notification mode, and the network side device includes at least one of an IMS device and a core network device.

[0380] In a possible implementation, the first notification manner can be used to notify the terminal of at least one of the following: failure of using the second notification manner to notify the terminal; an un-received call; an un-received message.

[0381] In a possible implementation, the network-side device includes an IMS device. The radio frequency unit 1001 can be specifically configured to send a SIP message to the IMS device, where the SIP message includes the identifier of the at least one third terminal.

[0382] In a possible implementation, the network-side device includes a core network device, and the core network device includes a third core network device configured to manage user subscription data. The radio frequency unit 1001 can be specifically configured to send a NAS message to the third core network device, where the NAS message includes the identifier of the at least one third terminal.

[0383] In a possible implementation, the core network device further includes a fifth core network device configured to access and mobility management. The radio frequency unit 1001 can be specifically configured to send the NAS message to the third core network device through the fifth core network device.

[0384] In the terminal provided in the embodiments of the present application, since the terminal can be configured to send the identifier of the at least one third terminal to at least one of the IMS device and the core network device, and each third terminal initiates a session with the first terminal, and the session is allowed to use the first notification manner, the network-side device receiving the identifier of the at least one third terminal can determine whether to notify the terminal using the first notification manner based on the identifier of the at least one third terminal, instead of directly using the first notification manner to notify the terminal when there is a service to be notified, thereby improving the flexibility of notification.

[0385] It can be understood that the implementation processes of the implementation manners mentioned in the embodiments can refer to the related descriptions of the terminal-side method embodiments, and achieve the same or corresponding technical effects. To avoid repetition, details are not described herein again.

[0386] The embodiments of the present application further provide a network-side device including a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run programs or instructions to implement the steps of the network-side device method embodiments. The network-side device embodiments correspond to the network-side device method embodiments, and each implementation process and implementation manner of the method embodiments can be applied to the network-side device embodiments and achieve the same technical effects.

[0387] Specifically, the embodiment of the present application further provides a network side device. As shown in FIG. 16, the network side device 1100 includes a processor 1101, a network interface 1102 and a memory 1103. The network side device can be the notification apparatus shown in FIG. 11, or can be the notification apparatus shown in FIG. 12. Wherein, the network interface 1102 is, for example, a common public radio interface (CPRI).

[0388] Specifically, the network side device 1100 of the embodiment of the present application further includes instructions or programs stored on the memory 1103 and executable on the processor 1101, the processor 1101 invokes the instructions or programs in the memory 1103 to execute the method performed by the network side device described above, and achieves the same technical effects. To avoid repetition, it will not be described here.

[0389] Wherein, the network interface 1102 can be used to receive a SIP invitation message, the IMS device serves a first terminal, the SIP invitation message carries an identity of a second terminal; and based on the SIP invitation message, send first information to a core network device; wherein the first information includes at least one of the following: the identity of the second terminal, the identity of the second terminal is used to determine whether to use a first notification mode to notify the first terminal; first indication information, the first indication information is used to indicate that the first notification mode is used or allowed to be used to notify the first terminal.

[0390] In a possible implementation, the first notification mode can be used to notify the terminal of at least one of the following: failure to use the second notification mode to notify the terminal; an un-received call; an un-received message.

[0391] In a possible implementation, the first information includes the first indication information. The network interface 1102 can be specifically used to send the first indication information to the core network device in a case where the identity of the second terminal matches an identity of at least one third terminal, wherein a session initiated by each third terminal with the first terminal allows the first notification mode to be used.

[0392] In a possible implementation, the first indication information can include at least one of the following: indication information used to indicate that the first notification mode is used; indication information used to indicate that the first notification mode is allowed to be used; and the identity of the second terminal.

[0393] In a possible implementation, the core network device includes a first core network device for processing user plane data. The network interface 1102 can be specifically used to send, based on the SIP invitation message, downlink data including the first information to the first core network device. In a possible implementation, the core network device includes a first core network device for processing user plane data. The network interface 1102 can be specifically used to send, based on the SIP invitation message, downlink data including the first information to the first core network device.

[0394] In a possible implementation, the first information can be at least one of the following: information in an IP header of the downlink data; a specific DSCP value; a specific parameter; and specific indication information.

[0395] In a possible implementation, the core network device comprises a second core network device for policy control. The network interface 1102 can be specifically configured to send, based on the SIP INVITE message, first downlink signaling to the second core network device, the first downlink signaling comprising the first information.

[0396] In a possible implementation, the network interface 1102 can be specifically configured to send, based on the SIP INVITE message, the first information to the core network device when a first condition is met, wherein the first condition comprises any of the following: a call or mobile terminal communication to the first terminal fails; or a response of the first terminal is not received for the call or mobile terminal communication to the first terminal.

[0397] In a possible implementation, the network interface 1102 can be further configured to obtain an identifier of at least one third terminal, and a session initiated by each third terminal to the first terminal is allowed to use the first notification mode.

[0398] In a possible implementation, the network interface 1102 can be specifically configured to: receive a SIP message sent by the first terminal, the SIP message comprising the identifier of the at least one third terminal; or receive subscription information of the first terminal sent by a third core network device, the subscription information comprising the identifier of the at least one third terminal, the third core network device being a core network device in the core network device for managing user subscription data; or obtain the identifier of the at least one third terminal according to preconfigured information, the preconfigured information being preconfigured in an IMS system.

[0399] In the network side device provided by the embodiments of the present application, the network side device can send first information to a core network device based on a received SIP INVITE message, to determine whether to use a first notification mode to notify a first terminal, or to instruct to use or allow to use the first notification mode to notify the first terminal. Therefore, when there is a service that needs to notify the first terminal, the network does not directly use the first notification mode to notify the first terminal, but can determine whether to use the first notification mode to notify the first terminal, thereby improving the flexibility of notification.

[0400] It can be understood that the implementation processes of the implementation modes mentioned in the embodiments can refer to the related descriptions of the IMS device method embodiments, and achieve the same or corresponding technical effects. To avoid repetition, they will not be described here again.

[0401] Alternatively,

[0402] The network interface 1102 can be configured to receive first information sent by an IMS device, wherein the IMS device serves a first terminal, and the first information comprises at least one of the following: an identifier of a second terminal, the identifier of the second terminal being used to determine whether the first terminal is notified by using a first notification mode; and first indication information, the first indication information being used to indicate that the first terminal is notified by using or allowed to use the first notification mode, wherein the first notification mode is a notification mode used or started in a case where the second terminal is failed to be notified by using a second notification mode.

[0403] In a possible implementation, the failure of the second terminal to be notified by using the second notification mode can include at least one of the following: failure of paging the terminal; failure of paging the terminal for N times without receiving a response of the terminal; failure of paging the terminal for a specific time without receiving a response of the terminal; failure of notifying the terminal for N times on a non-3GPP access or for a specific time without receiving a response of the terminal, wherein N is a positive integer.

[0404] In a possible implementation, the first notification mode can be used to notify the terminal of at least one of the following: failure of the terminal to be notified by using the second notification mode; a call that is not received; and a message that is not received.

[0405] In a possible implementation, the first indication information can include at least one of the following: indication information used to indicate that the first notification mode is used; indication information used to indicate that the first notification mode is allowed to be used; and the identifier of the second terminal.

[0406] In a possible implementation, the core network device includes a first core network device configured to process user plane data. The network interface 1102 can be specifically configured to receive downlink data sent by the IMS device, and the downlink data comprises the first information.

[0407] In a possible implementation, the first information can be at least one of the following: information in an IP header of the downlink data; a specific DSCP value; a specific parameter; and specific indication information.

[0408] In a possible implementation, the core network device further includes a fourth core network device configured to control session management, and a fifth core network device configured to access and mobility management. The network interface 1102 can be further configured to, after receiving the downlink data sent by the IMS device, send a downlink data notification to the fourth core network device, the downlink data notification comprising the first information; and in a case where the fourth core network device receives the downlink data notification, send third downlink signaling to the fifth core network device, the third downlink signaling comprising the first information.

[0409] In a possible implementation, the core network device comprises a second core network device for policy control. The network interface 1102 can be specifically configured to receive the first downlink signaling sent by the IMS device, where the first downlink signaling comprises the first information.

[0410] In a possible implementation, the core network device further comprises a fourth core network device for controlling session management, and a fifth core network device for access and mobility management. The network interface 1102 can be further configured to, after receiving the first downlink signaling sent by the IMS device, send, to the fourth core network device, second downlink signaling comprising the first information; and in a case where the fourth core network device receives the second downlink signaling, send, to the fifth core network device, third downlink signaling comprising the first information.

[0411] In a possible implementation, the processor 1101 can be configured to, in a case where the third downlink signaling is received, notify the first terminal by using the first notification mode according to the first information.

[0412] In a possible implementation, the first information comprises the first indication information. The processor 1101 can be specifically configured to, in a case where the first terminal fails to be notified by using the second notification mode, notify the first terminal by using the first notification mode according to the first indication information.

[0413] In a possible implementation, the first information comprises an identifier of the second terminal. The processor 1101 can be specifically configured to, in a case where the first terminal fails to be notified by using the second notification mode and the identifier of the second terminal matches an identifier of at least one third terminal, notify the first terminal by using the first notification mode, where a session initiated by each third terminal to the first terminal is allowed to use the first notification mode.

[0414] In a possible implementation, the network interface 1102 can be further configured to, before the processor 1101 notifies the first terminal by using the first notification mode, receive the identifier of the at least one third terminal sent by a third core network device, where the third core network device is a core network device in the core network device for managing user subscription data.

[0415] In a possible implementation, the processor 1101 can be specifically configured to, in a case where the first information comprises the first indication information and the first indication information comprises indication information of using the first notification mode, notify the first terminal by using the first notification mode.

[0416] In a possible implementation, the core network device includes a third core network device for managing user subscription data, and a fifth core network device for access and mobility management. The network interface 1102 can also be configured to send, to the IMS device or the fifth core network device, subscription information of the first terminal before receiving the first information sent by the IMS device, where the subscription information includes an identifier of at least one third terminal, and a session initiated by each third terminal to the first terminal is allowed to use the first notification mode.

[0417] In a possible implementation, the network interface 1102 can also be configured to receive the identifier of the at least one third terminal sent by the first terminal before the second sending module sends the subscription information of the first terminal to the IMS device or the fifth core network device.

[0418] In the network-side device provided in the embodiments of the present application, since the network-side device can receive the first information sent by the IMS device, it can determine whether to notify the first terminal using the first notification mode, or whether to be instructed to use or allowed to use the first notification mode to notify the first terminal based on the first information, so that when there is a service to be notified to the first terminal, the network does not directly notify the first terminal using the first notification mode, but can determine whether to notify the first terminal using the first notification mode, thereby improving the flexibility of notification.

[0419] It can be understood that the implementation processes of the implementation modes mentioned in the embodiments can refer to the related descriptions of the core network device method embodiments, and achieve the same or corresponding technical effects. To avoid repetition, they will not be described here again.

[0420] The embodiments of the present application also provide a readable storage medium having a program or instructions stored thereon, which, when executed by a processor, implements various processes of the above notification method embodiments and can achieve the same technical effects. To avoid repetition, they will not be described here again.

[0421] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes a computer readable storage medium, such as a computer readable only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc. In some examples, the readable storage medium can be a non-transitory readable storage medium.

[0422] The embodiments of the present application further provide a chip including a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement various processes of the above notification method embodiments and achieve the same technical effects. To avoid repetition, they will not be described here again.

[0423] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, etc.

[0424] The embodiments of the present application further provide a computer program / program product stored in a storage medium, which is executed by at least one processor to implement the processes of the above notification method embodiments and achieve the same technical effects. For the sake of brevity, the same will not be repeated here.

[0425] The embodiments of the present application further provide a communication system, comprising a terminal, an IMS device and a core network device. The terminal can be used to execute the steps of the first terminal-side method described above. The IMS device can be used to execute the steps of the IMS device method described above. The core network device can be used to execute the steps of the core network device method described above.

[0426] It should be noted that in this document, the terms "comprising", "including", or any other variant thereof are intended to cover non-exclusive inclusions, so that processes, methods, articles or devices that include a series of elements not only include those elements, but also include other elements not explicitly listed, or include elements inherent to such processes, methods, articles or devices. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to the order of performing the functions shown or discussed, and can also include performing the functions in a substantially simultaneous manner or in reverse order, for example, the described method can be performed in an order different from that described, and various steps can also be added, omitted or combined. In addition, the features described with reference to certain examples can be combined in other examples.

[0427] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned method embodiments can be realized by means of computer software product and general hardware platform, of course, it can also be realized by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), which includes a plurality of instructions for making the terminal or network side device execute the method described in each embodiment of the present application.

[0428] The embodiments of the present application are described above with reference to the accompanying drawings, but the present application is not limited to the specific embodiments described above, and the specific embodiments described above are merely illustrative, but not restrictive, and a person of ordinary skill in the art can make many forms of implementation under the inspiration of the present application without departing from the purpose of the present application and the scope protected by the claims, and these implementations all belong to the protection of the present application.

Claims

1. A method for notification, the method comprising: receiving, by an Internet Protocol Multimedia System (IMS) device, a Session Initiation Protocol (SIP) INVITE message, the IMS device serving a first terminal, the SIP INVITE message carrying an identity of a second terminal; sending, by the IMS device, first information to a core network device based on the SIP INVITE message; wherein the first information comprises at least one of: the identity of the second terminal, the identity of the second terminal being used to determine whether to notify the first terminal using a first notification mode; first indication information, the first indication information being used to indicate that the first notification mode is used or allowed to be used to notify the first terminal.

2. The method of claim 1, wherein, the first notification mode is used to notify a terminal of at least one of: failure of a second notification mode to notify a terminal; an un-received call; an un-received message.

3. The method of claim 1 or 2, wherein, the first information comprises the first indication information; the sending, by the IMS device, of the first information to the core network device based on the SIP INVITE message comprises: in a case where the identity of the second terminal matches an identity of at least one third terminal, the IMS device sending the first indication information to the core network device, wherein each session initiated by the at least one third terminal with the first terminal allows the first notification mode to be used.

4. The method of claim 3, wherein, the first indication information comprises at least one of: indication information used to indicate that the first notification mode is used; indication information used to indicate that the first notification mode is allowed to be used; the identity of the second terminal.

5. The method of any one of claims 1 to 4, wherein, the core network device comprises a first core network device for processing user plane data; the sending, by the IMS device, of the first information to the core network device based on the SIP INVITE message comprises: the IMS device sending, based on the SIP INVITE message, downlink data to the first core network device, the downlink data comprising the first information.

6. The method of claim 5, wherein, the first information is at least one of: information in an Internet Protocol (IP) header of the downlink data; a specific Differentiated Services Code Point (DSCP) value; a specific parameter; a specific indication information.

7. The method of any one of claims 1 to 4, wherein, the core network device comprises a second core network device for policy control related; the sending, by the IMS device, of the first information to the core network device based on the SIP INVITE message comprises: the IMS device sending, based on the SIP INVITE message, first downlink signaling to the second core network device, the first downlink signaling comprising the first information.

8. The method of any one of claims 1 to 7, wherein, the sending, by the IMS device, of the first information to the core network device based on the SIP INVITE message comprises: in a case where a first condition is met, the IMS device sending the first information to the core network device based on the SIP INVITE message; wherein the first condition comprises any one of: a call or mobile terminal communication to the first terminal fails; a response of the first terminal is not received for a call or mobile terminal communication to the first terminal.

9. The method of any one of claims 1 to 8, wherein, the method further comprises: the IMS device obtaining an identity of at least one third terminal, wherein each session initiated by the at least one third terminal with the first terminal allows the first notification mode to be used.

10. The method of claim 9, wherein, The IMS device acquires the identity of at least one third terminal, comprising: The IMS device receives the SIP message sent by the first terminal, and the SIP message comprises the identity of the at least one third terminal; Or, The IMS device receives the subscription information of the first terminal sent by the third core network device, and the subscription information comprises the identity of the at least one third terminal, and the third core network device is a core network device in the core network device for managing user subscription data; Or, The IMS device acquires the identity of the at least one third terminal according to preconfigured information, and the preconfigured information is preconfigured in the IMS system.

11. A notification method, the method comprising: The core network device receives the first information sent by the IMS device; Wherein, the IMS device serves the first terminal, and the first information comprises at least one of the following: The identity of the second terminal, the identity of the second terminal is used to judge whether to use the first notification mode to notify the first terminal; First indication information, the first indication information is used to indicate that the first notification mode is used or allowed to notify the first terminal; Wherein, the first notification mode is a notification mode used or started in the case of failure of using the second notification mode to notify the terminal.

12. The method of claim 11, wherein, The failure of using the second notification mode to notify the terminal comprises at least one of the following: Paging terminal failure; Paging terminal N times, no response of terminal is received; Paging terminal for a specific time, no response of terminal is received; N times of notification or notification for a specific time on non-third generation partnership project 3GPP access, no response of terminal is received; Wherein, N is a positive integer.

13. The method of claim 11 or 12, wherein, The first notification mode is used to notify the terminal of at least one of the following: Failure of using the second notification mode to notify the terminal; Unreceived call; Unreceived message.

14. The method of claim 13, wherein, The first indication information comprises at least one of the following: Indication information for indicating the use of the first notification mode; Indication information for indicating the permission to use the first notification mode; The identity of the second terminal.

15. The method of any one of claims 11 to 14, wherein, The core network device comprises a first core network device for processing user plane data; The core network device receives the first information sent by the IMS device, comprising: The first core network device receives the downlink data sent by the IMS device, and the downlink data comprises the first information.

16. The method of claim 15, wherein, The first information is at least one of the following: Information in the IP header of the downlink data; Specific DSCP value; Specific parameter; Specific indication information.

17. The method of claim 15 or 16, wherein, The core network device further comprises a fourth core network device for controlling session management and a fifth core network device for access and mobility management; After the first core network device receives the downlink data sent by the IMS device, the method further comprises: The first core network device sends the downlink data notification to the fourth core network device, and the downlink data notification comprises the first information; After receiving the downlink data notification, the fourth core network device sends the third downlink signaling to the fifth core network device, and the third downlink signaling comprises the first information.

18. The method of any one of claims 11 to 14, wherein, The core network device comprises a second core network device for policy control related; The core network device receives first information sent by an IMS device, comprising: The second core network device receives first downlink signaling sent by the IMS device, and the first downlink signaling comprises the first information.

19. The method of claim 18, wherein, The core network device further comprises a fourth core network device for controlling session management, and a fifth core network device for access and mobility management; After the second core network device receives the first downlink signaling sent by the IMS device, the method further comprises: The second core network device sends second downlink signaling to the fourth core network device, and the second downlink signaling comprises the first information; Upon receiving the second downlink signaling, the fourth core network device sends third downlink signaling to the fifth core network device, and the third downlink signaling comprises the first information.

20. The method of claim 17 or 19, wherein, The method further comprises: Upon receiving the third downlink signaling, the fifth core network device notifies the first terminal using the first notification mode according to the first information.

21. The method of claim 20, wherein, The first information comprises the first indication information; The fifth core network device notifies the first terminal using the first notification mode according to the first information, comprising: If the first terminal fails to be notified using the second notification mode, the fifth core network device notifies the first terminal using the first notification mode according to the first indication information.

22. The method of claim 20, wherein, The first information comprises an identifier of the second terminal; The fifth core network device notifies the first terminal using the first notification mode according to the first information, comprising: If the first terminal fails to be notified using the second notification mode, and the identifier of the second terminal matches an identifier of at least one third terminal, the fifth core network device notifies the first terminal using the first notification mode, wherein each session initiated by the third terminal to the first terminal allows the first notification mode to be used.

23. The method of claim 22, wherein, Before the fifth core network device notifies the first terminal using the first notification mode, the method further comprises: The fifth core network device receives the identifier of the at least one third terminal sent by a third core network device, and the third core network device is a core network device in the core network device for managing user subscription data.

24. The method of claim 20, wherein, The fifth core network device notifies the first terminal using the first notification mode according to the first information, comprising: If the first information comprises the first indication information, and the first indication information comprises indication information for indicating the use of the first notification mode, the fifth core network device notifies the first terminal using the first notification mode.

25. The method of any one of claims 11 to 24, wherein, The core network device comprises a third core network device for managing user subscription data, and a fifth core network device for access and mobility management; Before the core network device receives first information sent by an IMS device, the method further comprises: The third core network device sends the subscription information of the first terminal to the IMS device or the fifth core network device, wherein the subscription information comprises an identifier of at least one third terminal, and each session initiated by the third terminal to the first terminal is allowed to use the first notification mode.

26. The method of claim 25, wherein, Before the third core network device sends the subscription information of the first terminal to the IMS device or the fifth core network device, the method further comprises: The third core network device receives the identifier of the at least one third terminal sent by the first terminal.

27. A notification method, the method comprising: A first terminal sends an identifier of at least one third terminal to a network side device; Wherein each session initiated by the third terminal to the first terminal is allowed to use a first notification mode, and the network side device comprises at least one of an IMS device and a core network device.

28. The method of claim 27, wherein, The first notification mode is used to notify the terminal of at least one of the following: Failure to notify the terminal using a second notification mode; Unreceived call; Unreceived message.

29. The method of claim 27 or 28, wherein, The network side device comprises the IMS device; The first terminal sends an identifier of at least one third terminal to a network side device, comprising: The first terminal sends a SIP message to the IMS device, and the SIP message comprises the identifier of the at least one third terminal.

30. The method of claim 27 or 28, wherein, The network side device comprises the core network device, and the core network device comprises a third core network device for managing user subscription data; The first terminal sends an identifier of at least one third terminal to a network side device, comprising: The first terminal sends a non-access stratum (NAS) message to the third core network device, and the NAS message comprises the identifier of the at least one third terminal.

31. The method of claim 30, wherein, The core network device further comprises a fifth core network device for access and mobility management; The first terminal sends a NAS message to the third core network device, comprising: The first terminal sends the NAS message to the third core network device through the fifth core network device.

32. A notifying apparatus, applied to an IMS device, the apparatus comprising: A first receiving module and a first sending module; The first receiving module is configured to receive a SIP invitation message, the IMS device serves a first terminal, and the SIP invitation message carries an identifier of a second terminal; The first sending module is configured to send first information to a core network device based on the SIP invitation message; The first information comprises at least one of the following: The identifier of the second terminal, which is used to determine whether to notify the first terminal using a first notification mode; First indication information, which is used to indicate that the first notification mode is used or allowed to be used to notify the first terminal.

33. The apparatus of claim 32, wherein, The first information comprises the first indication information; The first sending module is configured to send the first indication information to the core network device in a case where the identifier of the second terminal matches an identifier of at least one third terminal, and each session initiated by the third terminal to the first terminal is allowed to use the first notification mode.

34. The apparatus of claim 32, wherein, The core network device comprises a first core network device for processing user plane data; The first sending module is configured to send, based on the SIP invitation message, downlink data to the first core network device, wherein the downlink data comprises the first information.

35. The apparatus of claim 32, wherein, The core network device comprises a second core network device related to policy control; The first sending module is configured to send, based on the SIP invitation message, first downlink signaling to the second core network device, wherein the first downlink signaling comprises the first information.

36. The apparatus according to any one of claims 32 to 35, wherein, The first sending module is configured to send, based on the SIP invitation message, the first information to the core network device when a first condition is met. The first condition comprises any one of the following: A call or mobile terminal communication to the first terminal fails. A response of the first terminal is not received for a call or mobile terminal communication to the first terminal.

37. A notification apparatus, the apparatus comprising a second receiving module; The second receiving module is configured to receive first information sent by an IMS device, wherein the IMS device serves a first terminal, and the first information comprises at least one of the following: wherein An identifier of a second terminal, wherein the identifier of the second terminal is used to determine whether a first notification mode is used to notify the first terminal; First indication information, wherein the first indication information is used to indicate that the first notification mode is used or allowed to notify the first terminal. The second receiving module is configured to receive downlink data sent by the IMS device, wherein the downlink data comprises the first information. The second receiving module is configured to receive first downlink signaling sent by the IMS device, wherein the first downlink signaling comprises the first information.

38. The apparatus of claim 37, wherein, 40. A notification apparatus, the apparatus comprising a third sending module; 39. The device of claim 37, wherein, The third sending module is configured to send an identifier of at least one third terminal to a network side device, wherein each session initiated by the at least one third terminal to a first terminal allows a first notification mode, and the network side device comprises at least one of an IMS device and a core network device. The network side device comprises the IMS device; The third sending module is configured to send a SIP message to the IMS device, wherein the SIP message comprises the identifier of the at least one third terminal. wherein A processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement steps of the notification method according to any one of claims 27 to 31.

41. The apparatus of claim 40, wherein, A processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement steps of the notification method according to any one of claims 1 to 10, or implement steps of the notification method according to any one of claims 11 to 26. ​ 42. A terminal, characterized by ​ 43. A network-side device, comprising: ​ 44. A readable storage medium, on which a computer program is stored, the computer program being executed by a processor to implement the steps of the notification method according to any one of claims 1 to 10, or to implement the steps of the notification method according to any one of claims 11 to 26, or to implement the steps of the notification method according to any one of claims 27 to 31.

45. A computer program product, which is executed by at least one processor to implement the steps of the notification method according to any one of claims 1 to 10, or to implement the steps of the notification method according to any one of claims 11 to 26, or to implement the steps of the notification method according to any one of claims 27 to 31.

46. An electronic device, which is configured to implement the steps of the notification method according to any one of claims 1 to 10, or to implement the steps of the notification method according to any one of claims 11 to 26, or to implement the steps of the notification method according to any one of claims 27 to 31.

47. A chip, which comprises a processor and a communication interface, the communication interface and the processor being coupled, the processor being configured to run a program or an instruction to implement the steps of the notification method according to any one of claims 1 to 10, or to implement the steps of the notification method according to any one of claims 11 to 26, or to implement the steps of the notification method according to any one of claims 27 to 31.

Images