WO2019158049A1 - 订阅信息更新的方法及装置 - Google Patents

订阅信息更新的方法及装置 Download PDF

Info

Publication number
WO2019158049A1
WO2019158049A1 PCT/CN2019/074848 CN2019074848W WO2019158049A1 WO 2019158049 A1 WO2019158049 A1 WO 2019158049A1 CN 2019074848 W CN2019074848 W CN 2019074848W WO 2019158049 A1 WO2019158049 A1 WO 2019158049A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscription
information
association identifier
update
message
Prior art date
Application number
PCT/CN2019/074848
Other languages
English (en)
French (fr)
Inventor
刘合伦
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP19754005.7A priority Critical patent/EP3755049B1/en
Priority to JP2020565007A priority patent/JP7342038B2/ja
Priority to KR1020207026249A priority patent/KR102448192B1/ko
Publication of WO2019158049A1 publication Critical patent/WO2019158049A1/zh
Priority to US16/989,777 priority patent/US11824950B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/14—Mobility data transfer between corresponding nodes

Definitions

  • the present disclosure relates to the field of communications, and in particular, to a method and apparatus for updating subscription information.
  • the new wireless 5G protocol requires the user to register across the NF
  • the previously registered Old NF needs to transfer the subscription information to the newly registered New NF of the user
  • the New NF directly uses the subscription information transferred by the Old NF, including the subscription association identifier.
  • Subscription Correlation ID is used to identify this subscription relationship and is assigned by NF (Subscriber Provider of Subscription Information), which is unique within each NF.
  • the Consumer NF associates the Subscription Correlation ID with the current subscription, and subsequent notification messages for the subscription (NF notification Consumer NF subscription event) , or cancel/modify this subscription, carry this identifier (Identity, abbreviated as ID).
  • New NF directly uses the Assigned Correlation ID of Old NF, which cannot guarantee that the Subscription Correlation ID is unique on New NF, and may cause Old NF to fail to reclaim the Subscription Correlation ID in time.
  • Embodiments of the present disclosure provide a method and apparatus for updating subscription information to at least solve the problem of lack of a subscription information update scheme adapted to a new system in the related art.
  • a method for updating subscription information including: receiving, by a third network function NF, first subscription information sent by a second NF, where the first subscription information includes a second NF a first association identifier assigned by the first NF; the third NF assigns a second association identifier to the first NF, and sends the second association identifier to the first NF; the third NF receives the An update subscription message of the first NF, wherein the second update identifier is included in the update subscription message.
  • a method for updating subscription information comprising: a first network function NF establishing a subscription relationship with the second NF; the first NF receiving the third NF allocation a second association identifier, where the third NF receives the first subscription information that carries the subscription relationship after the second NF sends the first association information, and allocates the second association identifier to the first NF; An NF sends an update subscription message to the third NF, where the update subscription message includes the second association identifier.
  • an apparatus for updating subscription information including: a first receiving module, configured to receive first subscription information sent by a second NF, where the first subscription information includes The second NF is a first association identifier that is allocated by the first NF.
  • the first sending module is configured to allocate a second association identifier to the first NF, and send the second association identifier to the first NF.
  • a module configured to receive an update subscription message of the first NF, where the update subscription message includes the second association identifier.
  • an apparatus for updating subscription information comprising: an establishing module configured to establish a subscription relationship with the second NF; and a third receiving module configured to receive the third a second association identifier of the NF allocation, where the third NF receives the first subscription information that carries the subscription relationship after the second NF sends, and allocates the second to the NF to which the third receiving module belongs And a second sending module, configured to send an update subscription message to the third NF, where the update subscription message includes the second association identifier.
  • a storage medium having stored therein a computer program, wherein the computer program is configured to perform the steps of any one of the method embodiments described above at runtime.
  • an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor being configured to execute the computer program to perform any of the above The steps in the method embodiments.
  • FIG. 1 is a flowchart of a third NF side of a method 1 for subscription information update according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a first NF side of a method 1 for subscription information update according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a third NF side of a method 2 of subscription information update according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart of a third NF side of a method 3 of subscription information update according to an embodiment of the present disclosure
  • FIG. 5 is a flowchart of a first NF side of method 2 or method 3 of subscription information update according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of cross-office movement according to an exemplary embodiment 1;
  • FIG. 7 is a schematic flowchart of a New AMF generating an update message to a Consumer NF according to an exemplary embodiment 2, updating a subscription relationship;
  • FIG. 8 is a schematic diagram of an event communication message according to an exemplary embodiment 3.
  • FIG. 9 is a schematic flow chart according to an exemplary embodiment 4.
  • FIG. 10 is a flow chart according to an exemplary embodiment 5.
  • a mobile communication network including but not limited to a 5G mobile communication network
  • the network architecture of the network may include a network side device (for example, a base station) and a terminal.
  • a network side device for example, a base station
  • an information transmission method that can be run on the network architecture is provided. It should be noted that the operating environment of the foregoing information transmission method provided in the embodiment of the present application is not limited to the foregoing network architecture.
  • the third NF in the present application file may be the newly registered provider NF, and the second NF is the old registered provider Provider NF, the first NF is the consumer Consumer NF.
  • FIG. 1 is a flowchart of a third NF side of a method 1 for subscription information update according to an embodiment of the present disclosure, as shown in FIG. The process includes the following steps:
  • Step S102 The third network function NF receives the first subscription information sent by the second NF, where the first subscription information includes a first association identifier that is allocated by the second NF to the first NF.
  • Step S104 the third NF assigns a second association identifier to the first NF, and sends the second association identifier to the first NF;
  • Step S106 The third NF receives the update subscription message of the first NF, where the update subscription message includes the second association identifier.
  • the first NF is a consumer NF, subscribes to an event of a UE on the second NF, and the subsequent second NF transfers the user information to the new third NF, the third NF and the first Update subscription messages between NFs.
  • association identifier may be a Subscription Correlation ID.
  • the first NF information After the first NF transfers the first subscription information to the third NF, the first NF information includes a first association identifier assigned by the second NF to the first NF, where the third NF is the first NF allocation.
  • the second association identifier solves the problem that the subscription technology update scheme adapted to the new system is lacking in the related art, and proposes a subscription information update scheme adapted to the new system, for example, when a user terminal cross-NF registration occurs, the new one
  • the subscription message is updated in time between the three NFs and the first NF.
  • step S102 the execution sequence of step S102, step S104, and step S106 is interchangeable, that is, step S104 may be performed first, and then S102 is performed.
  • the third NF sends a first notification message to the first NF, where the first notification message carries the second association identifier.
  • sending the second association identifier to the first NF the third NF sending a second notification message to the first NF, where the second notification message is used to notify the first NF to send a resubscribe Receiving information to the third NF; receiving resubscribing information sent by the first NF; the third NF sending a subscription response to the first NF according to the resubscribing information, wherein the subscription response includes a second association identifier.
  • the first NF includes a consumer NF
  • the second NF includes a source provider NF
  • the third NF includes a destination provider NF.
  • the third NF sends at least one of the following information to the first NF: an identity authentication ID of the third NF, a subscription event Event in the first subscription information, and the first indicated in the first subscription information
  • the target content of NF may be the content of interest of the first NF.
  • the second NF cancels the subscription relationship between the first NF and the second NF.
  • FIG. 2 is a flowchart of a first NF side of a method 1 for subscription information update according to an embodiment of the present disclosure, as shown in FIG. 2 .
  • the method includes the following processes:
  • Step S202 the first network function NF establishes a subscription relationship with the second NF;
  • Step S204 the first NF receives the second association identifier that is allocated by the third NF, where the third NF receives the first subscription information that carries the subscription relationship after the second NF sends the first subscription information, and allocates the first NF to the first NF.
  • Two associated identifiers Two associated identifiers;
  • Step S206 the first NF sends an update subscription message to the third NF, where the update subscription message includes the second association identifier.
  • the first NF receives the second association identifier that is allocated by the third NF, and includes: receiving a first notification message that is sent by the third NF and that carries the second association identifier.
  • the first NF receives the second association identifier of the third NF, the first NF receives the second notification message sent by the third NF, and sends the second NF to the third NF according to the second notification message.
  • FIG. 3 is a flowchart of a third NF side of a method 2 for subscription information update according to an embodiment of the present disclosure, as shown in FIG.
  • the method includes the following processes:
  • Step S302 the third network function NF receives the first subscription information sent by the second NF, where the first subscription information includes a first association identifier that is allocated by the second NF to the first NF.
  • Step S304 the third NF notifies the first NF update subscription
  • Step S306 the third NF receives the second subscription request sent by the first NF, allocates a second association identifier to the first NF according to the second subscription request, and establishes the second subscription information.
  • the user equipment has previously registered the first NF.
  • the third NF notifies the first NF update subscription, and is configured to notify at least one of the following: an updated association identifier, an updated identity identifier of the provider NF, a subscribed event Event, the first Subscribing to the content of interest of the first NF indicated in the request.
  • the second NF receives the subscription information sent by the first NF; and the second NF cancels the second according to the subscription information.
  • FIG. 4 is a flowchart of a third NF side of a method 3 for subscription information update according to an embodiment of the present disclosure, as shown in FIG.
  • the method includes the following processes:
  • Step S402 the third network function NF receives the first subscription information sent by the second NF, where the first subscription information includes a first association identifier that is allocated by the second NF to the first NF.
  • Step S404 after detecting that the event that the user equipment is registered with the provider NF occurs, the third NF sends the following information in the event notification message for the first NF that has subscribed to the event in the first subscription information. At least one of: a first association identifier assigned by the second NF, an ID of the second NF, a second association identifier assigned by the third NF, and an ID of the third NF;
  • Step S406 the third NF sends a subscription update message to the second first NF, where the third NF is not subscribed to the event in the first subscription information, where the subscription update message includes the third NF.
  • the assigned second association identifier, and/or the identity authentication ID of the third NF are assigned to the third NF.
  • FIG. 5 is a flowchart of a first NF side of method 2 or method 3 of subscription information update according to an embodiment of the present disclosure, such as As shown in Figure 5, the process includes the following steps:
  • Step S502 the first NF sends a first subscription request to the second NF, and is used to establish first subscription information of the first NF and the second NF.
  • Step S504 Receive a subscription update message sent by the second NF, where the subscription update message is used to update the first subscription information.
  • receiving the subscription update message sent by the second NF includes: receiving an indication of the first NF update subscription sent by the newly registered third NF, where the user equipment corresponding to the first subscription information occurs across the NF Registering the event, and the third NF receives the first subscription information from the second NF transfer; and sends a second subscription request to the third NF, for establishing the second subscription information of the first NF and the third NF.
  • the first NF after receiving the indication of the first NF update subscription sent by the third NF, the first NF sends a subscription information to the second NF, to indicate that the second NF and the first NF are cancelled. Subscription relationship between.
  • receiving the subscription update message sent by the second NF includes one of: detecting that the user equipment crosses the NF registration, and the newly registered third NF receives the first subscription from the second NF transfer.
  • the event notification message sent by the third NF is received, where the event notification message includes at least one of the following information: the second a first association identifier assigned by the NF, an ID of the second NF, a second association identifier of the third NF assignment, an ID of the third NF, and a first NF that is not subscribed to the event in the first subscription information, and receives The subscription update message sent by the third NF, where the subscription update message includes a second association identifier of the third NF assignment, and/or an identity authentication ID of the third NF.
  • the NF in the present application file may be an Access and Mobility Management Function (AMF), a Session Management Function (SMF), and a Policy Control Function (Policy). Control Function (referred to as PCF), Unified Data Management (UDM), etc.
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • Policy Policy Control Function
  • UDM Unified Data Management
  • the following optional embodiment uses User Equipment (UE) as a cross-AMF registration as an example to describe this application. That is, the third NF is a new AMF newly registered by the user equipment, the second NF is the old AMF registered before the user equipment, the third NF and the second NF may be referred to as a provider Provider NF, and the first NF is a Consumer Consumer NF.
  • UE User Equipment
  • this application is not limited to cross-AMF registration.
  • the New AMF directly uses the Old AMF's assigned Subscription Correlation ID scheme, which leads to the following three problems:
  • the New AMF When the New AMF reports the mobility event, it carries the Subscription Correlation ID assigned by the old AMF. The Consumer NF will determine that the user moves to the New AMF, and the message is sent to the New AMF when the subscription is canceled. As a result, the assigned Correlation cannot be reclaimed on the Old AMF. ID resource.
  • the present disclosure can solve the above problems by using any of the following three technical solutions.
  • Solution 1 (Scheme 1 here is similar to Method 2 of the above embodiment): After receiving the subscription information transferred by Old AMF, New AMF immediately informs Consumer NF for all subscriptions, and subscribes to Old AMF by Consumer NF. And to make a new subscription to New AMF, New AMF assigns its own Subscription Correlation ID during the subscription process.
  • the New AMF immediately assigns its subscription Correlation ID after receiving the subscription information transferred by the Old AMF, and immediately sends a subscription update message to the corresponding Consumer.
  • NF may be multiple. Notifies the Consumer NF to update the Subscription Correlation ID and the event provider NF ID.
  • the Consumer NF saves and updates the received information and subsequently receives notifications of events from New AMF.
  • the subscription information on the Old AMF is deleted by the Old AMF itself, and the Consumer NF does not need to send a subscription to the Old AMF.
  • Solution 3 (Scheme 3 here is similar to Method 3 of the above embodiment).
  • New AMF allocates its own Subscription Correlation ID for all subscription relationships after receiving the subscription information brought by Old AMF.
  • For the Consumer NF that does not need to trigger the notification event after the end of the process immediately send a subscription update message to update the subscription's Subscription Correlation ID.
  • the Consumer NF that needs to trigger the event notification immediately after the process ends carries the old Subscription Correlation ID and the newly assigned Subscription Correlation ID in the event notification message, except for the event notification.
  • the synchronization also updates the Subscription Correlation ID and the provider NF ID.
  • the AMF notifies the Subscriber NF of the subscription update message mechanism, which is not limited to the AMF and the Consumer, and can be used for any general message mechanism in the 5G system to notify the Consumer NF subscription information update as the provider NF. It is not only used to notify the Subscription Correlation ID and the change of the information provider NF ID, but also to update other information of the subscription relationship, such as the subscribed mobility event Event information.
  • Exemplary Embodiment 1 After the inter-office move, the New AMF updates to the Consumer NF, triggers the Consumer NF to subscribe to the Old AMF, and makes a subscription request to the New AMF.
  • FIG. 6 is a schematic diagram of cross-office movement according to an exemplary embodiment 1, as shown in FIG.
  • S602 The Old AMF replies to the Consumer NF, carries the assigned Subscription Correlation ID, its own NF ID, and the like.
  • the Consumer NF receives the response, and all subsequent messages carry the Subscription Correlation ID.
  • the New AMF when registering across the AMF, the New AMF requests the UE context information from the Old AMF.
  • the Old AMF returns a UE context transfer response, bringing the subscription information, including the Subscription Correlation ID, to the New AMF.
  • the New AMF sends a subscription update request to the Consumer NF, carrying the Subscription Correlation ID and the NF ID of the Old AMF in the subscription relationship transferred by the Old AMF.
  • the Consumer NF sends a subscription request to the Old AMF, and uses a Subscription Correlation ID to indicate the subscription relationship.
  • Old AMF deletes the subscription relationship indicated by the Subscription Correlation ID, and returns the subscription response to the Consumer NF.
  • New AMF accepts the subscription request of Consumer NF, assigns a new Subscription Correlation ID, and deletes the subscription information transferred by Old AMF.
  • Exemplary Embodiment 2 New AMF sends an update message to Consumer NF, updating the subscription relationship
  • FIG. 7 is a schematic flowchart of a New AMF generating update message to a Consumer NF according to an exemplary embodiment 2, and updating a subscription relationship, as shown in FIG. 7, including the following steps:
  • the Old AMF returns a subscription response to the Consumer NF, carrying the assigned Subscription Correlation ID, its own NF ID, and the like.
  • the Consumer NF receives the response, and all subsequent messages carry the Subscription Correlation ID.
  • the New AMF when registering across the AMF, the New AMF requests the UE context information from the Old AMF.
  • the Old AMF sends a subscription response, including the Subscription Correlation ID, to the New AMF based on the UE context request feedback response.
  • New AMF allocates a new Subscription Correlation ID, and sends a subscription update request to the Consumer NF, where the message carries the Subscription Correlation ID (Old) in the subscription relationship transferred by the Old AMF, the NF ID of the Old AMF, and the new AMF allocation. Subscription Correlation ID and NF ID for New AMF.
  • the Consumer NF After receiving the subscription update message of the New AMF, the Consumer NF finds the subscription relationship according to the Old Subscription Correlation ID in the message, updates the Provider party's Subscription Correlation ID, and responds to the New AMF.
  • the deletion of the subscription relationship on the Old AMF does not require Consumer NF separate notification, and Old AMF deletes the subscription relationship for the user when deleting its user context.
  • Exemplary Embodiment 3 New AMF sends an update message to a partial Consumer NF to update a subscription relationship, and part of the Consumer NF is updated by an event notification message.
  • FIG. 8 is a schematic diagram of an event communication message according to an exemplary embodiment 3, as shown in FIG. 8, including the following steps:
  • the plurality of Consumer NF initiates a subscription request to the old AMF, wherein the Consumer NF-2 subscribes to the mobile event related to the user registration.
  • Old AMF assigns a unique Subscription Correlation ID within this AMF to each subscription;
  • the New AMF when registering across the AMF, the New AMF requests the UE context information from the Old AMF.
  • the Old AMF sends a subscription response, including the Subscription Correlation ID, to the New AMF based on the UE context request feedback response.
  • the New AMF needs to notify the Consumer NF of the mobility event immediately after the registration is successful.
  • Consumer NF-2 has previously subscribed to the mobility event generated during the user registration process, and New AMF immediately notifies the Consumer NF-2 mobility event.
  • the notification event also needs to carry the New AMF's newly assigned Subscription Correlation ID and New AMF's NF ID.
  • the Consumer NF-2 also updates the subscription Correlation ID of the subscription, and the subsequent mutual interaction message uses the new Subscription Correlation ID.
  • the exemplary embodiment 3 does not need to send a subscription update message to all the Consumer NFs, and may carry the new Subscription Correlation ID and the NF ID of the Provider side in the event notification message to update the subscription relationship. purpose.
  • Exemplary Embodiment 4 A subscription update is used as a general mechanism for transferring an update mechanism after a subscription relationship across a Provider NF.
  • FIG. 9 is a schematic flowchart diagram of an exemplary embodiment 4, as shown in FIG. 9, including the following steps:
  • the Consumer NF initiates a subscription request to the Old Provider NF, and the Old Provider NF allocates a unique Subscription Correlation ID in the NF for each subscription; where the Provider NF is AMF, SMF, PCF, UDM, and the like.
  • S902 The Old NF replies with a subscription response to all Consumer NFs, carries the assigned Subscription Correlation ID, its own NF ID, and the like.
  • the Consumer NF receives the response, and all subsequent messages carry the Subscription Correlation ID.
  • the user information is transferred between the NFs due to various reasons such as the user's location movement, and the Old NF may transfer the user information including the subscription relationship to the New NF. For example, the user initiates a handover process across AMF.
  • the New Provider NF generates a subscription update message to the Consumer NF, including but not limited to the Subscription Correlation ID and the NF ID of the Provider side.
  • the subscription update is used as a general mechanism for transferring the subscription mechanism after the subscription relationship across the Provider NF.
  • Provider NF can be AMF, SMF, PCF, UDM, etc.
  • the subscription relationship can be passed between NFs.
  • New NF can use the subscription update message to notify the Consumer NF to update the subscription information, including but not limited to the Subscription Correlation ID and the NF ID of the Provider side.
  • Subscription Update is a general mechanism for the Provider NF to actively notify the Consumer NF to update subscription information.
  • FIG. 10 is a schematic flowchart diagram of an exemplary embodiment 5, as shown in FIG. 10, including the following steps:
  • Consumer NF initiates a subscription request to the Provider NF, where the Provider NF is AMF, SMF, PCF, UDM, and the like.
  • the Provider NF when the Provider NF needs to notify the Consumer NF to update the subscription information due to changes in its own capabilities or other reasons, the Provider NF sends a subscription update message to the Consumer NF, including but not limited to the Subscription Correlation ID, the NF ID of the Provider, and the subscription. Events, information of interest to Consumer NF, etc.;
  • a device for updating the subscription information is provided, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • an apparatus for updating subscription information comprising:
  • the first receiving module is configured to receive the first subscription information sent by the second NF, where the first subscription information includes a first association identifier that is allocated by the second NF to the first NF;
  • the first sending module is configured to allocate a second associated identifier to the first NF, and send the second associated identifier to the first NF;
  • a second receiving module configured to receive an update subscription message of the first NF, where the update subscription message includes the second association identifier.
  • association identifier may be a Subscription Correlation ID.
  • the first NF information includes a first association identifier that is allocated by the second NF to the first NF, and the third NF is the first NF.
  • Assigning the second association identifier solves the problem that the subscription technology update scheme adapted to the new system is lacking in the related art, and proposes a subscription information update scheme adapted to the new system, for example, when a user terminal cross-NF registration occurs, the new one is The subscription message is updated in time between the third NF and the first NF.
  • the third NF sending a first notification message to the first NF, where the first notification message carries the first Two associated identifiers.
  • the third NF sending a second notification message to the first NF, where the second notification message is used to notify the The first NF sends resubscription information to the third NF; receives resubscribing information sent by the first NF; and the third NF sends a subscription response to the first NF according to the resubscribing information, where The second association identifier is included in the subscription response.
  • the first NF comprises a consumer NF
  • the second NF comprises a source provider NF
  • the third NF comprises a destination provider NF.
  • the third NF sends at least one of the following information to the first NF: an identity authentication ID of the third NF, a subscription event Event in the first subscription information, and the first subscription information.
  • the target content of the first NF indicated. It should be added that the target content may be the content of interest of the first NF.
  • the second NF cancels the subscription relationship between the first NF and the second NF.
  • an apparatus for updating subscription information comprising:
  • a third receiving module configured to receive the second associated identifier that is allocated by the third NF, where the third NF receives the first subscription information that is sent by the second NF to send the subscription relationship, The NF to which the third receiving module belongs allocates the second associated identifier;
  • the second sending module is configured to send an update subscription message to the third NF, where the update subscription message includes the second association identifier.
  • the receiving, by the first NF, the second association identifier that is allocated by the third NF includes: receiving, by the third NF, a first notification message that carries the second association identifier.
  • the receiving, by the first NF, the second association identifier of the third NF, the first NF receiving the second notification message sent by the third NF, according to the second notification message The third NF sends a re-subscription information; and receives a subscription response that is sent by the third NF according to the re-subscription information, where the subscription response includes a second association identifier.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • a storage medium having stored therein a computer program, wherein the computer program is configured to execute the method described in any one of the above embodiments .
  • an electronic device comprising a memory and a processor, wherein the computer stores a computer program, the processor being arranged to run the computer program to perform the above method.
  • the first NF information includes a first association identifier assigned by the second NF to the first NF
  • the third NF is the first NF allocation.
  • the third NF receives the update subscription message of the first NF, where the update subscription message includes the second association identifier, and adopting the foregoing solution to solve the lack of subscription information adapted to the new system in the related art.
  • a subscription information update scheme adapted to the new system is proposed. For example, when a cross-NF registration occurs in the user terminal, a new subscription message between the third NF and the first NF is implemented.
  • modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
  • Meter Arrangements (AREA)

