[go: up one dir, main page]

WO2025052402A1 - Procédé et système de gestion d'abonnements périmés - Google Patents

Procédé et système de gestion d'abonnements périmés Download PDF

Info

Publication number
WO2025052402A1
WO2025052402A1 PCT/IN2024/051589 IN2024051589W WO2025052402A1 WO 2025052402 A1 WO2025052402 A1 WO 2025052402A1 IN 2024051589 W IN2024051589 W IN 2024051589W WO 2025052402 A1 WO2025052402 A1 WO 2025052402A1
Authority
WO
WIPO (PCT)
Prior art keywords
uri
nrf
node
notification request
active
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/IN2024/051589
Other languages
English (en)
Inventor
Aayush Bhatnagar
Birendra Singh Bisht
Harbinder Pal Singh
Durgesh RAJESH
Venkatakrishna Banka
Sunny DEVAL
Pradeep Kumar
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jio Platforms Ltd
Original Assignee
Jio Platforms Ltd
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 Jio Platforms Ltd filed Critical Jio Platforms Ltd
Publication of WO2025052402A1 publication Critical patent/WO2025052402A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the present disclosure generally relates to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to a method and system for managing stale subscriptions.
  • Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements.
  • the first generation of wireless communication technology was based on analog technology and offered only voice services.
  • 2G second-generation
  • 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services.
  • 4G fourth-generation
  • 5G fifth-generation
  • wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
  • a network function discovers another network function and establishes a communication channel for data transfer therebetween.
  • one NF is designated to be a microservice consumer and the other NF is designated to be a microservice producer.
  • microservice consumers and microservice producers can be an AMF or an SMF.
  • the discovered data about peer NFs expires and is required to be re-discovered.
  • NMF Network Repository Function
  • any changes in the status of one NF is notified to the other NF (e.g., a second NF).
  • the first NF may be designated to be the microservice consumer
  • the second NF may be designated to be the microservice producer.
  • the NRF can have multiple subscriptions, wherein one of the subscriptions is redundant. The redundant subscriptions are called stale subscriptions.
  • any change in the status of the second NF is notified multiple times to the first NF, by the NRF server.
  • the first NF needs to process the same information multiple times, leading to utilization of resources for redundant tasks, which is undesirable for efficient working of the first NF.
  • the number of stale subscriptions can become so prohibitively high that it can choke the network and affect user experience.
  • An aspect of the present disclosure relates to a method for managing one or more stale subscriptions from a network repository function (NRF) node.
  • the method includes receiving, by a receiving unit of at least one network function (NF), a notification request from the NRF node, wherein the notification request comprises a uniform resource identifier (URI).
  • the method further includes comparing, by an analysis unit of the at least one NF, the received URI of the notification request with an active URI stored in a database of the at least one NF.
  • the method further includes removing, by an execution unit of the at least one NF from the NRF node, the one or more stale subscriptions associated with the URI of the notification request in an event the received URI fails to match the active URI upon the comparison.
  • the at least one network function comprises one of an authentication and management function (AMF) and a session management function (SMF).
  • AMF authentication and management function
  • SMF session management function
  • the at least one NF receives a notification from the NRF node in case of an occurrence of a change in the profile of a peer network function associated with an active subscription.
  • the method further comprises transmitting, by a transmitting unit of the at least one NF, a notification acceptance response to NRF node after successful matching of the URI of the notification request with the active URI upon the comparison.
  • the method further comprises receiving the notification request from the NRF node is performed upon transmission of a subscription request from the at least one NF to the NRF node.
  • receiving the notification request from the NRF node is performed upon transmission of a subscription request from the at least one NF to the NRF node.
  • the active URI of the at least one NF is a unique URI that is created each time the at least one NF restarts for each of the subscriptions with the NRF node.
  • the system comprises a receiving unit of at least one network function (NF).
  • the receiving unit is configured to receive a notification request from the NRF node, wherein the notification request comprises a uniform resource identifier (URI).
  • URI uniform resource identifier
  • the system further comprises an analysis unit connected to the at least one NF connected at least with the receiving unit.
  • the analysis unit is configured to compare the received URI of the notification request with an active URI stored in a database of the at least one NF.
  • the system further comprises an execution unit connected to the at least one NF connected at least with the analysis unit, wherein the execution unit is configured to remove, from the NRF node, the one or more stale subscriptions associated with the URI of the notification request in an event the received URI fails to match the active URI upon the comparison.
  • Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for managing one or more stale subscriptions in a network repository function (NRF) node
  • the instructions include executable code which, when executed by one or more units of a system, causes a receiving unit connected to at least one network function (NF), to receive a notification request from the NRF node, wherein the notification request comprises a uniform resource identifier (URI).
  • the instruction when executed further causes an analysis unit connected to at least one network function (NF), to compare the received URI of the notification request with an active URI stored in a database of the at least one NF.
  • the instructions when executed further causes an execution unit connected to at least one network function (NF), to remove, from the NRF node, the one or more stale subscriptions associated with the URI of the notification request in an event the received URI fails to match the active URI upon the comparison.
  • NF network function
  • FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
  • 5GC 5th generation core
  • FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • FIG. 3 illustrates an exemplary block diagram of a system for managing one or more stale subscriptions, in accordance with exemplary implementations of the present disclosure.
  • FIG. 4 illustrates a method flow diagram for managing one or more stale subscriptions, in accordance with exemplary implementations of the present disclosure.
  • FIG. 5a illustrates a process flow diagram for managing one or more stale subscriptions, in accordance with exemplary implementations of the present disclosure.
  • FIG. 5b illustrates a process flow diagram for managing one or more stale subscriptions, in accordance with exemplary implementations of the present disclosure.
  • exemplary and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples.
  • any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art.
  • a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions.
  • a processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
  • the processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
  • a user equipment may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure.
  • the user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure.
  • the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
  • storage unit or “memory unit” refers to a machine or computer- readable medium including any mechanism for storing information in a form readable by a computer or similar machine.
  • a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media.
  • the storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
  • interface refers to a shared boundary across which two or more separate components of a system exchange information or data.
  • the interface may also refer to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
  • All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuits
  • FPGA Field Programmable Gate Array circuits
  • the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information, or a combination thereof between units/components within the system and/or connected with the system.
  • the Uniform Resource Identifier uniquely identifies an abstract or physical resource on the web. Internet protocols use these series of characters to pick apart multiple resources and enable interactions among them.
  • the standard web address, the Uniform Resource Locator (URL), is one of the most well-known instances of URIs. It helps identify exact websites, though other URIs can identify images, electronic documents, and other resources. These resources do not necessarily connect to the Internet, either.
  • the 5GC network architecture includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
  • UE user equipment
  • RAN radio access network
  • AMF Access and mobility management
  • Radio Access Network (RAN) is the part of a mobile telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
  • Access and Mobility Management Function (AMF) is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
  • Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
  • UPF User Plane Function
  • Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
  • AUSF Authentication Server Function
  • NSSAAF Network Slice Specific Authentication and Authorization Function
  • Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
  • Network Exposure Function [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
  • Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
  • PCF Policy Control Function
  • Unified Data Management [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
  • Application Function (AF) is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
  • User Plane Function [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
  • Data Network [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system.
  • the data services may include but are not limited to Internet services, private data network related services.
  • FIG. 2 illustrates an exemplary block diagram of a computing device [200] (also referred to herein as computer system [200]) upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • the computing device [200] may also implement a method for managing one or more stale subscriptions utilising the system.
  • the computing device [200] itself implements the method for managing one or more stale subscriptions using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
  • the computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information.
  • the hardware processor [204] may be, for example, a general- purpose microprocessor.
  • the computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204],
  • the main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204], Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions.
  • the computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204],
  • ROM read only memory
  • a storage device [210] such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions.
  • the computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user.
  • An input device [214] including alphanumeric and other keys, touch screen input means, etc.
  • a cursor controller [216] such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212].
  • This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
  • the computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware, and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine.
  • the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206], Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210], Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the process steps described herein.
  • hard-wired circuitry may be used in place of or in combination with software instructions.
  • the computing device [200] also may include a communication interface [218] coupled to the bus [202], The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222],
  • the communication interface [218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line.
  • the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
  • LAN local area network
  • Wireless links may also be implemented.
  • the communication interface [218] sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.
  • the computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218],
  • a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], host [224] and the communication interface [218],
  • the received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
  • the computing device [200] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of the computing device [200] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, the computing device [200] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, sselling their versatility in various technological applications.
  • FIG. 3 illustrates an exemplary block diagram of a system [300] for managing one or more stale subscriptions, in accordance with the exemplary implementations of the present disclosure.
  • the system [300] comprises at least one network function [300a], at least one receiving unit [302], at least one NRF node [304], at least one analysis unit [306], at least one database [308], at least one execution unit [310] and at least one transmitting unit [312], Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG.
  • system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
  • the system [300] may be present in a user device to implement the features of the present disclosure.
  • the system [300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE).
  • the system [300] may reside in a server or a network entity.
  • the system [300] may reside partly in the server/ network entity and partly in the user device.
  • the system [300] is configured for managing one or more stale subscriptions, with the help of the interconnection between the components/units of the system [300],
  • the system [300] comprises a receiving unit [302] connected to at least one network function (NF) [300a],
  • the receiving unit [302] is configured to receive a notification request from the NRF node [304], wherein the notification request comprises a uniform resource identifier (URI).
  • URI uniform resource identifier
  • the receiving unit [302] connected to at least network function [300a] receives the notification request from the NRF node [304],
  • the notification request includes the uniform resource identifier (URI) that is related to a particular subscription.
  • URI uniform resource identifier
  • the notification request notifies the receiving unit [302] to identify which subscription needs to be checked for further processing, analysis, and removal of the stale subscriptions.
  • the notification request may be received from a network function [300a] relating to a change in a current profile of the network function [300a],
  • the change in profile may include, without limitations, addition, or removal of instances associated with the network function [300a],
  • a record of an instance of the network function [300a] may be stored in the NRF node [304], and a notification of the corresponding change in the profile of the network function [300a] may be transmitted to the NRF node [304] to update the record.
  • another network function or microservice may send a request to the NRF node [304] for information related to a record of the network function [300a].
  • another network function or microservice such as, without limitations, an AMF [106], an SMF [108], etc.
  • the request pertains to a network function [300a] whose profile is currently changed, there may be a mismatch between the request and the record of the subscription in the NRF node [304]
  • the present system [300] provides a means to overcome such a case, particularly, when the NRF node [304] may receive a plurality of such requests.
  • network function [300a] is connected to the system [300] and the NRF node [304],
  • the URI may include, without limitations, a unique identifier, metadata, and other information about the subscription, including details about the subscriber, the service or resource, and the status of the subscription. It is crucial for tracking, managing, and validating subscriptions within a network or service environment.
  • the at least one network function [300a] may also include policy control function (PCF) [122], unified data management (UDM) [124], etc.
  • PCF policy control function
  • UDM unified data management
  • the at least one network function [300a] comprises one of an authentication and management function (AMF) [106] or a session management function (SMF) [108],
  • AMF authentication and management function
  • SMF session management function
  • the AMF [106] or the SMF [108] receives the notification request from theNRF node [304]
  • the network repository function (NRF) [120] provides information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
  • the at least one NF [300a] receives a notification from the NRF node [304] in case of an occurrence of a change in a profile of a peer network function associated with an active subscription.
  • the network function (NF) [300a] receives notifications from the NRF node [304] whenever there is a change in the profile of a peer network function associated with an active subscription. This ensures that the NF [300a] remains up to date with relevant changes, which is crucial for maintaining consistent and efficient network operations.
  • the receiving unit [302] receives the notification request from the NRF node [304] upon transmission of a subscription request from the at least one NF [300a] to the NRF node [304],
  • the network function (NF) [300a] transmits the subscription request to the NRF node [304], and in response, the receiving unit [302] of the NF [300a] receives a notification request from the NRF node [304], This notification request acts as a follow-up to the subscription request and includes information regarding the subscription status or updates. This ensures that the network function (NF) [300a] is kept informed and can respond appropriately to changes or confirmations related to the subscription.
  • the system [300] further comprises an analysis unit [306] of the at least one NF [300a] connected at least with the receiving unit [302],
  • the analysis unit [306] is configured to compare the received URI of the notification request with an active URI stored in a database [308] of the at least one NF [300a],
  • the analysis unit [306] compares the received URI of the notification request that was sent by the NRF node [304] with an active URI stored in the database [308] connected to the at least one NF [300a],
  • the database [308] connected to the network function (NF) [300a] maintains a list of active URIs. These URIs represent subscriptions that are currently active or valid.
  • the analysis unit [306] may identify which subscriptions are outdated and need to be addressed, thereby ensuring the NRF node [304] remains up-to-date and accurate.
  • the active URI of the at least one NF [300a] is a unique URI that is created each time the at least one NF [300a] restarts for each of the subscriptions with the NRF node [304],
  • the active URI stored in the database [308] is a unique identifier that is generated each time the NF [300a] restarts. This ensures that each subscription with the NRF node [304] is associated with a fresh, unique URI, which helps in maintaining accurate subscription records, avoiding conflicts, and enhancing the overall management of subscriptions.
  • the system [300] comprises a transmitting unit [312] connected to the at least one NF [300a] and to at least the analysis unit [306],
  • the transmitting unit [312] is configured to transmit a notification acceptance response to the NRF node [304] after successful matching of the URI of the notification request with the active URI upon the comparison.
  • the transmitting unit [312] sends a notification acceptance response to the NRF node [304], This response indicates that the notification has been successfully processed and that the subscription associated with the URI is valid. This ensures accurate and reliable communication between the NF [300a] and the NRF node [304], supporting efficient subscription management.
  • the transmitting unit [312] sends a 404 error (Not Found) response to the NRF node [304] i.e. NRF [120], which then facilitates the removal of the stale subscription from its records.
  • the network function [300a] such as the AMF [106] and the (SMF) [108] experience lower computational resource overhead which prevents unnecessary growth of subscriptions.
  • the system [300] comprises an execution unit [310] connected to the at least one NF [300a], and to at least the analysis unit [306], and to the NRF node [304],
  • the execution unit [310] is configured to remove, from the NRF node [304], the one or more stale subscriptions associated with the URI of the notification request in an event the received URI fails to match the active URI upon the comparison.
  • the transmitting unit [312] connected at least to the execution unit [310] in response to receiving the error response, is further configured to transmit a request to the NRF node [304] to remove the identified stale subscription.
  • the execution unit [310] is further configured to delete the stale subscription in the NRF node [304], Deletion of the stale subscription may include deleting a record of the identified stale subscription. In an embodiment, once the stale subscription is deleted, the transmitting unit [312] through the NRF node [304], may generate an acknowledgement indicative of successful deletion of the stale subscription.
  • the execution unit [310] removes the one or more stale subscriptions associated with the URI, in an event the received URI fails to match the active URI upon the comparison. This ensures that the network function [300a] operates more efficiently with fewer unnecessary notifications, leading to cleaner subscription records, which improves overall network efficiency.
  • FIG. 4 illustrates an exemplary flow diagram of a method [400] for managing one or more stale subscriptions, in accordance with exemplary implementations of the present disclosure is shown.
  • the method [400] is performed by the system [300], Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402],
  • the method [400] comprises receiving, by a receiving unit [302] connected to at least one network function (NF) [300a], a notification request from the NRF node [304], wherein the notification request comprises a uniform resource identifier (URI).
  • NF network function
  • URI uniform resource identifier
  • the receiving unit [302] connected to at least network function [300a] receives the notification request from the NRF node [304], These requests include the uniform resource identifier (URI) that are related to a particular subscription.
  • URI uniform resource identifier
  • URI provides the necessary information to the receiving unit [302] for taking appropriate action on the subscription referenced by that said URI.
  • these requests notify the receiving unit [302] to identify which subscriptions need to be checked for further processing, analysis, and removal of the stale subscriptions.
  • At least one network function [300a] comprises one of an authentication and management function (AMF) [106] or a session management function (SMF) [108],
  • AMF authentication and management function
  • SMF session management function
  • the AMF [106] or the SMF [108] receives the notification request from the NRF node [304],
  • the at least one NF [300a] receives a notification from the NRF node [304] in case of an occurrence of a change in the profile of a peer network function associated with an active subscription.
  • the network function (NF) [300a] receives notifications from the NRF node [304] whenever there is a change in the profile of a peer network function associated with an active subscription. This ensures that the NF [300a] remains up to date with relevant changes, which is crucial for maintaining consistent and efficient network operations.
  • the receiving the notification request from the NRF node [304] is performed upon transmission of a subscription request from the at least one NF [300a] to the NRF node [304],
  • the network function (NF) [300a] transmits the subscription request to the NRF node [304], the receiving unit [302] of the NF [300a] receives a notification request from the NRF node [304], This notification request acts as a follow-up to the subscription request and includes crucial information regarding the subscription status or updates. This ensures that the network function (NF) [300a] is kept informed and can respond appropriately to changes or confirmations related to the subscription.
  • the method [400] comprises comparing, by an analysis unit [306] connected to the at least one NF [300a], the received URI of the notification request with an active URI stored in a database [308] connected to the at least one NF [300a],
  • the active URI of the at least one NF [300a] is a unique URI that is created each time the at least one NF [300a] restarts for each of the subscriptions with the NRF node [304],
  • the active URI stored in the database [308] of the network function (NF) [300a] is a unique identifier that is generated each time the NF [300a] restarts. This ensures that each subscription with the NRF node [304] is associated with a fresh, unique URI, which helps in maintaining accurate subscription records, avoiding conflicts, and enhancing the overall management of subscriptions.
  • the method further comprises transmitting, by a transmitting unit [312] connected to the at least one NF [300a], a notification acceptance response to the NRF node [304] after successful matching of the URI of the notification request with the active URI upon the comparison.
  • the transmitting unit [312] sends a notification acceptance response to the NRF node [304], This response indicates that the notification has been successfully processed and that the subscription associated with the URI is valid. This ensures accurate and reliable communication between the NF [300a] and the NRF node [304], supporting efficient subscription management.
  • the transmitting unit [312] sends a 404 error (Not Found) response to the NRF node i.e. NRF [120], which then facilitates the removal of the stale subscription from its records.
  • the network function [300a] such as the AMF [106] and the (SMF) [108] experience lower computational resource overhead which prevents unnecessary growth of subscriptions.
  • the method [400] comprises removing, by an execution unit [310] connected to the at least one NRF [304], from the NRF node [304], the one or more stale subscriptions associated with the URI of the notification request in an event the received URI fails to match the active URI upon the comparison.
  • the execution unit [310] removes the one or more stale subscriptions associated with the URI of in an event the received URI fails to match the active URI upon the comparison. This ensures that the network function [300a] operates more efficiently with fewer unnecessary notifications leading to cleaner subscription records, which improves overall network efficiency.
  • step 410 the method [400] terminates.
  • FIGs. 5a and 5b illustrate an exemplary process flow diagrams [500a, 500b] for managing one or more stale subscriptions, in accordance with exemplary implementations of the present disclosure.
  • AMF [106]/SMF [108] sends a subscription request to the NRF [120],
  • the NRF [120] sends back a subscription response to the AMF [106] /SMF [108],
  • the AMF [106]/SMF [108] receives a notification request from the NRF [120].
  • the receiving unit [302] connected to at least network function [300a] i.e., AMF [106] / SMF [108]
  • the notification requests include a uniform resource identifier (URI) that is related to a particular subscription of the network function [300a] in the NRF [120]
  • the URI provides the necessary information to the receiving unit [302] for taking appropriate action on the subscription referenced by that said URI.
  • the notification request notifies the receiving unit [302] to identify which subscriptions need to be checked for further processing, analysis, and removal of the stale subscriptions.
  • the analysis unit [306] compares the received URI of notification request that was sent by the NRF [120] with an active URI stored in the database [308] connected to the at least one NF [300a],
  • the database [308] within the network function (NF) [300a] maintains the list of active URIs. These URIs represent subscriptions that are currently active or valid. By comparing the incoming URIs with the active URIs in the database [308], the analysis unit [306] may identify which subscriptions are outdated and need to be addressed, thereby ensuring the NRF [120] remains up-to-date and accurate.
  • the AMF [106]/SMF [108] sends back a notification response to the NRF [120].
  • the analysis unit [306] confirms that the URI in the notification request matches an active URI in the database [308]
  • the transmitting unit [312] sends a notification acceptance response to the NRF [120]
  • This response indicates that the notification has been successfully processed and the subscription associated with the URI is valid. This ensures accurate and reliable communication between the NF [300a] and the NRF [120], supporting efficient subscription management.
  • the transmitting unit [312] is configured to send an error notification to the NRF [120], This response indicated that the subscription is stale.
  • the execution unit [310] connected to the NRF [120] may facilitate removal of the stale subscription from the NRF [120],
  • the present disclosure further discloses a non-transitory computer readable storage medium storing instructions for detecting and removing one or more stale subscriptions at a network repository function node (NRF) node [304], the instructions include executable code which, when executed by one or more units of a system, causes: a receiving unit [302] connected to at least one network function (NF) [300a], to receive a notification request from the NRF node [304] , wherein the notification request comprises a uniform resource identifier (URI).
  • NRF network repository function node
  • the instructions when executed further causes an analysis unit [306] connected to at least one network function (NF) [300a], to compare the received URI of the notification request with an active URI stored in a database [308] connected to the at least one NF [300a],
  • the instructions when executed further causes an execution unit [310] connected to at least one network function (NF) [300a], to remove, from the NRF node [304], the one or more stale subscriptions associated with the URI of the notification request in an event the received URI fails to match the active URI upon the comparison.
  • the present disclosure provides a technically advanced solution for managing one or more stale subscriptions.
  • the invention disclosed in the present disclosure reduces the number of stale subscriptions registered with the central NRF server. This results in reduced number of notifications dispatched by NRF server and reduced number of notifications processed at a microservice providing server, thereby reducing wastage of resources that would otherwise be spent on redundant activities.
  • the invention disclosed in the present disclosure also prevents the network from choking due to a high number of stale subscriptions.

