Service joining method, program, chip, information transmission device, network device, network function network element, and communication system

Abstract

A service subscription method and apparatus are provided that are used to propose a mechanism for reporting service changes. In one embodiment, a first network function network element sends a first message to a second network function network element to subscribe to a first service for a third network function network element from the second network function network element. The first message includes a first address, which is the address of the first network function network element. The first network function network element receives a third message using the first address and determines, based on the third message, that the first service has changed. The first network function network element sends the address of the first network function network element to the second network function network element.

Description

[Technical field]

[0001] The present application relates to the field of communication technologies, and in particular to a service subscription method and apparatus. [Background technology]

[0002] The fifth generation (5G) system supports data connectivity and service enablement deployment. In the 5G system, network function network elements in the control plane may interact with each other on a service-by-service basis. A common service among the multiple services provided by the network function network elements is an event exposure service. The main implementation process of the service is as follows: When subscribing to a service requested by a service provider, the service subscriber provides an event receiving address to the service provider, and after determining that the service subscriber can provide the requested event to which the service provider subscribes, the service provider notifies the requested event to the event receiving address.

[0003] In practice, the service status or service subscription (i.e., subscription attributes) is changed after a change in user subscription, network policy, network capability, etc. For example, due to a change in user subscription, an event that was originally authorized to be monitored can no longer be monitored, and monitoring must be stopped, or due to a change in network capability, an event that was originally authorized to be monitored can no longer be monitored, and monitoring must be suspended. However, in the existing service subscription procedure, communication between devices when a service status or service subscription is changed is not improved, and a corresponding mechanism is not configured to enable a service provider to report a service change to a service subscriber. Therefore, the service subscription procedure is incomplete, and the service subscription procedure may be interrupted. Summary of the Invention

[0004] This application provides a service subscription method and apparatus to propose a mechanism for reporting service changes.

[0005] According to a first aspect, the present application provides a service subscription method, the method including the steps of: sending a first message by a first network function network element to a second network function network element to subscribe to a first service for a third network function network element from the second network function network element, the first message including a first address; receiving a third message by the first network function network element using the first address; and finding out that the first service has been changed based on the third message, the first address being an address of the first network function network element.

[0006] In this method, the first network function network element transmits the address of the first network function network element to the second network function network element. Thus, when the first service is changed, the first network function network element may receive a notification that the service has been changed. In this way, the mechanism for reporting the service change is improved so that the service subscription procedure can be relatively complete and no interruption occurs.

[0007] In a possible design, before sending the first message to the second network function network element, the first network function network element receives a second message from a third network function network element, the second message being used to subscribe to the second service, the second message including a second address, the second address being an address of the third network function network element. The method further includes determining, by the first network function network element, a first service to be subscribed to from the second network function network element based on the second service, the first message further including a second address used by the second network function network element to provide the first service to the third network function network element.

[0008] In this method, the first network function network element may determine the first service based on the second message so as to be able to subscribe to the first service from the second network function network element.

[0009] In a possible design, after knowing that the first service has been changed based on the third message, the first network function network element sends a fifth message to a second address of the third network function network element, where the fifth message is used to notify that the second service has been changed. In this way, the third network function network element may know that the service to which the third network function network element subscribes has been changed.

[0010] In a possible design, the first message further includes instruction information, which is used to instruct the first address to receive a message notifying that the first service has been changed. In this way, after detecting that the first service has been changed, the other network function network element sends a message to the first address indicating that the first service has been changed.

[0011] In a possible design, after sending the first message by the first network function network element to the second network function network element, the method further includes receiving, by the first network function network element, a second subscription correlation identifier from the second network function network element, the second subscription correlation identifier being an identifier assigned by the second network function network element for the subscription to the first service. The third message further includes the second subscription correlation identifier. Knowing, by the first network function network element, that the first service has changed based on the third message includes knowing, by the first network function network element, that the first service has changed based on the second subscription correlation identifier in the third message.

[0012] In this way, the first network function network element may know exactly that the first service has been changed.

[0013] In a 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 assigns a first subscription correlation identifier for the subscription to the second service and sends the first subscription correlation identifier to the third network function network element. Sending a fifth message by the first network function network element to the second address of the third network function network element includes sending, by the first network function network element, the fifth message including the first subscription correlation identifier to the second address of the third network function network element.

[0014] In a possible design, prior to sending the first message by the first network function network element to the second network function network element, the method further includes assigning, by the first network function network element, a first notification correlation identifier, and sending the first message by the first network function network element to the second network function network element includes sending, by the first network function network element, the first message including the first notification correlation identifier to the second network function network element. The third message received by the first network function network element using the first address further includes the first notification correlation identifier. Knowing, by the first network function network element, that the first service has changed based on the third message includes knowing, by the first network function network element, that the first service has changed based on the first notification correlation identifier in the third message.

[0015] In this manner, the first network function network element may accurately identify that the first service has changed.

[0016] In a possible design, the second message further includes a second notification correlation identifier, the second notification correlation identifier being assigned by the third network function network element. Sending the fifth message by the first network function network element to a second address of the third network function network element includes sending the fifth message including the second notification correlation identifier by the first network function network element to the second address of the third network function network element.

[0017] In a possible design, the first service being changed means that a status of the first service has changed and / or a subscription to the first service has changed. In a possible design, the change in subscription includes a change in a subscription correlation identifier or a change in event reporting information, and the change in the event reporting information includes at least one of a change in an event reporting mode, a change in a maximum number of event reports, and a change in a maximum duration of an event report.

[0018] In this way, the specific cases in which the first service is changed can be determined precisely.

[0019] In a possible design, if the first service is changed meaning that the status is changed, the third message further includes the first status information, which is a paused state, a resumed state, a discontinued state, or a deleted state. In this way, the first network function network element may know the current status of the subscribed service.

[0020] In a possible design, the third message further includes an event identifier and / or a user identity corresponding to the first status information. In this way, the first network function network element may know the status change event or the user corresponding to the status change event.

[0021] In a possible design, if the first service is changed meaning that the subscription is changed, the third message further includes subscription attributes of the changed subscription of the first service. In this way, the first network function network element and the third network function network element may know the current subscription attributes of the subscribed service.

[0022] In a possible design, if the change in subscription is a change in the subscription correlation identifier, the subscription attribute of the changed subscription of the first service is the updated subscription correlation identifier. In this way, the first network function network element and the third network function network element may know the specific subscription attribute of the changed subscription exactly.

[0023] In a possible design, if the change in subscription is a change in event reporting information, the subscription attributes of the changed subscription of the first service include at least one of an updated event reporting mode, an updated maximum amount of event reporting, and an updated maximum duration of event reporting. In this way, the first network function network element may know the specific subscription attributes of the changed subscription precisely.

[0024] In a possible design, the step of receiving the third message by the first network function network element using the first address may be performed in two ways: in a first way, the first network function network element receives the third message from the second network function network element using the first address; in a second way, the first network function network element receives the third message from the fourth network function network element using the first address; and the second network function network element requests the first service for the third network function network element from the fourth network function network element.

[0025] In this method, the first network function network element may successfully receive a message using the first address notifying that the first service has changed.

[0026] In a possible design, the instruction information is a third event identifier set, and the third event identifier set includes a status change event identifier and / or a subscription change event identifier. In this way, another network function network element may be triggered by a specific event to detect whether the first service has been changed.

[0027] In a possible design, the subscription change event identifier includes a subscription correlation identifier change event identifier or an event reporting information change event identifier. In this way, the event that detects that the first service has been changed can be accurately determined.

[0028] In a possible design, the third message further includes at least one event identifier in the third event identifier set. In this manner, the first network function network element may identify a particular change in the first service.

[0029] According to a second aspect, an embodiment of the present application provides a service subscription method, the method including: receiving, by a second network function network element, a first message from a first network function network element, the first message being used by the first network function network element to subscribe to a first service for a third network function network element from the second network function network element, the first message including a first address, the first address being an address of the first network function network element; and sending, by the second network function network element, a third message to the first address of the first network function network element to notify the first network function network element that the first service has changed.

[0030] In this method, the first network function network element transmits the address of the first network function network element to the second network function network element. Thus, when the first service is changed, the first network function network element may receive a notification that the service has been changed. In this way, the mechanism for reporting the service change is improved so that the service subscription procedure can be relatively complete and no interruption occurs.

[0031] In a possible design, the first message further includes a second address, the second address being an address of a third network function network element, and the second network function network element provides the first service to the third network function network element based on the second address. In this way, if the first service is normal, the second network function network element may normally notify the third network function network element of the requested event.

[0032] In a possible design, the first message further includes instruction information, which is used to instruct the second network function network element to use the first address to receive a message notifying that the first service has been changed. In this way, after detecting that the first service has been changed, the second network function network element sends to the first address a message indicating that the first service has been changed.

[0033] In a possible design, after receiving the first message from the first network function network element, the second network function network element assigns a second subscription correlation identifier for the subscription of the first service. Sending a third message by the second network function network element to the first address of the first network function network element includes adding, by the second network function network element, the second subscription correlation identifier to the third message and sending the third message to the first address of the first network function network element. In this way, the first network function network element may know that the first service has changed using the second subscription correlation identifier in the third message.

[0034] In a possible design, the first message further includes a first notification correlation identifier, and sending, by the second network function network element, the third message to the first address of the first network function network element includes sending, by the second network function network element, the third message including the first notification correlation identifier to the first address of the first network function network element. In this way, the first network function network element may know that the first service has changed using the first notification correlation identifier in the third message.

[0035] In a possible design, the first service being changed means that a status of the first service has changed and / or a subscription to the first service has changed. In a possible design, the change in subscription includes a change in a subscription correlation identifier or a change in event reporting information, and the change in the event reporting information includes at least one of a change in an event reporting mode, a change in a maximum number of event reports, and a change in a maximum duration of an event report.

[0036] In this way, the specific cases in which the first service is changed can be determined precisely.

