Communication method and communication apparatus

Abstract

The present application provides a communication method, comprising: an event subscription entity subscribes to a first event with a first event notification entity on the basis of interaction with a user data storage network element, wherein the first event is an event related to an IMS session of a first user; and the event subscription entity receives a first event notification request message sent by the first event notification entity, wherein the first event notification request message comprises information of the first event. An event for a particular user can be subscribed to with an IMS AS instance serving said user.

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 3, 2023, with application number 202311468978.6 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular, to a communication method and a communication device. Background Art

[0003] If there are multiple network function (NF) service producer instances in the network, when an NF service consumer subscribes to a specific user's events from an NF service producer, it must first determine which NF service producer instance provides services for the user, so as to send an event subscription request for the user to the NF service producer instance.

[0004] An IP multimedia subsystem (IMS) network typically has multiple IMS application server (AS) instances providing the same service to different users. However, these IMS AS instances are not bound to the IMS users they serve. In other words, it's impossible to directly locate the IMS AS instance serving a user using an IMS user ID.

[0005] How to subscribe the event notification entity serving a specific user to the events of that user is an urgent problem to be solved.

[0006] Summary of the Invention

[0007] The present application provides a communication method and a communication device, which can enable an event notification entity serving a specific user to subscribe to the user's events.

[0008] In a first aspect, a communication method is provided. The method may be executed by an event subscription entity, or may be executed by a module (e.g., a chip or circuit) of the event subscription entity, without limitation. For ease of description, the following description is based on an example of execution by an event subscription entity.

[0009] The method may include: an event subscription entity subscribing to a first event to a first event notification entity based on the interaction between the event subscription entity and a user data storage network element, where the first event is an event related to the IMS session of the first user; the event subscription entity receiving a first event notification request message sent by the first event notification entity, where the first event notification request message includes information about the first event.

[0010] Through the above solution, the event subscription entity subscribes to the event of a specific user to the event notification entity serving the specific user based on the interaction with the user data storage network element.

[0011] It should be understood that the event subscription entity may subscribe to the first event directly from the first event notification entity; or the event subscription entity may subscribe to the first event indirectly from the first event notification entity, such as the event subscription entity subscribing to the first event from the first event notification entity based on a proxy network element (e.g., a user data storage network element). For example, the event subscription entity subscribes to the first event from the user data storage network element, and the user data storage network element then subscribes to the first event from the first event notification entity.

[0012] Optionally, the event subscription entity subscribes to the first event to the first event notification entity, which refers to subscribing to a trigger condition of the first event; the event subscription entity receives the first event notification request message sent by the first event notification entity, and the first event notification request message includes information about the first event, and the information about the first event is an instance of the first event.

[0013] In combination with the first aspect, in some implementation methods of the first aspect, the event subscription entity subscribes to the first event to the first event notification entity based on the interaction between the event subscription entity and the user data storage network element, including: the event subscription entity sends first subscription information to the user data storage network element, and the first subscription information is used to subscribe to information about the first event.

[0014] Through the above solution, the event subscription entity sends subscription-related information to the user data storage network element. When the first event notification entity obtains the subscription-related information, it can start monitoring the first event.

[0015] In a possible implementation, the first subscription information includes a user identifier of the first user, an identifier of the first event, and a notification endpoint, where the notification endpoint identifies an address of a network element that receives a first event notification request message.

[0016] In a possible implementation manner, the network element that receives the first event notification request message is an event subscription entity.

[0017] In another possible implementation, the network element that receives the first event notification request message is another network element, and the event subscription entity subscribes to the first event from the first event notification entity on behalf of the other network element.

[0018] In a possible implementation, the event subscription entity sends the first subscription information to the user data storage network element, including: the event subscription entity sends an IMS user data management update request message to the user data storage network element, where the IMS user data management update request message includes the first subscription information.

[0019] In a possible implementation, the method further includes: the event subscription entity generating first subscription information.

[0020] In a possible implementation manner, the method further includes: the event subscription entity sending first subscription information deletion request information to the user data storage network element, where the first subscription information deletion request information is used to request deletion of the first subscription information.

[0021] Optionally, the event subscription entity sends an IMS user data management update request message or an IMS user data management deletion request message to the user data storage network element, where the IMS user data management update request message or the IMS user data management deletion request message includes first subscription information deletion request information.

[0022] In combination with the first aspect, in some implementation methods of the first aspect, the event subscription entity subscribes to the first event to the first event notification entity based on the interaction between the event subscription entity and the user data storage network element, including: the event subscription entity receives a first address sent by the user data storage network element, where the first address is the address of the first event notification entity; the event subscription entity sends a first event subscription request message to the first event notification entity based on the received first address, where the first event subscription request message is used to subscribe to information about the first event.

[0023] In a possible implementation manner, the event subscription entity sends first request information to the user data storage network element, where the first request information is used to request to obtain the first address.

[0024] In a possible implementation manner, the event subscription entity sends an IMS user data management acquisition request message to the user data storage network element, where the IMS user data management acquisition request message includes first request information.

[0025] In a possible implementation manner, the event subscription entity receives an IMS user data management acquisition response message sent by the user data storage network element, where the IMS user data management acquisition response message includes the first address.

[0026] Through the above solution, the first event notification entity stores its own address in the user data storage network element, so that the event subscription entity can obtain the address and initiate a subscription to the first event notification entity based on the address.

[0027] In another possible implementation, the event subscription entity indirectly sends an event subscription request message to the first event notification entity through the user data storage network element, including: the event subscription entity sends a first event subscription request message to the user data storage network element, and the first event subscription request message is used to subscribe to information about the first event from the user data storage network element; and the user data storage network element sends a second event subscription request message to the first event notification entity, and the second event subscription request message is used to subscribe to information about the first event from the first event notification entity.

[0028] In a possible implementation, the method further includes: the event subscription entity receiving a first event subscription response message from the first event notification entity, where the first event subscription response message is used to indicate that the first event has been successfully subscribed.

[0029] In another possible implementation, the event subscription entity indirectly receives an event subscription response message from the first event notification entity through a user data storage network element, including: first, the user data storage network element receives a second event subscription response message sent by the first event notification entity, and the second event subscription response message is used to indicate that the first event is successfully subscribed to the first event notification entity; and then the user data storage network element sends a first event subscription response message to the event subscription entity, and the first event subscription request message is used to indicate that the first event is successfully subscribed to the user data storage network element.

[0030] In a possible implementation, the method further includes: the event subscription entity sending a first event unsubscription request message to the first event notification entity, where the first event unsubscription request message is used to request cancellation of subscription to the first event.

[0031] In another possible implementation, the event subscription entity indirectly sends an event unsubscription request message to the first event notification entity through the user data storage network element, including: the event subscription entity sends a first event unsubscription request message to the user data storage network element, and the first event unsubscription request message is used to request to cancel the subscription to the first event; and the user data storage network element sends a second event unsubscription request message to the first event notification entity, and the second event unsubscription request message is used to request to cancel the subscription to the first event.

[0032] In a possible implementation, the method further includes: the event subscription entity receiving a first event unsubscription response message from the first event notification entity, where the first event unsubscription response message is used to indicate that the subscription to the first event has been canceled.

[0033] In another possible implementation, the event subscription entity indirectly receives an event unsubscription response message from the first event notification entity through a user data storage network element, including: first, the user data storage network element receives a second event unsubscription response message sent by the first event notification entity, and the second event unsubscription response message is used to indicate that the subscription to the first event has been canceled; and then the user data storage network element sends a first event unsubscription response message to the event subscription entity, and the first event unsubscription response message is used to indicate that the first event has been successfully unsubscribed in the user data storage network element.

[0034] In a possible implementation, the method further includes: the event subscription entity receiving a second address sent by the user data storage network element, where the second address is the address of a second event notification entity, and the second event notification entity is used to monitor information about the first event.

[0035] In a possible implementation, the method further includes: the event subscription entity sending a first event notification response message to the first event notification entity, where the first event notification response message is used to indicate that the event subscription entity has successfully received the first event notification request message.

[0036] In some of the above-mentioned implementations, the event subscription entity needs to interact with the user data storage network element for data (the event subscription entity sends data to the user data storage network element or receives data sent by the user data storage network element), and the event subscription entity needs to interact with the first event notification entity for data (the event subscription entity sends data to the first event notification entity or receives data sent by the first event notification entity).

[0037] In one possible implementation, the event subscription entity is a data channel application server, which indirectly interacts with the user data storage network element through the data channel signaling server, and indirectly interacts with the first event notification entity through the data channel signaling server. That is, the data channel application server calls the service of the data channel signaling server, and the data channel signaling server interacts with the first event notification entity as an event subscriber.

[0038] In another possible implementation, the event subscription entity is a capability open network element, which can directly interact with the user data storage network element and directly subscribe to the first event to the first event notification entity; or, the capability open network element can indirectly interact with the user data storage network element through a data channel signaling server, and indirectly subscribe to the first event to the first event notification entity through the data channel signaling server, that is, the capability open network element calls the event subscription service of the data channel signaling server, and the data channel signaling server interacts with the user data storage network element as an event subscriber, and the data channel signaling server interacts with the first event notification entity as an event subscriber.

[0039] In another possible implementation, the event subscription entity is a data channel signaling server. The data channel signaling server can directly interact with the user data storage network element based on the subscription-related information obtained from the capability exposure network element or the data channel application server, and directly subscribe to the first event to the first event notification entity.

[0040] In a second aspect, a communication method is provided. The method may be executed by an event notification entity, or by a module (e.g., a chip or circuit) of the event notification entity, without limitation. For ease of description, the following description will be based on an example of execution by the event notification entity.

[0041] The method may include: the first event notification entity obtains the subscription of the event subscription entity to the first event based on the interaction between the first event notification entity and the user data storage network element, where the first event is an event related to the IMS session of the first user; the first event notification entity sends a first event notification request message, and the first event notification request message includes information about the first event.

[0042] Through the above solution, the event subscription entity subscribes to the event of a specific user to the event notification entity serving the specific user based on the interaction with the user data storage network element.

[0043] In combination with the second aspect, in some implementation methods of the second aspect, the first event notification entity obtains the event subscription entity's subscription to the first event based on the interaction between the first event notification entity and the user data storage network element, including: the first event notification entity obtains first subscription information at the user data storage network element, and the first subscription information is used to subscribe to information about the first event.

[0044] Through the above solution, the event subscription entity sends subscription-related information to the user data storage network element. When the first event notification entity obtains the subscription-related information, it can start monitoring the first event.

[0045] In one possible implementation, the first event notification entity obtains the first subscription information at the user data storage network element, including: the first event notification entity obtains the user data information of the first user at the user data storage network element, and the user data information of the first user includes the first subscription information; or the first event notification entity receives the first subscription information sent by the user data storage network element.

[0046] Optionally, the first event notification entity obtains an IMS user data management acquisition request message at a user data storage network element, where the IMS user data management acquisition request message includes user data information of the first user.

[0047] In a possible implementation, the method further includes: according to the first subscription information, the first event notification entity monitors the first event.

[0048] In a possible implementation manner, the method further includes: the first event notification entity sending a first event notification request message according to the notification endpoint.

[0049] In a possible implementation, the first subscription information includes a user identifier of the first user, an identifier of the first event, and a notification endpoint, where the notification endpoint identifies an address of a network element that receives a first event notification request message.

[0050] In a possible implementation manner, the network element that receives the first event notification request message is an event subscription entity.

