Subscription method and device, equipment and storage medium
By receiving and sending shared information identifiers and shared information, the problems of resource consumption and information asynchrony during NRF subscription are solved, and cross-NRF information synchronization is achieved, thus improving subscription efficiency.
Patent Information
- Application Number
- CN202410480674.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-04-19
- Publication Date
- 2025-10-24
AI Technical Summary
In the 5G core network, the subscription process of the Network Storage Function (NRF) consumes a lot of transmission resources and reduces subscription efficiency, especially in the case of cross-NRF, where the information asynchrony between the subscriber and the NRF is serious.
By receiving the shared information identifier and shared information from the subscriber, it determines whether the corresponding information exists locally, and sends the subscription request to the target NRF to achieve cross-NRF shared information synchronization and avoid information asynchrony.
It improves subscription efficiency, reduces resource consumption, and ensures synchronization between NRF and subscriber information.
Smart Images
Figure CN120835280A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present disclosure relates to the field of communication technology, and particularly relates to a subscription method, device, equipment and storage medium. BACKGROUND
[0002] The Network Repository Function (NRF) is a key component in the 5G core network, used for storing and managing information related to the network, such as network services, slices, UE routing, etc. The NRF provides a service discovery mechanism for other network functions, enabling network functions to register, discover, select and communicate with other network functions. However, when other NFs subscribe to the NRF, all information of the NRF needs to be subscribed, which occupies a large amount of transmission resources and reduces the efficiency of subscription. SUMMARY
[0003] The present disclosure provides a subscription method, device, equipment and storage medium, which at least reduces the resources occupied by the NRF subscription and improves the efficiency of subscription.
[0004] Other characteristics and advantages of the present disclosure will become apparent from the following detailed description, or will be learned by practice of the present disclosure.
[0005] According to one aspect of the present disclosure, a subscription method is provided, applied to an NRF, comprising:
[0006] receiving a subscription request sent by a subscriber, the subscription request comprising a shared information identifier and / or shared information;
[0007] sending the subscription request to a second NRF according to the shared information identifier or the shared information, the subscriber comprising a network function (NF) and a service communication proxy (SCP).
[0008] In one embodiment of the present disclosure, it is determined whether there is corresponding shared information identifier and / or shared information locally based on the shared information identifier and / or the shared information;
[0009] sending the subscription request to the second NRF according to the shared information identifier or the shared information, comprising:
[0010] sending the subscription request to the second NRF according to the shared information identifier or the shared information in the case that there is no corresponding shared information identifier and / or shared information locally.
[0011] In one embodiment of the present disclosure, the shared information comprises: the same part of a plurality of NF information registered in the NRF.
[0012] In an embodiment of the disclosure, the method further comprises: in a case where the second NRF determines that the subscription fails, receiving a subscription failure message sent by the second NRF, the subscription failure message comprising at least one of redirection information, failure cause information, and internal failure information.
[0013] In an embodiment of the disclosure, the failure cause information comprises: the OAM does not configure the corresponding shared information of the shared information identifier, and the corresponding shared information of the shared information identifier is not found.
[0014] In an embodiment of the disclosure, the method further comprises:
[0015] In a case where the subscription failure message sent by the second NRF is received, forwarding the subscription failure message to the subscriber.
[0016] In an embodiment of the disclosure, the subscription request is sent to a third NRF based on the redirection information.
[0017] According to another aspect of the disclosure, a subscription method is provided, applied to a subscriber, the subscriber comprising a network function (Network Function, NF) and a SCP, the method comprising:
[0018] Sending a subscription request to a first network repository function (NRF), the subscription request comprising a shared information identifier and / or shared information, so that the first NRF sends the subscription request to a second NRF.
[0019] In an embodiment of the disclosure, the shared information comprises: a same part of a plurality of NF information registered in the NRF.
[0020] In an embodiment of the disclosure, the method further comprises:
[0021] In a case where the second NRF determines that the subscription fails, receiving a subscription failure message sent by the second NRF forwarded by the first NRF, the subscription failure message comprising at least one of redirection information, failure cause information, and internal failure information.
[0022] In an embodiment of the disclosure, the failure cause information comprises: the OAM does not configure the corresponding shared information of the shared information identifier, and the corresponding shared information of the shared information identifier is not found.
[0023] In an embodiment of the disclosure, the method further comprises:
[0024] In a case where the shared information changes, receiving a state change notification sent by the second NRF, the state change notification comprising a changed shared information identifier and / or changed shared information.
[0025] In an embodiment of the disclosure, the method further comprises:
[0026] synchronizing the shared information based on the state change notification;
[0027] In a case where it is determined that the synchronization fails, a synchronization failure message is sent to the second NRF, the synchronization failure message including at least one of the redirection information, the local absence of the shared information, and the internal failure information.
[0028] According to still another aspect of the present disclosure, a subscription apparatus is provided, applied to a first NRF, comprising:
[0029] A first receiving module is configured to receive a subscription request sent by a subscriber, the subscription request including shared information identification and / or shared information.
[0030] A first sending module is configured to send the subscription request to a second NRF according to the shared information identification or the shared information, the subscriber including a network function (NF) and an SCP.
[0031] In an embodiment of the present disclosure, the apparatus further comprises:
[0032] A determining module is configured to determine whether the local presence of corresponding shared information identification and / or shared information based on the shared information identification and / or the shared information.
[0033] The first sending module comprises:
[0034] A first sending unit is configured to send the subscription request to the second NRF according to the shared information identification or the shared information in a case where the local absence of corresponding shared information identification and / or shared information.
[0035] In an embodiment of the present disclosure, the shared information includes: a same part of a plurality of NF information registered in the NRF.
[0036] In an embodiment of the present disclosure, the apparatus further comprises:
[0037] A second receiving module is configured to receive a subscription failure message sent by the second NRF in a case where the second NRF determines that the subscription fails, the subscription failure message including at least one of redirection information, failure reason information, and internal failure information.
[0038] In an embodiment of the present disclosure, the failure reason information includes: the OAM not configuring shared information corresponding to the shared information identification and not finding shared information corresponding to the shared information identification.
[0039] In an embodiment of the present disclosure, the apparatus further comprises:
[0040] A forwarding module is configured to forward the subscription failure message to the subscriber in a case where the subscription failure message sent by the second NRF is received.
[0041] In one embodiment of the present disclosure, the apparatus further comprises:
[0042] The third sending module is configured to send the subscription request to the third NRF based on the redirection information.
[0043] According to yet another aspect of the present disclosure, there is provided an apparatus for subscribing, applied to a subscriber, the subscriber comprising an NF to SCP;
[0044] The apparatus comprises:
[0045] The second sending module is configured to send a subscription request to a first network repository function (NRF), the subscription request comprising shared information identification and / or shared information, so that the first NRF sends the subscription request to a second NRF.
[0046] In one embodiment of the present disclosure, the shared information comprises: a same part of a plurality of NF information registered in the NRF.
[0047] In one embodiment of the present disclosure, the apparatus further comprises:
[0048] The third receiving module is configured to receive a subscription failure message sent by the second NRF and forwarded by the first NRF in a case where the second NRF determines that the subscription fails, the subscription failure message comprising at least one of redirection information, failure cause information, and internal failure information.
[0049] In one embodiment of the present disclosure, the failure cause information comprises: the OAM does not configure the shared information corresponding to the shared information identification, and the shared information corresponding to the shared information identification is not found.
[0050] In one embodiment of the present disclosure, the apparatus further comprises:
[0051] The fourth receiving module is configured to receive a state change notification sent by the second NRF in a case where the shared information changes, the state change notification comprising shared information identification that changes and / or changed shared information.
[0052] In one embodiment of the present disclosure, the apparatus further comprises:
[0053] The synchronizing module is configured to synchronize the shared information based on the state change notification.
[0054] The fourth sending module is configured to send a synchronization failure message to the second NRF in a case where it is determined that the synchronization fails, the synchronization failure message comprising at least one of redirection information, locally non-existent shared information, and internal failure information.
[0055] According to still another aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the above-mentioned subscription method via execution of the executable instructions.
[0056] According to still another aspect of the present disclosure, a computer readable storage medium is provided, having stored thereon a computer program, which, when executed by a processor, implements the above-mentioned subscription method.
[0057] The subscription method, device, equipment and storage medium provided by the embodiments of the present disclosure receive a subscription request sent by a subscriber, and send the subscription request to a second NRF according to shared information identification or shared information, thereby realizing synchronization of the shared information across the NRF, avoiding the problem of asynchronization of the NRF and the subscriber information, and improving the efficiency of subscription.
[0058] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS
[0059] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present disclosure and, together with the specification, serve to explain the principles of the present disclosure. It is clear that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative labor on the basis of these drawings.
[0060] Figure 1 A flow chart of a subscription method in an embodiment of the present disclosure is shown;
[0061] Figure 2 A flow chart of another subscription method in an embodiment of the present disclosure is shown;
[0062] Figure 3 A flow chart of still another subscription method in an embodiment of the present disclosure is shown;
[0063] Figure 4 A flow chart of still another subscription method in an embodiment of the present disclosure is shown;
[0064] Figure 5 A flow chart of still another subscription method in an embodiment of the present disclosure is shown;
[0065] Figure 6 A flow chart of still another subscription method in an embodiment of the present disclosure is shown;
[0066] Figure 7 A flow chart of still another subscription method in an embodiment of the present disclosure is shown;
[0067] Figure 8Fig. 6 shows another subscription method flow chart in embodiments of the present disclosure;
[0068] Figure 9 Fig. 6 shows another subscription method flow chart in embodiments of the present disclosure;
[0069] Figure 10 Fig. 7 shows a subscription method signaling chart in embodiments of the present disclosure;
[0070] Figure 11 Fig. 8 shows another subscription method signaling chart in embodiments of the present disclosure;
[0071] Figure 12 Fig. 9 shows a subscription apparatus schematic diagram in embodiments of the present disclosure;
[0072] Figure 13 Fig. 10 shows another subscription apparatus schematic diagram in embodiments of the present disclosure;
[0073] Figure 14 Fig. 11 shows a structural block diagram of an electronic device in embodiments of the present disclosure. DETAILED DESCRIPTION
[0074] Example implementations will now be described more fully with reference to the accompanying drawings. Example implementations can be implemented in any
[0075] In addition, the drawings are only schematic and the dimensions of certain features can be exaggerated for clarity. Like reference numerals may
[0076] It should be understood that each of the steps of the method implementations of the present disclosure can be performed in different orders and / or in parallel. In addition, the method implementations can include additional steps and / or omit performing the steps shown. The scope of the present disclosure is not limited in this respect.
[0077] It should be noted that the terms "first", "second", etc. mentioned in the present disclosure are only used to distinguish different apparatuses, modules or units, and are not intended to limit the order or interdependence of the functions performed by these apparatuses, modules or units.
[0078] It should be noted that the modification of "one", "multiple" mentioned in the present disclosure is illustrative but not restrictive, and those skilled in the art should understand that "one or more" should be understood unless otherwise explicitly indicated in the context.
[0079] In the related art, the subscriber can register, deregister, information update, etc. through the shared information ID to the NRF, but when the shared information in the NRF changes, the subscriber using the shared information does not know that the shared information changes, thereby causing information asymmetry between the NRF and the subscriber, which may cause the problem that the information sent by each other is not understood. This situation is more serious in the case of cross-NRF, and the operation across the NRF will affect multiple NRF service areas, and the failed operation will occupy a large amount of NRF communication and storage resources. Therefore, how to synchronize the shared information across the NRF has become a problem to be solved in the field.
[0080] To solve the above problems, the embodiments of the present disclosure provide a subscription method, device, equipment and storage medium.
[0081] In order to explain the present disclosure in detail, Figure 1 A flow chart of a subscription method in the embodiments of the present disclosure is shown. It should be noted that the subscription method in the embodiments of the present disclosure is applied to the first NRF.
[0082] As Figure 1 indicated, the subscription method can include:
[0083] S110, receiving a subscription request sent by a subscriber, the subscription request including shared information identification and / or shared information.
[0084] In some embodiments, the first NRF and the second NRF can be NRFs under different public land mobile networks (Public Land Mobile Network, PLMN).
[0085] In some embodiments, the NRF can determine in advance with the subscriber whether the subscriber contains corresponding shared information, and in the case of determining that the corresponding shared information is contained, the shared information identification can be included in the state change notification sent by the NRF to the subscriber.
[0086] In some embodiments, the shared information and the shared information identification correspond one-to-one, and the shared information identification can include a shared information ID.
[0087] In some embodiments, the NF or SCP can be individually used as a subscriber.
[0088] In some embodiments, the shared information includes the same part of the plurality of NF information registered in the NRF.
[0089] For example, the NFs in the same NF Set stored in the NRF have the same applicable user number segment information, and these number segment information can be taken out as shared information.
[0090] The NF Set is a set of control plane NFs of the same type, same service, and same slice.
[0091] S120, according to the shared information identifier and / or the shared information, sends a subscription request to a second NRF, and the subscriber includes a network function (NF) and a service communication proxy (SCP).
[0092] In some embodiments, the first NRF can determine a target NRF based on the shared information identifier or the shared information, where the target NRF is the NRF that stores the shared information.
[0093] In some embodiments, the target NRF can be the second NRF.
[0094] In some embodiments, in the case where the second NRF is not the target NRF, the second NRF can send the subscription request to the target NRF based on the shared information identifier or the shared information.
[0095] The subscription method provided by the embodiments of the present disclosure receives a subscription request sent by a subscriber, and sends the subscription request to a second NRF according to a shared information identifier or shared information, thereby achieving synchronization of shared information across NRFs, avoiding the problem of out-of-sync between the NRF and the subscriber information, and improving the efficiency of subscription.
[0096] Figure 2 A flowchart of another subscription method in the embodiments of the present disclosure is shown. It should be noted that the subscription method in the embodiments of the present disclosure is applied to a first NRF.
[0097] As Figure 2 shown, the subscription method can include:
[0098] S210, receiving a subscription request sent by a subscriber, and the subscription request includes a shared information identifier and / or shared information.
[0099] S220, determining whether there is a corresponding shared information identifier and / or shared information locally based on the shared information identifier and / or the shared information.
[0100] In some embodiments, in the case where the first NRF receives the shared information identifier and / or the shared information, it can be determined whether there is a corresponding shared information identifier and / or shared information stored locally based on the received shared information identifier and / or shared information.
[0101] S230, in the case that the corresponding shared information identifier and / or shared information does not exist locally, sending the subscription request to the second NRF according to the shared information identifier or the shared information.
[0102] The subscription method provided by the embodiments of the present disclosure receives a subscription request sent by a subscriber, and sends the subscription request to a second NRF according to a shared information identifier or shared information, thereby realizing synchronization of shared information across NRFs, avoiding the problem of out-of-sync between the NRF and the subscriber information, and improving the efficiency of subscription.
[0103] Figure 3 Another flowchart of a subscription method in the embodiments of the present disclosure is shown. It should be noted that the subscription method in the embodiments of the present disclosure is applied to a first NRF.
[0104] As shown in Figure 3 , the subscription method can include:
[0105] S310, receiving a subscription request sent by a subscriber, the subscription request including a shared information identifier and / or shared information.
[0106] S320, sending the subscription request to a second NRF according to the shared information identifier or the shared information, the subscriber including a network function NF and a service communication proxy SCP.
[0107] S330, in the case that the second NRF determines that the subscription fails, receiving a subscription failure message sent by the second NRF, the subscription failure message including at least one of redirection information, failure cause information, and internal failure information.
[0108] Exemplarily, the shared information can be Share Data, and the shared information identifier can be Share Data ID or Share Data ID List.
[0109] In some embodiments, the subscription request can further include specific data of the shared information, Share Data IE.
[0110] In some embodiments, in the case that the first NRF stores the shared information identifier and / or the shared information corresponding to the subscription request, a subscription success notification can be sent to the first NRF.
[0111] In some embodiments, the subscription success notification can further include data SubscriptionData of the successful subscription.
[0112] Exemplarily, the subscription success notification can be 201 Created.
[0113] In some embodiments, the fault reason information includes that the OAM does not configure the shared information corresponding to the shared information identification, and the shared information corresponding to the shared information identification is not found.
[0114] In some embodiments, the fault reason information can be ProblemDetail.
[0115] For example, if the fault reason information is that the network management OAM does not configure the shared information corresponding to the shared information identification, the ProblemDetail can be SHARED_DATA_NOT_CONFIGURED at this time.
[0116] For example, if the fault reason information is that the shared information corresponding to the shared information identification is not found, the ProblemDetail can be SHARED_DATA_ID_UNKNOWN at this time.
[0117] For example, the redirection information can be 3XX.
[0118] In some embodiments, the fault reason information and the internal fault information can be represented by 4XX. The fault reason information can be 400 Bad Request, and the fault reason information can include the ProblemDetails IE.
[0119] The subscription method provided by the embodiments of the present disclosure receives a subscription request sent by a subscription party, and sends the subscription request to a second NRF according to a shared information identification or shared information, thereby realizing synchronization of the shared information across the NRFs, avoiding the problem of synchronization of the NRF and the subscription party information, and improving the efficiency of the subscription.
[0120] Figure 4 A flowchart of another subscription method in the embodiments of the present disclosure is shown. It should be noted that the subscription method in the embodiments of the present disclosure is applied to a first NRF.
[0121] As shown in Figure 4 , the subscription method can include:
[0122] S410, receiving a subscription request sent by a subscription party, the subscription request including a shared information identification and / or shared information.
[0123] S420, sending the subscription request to a second NRF according to the shared information identification or the shared information, the subscription party including a network function NF and a service communication proxy SCP.
[0124] S430, in the case that the second NRF determines that the subscription fails, receiving a subscription failure message sent by the second NRF, the subscription failure message including at least one of redirection information, fault reason information, and internal fault information.
[0125] S440, in a case where the second NRF sends a subscription failure message, forwarding the subscription failure message to the subscriber.
[0126] The subscription method provided by the embodiments of the present disclosure receives a subscription request sent by a subscriber, and sends the subscription request to a second NRF according to a shared information identifier or shared information, thereby achieving synchronization of the shared information across NRFs, avoiding the problem of information asynchronization between the NRF and the subscriber, and improving the efficiency of subscription.
[0127] Figure 5 A flowchart of another subscription method in the embodiments of the present disclosure is shown. It should be noted that the subscription method in the embodiments of the present disclosure is applied to a first NRF.
[0128] As shown in Figure 5 , the subscription method can include:
[0129] S510, receiving a subscription request sent by a subscriber, the subscription request including a shared information identifier and / or shared information.
[0130] S520, sending the subscription request to a second NRF according to the shared information identifier or shared information, the subscriber including a network function NF and a service communication proxy SCP.
[0131] S530, in a case where the second NRF determines that the subscription fails, receiving a subscription failure message sent by the second NRF, the subscription failure message including at least one of redirection information, failure cause information, and internal failure information.
[0132] S540, sending the subscription request to a third NRF based on the redirection information.
[0133] In some embodiments, the first NRF can determine the third NRF based on the shared information identifier and / or the shared information.
[0134] In some embodiments, the method can further include:
[0135] In a case where the second NRF determines that the subscription succeeds and the shared information changes, the second NRF can send a state change notification to the subscriber.
[0136] In some embodiments, the method can further include:
[0137] In a case where the subscriber fails to synchronize the shared information based on the state change notification, receiving a synchronization failure message sent by the subscriber, the synchronization failure message including at least one of redirection information, local absence of shared information, and internal failure information.
[0138] In some embodiments, when the subscriber receives a status change notification, the subscriber synchronizes the locally stored shared information based on the changed shared information identifier and / or the changed shared information contained in the status change notification.
[0139] In some embodiments, when synchronizing locally stored shared information, there may be two results: synchronization failure and synchronization success.
[0140] In some embodiments, regardless of whether the synchronization succeeds or fails, the subscriber will send a synchronization response to the NRF, and the synchronization response includes a synchronization failure message.
[0141] For example, if the synchronization is successful, the subscriber can send 204 No content to the NRF. If the synchronization failure message is that the shared information does not exist locally, the subscriber can send 404 Not Found to the NRF with ProblemDetails. If the synchronization failure message is a redirection message, the subscriber can send "3XX" to the NRF. If the synchronization failure message is an internal fault message, the subscriber can send "5XX" to the NRF.
[0142] In some embodiments, the method may further include:
[0143] When the third NRF determines that the subscription is successful and the shared information changes, the third NRF may send a status change notification to the subscriber.
[0144] In some embodiments, the method may further include:
[0145] In the case that the subscriber fails to synchronize the shared information based on the state change notification, a synchronization failure message sent by the subscriber is received, where the synchronization failure message includes at least one of redirection information, local non-existence of shared information, and internal fault information.
[0146] In some embodiments, when the subscriber receives a status change notification, the subscriber synchronizes the locally stored shared information based on the changed shared information identifier and / or the changed shared information contained in the status change notification.
[0147] In some embodiments, when synchronizing locally stored shared information, there may be two results: synchronization failure and synchronization success.
[0148] In some embodiments, regardless of whether the synchronization succeeds or fails, the subscriber will send a synchronization response to the NRF, and the synchronization response includes a synchronization failure message.
[0149] For example, if the synchronization is successful, the subscriber can send 204 No content to the NRF. If the synchronization failure message is that the shared information does not exist locally, the subscriber can send 404 Not Found to the NRF with ProblemDetails. If the synchronization failure message is a redirection message, the subscriber can send "3XX" to the NRF. If the synchronization failure message is an internal fault message, the subscriber can send "5XX" to the NRF.
[0150] The subscription method provided by the embodiment of the present disclosure receives a subscription request sent by a subscriber, and sends the subscription request to a second NRF according to a shared information identifier or shared information, thereby realizing synchronization of shared information across NRFs, avoiding the problem of information asynchrony between the NRF and the subscriber, and improving the efficiency of subscription.
[0151] Based on the same inventive concept, the present disclosure also provides a subscription method, such as the following embodiment. Since the principle of solving the problem in the subscription method embodiment is similar to that in the above method embodiment, the implementation of this system embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.
[0152] Figure 6 A flowchart of another subscription method in an embodiment of the present disclosure is shown. It should be noted that the subscription method in the embodiment of the present disclosure is applied to the subscriber. The subscriber includes the NF and the SCP.
[0153] like Figure 6 As shown, the method may include:
[0154] S610: Send a subscription request to a first network repository function NRF, where the subscription request includes a shared information identifier and / or shared information, so that the first NRF sends the subscription request to a second NRF.
[0155] In some embodiments, the shared information includes: the same portion of information of multiple NFs registered in the NRF.
[0156] The subscription method provided by the embodiment of the present disclosure receives a subscription request sent by a subscriber, and sends the subscription request to a second NRF according to a shared information identifier or shared information, thereby realizing synchronization of shared information across NRFs, avoiding the problem of information asynchrony between the NRF and the subscriber, and improving the efficiency of subscription.
[0157] Figure 7 A flowchart of another subscription method in an embodiment of the present disclosure is shown. It should be noted that the subscription method in the embodiment of the present disclosure is applied to the subscriber. The subscriber includes the NF and the SCP.
[0158] like Figure 7 As shown, the method may include:
[0159] S710, sending a subscription request to a first network repository function (NRF), the subscription request comprising a shared information identifier and / or shared information, so that the first NRF sends the subscription request to a second NRF.
[0160] S720, in a case where the second NRF determines that the subscription fails, receiving a subscription failure message sent by the second NRF and forwarded by the first NRF, the subscription failure message comprising at least one of redirection information, failure cause information, and internal failure information.
[0161] In some embodiments, the failure cause information comprises that the OAM does not configure the shared information corresponding to the shared information identifier, and the shared information corresponding to the shared information identifier is not found.
[0162] The subscription method provided by the embodiments of the present disclosure receives a subscription request sent by a subscriber, and sends the subscription request to a second NRF according to a shared information identifier or shared information, thereby achieving synchronization of shared information across NRFs, avoiding the problem of out-of-sync information between the NRF and the subscriber, and improving the efficiency of subscription.
[0163] Figure 8 A flowchart of another subscription method in the embodiments of the present disclosure is shown. It should be noted that the subscription method in the embodiments of the present disclosure is applied to a subscriber. The subscriber comprises an NF and an SCP.
[0164] As shown in Figure 8 , the method can comprise:
[0165] S810, sending a subscription request to a first network repository function (NRF), the subscription request comprising a shared information identifier and / or shared information, so that the first NRF sends the subscription request to a second NRF.
[0166] S820, in a case where the shared information changes, receiving a state change notification sent by the second NRF, the state change notification comprising a changed shared information identifier and / or changed shared information.
[0167] The subscription method provided by the embodiments of the present disclosure receives a subscription request sent by a subscriber, and sends the subscription request to a second NRF according to a shared information identifier or shared information, thereby achieving synchronization of shared information across NRFs, avoiding the problem of out-of-sync information between the NRF and the subscriber, and improving the efficiency of subscription.
[0168] Figure 9 A flowchart of another subscription method in the embodiments of the present disclosure is shown. It should be noted that the subscription method in the embodiments of the present disclosure is applied to a subscriber. The subscriber comprises an NF and an SCP.
[0169] As shown in Figure 9 , the method can comprise:
[0170] S910, sending a subscription request to a first network repository function (NRF), the subscription request comprising a shared information identifier and / or shared information, so that the first NRF sends the subscription request to a second NRF.
[0171] S920, synchronizing the shared information based on the state change notification;
[0172] S930, in a case where it is determined that the synchronization fails, sending a synchronization failure message to the second NRF, the synchronization failure message comprising at least one of the targeting information, the local absence of the shared information, and the internal failure information.
[0173] The subscription method provided by the embodiments of the present disclosure receives a subscription request sent by a subscriber, and sends the subscription request to a second NRF according to a shared information identifier or shared information, thereby achieving synchronization of shared information across NRFs, avoiding the problem of out-of-sync between the NRF and the subscriber information, and improving the efficiency of subscription.
[0174] In order to make a detailed description of the present disclosure, Figure 10 A signaling diagram of a subscription method in an embodiment of the present disclosure is shown. As shown in the figure, the method can include: Figure 10 The method can include:
[0175] S1010, sending, by a subscriber, an NF information subscription request to a first NRF.
[0176] In some embodiments, the NF information subscription request can comprise a shared information identifier Share Data ID, a shared information identifier list Share Data ID List, and shared information Share Data IE that need to be subscribed.
[0177] S1020, forwarding, by the first NRF, the NF information subscription request to a second NRF.
[0178] In some embodiments, the first NRF can determine the second NRF based on the shared information identifier Share Data ID, the shared information identifier list Share Data ID List, and the shared information Share Data IE in the NF information subscription request.
[0179] In some embodiments, if the second NRF is not a target NRF, the first NRF can re-determine the target NRF based on the NF information subscription request. The target NRF target NRF can be an NRF that contains the shared information identifier Share Data ID, the shared information identifier list Share Data ID List, and the shared information Share Data IE.
[0180] S1030, the second NRF replies to the first NRF with a subscription request.
[0181] In some embodiments, the subscription request can include a subscription success or a subscription failure.
[0182] In the case where the subscription request includes a subscription success, a reply "201 Created" can be returned, and the data SubscriptionData of the subscription success can be included.
[0183] In the case of a subscription failure, a reply "3xx" indicating redirection can be included; a reply "4xx" can be included, where "400 Bad Request" contains a ProblemDetails IE, i.e., a fault reason. If the Share Data on the NRF is configured by OAM, but the Share Data corresponding to the Share Data ID is not configured, the ProblemDetail can be SHARED_DATA_NOT_CONFIGURED.
[0184] If the Share Data on the NRF is not configured by OAM, and the Share Data corresponding to the Share Data ID is not found, the ProblemDetail can be SHARED_DATA_ID_UNKNOWN. A reply "5xx" indicating an internal failure of the NRF can be included.
[0185] S1040, the first NRF forwards the reply to the subscription request to the subscriber.
[0186] S1050, the shared information changes.
[0187] In some embodiments, the Share Data in the second NRF changes, and the change reason can be that the Share Data is modified by other NF / SCP, or the Share Data is modified by OAM, or the Share Data is modified by the NRF itself or other NRF.
[0188] S1060, the second NRF sends a state change notification to the subscriber.
[0189] In some embodiments, the second NRF feeds back the changed Share Data ID and the changed Share Data value to the NF / SCP
[0190] S1070, the subscriber sends a state change notification response to the second NRF.
[0191] In some embodiments, the state change notification response can include various information: the NF / SCP modifies its local Share Data according to the changed value of the Share Data, and returns "204 No content". If the local does not have the corresponding Share Data, "404 Not Found" is returned to the NRF with ProblemDetails. If redirection is needed, "3xx" is returned. If there is an internal failure in the NF / SCP, "5xx" is returned.
[0192] To make a detailed description of the present disclosure, Figure 11 Another subscription method signaling diagram in the embodiments of the present disclosure is shown. As shown in the method can include: Figure 11
[0193] S1110, the subscription direction first NRF sends NF information subscription request.
[0194] In some embodiments, the NF information subscription request can include the shared information identifier Share Data ID, the shared information identifier list Share Data ID List, and the shared information Share Data IE that need to be subscribed.
[0195] S1120, the first NRF forwards the NF information subscription request to the second NRF.
[0196] In some embodiments, the first NRF can determine the second NRF based on the shared information identifier Share Data ID, the shared information identifier list Share Data ID List, and the shared information Share Data IE in the NF information subscription request.
[0197] In some embodiments, if the second NRF is not the target NRF, the first NRF can re-determine the target NRF based on the NF information subscription request. Wherein, the target NRF target NRF can be the NRF containing the shared information identifier Share Data ID, the shared information identifier list Share Data ID List, and the shared information Share Data IE.
[0198] S1130, the second NRF sends a redirection request to the first NRF.
[0199] In some embodiments, the second NRF determines that the subscription request needs to be redirected to the third NRF 3 according to the information pre-configured locally and / or the related information carried by the NF information subscription request, such as the possible storage of the NRF information of the Share Data / Share Data ID. The second NRF sends the redirection request to the first NRF.
[0200] S1140, the first NRF forwards the NF information subscription request to the third NRF.
[0201] In some embodiments, the first NRF redirects the NF information subscription request to the third NRF.
[0202] S1150, the third NRF replies to the first NRF with the subscription request.
[0203] In some embodiments, the subscription request can include a subscription success or a subscription failure.
[0204] In the case where the subscription request includes a subscription success, a reply "201 Created" can be returned, and the data SubscriptionData of the subscription success can be included.
[0205] In the case of a subscription failure, a reply "3xx" can be included, indicating redirection; a reply "4xx" can be included, where "400 Bad Request" contains a ProblemDetails IE, i.e., a fault reason, if the Share Data is configured on the NRF by OAM, but the Share Data corresponding to the Share Data ID is not configured, the ProblemDetail can be SHARED_DATA_NOT_CONFIGURED.
[0206] If the Share Data on the NRF is not configured by OAM, and the Share Data corresponding to the Share Data ID is not found, the ProblemDetail can be SHARED_DATA_ID_UNKNOWN. A reply "5xx" can be included, indicating an internal failure of the NRF.
[0207] S1160, the first NRF forwards the reply to the subscription request to the subscriber.
[0208] S1170, the shared information changes.
[0209] In some embodiments, the Share Data in the third NRF changes, and the change reason can be that other NF / SCP modifies the Share Data, or that OAM modifies the Share Data, or that the NRF itself or other NRF modifies the Share Data.
[0210] S1180, the third NRF sends a state change notification to the subscriber.
[0211] In some embodiments, the NRF feeds back the changed Share Data ID and the changed Share Data value to the NF / SCP.
[0212] S1190, the subscription sends a state change notification response to the third NRF.
[0213] In some embodiments, the state change notification response can include a variety of information: the NF / SCP modifies its local Share Data according to the changed value of the Share Data, and returns "204 No content". If the local corresponding Share Data cannot be found, "404 Not Found" is returned to the NRF with ProblemDetails. If redirection is required, "3xx" is returned. If there is an internal failure of the NF / SCP, "5xx" is returned.
[0214] Based on the same inventive concept, the disclosure embodiments also provide a subscription device, as follows. Since the principles of the device embodiments for solving problems are similar to the above-mentioned method embodiments, the implementation of the device embodiments can be referred to the implementation of the above-mentioned method embodiments, and the repeated parts will not be described here.
[0215] The disclosure embodiments provide a subscription device, and it should be noted that the device is applied to the first NRF.
[0216] Figure 12 A schematic diagram of a subscription device in the embodiments of the disclosure is shown.
[0217] As shown in Figure 12 the device 1200 can include:
[0218] The first receiving module 1210 is configured to receive a subscription request sent by a subscriber, the subscription request including a shared information identifier and / or shared information.
[0219] The first sending module 1220 is configured to send the subscription request to a second NRF according to the shared information identifier or the shared information, the subscriber including a network function NF and an SCP.
[0220] In some embodiments, the device further includes:
[0221] The determining module is configured to determine whether there is corresponding shared information identifier and / or shared information locally based on the shared information identifier and / or the shared information.
[0222] The first sending module includes:
[0223] The first sending unit is configured to send the subscription request to the second NRF according to the shared information identifier or the shared information in the case that there is no corresponding shared information identifier and / or shared information locally.
[0224] In some embodiments, the shared information includes the same portion of information of multiple NFs registered in the NRF.
[0225] In some embodiments, the apparatus further comprises:
[0226] The second receiving module is configured to receive a subscription failure message sent by the second NRF when the second NRF determines that the subscription fails, where the subscription failure message includes at least one of redirection information, fault cause information, and internal fault information.
[0227] In some embodiments, the fault cause information includes: OAM not configuring the shared information corresponding to the shared information identifier and not finding the shared information corresponding to the shared information identifier.
[0228] In some embodiments, the apparatus further comprises:
[0229] The forwarding module is used to forward the subscription failure message to the subscriber when receiving the subscription failure message sent by the second NRF.
[0230] In some embodiments, the apparatus further comprises:
[0231] The third sending module is configured to send the subscription request to the third NRF based on the redirection information.
[0232] The subscription device provided by the embodiment of the present disclosure receives a subscription request sent by a subscriber, and sends the subscription request to a second NRF according to a shared information identifier or shared information, thereby realizing synchronization of shared information across NRFs, avoiding the problem of information asynchrony between NRF and subscriber, and improving the efficiency of subscription.
[0233] Based on the same inventive concept, another subscription device is provided in the embodiments of the present disclosure, such as the following embodiment. Since the principle of solving the problem in the embodiment of the device is similar to that in the above method embodiment, the implementation of the embodiment of the device can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.
[0234] A subscription device is provided in an embodiment of the present disclosure. It should be noted that the device is applied to a subscriber, and the subscriber includes an NF and an SCP.
[0235] Figure 13 A schematic diagram of another subscription device in an embodiment of the present disclosure is shown.
[0236] like Figure 13 As shown, the apparatus 1300 may include:
[0237] The second sending module 1310 is configured to send a subscription request to the first network repository function NRF, where the subscription request includes a shared information identifier and / or shared information, so that the first NRF sends the subscription request to the second NRF.
[0238] In some embodiments, the shared information comprises: a same part of a plurality of NF information registered in the NRF.
[0239] In some embodiments, the apparatus further comprises:
[0240] The third receiving module, in a case where the second NRF determines that the subscription fails, is configured to receive a subscription failure message sent by the second NRF and forwarded by the first NRF, the subscription failure message comprising at least one of redirection information, failure cause information, and internal failure information.
[0241] In some embodiments, the failure cause information comprises: the OAM does not configure the shared information corresponding to the shared information identifier, and the shared information corresponding to the shared information identifier is not found.
[0242] In some embodiments, the apparatus further comprises:
[0243] The fourth receiving module, in a case where the shared information changes, is configured to receive a state change notification sent by the second NRF, the state change notification comprising a shared information identifier of the changed shared information and / or the changed shared information.
[0244] In some embodiments, the apparatus further comprises:
[0245] The synchronizing module is configured to synchronize the shared information based on the state change notification.
[0246] The fourth sending module, in a case where it is determined that the synchronization fails, is configured to send a synchronization failure message to the second NRF, the synchronization failure message comprising at least one of redirection information, local absence of the shared information, and internal failure information.
[0247] The subscription apparatus provided by the embodiments of the present disclosure receives a subscription request sent by a subscriber, and sends the subscription request to the second NRF according to a shared information identifier or shared information, thereby realizing synchronization of the shared information across the NRFs, avoiding the problem of asynchronous information between the NRF and the subscriber, and improving the efficiency of the subscription.
[0248] The subscription apparatus provided by the embodiments of the present disclosure can be used to execute the positioning method provided by each method embodiment, and has similar implementation principles and technical effects. For the sake of brevity, the same will not be repeated here.
[0249] Those skilled in the art can understand that each aspect of the present disclosure can be implemented as a system, a method or a program product. Therefore, each aspect of the present disclosure can be embodied as a complete hardware embodiment, a complete software embodiment (including firmware, microcode, etc.), or an embodiment combining hardware and software aspects, which can be collectively referred to as a "circuit", a "module" or a "system" here.
[0250] The electronic device 1400 according to this embodiment of the present disclosure will be described below with reference to Figure 14 Figure 14 The electronic device 1400 shown is merely an example, and should not be taken as limiting the functionality or use of embodiments of the present disclosure.
[0251] As Figure 14 shown, the electronic device 1400 is in the form of a general computing device. Components of the electronic device 1400 can include, but are not limited to, the at least one processing unit 1410 described above, the at least one storage unit 1420 described above, a bus 1430 that connects different system components, including the storage unit 1420 and the processing unit 1410.
[0252] The storage unit stores program code that can be executed by the processing unit 1410, such that the processing unit 1410 performs the steps described above in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the present disclosure. For example, the processing unit 1410 can perform the following steps of the method embodiments described above:
[0253] receiving a subscription request sent by a subscriber, the subscription request including a shared information identifier and / or shared information;
[0254] sending the subscription request to a second NRF according to the shared information identifier or the shared information, the subscriber including a network function NF and a service communication proxy SCP. Or.
[0255] sending a subscription request to a first network repository function NRF, the subscription request including a shared information identifier and / or shared information, so that the first NRF sends the subscription request to a second NRF.
[0256] The storage unit 1420 can include a readable medium in the form of volatile storage such as a random access memory (RAM) 14201 and / or cache memory 14202, and can further include a read-only memory (ROM) 14203.
[0257] The storage unit 1420 can also include program / utility 14204 having a set of at least one program modules 14205, including but not limited to, an operating system, one or more application programs, other program modules, and program data, each or a combination thereof, which can include implementation of a network environment.
[0258] Bus 1430 can be one or more of several types of bus structure including a memory bus or memory controller, a peripheral bus, a graphics bus, a processor or local bus using any of a variety of bus architectures.
[0259] Electronic device 1400 can also be in subscription with one or more external devices 1440 such as a keyboard, a pointing device, a Bluetooth device, etc. and can also be in subscription with one or more devices that enable a user to interact with electronic device 1400 and / or one or more devices that enable electronic device 1400 to communicate with one or more other computing devices. Such subscription can be through input / output (I / O) interface 1450. Further, electronic device 1400 can also be in subscription with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or the public networks, such as the Internet) through network adapter 1460. As illustrated, network adapter 1460 is in subscription with the other modules of electronic device 1400 through bus 1430. It should be appreciated that although not shown, other hardware and / or software modules could be in subscription with electronic device 1400 including, but not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.
[0260] Those skilled in the art will readily understand that the example embodiments described herein can be implemented by software and / or by hardware coupled with software, as described above. Thus, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash disk, a mobile hard disk, or the like) or a network, and includes a number of instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to perform the methods according to the embodiments of the present disclosure.
[0261] In the example embodiments of the present disclosure, a computer readable storage medium is also provided, which can be a readable signal medium or a readable storage medium. A program product capable of implementing the above method of the present disclosure is stored on the computer readable storage medium. In some possible embodiments, various aspects of the present disclosure can also be implemented in the form of a program product, which includes program codes for causing a terminal device to perform the steps described in the above “example method” section according to various example embodiments of the present disclosure when the program product is run on the terminal device.
[0262] More specific examples of the computer-readable storage medium in the present disclosure can include but are not limited to an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0263] In the present disclosure, a computer readable storage medium can include a data signal carrying the readable program code in a baseband or in a carrier wave. Such a propagated data signal can take a wide variety of forms, including but not limited to electro-magnetic, optical, or any suitable combination thereof. A computer readable medium can also be any medium that can be read by a computer or a device that can be used to store or transport the program in a functional manner, rather than the medium that the program is presented on.
[0264] Optionally, program code embodied on a computer readable storage medium can be transmitted by any data transmission techniques, including but not limited to radio frequency, wireless, cable, wire, optical fiber cable, or any suitable combination thereof.
[0265] In an implementation, the program code for carrying out operations of the present disclosure can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++, and the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on a user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's device and partly on a remote computing device or entirely on the remote computing device or server. In the latter scenario, the remote computing device can be connected to the user's device through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computing device, such as through the Internet using an Internet Service Provider (ISP).
[0266] It should be noted that, although several modules or units for a device to perform actions are mentioned in the above detailed description, the division into the modules or units is not mandatory. In fact, according to an embodiment of the present disclosure, features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, features and functions of one module or unit described above can be further divided into a plurality of modules or units.
[0267] Moreover, although individual steps of the methods in the present disclosure are described in a particular order in the drawings, this is not required or implied, nor is it necessary to perform all of the steps shown to achieve the desired result. Additionally or alternatively, certain steps can be omitted, combined into a single step, performed in a different order, broken down into multiple steps, and / or the like.
[0268] From the above description of the embodiments, those skilled in the art will readily perceive that the example embodiments described herein can be implemented by software and / or by software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash disk, a mobile hard disk, or the like) or a network, and includes a number of instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the methods according to the embodiments of the present disclosure.
[0269] Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure following the general principles thereof and including such departures from the present disclosure that come within known use or custom in the art to which the present disclosure pertains. The specification and examples are to be regarded as illustrative only, and the true scope and spirit of the present disclosure are indicated by the appended claims.
Claims
1. A subscription method, characterized by, The method is applied to a first network repository function (NRF), and comprises the following steps: receiving a subscription request sent by a subscriber, wherein the subscription request comprises a shared information identifier and / or shared information; sending the subscription request to a second NRF according to the shared information identifier and / or the shared information, wherein the subscriber comprises a network function (NF) and a service communication proxy (SCP).
2. The subscription method of claim 1, wherein, The method further comprises the following steps: determining whether there is a corresponding shared information identifier and / or shared information locally based on the shared information identifier and / or the shared information; the step of sending the subscription request to the second NRF according to the shared information identifier or the shared information comprises the following steps: in the case where there is no corresponding shared information identifier and / or shared information locally, sending the subscription request to the second NRF according to the shared information identifier or the shared information.
3. The subscription method of claim 1, wherein, The shared information comprises an identical part of a plurality of NF information registered in the NRF.
4. The subscription method according to claim 1, wherein: The method further comprises the following steps:
5. The subscription method of claim 4, wherein, in the case where the second NRF determines that the subscription fails, receiving a subscription failure message sent by the second NRF, wherein the subscription failure message comprises at least one of redirection information, failure cause information and internal failure information.
6. The subscription method of claim 4, wherein, The failure cause information comprises that an operation and maintenance (OAM) does not configure shared information corresponding to the shared information identifier and that the shared information corresponding to the shared information identifier is not found. The method further comprises the following steps:
7. The subscription method of claim 4, wherein, in the case where the second NRF sends the subscription failure message, forwarding the subscription failure message to the subscriber. The method further comprises the following steps:
8. A subscription method, characterized by, sending the subscription request to a third NRF based on the redirection information. The method is applied to a subscriber, wherein the subscriber comprises an NF and an SCP, and comprises the following steps:
9. The subscription method of claim 8, wherein, sending a subscription request to a first network repository function (NRF), wherein the subscription request comprises a shared information identifier and / or shared information, so that the first NRF sends the subscription request to a second NRF.
10. The subscription method of claim 8, wherein, The shared information comprises an identical part of a plurality of NF information registered in the NRF. The method further comprises the following steps:
11. The subscription method of claim 10, wherein, in the case where the second NRF determines that the subscription fails, receiving a subscription failure message sent by the second NRF and forwarded by the first NRF, wherein the subscription failure message comprises at least one of redirection information, failure cause information and internal failure information.
12. The subscription method of claim 8, wherein, The failure cause information comprises that an OAM does not configure shared information corresponding to the shared information identifier and that the shared information corresponding to the shared information identifier is not found. The method further comprises the following steps:
13. The subscription method of claim 8, wherein, in the case where the shared information changes, receiving a state change notification sent by the second NRF, wherein the state change notification comprises a changed shared information identifier and / or changed shared information. The method further comprises the following steps: synchronizing the shared information based on the state change notification; 14. A subscription device, characterized by in the case where it is determined that the synchronization fails, sending a synchronization failure message to the second NRF, wherein the synchronization failure message comprises at least one of redirection information, local absence of the shared information and internal failure information. The method is applied to a first network repository function (NRF), and comprises the following steps: The first receiving module is configured to receive a subscription request sent by the subscriber, wherein the subscription request comprises a shared information identifier and / or shared information. The first sending module is configured to send the subscription request to a second NRF according to the shared information identifier and / or the shared information, wherein the subscriber comprises a network function (NF) and an SCP.
15. A subscription device, characterized by The application is applied to a subscriber, wherein the subscriber comprises a network function (NF) and an SCP, and comprises: The second sending module is configured to send a subscription request to a first network repository function (NRF), wherein the subscription request comprises a shared information identifier and / or shared information, so that the first NRF sends the subscription request to a second NRF.
16. An electronic device, comprising: The application comprises: a processor; and a memory configured to store executable instructions of the processor. The processor is configured to execute the executable instructions to perform the subscription method in any one of claims 1-13.
17. A computer readable storage medium having stored thereon a computer program, characterized in that The computer program is executed by the processor to implement the subscription method in any one of claims 1-13.