RU2783811C2 - Method for subscription to services and device - Google Patents

Abstract

FIELD: communication.

SUBSTANCE: invention relates to the field of communication technologies, namely to a method for subscription to services and a device. The first network element of a network function transmits the first message to the second element of the network function to subscribe to the first service the third network element of the network function in the second network element of the network function, where the first message contains the first address, and the first address is an address of the first network element of the network function. The first network element of the network function receives the third message, using the first address, and finds out, based on the third message, that the first service was changed. According to this method, the first network element of the network function transmits the address of the first network element of the network function to the second network element of the network function. Therefore, when the first service is changed, the first network element of the network function can receive a notification. Thus, a mechanism for information about a change in a service is improved, so a procedure of subscription to services can be relatively completed, and no interrupt is called.

EFFECT: provision of a mechanism allowing a service provider to inform a service subscriber about a change in the service.

82 cl, 10 dwg

Description

The field of technology to which the invention belongs

The present application relates to the field of communication technologies and, in particular, to a method for subscribing to services and a device.

State of the art

5th generation (5G) systems support deployment to allow connections and data services. In the 5G system, the network elements of the network function in the control plane can interact with each other based on services. A typical service among the services provided by the network elements of the network function is the event exposure service. The basic process of implementing a service is as follows: when subscribing to a required service provided by the service provider, the service subscriber provides the service provider with an address to receive an event, and after determining that the requested event that the service subscriber subscribes to can be provided, the service provider notifies the required event to the event receiving address.

In practice, the status of a service or a service subscription (namely, a subscription attribute) changes after a user's subscription changes, network policy changes, network capabilities change, and the like. For example, due to a change in the user's subscription, an event that was initially allowed to be controlled can no longer be controlled and control needs to be cancelled; or due to a change in network capabilities, an event that was initially allowed to be controlled can no longer be controlled and control must be suspended. However, in the existing service subscription procedure, communication between devices in the event of a service status change or service subscription is not improved and no appropriate mechanism is formulated to allow the service provider to notify the service subscriber of the service change. Therefore, the service subscription procedure is imperfect and the service subscription procedure may be interrupted.

Disclosure of the essence of the invention

The present application provides a method and apparatus for subscribing to services in order to provide a mechanism for reporting a service change.

According to the first approach, the present application provides a service subscription method comprising the steps of:

transmitting, by means of the first network function network element, a first message to the second network function element to subscribe to the first service of the third network function network element from the second network function network element, where the first message contains the first address; and receiving, by means of the first network function network element, the third message using the first address, and knowing based on the third message that the first service has been changed, the first address being the address of the first network function network element.

According to this method, the first network function network element passes the address of the first network function network element to the second network function network element. Therefore, when the first service is changed, the first network element of the network function can receive notification that the service has been changed. Thus, the service change reporting mechanism is improved so that the service subscription procedure can be relatively completed and no interruption is caused.

In an exemplary implementation, before transmitting the first message to the second network function network element, the first network function network element receives a second message from the third network function network element, where the second message is used to subscribe to the second service, the second message contains the second address, and the second address is the address of the third network element. network function. The method further comprises: determining, by means of the first network function network element, based on the second service, the first service to be subscribed to from the second network function network element, where the first message further comprises a second address used by the second network function network element, to provide the first service to the third network element of the network function.

According to this method, the first network function network element can determine the first service based on the second message, so that the first service can be subscribed from the second network function network element.

In an exemplary implementation, based on the third message and having learned that the first service has been changed, the first network function network element will send a fifth message to the second address of the third network function network element, where the fifth message is used to notify that the second service has been changed. Thus, the third network function network element can know that the service subscribed to by the third network function network element has been changed.

In an exemplary implementation, the first message further comprises command information, and the command information is used to command to receive, using the first address, a message notifying that the first service has been changed. Thus, upon 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.

In an exemplary implementation, after the first network function network element transmits the first message to the second network function network element, the method further comprises: receiving, via the first network function network element, a second subscription correlation identifier from the second network function network element, where the second subscription correlation identifier is an identifier assigned by the second network element of the network function to the subscription to the first service. The third message further contains a second subscription correlation identifier. Recognizing by the first network function network element based on the third message that the first service has been changed comprises: recognizing by the first network function network element based on the second subscription correlation identifier that the first service has been changed.

According to this method, the first network element of the network function can know for sure that the first service has been changed.

In an exemplary implementation, 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 the first subscription correlation identifier to subscribe to the second service, and transmits the first subscription correlation identifier to the third network function network element. The transmission by the first network function network element of the fifth message to the second address of the third network function network element comprises the step of: transmitting by means of the first network function network element the fifth message containing the first correlation identifier of the subscription to the second address of the third network function network element.

In an exemplary implementation, before the first network function network element transmits the first message to the second network function network element, the method further comprises: assigning, by means of the first network function network element, a first notification correlation identifier; and transmitting, by means of the first network function network element, the first message to the second network function network element, comprising: transmitting, by means of the first network function network element, a first message containing the first subscription 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 comprises a first notification correlation identifier. Knowing based on the third message and by the first network function network element that the first service has been changed comprises the step of: knowing by the first network function network element based on the first subscription correlation identifier in the third message that the first service has been changed.

According to this method, the first network element of the network function can positively identify that the first service has been changed.

In an exemplary implementation, the second message further comprises a second notification correlation identifier and the second notification correlation identifier is assigned by the third network element of the network function. The transmission by the first network function network element of the fifth message to the second address of the third network function network element comprises the step of: transmitting by means of the first network function network element the fifth message containing the second correlation identifier of the subscription to the second address of the third network function network element.

In a possible implementation, changing the first service means that the status of the first service has been changed and/or the subscription to the first service has been changed. In an exemplary implementation, changing a subscription comprises changing a subscription correlation identifier or changing the event reporting information and the event reporting information comprises at least one of the following: changing the event reporting mode, changing the maximum number of event reports, or changing the maximum reporting duration about the event.

According to this method, the specific case in which the first service is changed can be accurately determined.

In an exemplary implementation, when changing the first service means that the status has been changed, the third message further contains the first status information. The first status information is a paused state, a restored state, a canceled state, or a deleted state. Thus, the first network element of the network function can learn about the current status of the subscribed service.

In a possible implementation, the third message further comprises an event identifier and/or user identification corresponding to the first status information. Thus, the first network element of the network function can learn about the status change event or the user corresponding to the status change event.

In an exemplary implementation, when changing the first service means that the subscription has been changed, the third message further contains a subscription attribute for the changed subscription to the first service. Thus, the first network function network element and the third network function network element can learn about the current subscription attribute for the subscribed service.

In an exemplary implementation, when the subscription change is a subscription correlation ID change, the subscription attribute for the changed subscription to the first service is the updated subscription correlation ID. Thus, the first network function network element and the third network function network element can exactly the particular subscription attribute for the modified subscription.

In an exemplary implementation, when the subscription change is an event reporting information change, the subscription attribute for the first service subscription changed contains at least one of: an updated event message mode, an updated maximum number of event messages, or an updated maximum event message duration. Thus, the first network element of the network function can know exactly the specific subscription attribute for the modified subscription.

In an exemplary implementation, the reception by the first network function network element of the third message using the first address can be performed in the following two ways. According to the first method, the first network function network element receives a third message from the second network function network element using the first address. According to the second method, the first network function network element receives a third message from the fourth network function network element using the first address, wherein the second network function network element requests the first service for the third network function network element from the fourth network function network element.

According to this method, the first network element of the network function, using the first address, can successfully receive a message notifying that the first service has been changed.

In an exemplary implementation, the command information is a third set of event identifiers, where the third set of event identifiers contains a status change event identifier and/or a subscription change event identifier. Thus, another network function network element can be triggered by a specific event to detect if the first service has been changed.

In an exemplary implementation, the subscription change event identifier comprises the subscription correlation identifier change event identifier or the event reporting information change event identifier. Thus, the discovery event that the first service has been changed can be accurately determined.

In a possible implementation, the third message further comprises at least one event identifier in the third set of event identifiers. Thus, the first network function network element can identify a specific change to the first service.

According to the second approach, an embodiment of the present application provides a service subscription method, and said method comprises the steps of:

receiving, by means of the second network function network element, a first message from the first network function element, where the first message is used by the first network function network element to subscribe to the first service for the third network function network element from the second network function network element, the first message containing the first address and the first the address is the address of the first network element of the network function; and transmitting, via 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 been changed.

According to this method, the first network function network element passes the address of the first network function network element to the second network function network element. Therefore, when the first service is changed, the first network element of the network function can receive notification that the service has been changed. Thus, the service change reporting mechanism is improved so that the service subscription procedure can be relatively completed and no interruption is caused.

In an exemplary implementation, the first message contains a second address, the second address being the address of the third network function network element and the second network function network element providing the first service to the third network function network element based on the second address. Thus, when the first service is normal, the second network function network element may normally notify the third network function network element of the requested event.

In an exemplary implementation, the first message further comprises command information, and the command information is used to command to receive, using the first address, a message notifying that the first service has been changed. Thus, upon detecting that the first service has been changed, the second network function network element sends a message to the first address indicating that the first service has been changed.

In an exemplary implementation, after receiving the first message from the first network function network element, the second network function network element assigns a second subscription correlation identifier to the subscription to the first service. The transmission by the second network function network element of the third message to the first address of the first network function network element comprises the step of: adding a second subscription correlation identifier to the third message by means of the second network function network element and transmitting the third message to the first address of the first network function network element. Thus, the first network function network element can know, using the second subscription correlation identifier in the third message, that the first service has been changed.

In an exemplary implementation, the first message further comprises a first notification correlation identifier; and transmitting, by means of the second network function network element, a third message to the first address of the first network function network element, comprising: transmitting, by means of the second network function network element, a third message containing the first notification correlation identifier to the first address of the first network function network element. Thus, the first network function network element, using the first subscription correlation identifier in the third message, can know that the first service has been changed.

In a possible implementation, changing the first service means that the status of the first service has been changed and/or the subscription to the first service has been changed. In a possible implementation, changing a subscription comprises changing a subscription correlation identifier or changing the event reporting information, and changing the event reporting information comprises at least one of the following: changing the event reporting mode, changing the maximum number of event messages, or changing the maximum duration event messages.

According to this method, the specific case in which the first service is changed can be accurately determined.

In an exemplary implementation, when changing the first service means that the status has been changed, the third message further contains the first status information. The first status information is a paused state, a restored state, a canceled state, or a deleted state. Thus, the first network element of the network function can learn about the current status of the subscribed service.

In a possible implementation, the third message further contains an event identifier and/or user identification corresponding to the first status information. Thus, the first network element of the network function can learn about the status change event or the user corresponding to the status change event.

In an exemplary implementation, when changing the first service means that the subscription has been changed, the third message further contains a subscription attribute for the changed subscription to the first service. Thus, the first network element of the network function can learn about the current subscription attribute for the subscribed service.

In an exemplary implementation, when the subscription change is a subscription correlation ID change, the subscription attribute for the changed subscription to the first service is the updated subscription correlation ID. Thus, the first network element of the network function can know exactly the specific subscription attribute for the modified subscription.

In an exemplary implementation, when the subscription change is an event reporting information change, the subscription attribute for the changed subscription to the first service contains at least one of the following: an updated event message mode, an updated maximum number of event messages, or an updated maximum duration of event messages. . Thus, the first network element of the network function can know exactly the specific subscription attribute for the modified subscription.

In an exemplary implementation, the command information is a third set of event identifiers, where the third set of event identifiers contains a status change event identifier and/or a subscription change event identifier. Thus, the second network function network element can be triggered by a particular event to detect if the first service has been changed.