[0051] In a possible implementation, the first event notification entity monitors the first event according to the first subscription information, including: the first event notification entity monitors the first event according to an identifier of the first event.

[0052] In a possible implementation, the first event notification entity sends a first event notification request message to the event subscription entity, including: the first event notification entity sends the first event notification request message to the event subscription entity according to the notification endpoint.

[0053] In a possible implementation, the method further includes: the first event notification entity receiving notification information of first event subscription deletion sent by the user data storage network element, where the notification information of first event subscription deletion is used to notify that the first subscription information has been deleted.

[0054] Optionally, the first event notification entity receives an IMS user data management notification request message sent by the user data storage network element, where the IMS user data management notification request message includes notification information of deletion of the first event subscription.

[0055] In combination with the second aspect, in some implementation methods of the second aspect, the first event notification entity obtains the subscription of the event subscription entity to the first event based on the interaction between the first event notification entity and the user data storage network element, including: the first event notification entity sends a first address and an identifier of the first user to the user data storage network element, where the first address is the address of the first event notification entity; the first event notification entity receives a first event subscription request message sent by the event subscription entity, where the first event subscription request message is used to request subscription to the first event.

[0056] Through the above solution, the first event notification entity stores its own address in the user data storage network element, so that the event subscription entity can obtain the address and initiate a subscription to the first event notification entity based on the address.

[0057] In another possible implementation, the first event notification entity indirectly receives an event subscription request message from the event subscription entity through a user data storage network element, including: first, the user data storage network element receives a first event subscription request message sent by the event subscription entity, and the first event subscription request message is used to subscribe to information about the first event from the user data storage network element; then, the user data storage network element sends a second event subscription request message to the first event notification entity, and the second event subscription request message is used to subscribe to information about the first event from the first event notification entity.

[0058] In a possible implementation manner, the first event notification entity sends an IMS user data management update request message to the user data storage network element, where the IMS user data management update request message includes the first address and an identifier of the first user.

[0059] In a possible implementation, the method further includes: the first event notification entity sending a first event subscription response message to the event subscription entity, where the first event subscription response message is used to indicate that the first event has been successfully subscribed.

[0060] In another possible implementation, the first event notification entity indirectly sends an event subscription response message to the event subscription entity through the user data storage network element, including: the first event notification entity sends a second event subscription response message to the user data storage network element, and the second event subscription response message is used to indicate that the first event has been successfully subscribed to the first event notification entity; and then the user data storage network element sends a first event subscription response message to the event subscription entity, and the first event subscription request message is used to indicate that the first event has been successfully subscribed to the user data storage network element.

[0061] In a possible implementation, the method further includes: the first event notification entity receiving a first event unsubscribe request message from the event subscription entity, where the first event unsubscribe request message is used to request to cancel subscription to the first event.

[0062] In another possible implementation, the first event notification entity indirectly receives an event unsubscription request message from the event subscription entity through a user data storage network element, including: first, the user data storage network element receives a first event unsubscription request message sent by the event subscription entity, and the first event subscription request message is used to request cancellation of the subscription to the first event; and the user data storage network element sends a second event unsubscription request message to the first event notification entity, and the second event unsubscription request message is used to request cancellation of the subscription to the first event.

[0063] In a possible implementation, the method further includes: the first event notification entity sending a first event unsubscribe response message to the event subscription entity, where the first event unsubscribe response message is used to indicate that the subscription to the first event has been canceled.

[0064] In another possible implementation, the first event notification entity indirectly sends an event unsubscription response message to the event subscription entity through the user data storage network element, including: the first event notification entity sends a second event unsubscription response message to the user data storage network element, and the second event unsubscription response message is used to indicate that the subscription to the first event has been canceled; and then the user data storage network element sends a first event unsubscription response message to the event subscription entity, and the first event subscription request message is used to indicate that the subscription to the first event has been canceled.

[0065] In a possible implementation, the method further includes: the first event notification entity receiving a first event notification response message from the event subscription entity, where the first event notification response message is used to indicate that the event subscription entity has successfully received the first event notification request message.

[0066] In a third aspect, a communication method is provided. The method can be executed by a user data storage network element, or can also be executed by a module (such as a chip or circuit) of the user data storage network element, without limitation. For ease of description, the following description is based on an example of execution by a user data storage network element.

[0067] The method may include: a user data storage network element receives first subscription information from an event subscription entity, the first subscription information is used to subscribe to information of a first event, the first event is an event related to the IMS session of the first user, and the first event is monitored by a first event notification entity; the user data storage network element sends the first subscription information or user data information of the first user to the first event notification entity, and the user data information of the first user includes the first subscription information.

[0068] In a possible implementation manner, the user data storage network element receives an IMS user data management update request message from an event subscription entity, where the IMS user data management update request message includes the first subscription information.

[0069] In one possible implementation, the first subscription information includes the user identifier of the first user, the identifier of the first event and a notification endpoint, the notification endpoint identifies the network element address for receiving the first event notification request message, and the first event notification request message includes information about the first event.

[0070] In a possible implementation, the method further includes: the user data storage network element receiving first subscription information deletion request information, the first subscription information deletion request information being used to request deletion of the first subscription information; and the user data storage network element deleting the first subscription information from the user data information of the first user.

[0071] Optionally, the user data storage network element receives an IMS user data management update request message or an IMS user data management deletion request message from the event subscription entity, where the IMS user data management update request message or the IMS user data management deletion request message includes first subscription information deletion request information.

[0072] In a possible implementation, the method further includes: the user data storage network element sending notification information of first event subscription deletion to the first event notification entity, where the notification information of first event subscription deletion is used to indicate that the first subscription information has been deleted.

[0073] Optionally, the user data storage network element sends an IMS user data management notification request message to the first event notification entity, where the IMS user data management notification request message includes notification information of deletion of the first event subscription.

[0074] In a fourth aspect, a communication method is provided. The method can be executed by a user data storage network element, or can also be executed by a module (such as a chip or circuit) of the user data storage network element, without limitation. For ease of description, the following description is based on an example of execution by a user data storage network element.

[0075] The method may include: a user data storage network element receives a first request message from an event subscription entity, the first request message is used to request a first address, the first address is the address of a first event notification entity, and the first event notification entity is used to monitor a first event of a first user subscribed to by the event subscription entity; the user data storage network element sends the first address to the event subscription entity.

[0076] Through the above solution, the first event notification entity stores its own address in the user data storage network element, so that the event subscription entity can obtain the address and initiate a subscription to the first event notification entity based on the address.

[0077] In a possible implementation manner, the user data storage network element receives an IMS user data management acquisition request message from an event subscription entity, where the IMS user data management acquisition request message includes first request information.

[0078] In a possible implementation manner, the user data storage network element sends an IMS user data management acquisition response message to the event subscription entity, where the IMS user data management acquisition response message includes the first address.

[0079] In a possible implementation, the method further includes: the user data storage network element receiving the first address and the identifier of the first user from the first event notification entity; and the user data storage network element storing the first address in the user data information of the first user according to the identifier of the first user.

[0080] In a possible implementation manner, the user data storage network element receives an IMS user management update request message from the first event notification entity, where the IMS user management update request message includes the first address and an identifier of the first user.

[0081] In a possible implementation, the method also includes: the user data storage network element receives first event subscription request information sent by the event subscription entity, and the first event subscription request information is used to request subscription to the first event; the user data storage network element sends second event subscription request information to the first event notification entity, and the second event subscription request information is used to request subscription to the first event.

[0082] In a possible implementation, the method also includes: the user data storage network element receives a second event subscription response message sent by the first event notification entity, the second event subscription response message is used to indicate that the first event has been successfully subscribed; the user data storage network element sends a first event subscription response message to the event subscription entity, the first event subscription response message is used to indicate that the first event has been successfully subscribed.

[0083] In a possible implementation, the method also includes: the user data storage network element receives a first event unsubscribe request message sent by the event subscription entity, the first event unsubscribe request message is used to request cancellation of the subscription to the first event; the user data storage network element sends a second event unsubscribe request message to the first event notification entity.

[0084] In one possible implementation, the method also includes: the user data storage network element receives a second event unsubscription response message sent by the first event notification entity, the second event unsubscription response message is used to indicate that the subscription to the first event has been canceled; the user data storage network element sends a first event unsubscription response message to the event subscription entity, the first event unsubscription response message is used to indicate that the subscription to the first event has been canceled.

[0085] In a possible implementation, the method further includes: the user data storage network element sending a second address to the event subscription entity, where the second address is the address of a second event notification entity, and the second event notification entity is used to monitor information about the first event.

[0086] In a fifth aspect, a communication method is provided. The method can be executed by a communication system, or can also be executed by a module (such as a chip or circuit) arranged in the communication system, without limitation. The communication system may include: an event subscription entity, a user data storage network element, and a first event notification entity. For ease of description, the following description is based on an example of an event subscription entity, a user data storage network element, and a first event notification entity.

[0087] The method may include: based on the interaction between the event subscription entity and the first event notification entity and the user data storage network element, enabling the event subscription entity to subscribe to the first event notification entity for a first event, where the first event is an event related to the IMS session of the first user; the first event notification entity sends a first event notification request message, where the first event notification request message includes information about the first event.

[0088] In combination with the fifth aspect, in some implementation methods of the fifth aspect, based on the interaction between the event subscription entity and the first event notification entity and the user data storage network element, the event subscription entity subscribes to the first event notification entity for the first event, including: the event subscription entity sends the first subscription information to the user data storage network element, and the first subscription information is used to subscribe to the information of the first event; the user data storage network element sends the first subscription information or the user data information of the first user to the first event notification entity, and the user data information of the first user includes the first subscription information.

[0089] In a possible implementation, the event subscription entity sends the first subscription information to the user data storage network element, including: the event subscription entity sends an IMS user data management update request message to the user data storage network element, where the IMS user data management update request message includes the first subscription information.

[0090] In a possible implementation, the first subscription information includes a user identifier of the first user, an identifier of the first event, and a notification endpoint, where the notification endpoint identifies an address of a network element that receives a first event notification request message.

[0091] In a possible implementation manner, the network element that receives the first event notification request message is an event subscription entity.

[0092] In another possible implementation, the network element that receives the first event notification request message is another network element, and the event subscription entity subscribes to the first event from the first event notification entity on behalf of the other network element.

[0093] In one possible implementation, the first event notification entity obtains the first subscription information at the user data storage network element, including: the first event notification entity obtains the user data information of the first user at the user data storage network element, and the user data information of the first user includes the first subscription information; or the first event notification entity receives the first subscription information sent by the user data storage network element.

[0094] In one possible implementation, the first event notification entity obtains user data information of the first user at the user data storage network element, including: the first event notification entity obtains an IMS user data management acquisition request message at the user data storage network element, and the IMS user data management acquisition request message includes the user data information of the first user.

[0095] In a possible implementation, the method further includes: the event subscription entity generating first subscription information.

[0096] In a possible implementation manner, the method further includes: the first event notification entity monitoring the first event according to the first subscription information.

[0097] In a possible implementation, the first event notification entity monitors the first event according to the first subscription information, including: the first event notification entity monitors the first event according to an identifier of the first event.

[0098] In a possible implementation manner, the method further includes: the first event notification entity sending a first event notification request message according to the notification endpoint.

[0099] Optionally, the first event notification entity sends a first event notification request message to the event subscription entity according to the notification endpoint.