Abstract

本公开提供了一种订阅信息更新的方法及装置，其中，该方法包括：第二NF向第三NF转移了第一订阅信息后，其中，第一订阅信息中包括第二NF为第一NF分配的第一关联标识，该第三NF为第一NF分配第二关联标识，该第三NF接收该第一NF的更新订阅消息，其中，该更新订阅消息中包括该第二关联标识，采用上述方案，解决了相关技术中缺乏适应于新系统的订阅信息更新方案的问题，提出了适应于新系统的订阅信息更新方案，例如出现用户终端发生跨NF注册的情况下，实现了新的第三NF与第一NF之间及时更新订阅消息。

Description

订阅信息更新的方法及装置
相关申请的交叉引用
本公开要求于2018年2月13日提交的中国专利申请No.201810149926.5的优先权，其全部内容通过引用结合在本文中。
技术领域
本公开涉及通信领域，具体而言，涉及一种订阅信息更新的方法及装置。
背景技术
在相关技术中，新无线5G协议要求用户跨NF注册时，之前注册的Old NF需要将订阅信息转移到用户新注册的New NF，New NF直接使用Old NF转移过来的订阅信息，包括订阅关联标识Subscription Correlation ID。Subscription Correlation ID用于标识本次订阅关系，由NF(订阅信息的提供方Provider)分配，在每个NF内唯一。并在订阅响应消息中携带给订阅发起者Consumer NF(或称为消费者NF)，Consumer NF将Subscription Correlation ID和本次订阅关联起来，后续针对此订阅的通知消息(NF通知Consumer NF订阅事件)，或取消/修改本次订阅，都携带此标识(Identity，简称为ID)。
但New NF直接使用Old NF的分配的Subscription Correlation ID，无法保证该Subscription Correlation ID在New NF上也是唯一，以及可能导致Old NF无法及时回收Subscription Correlation ID。
针对相关技术中缺乏适应于新系统的订阅信息更新方案的问题，目前还没有有效的解决方案。
发明内容
本公开实施例提供了一种订阅信息更新的方法及装置，以至少解决相关技术中缺乏适应于新系统的订阅信息更新方案的问题。
根据本公开的一个实施例，提供了一种订阅信息更新的方法，包括：第三网络功能NF收到第二NF发送的第一订阅信息，其中，所述第一订阅信息包括第二NF为第一NF分配的第一关联标识；所述第三NF为所述第一NF分配第二关联标识，并发送所述第二关联标识至所述第一NF；所述第三NF接收所述第一NF的更新订阅消息，其中，所述更新订阅消息中包括所述第二关联标识。
根据本公开的另一个实施例，还提供了一种订阅信息更新的方法，包括：第一网络功能NF建立与所述第二NF的订阅关系；所述第一NF接收所述第三NF分配的第二关联标识，其中，所述第三NF接收到所述第二NF发送携带所述订阅关系的第一订阅信息之后，为所述第一NF分配所述第二关联标识；所述第一NF发送更新订阅消息至所述第三NF，其中， 所述更新订阅消息中包括所述第二关联标识。
根据本公开的另一个实施例，还提供了一种订阅信息更新的装置，包括：第一接收模块，设置为接收第二NF发送的第一订阅信息，其中，所述第一订阅信息包括第二NF为第一NF分配的第一关联标识；第一发送模块，设置为为所述第一NF分配第二关联标识，并发送所述第二关联标识至所述第一NF；第二接收模块，设置为接收所述第一NF的更新订阅消息，其中，所述更新订阅消息中包括所述第二关联标识。
根据本公开的另一个实施例，还提供了一种订阅信息更新的装置，包括：建立模块，设置为建立与所述第二NF的订阅关系；第三接收模块，设置为接收所述第三NF分配的第二关联标识，其中，所述第三NF接收到所述第二NF发送携带所述订阅关系的第一订阅信息之后，为所述第三接收模块归属的NF分配所述第二关联标识；第二发送模块，设置为发送更新订阅消息至所述第三NF，其中，所述更新订阅消息中包括所述第二关联标识。
根据本公开的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是根据本公开实施例的一种订阅信息更新的方法一的第三NF侧的流程图；
图2是根据本公开实施例的一种订阅信息更新的方法一的第一NF侧的流程图；
图3是根据本公开实施例的一种订阅信息更新的方法二的第三NF侧的流程图；
图4是根据本公开实施例的一种订阅信息更新的方法三的第三NF侧的流程图；
图5是根据本公开实施例的一种订阅信息更新的方法二或方法三的第一NF侧的流程图；
图6是根据示例性实施例1的跨局移动的示意图；
图7是根据示例性实施例2的New AMF向Consumer NF发生更新消息，更新订阅关系的流程示意图；
图8是根据示例性实施例3的事件通信消息示意图；
图9是根据示例性实施例4的流程示意图；
图10是根据示例性实施例5的流程示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二” 等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例中提供了一种移动通信网络(包括但不限于5G移动通信网络)，该网络的网络架构可以包括网络侧设备(例如基站)和终端。在本实施例中提供了一种可运行于上述网络架构上的信息传输方法，需要说明的是，本申请实施例中提供的上述信息传输方法的运行环境并不限于上述网络架构。
在用户终端跨网络功能(Net Function，简称为NF)注册的情况下，本申请文件中的第三NF可以为新注册的提供者NF，第二NF为旧注册的提供者Provider NF，第一NF为消费者Consumer NF。
实施例一
在本实施例中提供了一种运行于上述网络架构的订阅信息更新方法，图1是根据本公开实施例的一种订阅信息更新的方法一的第三NF侧的流程图，如图1所示，该流程包括如下步骤：
步骤S102，第三网络功能NF收到第二NF发送的第一订阅信息，其中，该第一订阅信息包括第二NF为第一NF分配的第一关联标识；
步骤S104，该第三NF为该第一NF分配第二关联标识，并发送该第二关联标识至该第一NF；
步骤S106，该第三NF接收该第一NF的更新订阅消息，其中，该更新订阅消息中包括该第二关联标识。
可选地，上述实施例中第一NF是消费者NF，订阅了第二NF上的某个UE的事件，后续第二NF将用户信息转移到新的第三NF，第三NF与第一NF之间更新订阅消息。
需要补充的是，上述关联标识可以是Subscription Correlation ID。
通过上述步骤，第二NF向第三NF转移了第一订阅信息后，其中，第一订阅信息中包括第二NF为第一NF分配的第一关联标识，该第三NF为第一NF分配第二关联标识，解决了相关技术中缺乏适应于新系统的订阅信息更新方案的问题，提出了适应于新系统的订阅信息更新方案，例如出现用户终端发生跨NF注册的情况下，新的第三NF与第一NF之间及时更新订阅消息。
可选地，步骤S102、步骤S104，步骤S106的执行顺序是可以互换的，即可以先执行步骤S104，然后再执行S102。
可选地，发送该第二关联标识至该第一NF，包括：该第三NF向该第一NF发送第一通知消息，其中，该第一通知消息携带有该第二关联标识。
可选地，发送该第二关联标识至该第一NF，包括：该第三NF向该第一NF发送第二通知消息，其中，该第二通知消息用于通知该第一NF发送重新订阅信息至该第三NF；接收该第一NF发送的重新订阅信息；该第三NF依据该重新订阅信息发送订阅响应至该第一NF，其中，该订阅响应中包括第二关联标识。
可选地，该第一NF包括消费者NF，该第二NF包括源提供者NF，该第三NF包括目的提供者NF。
可选地，该第三NF发送以下信息至少之一至该第一NF：该第三NF的身份认证ID、该第一订阅信息中的订阅事件Event、该第一订阅信息中指示的该第一NF的目标内容。需要补充的是，该目标内容可以是第一NF感兴趣的内容。
可选地，第三网络功能NF收到第二NF发送的第一订阅信息之后，该第二NF取消该第一NF与该第二NF之间的订阅关系。
根据本公开的另一个实施例，还提供了一种订阅信息更新的方法，图2是根据本公开实施例的一种订阅信息更新的方法一的第一NF侧的流程图，如图2所示，该方法包括以下流程：
步骤S202，第一网络功能NF建立与第二NF的订阅关系；
步骤S204，该第一NF接收第三NF分配的第二关联标识，其中，该第三NF接收到该第二NF发送携带该订阅关系的第一订阅信息之后，为该第一NF分配该第二关联标识；
步骤S206，该第一NF发送更新订阅消息至该第三NF，其中，该更新订阅消息中包括该第二关联标识。
可选地，该第一NF接收该第三NF分配的第二关联标识，包括：接收该第三NF发送的携带有该第二关联标识的第一通知消息。
可选地，该第一NF接收该第三NF分配的第二关联标识，包括：该第一NF接收该第三NF发送的第二通知消息；依据该第二通知消息向该第三NF发送重新订阅信息；接收该第三NF依据该重新订阅信息反馈的订阅响应，其中，该订阅响应中包括第二关联标识。
根据本公开的另一个实施例，还提供了一种订阅信息更新的方法，图3是根据本公开实施例的一种订阅信息更新的方法二的第三NF侧的流程图，如图3所示，该方法包括以下流程：
步骤S302，第三网络功能NF收到第二NF发送的第一订阅信息，其中，该第一订阅信息包括第二NF为第一NF分配的第一关联标识；
步骤S304，该第三NF通知该第一NF更新订阅；
步骤S306，该第三NF接收到该第一NF发送的第二订阅请求，依据该第二订阅请求为该第一NF分配第二关联标识，并建立该第二订阅信息。
可选地，该用户设备之前已经注册该第一NF。
可选地，该第三NF通知该第一NF更新订阅，用于通知以下内容至少之一：更新后的关联标识、更新后的提供者NF的身份认证ID、订阅的事件Event、该第一订阅请求中指示的该第一NF感兴趣的内容。
可选地，该第三NF通知该订阅信息对应的第一NF更新订阅之后，该第二NF接收到该第一NF发送的去订阅信息；该第二NF依据该去订阅信息取消该第二NF与该第一NF之间的订阅关系。
根据本公开的另一个实施例，还提供了一种订阅信息更新的方法，图4是根据本公开实施例的一种订阅信息更新的方法三的第三NF侧的流程图，如图4所示，该方法包括以下流程：
步骤S402，第三网络功能NF收到第二NF发送的第一订阅信息，其中，该第一订阅信息包括第二NF为第一NF分配的第一关联标识；
步骤S404，在检测到发生该用户设备跨该提供者NF注册的事件后，针对在该第一订阅信息中已经订阅了该事件的第一NF，该第三NF在事件通知消息中发送以下信息至少之一：该第二NF分配的第一关联标识，该第二NF的ID，该第三NF分配的第二关联标识，该第三NF的ID；
步骤S406，针对在该第一订阅信息中未订阅该事件的第二第一NF，该第三NF向该第二第一NF发送订阅更新消息，其中，该订阅更新消息中包括该第三NF分配的第二关联标识，和/或该第三NF的身份认证ID。
根据本公开的另一个实施例，还提供了一种订阅信息更新的方法，图5是根据本公开实施例的一种订阅信息更新的方法二或方法三的第一NF侧的流程图，如图5所示，该流程包括以下步骤：
步骤S502，第一NF发送第一订阅请求至第二NF，用于建立该第一NF与该第二NF的第一订阅信息；
步骤S504，接收该第二NF发送的订阅更新消息，其中，该订阅更新消息用于更新该第一订阅信息。
可选地，接收该第二NF发送的订阅更新消息包括：接收到该新注册的第三NF发送的该第一NF更新订阅的指示，其中，该第一订阅信息对应的用户设备发生跨NF注册事件，且第三NF接收到第二NF转移来的该第一订阅信息；向该第三NF发送第二订阅请求，用于建立该第一NF与该第三NF的第二订阅信息。
可选地，接收到该第三NF发送的该第一NF更新订阅的指示之后，该第一NF向该第二NF发送去订阅信息，用于指示取消该第二NF与该第一NF之间的订阅关系。
可选地，接收该第二NF发送的订阅更新消息包括以下之一：在检测到发生该用户设备跨该NF注册，且新注册的第三NF接收到第二NF转移来的该第一订阅信息的事件后，在该第一订阅信息中已经订阅了该事件的第一NF，接收该第三NF发送的事件通知消息，其中，该事件通知消息中包括以下信息至少之一：该第二NF分配的第一关联标识，该第二NF的ID，该第三NF分配的第二关联标识，该第三NF的ID；在该第一订阅信息中未订阅该事件的第一NF，接收该第三NF发送的订阅更新消息，其中，该订阅更新消息中包括该第三NF分配的第二关联标识，和/或该第三NF的身份认证ID。
下面结合本公开可选实施例进行详细说明。
需要补充的是，本申请文件中的NF可以为接入和移动性管理功能(Access and Mobility Management Function，简称为AMF)，会话管理功能(Session Management Function，简称为SMF)，策略控制功能(Policy Control Function，简称为PCF)，统一数据管理(Unified Data Management，简称为UDM)等，下面的可选实施例以用户设备(User Equipment，简称为UE)跨AMF注册为例来详细说明本申请文件，即第三NF为用户设备新注册的新AMF，第二NF为用户设备之前注册的旧AMF，第三NF和第二NF可以称为提供者Provider NF，第一 NF为消费者Consumer NF，但是本申请文件不局限于跨AMF注册。
在用户设备跨NF注册时，采用New AMF直接使用Old AMF的分配的Subscription Correlation ID的方案，会导致如下三个问题：
1，由于Subscription Correlation ID的分配要求是NF内部唯一，Old AMF的订阅资源带给New AMF之后，无法保证该Subscription Correlation ID在New AMF上也是唯一。
2，New AMF上报移动性事件时，携带old AMF分配的Subscription Correlation ID，Consumer NF会认定用户移动到New AMF，取消订阅时消息发送给New AMF，导致Old AMF上无法回收已经分配出的Subscription Correlation ID资源。
3，在New AMF上报移动性事件之前，Consumer NF取消订阅时，去订阅消息仍旧发送给Old AMF，Old AMF无法转给New AMF，New AMF上的订阅信息无法及时取消。
针对上述跨AMF传递订阅信息，存在的问题，本公开可以采用如下三种技术方案中任一者来解决上述问题。
方案一(此处的方案一类似于上述实施例的方法二)：New AMF收到Old AMF转移过来的订阅信息之后，针对所有的订阅，立即通知Consumer NF，由Consumer NF向Old AMF去订阅，并向New AMF进行新的订阅，New AMF在订阅过程中分配自己Subscription Correlation ID。
方案二(此处的方案而类似于上述实施例的方法一)，New AMF在收到Old AMF转移过来的订阅信息之后，立即分配自己的Subscription Correlation ID，并立即发送订阅更新消息给对应的Consumer NF(可以是多个)。通知Consumer NF更新Subscription Correlation ID和事件提供方NF ID。Consumer NF保存并更新接收到的信息，后续接受New AMF的事件通知。Old AMF上的订阅信息由Old AMF自身删除，Consumer NF不需要向Old AMF发送去订阅。
方案三(此处的方案三类似于上述实施例的方法三)，跨AMF的流程中，New AMF在收到Old AMF带过来的订阅信息之后，针对所有的订阅关系，分配自己的Subscription Correlation ID；对于本次流程结束之后不需要触发通知事件的Consumer NF，立即发送订阅更新消息，更新订阅的Subscription Correlation ID。但对于已经订阅了本次流程触发事件的Consumer NF，在流程结束之后需要立即触发事件通知的Consumer NF，在事件通知消息中携带老的Subscription Correlation ID和新分配的Subscription Correlation ID，除了事件通知之外，同步还进行Subscription Correlation ID和提供方NF ID的更新。
进一步，AMF通知Consumer NF的订阅更新消息机制，不限于AMF和Consumer之间，可以用于5G系统内任何作为提供方NF通知消费方Consumer NF订阅信息更新的通用消息机制。不仅仅用于通知订阅费Subscription Correlation ID和信息提供方NF ID的变化，还可以用于更新订阅关系的其他信息，比如订阅的移动性事件Event信息。
下面结合本公开具体实施例进一步说明
示例性实施例1：跨局移动后，New AMF向Consumer NF更新，触发Consumer NF向Old AMF去订阅，向New AMF进行订阅请求。
图6是根据示例性实施例1的跨局移动的示意图，如图6所示：
S601，Consumer NF向old AMF发起订阅请求。Old AMF针对本次订阅分配了本AMF内唯一的Subscription Correlation ID；
S602，Old AMF给Consumer NF回复响应，携带所分配的Subscription Correlation ID，自身NF ID等。Consumer NF收到响应，后续所有的消息都要携带Subscription Correlation ID。
S603，用户位置移动，向AMF发起注册请求。
S604和S605，跨AMF的注册时，New AMF向Old AMF请求UE上下文信息。Old AMF返回UE上下文传送响应，将订阅信息，包括Subscription Correlation ID带给New AMF。
S606，执行注册流程剩余步骤，直至注册成功结束。
S607，New AMF向Consumer NF发送订阅更新请求，携带Old AMF转移过来的订阅关系中的Subscription Correlation ID和Old AMF的NF ID。
S608，Consumer NF向Old AMF发送去订阅请求，使用Subscription Correlation ID指示订阅关系。
S609，Old AMF删除Subscription Correlation ID指示的订阅关系，给Consumer NF回去订阅响应。
S610，Consumer NF向New AMF发送订阅请求。
S611，New AMF接受Consumer NF的订阅请求，分配新的Subscription Correlation ID，同时删除Old AMF转过来的订阅信息。
示例性实施例2：New AMF向Consumer NF发生更新消息，更新订阅关系
图7是根据示例性实施例2的New AMF向Consumer NF发生更新消息，更新订阅关系的流程示意图，如图7所示，包括以下步骤：
S701，Consumer NF向old AMF发起订阅请求。Old AMF针对本次订阅分配了本AMF内唯一的Subscription Correlation ID；
S702，Old AMF给Consumer NF回复订阅响应，携带所分配的Subscription Correlation ID，自身NF ID等。Consumer NF收到响应，后续所有的消息都要携带Subscription Correlation ID。
S703，用户位置移动，向AMF发起注册请求。
S704和S705，跨AMF的注册时，New AMF向Old AMF请求UE上下文信息。Old AMF依据UE上下文请求反馈响应，将订阅信息，包括Subscription Correlation ID带给New AMF。
S706，执行注册流程剩余步骤，直至注册成功结束。
S707，New AMF分配新的Subscription Correlation ID，并向Consumer NF发送订阅更新请求，消息中携带Old AMF转移过来的订阅关系中的Subscription Correlation ID(Old)、Old AMF的NF ID、New AMF分配的新Subscription Correlation ID和New AMF的NF ID。
S708，Consumer NF收到New AMF的订阅更新消息之后，根据其中的消息中的Old Subscription Correlation ID找到订阅关系，更新Provider方的Subscription Correlation ID，并给New AMF回复响应。Old AMF上订阅关系的删除不需要Consumer NF单独通知，由Old AMF在删除其用户上下文时删除针对该用户的订阅关系即可。
示例性实施例3：New AMF向部分Consumer NF发送更新消息更新订阅关系，部分Consumer NF通过事件通知消息进行更新
图8是根据示例性实施例3的事件通信消息示意图，如图8所示，包括以下步骤：
S801，多个Consumer NF向old AMF发起订阅请求，其中Consumer NF-2订阅了用户注册相关的移动事件。Old AMF针对各个订阅分配了本AMF内唯一的Subscription Correlation ID；
S802，Old AMF给所有Consumer NF回复响应，携带所分配的Subscription Correlation ID，自身NF ID等。Consumer NF收到响应，后续所有的消息都要携带Subscription Correlation ID。
S803，用户位置移动，向AMF发起注册请求。
S804和S805，跨AMF的注册时，New AMF向Old AMF请求UE上下文信息。Old AMF依据UE上下文请求反馈响应，将订阅信息，包括Subscription Correlation ID带给New AMF。
S806，执行注册流程剩余步骤，直至注册成功。
S807，如果部分Consumer NF已经订阅了用户注册过程产生的移动性事件，New AMF需要在注册成功之后立即通知Consumer NF的移动性事件。比如本示例性实施例中Consumer NF-2此前订阅了用户注册过程中产生的移动性事件，则New AMF立即通知Consumer NF-2移动性事件。但在该通知事件中除了携带Old AMF的Subscription Correlation ID和NF ID之外，还需要携带New AMF新分配的Subscription Correlation ID和New AMF的NF ID。Consumer NF-2除了接收移动性事件之外，还要更新该订阅的Subscription Correlation ID，后续双方交互消息中使用新的Subscription Correlation ID。
S808和S809，对于注册之后不需要通知的Consumer NF，比如Consumer NF-1没有订阅注册所产生的移动性事件，New AMF需要立即发送更新消息。便于Consumer NF更新Subscription Correlation ID和Provider方的NF ID。此步同示例性实施例2中的S707和S708。
相比于示例性实施例2，本示例性实施例3不需要给所有Consumer NF发送订阅更新消息，可以在事件通知消息中携带新的Subscription Correlation ID和Provider方的NF ID，达到更新订阅关系的目的。
示例性实施例4：订阅更新作为通用机制用于跨Provider NF转移订阅关系后的更新机制。
图9是根据示例性实施例4的流程示意图，如图9所示，包括以下步骤:
S901，Consumer NF向Old Provider NF发起订阅请求，Old Provider NF针对各个订阅分配了本NF内唯一的Subscription Correlation ID；此处Provider NF为AMF、SMF、PCF、UDM等。
S902，Old NF给所有Consumer NF回复订阅响应，携带所分配的Subscription Correlation ID，自身NF ID等。Consumer NF收到响应，后续所有的消息都要携带Subscription Correlation ID。
S903，因用户位置移动等各种原因，导致用户信息在NF之间转移，Old NF可以将包含 订阅关系的用户信息转移到New NF。例如在用户发起跨AMF的切换流程。
S904和S905，New Provider NF向Consumer NF发生订阅更新消息，包括但不限于Subscription Correlation ID和Provider方的NF ID。
本示例性实施例中，订阅更新作为通用机制用于跨Provider NF转移订阅关系后的更新机制。此处Provider NF可以为AMF、SMF、PCF、UDM等。只要涉及用户信息在两个同类NF之间转移的，都可以将订阅关系在NF之间传递。并且New NF都可以使用订阅更新消息，通知Consumer NF更新订阅信息，包括但不限于Subscription Correlation ID和Provider方的NF ID。
示例性实施例5：订阅更新作为通用机制，用于Provider NF主动通知Consumer NF更新订阅信息。
图10是根据示例性实施例5的流程示意图，如图10所示，包括以下步骤：
S1001，Consumer NF向Provider NF发起订阅请求，此处Provider NF为AMF、SMF、PCF、UDM等。
S1002，Provider NF给Consumer NF回复响应。
S1003，当Provider NF因自身能力变化或其他原因，导致需要通知Consumer NF更新订阅信息时，Provider NF向Consumer NF发送订阅更新消息，更新内容包括但不限于Subscription Correlation ID、Provider方的NF ID、订阅的Event、Consumer NF感兴趣的信息等内容；
S1004，Consumer NF向Provider NF返回订阅更新响应。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
实施例二
在本实施例中还提供了一种订阅信息更新的装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
根据本公开的另一个实施例，还提供了一种订阅信息更新的装置，该装置包括：
第一接收模块，设置为接收第二NF发送的第一订阅信息，其中，所述第一订阅信息包括第二NF为第一NF分配的第一关联标识；
第一发送模块，设置为为所述第一NF分配第二关联标识，并发送所述第二关联标识至所述第一NF；
第二接收模块，设置为接收所述第一NF的更新订阅消息，其中，所述更新订阅消息中 包括所述第二关联标识。
需要补充的是，上述关联标识可以是Subscription Correlation ID。
通过上述步骤，第二NF向第三NF转移了第一订阅信息后，其中，第一订阅信息中包括第二NF为第一NF分配的第一关联标识，所述第三NF为第一NF分配第二关联标识，解决了相关技术中缺乏适应于新系统的订阅信息更新方案的问题，提出了适应于新系统的订阅信息更新方案，例如出现用户终端发生跨NF注册的情况下，新的第三NF与第一NF之间及时更新订阅消息。
可选地，发送所述第二关联标识至所述第一NF，包括：所述第三NF向所述第一NF发送第一通知消息，其中，所述第一通知消息携带有所述第二关联标识。
可选地，发送所述第二关联标识至所述第一NF，包括：所述第三NF向所述第一NF发送第二通知消息，其中，所述第二通知消息用于通知所述第一NF发送重新订阅信息至所述第三NF；接收所述第一NF发送的重新订阅信息；所述第三NF依据所述重新订阅信息发送订阅响应至所述第一NF，其中，所述订阅响应中包括第二关联标识。
可选地，所述第一NF包括消费者NF，所述第二NF包括源提供者NF，所述第三NF包括目的提供者NF。
可选地，所述第三NF发送以下信息至少之一至所述第一NF：所述第三NF的身份认证ID、所述第一订阅信息中的订阅事件Event、所述第一订阅信息中指示的所述第一NF的目标内容。需要补充的是，该目标内容可以是第一NF感兴趣的内容。
可选地，第三网络功能NF收到第二NF发送的第一订阅信息之后，所述第二NF取消所述第一NF与所述第二NF之间的订阅关系。
根据本公开的另一个实施例，还提供了一种订阅信息更新的装置，该装置包括：
建立模块，设置为建立与所述第二NF的订阅关系；
第三接收模块，设置为接收所述第三NF分配的第二关联标识，其中，所述第三NF接收到所述第二NF发送携带所述订阅关系的第一订阅信息之后，为所述第三接收模块归属的NF分配所述第二关联标识；
第二发送模块，设置为发送更新订阅消息至所述第三NF，其中，所述更新订阅消息中包括所述第二关联标识。
可选地，所述第一NF接收所述第三NF分配的第二关联标识，包括：接收所述第三NF发送的携带有所述第二关联标识的第一通知消息。
可选地，所述第一NF接收所述第三NF分配的第二关联标识，包括：所述第一NF接收所述第三NF发送的第二通知消息；依据所述第二通知消息向所述第三NF发送重新订阅信息；接收所述第三NF依据所述重新订阅信息反馈的订阅响应，其中，所述订阅响应中包括第二关联标识。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例三
根据本公开的另一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述实施例任一项中所述的方法。
实施例四
根据本公开的另一个实施例，还提供了一种电子装置，包括存储器和处理器，其中，存储器中存储有计算机程序，处理器被设置为运行所述计算机程序以执行上述方法。
通过本公开，第二NF向第三NF转移了第一订阅信息后，其中，第一订阅信息中包括第二NF为第一NF分配的第一关联标识，该第三NF为第一NF分配第二关联标识，该第三NF接收该第一NF的更新订阅消息，其中，该更新订阅消息中包括该第二关联标识，采用上述方案，解决了相关技术中缺乏适应于新系统的订阅信息更新方案的问题，提出了适应于新系统的订阅信息更新方案，例如出现用户终端发生跨NF注册的情况下，实现了新的第三NF与第一NF之间及时更新订阅消息。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (13)

  1. 一种订阅信息更新的方法，包括：
    第三网络功能NF收到第二NF发送的第一订阅信息，其中，所述第一订阅信息包括第二NF为第一NF分配的第一关联标识；
    所述第三NF为所述第一NF分配第二关联标识，并发送所述第二关联标识至所述第一NF；
    所述第三NF接收所述第一NF的更新订阅消息，其中，所述更新订阅消息中包括所述第二关联标识。
  2. 根据权利要求1所述的方法，其中，发送所述第二关联标识至所述第一NF，包括：
    所述第三NF向所述第一NF发送第一通知消息，其中，所述第一通知消息携带有所述第二关联标识。
  3. 根据权利要求1所述的方法，其中，发送所述第二关联标识至所述第一NF，包括：
    所述第三NF向所述第一NF发送第二通知消息，其中，所述第二通知消息设置为通知所述第一NF发送重新订阅信息至所述第三NF；
    接收所述第一NF发送的重新订阅信息；
    所述第三NF依据所述重新订阅信息发送订阅响应至所述第一NF，其中，所述订阅响应中包括第二关联标识。
  4. 根据权利要求1所述的方法，其中，所述第一NF包括消费者NF，所述第二NF包括源提供者NF，所述第三NF包括目的提供者NF。
  5. 根据权利要求1所述的方法，其中，所述方法还包括：所述第三NF发送以下信息至少之一至所述第一NF：
    所述第三NF的身份认证ID、所述第一订阅信息中的订阅事件Event、所述第一订阅信息中指示的所述第一NF的目标内容。
  6. 根据权利要求1所述的方法，其中，第三网络功能NF收到第二NF发送的第一订阅信息之后，所述方法还包括：
    所述第二NF取消所述第一NF与所述第二NF之间的订阅关系。
  7. 一种订阅信息更新的方法，其中，包括：
    第一网络功能NF建立与第二NF的订阅关系；
    所述第一NF接收第三NF分配的第二关联标识，其中，所述第三NF接收到所述第二NF发送携带所述订阅关系的第一订阅信息之后，为所述第一NF分配所述第二关联标识；
    所述第一NF发送更新订阅消息至所述第三NF，其中，所述更新订阅消息中包括所述第二关联标识。
  8. 根据权利要求7所述的方法，其中，所述第一NF接收所述第三NF分配的第二关联标识，包括：
    接收所述第三NF发送的携带有所述第二关联标识的第一通知消息。
  9. 根据权利要求7所述的方法，其中，所述第一NF接收所述第三NF分配的第二关联标识，包括：
    所述第一NF接收所述第三NF发送的第二通知消息；
    依据所述第二通知消息向所述第三NF发送重新订阅信息；
    接收所述第三NF依据所述重新订阅信息反馈的订阅响应，其中，所述订阅响应中包括第二关联标识。
  10. 一种订阅信息更新的装置，其中，包括：
    第一接收模块，设置为接收第二NF发送的第一订阅信息，其中，所述第一订阅信息包括第二NF为第一NF分配的第一关联标识；
    第一发送模块，设置为为所述第一NF分配第二关联标识，并发送所述第二关联标识至所述第一NF；
    第二接收模块，设置为接收所述第一NF的更新订阅消息，其中，所述更新订阅消息中包括所述第二关联标识。
  11. 一种订阅信息更新的装置，包括：
    建立模块，设置为建立与第二NF的订阅关系；
    第三接收模块，设置为接收第三NF分配的第二关联标识，其中，所述第三NF接收到所述第二NF发送携带所述订阅关系的第一订阅信息之后，为所述第三接收模块归属的NF分配所述第二关联标识；
    第二发送模块，设置为发送更新订阅消息至所述第三NF，其中，所述更新订阅消息中包括所述第二关联标识。
  12. 一种存储介质，其中，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至9任一项中所述的方法。
  13. 一种订阅信息更新的设备，包括存储器和处理器，其中，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至9任一项中所述的方法。