In an exemplary implementation, the subscription change event identifier comprises the subscription correlation identifier change event identifier or the event reporting information change event identifier. Thus, the second network element of the network function can accurately determine the event of detecting that the first service has been changed.

In a possible implementation, the third message further comprises at least one event identifier in the third set of event identifiers. Thus, the first network element of the network function can identify a particular change of the first service.

In an exemplary implementation, the second network function network element requests a first service from the fourth network function network element and passes the first address to the fourth network function network element. Thus, after the UE reselects the fourth network function network element as the UE moves, the fourth network function network element can send a message to the first address notifying that the first network service has been changed.

According to the third approach, the present application further provides the first network function network element and the first network function network element has the function of implementing the behavior of the first network function network element in the above embodiment of the method. The function may be implemented in hardware, or may be implemented in hardware running corresponding software. The hardware or software contains one or more modules corresponding to the above function.

In an exemplary implementation, the structure of the first network element of the network function comprises a transmitting unit, a receiving unit, and a processing unit, and in the example of the method presented above, the units may perform the respective functions. For details, see the detailed descriptions of the exemplary method. The details are not re-described here.

In an exemplary implementation, the structure of the first network function element comprises a transceiver and a processor, and optionally further comprises a memory. The transceiver is configured to receive and transmit data and is configured to communicate and interact with another device in the communication system. The processor is configured to support the first network element of the network function while executing the corresponding function in the method described above. The memory is coupled to the processor and the memory stores the program instructions and data needed for the first network device of the network function.

According to the fourth approach, the present application further provides a second network function network element, and the second network function network element has the function of implementing the behavior of the second network function network element in the above embodiment of the method. The function may be implemented in hardware, or may be implemented in hardware running corresponding software. The hardware or software contains one or more modules corresponding to the above function.

In an exemplary implementation, the structure of the second network function network element comprises a receiving block, a transmitting block, and a processing block, and in the example of the method presented above, the blocks may perform the respective functions. For details, see the detailed descriptions of the exemplary method. The details are not re-described here.

In an exemplary implementation, the structure of the second network function element comprises a transceiver and a processor, and optionally further comprises a memory. The transceiver is configured to receive and transmit data and is configured to communicate and interact with another device in the communication system. The processor is configured to support the second network element of the network function when performing the corresponding function in the method described above. The memory is connected to the processor and the memory stores program instructions and data required for the second network device of the network function.

According to the fifth approach, the present application further provides a system in which the system comprises a first network function network element and the first network function network element can be configured to implement the steps performed by the first network function network element in the first approach and in any method of the first approach. . In an exemplary implementation, the system may further comprise a second network function network element and the second network function network element may be configured to implement the steps performed by the second network function network element in the first approach in any method of the first approach. In an exemplary implementation, the system may further comprise another device such as a third network function network element that communicates with the first network function network element and/or with the second network element in the solution provided in this embodiment of the present application.

According to the sixth approach, the present application further provides a system in which the system comprises a second network function network element and the second network function network element can be configured to implement the steps performed by the second network function network element in the second approach and in any method of the second approach. . In an exemplary implementation, the system may further comprise a first network function network element and the first network function network element may be configured to implement the steps performed by the first network function network element in the second approach and in any method of the second approach. In an exemplary implementation, the system may further comprise another device such as a third network function network element that communicates with the first network function network element and/or with the second network element in the solution provided in this embodiment of the present application.

According to the seventh approach, the present application further provides a computer storage medium, where the computer storage medium stores computer-executable instructions and computer-executable instructions that cause, when executed by the computer, any of the above methods to be executed by the computer.

According to the eighth approach, the present application further provides a computer program product containing instructions. When a computer program product is executed on a computer, the computer performs any of the above methods.

In accordance with the ninth approach, the present application further provides a chip, where the chip is connected to the memory and is capable of reading and executing program instructions stored in the memory to implement the method according to any of the above methods.

Brief description of the drawings

Fig. 1 is a schematic architecture of a communication system according to the present application.

Fig. 2 is a flowchart of the operation sequence of the method of subscribing to services corresponding to the present application;

Fig. 3 is an exemplary flowchart of the service subscription method of the present application;

Fig. 4A and 4B are an exemplary flowchart of another service subscription method according to the present application;

Fig. 5 is a flowchart of another service subscription method according to the present application;

Fig. 6 is a schematic structural device corresponding to the present application;

Fig. 7 - schematic structural of another device corresponding to the present application;

Fig. 8 is a schematic block diagram of the first network element of the network function corresponding to the present application; and

Fig. 9 is a block diagram of the second network element of the network function according to the present application.

Implementation of the invention

The following is an additional detailed description of the present application with reference to the accompanying drawings.

Embodiments of the present application provide a method and apparatus for subscribing to services to provide a mechanism for reporting a change in a service. The method and device according to the present application are based on the same concept of the invention. Since the principle of solving the problem for the method and apparatus are similar, mutual reference may be made to implementations of apparatus and method, and repetitive details will not be described.

The following describes some of the terms used in the application to help those skilled in the art better understand the present application.

(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, support the event demonstration service, and can perform communication and interaction based on the event demonstration service. Specifically, in embodiments 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 control network element, a policy management function network element, and the like. the policy control function element may be a PCF (policy control function). The second network function network element may be, but is not limited to, a core network access and mobility control network element, a session management function network element, and the like. For example, the core network access and mobility control network element may be an AMF. (core access and mobility management function, core network access and mobility management function), and the network element of the session management function may be SMF (session management function, session management function). The third network element of the network function may be, but is not limited to, a network exposure function network element, for example, may be NEF (network exposure function, network exposure function). For example, when the first network function network element is a UDM, the second network function network element can be an AMF, respectively. As another example, when the first network function network element is an SMF, the second network function network element may be an SMF, respectively. In the examples with three network function NEs, the names of the NEs are just examples. The names of the NEs may be different in future communications. This is not limited in the present application.

(2) In the description of this application, words such as "first" and "second" are used merely for distinction and description and should not be understood as an indication or implied sense of relative importance, or as an indication or implied order.

(3) The term "and/or" describes a relationship relationship for describing related objects and indicates that there may be three relationships. For example, A and/or B can represent the following three cases: only A exists, A and B exist simultaneously, and only B exists. The symbol "/" usually indicates an "or" relationship between related entities.

In order to more clearly describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings, the following describes in detail the method and apparatus for obtaining service data presented in the embodiments of the present application.

An exemplary communication system architecture to which the service subscription method presented in the embodiments of the present application can be applied may comprise a Network Demonstration Function Network Element, a Policy Management Function Network Element, a Data Control Network Element, an Application Function Network Element, an Access Function Network Element to the core network and mobility management, a session management function network element, a terminal device, an access network device, a user plane function network element, and a communication network. In FIG. 1 shows a possible example of a communication system architecture, which specifically comprises: NEF network element, PCF network element, UDM network element, AF network element, AMF network element, SMF network element, UE, access network device (AN), network element UPF and data network (data network, DN). The AMF network element can connect to the terminal device through the N1 interface, the AMF can connect to the AN device through the N2 interface, the AN device can connect to the UPF through the N3 interface, the SMF can connect to the UPF through the N4 interface, and the UPF can connect to the DN through the N6 interface. The name of the interface is only exemplary and is for description only. In this embodiment of the present application, it is not particularly limited. It should be understood that this embodiment of the present application is not limited to the communication system shown in FIG. 1. The NE names shown in FIG. 1 are used merely as examples for the description herein and are not used as limitations for the network elements contained in the architecture of a communication system to which the method described in this application is applicable. The function of each network element or device in the communication system is described in detail below.

The terminal may also be referred to as a user equipment (user equipment, UE), a mobile station (mobile station, MS), a mobile terminal (mobile terminal, MT), etc., and is a device that provides the user with the ability to perform voice / data transmission. For example, a terminal device may include a portable device with a wireless communication function, an on-board device, and the like. internet device, MID), wearable device, virtual reality device (virtual reality, VR), augmented reality device (augmented reality, AR), wireless terminal for industrial control, wireless terminal for self-driving ), a wireless terminal in remote medical surgery, a wireless terminal in a smart grid (smart grid), a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in smart home (smart home), etc. On fig. 1, the terminal is shown using the UE as an example, and the nature of the terminal is not limited.

The radio access network may be an access network (AN) shown in FIG. 1 and provide a wireless access service to the terminal device. A network access device is a device in a communications network that allows a terminal device to access a wireless network. A network access device is a node in a radio access network and may also be referred to as a base station, or may also be referred to as a node (or a radio access network (RAN) device. Currently, for example, the network access device is a gNB, a transmission receiving point ( transmission reception point, TRP), deployed NodeB (evolved Node B, eNB), radio network controller (radio network controller, RNC), NodeB (Node B, NB), base station controller (BSC), base transceiver station ( base transceiver station, BTS), a home base station (for example, a home evolved NodeB (home evolved NodeB or home Node B, HNB)), a baseband unit (BBU), or a Wi-Fi access point ( access point, AP) (wireless fidelity, Wi-Fi).

A data network such as a data network (DN) shown in FIG. 1 may be the Internet, an IP Multimedia Service (IMS) network, a regional network, namely a local area network such as a mobile edge computing (MEC) network, and the like. data contains an application server and the application server provides services to the terminal device by transmitting data using the terminal device.

The core network is configured to allow a tag to access a DN that can implement a tag's service. The functions of the network elements in the core network are described below.

The network element of the core network access and mobility control function may be configured to control access and mobility of the tag. In actual application, the network element of the core network and mobility access control function contains the mobility management function in the mobility management entity (MME) in the network structure of the long-term evolution (LTE) system and contains the access control function. Specifically, the core network access control and mobility control network element may be responsible for terminal registration, mobility management, tracking area update procedure, availability detection, session control network element selection, mobility state change control, and the like. For example, in In the 5G system, the core access and mobility management function network element may be an AMF (core access and mobility management function) network element, for example, as shown in FIG. 1. In future communications, such as in a 6G system, the core network access control and mobility control network element may remain an AMF network element or have a different name. This is not limited in the present application. When the network element of the core network access control and mobility control function is an AMF network element, the AMF can provide the Namf service.

The session management function network element may be configured to be responsible for session management (including session establishment, modification, and disconnection) of the end device, selection and reselection of the function network element in the user plane, assignment of Internet protocol addresses, IP) for a terminal device, quality of service (QoS), and the like. For example, in a 5G system, a session management function network element may be, for example, an SMF (session management function) network element as shown in FIG. 1. In future communications, such as in 6G, the session management function network element may remain an SMF network element or have a different name. This is not limited in the present application. When the session management function network element is an SMF network element, the SMF may provide the Nsmf service.

The policy control function network element may be configured to be responsible for making policy control decisions and providing functions such as service and application based data flow discovery, throughput control, QoS, and flow based charging control. For example, in a 5G system, a policy control function network element may be, for example, a PCF (policy control function) network element as shown in FIG. 1. In future communication, such as in a 6G system, the policy control function network element may remain a PCF network element or have a different name. This is not limited in the present application. When the policy control function network element is a PCF network element, the PCF may provide the Npcf service.

The main function of the application function network element is to interact with the 3rd generation partnership project (3GPP) core network to provide a service such as influencing service flow routing, network access capability demonstration, policy control, etc. For example, in a 5G system, an application function network element may be, for example, an AF (application function) network element as shown in FIG. 1. In future communication, such as in a 6G system, the network element of the session control application function may remain an AF network element or have a different name. This is not limited in the present application. When the application function network element is an AF network element, the AF network element may provide the Naf service.