[0100] In a possible implementation, the method also includes: the event subscription entity sends a first subscription information deletion request message to the user data storage network element, and the first subscription information deletion request message is used to request deletion of the first subscription information; the user data storage network element deletes the first subscription information in the user data information of the first user; the user data storage network element sends a first event subscription deletion notification message to the first event notification entity, and the first event subscription deletion notification message is used to notify that the first subscription information has been deleted.

[0101] In a possible implementation, the event subscription entity sends an IMS user data management update request message or an IMS user data management deletion request message to the user data storage network element, where the IMS user data management update request message or the IMS user data management deletion request message includes first subscription information deletion request information.

[0102] In a possible implementation manner, the user data storage network element sends an IMS user data management notification request message to the first event notification entity. The IMS user data management notification request message includes notification information of deletion of the first event subscription.

[0103] In combination with the fifth aspect, in some implementation methods of the fifth aspect, based on the interaction between the event subscription entity and the first event notification entity and the user data storage network element, the event subscription entity subscribes to the first event notification entity for the first event, including: the first event notification entity sends a first address and an identifier of the first user to the user data storage network element, where the first address is the address of the first event notification entity; the user data storage network element sends the first address to the event subscription entity; the event subscription entity sends a first event subscription request message to the first event notification entity based on the received first address, where the first event subscription request message is used to subscribe to information about the first event.

[0104] In another possible implementation, the event subscription entity indirectly sends an event subscription request message to the first event notification entity through the user data storage network element, including: the event subscription entity sends a first event subscription request message to the user data storage network element, and the first event subscription request message is used to subscribe to information about the first event from the user data storage network element; and the user data storage network element sends a second event subscription request message to the first event notification entity, and the second event subscription request message is used to subscribe to information about the first event from the first event notification entity.

[0105] In a possible implementation manner, the event subscription entity sends first request information to the user data storage network element, where the first request information is used to request to obtain the first address.

[0106] In a possible implementation manner, the event subscription entity sends an IMS user data management acquisition request message to the user data storage network element, where the IMS user data management acquisition request message includes first request information.

[0107] In a possible implementation manner, the first event notification entity sends an IMS user data management update request message to the user data storage network element, where the IMS user data management update request message includes the first address and an identifier of the first user.

[0108] In a possible implementation manner, the user data storage network element sends an IMS user data management acquisition response message to the event subscription entity, where the IMS user data management acquisition response message includes the first address.

[0109] In a possible implementation, the method further includes: the first event notification entity sending a first event subscription response message to the event subscription entity, where the first event subscription response message is used to indicate that the first event has been successfully subscribed.

[0110] In another possible implementation, the first event notification entity indirectly sends an event subscription response message to the event subscription entity through the user data storage network element, including: the first event notification entity sends a second event subscription response message to the user data storage network element, and the second event subscription response message is used to indicate that the first event is successfully subscribed to the first event notification entity; and the user data storage network element sends a first event subscription response message to the event subscription entity, and the first event subscription request message is used to indicate that the first event is successfully subscribed to the user data storage network element.

[0111] In a possible implementation, the method further includes: the event subscription entity sending a first event unsubscription request message to the first event notification entity, where the first event unsubscription request message is used to request cancellation of subscription to the first event.

[0112] In another possible implementation, the event subscription entity indirectly sends an event unsubscription request message to the first event notification entity through the user data storage network element, including: the event subscription entity sends a first event unsubscription request message to the user data storage network element, and the first event unsubscription request message is used to request to cancel the subscription to the first event; and the user data storage network element sends a second event unsubscription request message to the first event notification entity, and the second event unsubscription request message is used to request to cancel the subscription to the first event.

[0113] In a possible implementation, the method further includes: the first event notification entity sending a first event unsubscribe response message to the event subscription entity, where the first event unsubscribe response message is used to indicate that the subscription to the first event has been canceled.

[0114] In another possible implementation, the first event notification entity indirectly sends an event unsubscription response message to the event subscription entity through the user data storage network element, including: the first event notification entity sends a second event unsubscription response message to the user data storage network element, and the second event unsubscription response message is used to indicate that the subscription to the first event has been canceled; and then the user data storage network element sends a first event unsubscription response message to the event subscription entity, and the first event unsubscription response message is used to indicate that the first event has been successfully unsubscribed in the user data storage network element.

[0115] In a possible implementation, the method further includes: the user data storage network element sending a second address to the event subscription entity, where the second address is the address of a second event notification entity, and the second event notification entity is used to monitor information about the first event.

[0116] In a possible implementation, the method further includes: the event subscription entity sending a first event notification response message to the first event notification entity, where the first event notification response message is used to indicate that the event subscription entity has successfully received the first event notification request message.

[0117] In some of the above-mentioned implementations, the event subscription entity needs to interact with the user data storage network element for data (the event subscription entity sends data to the user data storage network element or receives data sent by the user data storage network element), and the event subscription entity needs to interact with the first event notification entity for data (the event subscription entity sends data to the first event notification entity or receives data sent by the first event notification entity).

[0118] In one possible implementation, the event subscription entity is a data channel application server, which indirectly interacts with the user data storage network element through the data channel signaling server, and indirectly interacts with the first event notification entity through the data channel signaling server. That is, the data channel application server calls the event subscription service of the data channel signaling server, and the data channel signaling server interacts with the user data storage network element as an event reader, and the data channel signaling server interacts with the first event notification entity as an event subscriber.

[0119] In another possible implementation, the event subscription entity is a capability open network element, which can directly interact with the user data storage network element and directly subscribe to the first event to the first event notification entity; or, the capability open network element can indirectly interact with the user data storage network element through a data channel signaling server, and indirectly subscribe to the first event to the first event notification entity through the data channel signaling server, that is, the capability open network element calls the event subscription service of the data channel signaling server, and the data channel signaling server interacts with the user data storage network element as an event subscriber, and the data channel signaling server interacts with the first event notification entity as an event subscriber.

[0120] In another possible implementation, the event subscription entity is a data channel signaling server. The data channel signaling server can directly interact with the user data storage network element based on the subscription-related information obtained from the capability exposure network element or the data channel application server, and directly subscribe to the first event to the first event notification entity.

[0121] In a sixth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the first aspect or any possible implementation of the first aspect.

[0122] In a seventh aspect, a wireless communication device is provided, comprising modules or units for executing the method in the second aspect or any possible implementation of the second aspect.

[0123] In an eighth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the third aspect or any possible implementation of the third aspect.

[0124] In a ninth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the fourth aspect or any possible implementation of the fourth aspect.

[0125] In a tenth aspect, a communication device is provided, comprising a processor coupled to a memory and configured to execute the method of the first aspect and possible implementations thereof. In one possible implementation, the communication device further comprises a memory. In one possible implementation, the communication device further comprises a communication interface, the processor coupled to the communication interface. In another possible implementation, the communication device further comprises a communication interface, the processor coupled to the communication interface.

[0126] In one implementation, the communication device is an event subscription entity. When the communication device is an event subscription entity, the communication interface may be a transceiver, or an input / output interface.

[0127] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0128] In an eleventh aspect, a communication device is provided, comprising a processor coupled to a memory and configured to execute instructions in the memory to implement the method of the third aspect and possible implementations thereof or the fourth aspect and possible implementations thereof. In one possible implementation, the communication device further comprises a memory. In one possible implementation, the communication device further comprises a communication interface, the processor being coupled to the communication interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input / output interface may be an input / output circuit.

[0129] In one implementation, the communication device is a user data storage network element. When the communication device is a user data storage network element, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input / output interface may be an input / output circuit.

[0130] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0131] In a twelfth aspect, a communication device is provided, comprising a processor coupled to a memory and configured to execute instructions in the memory to implement the method of the second aspect and possible implementations thereof. In one possible implementation, the communication device further comprises a memory. In one possible implementation, the communication device further comprises a communication interface, the processor being coupled to the communication interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input / output interface may be an input / output circuit.

[0132] In one implementation, the communication device is an event notification entity. When the communication device is an event notification entity, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In another possible implementation, the input / output interface may be an input / output circuit.

[0133] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0134] In a thirteenth aspect, a communication device is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit, so that the method of any one of the first to fourth aspects, and any possible implementation of the aforementioned aspects, is implemented.

[0135] In a specific implementation, the communication device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. The input circuit and the output circuit may be different circuits or the same circuit, in which case the circuit functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0136] In a fourteenth aspect, a processing device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory and receive signals via a receiver and transmit signals via a transmitter to execute the method of any one of the first to fourth aspects, and any possible implementation of the aforementioned aspects.

[0137] In a possible implementation, there are one or more processors and one or more memories.

[0138] In a possible implementation, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0139] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0140] It should be understood that related data interaction processes, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of receiving input capability information from the processor. Specifically, the output data of the processing can be output to the transmitter, and the input data received by the processor can come from the receiver. The transmitter and receiver can be collectively referred to as a transceiver.

[0141] The processor in the above aspects can be a chip, which can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor or located outside the processor and exist independently.

[0142] In the fifteenth aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when run, enables a computer to execute any one of the first to fourth aspects, as well as any possible implementation method of the above aspects.

[0143] In the sixteenth aspect, a computer-readable medium is provided, which stores a computer program (also referred to as code, or instructions) which, when run on a computer, enables the computer to execute any one of the first to fourth aspects above, as well as any possible implementation of the above aspects.

[0144] In the seventeenth aspect, a communication system is provided, including at least one of the aforementioned event subscription entity, the user data storage network element, and the first event notification entity. BRIEF DESCRIPTION OF THE DRAWINGS

[0145] FIG1 is a schematic diagram of an example of a communication system to which the present application is applied.

[0146] FIG2 is an architecture diagram of a system provided in an embodiment of the present application.

[0147] FIG3 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0148] FIG4 is a schematic flow chart of a communication method provided in an embodiment of the present application.

[0149] FIG5 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0150] FIG6 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0151] FIG7 is a schematic block diagram of another communication device provided in an embodiment of the present application.

[0152] FIG8 is a schematic diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0153] In order to facilitate understanding of the embodiments of the present application, the following points are first explained.

[0154] 1. In this application, unless otherwise specified, "plurality" means two or more. In addition, "at least one" can be replaced by "one or more".

[0155] 2. In this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments based on their internal logical relationships.

[0156] 3. The various numerical numbers involved in this application are only used for the convenience of description and are not used to limit the scope of protection of this application. The size of the serial numbers involved in this application does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third", "fourth" and other various terminology labels (if any) in the specification and claims and drawings of this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. Among them, the data used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than what is illustrated or described here.

[0157] At the same time, any embodiment or design described in this application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0158] 4. The terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0159] 5. In this application, "pre-configuration" may include pre-definition, such as protocol definition. "Pre-definition" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in the device. This application does not limit the specific implementation method.

[0160] 6. "Storage" or "storage" as used in this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be provided in part separately and in part integrated into a decoder, processor, or communication device. The type of memory may be any form of storage medium and is not limited thereto.

[0161] 7. The “protocol” referred to in this application may refer to a standard protocol in the field of communications, for example, it may include the fourth generation (4G) network, the fifth generation (5G) network protocol, the new radio (NR) protocol, the 5.5G network protocol, the sixth generation (6G) network protocol and related protocols used in future communication systems. This application does not limit this.

[0162] 8. The dotted arrows or boxes in the schematic diagrams in the accompanying drawings of this application specification represent optional steps or optional modules.

[0163] 9. In this application, unless otherwise specified, “ / ” indicates that the objects associated with each other are in an “or” relationship. For example, A / B can represent A or B. “And / or” in this application is only a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural.