[0037] In a possible design, if the first service is changed meaning that the status is changed, the third message further includes the first status information, which is a paused state, a resumed state, a discontinued state, or a deleted state. In this way, the first network function network element may know the current status of the subscribed service.

[0038] In a possible design, the third message further includes an event identifier and / or a user identity corresponding to the first status information. In this way, the first network function network element may know the status change event or the user corresponding to the status change event.

[0039] In a possible design, if the first service is changed meaning that the subscription is changed, the third message further includes subscription attributes of the changed subscription of the first service. In this way, the first network function network element may know the current subscription attributes of the subscribed service.

[0040] In a possible design, if the change in the subscription is a change in the subscription correlation identifier, the subscription attribute of the changed subscription of the first service is the updated subscription correlation identifier. In this way, the first network function network element may know exactly the specific subscription attribute of the changed subscription.

[0041] In a possible design, if the change in subscription is a change in event reporting information, the subscription attributes of the changed subscription of the first service include at least one of an updated event reporting mode, an updated maximum amount of event reporting, and an updated maximum duration of event reporting. In this way, the first network function network element may know the specific subscription attributes of the changed subscription precisely.

[0042] In a possible design, the instruction information is a third event identifier set, and the third event identifier set includes a status change event identifier and / or a subscription change event identifier. In this way, the second network function network element may be triggered by a specific event to detect whether the first service has been changed.

[0043] In a possible design, the subscription change event identifier includes a subscription correlation identifier change event identifier or an event reporting information change event identifier. In this way, the second network function network element can accurately determine the event that detects that the first service has been changed.

[0044] In a possible design, the third message further includes at least one event identifier in the third event identifier set. In this manner, the first network function network element may identify a particular change in the first service.

[0045] In a possible design, the second network function network element requests the first service from the fourth network function network element and sends the first address to the fourth network function network element. In this way, after the UE reselects the fourth network function network element because the UE has moved, the fourth network function network element may send a message to the first address to notify that the first service has changed.

[0046] According to a third aspect, the present application further provides a first network function network element, the first network function network element having a function for implementing the behavior of the first network function network element in the embodiment of the aforementioned method. The function may be implemented by hardware, or may be implemented by hardware by executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions.

[0047] In a possible design, the structure of the first network function network element includes a sending unit, a receiving unit and a processing unit, and these units can perform corresponding functions in the above method example. For details, please refer to the detailed description of the method example. The details will not be described again.

[0048] In a possible design, the structure of the first network function network element includes a transceiver and a processor, and optionally further includes a memory. The transceiver is configured to receive and transmit data, and to communicate and interact with other devices in the communication system. The processor is configured to support the first network function network element in performing corresponding functions in the aforementioned method. The memory is coupled to the processor, and the memory stores program instructions and data required for the first network function network element.

[0049] According to a fourth aspect, the present application further provides a second network function network element, the second network function network element having a function for implementing the behavior of the second network function network element in the above-mentioned method example. The function may be implemented by hardware, or may be implemented by hardware by executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0050] In a possible design, the structure of the second network function network element includes a receiving unit, a sending unit and a processing unit, and these units can perform corresponding functions in the above method example. For details, please refer to the detailed description of the method example. Here, the details are not described again.

[0051] In a possible design, the structure of the second network function network element includes a transceiver and a processor, and optionally further includes a memory. The transceiver is configured to receive and transmit data, and to communicate and interact with another device in the communication system. The processor is configured to support the second network function network element in performing corresponding functions in the aforementioned method. The memory is coupled to the processor, and the memory stores program instructions and data required for the second network function network element.

[0052] According to a fifth aspect, the present application further provides a system, the system including a first network function network element, the first network function network element may be configured to perform the steps performed by the first network function network element in the first aspect and any method of the first aspect. In a possible design, the system may further include a second network function network element, the second network function network element may be configured to perform the steps performed by the second network function network element in the first aspect and any method of the first aspect. In a possible design, the system may further include another device, such as a third network function network element, that interacts with the first network function network element and / or the second network function network element in the solution provided in this embodiment of the present application.

[0053] According to a sixth aspect, the present application further provides a system, the system including a second network function network element, the second network function network element may be configured to perform the steps performed by the second network function network element in the second aspect and any method of the second aspect. In a possible design, the system may further include a first network function network element, the first network function network element may be configured to perform the steps performed by the first network function network element in the second aspect and any method of the second aspect. In a possible design, the system may further include another device, such as a third network function network element, that interacts with the first network function network element and / or the second network function network element in the solution provided in this embodiment of the present application.

[0054] According to a seventh aspect, the present application further provides a computer storage medium storing computer executable instructions which, when invoked by a computer, are used to cause the computer to perform any one of the methods described above.

[0055] According to an eighth aspect, the present application further provides a computer program product comprising instructions, when the computer program product is run on a computer, causing the computer to perform any one of the methods described above.

[0056] According to a ninth aspect, the present application further provides a chip, connected to the memory and configured to read and execute program instructions stored in the memory to perform any one of the aforementioned methods. [Brief description of the drawings]

[0057] [Figure 1] 1 is a schematic architecture diagram of a communication system according to the present application;

[0058] [Diagram 2] 2 is a flowchart of a service subscription method according to the present application.

[0059] [Diagram 3] 2 is an exemplary flowchart of a service subscription method according to the present application.

[0060] [Figure 4A] 4 is an exemplary flowchart of another service subscription method according to the present application. [Figure 4B] 4 is an exemplary flowchart of another service subscription method according to the present application.

[0061] [Diagram 5] 4 is a flowchart of another service subscription method according to the present application.

[0062] [Figure 6] FIG. 1 is a schematic structural diagram of an apparatus according to the present application.

[0063] [Figure 7] FIG. 2 is a schematic structural diagram of another device according to the present application.

[0064] [Figure 8] FIG. 2 is a structural diagram of a first network function network element according to the present application;

[0065] [Figure 9] FIG. 2 is a structural diagram of a second network function network element according to the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0066] The present application will now be described in more detail with reference to the accompanying drawings.

[0067] The embodiments of the present application provide a service subscription method and apparatus to propose a mechanism for reporting service changes. The method and apparatus in the present application are based on the same inventive concept. Because the principles of solving the problems of the method and apparatus are similar, the implementation aspects of the apparatus and method may be cross-referenced, and the overlapping parts will not be described.

[0068] Below, some terms used in this application will be explained to aid in better understanding by those skilled in the art.