The data network element may be configured to manage subscription data of a terminal device, registration information associated with a terminal device, and the like. For example, in a 5G system, the network data control element may be, for example, a unified data management, UDM), as shown in FIG. 1. In future communication, such as in a 6G system, the data control network element may remain a UDM network element or have a different name. This is not limited in the present application. When the entity network element is a UDM network element, the UDM network element may provide a Nudm service.

The Network Demonstration Function Network Element may be configured to allow the 3GPP to securely provide the network capabilities of a third party AF services (eg, a Services Capability Server (SCS) or an Application Server (AS)). For example, in a 5G system, the network exposure function network element may be, for example, NEF ((network exposure function), as shown in Fig. 1. In future communication, for example, in a 6G system, the network exposure function network element may remain a NEF network element or have another name.It is not limited in the present application.When the network demonstration function network element is NEF, the NEF may provide another network function network element with the Nnef service.

Each of the above network elements in the core network may also be referred to as a function entity and may be a network element running on dedicated hardware, or may be a software variant running on dedicated hardware, or a virtual function on an appropriate platform. For example, the virtualization platform may be a cloud platform.

It should be noted that the communication system architecture shown in FIG. 1 is not limited to the presence of only network elements shown in the drawing, and may additionally contain another device not shown in the drawing. The details are not described in this application.

It should be noted that the form of distribution of network elements in the core network in this embodiment of the present application is not limited. The distribution shape shown in Fig. 1 is merely an example and does not create limitations for the present application.

For ease of description in the following, the network element shown in FIG. 1 is used as an example for description in this application, and network element XX is directly referred to as XX. It should be understood that the names of all network elements in this application are used simply as examples and in a future communication system they may also be referred to with other names or the network element in this application may be replaced by another entity or device that in a future communication system has the same function. . This is not limited in the present application. A uniform description is presented here and is not repeated in the following content.

It should be noted that the communication system shown in FIG. 1 does not constitute a limitation on the communication system in which the embodiments of the present application may be applicable. The communication system architecture shown in FIG. 1 is the 5G system architecture. Alternatively, the method presented in the embodiments of this application may further be applicable to various future communication systems such as 6G or other communication network.

An embodiment of this application presents a service subscription method that can be applied to the communication system shown in FIG. 1. As shown in FIG. 2, the specific procedure for implementing the method comprises the following steps.

Step 201: The first network function network element transmits the first message to the second network function network element so as to subscribe to the first service for the third network function network element from the second network function network element, where the first message contains the first address and the first address is the address the first network element of the network function. The first address (an address that may also be referred to as a Notification Endpoint) may be at least one of the following or a combination of the following: the Internet protocol (IP) address of the first network element of the network function, the port number of the first network network function element, uniform resource locator (URL), etc.

The first network function network element transmits the first message to the second network function network element so as to subscribe to the first service provided to the third network function network element from the second network function network element, that is, the first network function network element subscribes to the first service from the name of the third network element of the network function.

In the communication system shown in FIG. 1, the first network function network element may be a UDM, PCF, or the like. In the communication system shown in FIG. 1, the second network function network element may be an AMF, an SMF, or the like. In the communication system shown in FIG. 1, the third network function network element may be a NEF, or the like. This is not limited in the present application.

In an exemplary implementation, before the first network function network element transmits the first message to the second network function network element, the method further comprises the following. The first network element of the network function assigns the first address a first notification correlation identifier. That is, the transmission by the first network function network element of the first message to the second network function network element comprises the following. The first network function network element transmits the first message containing the first notification correlation identifier to the second network function network element, so that when a message subsequently fed back using another network element carries the first notification correlation identifier, it could be known that the message is related to the subscription to the first service.

Alternatively, the first message further comprises command information, and the command information is used to issue a command to receive, using the first address, a message notifying that the first service has been changed.

In an embodiment, the command information may only be a command information value, or may be a set of event IDs (referred to as the third set of event IDs in this embodiment of the present application). When the command information is the third set of event identifiers, the third set of event identifiers comprises a status change event identifier, a subscription change event identifier, and/or the like. Alternatively, the subscription change event identifier may comprise a subscription correlation identifier change event identifier, an information change event identifier , reporting an event, etc.

In the embodiment, when the first message does not contain the above command information, after receiving the first message, the second network element of the network function detects that the first message contains more than one address compared to the prior art, and the address is not associated with any identifier. developments. That is, when the first address is present and the first address is not associated with any event identifier, it can be automatically identified that the first network function network element, using the first address, receives a message notifying that the first service has been changed. That is, in this scenario, the first address has the following function: implicitly instructs to receive, using the first address, a message notifying that the first service has been changed. Of course, in this scenario, when the second network function network element detects the first address, the second network function network element may alternatively, in any other form, for example, using the currently configured mechanism, identify that the message notifying that the first service has been changed, can be received using the first address. This is not limited in the present application.

In an exemplary implementation, changing the first service means that the status of the first service has been changed and/or the subscription to the first service (namely, the subscription to the first service) has been changed. The change in the status of the first service may be a change in 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 restored state, a canceled state, or a deleted state. The change in the subscription to the first service may be a change in the attribute of the subscription. For example, a subscription change may include a change in a subscription's correlation identifier or a change in information reporting an event. Changing the event reporting information comprises at least one of the following: changing the event reporting mode, changing the maximum number of event messages, or changing the maximum duration of event messages.

In an exemplary implementation, before the first network function network element transmits the first message to the second network function network element, the first network function network element further performs the following. The first network function network element receives a second message from the third network function network element, where the second network function network element is used to subscribe to the second service. In this case, the first message transmitted by the third network function network element to the first network function network element may be considered as a start message received by the first network function network element, and therefore the first network function network element may be triggered to perform step 201.

In an exemplary implementation, after the first network function network element receives the second message, the method further comprises the following. The first network function network element, based on the second service, determines the first service to be subscribed to from the second network function network element. Alternatively, the message for subscribing to the first service (namely, the first message) contains a first set of event identifiers, the second message contains a second set of event identifiers, the set of event identifiers corresponding to events to be provided by the second network element of the network function, and a specific set event IDs is the first set of event IDs.

Specifically, the second message contains the second address, and the second address is the address of the third network element of the network function. Alternatively, the first message further comprises a second address such that the second network function element provides the first service to the third network element of the network message using the second address.

In an exemplary implementation, the second message further comprises a second notification correlation identifier and the second notification correlation identifier is assigned to the second address by the third network element of the network function.

Alternatively, 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 the first subscription correlation identifier for the subscription to the second service (namely, subscription to the second service), and transmits the first the correlation identifier of the subscription to the third network element of the network function. Alternatively, when the first network function network element transmits the first subscription correlation identifier, the first subscription correlation identifier may be transmitted in an event demonstration subscription response (Nnf_EventExposure_Subscribe Response) sent by the first network function network element to the third network function network element.

In an exemplary implementation, after the first network function network element transmits the first message to the second network function network element, the method further comprises the following. The first network function network element receives the second subscription correlation identifier from the second network function network element, where the second subscription correlation identifier is the subscription correlation identifier assigned by the second network function network element to the first service subscription (namely, the first service subscription) (i.e., if the message subsequently received by the first network function network element contains a second subscription correlation identifier, the first network function network element learns that the message is associated with a subscription to the first service).

Step 202: The first network function network element receives the third message using the first address.

In an exemplary implementation in which the first network function network element receives the third message using the first address, the following two cases may specifically be contained:

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

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 the first service for the third network function network element from the fourth network function network element.

Specifically, in case 1, after detecting that the first service has been changed (refer to the corresponding first service change description 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, as the network policy changes, the current status of the first service can be changed from normally running to suspended (Suspend) and from suspended to resumed (Resume). As another example, the subscription to the first service is canceled (Cancel), canceled (Delete), and the like, due to the network policy or the user's subscription. In case 2, three scenarios are possible. In the first scenario, since the UE is moving, for the network element serving the UE, control is transferred from the second network function network element to the 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 the first service subscription information, 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 into the context information) to the fourth network element of the network function. Further, upon detecting that the first service has been changed (eg, the fourth network function network element assigns a new subscription correlation identifier to the first service subscription), the fourth network function network element transmits a third message to the first network function network element. In the second scenario, since the UE is moving, for the network element serving the UE, control is transferred 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 the function of the second network function network element. In this scenario, the second network function network element generates context information based on the first service subscription information, 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, using the function of the fourth network service network element, that the first service has been changed, the fourth network function network element transmits a third message to the first network function network element. In the third scenario, when the second network function network element cannot provide the first service, in any case, the second network function network element sends a fourth message to another network function network element, namely the fourth network function network element. The fourth message contains the first address used to subscribe to the first service. Thus, upon detecting that the first service has been changed, the fourth network function network element transmits a third message to the first network function network element.

In an embodiment, when the first message contains command information and the command information is a third set of event identifiers, the third message further comprises at least one event identifier in the third set of event identifiers such that the first network function network element identifies a particular change of the first service.

Step 203: The first network function network element learns based on the third message that the first service has been changed.

In an exemplary implementation, after the first network function network element learns based on the third message that the first service has been changed, the method further comprises the following. The first network function network element sends a fifth message to the second address of the third network function network element, where the fifth message is used to notify that the second service has been changed.

In a possible implementation, the transmission by the first network function network element of the fifth message to the second address of the third network function network element comprises the following. The first network function network element transmits a fifth message containing the first subscription correlation identifier mentioned in step 201 to the second address of the third network function network element.

In an exemplary implementation, the third message further comprises the second subscription correlation identifier mentioned in step 201. That the first network function network element knows based on the third message that the first service has been changed contains the following. The first network function network element, based on the second subscription correlation identifier in the third message, knows that the first service has been changed.

In an embodiment, the third message received by the first network function network element using the first address further comprises the first notification correlation identifier mentioned in step 201. That the first network function network element learns based on the third message that the first service has been changed , contains the following. The first network function network element, based on the first notification correlation identifier in the third message, knows that the first service has been changed (that is, if the message subsequently received by the first network function network element contains the first notification correlation identifier, the first network function network element learns that the message is associated with a subscription to the first service).

In an exemplary implementation, the transmission by the first network function network element of the fifth message to the second address of the third network function network element comprises the following. The first network function network element transmits a fifth message containing the second notification correlation identifier mentioned in step 201 to the second address of the third network function network element.

Alternatively, during a particular implementation, when the first service change is the status change mentioned in step 201, the third message further contains the first status information. The fifth message further contains second status information. The first status information or the second status information may be a paused state, a restored state, a canceled state, or a deleted state, or the like. Alternatively, the third message further comprises an event ID and/or user identification corresponding to the first status information.

Alternatively, when the first service change is the subscription change mentioned in step 201, the third message further includes a subscription attribute for the changed subscription to the first service. The fifth message further contains a subscription attribute for the modified subscription to the second service. Specifically, when the subscription change is a subscription correlation ID change, the subscription attribute for the changed subscription to the first service or the subscription attribute for the changed subscription to the second service is the updated subscription correlation ID. When the subscription change is an event reporting information change, the subscription attribute for the changed subscription to the first service or the subscription attribute for the changed subscription to the second service may comprise at least one of an updated event message mode, an updated maximum number of event messages, or updated maximum duration of event messages.

According to the service subscription method presented in this embodiment of the present application, the first network function network element transmits a first message to the second network function network element to subscribe to the first service of the third network function network element from the second network function network element, where the first message contains the first address and the first address is the address of the first network element of the network function; and the first network function network element receives the third message using the first address and learns based on the third message that the first service has been changed. According to this method, the first network function network element passes the address of the first network function network element to the second network function network element. Therefore, when the first service is changed, the first network element of the network function can receive notification that the service has been changed. Thus, the service change reporting mechanism is improved, and therefore, the service subscription procedure can be relatively completed and no interruption is caused.

The service subscription method presented in the embodiments of the present application is described in detail below in the embodiments shown in FIG. 3, 4A and 4B and 5 based on the embodiment shown in FIG. 2 using specific examples.

As shown in FIG. 3, an embodiment of this application further presents an example of a service subscription method. In this example, the first network function NE is UDM, the second network function NE is AMF, and the third network function NE is NEF. The NEF subscribes to a service (also referred to as a subscription event notification service) from the UDM, and the UDM additionally subscribes to a service for the NEF from the AMF. Specifically, the exemplary procedure may include the following steps.

Step 301: NEF receives trigger information. Specifically, after the NEF receives the start information, the NEF is started to perform the service subscription from the UDM.

Alternatively, the start information may come from another network function network element, such as an AF. The trigger information may alternatively be obtained by triggering the NEF's internal trigger.

Step 302: The NEF sends a second message to the UDM, and the NEF subscribes to the second service from the UDM using the second message.

The second message contains the NEF address, namely the second address. So NEF receives the requested event using the second address. In an embodiment, the second message further comprises the second set of event identifiers (such as Event Id1) and the second notification correlation identifier (such as Notification Correlation ID) mentioned in the embodiment of FIG. 2. The second set of event IDs may include at least one event ID. The second Notification Correlation Identifier is used by NEF to correlate successively received Event Notifications (namely, the information in the successively received fifth message) with the pre-delivered Event Subscription (namely, the second service subscription information in the second message).

In an embodiment, the second message further comprises an external UE identifier (e.g., for a single UE), a UE group group identifier (e.g., for a group of UEs), or an indication of any UE (e.g., any UE parameter valid for all UEs in the active network). ) so that it can be determined from which second service it is ultimately provided.

In an exemplary implementation, the second message further comprises information reporting the event, and the information reporting the event comprises at least one of the event reporting mode, the maximum number of event messages, or the maximum duration of event messages. The event reporting mode may be a one-time message, a continuous message, a periodic message, and the like.

In an embodiment, the second message may be a Nudm_Event Exposure_Subscribe Request sent from the NEF to the UDM. At implementation time, the NEF sends a Hypertext Protocol Transfer Request (HTTP POST) to the UDM. The destination address of the request may be a uniform resource locator (URL), and the body of the HTTP POST message carries the above information, which may be included in the second message. The details are not re-described here.

Step 303: The UDM stores the information in the second message and assigns a first Subscription Correlation ID 1 to the second service subscription in the second message.

During a specific implementation, the UDM creates a resource to subscribe to the second service based on the information carried in the main body, generates a subscription id1 to the child resource identifier, and constructs a Uniform Resource Locator (URI) 1 for the created resource. URI 1 is formed by using the requested URI as the parent resource and then splicing it to the child resource identifier. Here, the subscription id 1 can be used as the subscription correlation ID 1 .

Step 304: The UDM sends a first message to the AMF, and the UDM subscribes to a second service from the AMF using the first message. The first message contains the address of the UDM, namely the first address.

Alternatively, the UDM, based on the second service, determines the first service to subscribe from the AMF. Specifically, the first message further comprises a first event ID set, the first event ID set is generated based on the second event ID set, the first event ID set is an event ID set in the second event ID set corresponding to events to be provided by the AMF, and the second the set of event identifiers is contained in the second message.

For example, after receiving a second message, the UDM first determines one or more events (namely, the second set of events corresponding to the second set of event IDs in this embodiment of this application) that are in the second set of events corresponding to the second set of event IDs in the second message, and to be provided by the AMF, and then performs step 304. That is, the first set of event IDs in the first message is specifically determined based on the second set of event IDs in the second message. For example, the first set of event IDs is part or all of the second set of event IDs.

Specifically, in addition to the first address, the first message further contains a second address, which is used by the AMF to provide the first service to the NEF. When the first service is changed, the UDM may, using the first address, receive a message notifying that the first service has been changed.

In an exemplary implementation, the first message further comprises command information, and the command information is used to command, using the first address, to receive a message notifying that the first service has been changed. Specifically, changing the first service means that the status of the first service has been changed and/or the subscription to the first service has been changed. The change in the status of the first service may be a change in 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 restored state, a canceled state, or a deleted state. The subscription change may be a subscription attribute change. For example, a subscription change includes a change in the subscription correlation ID or a change in the information containing the event message. Changing the event reporting information comprises at least one of: changing the event reporting mode, changing the maximum number of event messages, or changing the maximum duration of event messages, and the like. That is, any of the cases described above may indicate, that the first service has been changed.

In an embodiment, the command information may only be a value of the command information, or may be a set of event IDs (namely, a third set of event IDs). When the command information is the third set of event IDs, the third set of event IDs contains a status change event ID, a subscription change event ID, and/or the like. In this case, the command information can be considered as having a function of issuing a command to provide a special event. For example, the special event may be a status change event or a subscription change event. Alternatively, the subscription change event ID may comprise a subscription correlation ID change event ID or a change event ID of the event reporting information.

In an embodiment where the first message does not contain the command information described above, after receiving the first message, the AMF detects that the first message carries more than one address, as compared to the prior art. That is, when the first address is transmitted, the AMF automatically identifies that the UDM is receiving, using the first address, a message notifying that the first service has been changed. That is, in this scenario, the first address has the following function: implicitly commands, using the first address, to receive a message notifying that the first service has been changed. Of course, in this scenario, when the AMF detects the first address, the AMF may alternatively identify in any other form, such as using the currently configured mechanism, that a message notifying that the first service has been changed can be received using the first address. This is not limited in the present application.

In an embodiment, the first message may be a Namf_Event Exposure_Subscribe Request sent from the UDF to the AMF.

Step 305: After receiving the first message, the AMF stores the information in the first message and assigns a second Subscription Correlation ID 2 to the first service subscription in the first message.

During a particular implementation, the AMF creates a resource to subscribe to the first service based on the information carried in the main body, generates a subscription id1 to the child resource identifier, and constructs a Uniform Resource Locator (URI) 1 for the created resource. URI2 is formed by using the requested URI as the parent resource and then splicing it to the child resource identifier. Here, the subscription id 2 may be used as the subscription correlation ID 2 .

Step 306: The AMF sends a sixth message to the UDM, where the sixth message contains the subscription correlation ID 2.

In an embodiment, the sixth message may be an Event Exposure Subscribe Response (Namf_EventExposure_Subscribe Response) sent from the AMF to the UDM. At implementation time, the AMF sends a UDM HTTP Response, where the HTTP Response carries a Status Code of "201 Created" and a header of "Location". The Location header carries a URI2.

Step 307: The UDM sends back a seventh message to the NEF, where the seventh message contains the subscription correlation ID 1.

In an embodiment, the seventh message may be an Event Exposure Subscribe Response (Nudm_ EventExposure_Subscribe Response) sent from the UDM to the NEF. At implementation time, the UDM sends back a NEF HTTP Response, where the HTTP Response carries a Status Code of "201 Created" and a header of "Location". The Location header carries the URI1.

Step 308: Upon detecting an event to be provided to the NEF, the AMF provides the first service to the NEF.

Step 309: When it is detected that the first service has been changed, the AMF performs step 310.

Alternatively, when the AMF that is serving the UE needs reselection because the UE is moving, the AMF transmits the information received in step 304 to another AMF (namely, the reselected AMF for the UE). In this case, the other AMF detects that the first service has been changed, that is, at step 309, the other AMF can perform the AMF operation, and then the other AMF continues to perform the AMF operation at step 310.

In an embodiment, when the first message contains command information, the AMF (or other AMF) may perform detection according to the command information. Alternatively, the AMF (or other AMF) may perform discovery according to system configuration. Specifically, the AMF (or other AMF) detects that the first service change may be any of the changes described in step 304, and the details are not re-described here.

For example, as the network policy changes or the capabilities of the AMF (or other AMF) change, the current status of the first service may be changed from normally running to suspended (Suspend) and from suspended to resumed (Resume). As another example, the subscription to the first service is canceled (Cancel), canceled (Delete), and the like, due to the network policy or the user's subscription.

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

The third message is used to notify that the first service has been changed.

During a specific implementation, the third message may be an Event Exposure Subscription Change Message Request (Namf_Event_Exposure_SubscriptionChangeReport Request) or an Event Exposure Notification Request (Namf_Event_Exposure_Notify Request) sent by the AMF (or other AMF) to the UDM.

Step 311: Based on the third message, the UDM learns that the first service has been changed.

Alternatively, during a particular implementation, when the first service change is the status change described in step 304, the third message further contains the first status information. The first status information may be a paused state, a restored state, a canceled state, or a deleted state, and the like. Alternatively, in this case, the third message further comprises an event identifier and/or a user identification (such as a UE identification) corresponding to the first information about status. The event ID is used as follows: when the status of one or more events corresponding to the first set of event IDs changes, the event ID that carries the status change may indicate that a status change event occurs. The event ID is used as follows: when the event subscription is for a group of users, the user identification that carries the status change is used to indicate the user corresponding to the status change.

In an embodiment where the first service change is a subscription change described in step 304, the third message further includes a subscription attribute for the changed subscription to the first service. Alternatively, when the subscription change is a subscription correlation ID change, the subscription attribute changed is the updated subscription correlation ID. When the subscription change is an event reporting information change, the changed subscription attribute contains at least one of an updated event message mode, an updated maximum number of event messages, or an updated maximum duration of event messages.

Alternatively, the first message further comprises a first notification correlation identifier and the first notification correlation identifier is assigned by the UDM to the first address. The third message sent by the AMF to the first UDM address further contains the first notification correlation identifier. What the UDM learns, based on the third message, that the first service has changed is as follows: The UDM learns, based on the first notification correlation ID, that the first service has been changed.

In an embodiment, when the first message contains command information and the command information is a third set of event identifiers, the third message further comprises at least one event identifier in the third set of event identifiers such that the UDM identifies a particular change of the first service.

Step 312: When the first service change notified in the third message affects the subscription to the second service, the UDM sends a fifth message to the NEF, with the fifth message being used to notify that the second service has been changed.

During a particular implementation, the fifth message may be an Event Exposure Subscription Change Message Request (Nudm_Event_Exposure_SubscriptionChangeReport Request) or an Event Exposure Notification Request (Nudm_Event_Exposure_Notify Request) sent by the UDM to the NEF.

In an embodiment, when the first service change is the status change described in step 304 and the third message further contains first status information, the fifth message further contains second status information. For a specific limitation on the second status information, refer to the limitation on the first status information. The details are not re-described here.

In an embodiment, when the first service change is a subscription change described in step 304 and the third message further contains a subscription attribute for the changed subscription to the first service, the fifth message further contains a subscription attribute for the changed subscription to the second service. Specifically, to restrict the subscription attribute for the modified subscription to the second service, refer to the restriction for the modified subscription attribute in the previous step. The details are not re-described here.

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

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

Specifically, the eighth message may be a response to an event display subscription change message request (Nudm_Event_Exposure_SubscriptionChangeReport Response) or a response to an event exposure notification request (Nudm_Event_Exposure_Notify Response) sent from the NEF to the UDM.

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

Specifically, the ninth message may be a response to an event display subscription change message request (Namf_Event_Exposure_SubscriptionChangeReport Response) or a response to an event display notification request (Namf_Event_Exposure_Notify Response) sent from the UDM to the AMF.

In the above example, since when the first service changes, the UDM sends the address of the UDM to the AMF, the UDM can receive the notification, and therefore the service subscription procedure can be relatively completed and no interruption is caused.

As shown in FIG. 4A and 4B, an embodiment of this application further presents an example of a service subscription method. In this example, the first network function NE is PCF, the second network function NE is SMF, and the third network function NE is NEF. The NEF subscribes to the service from the PCF and the PCF additionally subscribes to the NEF service from the SMF. Specifically, the exemplary procedure may include the following steps.

Step 401: NEF receives first trigger information. Specifically, after NEF receives the first start information, NEF starts to request policy authorization from the PCF.

Alternatively, the first start information may come from another network function network element, such as an AF. In this case, the first AF start information may be AF request policy authorization information from the PCF. The first trigger information may alternatively be obtained by triggering the NEF's internal trigger.

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

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

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

During a particular implementation, the PCF creates a resource for the application session based on the application layer information carried in the main body of the HTTP POST at step 402, generates a child application session identifier of the resource identifier, and constructs a URI1 for the created resource. URI1 is formed by using the requested URI as the parent resource and then splicing it to the child resource identifier.

Alternatively, the tenth message may contain network policy, the user's subscription, and so on.

Step 404: The PCF sends the eleventh message to the NEF. Specifically, the eleventh message may be a policy authorization request (Npcf_PolicyAuthorization_Create Response) sent by the NEF from the PCF.

At implementation time, the PCF MAY send an HTTP Response back to the NEF, where the HTTP Response carries a "201 Created" Status Code and a "Location" header. The Location header carries the URI1 constructed in step 403.

Step 405: After executing the policy decision made based on the application layer information in the tenth message, the PCF sends a twelfth message to the SMF, where the twelfth message contains the formulated policy.

Specifically, the twelfth message may be a policy update notification request (Npcf_Policy_UpdateNotify Request) sent by the SMF from the PCF. In a particular implementation, the PCF sends an HTTP POST SMF, where the body of the message carries the stated policy.

Step 406: After the policy is stored, the SMF sends a thirteenth message back to the PCF.

Specifically, the thirteenth message may be a response to a policy update notification request (Npcf_Policy_UpdateNotify Response) sent from the SMF to the PCF. In a particular implementation, the SMF sends an HTTP Response to the PCF, where the HTTP Response carries a "200 OK" status code.

Step 407: After the NEF receives the second start information and wants to subscribe to the 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.

The second message contains the NEF address, namely the second address. So NEF receives the requested event using the second address. In an embodiment, the second message further comprises the second set of event identifiers (such as Event Id1) and the second notification correlation identifier (such as Notification Correlation ID) mentioned in the embodiment of FIG. 2. The second set of event IDs may include at least one event ID.

In an embodiment, the second message further comprises an external UE identifier (e.g., for a single UE), a UE group group identifier (e.g., for a group of UEs), or an indication of any UE (e.g., any UE parameter valid for all UEs in the current network) so that it can be determined from which second service it is ultimately provided.

In an exemplary implementation, the second message further comprises information reporting the event, and the information reporting the event comprises at least one of the event reporting mode, the maximum number of event messages, or the maximum duration of event messages. The event reporting mode may be a one-time message, a continuous message, a periodic message, and the like.

In an embodiment, the second message may be a policy authorization subscription request (Npcf_PolicyAuthorization_Subscribe Request) sent by the PCF from the NEF. In a particular implementation, the NEF sends an HTTP PATCH for the PCF, and the body of the HTTP PATCH message carries the above information, which may be included in the second message. The details are not re-described here.

Step 408: The PCF saves the information in the second message, updates the application session context, and assigns a first Subscription Correlation ID 1 to the second service subscription.

In a specific implementation, the subscribed service is added to the resource created in step 403.

Step 409: The PCF sends a fourteenth message to the NEF, where the fourteenth message contains the subscription correlation ID 1.

Specifically, the fourteenth message may be a policy authorization subscription request (Npcf_PolicyAuthorization_Subscribe Response) sent from the PCF to the NEF.

In a particular implementation, the PCF sends an HTTP Response to the NEF, where the HTTP Response carries a "200 OK" status code and a Subscription Correlation ID of 1.

Step 410: The PCF sends a first message to the SMF, and the PCF subscribes to the first service from the SMF using the first message. The first message contains the address of the PCF, namely the first address.

Alternatively, the PCF, based on the second service, determines the first service to subscribe from the SMF. Specifically, the first message further comprises a first event ID set, the first event ID set is generated based on the second event ID set, the first event ID set is an event ID set in the second event ID set corresponding to events to be provided by the SMF, and the second the set of event identifiers is contained in the second message.

For example, after receiving a second message, the PCF first determines the event (namely, the second set of events corresponding to the second set of event IDs in this embodiment of this application) that is in the second set of events corresponding to the second set of event IDs in the second message and which should be provided by the SMF, and then performs step 410. That is, the first set of event IDs in the first message is specifically determined based on the second set of event IDs in the second message. For example, the first set of event IDs is part or all of the second set of event IDs.

Specifically, in addition to the first address, the first message further contains a second address, which is used by the SMF to provide the first service to the NEF. When the first service is changed, the PCF may receive, using the first address, a message notifying that the first service has been changed.

In an exemplary implementation, the first message further comprises command information, and the command information is used to command, using the first address, to receive a message notifying that the first service has been changed. Specifically, changing the first service means that the status of the first service has been changed and/or the subscription to the first service has been changed. The change in the status of the first service may be a change in 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 restored state, a canceled state, or a deleted state. The subscription change may be a subscription attribute change. For example, a subscription change includes a change in the subscription correlation ID or a change in the information containing the event message. Changing the event reporting information comprises at least one of: changing the event reporting mode, changing the maximum number of event messages, or changing the maximum duration of event messages, and the like. That is, any of the cases described above may indicate, that the first service has been changed.

In an embodiment, the command information may only be a value of the command information, or may be a set of event IDs (namely, a third set of event IDs). When the command information is the third set of event IDs, the third set of event IDs contains a status change event ID, a subscription change event ID, and/or the like. In this case, the command information can be considered as having a function of issuing a command to provide a special event. For example, the special event may be a status change event or a subscription change event. Alternatively, the subscription change event ID may comprise a subscription correlation ID change event ID or a change event ID of the event reporting information.

In an embodiment where the first message does not contain the command information described above, after receiving the first message, the AMF detects that the first message carries more than one address, as compared to the prior art. That is, when the first address is transmitted, it can be automatically identified that the UDM receives, using the first address, a message notifying that the first service has been changed. That is, in this scenario, the first address has the following function: implicitly instructs to receive, using the first address, a message notifying that the first service has been changed. Of course, in this scenario, when the AMF detects the first address, the AMF may alternatively identify in any other form, such as using the currently configured mechanism, that a message notifying that the first service has been changed can be received using the first address. This is not limited in the present application.

Step 411: The SMF remembers the information in the second message and assigns a second Subscription Correlation ID 2 to the first service subscription in the first message.

During a particular implementation, the SMF creates a resource to subscribe to the first service based on the information carried in the first message, generates a subscription id2 to the child resource identifier, and constructs a uniform URI2 for the created resource. URI2 is formed by using the requested URI as the parent resource and then splicing it to the child resource ID. Here, the subscription id 2 may be used as the subscription correlation ID 2 .

Step 412: The SMF sends a fifteenth message to the PCF, where the fifteenth message contains the subscription correlation ID 2.

In an embodiment, the fifteenth message may be an Event Exposure Subscribe Response (Nsmf_ EventExposure_Subscribe Response) sent from the SMF to the PCF. At implementation time, the SMF sends an HTTP Response to the PCF, where the HTTP Response carries a "201 Created" Status Code and a "Location" header. The Location header carries the URI2 constructed in step 411.

Step 413: Upon detecting an event to be provided to the NEF, the SMF provides the first service to the NEF.

Step 414: When it is detected that the first service has been changed, the SMF performs step 415.

Alternatively, when the SMF that is serving the UE needs reselection because the UE is moving, the SMF transmits the information received in step 410 to another SMF (namely, the reselected SMF for the UE). In this case, the other SMF detects that the first service has been changed (eg, the other SMF assigns a new subscription correlation ID to the subscription to the first service). That is, the other SMF may perform the SMF operation at step 414 and then the other SMF continues to perform the SMF operation at step 415.

For a specific implementation, refer to the description at 309 in the embodiment shown in FIG. 3. The principles are the same and the details are not repeated here.

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

During a particular implementation, the third message may be an Event Exposure Change Subscription Message Request (Nsmf_Event_Exposure_SubscriptionChangeReport Request) or an Event Exposure Notification Request (Nsmf_Event_Exposure_Notify Request) sent by the NEF from the SMF.

Step 416: Based on the third message, the PCF learns that the first service has been changed.

Alternatively, during a particular implementation, when the first service change is the status change described at step 410, the third message further contains the first status information. The first status information may be a paused state, a restored state, a canceled state, or a deleted state, and the like. Alternatively, in this case, the third message further comprises an event identifier and/or a user identification (such as a UE identification) corresponding to the first information about status. The event ID is used as follows: when the status of one or more events corresponding to the first set of event IDs changes, the event ID that carries the status change may indicate that a status change event occurs. The event ID is used as follows: when the event subscription is for a group of users, the user identification that carries the status change is used to indicate the user corresponding to the status change.

In an embodiment where the first service change is a subscription change described in step 410, the third message further includes a subscription attribute for the changed subscription to the first service. Alternatively, when the subscription change is a subscription correlation ID change, the subscription attribute changed is the updated subscription correlation ID. When the subscription change is an event reporting information change, the changed subscription attribute contains at least one of an updated event message mode, an updated maximum number of event messages, or an updated maximum duration of event messages.

Alternatively, the first message further comprises a first notification correlation identifier, and the first notification correlation identifier is assigned by the PCF to the first address. The third message sent from the SMF to the first PCF address further contains the first notification correlation identifier. What the PCF learns, based on the third message, that the first service has been changed is as follows: The PCF, based on the first notification correlation ID in the third message, knows that the first service has been changed.

In an embodiment, when the first message contains command information and the command information is a third set of event identifiers, the third message further comprises at least one event identifier in the third set of event identifiers such that the PCF identifies a particular change of the first service.

Step 417: When the PCF determines that the first service change notified in the third message affects the subscription to 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.

In a specific implementation, the fifth message may be an Event Exposure Subscription Change Message Request (Npcf_Event_Exposure_SubscriptionChangeReport Request) or an Event Exposure Notify Request (Npcf_Event_Exposure_Notify Request) sent by the NEF from the PCF.

In an embodiment, when the first service change is the status change described in step 410 and the third message further contains the first status information, the fifth message further contains the second status information. For a specific limitation on the second status information, refer to the limitation on the first status information. The details are not re-described here.

In an embodiment, when the first service change is a subscription change described in step 410, and the third message further contains a subscription attribute for the changed subscription to the first service, the fifth message further contains a subscription attribute for the changed subscription to the second service. Specifically, to restrict the subscription attribute for the modified subscription to the second service, refer to the restriction for the modified subscription attribute in the previous step. The details are not re-described here.

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

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

Specifically, the sixteenth message may be a response to an event display subscription change message request (Npcf_Event_Exposure_SubscriptionChangeReport Response) or a response to an event exposure notification request (Npcf_Event_Exposure_Notify Response) sent from the NEF to the PCF.

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

Specifically, the seventeenth message may be a response to an event demonstration subscription change message request (Nsmf_Event_Exposure_SubscriptionChangeReport Response) or a response to an event demonstration notification request (Nsmf_Event_Exposure_Notify Response) sent from the PCF to the SMF.

In the above example, since when the first service is changed, the PCF sends the address of the PCF to the SMF, the PCF can receive the notification, and therefore the service subscription procedure can be relatively completed and no interruption is caused.

Based on the embodiments described above, an embodiment of this application further provides a service subscription method. In this embodiment, network elements subscribing to services may be collectively referred to as a network function service consumer (NF Service Consumer), and network elements may provide services, which 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 in the communication system shown in FIG. 1 are collectively the network elements of the network function. As shown in FIG. 5, the specific procedure for implementing the method comprises the following steps.

Step 501: The NF service consumer receives trigger information and needs to subscribe to a service for another network function network element from the NF service provider. Specifically, after the NF service consumer receives the start information, the NF service consumer is triggered to perform a service subscription from the NF service producer.

Alternatively, the start information may come from another network function network element (namely, another NF). For example, triggering information can be obtained by triggering with NEF in the embodiment described above, that is, triggering by the second message. The trigger information may alternatively be obtained by triggering with the NF's internal trigger.

Step 502: The NF service consumer sends a first message to the NF service producer, and the NF service consumer subscribes to the first service from the NF service producer using the first message. The first message contains the address of the NF service consumer, namely the first address. When the first service is changed, the NF service consumer may receive, using the first address, a message notifying that the first service has been changed.

Specifically, in addition to the first address, the first message further contains a Notification Target Address. The device corresponding to the notification destination address can receive the requested event using the notification destination address, that is, the NF service provider provides the first service to the device corresponding to the notification destination address using the notification destination address. Alternatively, the notification target address in the above embodiment may be, but is not limited to, the second address.

In an embodiment, the first message further comprises a first notification correlation identifier and the first notification correlation identifier is used by the NF service consumer to correlate an Event Notification with a corresponding Event Subscription. The first message further comprises an external UE identifier (eg, for a single UE), a UE group group identifier (eg, for a group of UEs), or an indication of any UE (eg, any UE parameter valid for all UEs in the active network).

In an exemplary implementation, the first message further comprises information reporting the event, and the information reporting the event comprises at least one of the event reporting mode, the maximum number of event messages, or the maximum duration of event messages. The event reporting mode may be a one-time message, a continuous message, a periodic message, and the like.

In an exemplary implementation, the first message further comprises command information, and the command information is used to command to receive, using the first address, a message notifying that the first service has been changed. Specifically, changing the first service means that the status of the first service has been changed and/or the subscription to the first service has been changed. The change in the status of the first service may be a change in 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 restored state, a canceled state, or a deleted state. The subscription change may be a subscription attribute change. For example, a subscription change includes a change in the subscription correlation ID or a change in the information containing the event message. Changing the event reporting information comprises at least one of: changing the event reporting mode, changing the maximum number of event messages, or changing the maximum duration of event messages, and the like. That is, any of the cases described above may indicate, that the first service has been changed.

In an embodiment, the command information may only be a value of the command information, or may be a set of event IDs (namely, a third set of event IDs). When the command information is the third set of event IDs, the third set of event IDs contains a status change event ID, a subscription change event ID, and/or the like. In this case, the command information can be considered as having a function of issuing a command to provide a special event. For example, the special event may be a status change event or a subscription change event. Alternatively, the subscription change event ID may comprise a subscription correlation ID change event ID or a change event ID of the event reporting information.

In an embodiment where the first message does not contain the command information described above, after receiving the first message, the NF service provider detects that the first message carries more than one address, as compared to the prior art. That is, when the first address is transmitted, the NF service producer automatically identifies that the NF service consumer receives, using the first address, a message notifying that the first service has been changed. That is, in this scenario, the first address has the following function: implicitly, using the first address, instructs to receive a message notifying that the first service has been changed. Of course, in this scenario, when the AMF detects the first address, the AMF may alternatively identify in any other form, such as using the currently configured mechanism, that a message notifying that the first service has been changed can be received using the first address. This is not limited in the present application.

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

Step 503: After receiving the first message, the NF service provider stores the information in the first message and assigns a second Subscription Correlation ID 2 to the first service subscription in the first message.

During a specific implementation, the service provider NF creates a resource to subscribe to the first service based on the information carried in the main body, generates a subscription id1 to the child resource identifier, and constructs a Uniform Resource Locator (URI) 2 for the created resource. URI2 is formed by using the requested URI as the parent resource and then splicing it to the child resource ID. Here, the subscription id 2 may be used as the subscription correlation ID 2 .

Step 504: The NF service producer sends an eighteenth message to the NF service consumer, where the eighteenth message contains the subscription correlation ID 2.

In an embodiment, the eighteenth message may be an Event Exposure Subscribe Request (Nnf_EventExposure_Subscribe Request) sent by the NF service producer to the NF service consumer. At implementation time, the NF service producer sends back to the NF service consumer an HTTP Response, where the HTTP Response carries a Status Code of "201 Created" and a header of "Location". The Location header carries a URI2.

Step 505: Upon detecting an event that can be provided to the NF service consumer, the service provider provides the NF service consumer with a first service.

Step 506: When it is detected that the first service has been changed, the NF service provider executes step 507.

Alternatively, as the UE moves, the NF service provider that serves the UE needs reselection, the NF service provider transmits the information received in step 502 to another NF network element (namely, the reselected NF network element for the UE). In this case, the other NF network element detects that the first service has been changed, that is, the other NF network element can perform the NF service producer operation in step 505, and then the other NF network element continues to perform the NF service producer operation in step 507. The function of the other NF network element is the same as that of the NF service provider.

In an embodiment, when the first message contains command information, the NF service producer (or other NF network element) may perform discovery according to the command information. Alternatively, the NF service provider (or other NF network element) may perform the discovery according to the system configuration. Specifically, the NF service provider (or other NF network element) detects that the second service change may be any change described in step 502, and the details are not re-described here.

For example, as the network policy changes or the capabilities of the NF service provider (or other NF network element) change, the current status of the first service can be changed from normally running to Suspend and from Suspended to Resume. As another example, the subscription to the first service is canceled (Cancel), canceled (Delete), and the like, due to the network policy or the user's subscription.

Step 507: The NF service provider (or other NF network element) sends a third message to the first NF service consumer address, where the third message is used to notify that the first service has been changed.

During a particular implementation, the third message may be an Event Exposure Subscription Change Message Request (Nnf_Event_Exposure_SubscriptionChangeReport Request) or an Event Exposure Notification Request (Nnf_Event_Exposure_Notify Request) sent to the NF service consumer.

Step 508: The NF service consumer learns based on the third message that the first service has been changed.

Alternatively, during a particular implementation, when the first service change is the status change described in step 502, the third message further contains the first status information. The first status information may be a paused state, a restored state, a canceled state, or a deleted state, and the like. Alternatively, in this case, the third message further comprises an event identifier and/or a user identification (such as a UE identification) corresponding to the first information about status. The event ID is used as follows: When the status of one or more events corresponding to the first set of event IDs changes, the event ID that carries the status change may indicate that a status change event is occurring. The event ID is used as follows: when the event subscription is for a group of users, the user identification that carries the status change is used to indicate the user corresponding to the status change.

In an embodiment, when the first service change is a subscription change described in step 502, the third message further contains a subscription attribute for the changed subscription to the first service. Alternatively, when the subscription change is a subscription correlation ID change, the subscription attribute changed is the updated subscription correlation ID. When the subscription change is an event reporting information change, the changed subscription attribute contains at least one of an updated event message mode, an updated maximum number of event messages, or an updated maximum duration of event messages.

Alternatively, the first message further comprises a first notification correlation identifier, and the first notification correlation identifier is assigned by the NF service consumer to the first address. The third message sent by the NF service producer to the first NF service consumer address further comprises a first notification correlation identifier. What the NF service consumer learns based on the third message that the first service has been changed is as follows: The NF service consumer learns based on the first notification correlation ID in the third message that the first service has been changed.

In an embodiment, when the first message contains command information and the command information is a third set of event identifiers, the third message further comprises at least one event identifier in the third set of event identifiers so that the service consumer NF identifies a particular change of the first service.

Step 509: The NF service consumer sends the nineteenth message to the NF service producer.

Specifically, the nineteenth message may be a response to an event exposure change subscription message request (Nnf_Event_Exposure_SubscriptionChangeReport Response) or a response to an event exposure notification request (Nnf_Event_Exposure_Notify Response) sent by the NF service consumer to the NF service producer.

According to the service subscription method presented in this embodiment of the present application, the NF service consumer transmits the address of the NF service consumer to the NF service producer. Thus, when the first service is changed, the NF service consumer can receive the notification, and therefore the service subscription procedure can be relatively completed and no interruption is caused.

Based on the same inventive concept as the method embodiment, an embodiment of this application further provides an apparatus and the apparatus is applied to the first network element of the network function. Device 600 may be a processor, chip or chip system, function module, or the like in the first network element of the network function. As shown in FIG. 6, device 600 may include a transmitter unit 601, a receiver unit 602, and a processing unit 603. The transmitting unit 601 is used by the device 600 to transmit information, the receiving unit 602 is used by the device 600 to receive information, and the processing unit 603 is configured to control and direct the operation of the device 600. The processing unit 603 may further be configured to indicate a processing process associated with the first network a network function element (such as a UDM or PCF) in any of the embodiments described above and/or with another technical solution process described in this application. Specifically, the processing unit 603 may control the transmitting unit 601 to perform step 201 and control the receiving unit 602 to perform step 202 and step 203. See the embodiment shown in FIG. 2. Details are not re-described here.

In a hardware implementation, the processing unit 603 may be a processor, a processing circuit, or the like, the transmitting unit 601 may be a transmitter, a transmitting circuit, or the like, and the receiving unit 602 may be a receiver, a receiving circuit, or the like. 601 and the receiving unit 602 may form a transceiver.

Based on the same inventive concept as in the method embodiment, an embodiment of this application further provides an apparatus and the apparatus is applied to the second network element of the network function. Device 700 may specifically be a processor, chip or chip system, function module, or the like in the second network element of the network function. As shown in FIG. 7, device 700 may include a receiving unit 701, a transmitting unit 702, and a processing unit 703. The transmitting unit 702 is used by the device 700 to transmit information, the receiving unit 701 is used by the device 700 to receive information, and the processing unit 703 is configured to control and direct the operations of the device 700. The processing unit 703 may further be configured to indicate a processing process associated with the second network a network function element (such as AMF or SMF) in any of the embodiments described above and/or in another process of the technical solution described in this application. Specifically, for the steps that the processing unit 703 can perform to control the transmitting unit 702 and the receiving unit 701, refer to the above-described embodiments. The details of the content are not described again here.

In a hardware implementation, the processing unit 703 may be a processor, a processing circuit, or the like, the transmitting unit 702 may be a transmitter, a transmitting circuit, or the like, and the receiving unit 701 may be a receiver, a receiving circuit, or the like. 702 and the receiving unit 701 may form a transceiver.

It should be noted that in the embodiments of the present application, the division into blocks is exemplary and is simply division by logical functions. In actual implementation, a different division method may be used. The functional blocks in embodiments of the present application may be integrated into a single processing unit, or each of the units may physically exist separately, or two or more units may be integrated into one unit. An integrated block may be implemented in hardware form or in the form of a software function block.

When an integrated block is implemented in the form of a software function block and sold or used as a standalone product, the integrated block may be stored on a computer-readable storage medium. Based on this understanding, the technical solutions of the present application, predominantly or partially constituting the prior art, or all or some of the technical solutions may be implemented in the form of a software product. The computer program product is stored on a storage medium and contains one or more instructions for controlling a computing device (which may be a personal computer, a server or a network device, etc.), or a processor (processor), to perform all or some of the steps of the methods described in the embodiments of the present application. The above storage medium includes any medium that can store a control program, such as USB flash memory, removable hard disk, Read-Only Memory (ROM), Random Access Memory (RAM), magnetic disk or CD.

Based on the above-described embodiments, an embodiment of this application further provides another first network function network element capable of implementing the service subscription method described above. As shown in FIG. 8, the first network function network element 800 may include a transceiver 801 and a processor 802. Alternatively, the first network function network element 800 may further comprise a memory 803. The memory 803 may be located within the first network function network element 800 or outside the first network function network element 800 . The processor 802 controls the transceiver 801 to receive and transmit data, and is configured to implement the methods performed by the first network function network elements (such as UDM and PCF) in FIG. 2-5.

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

The transceiver 801, the processor 802 and the memory 803 are interconnected. Alternatively, transceiver 801, processor 802, and memory 803 are interconnected using a bus 804. Bus 804 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA), etc. etc. A bus can be classified as an address bus, a data bus, a control bus, and the like. For ease of presentation, the bus is represented in FIG. 8 using only one thick line, but this does not mean that there is only one tire or only one type of tire.