[0164] 10. The technical solutions provided in the embodiments of this application can be applied to wireless communications between communication devices. Wireless communications between communication devices may include: wireless communications between network devices and terminals, wireless communications between network devices, and wireless communications between terminals. In the embodiments of this application, the term "wireless communications" may also be referred to as "communication," which may also be described as "data transmission," "information transmission," or "transmission."

[0165] 11. The names of all nodes and messages in this application are merely names set for the convenience of description. The names in the actual network may be different. This application should not be understood as limiting the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in this application is regarded as the method or equivalent replacement of this application, and is within the scope of protection of this application. No further details will be given below.

[0166] 12. In this application, the phrase "sending information to ... (terminal)" should be understood to mean that the destination of the information is the terminal, and may include directly or indirectly sending information to the terminal. The phrase "receiving information from ... (terminal)" should be understood to mean that the source of the information is the terminal, and may include directly or indirectly receiving information from the terminal. Information may undergo necessary processing between the source and destination, such as formatting changes, but the destination can still understand the valid information from the source. Similar expressions in this application should be understood similarly and will not be elaborated on here.

[0167] First, the communication system to which the technical solution of the present application is applicable is described.

[0168] The technical solution of the present application can be applied to various communication systems, such as: 6G system, 5G system, 4G system (or long term evolution (LTE) system), LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system and future communication systems. The technical solution provided by the present application can also be applied to device to device (D2D) communication, vehicle to everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication system or other communication systems.

[0169] The following describes a communication system 100 applicable to an embodiment of the present application in conjunction with Figure 1. Communication system 100 is merely an example and does not limit the present application in any way. Communication system 100 includes: a first terminal device, a second terminal device, and an IMS network. The IMS network in communication system 100 may also be a web real-time communication (WebRTC) network. For ease of description, the present embodiment of the application uses the IMS network as an example.

[0170] Specifically, the first terminal device and the second terminal device communicate via the IMS network. The first terminal device is a calling device (ie, a device initiating a call), and the second terminal device is a called device (ie, a device being called).

[0171] An IMS network can be a collection of multiple devices capable of processing voice and multimedia services, or a collection of multiple servers capable of processing audio, video, and multimedia services. An IMS network includes one or more network devices, such as a call session control function (CSCF) network element, an IMS access media gateway (AGW), a data channel signaling function (DCSF) network element, a media function (MF) network element, and a home subscriber server (HSS).

[0172] When the first terminal device acts as a calling device, it can be any electronic device with a call function. Exemplarily, the first terminal device is user equipment (UE). UE can be any device that can access a network and can also be referred to as terminal equipment (terminal equipment), terminal device, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. UE can be a device that provides voice / data connectivity to a user, such as a handheld device or vehicle-mounted device with wireless connection capabilities. At present, some examples of terminals may include: mobile phones, tablet computers, computers with wireless transceiver functions (such as laptops, PDAs, etc.), mobile internet devices (MIDs), virtual reality (VR) devices, AR devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 4G / 5G networks or future evolved public land mobile communication networks (PLMNs). terminal equipment in network, PLMN, etc.

[0173] Furthermore, a UE can also be a UE in an Internet of Things (IoT) system. IoT is a crucial component of future information technology development. Its primary technical feature is connecting objects to the network through communication technologies, thereby enabling intelligent networks that interconnect humans and machines, and objects and things. IoT technology can achieve massive connectivity, deep coverage, and power-saving terminals through technologies such as narrowband (NB). UEs can also include smart printers and train detectors, with their primary functions including collecting data (partial terminal equipment), receiving control information and downlink data from network devices, and transmitting electromagnetic waves to transmit uplink data to network devices.

[0174] A UE can be used to act as a base station. For example, a user equipment can act as a dispatching entity, providing sidelink signals between user equipment in vehicle-to-everything (V2X) or device-to-device (D2D) applications. For example, a cell phone and a car can communicate with each other using sidelink signals. A cell phone and a smart home device can also communicate without relaying the communication signal through a base station.

[0175] When the second terminal device acts as the called device, it can be any electronic device with call functionality. For example, the second terminal device is a user device, or the second terminal device is a public safety answering point (PSAP) in an IMS emergency call scenario (i.e., communication device 1 initiates an IMS emergency call to communication device 2), or any electronic device with call functionality under a public safety answering point.

[0176] The above-mentioned network architecture applied to the embodiment of the present application is only an example. The network architecture applicable to the embodiment of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiment of the present application. That is, the network architecture and business scenarios described in the embodiment of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiment of the present application, and do not constitute a limitation on the technical solutions provided in the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiment of the present application are also applicable to similar technical problems.

[0177] The network elements or devices listed in the above network architecture are only exemplary. The network architecture applicable to this application may also include other network elements or devices, and this application does not limit this. The naming of the above network elements or devices is only defined to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 4G networks, 5G networks and other networks in the future. For example, in a 6G network, some or all of the above network elements may use the terminology in 4G / 5G, or may use other names.

[0178] The communication device in the embodiment of the present application includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU) and a memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through a process (Process), for example, a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system or a windows operating system. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. In addition, the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application. As long as it is possible to communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application can be a terminal device or a network device, or a functional module in a terminal device or a network device that can call a program and execute the program.

[0179] In addition, various aspects or features of the embodiments of the present application can be implemented as methods, devices or products using standard programming and / or engineering techniques. The term "product" as used in this application covers computer programs that can be accessed from any computer-readable device, carrier or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks or tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

[0180] Figure 2 is a diagram of an IMS session network architecture according to an embodiment of the present application. The following briefly introduces some network elements or devices involved in the network architecture shown in Figure 2.

[0181] 1. CSCF Network Element: The CSCF is a functional entity within the IMS and the core of the entire IMS. It is primarily responsible for handling signaling control during multimedia call sessions. It manages IMS user authentication, the IMS bearer plane quality of service (QoS), and collaborates with other network elements to control SIP sessions, as well as service negotiation and resource allocation. For convenience, the CSCF network element will be referred to as "CSCF" in this application.

[0182] The CSCF can communicate with the terminal device or the gateway device. For example, the CSCF selects the gateway device to communicate with the terminal device, and can also allocate routing information, such as IP addresses or ports, to the terminal device and the gateway device.

[0183] As an example and not a limitation, CSCF is classified into proxy CSCF (P-CSCF), interrogating CSCF (I-CSCF), serving CSCF (S-CSCF), etc. according to its function.

[0184] The P-CSCF is the entry point for users to access the IMS network and is primarily responsible for forwarding SIP signaling between IMS users and their home networks. The I-CSCF is the unified entry point for IMS users' home networks and is responsible for allocating or querying the S-CSCF serving them. The S-CSCF is the unified entry point for IMS users' home networks and is responsible for allocating or querying the S-CSCF serving them.

[0185] The above-mentioned P-CSCF, S-CSCF, and I-CSCF may be independently configured in different entities or integrated into the same entity, without limitation.

[0186] 2. IMS-AGW: IMS-AGW can provide IMS network access gateway and media gateway functions.

[0187] The CSCF and IMS AGW may be collectively referred to as the IMS core. This application does not limit the signaling interaction method between network elements in the IMS core.

[0188] 3. DCSF network element: DCSF is a logical functional entity in the data channel server (DCS). DCSF is mainly used to provide data channel signaling control functions.

[0189] 4. MF network element: MF is also a part of the logical functional entity in DCS. MF is mainly used to provide data channel media resource management functions.

[0190] 5. Multimedia Telephony Application Server (MMTel AS): An MMTel AS is an upper-layer application layer device in the IMS system, providing basic audio and video services and supplementary services. The IMS network is an open system that provides various multimedia services to users based on IP bearer. The MMTel AS interacts with the CSCF using the SIP protocol to trigger and execute various network services.

[0191] 6. DCAR (data channel application repository) network element: used to store data channel applications.

[0192] 7. IMS Application Server (AS): The IMS AS is the top-level application layer device in the IMS system. It provides basic audio and video calling services, supplementary services, multimedia conferencing, converged communications, SMS gateways, standard attendant consoles, and other services. An example of an IMS AS is the MMTel AS. The IMS network is an open system that provides various multimedia services to users based on IP bearer networks. The IMS AS interacts with the CSCF to trigger and execute various network services.

[0193] 8. HSS network element: responsible for storing IMS user subscription data in the 4G network.

[0194] 9. UDM (unified data management) network element: Responsible for storing IMS user subscription data in the 5G network.

[0195] 10. NEF (network exposure function) network element: A capability exposure network element of the 5G core network (5GC), which securely opens various services of the 5GC network to third parties.

[0196] 11. IMSEF (IMS exposure function) network element, an IMS domain capability exposure network element, is used to securely expose various IMS network services to third parties.

[0197] 12. DCAS (data channel application server) network element: mainly used to provide data channel application service functions.

[0198] It can be understood that the above-mentioned network architecture applied to the present application is only an example, and the network architecture applicable to the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the present application, that is, the network architecture and business scenarios described in the present application are for the purpose of more clearly illustrating the technical solution of the present application, and do not constitute a limitation on the technical solution provided by the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solution provided by the present application is also applicable to similar technical problems.

[0199] The network elements or devices listed in the above network architecture are only exemplary. The network architecture applicable to this application may also include other network elements or devices, and this application does not limit this. The naming of the above network elements or devices is only defined to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 4G networks, 5G networks and other networks in the future. For example, in a 6G network, some or all of the above network elements may use the terminology in 4G / 5G, or may use other names.

[0200] The communication equipment of the present application (for example, the above-mentioned terminal equipment, CSCF equipment or AS equipment, etc.) includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU) and a memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system or a Windows operating system. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. In addition, the present application does not specifically limit the specific structure of the execution subject of the method provided by the present application. As long as it is possible to communicate according to the method provided by the present application by running a program that records the code of the method provided by the present application, for example, the execution subject of the method provided by the present application can be a terminal device or a network device, or a functional module in a terminal device or a network device that can call and execute a program.

[0201] In addition, various aspects or features of the present application can be implemented as methods, apparatuses, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used in this application covers computer programs that can be accessed from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.). The various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0202] If there are multiple NF service producer instances in the network, when an NF service consumer subscribes to an event of a specific user from an NF service producer, it must first determine which NF service producer instance provides services for the user, so as to send an event subscription request for the user to the NF service producer instance.

[0203] When there are multiple NF instances serving different users, if each user is provided with services by a fixed NF instance, the NF instances providing services are generally divided according to the user identification number segment, that is, each NF instance provides services to users with different user identification number segments.

[0204] The above user identification can be understood as follows: In a mobile communication network, each mobile user is assigned multiple types of user identifications to uniquely identify the user and are used in scenarios such as registration authentication and call routing. Common user identifications are as follows:

[0205] The Mobile Station ISDN number (MSISDN), also known as the Integrated Services Digital Network (ISDN) number, is a unique identifier for mobile subscribers within the Public Switched Telephone Network (PSTN) numbering plan. It uniquely identifies mobile subscribers on 2G, 3G, and 4G networks. The MSISDN is the mobile phone number we use daily. We use it to call or text a mobile subscriber.

[0206] The International Mobile Subscription Identity (IMSI) is a private identifier assigned to mobile users by 2G, 3G, and 4G networks. It is stored in the subscriber identity module (SIM) of a mobile phone. Simply put, the IMSI is the SIM card ID. The association between the IMSI and the MSISDN is stored in the user's subscription data.

