A method and device for subscription service

Abstract

A method and device for subscribing to a service, used to propose a mechanism for reporting service changes. A first network function network element sends a first message to a second network function network element, for subscribing a first service to the second network function network element for a third network function network element, the first message includes a first address, and the first address is the address of the first network function network element; the first network function network element receives the third message through the first address, and learns that the first service has changed according to the third message. In this method, since the first network function network element sends its own address to the second network function network element, when the first service changes, the first network function network element can receive a notification, which improves the mechanism for reporting service changes, so that the service subscription process can be more complete and will not cause interruptions.

Description

[0001] This application claims priority to a Chinese patent application filed with the State Intellectual Property Office of China on April 9, 2018, with application number 201810312964.8 and invention name “A method and device for subscription service”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] The fifth generation mobile communication technology (5G) system supports data connection and business enabling deployment. In the 5G system, the various network function network elements of the control plane can interact based on services. Among them, among the services provided by various network function network elements, there is a commonly used service called event exposure service. The main process of implementing the service is: when the service subscriber subscribes to the required service from the service provider, the address for receiving events is provided to the service provider, and then the service provider determines that the required event subscribed by the service subscriber can be provided, and then the required event is notified to the address for receiving events.

[0004] In practice, the status of a service or the subscription (i.e., subscription attributes) of a service may also change due to changes in user contracts, network policies, network capabilities, etc. For example, due to changes in user contracts, the originally authorized monitoring events are no longer allowed to be monitored and need to be cancelled, or due to changes in network capabilities, the originally authorized monitoring events cannot be monitored and need to be paused, etc. However, the existing subscription service process does not improve the communication between various devices when the status or subscription of the service changes, and does not establish a corresponding mechanism for the service provider to report service changes to the service subscriber, resulting in an imperfect subscription service process, which may cause the subscription service process to be interrupted. Summary of the invention

[0005] The present application provides a method and device for subscribing to a service, which are used to propose a mechanism for reporting changes in the service.

[0006] In a first aspect, the present application provides a method for subscribing to a service, the method comprising:

[0007] A first network function network element sends a first message to a second network function network element, for subscribing a first service to the second network function network element on behalf of a third network function network element, wherein the first message includes a first address; the first network function network element receives a third message via the first address, and learns that the first service has changed according to the third message; wherein the first address is the address of the first network function network element.

[0008] Through the above method, since the first network function network element sends its own address to the second network function network element, when the first service changes, the first network function network element can receive a notification of the service change, thereby improving the mechanism for reporting service changes, thereby making the service subscription process more complete and not causing interruptions.

[0009] In one possible design, before the first network function network element sends the first message to the second network function network element, it receives a second message from the third network function network element, where the second message is used to subscribe to a second service, and the second message includes a second address, which is the address of the third network function network element; the method also includes: the first network function network element determines the first service that needs to be subscribed to the second network function network element based on the second service; wherein the first message also includes the second address, which is used for the second network function network element to provide the first service to the third network function network element.

[0010] Through the above method, the first network function network element can determine the first service according to the second message, so as to subscribe to the first service from the second network function network element.

[0011] In one possible design, after the first network function network element learns that the first service has changed according to the third message, the first network function network element sends a fifth message to the second address of the third network function network element, and the fifth message is used to notify that the second service has changed. In this way, the third network function network element can learn that the service it subscribes to has changed.

[0012] In one possible design, the first message also includes indication information, and the indication information is used to indicate that a message notifying the change of the first service is received through the first address. In this way, after other network function network elements detect that the first service has changed, they can send a message notifying the change of the first service to the first address.

[0013] In one possible design, after the first network function network element sends the first message to the second network function network element, the method also includes: the first network function network element receives a second subscription association identifier from the second network function network element, where the second subscription association identifier is an identifier assigned by the second network function network element to the subscription of the first service; wherein the third message also includes the second subscription association identifier, then the first network function network element learns that the first service has changed according to the third message, including: the first network function network element learns that the first service has changed according to the second subscription association identifier in the third message.

[0014] Through the above method, the first network function network element can accurately know that the first service has changed.

[0015] In one possible design, after the first network function network element receives the second message from the third network function network element, the first network function network element allocates a first subscription association identifier for the subscription to the second service, and sends the first subscription association identifier to the third network function network element; the first network function network element sends the fifth message to the second address of the third network function network element, including: the first network function network element sends the fifth message including the first subscription association identifier to the second address of the third network function network element.

[0016] In one possible design, before the first network function network element sends the first message to the second network function network element, the method also includes: the first network function network element allocates a first notification association identifier; the first network function network element sends the first message to the second network function network element, including: the first network function network element sends the first message including the first notification association identifier to the second network function network element; wherein the third message received by the first network function network element through the first address also includes the first notification association identifier, then the first network function network element learns that the first service has changed according to the third message, including: the first network function network element learns that the first service has changed according to the first notification association identifier in the third message.

[0017] Through the above method, the first network function network element can accurately identify that the first service has changed.

[0018] In one possible design, the second message also includes a second notification association identifier, which is allocated to the third network function network element; the first network function network element sends the fifth message to the second address of the third network function network element, including: the first network function network element sends the fifth message including the second notification association identifier to the second address of the third network function network element.

[0019] In one possible design, the change in the first service refers to a change in the state of the first service and / or a change in the subscription of the first service. In one possible design, the subscription change includes a change in a subscription association identifier or a change in event report information, wherein the event report information change includes at least one of the following: a change in the event report mode, a change in the maximum number of event reports, and a change in the maximum duration of event reports.

[0020] Through the above method, the specific situation in which the first service is changed can be accurately determined.

[0021] In a possible design, when the change in the first service refers to the change in the state, the third message also includes first state information; wherein the first state information is a pause state, a continue state, a cancel state, or a delete state. In this way, the first network function network element can be informed of the current state of the subscribed service.

[0022] In a possible design, the third message also includes an event identifier and / or a user identifier corresponding to the first state information. This allows the first network function network element to be informed of the event in which the state has changed or the user corresponding to the event in which the state has changed.

[0023] In one possible design, when the change in the first service refers to the subscription change, the third message also includes the subscription attributes of the first service after the subscription change; this allows the first network function network element and the third network function network element to know the current subscription attributes of the subscribed service.

[0024] In one possible design, when the subscription change is a subscription association identifier change, the subscription attribute after the subscription change of the first service is an updated subscription association identifier. In this way, the first network function network element and the third network function network element can accurately know the subscription attribute after the specific subscription change.

[0025] In one possible design, when the subscription is changed to an event report information change, the subscription attribute after the subscription of the first service is changed includes at least one of the following: an updated event report mode, a maximum number of updated event reports, and a maximum duration of updated event reports. In this way, the first network function network element can accurately know the subscription attribute after the specific subscription is changed.

[0026] In one possible design, the first network function network element receives the third message through the first address in the following two ways: in the first way, the first network function network element receives the third message from the second network function network element through the first address; in the second way, the first network function network element receives the third message from the fourth network function network element through the first address, wherein the second network function network element requests the first service from the fourth network function network element on behalf of the third network function network element.

[0027] Through the above method, the first network function network element can successfully receive the message notifying the change of the first service through the first address.

[0028] In one possible design, the indication information is a third event identifier set, wherein the third event identifier set includes a state change event identifier and / or a subscription change event identifier. In this way, other network function network elements can be triggered by specific events to detect whether the first service has changed.

[0029] In a possible design, the subscription change event identifier includes a subscription association identifier change event identifier or an event report information change event identifier. In this way, the event of detecting a change in the first service can be accurately determined.

[0030] In a possible design, the third message also includes at least one event identifier in the third event identifier set. This enables the first network function network element to identify which specific changes have occurred in the first service.

[0031] In a second aspect, an embodiment of the present application provides a method for subscribing to a service, the method comprising:

[0032] The second network function network element receives a first message from the first network function network element, where the first message is used by the first network function network element to subscribe to a first service from the second network function network element on behalf of a third network function network element, and the first message includes a first address, which is the address of the first network function network element; the second network function network element sends a third message to the first address of the first network function network element, so as to inform the first network function network element that the first service has changed.

[0033] Through the above method, since the first network function network element sends its own address to the second network function network element, when the first service changes, the first network function network element can receive a notification of the service change, thereby improving the mechanism for reporting service changes, thereby making the service subscription process more complete and not causing interruptions.

[0034] In one possible design, the first message also includes a second address, the second address is the address of the third network function network element, and the second network function network element provides the first service to the third network function network element according to the second address. In this way, when the first service is normal, the second network function network element can normally notify the third network function network element of the required events.

[0035] In one possible design, the first message also includes indication information, and the indication information is used to indicate that a message notifying the change of the first service is received through the first address. In this way, after the second network function network element detects that the first service has changed, it can send a message notifying the change of the first service to the first address.

[0036] In a possible design, after receiving the first message from the first network function network element, the second network function network element allocates a second subscription association identifier for the subscription of the first service; then the second network function network element sends a third message to the first address of the first network function network element, including: the second network function network element carries the second subscription association identifier in the third message, and sends the third message to the first address of the first network function network element. In this way, the first network function network element can be informed of the change of the first service through the second subscription association identifier in the third message.

[0037] In a possible design, the first message also includes a first notification association identifier; then the second network function network element sends the third message to the first address of the first network function network element, including: the second network function network element sends the third message including the first notification association identifier to the first address of the first network function network element. In this way, the first network function network element can be informed of the change of the first service through the first notification association identifier in the third message.

[0038] In one possible design, the change in the first service refers to a change in the state of the first service and / or a change in the subscription of the first service. In one possible design, the subscription change includes a change in a subscription association identifier or a change in event report information, wherein the event report information change includes at least one of the following: a change in the event report mode, a change in the maximum number of event reports, and a change in the maximum duration of event reports.