In an embodiment, the memory 803 is configured to store a program or the like. Specifically, the program may include a control program, and the control program may contain instructions for operating the computer. Memory 803 may comprise RAM and may further comprise non-volatile memory, such as at least magnetic disk memory. The processor 802 executes the application program stored in the memory 803 to implement the functions described above so as to implement the service subscription method presented in the embodiments of the present application.

Based on the above-described embodiments, an embodiment of this application further provides another second network function network element capable of implementing the service subscription method described above. As shown in FIG. 9, the second network function network element 900 may include a transceiver 901 and a processor 902. Alternatively, the second network function network element 900 may further comprise a memory 903. The memory 903 may be located within the second network function network element 900 or outside the second network function network element 900 . The processor 902 controls the transceiver 901 to receive and transmit data, and is configured to implement the methods performed by the second network function network elements (such as AMF and SMF) shown in FIG. 2-5.

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

The transceiver 901, the processor 902 and the memory 903 are interconnected. Alternatively, transceiver 901, processor 902, and memory 903 are interconnected using a bus 904. Bus 904 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA), etc. etc. A bus can be classified as an address bus, a data bus, a control bus, and the like. For ease of presentation, the bus is represented in FIG. 9 using only one thick line, but this does not mean that there is only one tire or only one type of tire.