[0069] (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 in the control plane of the core network, and may support the event exposure service and perform communication and interaction based on the event exposure service. Specifically, in an embodiment related to the present application, the first network function network element subscribes to a service for the first network function network element from the second network function network element. The first network function network element may be, but is not limited to, a data management network element, a policy control function network element, etc. For example, the data management network element may be a unified data management (UDM) and the policy control function network element may be a policy control function (PCF). The second network function network element may be, but is 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 an AMF (core access and mobility management function), and the session management function network element may be an SMF (session management function). The third network function network element may be, but is not limited to, a network exposure function network element, for example, a NEF (Network Exposure Function). For example, if the first network function network element is a UDM, the second network function network element may be an AMF accordingly. In another example, if the first network function network element is an SMF, the second network function network element may be an SMF accordingly. In these three network function network element examples, the names of the network elements are merely examples. In future communications, the names of the network elements may be changed. This is not limited in this application.

[0070] (2) In the description of this application, the terms "first" and "second," etc. are used merely for purposes of distinction and explanation and should not be understood as denoting or implying relative importance or as denoting or implying an order.

[0071] (3) The term "and / or" describes a relational relationship for describing related objects and indicates that three relations may exist. For example, A and / or B may represent three cases: only A exists, both A and B exist, and only B exists. The symbol " / " generally indicates an "or" relationship between related objects.

[0072] In order to more clearly describe the technical solutions in the embodiments of the present application, the following describes in detail the service data obtaining method and device provided in the embodiments of the present application with reference to the accompanying drawings.

[0073] A possible communication system architecture to which the service subscription method provided in the embodiment of the present application can be applied may include a network exposure 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. Figure 1 shows a possible example of the communication system architecture. The communication system architecture specifically includes a NEF network element, a PCF network element, a UDM network element, an AF network element, an AMF network element, an SMF network element, a UE, an access network (AN) device, a UPF network element, and a data network (DN). The AMF network element may be connected to the terminal device through an N1 interface, the AMF may be connected to the AN device through an N2 interface, the AN device may be connected to the UPF through an N3 interface, the SMF may be connected to the UPF through an N4 interface, and the UPF may be connected to the DN through an N6 interface. The names of the interfaces are merely examples for explanation. This is not particularly limited in this embodiment of the present application. It should be understood that this embodiment of the present application is not limited to the communication system shown in Figure 1. The names of the network elements shown in Figure 1 are used in this specification only as examples for explanation, and are not used to limit the network elements included in the communication system architecture to which the method in the present application can be applied. In the following, the functions of each network element or device in the communication system are described in detail.

[0074] A terminal device may be referred to as a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc., and is a device that provides voice and / or data connectivity to a user. For example, the terminal device may include a handheld device with a wireless connection function, an in-vehicle device, etc. Currently, the terminal device may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, 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 a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. In FIG. 1, the terminal device is illustrated using a UE as an example, but the terminal device is not limited thereto.

[0075] A radio access network is an access network (AN) shown in FIG. 1 and may provide radio access services to terminal devices. An access network device is a device in a communication system that enables a terminal device to access a radio network. An access network device is a node in a radio access network and may be referred to as a base station or a radio access network (RAN) node (or device). Currently, for example, an access network device is a gNB, a transmission reception point (TRP), an evolved NodeB (eNB), a radio network controller (RNC), a NodeB (NodeB, NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved NodeB or Home NodeB, HNB), a baseband unit (BBU) or a wireless fidelity (Wi-Fi) access point (AP).

[0076] A data network, such as the data network (DN) shown in Figure 1, 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, which provides services to the terminal device by transmitting data with the terminal device.

[0077] The core network is configured to enable the terminal device to access the DN that can implement the services of the terminal device. The following describes the functions of the network elements in the core network.

[0078] The core network access and mobility management function network element may be configured to manage the access control and mobility of the terminal device. In practical application, the core network access and mobility management function network element includes a mobility management function in a mobility management entity (MME) in a network framework of long term evolution (LTE), and includes an access management function. Specifically, the core network access and mobility management function network element may be responsible for the registration, mobility management, tracking area update procedure, reachability detection, selection of session management function network element, mobility status transition management, etc. of the terminal device. For example, in 5G, the core network access and mobility management function network element may be, for example, an AMF (Access and Mobility Management Function) network element as shown in FIG. 1. In future communications, for example, in 6G, the core network access and mobility management function network element may still be an AMF network element, or may have another name. This is not limited in the present application. If the core network access and mobility management function network element is an AMF network element, the AMF may provide Namf services.

[0079] The session management function network element may be configured to be responsible for session management (including session establishment, modification, and release) of terminal devices, selection and reselection of user plane function network elements, internet protocol (IP) address allocation of terminal devices, quality of service (QoS) control, etc. For example, in 5G, the session management function network element may be, for example, an SMF (Session Management Function) network element as shown in FIG. 1. In future communications, for example, in 6G, the session management function network element may still be an SMF network element or may have another name. This is not limited in the present application. If the session management function network element is an SMF network element, the SMF may provide Nsmf services.

[0080] The policy control function network element may be configured to be responsible for policy control decision making and provide functions such as service-based data flow and application detection, gating, QoS, and flow-based charging control. For example, in 5G, the policy control function network element may be, for example, a PCF (Policy Control Function) network element as shown in FIG. 1. In future communications, for example, in 6G, the policy control function network element may still be a PCF network element or may have another name. This is not limited in this application. If the policy control function network element is a PCF network element, the PCF network element may provide an Npcf service.

[0081] The main function of the application function network element is to interact with the 3rd generation partnership project (3GPP) core network to provide services, such as affecting service flow routing, access network capability exposure, policy control, etc. For example, in 5G, the application function network element may be, for example, an AF (Application Function) network element as shown in FIG. 1. In future communications, for example, in 6G, the application function network element may still be an AF network element or may have a different name. This is not limited in this application. If the application function network element is an AF network element, the AF network element may provide Naf services.

[0082] The data management network element may be configured to manage subscription data of a terminal device, registration information related to the terminal device, etc. For example, in 5G, the data management network element may be, for example, a unified data management (UDM) network element as shown in FIG. 1. In future communications, for example, in 6G, the data management network element may still be a UDM network element or may have another name. This is not limited in the present application. If the data management network element is a UDM network element, the UDM network element may provide a Nudm service.

[0083] The network exposure function network element may be configured to enable 3GPP to securely provide network service capabilities to a third party AF (e.g., a Services Capability Server (SCS) or an Application Server (AS)). For example, in 5G, the network exposure function network element may be, for example, a NEF (Network Exposure Function) as shown in FIG. 1. In future communications, for example, in 6G, the network exposure function network element may still be a NEF network element or may have another name. This is not limited in this application. If the network exposure function network element is a NEF, the NEF may provide Nnef services to another network function network element.

[0084] Each of the aforementioned network elements in the core network may be referred to as a functional entity and may be a network element implemented in dedicated hardware or may be a software instance running on dedicated hardware or an instance of a virtual function on a suitable platform, for example the virtualization platform may be a cloud platform.

[0085] It should be noted that the communication system architecture shown in Figure 1 is not limited to include only the network elements shown in the figure, and may further include other devices not shown in the figure, and the details will not be described one by one here in this application.

[0086] It should be noted that the distribution of network elements in the core network is not limited in this embodiment of the present application. The distribution shown in FIG. 1 is merely an example and is not intended to limit the present application.

[0087] For ease of explanation, hereafter, the network element shown in FIG. 1 is used as an example for explanation in this application, 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 merely used as examples, and may be referred to by other names in future communications, or the network elements in this application may be replaced by other entities or devices having the same functions in future communications. This is not limited in this application. A unified description is provided in this specification and will not be repeated in the following content.

[0088] It should be noted that the communication system shown in Fig. 1 does not constitute a limitation on the communication system to which the embodiments of the present application can be applied. The communication system architecture shown in Fig. 1 is a 5G system architecture. Optionally, the method in the embodiments of the present application can be further applied to various future communication systems, such as 6G or another communication network.

[0089] An embodiment of the present application provides a service subscription method applicable to the communication system shown in Figure 1. Referring to Figure 2, the specific steps of the method include the following steps:

[0090] Step 201: A first network function network element sends a first message to a second network function network element to subscribe to a first service for a third network function network element from the second network function network element. The first message includes a first address, and the first address is an address of the first network function network element. The first address (the address may be referred to as a Notification Endpoint) may be at least one or a combination of an internet protocol (IP) address of the first network function network element, a port number of the first network function network element, a uniform resource locator (URL), and the like.

[0091] The first network function network element sends a first message to the second network function network element to subscribe to a first service provided by the second network function network element for the third network function network element, i.e., the first network function network element subscribes to the first service on behalf of the third network function network element.

[0092] The first network function network element may be a UDM, a PCF, etc. in the communication system shown in Figure 1. The second network function network element may be an AMF, an SMF, etc. in the communication system shown in Figure 1. The third network function network element may be an NEF, etc. in the communication system shown in Figure 1. This is not limited in the present application.

[0093] In an optional embodiment, before the first network function network element sends the first message to the second network function network element, the method further includes the first network function network element assigning a first notification correlation identifier to the first address. The first network function network element sending the first message to the second network function network element includes the first network function network element sending the first message including the first notification correlation identifier to the second network function network element such that if a message later returned using another network element retains the first notification correlation identifier, the message may be known to be related to a subscription to the first service.

[0094] Optionally, the first message further includes instruction information, the instruction information being used to instruct the first address to receive a message notifying that the first service has been changed.

[0095] In an optional implementation, the command information may simply be a command information value, or may be an event identifier set (referred to as a third event identifier set in this embodiment of the present application). When the command information is a third event identifier set, the third event identifier set may include a status change event identifier, a subscription change event identifier, etc. Optionally, the subscription change event identifier may include a subscription correlation identifier change event identifier, an event reporting information change event identifier, etc.

[0096] In an optional embodiment, if the first message does not include the aforementioned instruction information, after receiving the first message, the second network function network element finds that one more address is held in the first message compared to the prior art, and this address is not associated with any event identifier. That is, if the first address is held and the first address is not associated with any event identifier, the first network function network element may automatically be identified as having received a message notifying that the first service has been changed using the first address. That is, in this scenario, the first address has a function that implicitly instructs to receive a message notifying that the first service has been changed using the first address. Of course, in this scenario, if the second network function network element finds the first address, the second network function network element may alternatively identify that the message notifying that the first service has been changed may have been received using the first address in any other form, for example, using a currently configured mechanism. This is not limited in the present application.

[0097] In an optional embodiment, the first service being changed means that the status of the first service is changed and / or the subscription of the first service (i.e., the subscription of the first service) is changed. The status change of the first service may be a change of the current status of the first service. For example, the current status of the first service may be, but is not limited to, a paused state, a resumed state, a stopped state, or a deleted state. The subscription change of the first service may be a change of a subscription attribute. For example, the subscription change may include a change of a subscription correlation identifier or a change of event reporting information. The event reporting information change includes at least one of a change of an event reporting mode, a change of a maximum number of event reports, and a change of a maximum duration of an event report.

[0098] In an optional embodiment, 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 performs the following step: the first network function network element receives a second message from a third network function network element, where the second message is used to subscribe to a second service. In this case, the first message sent by the third network function network element to the first network function network element may be regarded as a trigger message received by the first network function network element, so as to trigger the first network function network element to perform step 201.

[0099] In an optional embodiment, after the first network function network element receives the second message, the method further includes the first network function network element determining a first service to be subscribed to from the second network function network element based on the second service. Optionally, the message for subscribing to the first service (i.e., the first message) includes a first event identifier set, the second message includes a second event identifier set, and the first network function network element determines a set of event identifiers corresponding to events to be provided by the second network function network element in the second event identifier set, and the determined set of event identifiers is the first event identifier set.

[0100] Specifically, the second message includes a second address, and the second address is an address of a third network function network element. Optionally, the first message further includes the second address, such that the second network function network element uses the second address to provide the first service to the third network function network element.

[0101] In an optional embodiment, the second message further includes a second notification correlation identifier, the second notification correlation identifier being assigned to the second address by a third network function network element.

[0102] 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 assigns a first subscription correlation identifier to the subscription of the second service (i.e., the subscription of the second service) and sends the first subscription correlation identifier to the third network function network element. Optionally, when the first network function network element sends the first subscription correlation identifier, the first subscription correlation identifier may be retained in an event exposure subscribe response (Nnf_EventExposure_Subscribe Response) sent by the first network function network element to the third network function network element.

[0103] In an optional embodiment, after the first network function network element sends the first message to the second network function network element, the method further includes the step of: the first network function network element receiving a second subscription correlation identifier from the second network function network element, where the second subscription correlation identifier is a subscription correlation identifier assigned by the second network function network element to the subscription of the first service (i.e., the subscription of the first service) (i.e., if a message subsequently received by the first network function network element includes the second subscription correlation identifier, the first network function network element knows that the message is related to the subscription of the first service).

[0104] Step 202: A first network function network element receives a third message using the first address.

[0105] In an optional embodiment, the first network function network element receiving the third message using the first address may specifically include the following two cases:

[0106] Case 1: The first network function network element receives a third message from the second network function network element using the first address.

[0107] Case 2: The first network function network element receives a third message from the fourth network function network element using the first address, where the second network function network element requests a first service for the third network function network element from the fourth network function network element.

[0108] Specifically, in case 1, after it is detected that the first service has been changed (please refer to the related description of the change of the first service mentioned in step 201 for details), the second network function network element sends a third message to the first network function network element. For example, because the network policy has been changed, the current status of the first service may be changed from normal execution to suspended, and from suspended to resume. In another example, the subscription of the first service is cancelled, deleted, etc., due to the network policy or user subscription. In case 2, there may be three scenarios. In the first scenario, because the UE moves, the network element serving the UE is handed over from the second network function network element to a fourth network function network element. In this case, 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 subscription information of the first service, transmits the context information to the fourth network function network element to request the first service from the fourth network function network element, and transmits the first address (which may be included in the context information) to the fourth network function network element. Then, after detecting that the first service has changed (e.g., the fourth network function network element assigns a new subscription correlation identifier for the subscription of the first service), the fourth network function network element transmits a third message to the first network function network element. In the second scenario, because the UE moves, the network element serving the UE is handed over from the second network function network element to the fourth network function network element. In this case, the function of the fourth network function network element is different from that of the second network function network element.In this scenario, the second network function network element generates context information based on subscription information of the first service, transmits the context information to the fourth network function network element to request the first service from the fourth network function network element, and transmits the first address to the fourth network function network element. After detecting that the first service has changed using the functionality of the fourth network function network element, the fourth network function network element transmits a third message to the first network function network element. In the third scenario, if the second network function network element also cannot provide the first service, the second network function network element transmits a fourth message to another network function network element, i.e., the fourth network function network element. The fourth message includes the first address used to subscribe to the first service. In this way, after detecting that the first service has changed, the fourth network function network element transmits the third message to the first network function network element.

[0109] In an optional embodiment, when the first message includes command information and the command information is a third event identifier set, the third message further includes at least one event identifier in the third event identifier set such that the first network function network element identifies a specific change in the first service.

[0110] Step 203: The first network function network element knows, based on the third message, that the first service has been changed.

[0111] In an optional embodiment, after the first network function network element knows that the first service has been changed based on the third message, the method further includes the following steps: the first network function network element sends a fifth message to a second address of the third network function network element, where the fifth message is used to notify that the second service has been changed.

[0112] In an optional embodiment, the first network function network element sending a fifth message to the second address of the third network function network element includes the first network function network element sending a fifth message to the second address of the third network function network element, the fifth message including the first subscription correlation identifier mentioned in step 201.

[0113] In an optional embodiment, the third message further includes the second subscription correlation identifier mentioned in step 201. The first network function network element knowing that the first service has changed based on the third message includes the first network function network element knowing that the first service has changed based on the second subscription correlation identifier in the third message.

[0114] In an optional embodiment, the third message received by the first network function network element using the first address further includes the first notification correlation identifier mentioned in step 201. The first network function network element knowing that the first service has changed based on the third message includes the first network function network element knowing that the first service has changed based on the first notification correlation identifier in the third message (i.e., if a message subsequently received by the first network function network element includes the first notification correlation identifier, the first network function network element knows that the message is related to a subscription to the first service).

[0115] In an optional embodiment, the first network function network element sending a fifth message to the second address of the third network function network element includes the first network function network element sending a fifth message to the second address of the third network function network element, the fifth message including the second notification correlation identifier mentioned in step 201.

[0116] Optionally, in a specific implementation, if the change of the first service is the status change mentioned in step 201, the third message further includes the first status information. The fifth message further includes the second status information. The first status information or the second status information may be a paused state, a resumed state, a stopped state, a deleted state, etc. Optionally, the third message further includes an event identifier and / or a user identity corresponding to the first status information.

[0117] Optionally, if the change of the first service is a change of subscription mentioned in step 201, the third message further includes subscription attributes of the changed subscription of the first service. The fifth message further includes subscription attributes of the changed subscription of the second service. Specifically, if the change of subscription is a change of subscription correlation identifier, the subscription attributes of the changed subscription of the first service or the subscription attributes of the changed subscription of the second service are an updated subscription correlation identifier. If the change of subscription is a change of event reporting information, the subscription attributes of the changed subscription of the first service or the subscription attributes of the changed subscription of the second service may include at least one of an updated event reporting mode, an updated maximum amount of event reporting, and an updated maximum duration of event reporting.

[0118] According to the service subscription method provided in this embodiment of the present application, a first network function network element sends a first message to a second network function network element to subscribe to a first service for a third network function network element from the second network function network element. Wherein, the first message includes a first address, the first address is an address of the first network function network element, and the first network function network element receives a third message using the first address, and knows that the first service has been changed based on the third message. In this method, the first network function network element sends the address of the first network function network element to the second network function network element. Thus, when the first service is changed, the first network function network element may receive a notification that the service has been changed. In this way, the mechanism for reporting the service change is improved so that the service subscription procedure can be relatively complete and no interruption occurs.

[0119] The service subscription method provided in the embodiment of the present application will be described in detail below using specific examples in the embodiments of FIG. 3, FIG. 4A and FIG. 4B, and FIG. 5 based on the embodiment of FIG.

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

[0121] Step 301: The NEF obtains trigger information. Specifically, after the NEF obtains the trigger information, the NEF is triggered to perform service subscription from the UDM.

[0122] Optionally, the trigger information may come from another network function network element, such as an AF. Alternatively, the trigger information may be obtained by triggering through an internal trigger mechanism of the NEF.

[0123] Step 302: The NEF sends a second message to the UDM, and the NEF uses the second message to subscribe to a second service from the UDM.

[0124] The second message includes an address of the NEF, i.e., the second address. In this way, the NEF uses the second address to receive the requested event. In an optional implementation, the second message further includes a second event identifier set (such as Event Id1) and a second notification correlation identifier (such as Notification Correlation ID) mentioned in the embodiment of FIG. 2. The second event identifier set may include at least one event identifier. The second notification correlation identifier is used by the NEF to correlate a later received Event Notification (i.e., information in the later received fifth message) with a previously delivered Event Subscription (i.e., subscription information for the second service in the second message).

[0125] In an optional embodiment, the second message may further include an external identifier of a UE (e.g., for one UE), a group identifier of a group of UEs (e.g., for a group of UEs), or an indication of any UE (e.g., any UE parameter valid for all UEs in the live network), thereby determining to which UE the second service will ultimately be provided.

[0126] In an optional embodiment, the second message further includes event reporting information, and the event reporting information includes at least one of an event reporting mode, a maximum number of event reports, and a maximum duration of the event reports. The event reporting mode may be a one-time report, a continuous report, a periodic report, etc.

[0127] In an optional embodiment, the second message may be a Nudm_Event Exposure_Subscribe Request sent by the NEF to the UDM. In a specific implementation, the NEF sends a HyperText Transfer Protocol request (HTTP POST) to the UDM. The destination address of the request may be a uniform resource locator (URL), and the message body of the HTTP POST holds the aforementioned information that may be included in the second message. Here, the details will not be described again.

[0128] Step 303: The UDM stores the information in the second message and assigns a first subscription correlation identifier (Subscription Correlation ID1) to the subscription to the second service in the second message.

[0129] In a specific implementation, the UDM creates a resource for subscription of the second service based on the above information held in the body, generates a child resource identifier subscription id1, and constructs a uniform resource identifier 1 (Uniform Resource Locator, URI) for the created resource. The URI1 is generated by using the requested URI as the parent resource and then splicing in the child resource identifier. Here, subscription id1 may be used as subscription correlation ID1.

[0130] Step 304: The UDM sends a first message to the AMF, and the UDM uses the first message to subscribe to a first service from the AMF. The first message includes an address of the UDM, i.e., a first address.

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

[0132] For example, after receiving the second message, the UDM first determines one or more events (i.e., the second event set corresponding to the second event identifier set in the second message) that are in the second event set corresponding to the second event identifier set in the second message and need to be provided by the AMF, and then executes step 304. That is, 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 a part or all of the second event identifier set.

[0133] Specifically, in addition to the first address, the first message further includes a second address used by the AMF to provide the first service to the NEF. When the first service is changed, the UDM may use the first address to receive a message notifying that the first service has been changed.

[0134] In an optional embodiment, the first message further includes instruction information, and the instruction information is used to instruct the first address to receive a message notifying that the first service has been changed. Specifically, the first service has been changed means that the status of the first service has been changed and / or the subscription of the first service has been changed. The status change of the first service may be a change of the current status of the first service. For example, the current status of the first service may be, but is not limited to, a dormant state, a resumed state, a discontinued state, or a deleted state. The subscription change may be a change of a subscription attribute. For example, the subscription change includes a change of a subscription correlation identifier or a change of event reporting information. The event reporting information change includes at least one of a change of an event reporting mode, a change of a maximum number of event reports, a change of a maximum duration of an event report, and the like. That is, any one of the aforementioned cases may indicate that the first service has been changed.

[0135] In an optional embodiment, the command information may simply be a command information value or may be an event identifier set (i.e., a third event identifier set). When the command information is a third event identifier set, the third event identifier set may include a status change event identifier, a subscription change event identifier, etc. In this case, the command information may be considered to have a function of commanding to provide a special event. For example, the special event may be a status change event or a subscription change event. Optionally, the subscription change event identifier may include a subscription correlation identifier change event identifier or an event reporting information change event identifier.

[0136] In an optional embodiment, if the first message does not include the aforementioned instruction information, after receiving the first message, the AMF finds that the first message holds one more address than the prior art. That is, if the first address is held, the AMF automatically identifies that the UDM has received a message notifying that the first service has been changed using the first address. That is, in this scenario, the first address has a function of implicitly instructing the UDM to receive a message notifying that the first service has been changed using the first address. Of course, in this scenario, alternatively, if the AMF finds the first address, the AMF may identify that the message notifying that the first service has been changed may have been received using the first address in any other form, for example, using a currently configured mechanism. This is not limited in the present application.

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

[0138] Step 305: After receiving the first message, the AMF stores information in the first message and assigns a second subscription correlation identifier (Subscription Correlation ID2) to the subscription of the first service in the first message.

[0139] In a specific implementation, the AMF creates a resource for subscription of the first service based on the information held in the body, generates a child resource identifier subscription id1, and constructs a uniform resource identifier (Uniform Resource Locator, URI) 2 for the created resource. The URI 2 is generated by using the requested URI as a parent resource and then splicing the child resource identifier. Here, subscription id2 may be used as subscription correlation ID2.

[0140] Step 306: The AMF sends a sixth message to the UDM, where the sixth message includes subscription correlation ID2.

[0141] In an optional embodiment, the sixth message may be an event exposure subscribe response (Namf_EventExposure_Subscribe Response) sent by the AMF to the UDM. In a specific implementation, the AMF returns an HTTP response to the UDM, where the HTTP response carries a status code of "201 Created" and a "Location" header. The location header carries URI2.

[0142] Step 307: The UDM returns a seventh message to the NEF, where the seventh message includes the subscription correlation ID1.

[0143] In an optional embodiment, the seventh message may be an event exposure subscribe response (Nudm_EventExposure_Subscribe Response) sent by the UDM to the NEF. In a specific implementation, the UDM returns an HTTP response to the NEF, where the HTTP response carries a status code of "201 Created" and a "Location" header. The location header carries URI1.

[0144] Step 308: If an event to be provided to the NEF is detected, the AMF provides a first service to the NEF.

[0145] Step 309: If it detects that the first service has been changed, the AMF executes step 310.

[0146] Optionally, if the AMF serving the UE needs to be reselected because the UE moves, the AMF transmits the information received in step 304 to another AMF (i.e., the AMF reselected for the UE). In this case, the other AMF may detect that the first service has been changed, i.e., the other AMF may perform the AMF operation in step 309, and then the other AMF continues to perform the AMF operation in step 310.

[0147] In an optional embodiment, if the first message includes instruction information, the AMF (or another AMF) may perform detection according to the instruction information. Alternatively, the AMF (or another AMF) may perform detection according to a system configuration. Specifically, the AMF (or another AMF) detects that the change of the first service may be any change described in step 304, and the details will not be described again here.

[0148] For example, the current status of the first service may change from normal execution to suspended and from suspended to resume due to a network policy change or a capability of the AMF (or another AMF) change. In another example, the subscription of the first service may be cancelled, deleted, etc., due to a network policy or a user subscription.

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

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

[0151] 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 another AMF) to the UDM.