[0039] Through the above method, the specific situation in which the first service is changed can be accurately determined.

[0040] In one possible design, when the change in the first service refers to the change in the state, the third message also includes first state information, and the first state information is a pause state, a continue state, a cancel state, or a delete state. In this way, the first network function network element can be informed of the current state of the subscribed service.

[0041] In a possible design, the third message also includes an event identifier and / or a user identifier corresponding to the first state information. This allows the first network function network element to be informed of the event in which the state has changed or the user corresponding to the event in which the state has changed.

[0042] In a possible design, when the change in the first service refers to the subscription change, the third message also includes the subscription attributes of the first service after the subscription change. In this way, the first network function network element can be informed of the current subscription attributes of the subscribed service.

[0043] In a possible design, when the subscription change is a subscription association identifier change, the subscription attribute after the subscription change of the first service is an updated subscription association identifier. In this way, the first network function network element can accurately know the subscription attribute after the specific subscription change.

[0044] In one possible design, when the subscription is changed to an event report information change, the subscription attribute after the subscription of the first service is changed includes at least one of the following: an updated event report mode, a maximum number of updated event reports, and a maximum duration of updated event reports. In this way, the first network function network element can accurately know the subscription attribute after the specific subscription is changed.

[0045] In one possible design, the indication information is a third event identifier set, wherein the third event identifier set includes a state change event identifier and / or a subscription change event identifier. In this way, the second network function network element can be triggered by a specific event to detect whether the first service has changed.

[0046] In one possible design, the subscription change event identifier includes a subscription association identifier change event identifier or an event report information change event identifier. This enables the second network function network element to accurately determine the event of detecting a change in the first service.

[0047] In a possible design, the third message also includes at least one event identifier in the third event identifier set. This enables the first network function network element to identify which specific changes have occurred in the first service.

[0048] In one possible design, the second network function element requests the first service from the fourth network function element and sends the first address to the fourth network function element. In this way, after the UE reselects the fourth network function element due to the movement of the UE, the fourth network function element can send a message to the first address notifying that the first service has changed.

[0049] In a third aspect, the present application further provides a first network function network element, which has the function of implementing the first network function network element behavior in the above method example. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0050] In one possible design, the structure of the first network function network element includes a sending unit, a receiving unit and a processing unit. These units can perform the corresponding functions in the above method example. Please refer to the detailed description in the method example for details, which will not be repeated here.

[0051] In one possible design, the structure of the first network function network element includes a transceiver and a processor, and optionally a memory, the transceiver is used to send and receive data, and to communicate and interact with other devices in the communication system, and the processor is configured to support the first network function network element to perform corresponding functions in the above method. The memory is coupled to the processor and stores necessary program instructions and data for the first network function network element.

[0052] In a fourth aspect, the present application further provides a second network function network element, which has the function of implementing the second network function network element behavior in the above method example. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0053] In one possible design, the structure of the second network function network element includes a receiving unit, a sending unit and a processing unit. These units can perform the corresponding functions in the above method example. Please refer to the detailed description in the method example for details, which will not be repeated here.

[0054] In one possible design, the structure of the second network function network element includes a transceiver and a processor, and optionally a memory, the transceiver is used to send and receive data, and to communicate and interact with other devices in the communication system, and the processor is configured to support the second network function network element to perform corresponding functions in the above method. The memory is coupled to the processor and stores necessary program instructions and data for the second network function network element.

[0055] In a fifth aspect, the present application further provides a system, the system comprising a first network function network element, the first network function network element can be used to execute the steps performed by the first network function network element in the above-mentioned first aspect and any method of the first aspect. In one possible design, the system may also include a second network function network element, the second network function network element can be used to execute the steps performed by the second network function network element in the above-mentioned first aspect and any method of the first aspect. In one possible design, the system may also include other devices that interact with the first network function network element and / or the second network function network element in the solution provided in the embodiment of the present application, such as a third network function network element, etc.

[0056] In a sixth aspect, the present application further provides a system, the system comprising a second network function network element, the second network function network element can be used to execute the steps performed by the second network function network element in the second aspect and any of the methods of the second aspect. In one possible design, the system may also include a first network function network element, the first network function network element can be used to execute the steps performed by the first network function network element in the second aspect and any of the methods of the second aspect. In one possible design, the system may also include other devices that interact with the first network function network element and / or the second network function network element in the solution provided in the embodiment of the present application, such as a third network function network element, etc.

[0057] In a seventh aspect, the present application further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions, when called by the computer, are used to cause the computer to execute any of the above methods.

[0058] In an eighth aspect, the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute any of the above methods.

[0059] In a ninth aspect, the present application also provides a chip, which is connected to a memory and is used to read and execute program instructions stored in the memory to implement any of the above methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 A schematic diagram of the architecture of a communication system provided for this application;

[0061] Figure 2 A flowchart of a method for subscription service provided for this application;

[0062] Figure 3 A flowchart of an example of a method for subscription service provided by the present application;

[0063] Figure 4 A flowchart of an example of another subscription service method provided by the present application;

[0064] Figure 5 A flowchart of another method for subscription service provided for the present application;

[0065] Figure 6 A schematic diagram of the structure of a device provided in this application;

[0066] Figure 7 A schematic diagram of the structure of another device provided in this application;

[0067] Figure 8 A structural diagram of a first network function network element provided by this application;

[0068] Fig. 9 A structural diagram of a second network function network element provided in this application. DETAILED DESCRIPTION

[0069] The present application will be described in further detail below in conjunction with the accompanying drawings.

[0070] The embodiment of the present application provides a method and device for subscribing to a service, which is used to propose a mechanism for reporting changes in a service. The method and device described in the present application are based on the same inventive concept. Since the method and device solve the problem in a similar way, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0071] Below, some terms in this application are explained to facilitate understanding by those skilled in the art.

[0072] 1) The first network function network element, the second network function network element and the third network function network element are network function network elements located in the core network control plane, support event open services, and can communicate and interact based on the event open services. Specifically, in the embodiment involved in the present application, the first network function network element is the first network function network element subscribing to the second network function network element. Among them, the first network function network element may be, but not limited to, a data management network element, a policy control function network element, etc. For example, the data management network element may be UDM (unified data management), etc., the policy control function network element may be PCF (policy control function), etc., the second network function network element may be, but not limited to, a core network access and mobility management function network element, a session management function network element, etc. For example, the core network access and mobility management function network element may be AMF (core access and mobility management function), etc., the session management function network element may be SMF (session management function), etc., the third network function network element may be, but not limited to, a network exposure function network element, etc., for example, it may be NEF (network exposure function), etc. For example, when the first network function network element is UDM, the corresponding second network function network element may be AMF; for another example, when the first network function network element is SMF, the corresponding second network function network element may be SMF. Among them, in the above examples of three network function network elements, the names of the network elements are only exemplary. In future communications, the names of the above network elements may change, and this application does not limit this.

[0073] 2) In the description of this application, words such as "first" and "second" are only used for the purpose of distinguishing the description and cannot be understood as indicating or implying relative importance or order.

[0074] 3) "And / or" describes the relationship between the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0075] In order to more clearly describe the technical solution of the embodiment of the present application, the business data acquisition method and device provided by the embodiment of the present application are described in detail below with reference to the accompanying drawings.

[0076] The method for subscribing to services provided in the embodiments of the present application is applicable to a possible communication system architecture, which may include a network open function network element, a policy control function network element, a data management network element, an application function network element, a core network access and mobility management function network element, a session management function network element, a terminal device, an access network device, a user plane function network element, and a data network. Among them, Figure 1 A possible example of the architecture of the communication system is shown, specifically including: NEF network element, PCF network element, UDM network element, AF network element, AMF network element, SMF network element, UE, access network (AN) equipment, UPF network element and data network (DN). Among them, the AMF network element and the terminal device can be connected through the N1 interface, the AMF and the AN device can be connected through the N2 interface, the AN device and the UPF can be connected through the N3 interface, the SMF and the UPF can be connected through the N4 interface, and the UPF and the DN can be connected through the N6 interface. The interface name is only an example description, and the embodiments of the present application do not specifically limit this. It should be understood that the embodiments of the present application are not limited to Figure 1 The communication system shown, Figure 1 The names of the network elements shown in the figure are only used as an example and are not intended to limit the network elements included in the communication system architecture to which the method of the present application is applicable. The functions of each network element or device in the communication system are described in detail below:

[0077] The terminal device, which can also be called user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a device that provides voice and / or data connectivity to users. For example, the terminal device may include a handheld device with wireless connection function, a vehicle-mounted device, etc. At present, the terminal device can be: a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home, etc. Among them, Figure 1 The terminal device described in the figure is shown as UE, which is only an example and does not limit the terminal device.

[0078] Wireless access networks can be Figure 1The access network (AN) shown in the figure provides wireless access services to the terminal device. The access network device is a device in the communication system that connects the terminal device to the wireless network. The access network device is a node in the wireless access network, which can also be called a base station, or a radio access network (RAN) node (or device). At present, some examples of access network devices are: gNB, transmission reception point (TRP), evolved Node B (evolved Node B, eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), base band unit (BBU), or wireless fidelity (Wifi) access point (AP), etc.

[0079] The data network, for example Figure 1 The data network (DN) shown may be the Internet, an IP Multimedia Service (IMS) network, a regional network (i.e., a local network, such as a mobile edge computing (MEC) network), etc. The data network includes an application server, and the application server provides business services to the terminal device by performing data transmission with the terminal device.

[0080] The core network is used to connect the terminal device to the DN that can realize the service of the terminal device. The functions of each network element in the core network are described below:

[0081] The core network access and mobility management function network element can be used to manage the access control and mobility of the terminal device. In practical applications, it includes the mobility management function in the mobility management entity (MME) in the network framework of long term evolution (LTE), and adds the access management function, which can be responsible for the registration of the terminal device, mobility management, tracking area update process, reachability detection, selection of session management function network element, mobile state transition management, etc. For example, in 5G, the core network access and mobility management function network element can be an AMF (access and mobility management function) network element, such as Figure 1 As shown, in future communications, such as 6G, the core network access and mobility management function network element can still be an AMF network element, or have other names, which are not limited in this application. When the core network access and mobility management function network element is an AMF network element, the AMF can provide Namf services.

[0082] The session management function network element may be used to be responsible for the session management of the terminal device (including the establishment, modification and release of the session), the selection and reselection of the user plane function network element, the allocation of the Internet Protocol (IP) address of the terminal device, and the control of the quality of service (QoS). For example, in 5G, the session management function network element may be an SMF (session management function) network element, such as Figure 1 As shown, in future communications, such as 6G, the session management function network element may still be an SMF network element, or have other names, which are not limited in this application. When the session management function network element is an SMF network element, the SMF may provide Nsmf services.

[0083] The policy control function network element can be used to be responsible for policy control decisions, provide functions such as service data flow and application detection, gating, QoS and flow-based charging control, etc. For example, in 5G, the policy control function network element can be a PCF (policy control function) network element, such as Figure 1 As shown, in future communications, such as 6G, the policy control function network element may still be a PCF network element, or have other names, which are not limited in this application. When the policy control function network element is a PCF network element, the PCF network element may provide Npcf services.

[0084] The main function of the application function network element is to interact with the 3rd generation partnership project (3GPP) core network to provide services, to affect service flow routing, access network capability opening, policy control, etc. For example, in 5G, the application function network element can be an AF (application function) network element, such as Figure 1 As shown, in future communications, such as 6G, the application function network element may still be an AF network element, or have other names, which are not limited in this application. When the application function network element is an AF network element, the AF network element may provide Naf services.

[0085] The data management network element may be used to manage the subscription data of the terminal device, registration information related to the terminal device, etc. For example, in 5G, the data management network element may be a unified data management network element (UDM), such as Figure 1 As shown, in future communications, such as 6G, the data management network element may still be a UDM network element, or have other names, which are not limited in this application. When the data management network element is a UDM network element, the UDM network element may provide Nudm services.

[0086] The network exposure function network element can be used to enable 3GPP to securely provide network service capabilities to third-party AFs (e.g., service capability servers (SCS), application servers (AS), etc.). For example, in 5G, the network exposure function network element can be NEF (network exposure function), such as Figure 1 As shown, in future communications, such as 6G, the network open function network element can still be a NEF network element, or have other names, which are not limited in this application. When the network open function network element is a NEF, the NEF can provide Nnef services to other network function network elements.

[0087] The above network elements in the core network can also be called functional entities, which can be network elements implemented on dedicated hardware, software instances running on dedicated hardware, or instances of virtualized functions on an appropriate platform. For example, the above virtualization platform can be a cloud platform.

[0088] It should be noted that Figure 1 The architecture of the communication system shown is not limited to including only the network elements shown in the figure, but may also include other devices not shown in the figure, which will not be listed one by one in this application.

[0089] It should be noted that the embodiments of the present application do not limit the distribution form of each network element in the core network. Figure 1 The distribution form shown is only exemplary and is not limited in this application.

[0090] For the convenience of explanation, this application will be referred to as Figure 1 The network element shown in the figure is used as an example for explanation, and the XX network element is directly referred to as XX. It should be understood that the names of all network elements in this application are only examples, and they can also be called other names in future communications, or the network elements involved in this application can also be replaced by other entities or devices with the same functions in future communications, and this application does not limit this. A unified explanation is given here, and no further description will be given later.

[0091] It should be noted that Figure 1 The communication system shown does not constitute a limitation on the communication systems to which the embodiments of the present application can be applied. Figure 1 The communication system architecture shown is a 5G system architecture. Optionally, the method of the embodiment of the present application is also applicable to various future communication systems, such as 6G or other communication networks.

[0092] A subscription service method provided in an embodiment of the present application is applicable to Figure 1 The communication system shown. Figure 2 As shown, the specific process of the method includes:

[0093] Step 201: A first network function network element sends a first message to a second network function network element, for subscribing a first service to the second network function network element for a third network function network element, wherein the first message includes a first address, and the first address is the address of the first network function network element. The first address (the address may also be referred to as a notification endpoint) may be at least one or a combination of the following: an Internet protocol (IP) address of the first network device, a port number of the first network function network element, a uniform resource locator (URL), etc.

[0094] The first network function network element sends a first message to the second network function network element in order to subscribe the second network function network element to a first service provided to the third network function network element, that is, the first network function network element subscribes on behalf of the third network function network element.

[0095] The first network function network element may be Figure 1 UDM, PCF, etc. in the communication system shown; the second network function network element may be Figure 1AMF, SMF, etc. in the communication system shown; the third network function network element may be the Figure 1 The NEF in the communication system shown in the figure is not limited in this application.

[0096] In an optional embodiment, before the first network function network element sends the first message to the second network function network element, the method also includes: the first network function network element assigns a first notification association identifier to the first address; the first network function network element sends the first message to the second network function network element including: the first network function network element sends the first message including the first notification association identifier to the second network function network element, so that when the message returned subsequently by other network elements carries the first notification association identifier, it can be known that the message is related to the subscription to the first service.

[0097] Optionally, the first message also includes indication information, where the indication information is used to indicate that a message notifying a change in the first service is received through the first address.

[0098] In an optional implementation, the indication information may be only an indication information value, or may be an event identifier set (referred to as a third event identifier set in the embodiment of the present application). When the indication information is the third event identifier set, the third event identifier set may include a state change event identifier and / or a subscription change event identifier, etc. Optionally, the subscription change event identifier may include a subscription association identifier change event identifier or an event report information change event identifier, etc.

[0099] In an optional implementation, in a scenario where the first message does not include the indication information mentioned above, after the second network function network element receives the first message, it finds that the first message carries an additional address compared to the prior art and the address is not associated with any event identifier, that is, it carries the first address and the first address is not associated with any event identifier. Then, it can automatically identify that the first network function network element receives the message notifying the change of the first service through the first address. That is to say, in this scenario, the first address has the following function: implicitly indicating that the message notifying the change of the first service is received through the first address. Of course, in this scenario, when the second network function network element discovers the first address, it can also use any other form, such as using the currently configured mechanism to identify that the first address can receive the message notifying the change of the first service, and this application does not limit this.

[0100] In an optional implementation, the change in the first service refers to a change in the state of the first service and / or a change in the subscription of the first service (i.e., the subscription of the first service). The change in the state of the first service may be a change in the current state of the first service, for example, the current state of the first service may be, but is not limited to, a pause state, a resume state, a cancel state, or a delete state, etc. The change in the subscription of the first service may be a change in a subscription attribute, for example, the subscription change may include a change in a subscription association identifier or a change in event report information, wherein the change in event report information includes at least one of the following: a change in the mode of event reporting, a change in the maximum number of event reports, and a change in the maximum duration of event reporting.

[0101] In an optional implementation, before the first network function network element sends the first message to the second network function network element, the first network function network element further executes: the first network function network element receives a second message from the third network function network element, and the second message is used to subscribe to a second service. At this time, the first message sent by the third network function network element to the first network function network element can be regarded as a trigger message received by the first network function network element, thereby triggering the first network function network element to execute step 201.

[0102] In an optional implementation, after the first network function network element receives the second message, the method further includes: the first network function network element determines the first service that needs to be subscribed to the second network function network element according to the second service. Optionally, the message for subscribing to the first service (i.e., the first message) includes a first event identifier set, and the second message includes a second event identifier set. The first network function network element determines a set of event identifiers corresponding to events that need to be provided by the second network function network element from the second event identifier set, and the determined set of event identifiers is the first event identifier set.

[0103] Specifically, the second message includes a second address, which is the address of the third network function network element; optionally, the first message also includes the second address, so that the second network function network element provides the first service to the third network function network element through the second address.

[0104] In an optional implementation, the second message further includes a second notification association identifier, where the second notification association identifier is allocated by the third network function network element to the second address.

[0105] Optionally, after the first network function network element receives the second message from the third network function network element, the first network function network element allocates a first subscription association identifier for the subscription of the second service (i.e., the subscription of the second service), and sends the first subscription association identifier to the third network function network element. Optionally, when the first network function network element sends the first subscription association identifier, the first subscription association identifier may be carried in an event open subscription response (Nnf_EventExposure_Subscribe Response) sent by the first network function network element to the third network function network element.

[0106] In an optional implementation, after the first network function network element sends the first message to the second network function network element, the method also includes: the first network function network element receives a second subscription association identifier from the second network function network element, and the second subscription association identifier is a subscription association identifier allocated by the second network function network element for the subscription to the first service (i.e., the subscription of the first service) (i.e., if the message subsequently received by the first network function network element contains the second subscription association identifier, the first network function network element knows that the message is related to the subscription to the first service).

[0107] Step 202: The first network function network element receives a third message through the first address.

[0108] In an optional implementation manner, the first network function network element receives the third message through the first address, which may specifically include the following two situations:

[0109] The first situation: the first network function network element receives the third message from the second network function network element through the first address.

[0110] The second situation: the first network function network element receives the third message from the fourth network function network element through the first address, and the second network function network element requests the first service from the fourth network function network element on behalf of the third network function network element.