In an embodiment, the memory 903 is configured to store a program or the like. Specifically, the program may contain a program program, and the program program contains instructions for operating the computer. The memory 903 may include RAM and may further include non-volatile memory, such as at least a memory on a magnetic disk. The processor 902 executes the application program stored in the memory 903 to implement the functions described above for implementing the service subscription method presented in the embodiments of the present application.

Based on the embodiments described above, an embodiment of this application further provides a computer storage medium. The storage medium stores the software program and when it is read and executed by one or more processors, the software program may implement the method presented in one or more of the above embodiments. The computer storage medium may comprise any medium that can store a control program, such as a USB flash drive, a removable hard drive, read only memory, RAM, a magnetic disk, or a CD.

Based on the above embodiments, an embodiment of the present application further provides a microchip, wherein the microchip comprises a processor configured to perform the functions in one or more of the above embodiments, such as receiving or processing information or messages in the methods presented above. Alternatively, the chip further comprises a memory, and the memory is configured to store the necessary program instructions and data that are executed by the processor. A microcircuit may contain a microcircuit or contain a microcircuit and other discrete device.

Finally, according to the service subscription method and apparatus presented in the embodiments of the present application, the first network function network element transmits a first message to the second network function network element to subscribe the third network function network element to the first service from the second network function network element, where the first message contains the first address and the first address is the address of the first network element of the network function; and the first network function network element receives the third message using the first address and learns based on the third message that the first service has been changed. According to this method, the first network function network element passes the address of the first network function network element to the second network function network element. Therefore, when the first service is changed, the first network element of the network function can receive notification that the service has been changed. Thus, the service change reporting mechanism is improved, and therefore, the service subscription procedure can be relatively completed and no interruption is caused.