PCT/CN2019/074848 2018-02-13 2019-02-12 订阅信息更新的方法及装置 WO2019158049A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP19754005.7A EP3755049B1 (en) 2018-02-13 2019-02-12 Subscription information update method and apparatus
JP2020565007A JP7342038B2 (ja) 2018-02-13 2019-02-12 サブスクリプション情報更新の方法および装置
KR1020207026249A KR102448192B1 (ko) 2018-02-13 2019-02-12 구독 정보를 업데이트하는 방법 및 장치
US16/989,777 US11824950B2 (en) 2018-02-13 2020-08-10 Subscription information update method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810149926.5 2018-02-13
CN201810149926.5A CN110167080A (zh) 2018-02-13 2018-02-13 订阅信息更新的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/989,777 Continuation US11824950B2 (en) 2018-02-13 2020-08-10 Subscription information update method and apparatus

Publications (1)

Publication Number Publication Date
WO2019158049A1 true WO2019158049A1 (zh) 2019-08-22

Family

ID=67618903

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/074848 WO2019158049A1 (zh) 2018-02-13 2019-02-12 订阅信息更新的方法及装置

Country Status (6)

Country Link
US (1) US11824950B2 (zh)
EP (1) EP3755049B1 (zh)
JP (1) JP7342038B2 (zh)
KR (1) KR102448192B1 (zh)
CN (1) CN110167080A (zh)
WO (1) WO2019158049A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114520832A (zh) * 2020-11-19 2022-05-20 腾讯科技（深圳）有限公司 一种数据流处理方法、装置、设备及计算机存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2885801T3 (es) * 2018-11-14 2021-12-15 Ericsson Telefon Ab L M Detección de reinicio de consumidor de servicios de NF utilizando señalización directa entre NF
WO2024012064A1 (en) * 2022-07-15 2024-01-18 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for event report
EP4307741A1 (en) * 2022-07-15 2024-01-17 Nokia Technologies Oy Methods and apparatus for subscription authorization enhancement
CN116737405B (zh) * 2022-10-24 2024-03-05 荣耀终端有限公司 一种快应用卡片的数据通信的方法及相关设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103765951A (zh) * 2011-06-10 2014-04-30 电话有限公司 一种用于无线通信系统中的小区重选和小区切换的方法
US20150358248A1 (en) * 2014-06-09 2015-12-10 Nokia Solutions And Networks Oy Controlling of virtualized network functions for usage in communication network

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9385862B2 (en) * 2010-06-16 2016-07-05 Qualcomm Incorporated Method and apparatus for binding subscriber authentication and device authentication in communication systems
US20110312299A1 (en) * 2010-06-18 2011-12-22 Qualcomm Incorporated Methods and apparatuses facilitating synchronization of security configurations
US9277047B2 (en) * 2012-03-22 2016-03-01 Telefonaktiebolaget L M Ericsson (Publ) Technology for operating network nodes of a communication network
US9629020B2 (en) * 2013-05-28 2017-04-18 Rivada Networks, Llc Methods and systems for data context and management via dynamic spectrum controller and dynamic spectrum policy controller
US9094958B2 (en) * 2013-05-29 2015-07-28 Rivada Networks, Llc Methods and systems for dynamic spectrum arbitrage user profile management
CN103618800B (zh) * 2013-12-05 2017-11-03 华为技术有限公司 订阅通知的实现方法和装置
US20190021064A1 (en) * 2016-07-04 2019-01-17 Lg Electronics Inc. Method for managing registration in wireless communication system and device for same
US10652784B2 (en) * 2016-09-30 2020-05-12 Huawei Technologies Co., Ltd. Method and apparatus for serving mobile communication devices using tunneling protocols
US11116029B2 (en) * 2016-10-31 2021-09-07 Nec Corporation Mobility management entity, network entity, and method and computer readable medium therefor
CN107018542A (zh) * 2017-03-27 2017-08-04 中兴通讯股份有限公司 网络系统中状态信息的处理方法、装置及存储介质
EP3496465B1 (en) * 2017-12-08 2021-10-27 Comcast Cable Communications, LLC User plane function selection for isolated network slice
US10736155B2 (en) * 2017-12-15 2020-08-04 Huawei Technologies Co., Ltd. Shared PDU session establishment and binding
CN112188444B (zh) * 2018-04-09 2021-08-03 华为技术有限公司 一种订阅服务的方法及装置
CN109936843B (zh) * 2018-05-11 2020-02-14 华为技术有限公司 订阅更新方法、设备及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103765951A (zh) * 2011-06-10 2014-04-30 电话有限公司 一种用于无线通信系统中的小区重选和小区切换的方法
US20150358248A1 (en) * 2014-06-09 2015-12-10 Nokia Solutions And Networks Oy Controlling of virtualized network functions for usage in communication network

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15", 3GPP TS 23.502 V15.0.0, vol. SA WG2, no. V15.0.0, 22 December 2017 (2017-12-22) - 31 December 2017 (2017-12-31), pages 1 - 258, XP051392102 *
HUAWEI ET AL.: "Discussion on the Monitoring Event Subscription to a Group", 3GPP TSG-SA2 MEETING #129, S 2-1810485, vol. SA WG2, 9 October 2018 (2018-10-09) - 19 October 2018 (2018-10-19), XP051539462 *
NOKIA ET AL.: "Improvements on the Specification of the Subscription to Network Exposure", SA WG2 MEETING #125, S 2-180131, vol. SA WG2, 24 January 2018 (2018-01-24) - 26 January 2018 (2018-01-26), XP051382396 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114520832A (zh) * 2020-11-19 2022-05-20 腾讯科技（深圳）有限公司 一种数据流处理方法、装置、设备及计算机存储介质
CN114520832B (zh) * 2020-11-19 2023-08-25 腾讯科技（深圳）有限公司 一种数据流处理方法、装置、设备及计算机存储介质