[0111] Specifically, in the first case above, after the second network function network element detects that the first service has changed (specifically, refer to the description of the change of the first service mentioned in step 201 above), it sends the third message to the first network function network element. For example, due to a change in network policy, the current state of the first service changes from being able to execute normally to being suspended (Suspend), and then from Suspend to being resumed (Resume), etc.; for another example, due to a network policy or a user's contract, the subscription to the first service is canceled (Cancel) or deleted (Delete), etc. In the above second situation, there may be three scenarios: In the first scenario: due to the movement of the UE, the network element serving the UE is switched from the second network function network element to the fourth network function network element. At this time, the fourth network function network element has the same function as the second network function network element. In this scenario, the second network function network element generates context information based on the subscription information for the first service, and sends the context information to the fourth network function network element to request the first service from the fourth network function network element, and sends the first address (which may be included in the above context information) to the fourth network function network element. Subsequently, the fourth network function network element detects that the first service has changed (for example, the fourth network function is a subscriber of the first service). In the second scenario, due to the movement of the UE, the network element serving the UE is switched from the second network function network element to the fourth network function network element. At this time, the functions of the fourth network function network element and the second network function network element are different. In this scenario, the second network function network element generates context information according to the subscription information of the first service, and sends the context information to the fourth network function network element to request the first service from the fourth network function network element, and sends the first address to the fourth network function network element. After the fourth network function network element detects that the first service has changed according to its own function, it sends the third message to the first network function network element. In the third scenario: when the second network function network element is also unable to provide the first service, the second network function network element sends a fourth message to other network function network elements, that is, to the fourth network function network element. The fourth message includes the first address for subscribing to the first service. In this way, after the fourth network function network element detects that the first service has changed, it sends the third message to the first network function network element.

[0112] In an optional embodiment, when the first message includes the indication information and the indication information is the third event identifier set, the third message also includes at least one event identifier in the third event identifier set, so that the first network function network element can identify what specific changes have occurred in the first service.

[0113] Step 203: The first network function network element learns that the first service has changed according to the third message.

[0114] In an optional embodiment, after the first network function network element learns that the first service has changed based on the third message, the method further includes: the first network function network element sends a fifth message to the second address of the third network function network element, and the fifth message is used to notify the second service of the change.

[0115] In an optional implementation, the first network function network element sending the fifth message to the second address of the third network function network element includes: the first network function network element sending the fifth message including the first subscription association identifier mentioned in the above step 201 to the second address of the third network function network element.

[0116] In an optional implementation, the third message also includes the second subscription association identifier mentioned in the above step 201; then the first network function network element learns that the first service has changed according to the third message, including: the first network function network element learns that the first service has changed according to the second subscription association identifier in the third message.

[0117] In an optional implementation, the third message received by the first network function network element through the first address also includes the first notification association identifier mentioned in the above step 201; then the first network function network element learns that the first service has changed according to the third message, including: the first network function network element learns that the first service has changed according to the first notification association identifier in the third message (that is, if the message subsequently received by the first network function network element contains the first notification association identifier, the first network function network element learns that the message is related to the subscription to the first service).

[0118] In an optional implementation, the first network function network element sends the fifth message to the second address of the third network function network element, including: the first network function network element sends the fifth message including the second notification association identifier mentioned in the above step 201 to the second address of the third network function network element.

[0119] Optionally, in a specific implementation, when the change in the first service refers to the state change mentioned in the above step 201, the third message also includes the first state information; the fifth message also includes the second state information; wherein the first state information or the second state information may be a pause state, a resume state, a cancel state or a delete state, etc. Optionally, the third message also includes an event identifier and / or a user identifier corresponding to the first state information.

[0120] Optionally, when the change in the first service refers to the subscription change mentioned in the above step 201, the third message also includes the subscription attributes of the first service after the subscription change; the fifth message also includes the subscription attributes of the second service after the subscription change. Specifically, when the subscription change is a subscription association identifier change, the subscription attributes of the first service after the subscription change or the subscription attributes of the second service after the subscription change are updated subscription association identifiers; when the subscription change is an event report information change, the subscription attributes of the first service after the subscription change or the subscription attributes of the second service after the subscription change may include at least one of the following: an updated event report mode, an updated maximum number of event reports, and an updated maximum duration of event reports.

[0121] Using the method for subscribing to a service provided in an embodiment of the present application, a first network function network element sends a first message to a second network function network element, for subscribing a first service to the second network function network element for a third network function network element, the first message includes a first address, and the first address is the address of the first network function network element; the first network function network element receives the third message through the first address, and learns that the first service has changed according to the third message. In this method, since the first network function network element sends its own address to the second network function network element, when the first service changes, the first network function network element can receive a notification of the service change, thus improving the mechanism for reporting service changes, so that the service subscription process can be more complete and will not cause interruptions.

[0122] under Figure 3 ,4,5 embodiments, based on Figure 2 The embodiment of the present application describes in detail the method of subscription service provided in the embodiment of the present application with specific examples.

[0123] like Figure 3As shown, the embodiment of the present application also provides an example of a method for subscribing to a service. In this example, the first network function network element is UDM, the second network function network element is AMF, and the third network function network element is NEF. The NEF subscribes to a service (also called a subscription event notification service) from the UDM, and the UDM further subscribes to a service from the NEF to the AMF. Specifically, the process of this example may include:

[0124] Step 301: The NEF obtains trigger information. Specifically, after the NEF obtains the trigger information, it triggers the NEF to subscribe to the service from the UDM.

[0125] Optionally, the trigger information may come from other network function elements, such as AF; the trigger information may also come from the triggering of an internal trigger mechanism of the NEF.

[0126] Step 302: The NEF sends a second message to the UDM, and the NEF subscribes to a second service from the UDM through the second message.

[0127] The second message includes the address of the NEF, that is, the second address, so that the NEF receives the required events through the second address. In an optional implementation, the second message also includes the above Figure 2 The second event identifier set (e.g., Event Id1) and the second notification correlation identifier (e.g., Notification Correlation ID) mentioned in the embodiment. The second event identifier set may include at least one event identifier; the second notification correlation identifier is used by the NEF to associate the subsequently received event notification (Event Notification) (i.e., the information in the subsequently received fifth message) with the previously issued event subscription (Event Subscription) (i.e., the subscription information of the second message to the second service).

[0128] In an optional implementation, the second message also includes an external identifier of the UE (for example, for one UE), a group identifier of a group of UEs (for example, for a group of UEs), or an indication of any UE (for example, any UE parameter, which is valid for all UEs in the existing network), so that it can be determined for whom the second service is ultimately provided.

[0129] In an optional implementation, the second message also includes event report information, and the event report information includes at least one of the following: event report mode, maximum number of event reports, and maximum duration of event reports. The event report mode can be one-time report, continuous report, periodic report, etc.

[0130] In an optional implementation, the second message may be an event exposure subscription request (Nudm_Event Exposure_Subscribe Request) sent by the NEF to the UDM. In specific implementation, the NEF sends a hypertext transfer protocol request (HTTP POST) to the UDM, wherein the destination address of the request may be a uniform resource locator (URL) 1, and the message body of the HTTP POST carries the information that may be included in the second message mentioned above, which will not be described in detail here.

[0131] Step 303: The UDM saves the information in the second message, and allocates a first subscription correlation identifier (Subscription Correlation ID 1) for the subscription of the second service in the second message.

[0132] In specific implementation, the UDM creates resources for the subscription of the second service according to the information carried in the body, generates a sub-resource identifier subscription id1, and constructs a Uniform Resource Locator (URI) 1 for the created resource. The URI1 is generated by taking the requested URI as the parent resource and then concatenating the sub-resource identifier. The subscription id 1 here can be used as SubscriptionCorrelation ID 1.

[0133] Step 304: The UDM sends a first message to the AMF, and the UDM subscribes to a first service from the AMF through the first message. The first message includes the address of the UDM, that is, the first address.

[0134] Optionally, the UDM determines the first service that needs to be subscribed to the AMF based on the second service. Specifically, the first message also includes a first event identifier set, and the first event identifier set is generated based on the second event identifier set, wherein the first event identifier set is a set of event identifiers corresponding to events in the second event identifier set that need to be provided by the AMF, and the second event identifier set is included in the second message.

[0135] For example, after receiving the second message, the UDM first determines the events in the second event set corresponding to the second event identifier set in the second message that need to be provided by the AMF (that is, the second event set corresponding to the second event identifier set described above in the embodiment of the present application), and then executes step 304. That is to say, the first event identifier set in the first message is specifically determined according to the second event identifier set in the second message, for example, the first event identifier set is part or all of the event identifier sets in the second event identifier set.

[0136] Specifically, the first message includes, in addition to the first address, the second address, which is used by the AMF to provide the first service to the NEF. When the first service changes, the UDM can receive a message notifying the change of the first service through the first address.

[0137] In an optional embodiment, the first message also includes indication information, and the indication information is used to indicate that a message notifying the change of the first service is received through the first address. Specifically, the change of the first service refers to a change in the state of the first service and / or a change in the subscription of the first service. Among them, the state change of the first service can be a change in the current state of the first service, for example, the current state of the first service can be but is not limited to a pause state, a continue state, a cancel state or a delete state, etc. Among them, the subscription change can be a change in a subscription attribute, for example, the subscription change includes a subscription association identifier change or an event report information change, wherein the event report information change includes at least one of the following: a change in the event report mode, a change in the maximum number of event reports, a change in the maximum duration of event reports, etc. That is to say, any of the above-mentioned situations can indicate that the first service has changed.

[0138] In an optional implementation, the indication information may be only an indication information value, or may be an event identifier set (i.e., a third event identifier set), wherein when the indication information is the third event identifier set, the third event identifier set may include a state change event identifier and / or a subscription change event identifier, etc. At this time, the indication information may be regarded as having a function of indicating the provision of a special event. For example, the special event may be a state change event, a subscription change event, etc. Optionally, the subscription change event identifier may include a subscription association identifier change event identifier or an event report information change event identifier.

[0139] In an optional implementation, in a scenario where the first message does not include the indication information mentioned above, after the AMF receives the first message, it finds that the first message carries one more address than in the prior art, that is, carries the first address. Then, it can automatically identify that the UDM receives the message notifying the change of the first service through the first address. That is to say, in this scenario, the first address has the following function: implicitly indicating that the message notifying the change of the first service is received through the first address. Of course, in this scenario, when the AMF discovers the first address, it can also use any other form, such as using the currently configured mechanism to identify that the first address can receive the message notifying the change of the first service. This application does not limit this.