One skilled in the art will understand that embodiments of the present application may be provided as a method, system, or computer program product. Therefore, the present application may use any form of hardware-only embodiments, software-only embodiments, or combination of software and hardware embodiments. Moreover, the present application may use some form of computer program product implemented on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, CD-ROMs, optical memory etc.) that contain the control program used by the computer.

The present application is described with reference to flowcharts of the method and/or flowcharts of the method, devices (systems) and computer program product corresponding to the present application. It should be understood that computer program instructions may be used to implement each process and/or each block in flowcharts, or in process and/or block flowcharts and combinations in flowcharts and/or block diagrams. schemes. These computer program instructions may be provided to a mainframe computer, a specialized computer, an embedded processor, or the processor of any other programmable data processing device, to form such a machine such that the instructions executed by the computer or the processor of any other programmable data processing device create a device to implement a particular function. in one or more processes in the flowcharts and/or in one or more blocks in the flowcharts.

These computer program instructions may alternatively be stored in computer-readable memory, which may instruct the computer or other programmable processing device to operate in a certain way, such that the instructions stored in the computer-readable memory create an artifact containing the command device. The command device implements a particular function in one or more processes according to flowcharts and/or one or more blocks in the flowcharts.

These computer program instructions may alternatively be downloaded to a computer or other programmable processing device such that the sequences of operations and steps are executed on the computer or other programmable device, thereby producing computer-implemented processing. Therefore, instructions executable on a computer or other programmable device provide steps for implementing a particular function in one or more processes according to flowcharts and/or one or more blocks in the flowcharts.