[0152] Step 311: The UDM knows based on the third message that the first service has been changed.

[0153] In an optional embodiment, if the first service change is a status change as described in step 304, the third message further includes first status information. The first status information may be a dormant state, a resumed state, a suspended state, a deleted state, etc. Optionally, in this case, the third message further includes an event identifier and / or a user identity (such as a UE identity) corresponding to the first status information. The event identifiers are used as follows: If the status of one or more events corresponding to the first event identifier set is changed, the event identifier carrying the status change may indicate that a status change event has occurred. The user identity is used as follows: If the event subscription is for a group of users, the user identity carrying the status change is used to indicate the user corresponding to the status change.

[0154] In an optional embodiment, if the change in the first service is a change in a subscription as described in stage 304, the third message further includes subscription attributes of the changed subscription to the first service. Optionally, if the change in the subscription is a change in a subscription correlation identifier, the changed subscription attributes are an updated subscription correlation identifier. If the change in the subscription is a change in event reporting information, the changed subscription attributes include at least one of an updated event reporting mode, an updated maximum amount of event reporting, and an updated maximum duration of event reporting.

[0155] Optionally, the first message further includes a first notification correlation identifier, the first notification correlation identifier being assigned by the UDM to the first address. The third message sent by the AMF to the first address of the UDM further includes the first notification correlation identifier. The UDM knowing that the first service has changed based on the third message includes the UDM knowing that the first service has changed based on the first notification correlation identifier in the third message.