[0140] In an optional implementation, the first message may be an event open subscription request (Namf_Event Exposure_Subscribe Request) sent by the UDM to the AMF.

[0141] Step 305: After receiving the first message, the AMF saves the information in the first message and allocates a second subscription correlation identifier (Subscription CorrelationID 2) for the subscription of the first service in the first message.

[0142] In specific implementation, the AMF creates resources for the subscription of the first service according to the information carried in the body, generates a sub-resource identifier subscription id1, and constructs a Uniform Resource Locator (URI) 2 for the created resource. The URI 2 is generated by taking the requested URI as the parent resource and then concatenating the sub-resource identifier. The subscription id 2 here can be used as SubscriptionCorrelation ID 2.

[0143] Step 306: The AMF sends a sixth message to the UDM, where the sixth message includes the Subscription Correlation ID 2.

[0144] In an optional implementation, the sixth message may be an event open subscription response (Namf_EventExposure_Subscribe Response) sent by the AMF to the UDM. In specific implementation, the AMF returns an HTTP Response to the UDM, carrying a "201Created" status code (Status Code) and a "Location" header (header). The Location header carries the URI2.

[0145] Step 307: The UDM returns a seventh message to the NEF, where the seventh message includes the Subscription Correlation ID 1.

[0146] In an optional implementation, the seventh message may be an event open subscription response (Nudm_EventExposure_Subscribe Response) sent by the UDM to the NEF. Specifically, the UDM returns an HTTP Response to the NEF, carrying a "201Created" status code (Status Code) and a "Location" header (header). The Location header carries the URI1.

[0147] Step 308: When the AMF detects an event that can be provided to the NEF, the AMF provides the first service to the NEF.

[0148] Step 309: When the AMF detects that the first service has changed, execute step 310.

[0149] Optionally, in the case where the AMF serving the UE needs to be reselected due to the movement of the UE, the AMF will send the information received in step 304 to other AMFs (i.e., the AMF after the UE reselects). At this time, the other AMF detects that the first service has changed, that is, the other AMF can execute the operation of the AMF in step 309, and then the other AMF continues to execute the operation of the AMF in step 310.

[0150] In an optional implementation, when the first message includes the indication information, the AMF (or the other AMF) may detect according to the indication information; or the AMF (or the other AMF) may detect according to the system configuration. Specifically, the AMF (or the other AMF) detecting that the first service has changed may be any change described in step 304, which will not be repeated here.

[0151] For example, due to changes in network policy or changes in the capabilities of the AMF (or other AMFs), the current status of the first service changes from normal execution to suspension (Suspend), and then from Suspend to resume (Resume); for another example, due to network policy or user's contract, the subscription to the first service is canceled (Cancel) or deleted (Delete).

[0152] Step 310: The AMF (or the other AMF) sends a third message to the first address of the UDM.

[0153] The third message is used to notify that the first service has changed.

[0154] In a specific implementation, the third message may be an event exposure subscription change report request (Namf_Event_Exposure_SubscriptionChangeReport Request) or an event exposure notification request (Namf_Event_Exposure_Notify Request) sent by the AMF (or the other AMF) to the UDM.

[0155] Step 311: The UDM learns that the first service has changed according to the third message.

[0156] In an optional implementation, when the change in the first service refers to the state change described in step 304, the third message also includes the first state information. The first state information may be a pause state, a continue state, a cancel state, a delete state, or the like. Optionally, at this time, the third message also includes an event identifier and / or a user identifier (e.g., a UE identifier) ​​corresponding to the first state information. The event identifier is used when the state of one or part of the events corresponding to the first event identifier set changes, and the event identifier carrying the state change can indicate the event in which the state change occurs; the user identifier is used when the event subscription is for a group of users, and the user identifier carrying the state change is used to indicate the user corresponding to the state change.

[0157] In an optional implementation, when the change in the first service refers to the subscription change described in step 304, the third message also includes the subscription attributes of the first service after the subscription change. Optionally, when the subscription change is a subscription association identifier change, the changed subscription is an updated subscription association identifier; when the subscription change is an event report information change, the changed subscription attributes include at least one of the following: an updated event report mode, an updated maximum number of event reports, and an updated maximum duration of event reports.

[0158] Optionally, the first message also includes a first notification association identifier, wherein the first notification association identifier is assigned by the UDM to the first address; the third message sent by the AMF to the first address of the UDM also includes the first notification association identifier; then the UDM learns that the first service has changed according to the third message, including: the UDM learns that the first service has changed according to the first notification association identifier in the third message.

[0159] In an optional embodiment, when the first message includes the indication information and the indication information is the third event identifier set, the third message also includes at least one event identifier in the third event identifier set, so that the UDM can identify what specific changes have occurred in the first service.

[0160] Step 312: When the change of the first service notified in the third message affects the subscription of the second service, the UDM sends a fifth message to the NEF, where the fifth message is used to notify the second service of the change.

[0161] In a specific implementation, the fifth message may be an event exposure subscription change report request (Nudm_Event_Exposure_SubscriptionChangeReport Request) or an event exposure notification request (Nudm_Event_Exposure_Notify Request) sent by the UDM to the NEF.

[0162] In an optional implementation, when the change in the first service refers to the state change described in step 304, the third message also includes first state information, and the fifth message also includes second state information. The specific limitations of the second state information can refer to the limitations of the first state information, and will not be repeated here.

[0163] In an optional implementation, when the change in the first service refers to the subscription change described in step 304, the third message also includes the subscription attributes of the first service after the subscription change, and the fifth message also includes the subscription attributes of the second service after the subscription change. Specifically, the definition of the subscription attributes of the second service after the subscription change refers to the definition of the changed subscription attributes in the above steps, and will not be repeated here.

[0164] In a specific implementation, the second message further includes a second notification association identifier, where the second notification association identifier is allocated by the NEF to the second address; and the fifth message sent by the UDM to the NEF further includes the second notification association identifier.

[0165] Step 313: The NEF sends an eighth message to the UDM.

[0166] Specifically, the eighth message may be an event exposure subscription change report response (Nudm_Event_Exposure_SubscriptionChangeReport Response) or an event exposure notification response (Nudm_Event_Exposure_Notify Reponse) sent by the NEF to the UDM.

[0167] Step 314: The UDM sends a ninth message to the AMF.

[0168] Specifically, the ninth message may be an event open subscription change report response (Namf_Event_Exposure_SubscriptionChangeReport Response) or an event open notification response (Namf_Event_Exposure_Notify Reponse) sent by the UDM to the AMF.

[0169] In the above example, since the UDM sends its own address to the AMF, when the first service changes, the UDM can receive a notification, so that the service subscription process can be more complete without causing interruption.

[0170] like Figure 4 As shown, the embodiment of the present application also provides an example of a method for subscribing to a service. In this example, the first network function network element is a PCF, the second network function network element is an SMF, and the third network function network element is an NEF. The NEF subscribes to the service from the PCF, and the PCF further subscribes to the service from the NEF to the SMF. Specifically, the process of this example may include:

[0171] Step 401: The NEF obtains first trigger information. Specifically, after the NEF obtains the first trigger information, it triggers the NEF to request policy authorization from the PCF.

[0172] Among them, optionally, the first trigger information may come from other network function network elements, such as AF. In this case, the first trigger information of the AF may be the AF requesting policy authorization from the PCF; the first trigger information may also come from the triggering of the internal trigger mechanism of the NEF.

[0173] Step 402: The NEF sends a tenth message to the PCF, where the tenth message includes application layer information for requesting policy authorization.

[0174] Specifically, the tenth message may be a policy authorization request (Npcf_PolicyAuthorization_Create Request) sent by the NEF to the PCF. In specific implementation, the NEF sends an HTTP POST to the PCF, and the application layer information is carried in the message body of the HTTP POST.

[0175] Step 403: The PCF saves the information in the tenth message and creates an application session context.

[0176] In specific implementation, the PCF creates a resource for the application session according to the application layer information carried in the body of the HTTP POST in step 402, generates a sub-resource identifier appsession id, and constructs a URI 1 for the created resource. The URI 1 is generated by taking the requested URI as the parent resource and then concatenating the sub-resource identifier.

[0177] Optionally, the tenth message may include network policies and user contract agreements, etc.

[0178] Step 404: the PCF sends an eleventh message to the NEF. Specifically, the eleventh message may be a policy authorization response (Npcf_PolicyAuthorization_Create Response) sent by the PCF to the NEF.

[0179] In specific implementation, the PCF may return an HTTP Response to the NEF, carrying a "201 Created" status code and a "Location" header, wherein the Location header carries the URI1 constructed in step 403.

[0180] Step 405: After making a policy decision based on the application layer information in the tenth message, the PCF sends a twelfth message to the SMF, where the twelfth message includes the formulated policy.

[0181] Specifically, the twelfth message may be a policy update notification request (Npcf_Policy_UpdateNotify Request) sent by the PCF to the SMF. In specific implementation, the PCF sends an HTTP POST to the SMF, and the body of the message carries the formulated policy.

[0182] Step 406: After saving the policy, the SMF returns the thirteenth message to the PCF.

[0183] Specifically, the thirteenth message may be a policy update notification response (Npcf_Policy_UpdateNotify Response) sent by the SMF to the PCF. In specific implementation, the SMF sends an HTTPResponse to the PCF, carrying a status code "200OK".

[0184] Step 407: After the NEF obtains the second trigger information and needs to subscribe to the service for the above-mentioned application session, the NEF sends a second message to the PCF, where the second message is used to subscribe to the second service from the PCF.