Obviously, those skilled in the art can make various modifications and variations of the embodiments of the present application without departing from the spirit and scope of protection of the present application. The present application is intended to cover these modifications and variations of the embodiments of the present application, provided that they fall within the protection scope of the claims of the present application and their equivalent technologies.

Claims (145)

1. A method for subscribing to services, comprising the steps of: transmitting, by means of the first network function network element, a first message to the second network function network element, for subscription, on behalf of the third network function network element, to the first service at the second network function network element, the first message containing the first address of the first network function network element ; receiving, with the first network function network element, using the first address, a third message notifying the first network function network element that the subscription to the first service has been changed. 2. The method of claim 1, wherein the first message further comprises a second address, the second address being the address of the third network function network element. 3. The method of claim 2, further comprising the steps of: receiving, with the help of the first network function network element, a second message from the third network function network element, the second message being used to subscribe to the second service and the second message containing the second address; and determining, with the first network function network element, based on the second service, a first service to be subscribed to from the second network function network element. 4. The method according to claim 2 or 3, further comprising the step of transmitting, by means of the first network function network element, a fifth message to a second address of the third network function network element, the fifth message being used to notify that the second service has been changed. 5. The method according to any one of paragraphs. 1-3, further comprising the step of assigning, with the first network function network element, a first notification correlation identifier; wherein the first message transmitted by the first network function network element to the second network function network element further comprises a first notification correlation identifier. 6. The method of claim 5, wherein the third message further comprises a first notification correlation identifier. 7. The method according to any one of paragraphs. 4-6, wherein the second message further comprises a second notification correlation identifier, wherein the second notification correlation identifier is assigned by the third network function network element; while the stage transmission, with the help of the first network function network element, of the fifth message to the second address of the third network function network element comprises a sub-step, in which the transmission, with the help of the first network function network element, of the fifth message containing the second correlation identifier of the subscription to the second address of the third network function network element functions. 8. The method according to any one of paragraphs. 1-7, wherein the step of receiving, using the first network function network element, the third message, using the first address, comprises a sub-step of: receiving, with the help of the first network function network element, a third message from the second network function network element using the first address; or receiving, with the first network function network element, a third message from the fourth network function network element using the first address when control for the UE is transferred from the second network function network element to the fourth network function network element. 9. A method for subscribing to services, comprising the steps of: receiving, with the help of the second network function network element, a first message from the first network function network element, wherein the first message is used by the first network function network element to subscribe to the first service for the third network function network element from the second network function network element, the first the message contains a first address, and the first address is the address of the first network element of the network function; and transmitting, with the second network function network element, a third message to the first address to notify the first network function network element that the first service has been changed. 10. The method of claim 9, further comprising, when the first message further comprises a second address, the second address being the address of a third network function network element, providing, by the second network function network element, a first service to a third network function network element based on the second address. 11. The method of claim 9 or 10, wherein the first message further comprises a first notification correlation identifier; a the third message sent by the second network element of the network function to the first address contains the first notification correlation identifier. 12. The method according to any one of paragraphs. 9-11, further comprising the step of requesting, by means of the second network function network element, a first service from the fourth network function network element, and transmitting the first address to the fourth network function network element. 13. A method for subscribing to services, comprising the steps of: receiving, with the help of the second network function network element, a first message from the first network function network element, wherein the first message is 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 containing the first address of the first network function network function element; and when the UE is handed over from the second network function network element to the fourth network function network element, the first address to the fourth network function network element is transmitted. 14. The method of claim 13, wherein the step of transmitting, by means of the second network function network element, the first address to the fourth network function network element, comprises the sub-step of transmitting, by means of the second network function network element, the context information to the fourth network function network element, the context information being generated based on the first service subscription information, and the context information containing the second address. 15. The method of claim 13, further comprising, when the first message further comprises a first notification correlation identifier assigned by the second network function network element, transmitting, via the second network function network element, the first notification correlation identifier to the fourth network function network element. 16. The method of claim 15, wherein the step of transmitting the first address to the fourth network function network element and transmitting the first notification correlation identifier to the fourth network function network element comprises the sub-step of transmitting, by means of the second network function network element, the context information to the fourth network function network element, the context information being generated based on the first service subscription information, and the context information containing the first address and the first notification correlation identifier. 17. The method according to any one of paragraphs. 13-16, further comprising, when the first message further comprises a second address of the third network function network element, a step of providing, by the second network function network element, a first service to a third network function network element based on the second address. 18. A method for subscribing to services, comprising the steps of: receiving, via the fourth network function network element, from the second network function network element a first address of the first network function network element; and sending, by means of the fourth network function network element, a third message to the first address to notify the first network function network element that the first service has been changed, the first service being subscribed by the first network function network element on behalf of the third network function network element. 19. The method of claim 18, wherein the step of receiving, by means of the fourth network function network element, from the second network function network element, the first address of the first network function network element, comprises the sub-step of receiving, by means of the fourth network function network element, context information from the second network function network element, wherein the context information is generated based on the subscription information for the first service and the context information contains the first address. 20. The method according to claim 18 or 19, in which the method comprises the step of assigning, by the fourth network function, a new subscription correlation ID to the first service subscription. 21. A method for subscribing to services, comprising the steps of: receiving, with the help of the second network function network element, a first message from the first network function network element, the first message being used by the first network function network element to subscribe to the first service for the third network function network element from the second network function network element, the first message contains the first address and the first address is the address of the first network element of the network function; and when control of the network element serving the UE is transferred from the second network function network element to the fourth network function network element, by means of the second network function network element, the first service subscription information to the fourth network function network element, the first service subscription information comprising the first address. 22. The method of claim 21, wherein the step of transmitting, by the second network function network element, the first service subscription information to the fourth network function network element, comprises the sub-step of transmitting, by means of the second network function network element, the context information to the fourth network function network element, the context information being generated based on the first service subscription information. 23. The method of claim 21 or 22, wherein the first message further comprises a first notification correlation identifier assigned by the first network function network element, and the first service subscription information comprises the first notification correlation identifier. 24. The method according to any one of paragraphs. 21-23, further comprising, when the first message further comprises a second address, wherein the second address is an address of a third network function network element, providing, by the second network function network element, a first service to a third network function network element based on the second address. 25. A method for subscribing to services, comprising the steps of: receiving, by means of the fourth network function network element, subscription information for the first service from the second network function network element, wherein the first network function network element subscribes the first service for the third network function network element from the second network function network element, wherein the subscription information for the first service contains the first address and the first address is the address of the first network element of the network function; and transmitting, with the fourth network function network element, a third message to the first address to notify the first network function network element that the first service has been changed. 26. The method of claim 25, further comprising the step of assigning, by the fourth network function, a new subscription correlation ID to the first service subscription. 27. The first network element of the network function, containing: a transceiver configured to receive and transmit data; and a processor configured to: control the transceiver to transmit to the second network function network element a first message, to subscribe, on behalf of the third network function network element, to the first service from the second network function network element, wherein the first message contains the first address of the first network function network element ; and controlling the transceiver to receive, using the first address, a third message notifying the first network element of the network function that the subscription to the first service has been changed. 28. The first network function network element of claim 27, wherein the first message further comprises a second address of the third network function network element. 29. The first network function network element of claim 28, wherein the processor is further configured to controlling the transceiver to receive a second message from a third network element of the network function, the second message being used to subscribe to a second service and the second message containing a second address; and the processor is further configured to determine, based on the second service, the first service to be subscribed to from the second network element of the network function. 30. The first network function network element of claim 27, wherein the processor is further configured to controlling the transceiver to transmit the fifth message to the second address of the third network function network element, the fifth message being used to notify that the second service has been changed. 31. The first network element of the network function according to any one of paragraphs. 27-30, wherein the processor is further configured to assign a first notification correlation ID, wherein the first message further comprises a first notification correlation ID. 32. The first network element of the network function according to paragraphs. 27-31, in which the third message further contains the first notification correlation identifier. 33. The first network element of the network function according to any one of paragraphs. 30-32, wherein the second message further comprises a second notification correlation ID and a second notification correlation ID assigned to the third network function network element; wherein the processor is further configured to, when controlling the transceiver to transmit the fifth message to the second address of the third network function network element, control the transceiver to transmit the fifth message containing the second notification correlation identifier to the second address of the third network function network element. 34. The first network element of the network function according to any one of paragraphs. 27-33, wherein, in controlling the transceiver to receive the third message using the first address, the processor is specifically configured to: controlling the transceiver to receive a third message from the second network element of the network function using the first address; or controlling the transceiver to receive a third message from the fourth network function network element using the first address when control of the UE is transferred from the second network function network element to the fourth network function network element. 35. The second network element of the network function, containing: a transceiver configured to receive and transmit data; and a processor configured to: control the transceiver to receive a first message from the first network function network element, the first message being used by the first network function network element to subscribe to the first service, the third network function network element, from the second network function network element, the first message contains the first address and the first address is the address of the first network element of the network function; and controlling the transceiver to send a third message to the first address to notify the first network element of the network function that the first service has been changed. 36. The second network function network element of claim 35, wherein the first message further comprises a second address and the second address is an address of a third network function network element, wherein the processor is further configured to provide the first service to the third network function network element based on the second addresses. 37. The second network function network element of claim 35, wherein the first message further comprises a first notification correlation identifier; wherein the processor is further configured to, when controlling the transceiver to transmit the third message to the first address, control the transceiver to transmit, to the first address, the third message containing the first notification correlation identifier. 38. The second network function network element of claim 35 or 36, wherein the processor is further configured to controlling the transceiver to request a first service from the fourth network function network element; and controlling the transceiver to transmit the first address to the fourth network function network element. 39. The second network element of the network function, containing: a transceiver configured to receive and transmit data; and a processor configured to control the transceiver to receive a first message from the first 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 at the second network function network element, the first message comprising the first address of the first network element of the network function, while, 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 transmit the first address to the fourth network function network element. 40. The second network function network element of claim 39, wherein the processor is configured to communicate the first address to the fourth network function network element, comprising: the processor is configured to control the transceiver to transmit context information to the fourth network element of the network function, wherein the context information is generated based on the first service subscription information and the context information contains the first address. 41. The second network function network element of claim 39, wherein the first message further comprises 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. 42. The second network function network element of claim 41, wherein the processor is configured to control the transceiver to send the first address to the fourth network function network element and send the first notification correlation identifier to the fourth network function network element, comprising: the processor is configured to control the transceiver to transmit context information to the fourth network function network element, wherein the context information is generated based on the first service subscription information, and the context information comprises a first address and a first notification correlation identifier. 43. The second network element of the network function according to any one of paragraphs. 39-42, wherein the first message further comprises 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. 44. The fourth network element of the network function, containing: a transceiver configured to receive and transmit data; and a processor configured to control the transceiver to receive from the second network element the first address of the first network element of the network function; and the processor is further configured to control the transceiver to transmit a third message to the first address, to notify the first network function network element that the first service has been changed, wherein the first service is subscribed to by the first network function network element on behalf of the third network function network element. 45. The fourth network function network element of claim 44, wherein the processor is configured to control the transceiver to receive context information from the second network function network element, wherein the context information is generated based on the first service subscription information and the context information comprises the first address . 46. The fourth network function network element of claim 44 or 45, wherein the processor is further configured to assign a new subscription correlation ID to the first service subscription. 47. The second network element of the network function, containing: a transceiver configured to receive and transmit data; and a processor configured to control the transceiver to receive a first message from the first network function network element, wherein the first message is used by the first network function network element to subscribe to the first service for the third network function network element at the second network function network element, the first message comprising the first address and the first address is the address of the first network element of the network function, wherein, when control of the network element serving the UE is transferred from the second network function network element to the fourth network function network element, the processor is further configured to control the transceiver to transmit the first service subscription information to the fourth network function network element, wherein the first service subscription information contains the first address. 48. The second network function network element of claim 47, wherein the processor is configured to control the transceiver to transmit subscription information for the first service to the fourth network function network element, comprising: the processor is configured to control the transceiver to transmit context information to the fourth network element of the network function, the context information being generated based on the first service subscription information. 49. The second network function network element of claim 47 or 48, wherein the first message further comprises a first notification correlation identifier assigned by the first network function network element, and the first service subscription information comprises the first notification correlation identifier. 50. The second network element of the network function according to any one of paragraphs. 47-49, wherein the first message further comprises a second address, the second address being the address of a third network function network element, wherein the processor is further configured to provide a first service to the third network function network element based on the second address. 51. The fourth network element of the network function, containing: a transceiver configured to receive and transmit data; and a processor configured to control the transceiver to receive the first service subscription information from the second network function network element, wherein the first network function network element subscribes to the first service for the third network function network element from the second network function network element, and the subscription information to the first service contains the first address and the first address is the address of the first network element of the network function; wherein 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 been changed. 52. The fourth network function network element of claim 51, wherein the processor is further configured to assign a new subscription correlation ID to the first service subscription. 53. The method according to any one of paragraphs. 1-17 and 21-24, wherein the first message further comprises command information, wherein the command information is a third set of event IDs, and the third set of event IDs comprises a status change event ID and/or a subscription change event ID. 54. The method according to any one of paragraphs. 1-12, 18-20, 25 and 26, wherein the third message further comprises a status change event ID and/or a subscription change event ID. 55. The method according to any one of paragraphs. 1-12, 18-20, 25 and 26, wherein changing the first service means that the status of the first service has been changed and/or the subscription to the first service has been changed. 56. The method of claim 55, wherein changing the subscription may comprise changing the subscription correlation identifier or changing the event reporting information. 57. The method of claim 55, wherein changing the first service means that the status has been changed, the third message further comprises the first status information, and the first status information is a paused state, a restored state, a canceled state, or a deleted state. 58. The method of claim 57, wherein the third message further comprises an event identifier and/or user identification corresponding to the first status information. 59. The method of claim 55, wherein changing the first service means that the subscription has been changed, the third message further includes a subscription attribute for the changed subscription to the first service. 60. The method of claim 59, wherein when the subscription change is a subscription correlation ID change, the subscription attribute for the changed subscription to the first service is the updated subscription correlation ID. 61. The method of claim 59, wherein when the subscription change is a change in information reporting a subscription, the subscription attribute for the changed subscription to the first service comprises at least one of: an updated event message mode, an updated maximum number of event messages, or updated maximum duration of event messages. 62. The method of claim 53 or 54, wherein the subscription change event identifier comprises a subscription correlation identifier change event identifier or an event reporting information change event identifier. 63. The method of claim 53 or 54, wherein the third message further comprises at least one event identifier from the third set of event identifiers. 64. Network element according to any one of paragraphs. 27-43 and 47-50, wherein the first message further comprises command information, wherein the command information is a third set of event IDs, and the third set of event IDs comprises a status change event ID and/or a subscription change event ID. 65. Network element according to any one of paragraphs. 27-38, 44-46, 51 and 52, wherein the third message further comprises a status change event ID and/or a subscription change event ID. 66. Network element according to any one of paragraphs. 27-38, 44-46, 51 and 52, in which changing the first service means that the status of the first service has been changed and/or the subscription to the first service has been changed. 67. The network element of claim 66, wherein the subscription change may comprise changing the subscription correlation identifier or changing the event reporting information. 68. The network element of claim 66, wherein the change of the first service means that the status has been changed, the third message further contains the first status information, and the first status information is a paused state, a restored state, a canceled state, or a deleted state. 69. The network element of claim 66, wherein the third message further comprises an event identifier and/or user identification corresponding to the first status information. 70. The network element of claim 66, wherein changing the first service means that the subscription has been changed, the third message further contains a subscription attribute for the changed subscription to the first service. 71. The network element of claim 70, wherein when the subscription change is a subscription correlation ID change, the subscription attribute for the changed subscription to the first service is the updated subscription correlation ID. 72. The network element of claim 70, wherein when the subscription change is a change of information reporting a subscription, the subscription attribute for the changed subscription to the first service contains at least one of: an updated event message mode, an updated maximum number of event messages or the updated maximum duration of event messages. 73. The network element of claim 64 or 65, wherein the subscription change event identifier comprises a subscription correlation identifier change event identifier or an event reporting information change event identifier. 74. The network element of claim 64 or 65, wherein the third message further comprises at least one event identifier from the third set of event identifiers. 75. An information transfer chip connected to the memory and characterized in that it is configured to read and execute program instructions stored in the memory to implement the method according to any one of paragraphs. 1-26. 76. An information transmission device, characterized in that it is configured to implement the method according to any one of paragraphs. 1-26. 77. A computer-readable storage medium that stores commands that cause, when the computer readable storage medium is read by a computer, the execution, by the computer, of the method according to any one of paragraphs. 1-26. 78. Communication system containing the first network element of the network function according to any one of paragraphs. 27-34 and the second network element of the network function according to any one of paragraphs. 35-38. 79. Communication system containing the first network element of the network function according to any one of paragraphs. 27-34 and the fourth network function network element of claim 44 or 46. 80. The system according to claim 79, further comprising a second network element of the network function according to any one of paragraphs. 39-43. 81. Communication system containing the first network element of the network function according to any one of paragraphs. 27-34 and the fourth network function network element of claim 51 or 52. 82. The system of claim. 81, further comprising a second network element of the network function according to any one of paragraphs. 47-50.

Images