[0207] The generic public subscription identifier (GPSI) is a public identity identifier assigned to mobile users by the 5G network. It is an externally addressable identifier for users, similar to the MSISDN of 2G / 3G / 4G networks.

[0208] The Subscription Permanent Identifier (SUPI) is a private identifier assigned to mobile users by the 5G network, similar to the IMSI in 2G, 3G, and 4G networks, and is stored on the phone's SIM card. The association between the GPSI and SUPI is stored in the 5G user's subscription data.

[0209] The IP multimedia public identity (IMPU) is the public identity of an IMS user. It is an externally addressable identifier of the user and is used for routing IMS signaling.

[0210] The IP Multimedia Private Identity (IMPI) is the private identity of an IMS user and is used for registration, authentication, and other purposes when a user accesses the IMS network.

[0211] Taking the UDM of the 5G network as an example, when SMF, as a service consumer, wants to subscribe to a specific event (one or more) of a user from the service producer UDM, SMF must first use the user's identifier (GPSI or SUPI) to discover the UDM service to NRF, find the UDM instance that provides services to the user, and then SMF sends a subscription request message to the UDM instance to subscribe to the user's events.

[0212] An IMS network typically has multiple instances of the same IMS AS (IMS Application Server) providing the same services to different users. However, these IMS AS instances are not bound to the IMS users they serve. In other words, the IMS AS instance serving a user cannot be directly found using an IMS user identity (IMPU, IMPI, GPSI / MSISDN, or SUPI / IMSI). This is because the IMS AS instance serving a user is dynamically selected by the S-CSCF after the user UE completes IMS registration, based on the user's initial filter criteria (iFC) during third-party registration. Furthermore, the S-CSCF may select different IMS AS instances for the same user UE during multiple registrations. The MMTel AS is the AS that provides basic IMS audio and video calls and supplementary services to IMS users. For example, during UE A's first third-party registration, the S-CSCF selects MMTel AS-1. However, during subsequent third-party registrations, if the S-CSCF detects a failure in MMTel AS-1, it will select another MMTel AS instance, such as MMTel AS-2.

[0213] The existing technology cannot solve the problem of how an event subscription entity subscribes to a user event from an IMS AS instance serving a specific user (hereinafter referred to as IMS AS).

[0214] Note: For security reasons, if a third-party device outside the network wants to subscribe to events for a specific user on the IMS AS, it must subscribe through the capability exposure network element within the operator's network. After receiving the event subscription request from the third-party device (outside the network), the capability exposure network element subscribes to the specific user events from the IMS AS within the network on behalf of the third-party device.

[0215] That is to say, the event subscription entity mentioned in this article can be other network elements within the operator network, such as a data channel signaling server (such as a DCSF network element), or a capability open network element in the operator network (such as an IMSEF network element / NEF network element). The capability open network element subscribes to the events of a specific user from the IMS AS within the network on behalf of a third-party device outside the network. Among them, the capability open network element can subscribe to the events of a specific user directly from the IMS AS, and the capability open network element can also subscribe to the events of a specific user indirectly from the IMS AS through the data channel signaling server, that is, the capability open network element calls the event subscription service of the data channel signaling server, and the data channel signaling server subscribes to the events of a specific user from the IMS AS as an event subscription entity. The data channel application server in the network (such as a DC AS network element) subscribes to the events of a specific user indirectly from the IMS AS through the data channel signaling server, that is, the data channel application server calls the event subscription service of the data channel signaling server, and the data channel signaling server subscribes to the events of a specific user from the IMS AS as an event subscription entity.

[0216] This application provides a variety of data transmission methods, which can enable a notifier network element serving a specific user to subscribe to the user's events.

[0217] It should be understood that the description of the specific scenarios in the embodiments of the present application is only an example. In addition to being applicable to the application scenarios described above, the methods provided in the embodiments of the present application are also applicable to application scenarios with similar problems.

[0218] The following describes in detail various communication methods provided in the embodiments of the present application with reference to the accompanying drawings.

[0219] It should be understood that the step numbers in the embodiments of the present application are for illustration only and do not limit the order in which the steps occur.

[0220] For ease of understanding and explanation, the following describes the communication method of an embodiment of the present application by taking the interaction between an event subscription entity and a user data storage network element and a first event notification entity as an example, but this should not constitute any limitation on the execution subject of the communication method of an embodiment of the present application. For example, the method executed by the event subscription entity can also be executed by a module of the event subscription entity (such as a circuit, a chip or a chip system, etc.), and can also be implemented by a logical node, a logical module or software that can realize all or part of the functions of the event subscription entity. The method executed by the first event notification entity can also be executed by a module of the first event notification entity (such as a circuit, a chip or a chip system, etc.), and can also be implemented by a logical node, a logical module or software that can realize all or part of the functions of the first event notification entity.

[0221] FIG3 shows a method 300 provided in the present application. The method in FIG3 includes at least part of steps S310 to S330.

[0222] S310: Based on interaction with a user data storage network element, an event subscription entity subscribes to a first event from a first event notification entity, where the first event is an event related to an IMS session of a first user.

[0223] Among them, the event subscription entity can subscribe to the first event directly to the first event notification entity; or, the event subscription entity can also subscribe to the first event indirectly to the first event notification entity, such as the event subscription entity subscribes to the first event to the first event notification entity based on a certain proxy network element (such as a user data storage network element).

[0224] S310 can be implemented in two ways, which are described in detail below.

[0225] In a possible implementation, S310 includes S3101 and S3102. As an example, S310 can be replaced by S3101 and S3102.

[0226] S3101: An event subscription entity sends first subscription information to a user data storage network element. The first subscription information is used to subscribe to information about a first event, where the first event is an event related to an IMS session of a first user.

[0227] Optionally, the first subscription information includes a user identifier of the first user, an identifier of the first event, and a notification endpoint (notification endpoint), where the notification endpoint identifies an address of a network element that receives the first event notification request message.

[0228] Optionally, the network element that receives the first event notification request message is an event subscription entity.

[0229] Optionally, the event subscription entity sends the first subscription information to the user data storage network element, including: the event subscription entity sends an IMS user data management update (Nhss_ImsSDM_Update) request message to the user data storage network element, where the Nhss_ImsSDM_Update request message includes the first subscription information.

[0230] S3102: The user data storage network element sends first subscription information or user data information of the first user to the first event notification entity, where the user data information of the first user includes the first subscription information.

[0231] It should be understood that the first event notification entity identifies the events that need to be monitored by itself according to the first subscription information in the user data of the first user, and starts monitoring the subscribed events (one or more) of the first user.

[0232] In another possible implementation, S310 includes S3103 to S3105. As an example, S310 may be replaced by S3103 to S3105.

[0233] S3103: The first event notification entity sends a first address to the user data storage network element, where the first address is the address of the first event notification entity.

[0234] In one implementation, the first event notification entity further sends the identifier of the first user to the user data storage network element, so that the user data storage network element stores the first address in the user data of the first user according to the identifier of the first user.

[0235] Optionally, the first event notification entity sends the first address and / or the identifier of the first user to the user data storage network element through an Nhss_ImsSDM_Update request message.

[0236] S3104: The user data storage network element sends the first address to the event subscription entity.

[0237] In one implementation, the event subscription entity sends an IMS user data management acquisition (Nhss_ImsSDM_Get) request message to the user data storage network element. The IMS user data management acquisition request message is used to request to acquire the first address.

[0238] After receiving the Nhss_ImsSDM_Get request message, the user data storage network element sends the first address to the event subscription entity.

[0239] S3105: The event subscription entity sends a first event subscription request message to the first event notification entity according to the first address. The first event subscription request message is used to request subscription to a first event.

[0240] Optionally, the event subscription entity may first send a first event subscription request message to the user data storage network element, so that the user data storage network element sends the first event subscription request message to the first event notification entity according to the first address.

[0241] S320: The first event notification entity sends a first event notification request message to a network element that needs to receive the first event notification request message, where the first event notification request message includes information about the first event.

[0242] The network element that needs to receive the first event notification request message is, for example, an event subscription entity.

[0243] It should be understood that after obtaining the subscription of the event subscription entity to the first event, the first event notification entity starts monitoring the first event. When the first event notification entity monitors the occurrence of the first event, it sends a first event notification request message to the network element that needs to receive the first event notification request message.

[0244] S330: The event subscription entity sends a first event notification response message to the first event notification request message. The first event notification response message is used to indicate that the event subscription entity has successfully received the first event notification request message.

[0245] In the above method, the event subscription entity needs to interact with the user data storage network element for data (the event subscription entity sends data to the user data storage network element or receives data sent by the user data storage network element), and the event subscription entity needs to interact with the first event notification entity for data (the event subscription entity sends data to the first event notification entity or receives data sent by the first event notification entity).

[0246] In one possible implementation, the event subscription entity is a data channel application server, which indirectly interacts with the user data storage network element through the data channel signaling server, and indirectly interacts with the first event notification entity through the data channel signaling server. That is, the data channel application server calls the event subscription service of the data channel signaling server, and the data channel signaling server interacts with the user data storage network element as an event reader, and the data channel signaling server interacts with the first event notification entity as an event subscriber.

[0247] In another possible implementation, the event subscription entity is a capability exposure network element, which can directly interact with the user data storage network element and directly subscribe to the first event to the first event notification entity; or, the capability exposure network element can indirectly interact with the user data storage network element through a data channel signaling server, and indirectly subscribe to the first event to the first event notification entity through the data channel signaling server, that is, the capability exposure network element calls the service of the data channel signaling server, and the data channel signaling server interacts with the user data storage network element as an event subscriber.

[0248] In another possible implementation, the event subscription entity is a data channel signaling server. The data channel signaling server can directly interact with the user data storage network element based on the subscription-related information obtained from the capability exposure network element or the data channel application server, and directly subscribe to the first event to the first event notification entity.

[0249] 4 , an implementation of the method provided in the present application is described in detail with reference to FIG4 , in which the first event notification entity takes IMS AS as an example, the event subscription entity takes IMSEF network element / NEF network element (hereinafter referred to as IMSEF / NEF) as an example, and the user data storage network element takes HSS / UDM as an example. It should be understood that method 400 is a specific implementation of method 300.

[0250] FIG4 shows a method 400 provided in the present application. The method in FIG4 includes at least part of steps S410 to S490.

[0251] S410: The IMSEF / NEF generates first subscription information.

[0252] S420: The IMSEF / NEF sends first subscription information to the HSS / UDM.

[0253] S430: The HSS / UDM saves the first subscription information.

[0254] S440: The IMS AS obtains the first subscription information from the HSS / UDM.

[0255] S450: The IMS AS starts monitoring the first event.

[0256] S460: The IMS AS sends a first event notification request message to the IMSEF / NEF.

[0257] S470: The IMSEF / NEF sends a first event notification response message to the IMS AS.

[0258] S480: The IMSEF / NEF sends a first subscription information deletion request message to the HSS / UDM.

[0259] S490: The HSS / UDM notifies the IMS AS that the first subscription information has been deleted.

[0260] The following is a detailed introduction.

[0261] S410: The IMSEF / NEF generates first subscription information.

[0262] The first subscription information is used to subscribe to information about a first event, where the first event is an event related to the IMS session of the first user. The first subscription information includes the user identifier of the first user, the identifier of the first event, and a notification endpoint, where the notification endpoint identifies the address of a network element that receives a notification request message for the first event.