Also Published As

Publication number Publication date
EP3755049B1 (en) 2023-08-09
US11824950B2 (en) 2023-11-21
CN110167080A (zh) 2019-08-23
JP2021513309A (ja) 2021-05-20
EP3755049A4 (en) 2021-11-24
EP3755049A1 (en) 2020-12-23
KR20200118486A (ko) 2020-10-15
JP7342038B2 (ja) 2023-09-11
US20210112129A1 (en) 2021-04-15
KR102448192B1 (ko) 2022-09-27

Similar Documents

Publication Publication Date Title
WO2019158049A1 (zh) 订阅信息更新的方法及装置
CN112291381B (zh) 应用服务器切换方法、设备及系统
JP6855575B2 (ja) ネットワーク間変更方法および装置、ならびに関連デバイス
TWI679543B (zh) 行動邊緣平台伺服器及其使用者設備內容之遷移管理方法
CN109995845B (zh) 一种控制面资源迁移的实现方法、装置及网络功能实体
WO2018112897A1 (zh) 一种会话激活方法及装置和系统
WO2017132951A1 (zh) 服务迁移方法、装置及系统
US11929882B2 (en) Migration to indirect communication mode in a service-based architecture
WO2018233419A1 (zh) 一种信息处理方法及装置
CN112187495B (zh) 终端与服务器的通信方法、通信系统
US11082893B2 (en) Session migration method and device applied to a UE tracking area update
CN105472597B (zh) 应用的注册方法及装置
CN110505318B (zh) 统一资源定位符寻址方法及装置、网络系统
CN105637913A (zh) 在通信系统中提供推送服务的方法和装置
CN114513770B (zh) 部署应用的方法、系统和介质
CN112752352A (zh) 一种中间会话管理功能i-smf确定方法和设备
US20240137422A1 (en) Edge exposure context transfer
CN113424608A (zh) 用于为网络提供外部服务的实体
EP3826229B1 (en) Management method and device for management service
KR20070061420A (ko) 서비스 플로우 식별자를 분산 관리하는 무선 통신 시스템및 그 시스템에서의 서비스 플로우 식별자 관리 방법
US20220019380A1 (en) Methods providing network service restoration context and related service instance sets and storage resource nodes
JP2020522902A (ja) 通信トランザクションを実行するためのネットワーク機能インスタンス及び方法
JP6496648B2 (ja) 通信制御方法および通信システム
CN113747436B (zh) 通信系统、服务器、通信方法和装置
WO2023217070A1 (en) Federated eas discovery

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19754005

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020565007

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207026249

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019754005

Country of ref document: EP

Effective date: 20200914