WO2019158049A1 - 订阅信息更新的方法及装置 - Google Patents
订阅信息更新的方法及装置 Download PDFInfo
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 69
- 230000004044 response Effects 0.000 claims description 26
- 230000006870 function Effects 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 12
- 230000008569 process Effects 0.000 description 16
- 238000012546 transfer Methods 0.000 description 9
- 230000007246 mechanism Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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)
- Meter Arrangements (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims (13)
- 一种订阅信息更新的方法,包括:第三网络功能NF收到第二NF发送的第一订阅信息,其中,所述第一订阅信息包括第二NF为第一NF分配的第一关联标识;所述第三NF为所述第一NF分配第二关联标识,并发送所述第二关联标识至所述第一NF;所述第三NF接收所述第一NF的更新订阅消息,其中,所述更新订阅消息中包括所述第二关联标识。
- 根据权利要求1所述的方法,其中,发送所述第二关联标识至所述第一NF,包括:所述第三NF向所述第一NF发送第一通知消息,其中,所述第一通知消息携带有所述第二关联标识。
- 根据权利要求1所述的方法,其中,发送所述第二关联标识至所述第一NF,包括:所述第三NF向所述第一NF发送第二通知消息,其中,所述第二通知消息设置为通知所述第一NF发送重新订阅信息至所述第三NF;接收所述第一NF发送的重新订阅信息;所述第三NF依据所述重新订阅信息发送订阅响应至所述第一NF,其中,所述订阅响应中包括第二关联标识。
- 根据权利要求1所述的方法,其中,所述第一NF包括消费者NF,所述第二NF包括源提供者NF,所述第三NF包括目的提供者NF。
- 根据权利要求1所述的方法,其中,所述方法还包括:所述第三NF发送以下信息至少之一至所述第一NF:所述第三NF的身份认证ID、所述第一订阅信息中的订阅事件Event、所述第一订阅信息中指示的所述第一NF的目标内容。
- 根据权利要求1所述的方法,其中,第三网络功能NF收到第二NF发送的第一订阅信息之后,所述方法还包括:所述第二NF取消所述第一NF与所述第二NF之间的订阅关系。
- 一种订阅信息更新的方法,其中,包括:第一网络功能NF建立与第二NF的订阅关系;所述第一NF接收第三NF分配的第二关联标识,其中,所述第三NF接收到所述第二NF发送携带所述订阅关系的第一订阅信息之后,为所述第一NF分配所述第二关联标识;所述第一NF发送更新订阅消息至所述第三NF,其中,所述更新订阅消息中包括所述第二关联标识。
- 根据权利要求7所述的方法,其中,所述第一NF接收所述第三NF分配的第二关联标识,包括:接收所述第三NF发送的携带有所述第二关联标识的第一通知消息。
- 根据权利要求7所述的方法,其中,所述第一NF接收所述第三NF分配的第二关联标识,包括:所述第一NF接收所述第三NF发送的第二通知消息;依据所述第二通知消息向所述第三NF发送重新订阅信息;接收所述第三NF依据所述重新订阅信息反馈的订阅响应,其中,所述订阅响应中包括第二关联标识。
- 一种订阅信息更新的装置,其中,包括:第一接收模块,设置为接收第二NF发送的第一订阅信息,其中,所述第一订阅信息包括第二NF为第一NF分配的第一关联标识;第一发送模块,设置为为所述第一NF分配第二关联标识,并发送所述第二关联标识至所述第一NF;第二接收模块,设置为接收所述第一NF的更新订阅消息,其中,所述更新订阅消息中包括所述第二关联标识。
- 一种订阅信息更新的装置,包括:建立模块,设置为建立与第二NF的订阅关系;第三接收模块,设置为接收第三NF分配的第二关联标识,其中,所述第三NF接收到所述第二NF发送携带所述订阅关系的第一订阅信息之后,为所述第三接收模块归属的NF分配所述第二关联标识;第二发送模块,设置为发送更新订阅消息至所述第三NF,其中,所述更新订阅消息中包括所述第二关联标识。
- 一种存储介质,其中,所述存储介质中存储有计算机程序,其中,所述计算机程序被设置为运行时执行所述权利要求1至9任一项中所述的方法。
- 一种订阅信息更新的设备,包括存储器和处理器,其中,所述存储器中存储有计算机程序,所述处理器被设置为运行所述计算机程序以执行所述权利要求1至9任一项中所述的方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2020565007A JP7342038B2 (ja) | 2018-02-13 | 2019-02-12 | サブスクリプション情報更新の方法および装置 |
KR1020207026249A KR102448192B1 (ko) | 2018-02-13 | 2019-02-12 | 구독 정보를 업데이트하는 방법 및 장치 |
EP19754005.7A EP3755049B1 (en) | 2018-02-13 | 2019-02-12 | Subscription information update method and apparatus |
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.5A CN110167080A (zh) | 2018-02-13 | 2018-02-13 | 订阅信息更新的方法及装置 |
CN201810149926.5 | 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)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114520832A (zh) * | 2020-11-19 | 2022-05-20 | 腾讯科技(深圳)有限公司 | 一种数据流处理方法、装置、设备及计算机存储介质 |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113039763B (zh) | 2018-11-14 | 2024-05-24 | 瑞典爱立信有限公司 | 使用nf之间的直接信令的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)
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)
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 |
WO2013139984A1 (en) * | 2012-03-22 | 2013-09-26 | 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 |
CN106790676B (zh) | 2013-12-05 | 2020-07-07 | 华为技术有限公司 | 订阅通知的实现方法和装置 |
WO2018008944A1 (ko) | 2016-07-04 | 2018-01-11 | 엘지전자(주) | 무선 통신 시스템에서 등록 관리 방법 및 이를 위한 장치 |
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 | 中兴通讯股份有限公司 | 网络***中状态信息的处理方法、装置及存储介质 |
EP3972347A1 (en) * | 2017-12-08 | 2022-03-23 | 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 | 华为技术有限公司 | 一种订阅服务的方法及装置 |
CN110475239A (zh) * | 2018-05-11 | 2019-11-19 | 华为技术有限公司 | 订阅更新方法、设备及*** |
-
2018
- 2018-02-13 CN CN201810149926.5A patent/CN110167080A/zh active Pending
-
2019
- 2019-02-12 WO PCT/CN2019/074848 patent/WO2019158049A1/zh unknown
- 2019-02-12 EP EP19754005.7A patent/EP3755049B1/en active Active
- 2019-02-12 KR KR1020207026249A patent/KR102448192B1/ko active IP Right Grant
- 2019-02-12 JP JP2020565007A patent/JP7342038B2/ja active Active
-
2020
- 2020-08-10 US US16/989,777 patent/US11824950B2/en active Active
Patent Citations (2)
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)
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)
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 |
---|---|
JP2021513309A (ja) | 2021-05-20 |
EP3755049A4 (en) | 2021-11-24 |
US20210112129A1 (en) | 2021-04-15 |
KR102448192B1 (ko) | 2022-09-27 |
KR20200118486A (ko) | 2020-10-15 |
EP3755049A1 (en) | 2020-12-23 |
EP3755049B1 (en) | 2023-08-09 |
JP7342038B2 (ja) | 2023-09-11 |
US11824950B2 (en) | 2023-11-21 |
CN110167080A (zh) | 2019-08-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019158049A1 (zh) | 订阅信息更新的方法及装置 | |
TWI679543B (zh) | 行動邊緣平台伺服器及其使用者設備內容之遷移管理方法 | |
JP6855575B2 (ja) | ネットワーク間変更方法および装置、ならびに関連デバイス | |
CN109995845B (zh) | 一种控制面资源迁移的实现方法、装置及网络功能实体 | |
CN112291381A (zh) | 应用服务器切换方法、设备及*** | |
CN109076422A (zh) | 一种通信***间移动方法、设备和*** | |
US11929882B2 (en) | Migration to indirect communication mode in a service-based architecture | |
WO2017132951A1 (zh) | 服务迁移方法、装置及*** | |
CN112187495B (zh) | 终端与服务器的通信方法、通信*** | |
KR20200131149A (ko) | 무선통신 시스템에서 서비스 유연하게 제공하는 방법 및 장치 | |
US11082893B2 (en) | Session migration method and device applied to a UE tracking area update | |
CN105472597B (zh) | 应用的注册方法及装置 | |
CN110505318B (zh) | 统一资源定位符寻址方法及装置、网络*** | |
CN110324152A (zh) | 策略和计费控制规则获取方法、装置及*** | |
CN114513770B (zh) | 部署应用的方法、***和介质 | |
US20240137422A1 (en) | Edge exposure context transfer | |
CN113424608A (zh) | 用于为网络提供外部服务的实体 | |
CN114845350A (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 | |
CN108307457B (zh) | 一种消息路由的方法及装置 | |
JP2020522902A (ja) | 通信トランザクションを実行するためのネットワーク機能インスタンス及び方法 | |
JP6496648B2 (ja) | 通信制御方法および通信システム | |
CN113747436B (zh) | 通信***、服务器、通信方法和装置 |
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 |