[0263] Optionally, the first subscription information is included in an event subscription record of the first user. A subscription record includes at least a globally unique notification association ID (or an identification ID of the event subscription record), an event list, and a notification endpoint, wherein the event list includes one or more events, the one or more events including the first event, and the notification endpoint identifies the address of the network element that needs to receive information related to the subscribed event (i.e., the uniform resource identifier (URI) of the NF that receives the first event notification). Optionally, the network element that receives the information related to the first event is an IMSEF / NEF.

[0264] S420: The IMSEF / NEF sends first subscription information to the HSS / UDM.

[0265] First, the IMSEF / NEF finds the HSS / UDM serving the first user through NRF service discovery according to the user identifier of the first user.

[0266] Subsequently, the IMSEF / NEF sends the first subscription information to the HSS / UDM. Optionally, the first subscription information is carried in an Nhss_ImsSDM_Update request message.

[0267] In a possible implementation, the IMSEF / NEF sends an Nhss_ImsSDM_Update request message to the HSS / UDM, carrying the event subscription record of the first user through a PUT method.

[0268] In another possible implementation, the PUT method is used in the Nhss_ImsSDM_Update request message to fully update the user's event subscription data on the HSS / UDM. Specifically, the IMSEF / NEF first downloads all the user's event subscription data from the HSS / UDM using the Nhss_ImsSDM_Get request message, then adds the new event subscription record generated in step S410 to the downloaded event subscription data. Finally, the updated full event subscription data is sent to the HSS / UDM using the PUT method of the Nhss_ImsSDM_Update request message.

[0269] S430: The HSS / UDM saves the first subscription information.

[0270] It should be understood that the HSS / UDM saves the first subscription information to the user data of the first user. Each user's user data may store zero or more event subscription records, which are collectively referred to as event subscription data.

[0271] Optionally, the HSS / UDM sends an Nhss_ImsSDM_Update response message to the IMSEF / NEF, indicating that the user data is updated successfully.

[0272] S440: The IMS AS obtains the first subscription information from the HSS / UDM.

[0273] Specifically, the IMS AS may obtain user data information of the first user from the HSS / UDM, where the user data information of the first user includes the first subscription information. There are mainly three scenarios in which the IMS AS obtains user data of a user from the HSS / UDM.

[0274] 1) When a third party registers, the IMS AS downloads the user data of the user from the HSS / UDM serving the user through the Nhss_ImsSDM_Get request / response message.

[0275] 2) During third-party registration, the IMS AS also subscribes to the user's user data changes with the HSS / UDM serving the user. If the user's user data subsequently changes, the HSS / UDM sends an IMS Subscriber Data Management Notification (Nhss_ImsSDM_Notification) request message to the IMS AS. This message carries the details of the user data change, including the resource ID (the resource URI corresponding to the changed data), the change type (addition / deletion / replacement / move), and the original and new values.

[0276] This situation can also be regarded as the IMS AS receiving the first subscription information sent by the HSS / UDM.

[0277] 3) Abnormal scenario, for example, if the IMS AS finds that the user data of the user does not exist when triggering the user service, the IMS AS can also download the user data of the user from the HSS / UDM serving the user through the Nhss_ImsSDM_Get request / response message.

[0278] S450: The IMS AS starts monitoring the first event.

[0279] The IMS AS records and identifies the first event to be monitored by itself according to the first subscription information in the user data of the first user, thereby starting monitoring of the first event.

[0280] S460: The IMS AS sends a first event notification request message.

[0281] When the IMS AS detects that the subscribed event of the first user occurs, it sends a first event notification request message to the notification endpoint recorded in the first subscription information, thereby notifying the first event information.

[0282] S470: The IMS AS receives the first event notification response message.

[0283] The notification endpoint returns a first event notification response message to the IMS AS, indicating that the first event notification request message is received successfully.

[0284] S480: The IMSEF / NEF sends a first subscription information deletion request message to the HSS / UDM.

[0285] When the IMSEF / NEF needs to unsubscribe from the first event, it sends a first subscription information deletion request message to the HSS / UDM, requesting the deletion of the first subscription information. The HSS / UDM deletes the corresponding event subscription record or first subscription information from the user data of the first user based on the identifier of the event subscription record or first subscription information carried in the request message.

[0286] In one implementation, the first subscription information deletion request message is an Nhss_ImsSDM_Update request message. The IMSEF / NEF sends the Nhss_ImsSDM_Update request message to the HSS / UDM, uses the DELETE method, and carries a notification association ID parameter to indicate the event subscription record to be deleted.

[0287] IMSEF / NEF deletes event subscription records using either incremental updates or full updates. Specifically, IMSEF / NEF first downloads all event subscription data for the user from HSS / UDM using the Nhss_ImsSDM_Get request message, then deletes the event subscription record from the downloaded event subscription data, and then sends the updated full event subscription data to HSS / UDM using the Nhss_ImsSDM_Update request message PUT method.

[0288] S490: The HSS / UDM notifies the IMS AS that the first subscription information has been deleted.

[0289] The HSS / UDM sends a first event subscription deletion notification message to the IMS AS that subscribes to the user data change. The first event subscription deletion notification message is used to notify that the first subscription information has been deleted.

[0290] Optionally, the notification information of the first event subscription deletion is an Nhss_ImsSDM_Notification request message, which is used to inform that the corresponding event subscription record is deleted.

[0291] Figure 5 shows a method 500 provided by the present application. The first event notification entity takes IMS AS as an example, the event subscription entity takes IMSEF / NEF as an example, and the user data storage network element takes HSS / UDM as an example. An implementation of the method provided by the present application is introduced in detail. It should be understood that method 500 is a specific implementation of method 300.

[0292] The method in FIG. 5 includes at least part of steps S510 to S592 .

[0293] S510: The IMS AS sends a first address to the HSS / UDM, where the first address is the address of the IMS AS.

[0294] S520: HSS / UDM saves the first address.

[0295] S530: The IMSEF / NEF sends a first request message to the HSS / UDM, requesting to obtain a first address.

[0296] S540: The HSS / UDM sends the first address to the IMSEF / NEF.

[0297] S550: The IMSEF / NEF sends a first event subscription request message to the IMS AS.

[0298] S560: The IMS AS sends a first event subscription response message to the IMSEF / NEF.

[0299] S570: The IMS AS starts monitoring the first event.

[0300] S580: The IMS AS sends a first event notification request message.

[0301] S590: The IMS AS receives the first event notification response message.

[0302] S591, the IMSEF / NEF sends a first event unsubscribe request message to the HSS / UDM.

[0303] S592: The HSS / UDM sends a first event unsubscribe response message to the IMSEF / NEF.

[0304] The following is a detailed introduction.

[0305] S510: The IMS AS sends a first address to the HSS / UDM, where the first address is the address of the IMS AS.

[0306] First, after the UE successfully registers or re-registers, the S-CSCF performs an iFC trigger analysis and selects the IMS AS to be triggered for the first user. The S-CSCF then sends a REGISTER request message to the selected IMS AS to perform third-party registration.