[0156] In an optional embodiment, if the first message includes instruction information and the instruction information is a third event identifier set, the third message further includes at least one event identifier in the third event identifier set such that the UDM identifies a particular change to the first service.

[0157] Step 312: If the change in 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 that the second service has been changed.

[0158] 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.

[0159] In an optional embodiment, if the first service change is the status change described in step 304 and the third message further includes the first status information, the fifth message further includes the second status information. For specific restrictions on the second status information, please refer to the restrictions on the first status information. Here, the details will not be described again.

[0160] In an optional embodiment, when the change of the first service is the change of subscription described in step 304, and the third message further includes subscription attributes of the changed subscription of the first service, the fifth message further includes subscription attributes of the changed subscription of the second service. In particular, for restrictions on the subscription attributes of the changed subscription of the second service, please refer to the restrictions on the changed subscription attributes in the preceding step. Here, the details will not be described again.

[0161] In a specific implementation, the second message further includes a second notification correlation identifier, and the second notification correlation identifier is assigned to a second address by the NEF. The fifth message sent to the NEF by the UDM further includes a second notification correlation identifier.

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

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

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

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

[0166] In the above example, the UDM sends the AMF its address so that when the first service is changed, the UDM may receive a notification so that the service subscription procedure can be relatively complete and no interruptions occur.

[0167] As shown in Figures 4A and 4B, an embodiment of the present application further provides an example of a service subscription method. In this example, a first network function network element is a PCF, a second network function network element is an SMF, and a third network function network element is an NEF. The NEF subscribes to a service from the PCF, and the PCF further subscribes to a service for the NEF from the SMF. Specifically, the procedure of this example may include the following steps:

[0168] Step 401: The NEF first obtains trigger information. Specifically, after the NEF obtains the first trigger information, the NEF is triggered to request policy authorization from the PCF.

[0169] Optionally, the first trigger information may come from another network function network element, such as an AF. In this case, the first trigger information of the AF may be that the AF requests policy authorization from the PCF. Alternatively, the first trigger information may be obtained by triggering an internal trigger mechanism of the NEF.

[0170] Step 402: The NEF sends a tenth message to the PCF, where the tenth message includes application layer information and is used to request policy authorization.

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

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

[0173] In a specific implementation, the PCF creates a resource for the application session based on the application layer information carried in the body of the HTTP POST in step 402, generates a child resource identifier appsessionid, and constructs a URI1 for the created resource. URI1 is generated by using the requested URI as the parent resource and then splicing in the child resource identifier.

[0174] Optionally, the tenth message may include network policies, user subscriptions, and the like.

[0175] 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.

[0176] In a specific implementation, the PCF may return an HTTP response to the NEF, where the HTTP response carries a status code of "201 Created" and a "Location" header, where the Location header carries the URI1 constructed in step 403.

[0177] Step 405: After performing policy decision-making 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.

[0178] Specifically, the twelfth message may be a policy update notify request (Npcf_Policy_UpdateNotify Request) sent by the PCF to the SMF. In a specific implementation, the PCF sends an HTTP POST to the SMF, where the message body holds the formulated policy.

[0179] Step 406: After storing the policy, the SMF returns a thirteenth message to the PCF.

[0180] Specifically, the thirteenth message may be a policy update notify response (Npcf_Policy_UpdateNotify Response) sent by the SMF to the PCF. In a specific implementation, the SMF sends an HTTP response to the PCF, where the HTTP response carries a status code of “200 OK”.

[0181] Step 407: After the NEF obtains the second trigger information, if the NEF needs to subscribe to a service for the 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.

[0182] The second message includes an address of the NEF, i.e., the second address. In this way, the NEF uses the second address to receive the requested event. In an optional implementation, the second message further includes a second event identifier set (Event Id1) and a second notification correlation identifier (Notification Correlation ID) described in the embodiment of FIG. 2. The second event identifier set may include at least one event identifier.

[0183] In an optional embodiment, the second message may further include an external identifier of a UE (e.g., for one UE), a group identifier of a group of UEs (e.g., for a group of UEs), or an indication of any UE (e.g., any UE parameter valid for all UEs in the live network), thereby determining to which UE the second service will ultimately be provided.

[0184] In an optional embodiment, the second message further includes event reporting information, and the event reporting information includes at least one of an event reporting mode, a maximum number of event reports, and a maximum duration of the event reports. The event reporting mode may be a one-time report, a continuous report, a periodic report, etc.

[0185] In an optional embodiment, the second message may be a policy authorization subscription request (Npcf_PolicyAuthorization_Subscribe Request) sent by the NEF to the PCF. In a specific implementation, the NEF sends an HTTP PATCH to the PCF, and the message body of the HTTP PATCH holds the above-mentioned information that may be included in the second message. Here, the details are not described again.

[0186] Step 408: The PCF stores the information in the second message, updates the application session context, and assigns a first subscription correlation identifier (Subscription Correlation ID1) for the subscription of the second service.

[0187] In a specific implementation, the subscribed services are added to the resources created in step 403 .

[0188] Step 409: The PCF sends a fourteenth message to the NEF, where the fourteenth message includes the subscription correlation ID1.

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

[0190] In a specific implementation, the PCF sends an HTTP response to the NEF, where the HTTP response carries the status code "200 OK" and the subscription correlation ID1.

[0191] Step 410: The PCF sends a first message to the SMF, and the PCF uses the first message to subscribe to a first service from the SMF. The first message includes an address of the PCF, i.e. a first address.

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

[0193] For example, after receiving the second message, the PCF first determines the events that need to be provided by the SMF that are in the second event set corresponding to the second event identifier set in the second message (i.e., the second event set corresponding to the second event identifier set in this embodiment of the present application), and then executes step 410. That is, 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 a part or all of the second event identifier set.

[0194] Specifically, in addition to the first address, the first message further includes a second address, and the second address is used by the SMF to provide the first service to the NEF. When the first service is changed, the PCF may use the first address to receive a message notifying that the first service has been changed.