[0185] The second message includes the address of the NEF, that is, the second address, so that the NEF receives the required events through the second address. In an optional implementation, the second message also includes the above Figure 2 The second event identifier set (Event Id1) and the second notification correlation identifier (NotificationCorrelation ID) mentioned in the embodiment described above include at least one event identifier.

[0186] In an optional implementation, the second message also includes an external identifier of the UE (for example, for one UE), a group identifier of a group of UEs (for example, for a group of UEs), or an indication of any UE (for example, any UE parameter, which is valid for all UEs in the existing network), so that it can be determined for whom the second service is ultimately provided.

[0187] In an optional implementation, the second message also includes event report information, and the event report information includes at least one of the following: event report mode, maximum number of event reports, and maximum duration of event reports. The event report mode can be one-time report, continuous report, periodic report, etc.

[0188] In an optional implementation, the second message may be a policy authorization subscription request (Npcf_PolicyAuthorization_Subscribe Request) sent by the NEF to the PCF. In specific implementation, the NEF sends an HTTP PATCH to the PCF, and the message body of the HTTP PATCH carries the information that may be included in the second message mentioned above, which will not be described in detail here.

[0189] Step 408: The PCF saves the information in the second message, updates the application session context, and allocates a first subscription correlation identifier (Subscription Correlation ID 1) for the subscription of the second service.

[0190] The specific implementation is to add the subscribed service to the resources created in step 403.

[0191] Step 409: The PCF sends a fourteenth message to the NEF, where the fourteenth message includes the Subscription Correlation ID 1.

[0192] Specifically, the fourteenth message may be a policy authorization subscription response (Npcf_PolicyAuthorization_Subscribe Response) sent by the PCF to the NEF.

[0193] In specific implementation, the PCF sends an HTTP Response to the NEF, carrying the status code "200OK" and the SubscriptionCorrelationID1.

[0194] Step 410: The PCF sends a first message to the SMF, and the PCF subscribes to a first service from the SMF through the first message, wherein the first message includes the address of the PCF, that is, the first address.

[0195] Optionally, the PCF determines the first service that needs to be subscribed to the SMF based on the second service. Specifically, the first message also includes a first event identifier set, and the first event identifier set is generated based on the second event identifier set, wherein the first event identifier set is a set of event identifiers corresponding to events in the second event identifier set that need to be provided by the SMF, and the second event identifier set is included in the second message.

[0196] For example, after receiving the second message, the PCF first determines the events in the second event set corresponding to the second identifier set in the second message that need to be provided by the SMF (i.e., the second event set corresponding to the second event identifier set described above in the embodiment of the present application), and then executes step 410. That is to say, the first event identifier set in the first message is specifically determined based on the second event identifier set in the second message, for example, the first event identifier set is part or all of the event identifier set in the second event identifier set.

[0197] Specifically, the first message includes not only the first address but also the second address, which is used by the SMF to provide the first service to the NEF. When the first service changes, the PCF can receive a message notifying the change of the first service through the first address.

[0198] In an optional embodiment, the first message also includes indication information, and the indication information is used to indicate that a message notifying the change of the first service is received through the first address. Specifically, the change of the first service refers to a change in the state of the first service and / or a change in the subscription of the first service. Among them, the state change of the first service can be a change in the current state of the first service, for example, the current state of the first service can be but is not limited to a pause state, a continue state, a cancel state or a delete state, etc. Among them, the subscription change can be a change in a subscription attribute, for example, the subscription change includes a subscription association identifier change or an event report information change, wherein the event report information change includes at least one of the following: a change in the event report mode, a change in the maximum number of event reports, a change in the maximum duration of event reports, etc. That is to say, any of the above-mentioned situations can indicate that the first service has changed.

[0199] In an optional implementation, the indication information may be only an indication information value, or may be an event identifier set (i.e., a third event identifier set), wherein when the indication information is the third event identifier set, the third event identifier set may include a state change event identifier and / or a subscription change event identifier, etc. At this time, the indication information may be regarded as having a function of indicating the provision of a special event. For example, the special event may be a state change event, a subscription change event, etc. Optionally, the subscription change event identifier may include a subscription association identifier change event identifier or an event report information change event identifier.

[0200] In an optional implementation, in a scenario where the first message does not include the indication information mentioned above, after the AMF receives the first message, it finds that the first message carries one more address than in the prior art, that is, carries the first address. Then, it can automatically identify that the UDM receives the message notifying the change of the first service through the first address. That is to say, in this scenario, the first address has the following function: implicitly indicating that the message notifying the change of the first service is received through the first address. Of course, in this scenario, when the AMF discovers the first address, it can also use any other form, such as using the currently configured mechanism to identify that the first address can receive the message notifying the change of the first service. This application does not limit this.

[0201] Step 411: The SMF saves the information in the first message, and allocates a second subscription correlation identifier (Subscription Correlation ID 2) for the subscription of the first service in the first message.

[0202] The specific implementation is that the SMF creates resources for the subscription of the first service according to the information carried by the first message, generates a sub-resource identifier subscription id 2, and constructs a URI 2 for the created resource. The URI 2 is generated by taking the requested URI as the parent resource and then concatenating the sub-resource identifier. The subscription id 2 here can be used as Subscription Correlation ID 2.

[0203] Step 412: The SMF sends a fifteenth message to the PCF, where the fifteenth message includes the Subscription Correlation ID 2.

[0204] In an optional implementation, the fifteenth message may be an event open subscription response (Nsmf_EventExposure_Subscribe Response) sent by the SMF to the PCF. In specific implementation, the SMF returns an HTTP Response to the PCF, carrying a "201Created" status code (Status Code) and a "Location" header (header). The Location header carries the URI2 constructed in step 411.

[0205] Step 413: When the SMF detects an event that can be provided to the NEF, it provides the first service to the NEF.

[0206] Step 414: When the SMF detects that the first service has changed, execute step 415.

[0207] Optionally, when the SMF serving the UE needs to be reselected due to the movement of the UE, the SMF will send the information received in step 410 to other SMFs (i.e., the SMF after the UE reselects). At this time, the other SMF detects that the first service has changed (for example, the other SMF has assigned a new subscription association identifier to the subscription of the first service), that is, the other SMF can execute the operation of the SMF in step 414, and then the other SMF continues to execute the operation of the SMF in step 415.

[0208] For specific implementation, please refer to Figure 3 The description of step 309 in the illustrated embodiment has the same principle and will not be repeated here.

[0209] Step 415: The SMF (or the other SMF) sends a third message to the first address of the PCF. The third message is used to notify that the first service has changed.

[0210] In a specific implementation, the third message may be an event exposure subscription change report request (Nsmf_Event_Exposure_SubscriptionChangeReport Request) or an event exposure notification request (Nsmf_Event_Exposure_Notify Request) sent by the SMF to the PCF.

[0211] Step 416: The PCF learns that the first service has changed according to the third message.

[0212] In an optional implementation, when the change in the first service refers to the state change described in step 410, the third message also includes the first state information. The first state information may be a pause state, a continue state, a cancel state, a delete state, or the like. Optionally, at this time, the third message also includes an event identifier and / or a user identifier (e.g., a UE identifier) ​​corresponding to the first state information. The event identifier is used when the state of one or part of the events corresponding to the first event identifier set changes, and the event identifier carrying the state change can indicate the event in which the state change occurs; the user identifier is used when the event subscription is for a group of users, and the user identifier carrying the state change is used to indicate the user corresponding to the state change.

[0213] In an optional implementation, when the change in the first service refers to the subscription change described in step 410, the third message also includes the subscription attributes of the first service after the subscription change. Optionally, when the subscription change is a subscription association identifier change, the changed subscription attributes are updated subscription association identifiers; when the subscription change is an event report information change, the changed subscription attributes include at least one of the following: an updated event report mode, an updated maximum number of event reports, and an updated maximum duration of event reports.

[0214] Optionally, the first message also includes a first notification association identifier, wherein the first notification association identifier is assigned by the PCF to the first address; the third message sent by the SMF to the first address of the PCF also includes the first notification association identifier; then the PCF learns that the first service has changed according to the third message, which includes: the PCF learns that the first service has changed according to the first notification association identifier in the third message.

[0215] In an optional embodiment, when the first message includes the indication information and the indication information is the third event identifier set, the third message also includes at least one event identifier in the third event identifier set, so that the PCF can identify what specific changes have occurred in the first service.

[0216] Step 417: When the PCF determines that the change of the first service notified in the third message affects the subscription of the second service, the PCF sends a fifth message to the NEF, where the fifth message is used to notify the second service of the change.

[0217] In a specific implementation, the fifth message may be an event exposure subscription change report request (Npcf_Event_Exposure_SubscriptionChangeReport Request) or an event exposure notification request (Npcf_Event_Exposure_Notify Request) sent by the PCF to the NEF.

[0218] In an optional embodiment, when the change in the first service refers to the state change described in step 410, the third message also includes first state information, and the fifth message also includes second state information. The specific limitations of the second state information can refer to the limitations of the first state information, and will not be repeated here.

[0219] In an optional implementation, when the change in the first service refers to the subscription change described in step 410, the third message also includes the subscription attributes of the first service after the subscription change, and the fifth message also includes the subscription attributes of the second service after the subscription change. Specifically, the definition of the subscription attributes of the second service after the subscription change refers to the definition of the changed subscription attributes in the above steps, and will not be repeated here.

[0220] In a specific implementation, the second message further includes a second notification association identifier, where the second notification association identifier is allocated by the NEF to the second address; and the fifth message sent by the PCF to the NEF further includes the second notification association identifier.

[0221] Step 418: The NEF sends a sixteenth message to the PCF.

[0222] Specifically, the sixteenth message may be an event exposure subscription change report response (Npcf_Event_Exposure_SubscriptionChangeReport Response) or an event exposure notification response (Npcf_Event_Exposure_Notify Response) sent by the NEF to the PCF.