Landscapes

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

Abstract

La présente divulgation concerne un procédé et un système de gestion d'un ou de plusieurs abonnements périmés. Le procédé consiste en : la réception, par une unité de réception [302] connectée à au moins une fonction de réseau (NF) [300a], d'une demande de notification provenant d'un nœud de NRF [304], la demande de notification comprenant un identifiant de ressource uniforme (URI) ; la comparaison, par une unité d'analyse [306] connectée à ladite au moins une NF [300a], de l'URI reçu de la demande de notification avec un URI actif stocké dans une base de données [308] de ladite au moins une NF [300a] ; le retrait, par une unité d'exécution [310] connectée audit moins au nœud de NRF [304], du nœud de NRF [304], du ou des abonnements périmés associés à l'URI de la demande de notification dans un cas où l'URI reçu ne correspond pas à l'URI actif lors de la comparaison.
PCT/IN2024/051589 2023-09-06 2024-08-30 Procédé et système de gestion d'abonnements périmés Pending WO2025052402A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321059832 2023-09-06
IN202321059832 2023-09-06

Publications (1)

Publication Number Publication Date
WO2025052402A1 true WO2025052402A1 (fr) 2025-03-13

Family

ID=94922988

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/051589 Pending WO2025052402A1 (fr) 2023-09-06 2024-08-30 Procédé et système de gestion d'abonnements périmés