[0195] In an optional embodiment, the first message further includes instruction information, and the instruction information is used to instruct the first address to receive a message notifying that the first service has been changed. Specifically, the first service has been changed means that the status of the first service has been changed and / or the subscription of the first service has been changed. The status change of the first service may be a change of the current status of the first service. For example, the current status of the first service may be, but is not limited to, a dormant state, a resumed state, a discontinued state, or a deleted state. The subscription change may be a change of a subscription attribute. For example, the subscription change includes a change of a subscription correlation identifier or a change of event reporting information. The event reporting information change includes at least one of a change of an event reporting mode, a change of a maximum number of event reports, a change of a maximum duration of an event report, and the like. That is, any one of the aforementioned cases may indicate that the first service has been changed.

[0196] In an optional embodiment, the command information may simply be a command information value or may be an event identifier set (i.e., a third event identifier set). When the command information is a third event identifier set, the third event identifier set may include a status change event identifier, a subscription change event identifier, etc. In this case, the command information may be considered to have a function of commanding to provide a special event. For example, the special event may be a status change event or a subscription change event. Optionally, the subscription change event identifier may include a subscription correlation identifier change event identifier or an event reporting information change event identifier.

[0197] In an optional embodiment, if the first message does not include the aforementioned instruction information, after receiving the first message, the AMF finds that the first message holds one more address than the prior art. That is, if the first address is held, the UDM may automatically identify that it has received a message notifying that the first service has been changed using the first address. That is, in this scenario, the first address has a function that implicitly instructs the UDM to use the first address to receive a message notifying that the first service has been changed. Of course, in this scenario, alternatively, if the AMF finds the first address, the AMF may identify that the message notifying that the first service has been changed may have been received using the first address in any other form, for example, using a currently configured mechanism. This is not limited in the present application.

[0198] Step 411: The SMF stores information in the first message and assigns a second subscription correlation identifier (Subscription Correlation ID2) to the subscription to the first service in the first message.

[0199] In a specific implementation, the SMF creates a resource for the subscription of the first service based on the information carried in the first message, generates a child resource identifier subscription_id2, and constructs a URI2 for the created resource, where URI2 is generated by using the requested URI as a parent resource and then splicing in the child resource identifier, where subscription_id2 may be used as subscription correlation_id2.

[0200] Step 412: The SMF sends a 15th message to the PCF, where the 15th message includes the subscription correlation ID2.

[0201] In an optional embodiment, the fifteenth message may be an event exposure subscribe response (Nsmf_EventExposure_Subscribe Response) sent by the SMF to the PCF. In a specific implementation, the SMF returns an HTTP response to the PCF, where the HTTP response carries a status code of "201 Created" and a "Location" header. The location header carries the URI2 constructed in step 411.

[0202] Step 413: If an event to be provided to the NEF is detected, the SMF provides a first service to the NEF.

[0203] Step 414: If it is detected that the first service has been changed, the SMF executes step 415.

[0204] Optionally, if the SMF serving the UE needs to be reselected because the UE moves, the SMF transmits the information received in step 410 to another SMF (i.e., the SMF reselected for the UE). In this case, the other SMF detects that the first service has changed (e.g., the other SMF assigns a new subscription correlation identifier for the subscription of the first service). That is, the other SMF may perform the operation of the SMF in step 414, and then the other SMF continues to perform the operation of the SMF in step 415.

[0205] For specific implementation, please refer to the description of step 309 in the embodiment shown in Figure 3. The principle is the same, and the details will not be described again here.

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

[0207] 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.

[0208] Step 416: The PCF knows based on the third message that the first service has been modified.

[0209] In an optional embodiment, if the first service change is a status change as described in step 410, the third message further includes first status information. The first status information may be a dormant state, a resumed state, a suspended state, a deleted state, etc. Optionally, in this case, the third message further includes an event identifier and / or a user identity (such as a UE identity) corresponding to the first status information. The event identifiers are used as follows: If the status of one or more events corresponding to the first event identifier set is changed, the event identifier carrying the status change may indicate that a status change event has occurred. The user identity is used as follows: If the event subscription is for a group of users, the user identity carrying the status change is used to indicate the user corresponding to the status change.

[0210] In an optional embodiment, if the change in the first service is a change in a subscription as described in stage 410, the third message further includes subscription attributes of the changed subscription for the first service. Optionally, if the change in the subscription is a change in a subscription correlation identifier, the changed subscription attributes are an updated subscription correlation identifier. If the change in the subscription is a change in event reporting information, the changed subscription attributes include at least one of an updated event reporting mode, an updated maximum amount of event reporting, and an updated maximum duration of event reporting.

[0211] Optionally, the first message further includes a first notification correlation identifier, the first notification correlation identifier being assigned to the first address by the PCF. The third message sent by the SMF to the first address of the PCF further includes the first notification correlation identifier. The PCF knowing that the first service has changed based on the third message includes the PCF knowing that the first service has changed based on the first notification correlation identifier in the third message.

[0212] In an optional embodiment, if the first message includes command information and the command information is a third event identifier set, the third message further includes at least one event identifier in the third event identifier set such that the PCF identifies a specific change in the first service.

[0213] Step 417: If the PCF determines that the change in 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 that the second service has been changed.

[0214] 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.

[0215] In an optional embodiment, if the first service change is the status change described in step 410 and the third message further includes the first status information, the fifth message further includes the second status information. For specific restrictions on the second status information, please refer to the restrictions on the first status information. Here, the details will not be described again.

[0216] In an optional embodiment, when the change of the first service is the change of subscription described in step 410, and the third message further includes subscription attributes of the changed subscription of the first service, the fifth message further includes subscription attributes of the changed subscription of the second service. In particular, for restrictions on the subscription attributes of the changed subscription of the second service, please refer to the restrictions on the changed subscription attributes in the preceding step. Here, the details will not be described again.

[0217] In a specific implementation, the second message further includes a second notification correlation identifier, and the second notification correlation identifier is assigned to a second address by the NEF. The fifth message sent by the PCF to the NEF further includes a second notification correlation identifier.

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

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

[0220] Step 419: The PCF sends the 17th message to the SMF.

[0221] Specifically, the 17th message may be an event exposure subscription change report response (Nsmf_Event_Exposure_SubscriptionChangeReport Response) or an event exposure notify response (Nsmf_Event_Exposure_Notify Response) sent by the PCF to the SMF.

[0222] In the above example, the PCF sends the SMF the address of the PCF so that when the first service is changed, the PCF may receive a notification so that the service subscription procedure can be relatively complete and no interruptions occur.

[0223] Based on the above embodiment, an embodiment of the present application further provides a service subscription method. In this embodiment, the network element that performs the service subscription may be collectively referred to as a network function service consumer (NF service consumer), and the network element that provides the service may be collectively referred to as a network function service producer (NF service producer). Both the network function service consumer and the network function service producer are network function network elements in the communication system shown in Figure 1. Referring to Figure 5, the specific steps of the method include the following steps:

[0224] Step 501: An NF service consumer needs to obtain trigger information and subscribe to a service for another functional network element from an NF service producer. Specifically, after the NF service consumer obtains the trigger information, the NF service consumer is triggered to perform a service subscription from the NF service producer.

[0225] Optionally, the trigger information may come from another network function network element (i.e., another NF). For example, the trigger information may be obtained by triggering by the NEF in the above embodiment, i.e., triggering by the second message. Alternatively, the trigger information may be obtained by triggering by an internal trigger mechanism of the NF service consumer.

[0226] Step 502: The NF service consumer sends a first message to the NF service producer, and the NF service consumer uses the first message to subscribe to a first service from the NF service producer. The first message includes an address of the NF service consumer, i.e., a first address. If the first service is changed, the NF service consumer may use the first address to receive a message notifying that the first service has been changed.

[0227] Specifically, in addition to the first address, the first message further includes a notification target address. A device corresponding to the notification target address may use the notification target address to receive the requested event, that is, the NF service producer uses the notification target address to provide the first service to the device corresponding to the notification target address. Optionally, the notification target address may be, but is not limited to, the second address in the above embodiment.

[0228] In an optional embodiment, the first message further includes a first notification correlation identifier, which is used by the NF service consumer to correlate the Event Notification with a corresponding Event Subscription. The first message further includes an external identifier of the UE (e.g., for one UE), a group identifier of a group of UEs (e.g., for a group of UEs), or an indication of any UE (e.g., any UE parameter valid for all UEs in the live network).

[0229] In an optional embodiment, the first message further includes event reporting information, and the event reporting information includes at least one of an event reporting mode, a maximum number of event reports, and a maximum duration of the event reports. The event reporting mode may be a one-time report, a continuous report, a periodic report, etc.

[0230] In an optional embodiment, the first message further includes instruction information, and the instruction information is used to instruct the first address to receive a message notifying that the first service has been changed. Specifically, the first service has been changed means that the status of the first service has been changed and / or the subscription of the first service has been changed. The status change of the first service may be a change of the current status of the first service. For example, the current status of the first service may be, but is not limited to, a dormant state, a resumed state, a discontinued state, or a deleted state. The subscription change may be a change of a subscription attribute. For example, the subscription change includes a change of a subscription correlation identifier or a change of event reporting information. The event reporting information change includes at least one of a change of an event reporting mode, a change of a maximum number of event reports, a change of a maximum duration of an event report, and the like. That is, any one of the aforementioned cases may indicate that the first service has been changed.

[0231] In an optional embodiment, the command information may simply be a command information value or may be an event identifier set (i.e., a third event identifier set). When the command information is a third event identifier set, the third event identifier set may include a status change event identifier, a subscription change event identifier, etc. In this case, the command information may be considered to have a function of commanding to provide a special event. For example, the special event may be a status change event or a subscription change event. Optionally, the subscription change event identifier may include a subscription correlation identifier change event identifier or an event reporting information change event identifier.

[0232] In an optional embodiment, if the first message does not include the aforementioned instruction information, after receiving the first message, the NF service producer finds that the first message holds one more address than that of the prior art. That is, if the first address is held, the NF service producer automatically identifies that the NF service consumer has received a message notifying that the first service has been changed using the first address. That is, in this scenario, the first address has a function of implicitly instructing the NF service consumer to receive a message notifying that the first service has been changed using the first address. Of course, in this scenario, alternatively, if the NF service producer finds the first address, the NF service producer may identify that the message notifying that the first service has been changed may have been received using the first address in any other form, for example, using a currently configured mechanism. This is not limited in the present application.