[0307] The IMS AS downloads user data (including the first user's user identity data, service subscription data, etc.) from the HSS / UDM serving the first user through the Sh interface (user data request (UDR) / user data answer (UDA) message) or the Nhss service interface (Nhss_ImsSDM_Get request / response message).

[0308] In one implementation, the IMS AS sends an Nhss_ImsSDM_Update request message to the HSS / UDM, carrying the AS type and address information of the IMS AS through a PUT method.

[0309] In another implementation, the PUT method is used in the Nhss_ImsSDM_Update request message to fully update the IMS AS address data of the first user on the HSS / UDM. Specifically, the IMSEF / NEF must first download the IMS AS address data of the user from the HSS / UDM through the Nhss_ImsSDM_Get request message, then update the new IMS AS address record to the downloaded IMS AS address data, and then send the updated IMS AS address data to the HSS / UDM using the PUT method of the Nhss_ImsSDM_Update request message.

[0310] In yet another implementation, the first address record may be updated to the user data of the HSS / UDM via a Profile-Update-Request (PUR) / Profile-Update-Answer (PUA) message of the Sh interface.

[0311] It should be understood that, depending on the user's service subscription, the user's user data may contain zero or multiple IMS AS address records. For example, if a user has subscribed to both the IMS basic audio and video call service and the color ring back tone service, their user data may contain two IMS AS address records: one for the MMTel AS instance address information and the other for the color ring back tone AS instance address information.

[0312] In addition, the IMS AS also sends the identifier of the first user to the HSS / UDM. The identifier of the first user may be included in the information of the first address.

[0313] S520: HSS / UDM saves the first address.

[0314] Specifically, the HSS / UDM updates the address record of the IMS AS carried in the Nhss_ImsSDM_Update request message into the user data of the first user according to the identifier of the first user.

[0315] Optionally, the HSS / UDM returns an Nhss_ImsSDM_Update response message to the IMS AS, indicating that the user data of the first user is updated successfully.

[0316] S530: The IMSEF / NEF sends a first request message to the HSS / UDM, requesting to obtain a first address.

[0317] First, the IMSEF / NEF finds the HSS / UDM serving the first user through NRF service discovery according to the user identity (MSISDN, IMPU, etc.) of the first user.

[0318] Then, the IMSEF / NEF sends a first request message to the HSS / UDM serving the user, to download the address record of the IMS AS serving the first user.

[0319] Optionally, the first request information is carried in an Nhss_ImsSDM_Get request message.

[0320] S540: The HSS / UDM sends the first address to the IMSEF / NEF.

[0321] Optionally, the HSS / UDM sends an Nhss_ImsSDM_Get response message, carrying the address record of the IMS AS serving the first user to the IMSEF / NEF.

[0322] S550: The IMSEF / NEF sends a first event subscription request message to the IMS AS.

[0323] The IMSEF / NEF sends a first event subscription request message to the IMS AS based on the first address, where the first event subscription request message is used to subscribe to the first event of the first user. The first event subscription request message carries subscription-related information, including: the user identifier of the first user, the identifier of the first event, and the notification endpoint.

[0324] In one implementation, the IMSEF / NEF may send a first event subscription request message to the HSS / UDM serving the first user, and the HSS / UDM may subscribe to the first event from the IMS AS based on the first address. For example, the HSS / UDM may send a second event subscription request message to the IMS AS, and the second event subscription request message may also carry subscription-related information, including: the user identifier of the first user, the identifier of the first event, and the notification endpoint.

[0325] S560: The IMS AS sends a first event subscription response message to the IMSEF / NEF.

[0326] After receiving the first event subscription request message, the IMS AS first creates a subscription resource, generates a subscription ID (subscriptionId), and starts monitoring the first event of the first user.

[0327] Subsequently, the IMS AS returns a first event subscription response message to the IMSEF / NEF. The first event subscription response message is used to indicate that the first event has been successfully subscribed to, and returns the created subscription resource URI through the Location header field, which includes the generated subscription ID.

[0328] In one implementation, the IMS AS may first send a first event subscription response message to the HSS / UDM, and then the HSS / UDM may send a second event subscription response message to the IMSEF / NEF to indicate that the subscription is successful.

[0329] After receiving the first event subscription response message, the IMSEF / NEF saves the subscription resource URI.

[0330] S570: The IMS AS starts monitoring the first event.

[0331] S580: The IMS AS sends a first event notification request message.

[0332] After detecting the triggering of the first event, the IMS AS sends a first event notification request message to the notification endpoint according to the notification endpoint recorded in the first event subscription request message or the second event subscription request message, thereby notifying the first event information.

[0333] Optionally, the network element corresponding to the notification endpoint is IMSEF / NEF.

[0334] S590: The IMS AS receives the first event notification response message.

[0335] The notification endpoint returns a first event notification response message to the IMS AS, indicating that the first event notification request message is received successfully.

[0336] S591, the IMSEF / NEF sends a first event unsubscribe request message to the HSS / UDM.

[0337] The IMSEF / NEF sends a first event unsubscribe request message to the IMS AS serving the first user, requesting to cancel subscription to the first event.

[0338] Optionally, the DELETE method is used to cancel the subscription to the first event, and the resource URI of the first event unsubscribe request message indicates the subscription ID of the event subscription to be deleted.

[0339] In one implementation, the IMSEF / NEF may first send a first event unsubscribe request message to the HSS / UDM serving the first user, and the HSS / UDM may send the first event unsubscribe request message to the IMS AS according to the first address.

[0340] S592: The HSS / UDM sends a first event unsubscribe response message to the IMS AS, thereby indicating that the subscription to the first event has been canceled.

[0341] In one implementation, the IMS AS may first send a first event unsubscribe response message to the HSS / UDM, and then the HSS / UDM sends a first event unsubscribe response message to the IMSEF / NEF.

[0342] In addition, after the first user subsequently performs initial registration / re-registration, the S-CSCF may, for some reason (such as when the original IMS AS serving the user fails or is overloaded), select another IMS AS that triggers similar services for third-party registration on behalf of the user. For example, to provide the user with telephony services, it may select another MMTel AS instance. The new IMS AS (i.e., an instance of the second event notification entity) will then update its address in the HSS / UDM serving the user.

[0343] The address of the new IMS AS is called a second address, and the new IMS AS sends the second address to the HSS / UDM in the same manner as step S510.

[0344] Because the IMSEF / NEF has previously subscribed to IMS AS address changes for the first user's data with the HSS / UDM serving the first user, when the IMS AS address data for the first user changes in the HSS / UDM, it sends an Nhss_ImsSDM_Notification request message to the IMSEF / NEF, carrying the IMS AS address change information. In other words, when the IMS AS address changes, the HSS / UDM sends a second address to the IMSEF / NEF. After receiving the second address, the IMSEF / NEF returns an Nhss_ImsSDM_Notification response message to the HSS / UDM, indicating a successful notification.

[0345] Figure 6 is a schematic block diagram of a communication device 600 provided in an embodiment of the present application. The device 600 includes a transceiver unit 610 and a processing unit 620. The transceiver unit 610 can communicate with the outside world, and the processing unit 620 is used to process data. The transceiver unit 610 can also be referred to as a communication interface or a communication unit.

[0346] In a possible implementation, the apparatus 600 may further include a storage unit, which may be used to store instructions and / or data, and the processing unit 620 may read the instructions and / or data in the storage unit.

[0347] The device 600 can be used to execute the actions performed by the event subscription entity in the above method embodiment. In this case, the device 600 can be the event subscription entity or a component that can be configured in the event subscription entity. Among them, the transceiver unit 610 is used to perform the transceiver related operations on the event subscription entity side in the above method embodiment. For example, the transceiver unit 610 can be used to perform the operation of sending the first subscription information to the user data storage network element in step 3101 in Figure 3, the operation of sending the first event subscription request message to the first event notification entity in step 3105, and the operation of sending the first event notification response message to the first event notification request message in step 330. It can also be used to perform the operation of sending the first subscription information to HSS / UDM in step 420 in Figure 4, the operation of sending the first event notification response message to IMS AS in step 460, and the operation of sending the first subscription information deletion request information to HSS / UDM in step 470. It can also be used to perform the operation of sending the first request information to HSS / UDM in step 530 in Figure 5, the operation of sending the first event subscription request message to IMS AS in step 550, and the operation of sending the first event cancellation subscription request message to HSS / UDM in step 591. The processing unit 620 is used to perform operations related to processing on the event subscription entity side in the above method embodiment. For example, the processing unit 620 can be used to perform the operation of generating the first subscription information in step 410 in Figure 4.

[0348] Alternatively, the device 600 can be used to execute the actions performed by the user data storage network element in the above method embodiment. In this case, the device 600 can be a user data storage network element or a component that can be configured in the user data storage network element. The transceiver unit 610 is used to perform the operations related to transmission and reception on the user data storage network element side in the above method embodiment. For example, the transceiver unit 610 can be used to perform the operation of sending the first address to the event subscription entity in step 3104 in Figure 3, and can also be used to perform the operation of notifying the IMS AS that the first subscription information has been deleted in step 490 in Figure 4. It can also be used to perform the operation of sending the first address to the IMSEF / NEF in step 540 in Figure 5 and the operation of sending the first event unsubscription response message to the IMSEF / NEF in step 592. The processing unit 620 is used to perform the operations related to processing on the user data storage network element side in the above method embodiment.

[0349] Alternatively, the device 600 can be used to execute the actions performed by the event notification entity in the above method embodiment. In this case, the device 600 can be an event notification entity or a component that can be configured in the event notification entity, and the transceiver unit 610 is used to perform the transceiver-related operations on the event notification entity side in the above method embodiment. For example, the transceiver unit 610 can be used to execute the operation of sending the first event notification request message to the network element that needs to receive the first event notification request message in step 320 in Figure 3, and can also be used to execute the operation of sending the first event notification request message to the IMSEF / NEF in step 460 in Figure 4, and can also be used to execute the operation of sending the first event subscription response message to the IMSEF / NEF in step 560 in Figure 5. The processing unit 620 is used to execute the processing-related operations on the event notification entity side in the above method embodiment.

[0350] As shown in Figure 7, an embodiment of the present application further provides a communication device 700. The communication device 700 includes a processor 710, which is coupled to a memory 720. The memory 720 is used to store computer programs or instructions and / or data. The processor 710 is used to execute the computer programs or instructions and / or data stored in the memory 720, so that the method in the above method embodiment is executed.

[0351] In a possible implementation, the communication device 700 includes one or more processors 710 .

[0352] In a possible implementation, as shown in FIG. 7 , the communication device 700 may further include a memory 7720 .

[0353] In a possible implementation, the communication device 700 may include one or more memories 720 .

[0354] In a possible implementation, the memory 720 may be integrated with the processor 710 or provided separately.

[0355] In one possible implementation, as shown in Figure 7, the wireless communication device 700 may further include a transceiver 730, which is configured to receive and / or transmit signals. For example, the processor 710 is configured to control the transceiver 730 to receive and / or transmit signals.

[0356] As a solution, the communication device 700 is used to implement the operations performed by the event notification entity in the above method embodiment.

[0357] For example, the processor 710 is used to implement the processing-related operations performed by the event notification entity in the above method embodiment, and the transceiver 730 is used to implement the sending and receiving-related operations performed by the event notification entity in the above method embodiment.

[0358] As another solution, the communication device 700 is used to implement the operations performed by the user data storage network element in the above method embodiment.

[0359] For example, the processor 710 is used to implement the processing-related operations performed by the user data storage network element in the above method embodiment, and the transceiver 730 is used to implement the sending and receiving-related operations performed by the user data storage network element in the above method embodiment.

[0360] As another solution, the communication device 700 is used to implement the operations performed by the event subscription entity in the above method embodiment.

[0361] For example, the processor 710 is used to implement the processing-related operations performed by the event subscription entity in the above method embodiment, and the transceiver 730 is used to implement the sending and receiving-related operations performed by the event subscription entity in the above method embodiment.

[0362] As shown in FIG8 , an embodiment of the present application provides a chip system 800 . The chip system 800 (or also referred to as a processing system) includes a logic circuit 810 and an input / output interface 820 .

[0363] The logic circuit 810 may be a processing circuit in the chip system 800. The logic circuit 810 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 800 can implement the methods and functions of the various embodiments of the present application. The input / output interface 820 may be an input / output circuit in the chip system 800, outputting information processed by the chip system 800 or inputting data or signaling information to be processed into the chip system 800 for processing.

[0364] As a solution, the chip system 800 is used to implement the operations performed by the event subscription entity, the user data storage network element or the event notification entity in the above various method embodiments.

[0365] For example, the logic circuit 810 is used to implement the processing-related operations of the event subscription entity in the above method embodiment; the input / output interface 820 is used to implement the sending and / or receiving-related operations of the event subscription entity in the above method embodiment.

[0366] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the method executed by the event subscription entity in the above method embodiment, or the method executed by the user data storage network element, or the method executed by the event notification entity.

[0367] For example, when the computer program is executed by a computer, the computer can implement the method executed by the event subscription entity in the above method embodiment, or the method executed by the user data storage network element, or the method executed by the event notification entity.

[0368] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method executed by the event subscription entity in the above method embodiment, or the method executed by the user data storage network element, or the method executed by the event notification entity.

[0369] An embodiment of the present application further provides a communication system, which includes the event subscription entity, user data storage network element and event notification entity in the above embodiment.

[0370] The explanation and beneficial effects of the relevant contents in any of the wireless communication devices provided above may refer to the corresponding method embodiments provided above, and will not be repeated here.

[0371] In an embodiment of the present application, an event subscription entity, a user data storage network element, or an event notification entity may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system of the operating system layer may be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0372] The embodiments of the present application do not specifically limit the specific structure of the execution subject of the method provided in the embodiments of the present application. As long as it is possible to communicate according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application. For example, the execution subject of the method provided in the embodiments of the present application can be an event subscription entity, a user data storage network element, or an event notification entity, or a functional module in the event subscription entity, the user data storage network element, or the event notification entity that can call and execute the program.

[0373] Various aspects or features of the embodiments of the present application can be implemented as methods, devices, or articles of manufacture using standard programming and / or engineering techniques. As used herein, the term "article of manufacture" can encompass a computer program accessible from any computer-readable device, carrier, or medium. For example, a computer-readable medium can include, but is not limited to, magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.).

[0374] The various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0375] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0376] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM may include the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

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

[0378] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

[0380] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0381] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0383] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0384] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0385] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the embodiments of the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: include: The event subscription entity subscribes to a first event with a first event notification entity based on interaction between the event subscription entity and a user data storage network element, where the first event is an event related to an IMS session of a first user; The event subscription entity receives a first event notification request message sent by the first event notification entity, where the first event notification request message includes information about the first event.

2. The method according to claim 1, characterized in that The event subscription entity subscribes to the first event from the first event notification entity based on the interaction with the user data storage network element, including: The event subscription entity sends first subscription information to the user data storage network element, where the first subscription information is used to subscribe to information about the first event.

3. The method according to claim 2, characterized in that The first subscription information includes a user identifier of the first user, an identifier of the first event and a notification endpoint, wherein the notification endpoint identifies an address of a network element for receiving a notification request message of the first event.

4. The method according to claim 2 or 3, characterized in that: The event subscription entity sends first subscription information to the user data storage network element, including: The event subscription entity sends an IMS user data management update request message to the user data storage network element, where the IMS user data management update request message includes the first subscription information.

5. The method according to any one of claims 2 to 4, characterized in that The method further comprises: The event subscription entity sends first subscription information deletion request information to the user data storage network element, where the first subscription information deletion request information is used to request deletion of the first subscription information.

6. The method according to claim 5, characterized in that The event subscription entity sends first subscription information deletion request information to the user data storage network element, including: The event subscription entity sends an IMS user data management update request message or an IMS user data management deletion request message to the user data storage network element, and the IMS user data management update request message or the IMS user data management deletion request message includes the first subscription information deletion request information.