Country Status (1)

Country Link
WO (1) WO2025052402A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020108507A1 (fr) * 2018-11-30 2020-06-04 华为技术有限公司 Procédé et système d'utilisation d'informations de métadonnées d'un service de fonction de réseau et dispositif associé
JP2023512957A (ja) * 2020-02-14 2023-03-30 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 購読データの変更の通知を要求元のネットワーク機能に送信しないように指示する変更要求
WO2023131495A1 (fr) * 2022-01-07 2023-07-13 Telefonaktiebolaget Lm Ericsson (Publ) Apport de contexte d'abonnement à la définition de données de notification de type

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020108507A1 (fr) * 2018-11-30 2020-06-04 华为技术有限公司 Procédé et système d'utilisation d'informations de métadonnées d'un service de fonction de réseau et dispositif associé
JP2023512957A (ja) * 2020-02-14 2023-03-30 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 購読データの変更の通知を要求元のネットワーク機能に送信しないように指示する変更要求
WO2023131495A1 (fr) * 2022-01-07 2023-07-13 Telefonaktiebolaget Lm Ericsson (Publ) Apport de contexte d'abonnement à la définition de données de notification de type

Similar Documents

Publication Publication Date Title
WO2025052402A1 (fr) Procédé et système de gestion d'abonnements périmés
WO2019201111A1 (fr) Procédé, appareil et dispositif de traitement d'informations, et support de stockage lisible par ordinateur
WO2025052474A1 (fr) Procédé et système permettant de gérer un abonnement de fonctions de réseau
WO2025013048A1 (fr) Procédé et système de mise à jour de paramètres pour un ou plusieurs nœuds réseau
WO2025062454A1 (fr) Procédé et système pour augmenter le débit de transactions de données par mise en œuvre d'un système de stockage
WO2025008911A1 (fr) Procédé et système d'envoi d'une notification d'alerte à un abonné d'équipement utilisateur (ue)
WO2025012937A1 (fr) Procédé et système de récupération d'un emplacement d'abonné cible
WO2025008863A1 (fr) Procédé et système d'octroi d'un accès à un trafic de données associé à un réseau cible
WO2025062421A1 (fr) Procédé et système de gestion d'un microservice sur la base d'une interface de ligne d'instruction (cli)
WO2025052401A1 (fr) Procédé et système de gestion d'une condition de surcharge dans un réseau
WO2025069062A1 (fr) Procédé et système de continuité de service dans un réseau de communication
WO2025062417A1 (fr) Procédé et système pour éviter la suspension d'une ou de plusieurs fonctions de réseau provenant d'un réseau
WO2025052458A1 (fr) Procédé et système d'enregistrement d'une fonction de réseau (nf) dans réseau de communication sans fil
WO2025057186A1 (fr) Procédé et système de gestion d'enregistrement d'une fonction de réseau
WO2025062422A1 (fr) Procédé et système de gestion de liaisons de session dans un réseau
WO2025057205A1 (fr) Procédé et système de mise à niveau automatique d'un groupe de réseaux cibles
WO2025012980A1 (fr) Procédé et système pour la réalisation d'une procédure d'interdiction dans une zone de rapport de présence prédéfinie (pra)
WO2025012979A1 (fr) Procédé et système aux fins d'une gestion basée sur la configuration d'une demande de procédure
WO2025052421A1 (fr) Procédé et système de traitement des demandes de localisation dans un réseau de communication sans fil
WO2025052413A1 (fr) Procédé et système pour effectuer une mise à jour de commande de politique pour une application
WO2025012939A1 (fr) Procédé et système de surveillance en temps réel d'état(s) de fonction(s) réseau
WO2025012950A1 (fr) Procédé et système de fourniture dynamique d'informations d'enregistrements de données de diffusion en continu (sdr)
WO2025052462A1 (fr) Procédé et système permettant de restaurer une ou plusieurs fonctions de réseau (nf) dans un environnement de réseau
WO2025012938A1 (fr) Procédé et système pour initier une planification de notification d'attribut de charge à partir d'une fonction de référentiel de réseau (nrf)
WO2025012936A1 (fr) Procédé et système de rapport d'informations de charge spécifiques à une tranche

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: 24862249

Country of ref document: EP

Kind code of ref document: A1