[0233] In an optional embodiment, the first message sent by the NF service consumer to the NF service producer may be an event exposure subscription request (Nnf_Event Exposure_Subscribe Request).

[0234] Step 503: After receiving the first message, the NF service producer stores the information in the first message and assigns a second subscription correlation identifier (Subscription Correlation ID2) to the subscription for the first service in the first message.

[0235] In a specific implementation, the NF service producer creates a resource for subscription of the first service based on the information held in the body, generates a child resource identifier subscription id1, and constructs a uniform resource identifier (Uniform Resource Locator, URI) 2 for the created resource. The URI 2 is generated by using the requested URI as a parent resource and then splicing the child resource identifier. Here, subscription id2 may be used as subscription correlation ID2.

[0236] Step 504: The NF service producer sends an 18th message to the NF service consumer, where the 18th message includes the subscription correlation ID2.

[0237] In an optional embodiment, the 18th message may be an event exposure subscribe response (Nnf_EventExposure_Subscribe Response) sent by the NF service producer to the NF service consumer. In a specific implementation, the NF service producer returns an HTTP response to the NF service consumer, where the HTTP response carries a status code of "201 Created" and a "Location" header. The location header carries a URI2.

[0238] Step 505: When detecting an event to be provided to the NF service consumer, the NF service producer provides a first service to the NF service consumer.

[0239] Step 506: If the NF service producer detects that the first service has changed, it executes step 507.

[0240] Optionally, if the NF service producer serving the UE needs to be reselected because the UE moves, the NF service producer transmits the information received in step 502 to another NF network element (i.e., the NF network element reselected for the UE). In this case, the other NF network element may detect that the first service has changed, i.e., the other NF network element performs the operation of the NF service producer in step 505, and then the other NF network element continues to perform the operation of the NF service producer in step 507. The function of the other NF network element is the same as that of the NF service producer.

[0241] In an optional embodiment, if the first message includes instruction information, the NF service producer (or another NF network element) may perform detection according to the instruction information. Alternatively, the NF service producer (or another NF network element) may perform detection according to the system configuration. Specifically, the NF service producer (or another NF network element) detects that the change of the second service may be any change described in step 502, and the details will not be described again here.

[0242] For example, the current status of the first service may change from normal execution to Suspend and from Suspend to Resume due to a network policy change or a capability of the NF service producer (or another NF network element) change. In another example, the subscription of the first service may be Canceled, Deleted, etc., due to a network policy or a user subscription.

[0243] Step 507: The NF service producer (or another NF network element) sends a third message to a first address of the NF service consumer, where the third message is used to notify that the first service has been changed.

[0244] In a 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 an NF service producer (or another NF network element) to an NF service consumer.

[0245] Step 508: The NF service consumer knows that the first service has been changed based on the third message.

[0246] In an optional embodiment, if the first service change is a status change as described in step 502, the third message further includes first status information. The first status information may be a dormant state, a resumed state, a suspended state, a deleted state, etc. Optionally, in this case, the third message further includes an event identifier and / or a user identity (such as a UE identity) corresponding to the first status information. The event identifiers are used as follows: If the status of one or more events corresponding to the first event identifier set is changed, the event identifier carrying the status change may indicate that a status change event has occurred. The user identity is used as follows: If the event subscription is for a group of users, the user identity carrying the status change is used to indicate the user corresponding to the status change.

[0247] In an optional embodiment, if the change in the first service is a change in a subscription as described in stage 502, the third message further includes subscription attributes of the changed subscription in the first service. Optionally, if the change in the subscription is a change in a subscription correlation identifier, the changed subscription attributes are an updated subscription correlation identifier. If the change in the subscription is a change in event reporting information, the changed subscription attributes include at least one of an updated event reporting mode, an updated maximum amount of event reporting, and an updated maximum duration of event reporting.

[0248] Optionally, the first message further includes a first notification correlation identifier, the first notification correlation identifier being assigned to the first address by the NF service consumer. The third message sent by the NF service producer to the first address of the NF service consumer further includes the first notification correlation identifier. The NF service consumer knowing that the first service has changed based on the third message includes the NF service consumer knowing that the first service has changed based on the first notification correlation identifier in the third message.

[0249] In an optional embodiment, if the first message includes command information and the command information is a third event identifier set, the third message further includes at least one event identifier in the third event identifier set such that the NF service consumer identifies a particular change in the first service.

[0250] Step 509: The NF service consumer sends a nineteenth message to the NF service producer.

[0251] Specifically, the 19th message may be an event exposure subscription change report response (Nnf_Event_Exposure_SubscriptionChangeReport Response) or an event exposure notify response (Nnf_Event_Exposure_Notify Response) sent by the NF service consumer to the NF service producer.

[0252] In the service subscription method provided in this embodiment of the present application, the NF service consumer sends the address of the NF service consumer to the NF service producer. In this way, when the first service is changed, the NF service consumer may receive a notification, so that the service subscription procedure can be relatively complete and no interruption occurs.

[0253] Based on the same inventive concept of the method embodiment, an embodiment of the present application further provides an apparatus, which is applied to a first network function network element. The apparatus 600 may specifically be a processor, a chip or chip system, a function module, etc. in the first network function network element. Referring to FIG. 6, the apparatus 600 may include a sending unit 601, a receiving unit 602, and a processing unit 603. The sending unit 601 is used by the apparatus 600 to send information, the receiving unit 602 is used by the apparatus 600 to receive information, and the processing unit 603 is configured to control and manage the operation of the apparatus 600. The processing unit 603 may be further configured to direct a processing process related to the first network function network element (such as UDM or PCF) in any one of the previous embodiments and / or another process of the technical solution described in the present application. Specifically, the processing unit 603 may control the sending unit 601 to perform step 201, and control the receiving unit 602 to perform step 202 and step 203. For details, please refer to the embodiment shown in Fig. 2. Here, the details will not be described again.

[0254] In a hardware implementation, the processing unit 603 may be a processor, a processing circuit, etc., the transmitting unit 601 may be a transmitter, a transmitting circuit, etc., and the receiving unit 602 may be a receiver, a receiving circuit, etc. The transmitting unit 601 and the receiving unit 602 may constitute a transceiver.

[0255] Based on the same inventive concept as the method embodiment, an embodiment of the present application further provides an apparatus, which is applied to a second network function network element. The apparatus 700 may specifically be a processor, a chip or a chip system, a function module, etc. in the second network function network element. Referring to FIG. 7, the apparatus 700 may include a receiving unit 701, a sending unit 702, and a processing unit 703. The sending unit 702 is used by the apparatus 700 to send information, the receiving unit 701 is used by the apparatus 700 to receive information, and the processing unit 703 is configured to control and manage the operation of the apparatus 700. The processing unit 703 may further be configured to instruct a processing process related to the second network function network element (such as AMF or SMF) in any one of the foregoing embodiments, and / or another process of the technical solution described in the present application. Specifically, please refer to the foregoing embodiment for the steps that the processing unit 703 may control the sending unit 702 and the receiving unit 701 to perform. The overlapping content will not be explained again here.

[0256] In a hardware implementation, the processing unit 703 may be a processor, a processing circuit, etc., the transmitting unit 702 may be a transmitter, a transmitting circuit, etc., and the receiving unit 701 may be a receiver, a receiving circuit, etc. The transmitting unit 702 and the receiving unit 701 may constitute a transceiver.

[0257] It should be noted that in the embodiment of the present application, the division of the units is merely an example and is merely a logical division of functions. In actual implementation, other division methods may be used. The functional units in the embodiment of the present application may be integrated into one processing unit, or each of the units may exist physically alone, or two or more units may be integrated into one unit. The integrated units may be implemented in the form of hardware or in the form of software functional units.

[0258] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application in essence, or a part contributing to the prior art, or all or a part of the technical solution may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes one or more instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) or a processor to execute all or a part of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or a compact disk.

[0259] Based on the above embodiment, an embodiment of the present application further provides another first network function network element configured to implement the above service subscription method. Referring to FIG. 8, 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 further include a memory 803. The memory 803 may be disposed inside the first network function network element 800, or may be disposed outside the first network function network element 800. The processor 802 is configured to control the transceiver 801 to receive and transmit data, and to implement the method performed by the first network function network element (such as UDM and PCF) in FIG. 2-FIG. 5.

[0260] 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.

[0261] The transceiver 801, the processor 802, and the memory 803 are connected to each other. Optionally, the transceiver 801, the processor 802, and the memory 803 are connected to each other using a bus 804. The bus 804 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be classified into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used to represent a bus in FIG. 8, but this does not imply that there is only one bus or only one type of bus.

[0262] In an optional embodiment, the memory 803 is configured to store a program. Specifically, the program may include a program code, and the program code includes computer operation instructions. The memory 803 may include a RAM and may further include a non-volatile memory such as at least one magnetic disk memory. The processor 802 executes an application program stored in the memory 803 to implement the aforementioned functions and implements a service subscription method provided in the embodiment of the present application.

[0263] Based on the above embodiment, an embodiment of the present application further provides another second network function network element configured to implement the above service subscription method. Referring to FIG. 9, 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 further include a memory 903. The memory 903 may be disposed inside the second network function network element 900, or may be disposed outside the second network function network element 900. The processor 902 is configured to control the transceiver 901 to receive and transmit data, and to implement the method performed by the second network function network elements (AMF and SMF) in FIG. 2-FIG. 5.

[0264] 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.

[0265] The transceiver 901, the processor 902, and the memory 903 are connected to each other. Optionally, the transceiver 901, the processor 902, and the memory 903 are connected to each other using a bus 904. The bus 904 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be classified into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used to represent a bus in FIG. 9, but this does not mean that there is only one bus or only one type of bus.