[0223] Step 419: The PCF sends the seventeenth message to the SMF.

[0224] Specifically, the seventeenth message may be an event exposure subscription change report response (Nsmf_Event_Exposure_SubscriptionChangeReport Response) or an event exposure notification response (Nsmf_Event_Exposure_Notify Response) sent by the PCF to the SMF.

[0225] In the above example, since the PCF sends its own address to the SMF, when the first service changes, the PCF can receive a notification, thereby making the service subscription process more complete without causing interruption.

[0226] Based on the above embodiments, the embodiments of the present application also provide a method for subscribing to services. In this embodiment, the network elements that subscribe to services can be collectively referred to as network function service consumers (NF Service Consumers), and the network elements that provide services can be collectively referred to as network function service providers (NF Service Producers). Figure 1 The network function elements in the communication system shown. Figure 5As shown, the specific process of the method includes:

[0227] Step 501: The NF Service Consumer obtains trigger information and needs to subscribe services from the NF Service Producer for other functional network elements. Specifically, after the NF Service Consumer obtains the trigger information, it triggers the NF Service Consumer to subscribe services from the NF Service Producer.

[0228] Among them, optionally, the trigger information may come from other network function network elements (i.e., other NFs), for example, it may be the trigger of the NEF in the above embodiment, that is, the trigger of the second message, etc.; the trigger information may also come from the trigger of the internal trigger mechanism of the NF Service Consumer.

[0229] Step 502: The NF Service Consumer sends a first message to the NF Service Producer, and the NF Service Consumer subscribes to a first service from the NF Service Producer through the first message. The first message includes the address of the NF Service Consumer, that is, the first address. When the first service changes, the NF Service Consumer can receive a message notifying the change of the first service through the first address.

[0230] Specifically, in addition to the first address, the first message also includes a notification target address (Notification Target Address), and the device corresponding to the Notification Target Address can receive the required event through the Notification Target Address, that is, the NF Service Producer provides the first service to the device corresponding to the Notification Target Address through the Notification Target Address. Optionally, the Notification Target Address can be but is not limited to the second address involved in the above embodiment.

[0231] In an optional implementation, the first message also includes a first notification association identifier, which is used by the NF Service Consumer to associate an event notification (Event Notification) with a corresponding event subscription (Event Subscription). The first message also includes an external identifier of a UE (for example, for one UE), a group identifier of a group of UEs (for example, for a group of UEs), or an indication of any UE (for example, any UE parameter, which is valid for all UEs in the existing network).

[0232] In an optional implementation, the first message also includes event report information, and the event report information includes at least one of the following: event report mode, maximum number of event reports, and maximum duration of event reports. The event report mode may be one-time report, continuous report, periodic report, etc.

[0233] In an optional embodiment, the first message also includes indication information, and the indication information is used to indicate that a message notifying the change of the first service is received through the first address. Specifically, the change of the first service refers to a change in the state of the first service and / or a change in the subscription of the first service. Among them, the state change of the first service can be a change in the current state of the first service, for example, the current state of the first service can be but is not limited to a pause state, a continue state, a cancel state or a delete state, etc. Among them, the subscription change can be a change in a subscription attribute, for example, the subscription change includes a subscription association identifier change or an event report information change, wherein the event report information change includes at least one of the following: a change in the event report mode, a change in the maximum number of event reports, a change in the maximum duration of event reports, etc. That is to say, any of the above-mentioned situations can indicate that the first service has changed.

[0234] In an optional implementation, the indication information may be only an indication information value, or may be an event identifier set (i.e., a third event identifier set), wherein when the indication information is the third event identifier set, the third event identifier set may include a state change event identifier and / or a subscription change event identifier, etc. At this time, the indication information may be regarded as having a function of indicating the provision of a special event. For example, the special event may be a state change event, a subscription change event, etc. Optionally, the subscription change event identifier may include a subscription association identifier change event identifier or an event report information change event identifier.

[0235] In an optional implementation, in a scenario where the first message does not include the indication information mentioned above, after receiving the first message, the NF Service Producer finds that the first message carries an additional address compared to the prior art, that is, carries the first address, and can automatically identify that the NFService Consumer receives the message notifying the change of the first service through the first address. That is to say, in this scenario, the first address has the following function: implicitly indicating that the message notifying the change of the first service is received through the first address. Of course, in this scenario, when the NF Service Producer discovers the first address, it can also use any other form, such as using the currently configured mechanism to identify that the first address can receive the message notifying the change of the first service, and this application does not limit this.

[0236] In an optional implementation, the first message may be an event exposure subscription request (Nnf_Event Exposure_SubscribeRequest) sent by the NF Service Consumer to the NF Service Producer.

[0237] Step 503: After receiving the first message, the NF Service Producer saves the information in the first message and allocates a second subscription correlation identifier (Subscription Correlation ID 2) for the subscription of the first service in the first message.

[0238] In specific implementation, the NF Service Producer creates resources for the subscription of the first service according to the information carried in the body, generates a sub-resource identifier subscription id1, and constructs a Uniform Resource Locator (URI) 2 for the created resource. The URI 2 is generated by taking the requested URI as the parent resource and then concatenating the sub-resource identifier. The subscription id 2 here can be used as Subscription Correlation ID 2.

[0239] Step 504: The NF Service Producer sends an eighteenth message to the NF Service Consumer, where the eighteenth message includes the Subscription Correlation ID 2.

[0240] In an optional implementation, the eighteenth message may be an event open subscription response (Nnf_EventExposure_SubscribeResponse) sent by the NF Service Producer to the NF Service Consumer. In a specific implementation, the NF Service Producer returns an HTTPResponse to the NF Service Consumer, carrying a "201Created" status code (Status Code) and a "Location" header (header). The Location header carries the URI2.

[0241] Step 505: When the NF Service Producer detects an event that can be provided to the NF Service Consumer, it provides the first service to the NF Service Consumer.

[0242] Step 506: When the NF Service Producer detects that the first service has changed, it executes step 507.

[0243] Optionally, when the NF Service Producer serving the UE needs to be reselected due to the movement of the UE, the NF Service Producer will send the information received in step 502 to other NF network elements (i.e., the NF network elements after the UE reselects). At this time, the other NF network elements detect that the first service has changed, that is, the other NF network elements can perform the operation of the NF Service Producer in step 505, and then the other NF network elements continue to perform the operation of the NF Service Producer in step 507. The other NF network elements have the same function as the NF Service Producer.

[0244] In an optional implementation, when the first message includes the indication information, the NFService Producer (or the other NF network element) may detect according to the indication information; or the NFServiceProducer (or the other NF network element) may detect according to the system configuration. Specifically, the NFServiceProducer (or the other NF network element) detects that the second service has changed, which may be any change described in step 502, and will not be repeated here.

[0245] For example, due to changes in network policy or changes in the capabilities of the NF Service Producer (or other NF network elements), the current status of the first service changes from normal execution to suspension (Suspend), and then from Suspend to resume (Resume); for another example, due to network policy or user contract, the subscription to the first service is canceled (Cancel) or deleted (Delete).

[0246] Step 507: The NF Service Producer (or the other NF network element) sends a third message to the first address of the NF ServiceConsumer, wherein the third message is used to notify that the first service has changed.

[0247] In specific implementation, the third message may be an event exposure subscription change report request (Nnf_Event_Exposure_SubscriptionChangeReport Request) or an event exposure notification request (Nnf_Event_Exposure_Notify Request) sent by the NF Service Producer (or the other NF network element) to the NF Service Consumer.

[0248] Step 508: The NF Service Consumer learns that the first service has changed according to the third message.

[0249] In an optional implementation, when the change in the first service refers to the state change described in step 502, the third message also includes the first state information. The first state information may be a pause state, a continue state, a cancel state, a delete state, or the like. Optionally, at this time, the third message also includes an event identifier and / or a user identifier (e.g., a UE identifier) ​​corresponding to the first state information. The event identifier is used when the state of one or part of the events corresponding to the first event identifier set changes, and the event identifier carrying the state change can indicate the event in which the state change occurs; the user identifier is used when the event subscription is for a group of users, and the user identifier carrying the state change is used to indicate the user corresponding to the state change.

[0250] In an optional implementation, when the change in the first service refers to the subscription change described in step 502, the third message also includes the subscription attributes of the first service after the subscription change. Optionally, when the subscription change is a subscription association identifier change, the changed subscription attributes are updated subscription association identifiers; when the subscription change is an event report information change, the changed subscription attributes include at least one of the following: an updated event report mode, an updated maximum number of event reports, and an updated maximum duration of event reports.

[0251] Optionally, the first message also includes a first notification association identifier, wherein the first notification association identifier is allocated by the NF Service Consumer to the first address; the third message sent by the NF Service Producer to the first address of the NFService Consumer also includes the first notification association identifier. Then the NF Service Consumer learns that the first service has changed according to the third message, which includes: the NFService Consumer learns that the first service has changed according to the first notification association identifier in the third message.

[0252] In an optional embodiment, when the first message includes the indication information and the indication information is the third event identifier set, the third message also includes at least one event identifier in the third event identifier set, so that the NF Service Consumer can identify what specific changes have occurred in the first service.

[0253] Step 509: The NF Service Consumer sends the nineteenth message to the NF Service Producer.

[0254] Specifically, the nineteenth message may be an event exposure subscription change report response (Nnf_Event_Exposure_SubscriptionChangeReport Response) or an event exposure notification response (Nnf_Event_Exposure_Notify Reponse) sent by the NF Service Consumer to the NF ServiceProducer.

[0255] In the subscription service method provided in the embodiment of the present application, since the NF Service Consumer sends its own address to the NF Service Producer, when the first service changes, the NF ServiceConsumer can receive a notification, thereby making the service subscription process more complete and not causing interruptions.