7. The method according to claim 1, characterized in that The event subscription entity subscribes to the first event from the first event notification entity based on the interaction with the user data storage network element, including: The event subscription entity receives a first address sent by the user data storage network element, where the first address is an address of the first event notification entity; The event subscription entity sends a first event subscription request message to the first event notification entity according to the first address, where the first event subscription request message is used to subscribe to information about the first event.

8. The method according to claim 7, characterized in that The method further comprises: The event subscription entity sends first request information to the user data storage network element, where the first request information is used to request to obtain the first address.

9. The method according to claim 8, characterized in that The event subscription entity sends first request information to the user data storage network element, including: The event subscription entity sends an IMS user data management acquisition request message to the user data storage network element, where the IMS user data management acquisition request message includes the first request information.

10. The method according to any one of claims 7 to 9, characterized in that The event subscription entity receives the first address sent by the user data storage network element, including: The event subscription entity receives an IMS user data management acquisition response message sent by the user data storage network element, where the IMS user data management acquisition response message includes the first address.

11. The method according to any one of claims 7 to 10, characterized in that The method further comprises: The event subscription entity receives a first event subscription response message from the first event notification entity, where the first event subscription response message is used to indicate that the first event has been subscribed successfully.

12. The method according to any one of claims 7 to 11, characterized in that The method further comprises: The event subscription entity sends a first event unsubscribe request message to the first event notification entity. The read request message is used to request to cancel the subscription to the first event.

13. The method according to any one of claims 7 to 12, characterized in that The method further comprises: The event subscription entity receives a first event unsubscription response message from the first event notification entity, where the first event unsubscription response message is used to indicate that the subscription to the first event has been canceled.

14. The method according to any one of claims 7 to 13, characterized in that The method further comprises: The event subscription entity receives a second address sent by the user data storage network element, where the second address is an address of a second event notification entity, and the second event notification entity is used to monitor information of the first event.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: The event subscription entity sends a first event notification response message to the first event notification entity, where the first event notification response message is used to indicate that the event subscription entity has successfully received the first event notification request message.

16. A communication method, characterized in that: include: The first event notification entity acquires, based on interaction between the first event notification entity and the user data storage network element, a subscription of the event subscription entity to a first event, where the first event is an event related to an IMS session of the first user; The first event notification entity sends a first event notification request message, where the first event notification request message includes information about the first event.

17. The method according to claim 16, characterized in that The first event notification entity obtains a subscription of the event subscription entity to the first event based on interaction with the user data storage network element, including: The first event notification entity obtains first subscription information at the user data storage network element, where the first subscription information is used to subscribe to information about the first event.

18. The method according to claim 17, characterized in that The first event notification entity obtains the first subscription information at a user data storage network element, including: The first event notification entity obtains user data information of a first user from the user data storage network element, where the user data information of the first user includes the first subscription information; or The first event notification entity receives the first subscription information sent by the user data storage network element.

19. The method according to claim 18, characterized in that The first event notification entity obtains user data information of the first user from the user data storage network element, including: The first event notification entity obtains an IMS user data management acquisition request message at the user data storage network element, where the IMS user data management acquisition request message includes user data information of the first user.

20. The method according to any one of claims 17 to 19, characterized in that The method further comprises: According to the first subscription information, the first event notification entity monitors the first event.

21. The method according to any one of claims 17 to 20, characterized in that The first subscription information includes a user identifier of the first user, an identifier of the first event and a notification endpoint, wherein the notification endpoint identifies an address of a network element for receiving a notification request message of the first event.

22. The method according to claim 21, characterized in that The network element that receives the first event notification request message is the event subscription entity.

23. The method according to claim 21 or 22, characterized in that The first event notification entity monitoring the first event according to the first subscription information includes: The first event notification entity monitors the first event according to the identifier of the first event.

24. The method according to any one of claims 21 to 23, characterized in that The first event notification entity sending the first event notification request message includes: The first event notification entity sends the first event notification request message according to the notification endpoint.

25. The method according to any one of claims 17 to 24, characterized in that The method further comprises: The first event notification entity receives notification information of first event subscription deletion sent by the user data storage network element, where the first event subscription deletion notification information is used to indicate that the first subscription information has been deleted.

26. The method according to claim 16, characterized in that The first event notification entity obtains a subscription of the event subscription entity to the first event based on interaction with the user data storage network element, including: The first event notification entity sends a first address and an identifier of the first user to the user data storage network element, where the first address is an address of the first event notification entity; The first event notification entity receives a first event subscription request message sent by the event subscription entity, where the first event subscription request message is used to request subscription to the first event.

27. The method according to claim 26, characterized in that The first event notification entity sending the first address and the identifier of the first user to the user data storage network element includes: The first event notification entity sends an IMS user management update request message to the user data storage network element, where the IMS user management update request message includes the first address and an identifier of the first user.

28. The method according to claim 26 or 27, characterized in that The method further comprises: The first event notification entity sends a first event subscription response message to the event subscription entity, where the first event subscription response message is used to indicate that the first event has been subscribed successfully.

29. The method according to any one of claims 26 to 28, characterized in that The method further comprises: The first event notification entity receives a first event unsubscription request message from the event subscription entity, where the first event unsubscription request message is used to request cancellation of subscription to the first event.

30. The method according to any one of claims 26 to 29, characterized in that The method further comprises: The first event notification entity sends a first event unsubscription response message to the event subscription entity, where the first event unsubscription response message is used to indicate that the subscription to the first event has been canceled.

31. The method according to any one of claims 16 to 30, characterized in that The method further comprises: The first event notification entity receives a first event notification response message, where the first event notification response message is used to indicate that the first event notification request message is successfully received.

32. A communication method, characterized in that: include: The user data storage network element receives first subscription information from an event subscription entity, where the first subscription information is used to subscribe to information about a first event, where the first event is an event related to an IMS session of a first user, and the first event is monitored by a first event notification entity; The user data storage network element sends the first subscription information or the user data information of the first user to the first event notification entity, where the user data information of the first user includes the first subscription information.

33. The method according to claim 32, characterized in that The first subscription information includes a user identifier of the first user, an identifier of the first event and a notification endpoint, wherein the notification endpoint identifies an address of a network element for receiving a first event notification request message.

34. The method according to claim 32 or 33, characterized in that The user data storage network element receives first subscription information from an event subscription entity, including: The user data storage network element receives an IMS user data management update request message from the event subscription entity, where the IMS user data management update request message includes the first subscription information.

35. The method according to any one of claims 32 to 34, characterized in that The method further comprises: The user data storage network element receives first subscription information deletion request information from the event subscription entity, where the first subscription information deletion request information is used to request deletion of the first subscription information; The user data storage network element deletes the first subscription information from the user data information of the first user.

36. The method according to claim 35, characterized in that The user data storage network element receives first subscription information deletion request information from the event subscription entity, including: The user data storage network element receives an IMS user data management update request message or an IMS user data management deletion request message from the event subscription entity, where the IMS user data management update request message or the IMS user data management deletion request message includes the first subscription information deletion request information.

37. The method according to any one of claims 32 to 36, characterized in that The method further comprises: The user data storage network element sends notification information of first event subscription deletion to the first event notification entity, where the notification information of first event subscription deletion is used to notify the first event notification entity that the first subscription information has been deleted.

38. The method according to claim 37, characterized in that The user data storage network element sends notification information of first event subscription deletion to the first event notification entity, including: The user data storage network element sends an IMS user data management notification request message to the first event notification entity, where the IMS user data management notification request message includes notification information of deletion of the first event subscription.

39. A communication method, characterized in that: include: The user data storage network element receives a first request message from an event subscription entity, wherein the first request message is used to request to obtain a first address, wherein the first address is an address of a first event notification entity, and the first event notification entity is used to monitor the subscription of the event subscription entity. the first event of the first user; The user data storage network element sends the first address to the event subscription entity.

40. The method according to claim 39, characterized in that The user data storage network element receives first request information from an event subscription entity, including: The user data storage network element receives an IMS user data management acquisition request message from the event subscription entity, where the IMS user data management acquisition request message includes the first request information.

41. The method according to claim 39 or 40, characterized in that The user data storage network element sends the first address to the event subscription entity, including: The user data storage network element sends an IMS user data management acquisition response message to the event subscription entity, and the IMS user data management acquisition response message includes the first address.

42. The method according to any one of claims 39 to 41, characterized in that The method further comprises: The user data storage network receives the first address and the identifier of the first user from the first event notification entity; The user data storage network element stores the first address in the user data information of the first user according to the identifier of the first user.

43. The method according to claim 42, characterized in that The user data storage network element receives the first address and the identifier of the first user from the first event notification entity, including: The user data storage network element receives an IMS user management update request message from the first event notification entity, where the IMS user management update request message includes the first address and an identifier of the first user.

44. The method according to any one of claims 39 to 43, characterized in that The method further comprises: The user data storage network element receives first event subscription request information sent by the event subscription entity, where the first event subscription request information is used to request the user data storage network element to subscribe to the first event; The user data storage network element sends second event subscription request information to the first event notification entity according to the first address, where the second event subscription request information is used to request the first event notification entity to subscribe to the first event.

45. The method according to any one of claims 39 to 44, characterized in that The method further comprises: The user data storage network element receives a second event subscription response message sent by the first event notification entity, where the second event subscription response message is used to indicate to the user data storage network element that the first event has been successfully subscribed on the first event notification entity; The user data storage network element sends a first event subscription response message to the event subscription entity, where the first event subscription response message is used to indicate to the event subscription entity that the first event has been successfully subscribed on the user data storage network element.

46. ​​The method according to any one of claims 39 to 45, characterized in that The method further comprises: The user data storage network element receives a first event unsubscribe request message sent by the event subscription entity, where the first event unsubscribe request message is used to request to cancel subscription to the first event; The user data storage network element sends a second event unsubscribe request message to the first event notification entity, where the first event unsubscribe request message is used to request to cancel subscription to the first event.

47. The method according to any one of claims 39 to 46, characterized in that The method further comprises: The user data storage network element receives a second event unsubscribe response message sent by the first event notification entity, where the second event unsubscribe response message is used to indicate that the subscription to the first event has been cancelled; The user data storage network element sends a first event unsubscription response message to the event subscription entity, where the first event unsubscription response message is used to indicate that the subscription to the first event has been canceled.

48. The method according to any one of claims 39 to 47, characterized in that The method further comprises: The user data storage network element sends a second address to the event subscription entity, where the second address is an address of a second event notification entity, and the second event notification entity is used to monitor information of the first event.

49. A communication device, characterized in that: include: A unit for implementing the method of any one of claims 1 to 15; or, a unit for implementing the method of any one of claims 16 to 31; or, a unit for implementing the method of any one of claims 32 to 38; or, a unit for implementing the method of any one of claims 39 to 48.

50. A computer-readable storage medium, characterized in that The computer readable storage medium stores a computer program. When the computer program is executed, Execute the method according to any one of claims 1 to 15, or Performing the method according to any one of claims 16 to 31, or Performing the method of any one of claims 32 to 38, or Perform the method as claimed in any one of claims 39 to 48.

51. A communication system, characterized in that: It includes one or more of an event subscription entity, a first event notification entity and a user data storage network element, the event subscription entity is used to execute the method as described in any one of claims 1 to 15, the first event notification entity is used to execute the method as described in any one of claims 16 to 31, the user data storage network element is used to execute the method as described in any one of claims 32 to 38, or the user data storage network element is used to execute the method as described in any one of claims 39 to 48.

Images