[0266] In an optional embodiment, the memory 903 is configured to store a program. Specifically, the program may include a program code, and the program code includes computer operation instructions. The memory 903 may include a RAM and may further include a non-volatile memory such as at least one magnetic disk memory. The processor 902 executes an application program stored in the memory 903 to implement the aforementioned functions and implements a service subscription method provided in an embodiment of the present application.

[0267] Based on the above embodiment, an embodiment of the present application further provides a computer storage medium. The storage medium stores a software program, which, when read and executed by one or more processors, can implement the method provided in any one or more of the above embodiments. The computer storage medium may include any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory, a random access memory, a magnetic disk, or a compact disk.

[0268] Based on the above-mentioned embodiment, an embodiment of the present application further provides a chip, the chip includes a processor configured to implement the functions in any one or more of the above-mentioned embodiments, for example, to obtain or process information or messages in the above-mentioned method. Optionally, the chip further includes a memory, the memory is configured to store necessary program instructions and data executed by the processor. The chip may include one chip, or may include one chip and another separate device.

[0269] In summary, according to the service subscription method and device provided in the embodiment of the present application, a first network function network element sends a first message to a second network function network element to subscribe to a first service for a third network function network element from the second network function network element. The first message includes a first address, the first address is an address of the first network function network element, and the first network function network element receives a third message using the first address, and knows that the first service has been changed based on the third message. In this method, the first network function network element sends the address of the first network function network element to the second network function network element. Thus, when the first service is changed, the first network function network element may receive a notification that the service has been changed. In this way, the mechanism for reporting the service change is improved so that the service subscription procedure can be relatively complete and no interruption occurs.

[0270] Those skilled in the art should understand that the embodiments of the present application may be provided as a method, a system, or a computer program product. Thus, the present application may take the form of a hardware-only embodiment, a software-only embodiment, or an embodiment having a combination of software and hardware. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

[0271] The present application is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present application. It should be understood that computer program instructions may be used to implement each process and / or each block in the flowcharts and / or block diagrams and combinations of processes and / or blocks in the flowcharts and / or block diagrams. These computer program instructions may be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or a processor of another programmable data processing device to generate a machine, such that the instructions executed by the processor of a computer or any other programmable data processing device generate an apparatus implementing a particular function in one or more processes of the flowcharts and / or one or more blocks of the block diagrams.

[0272] Alternatively, these computer program instructions may be stored in a computer readable memory capable of instructing a computer or another programmable data processing device to function in a particular manner to generate an artifact comprising an instruction apparatus, the instruction apparatus implementing a particular function(s) in one or more processes of the flowcharts and / or one or more blocks of the block diagrams.

[0273] Alternatively, these computer program instructions may be loaded into a computer or another programmable device such that a sequence of operations and steps are executed on the computer or another programmable data processing device, thereby generating a computer-implemented process. Thus, the instructions executing on the computer or another programmable device provide steps for implementing a particular function in one or more processes of the flowcharts and / or one or more blocks of the block diagrams.

[0274] It is obvious that a person skilled in the art can make various modifications and variations to the embodiments of the present application without departing from the scope of the present application. The present application is intended to cover these modifications and variations to the embodiments of the present application if they fall within the scope of the claims of the present application and are equivalent to the technology thereof.

Claims

1. receiving, by the first network function network element, a service subscription request from a third network function network element for the third network function network element to receive a first service provided by the second network function network element; sending a first message by the first network function network element to the second network function network element for the third network function network element to receive the first service provided by the second network function network element, the first message including a first address of the first network function network element and a second address of the third network function network element, the first address being usable for a message notifying the first network function network element that a subscription to the first service has changed, and the second address being usable by the third network function network element to receive the first service; receiving, by the second network function network element, the first message; providing, by the second network function network element, the first service to the third network function network element based on the second address; receiving, by the first network function network element, a third message informing the first network function network element that a subscription of the first service has changed, when the UE is handed over from the second network function network element to a fourth network function network element, the third message being sent by the fourth network function network element according to the first address; (c) how to subscribe to the service;

2. transmitting, by the second network function network element, the first address to the fourth network function network element; sending, by the fourth network function network element, the third message to the first address. The service subscription method according to claim 1.

3. 3. The service subscription method according to claim 1, further comprising the step of: allocating, by the first network function network element, a first notification correlation identifier, wherein the first message sent by the first network function network element to the second network function network element further includes the first notification correlation identifier.

4. The method of claim 3 , wherein the third message further includes the first notification correlation identifier.

5. the service subscription request is used to subscribe to a second service, the second service having the first service; the service subscription request further includes a second notification correlation identifier, the second notification correlation identifier being assigned by the third network function network element; The method further comprising: sending, by the first network function network element, a fifth message including the second notification correlation identifier to the second address of the third network function network element; Further comprising: The service subscription method according to claim 3 or 4, wherein the fifth message is used to notify that the second service has been changed.

6. receiving, by the fourth network function network element, the first address of the first network function network element from the second network function network element when the UE is handed over from the second network function network element to the fourth network function network element; The service subscription method according to any one of claims 1 to 5, further comprising:

7. receiving, by the fourth network function network element, the first address of the first network function network element from the second network function network element, 7. The service subscription method of claim 6, comprising receiving, by the fourth network function network element, context information from the second network function network element, the context information being generated based on subscription information of the first service, and the context information including the first address.

8. The method of claim 6 or 7, comprising the step of allocating, by the fourth network function network element, a new subscription correlation identifier for the subscription of the first service.

9. A program causing a computer to execute the service subscription method according to any one of claims 1 to 5.

10. A chip connected to a memory and configured to read and execute program instructions stored in the memory to perform the step of receiving at least the first address by the fourth network function network element in the service subscription method of any one of claims 6 to 8.

11. An information transmission device configured to perform the step of receiving at least the first address by the fourth network function network element in the service subscription method according to any one of claims 6 to 8.

12. receiving, by a second network function network element, a first message from a first network function network element for a third network function network element to receive a first service provided by a second network function network element, the first message being received by the second network function network element in response to the third network function network element receiving, by the first network function network element, a service subscription request for the third network function network element to receive the first service provided by the second network function network element, the first message being used by the first network function network element to subscribe to the first service on behalf of the third network function network element, the first message including a first address of the first network function network element and a second address of the third network function network element, the first address being usable to notify the first network function network element that a subscription to the first service has changed, and the second address being usable by the third network function network element to receive the first service; providing, by the second network function network element, the first service to the third network function network element based on the second address; sending the first address by the second network function network element to the fourth network function network element when the UE is handed over from the second network function network element to a fourth network function network element; (c) how to subscribe to the service;

13. transmitting, by the second network function network element, the first address to the fourth network function network element, 13. The service subscription method of claim 12, comprising transmitting, by the second network function network element, context information to the fourth network function network element, the context information being generated based on subscription information of the first service, and the context information including the first address.

14. The first message further includes a first notification correlation identifier assigned by the first network function network element, and the service subscription method includes: The method of claim 12 or 13, comprising the step of transmitting, by the second network function network element, the first notification correlation identifier to the fourth network function network element.

15. The first message further includes a second address of the third network function network element, and the service subscription method includes: The service subscription method according to any one of claims 12 to 14, comprising the step of providing, by the second network function network element, the first service to the third network function network element based on the second address.

16. A chip connected to a memory and configured to read and execute program instructions stored in said memory so as to implement a service subscription method according to any one of claims 12 to 15.

17. An information transmission device configured to perform a service subscription method according to any one of claims 12 to 15.

18. a transceiver configured to receive and transmit data; A processor configured to control the transceiver to receive a first message from a first network function network element for a third network function network element to receive a first service provided by a second network function network element, the first message being received in response to the third network function network element receiving, from the first network function network element, a service subscription request for the third network function network element to receive the first service provided by the second network function network element, the first message being received by the first network function network element and a first message is used to subscribe to a first service on behalf of a third network function network element from a second network function network element, the first message including a first address of the first network function network element and a second address of the third network function network element, the first address being usable to notify the first network function network element that the subscription to the first service has changed, the second address being usable by the third network function network element to receive the first service, and providing the first service to the third network function network element based on the second address; a processor, the processor being further configured to: send the first address to the fourth network function network element when a UE is handed over from the second network function network element to a fourth network function network element; A second network function network element comprising:

19. The processor is configured to control the transceiver to transmit the first address to the fourth network function network element, 20. The second network function network element of claim 18, further comprising: the processor configured to control the transceiver to transmit context information to the fourth network function network element, the context information being generated based on subscription information of the first service, and the context information including the first address.

20. 20. The second network function network element of claim 18, wherein the first message further includes a first notification correlation identifier assigned by the first network function network element, and the processor is further configured to control the transceiver to transmit the first notification correlation identifier to the fourth network function network element.

21. 20. The second network function network element of claim 18, wherein the first message further includes a second address of the third network function network element, and the processor is further configured to provide the first service to the third network function network element based on the second address.

22. 1. A communication system comprising: A second network function network element according to any one of claims 18 to 21; the fourth network function network element; Equipped with The fourth network function network element, a transceiver configured to receive and transmit data; a processor configured to control the transceiver to receive the first address of the first network function network element from the second network function network element when the UE is handed over from the second network function network element to the fourth network function network element, the processor is further configured to control the transceiver to send a third message to the first address to notify the first network function network element that the first service has changed, the first service being subscribed by the first network function network element on behalf of the third network function network element, and the first service being received by the third network function network element via a second address of the third network function network element; Equipped with Communication systems.

23. 23. The communications system of claim 22, wherein the processor of the fourth network function network element is configured to control the transceiver to receive context information from the second network function network element, the context information being generated based on subscription information of the first service, and the context information including the first address.

24. 24. The communication system of claim 22 or 23, wherein the processor of the fourth network function network element is further configured to assign a new subscription correlation identifier for the first service subscription.

25. The communication system of any one of claims 22 to 24, wherein the third message further comprises an updated subscription correlation identifier.

26. A communication system according to claim 25, further comprising a second network function network element according to any one of claims 18 to 21.

Images