[0256] Based on the same inventive concept as the method embodiment, the embodiment of the present application also provides a device, which is applied to the first network function network element. The device 600 can be a processor, a chip, a chip system, or a functional module in the first network function network element. Figure 6 As shown, the device 600 may include a sending unit 601, a receiving unit 602 and a processing unit 603. The sending unit 601 is used for the device 600 to send information, the receiving unit 602 is used for the device 600 to receive information, and the processing unit 603 is used to control and manage the actions of the device 600. The processing unit 603 may also be used to indicate the processing process involving the first network function network element (such as UDM, PCF) in any of the above embodiments and / or other processes of the technical solution described in this application. Specifically, the processing unit 603 may control the sending unit 601 to execute step 201, and control the receiving unit 602 to execute step 202, and execute step 203. For details, please refer to Figure 2 The embodiments shown will not be described in detail herein.

[0257] In hardware implementation, the processing unit 603 may be a processor or a processing circuit, etc.; the sending unit 601 may be a transmitter or a sending circuit, etc.; the receiving unit 602 may be a receiver or a receiving circuit, etc.; the sending unit 601 and the receiving unit 602 may constitute a transceiver.

[0258] Based on the same inventive concept as the method embodiment, the embodiment of the present application also provides a device, which is applied to the second network function network element. The device 700 can be a processor, a chip, a chip system, or a functional module in the second network function network element. Figure 7As shown, the device 700 may include a receiving unit 701, a sending unit 702 and a processing unit 703. The sending unit 702 is used for the device 700 to send information, the receiving unit 701 is used for the device 700 to receive information, and the processing unit 703 is used to control and manage the actions of the device 700. The processing unit 703 can also be used to indicate the processing process involving the second network function network element (such as AMF, SMF) in any of the above embodiments and / or other processes of the technical solution described in this application. Specifically, the processing unit 703 can control the steps performed by the sending unit 702 and the receiving unit 701. For details, please refer to the above embodiments, and the repeated parts will not be repeated here.

[0259] In hardware implementation, the processing unit 703 may be a processor or a processing circuit, etc.; the sending unit 702 may be a transmitter or a sending circuit, etc.; the receiving unit 701 may be a receiver or a receiving circuit, etc.; the sending unit 702 and the receiving unit 701 may constitute a transceiver.

[0260] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. Each functional unit in the embodiments of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0261] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0262] Based on the above embodiments, the present application also provides another first network function network element, which is used to implement the above subscription service method. Figure 8As shown, the first network function network element 800 may include a transceiver 801 and a processor 802. Optionally, the first network function network element 800 may also include a memory 803. The memory 803 may be set inside the first network function network element 800, or may be set outside the first network function network element 800. The processor 802 controls the transceiver 801 to receive and send data, and is used to implement Figure 2 to Figure 5 The method executed by the first network function network element (such as UDM, PCF).

[0263] Specifically, the processor 802 may be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and a NP. The processor 802 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0264] The transceiver 801, the processor 802 and the memory 803 are interconnected. Optionally, the transceiver 801, the processor 802 and the memory 803 are interconnected via a bus 804; the bus 804 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0265] In an optional implementation, the memory 803 is used to store programs, etc. Specifically, the program may include a program code, which includes a computer operation instruction. The memory 803 may include a RAM, and may also include a non-volatile memory, such as at least one disk storage. The processor 802 executes the application stored in the memory 803 to implement the above functions, thereby implementing the subscription service method provided in the embodiment of the present application.

[0266] Based on the above embodiments, the present application also provides another second network function network element, which is used to implement the above subscription service method. Fig. 9 As shown, the second network function network element 900 may include a transceiver 901 and a processor 902. Optionally, the second network function network element 900 may also include a memory 903. The memory 903 may be arranged inside the second network function network element 900, or may be arranged outside the second network function network element 900. The processor 902 controls the transceiver 901 to receive and send data, and is used to implement Figure 2 to Figure 5 The method executed by the second network function network element (such as AMF, SMF).

[0267] Specifically, the processor 902 may be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and a NP. The processor 902 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0268] The transceiver 901, the processor 902 and the memory 903 are interconnected. Optionally, the transceiver 901, the processor 902 and the memory 903 are interconnected via a bus 904; the bus 904 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 9 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0269] In an optional implementation, the memory 903 is used to store programs, etc. Specifically, the program may include a program code, and the program code includes computer operation instructions. The memory 903 may include RAM, and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. The processor 902 executes the application stored in the memory 903 to implement the above functions, thereby implementing the subscription service method provided in the embodiment of the present application.

[0270] Based on the above embodiments, the embodiments of the present application further provide a computer storage medium, in which a software program is stored, and when the software program is read and executed by one or more processors, the method provided in any one or more of the above embodiments can be implemented. The computer storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and other media that can store program codes.

[0271] Based on the above embodiments, the embodiments of the present application further provide a chip, which includes a processor for implementing the functions involved in any one or more of the above embodiments, such as obtaining or processing the information or messages involved in the above methods. Optionally, the chip also includes a memory, which is used for the necessary program instructions and data executed by the processor. The chip can be composed of a chip, or it can include a chip and other discrete devices.

[0272] In summary, a method and device for subscribing to a service are provided through an embodiment of the present application, wherein a first network function network element sends a first message to a second network function network element, for subscribing a first service to the second network function network element for a third network function network element, wherein the first message includes a first address, and the first address is the address of the first network function network element; the first network function network element receives the third message through the first address, and learns that the first service has changed according to the third message. In this method, since the first network function network element sends its own address to the second network function network element, when the first service changes, the first network function network element can receive a notification of the service change, thus improving the mechanism for reporting service changes, thereby making the service subscription process more complete and not causing interruptions.

[0273] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0274] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0275] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0276] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0277] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for subscription service, characterized in that: include: The first network function network element sends a first message to the second network function network element, which is used to subscribe a first service for a third network function network element to the second network function network element, wherein the first message includes a first address and a second address, the first address is the address of the first network function network element, and the second address is the address of the third network function network element; The second network function network element sends a third message to the first address, used to notify the first network function network element that the first service has changed; The first network function network element receives the third message; The first network function network element learns that the first service has changed according to the third message.

2. The method of claim 1, further comprising: The third network function network element sends a second message to the first network function unit, where the second message is used to subscribe to a second service, and the second message includes the second address; The first network function network element receives the second message and determines the first service that needs to be subscribed to the second network function network element based on the second service.

3. The method according to claim 2, characterized in that After the first network function network element learns, according to the third message, that the first service has changed, the method further includes: The first network function network element sends a fifth message to the second address of the third network function network element, where the fifth message is used to notify that the second service has changed.

4. The method according to any one of claims 1 to 2, characterized in that: The method also includes: the first network function network element allocating a first notification association identifier, wherein the first message sent by the first network function network element to the second network function network element also includes the first notification association identifier.

5. The method according to claim 4, characterized in that The third message sent by the second network function network element to the first address includes the first notification association identifier.

6. The method according to claim 5, characterized in that The first network function network element being informed, according to the third message, that the first service has changed includes: the first network function network element being informed, according to the first notification association identifier in the third message, that the first service has changed.

7. The method according to claim 3, characterized in that The second message also includes a second notification association identifier, where the second notification association identifier is allocated by the third network function network element; The first network function network element sends the fifth message to the second address of the third network function network element, including: the first network function network element sends the fifth message including the second notification association identifier to the second address of the third network function network element.

8. The method according to any one of claims 1 to 3 or 7, characterized in that: The method comprises: The second network function network element provides the first service to the third network function network element according to the second address.

9. A method for subscription service, characterized in that: include: The first network function network element sends a first message to the second network function network element, where the first message is used for the first network function network element to subscribe a first service to the second network function network element for a third network function network element, and the first message includes a first address and a second address, where the first address is the address of the first network function network element, and the second address is the address of the third network function network element; The second network function network element receives the first message; When the network element serving the UE is switched from the second network function network element to the fourth network function network element, The second network function network element sends context information to the fourth network function network element, wherein the context information is generated according to subscription information of the first service, and the context information includes the first address; the first message also includes a first notification association identifier assigned by the first network function network element, and the method includes: Then the second network function network element sends the first notification association identifier to the fourth network function network element.

10. The method according to claim 9, characterized in that The second network function network element requests the first service from the fourth network function network element for the third network function network element, sends the first address to the fourth network function network element, and sends the first notification association identifier to the fourth network function network element, including: The second network function network element sends context information to the fourth network function network element, wherein the context information is generated according to subscription information of the first service, and the context information includes the first address and the first notification association identifier.

11. The method according to any one of claims 9 to 10, characterized in that: The first message also includes a second address, where the second address is an address of the third network function network element, and the method includes: The second network function network element provides the first service to the third network function network element according to the second address.

12. The method according to any one of claims 9 to 10, characterized in that: The method also includes: the fourth network function network element sending a third message to the first address to notify the first network function network element that the first service has changed.

13. The method according to claim 9, characterized in that The method comprises: The fourth network function allocates a new subscription association identifier for the subscription of the first service.

14. A method for subscription service, characterized in that: include: The first network function network element sends a first message to the second network function network element, where the first message is used for the first network function network element to subscribe a first service to the second network function network element for a third network function network element, and the first message includes a first address and a second address, where the first address is the address of the first network function network element, and the second address is the address of the third network function network element; The second network function network element receives the first message; When the network element serving the UE is switched from the second network function network element to the fourth network function network element, the second network function network element sends the subscription information of the first service to the fourth network function network element, wherein the subscription information of the first service includes the first address; The method comprises: The fourth network function network element receives subscription information of the first service; The fourth network function network element sends a third message to the first address to notify the first network function network element that the first service has changed.

15. The method according to claim 14, characterized in that The method comprises: The fourth network function allocates a new subscription association identifier for the subscription of the first service.

Images