Method for informing NF plan removal

Abstract

A wireless communication method for use in a first network function (NF) is disclosed. The method includes transmitting an NF update message to a network warehousing function (NRF), the NF update message including planned removal information indicating that a first NF is planned to be removed.

Description

[0001] This document relates generally to wireless communications and, in particular, to 5G communications.

[0002] In the 5G system, the core network consists of various virtual network functions (NFs) that provide different services. Among the different types of NFs, a special NF named NRF (Network Repository Function) is designed as a central registration node for various types of NFs. After a NF is deployed in the network and is ready to provide services, the NF should register itself in the NRF to indicate that its status is discoverable (which means that the NF can be discovered and is ready to provide services). As an alternative, the OAM (Operation, Administration, and Maintenance) system can be used to register a batch of NFs to the NRF.

[0003] Once a NF is registered with the NRF and its status is set to be discoverable, other NFs can call the NRF service (i.e., discovery service) to discover and select the registered NF, and can then subscribe to the NF profile changes of the selected NF from the NRF. The NRF then keeps monitoring the status of the selected NF periodically. If the NRF detects that the selected / monitored NF is unavailable within a period, the NRF sets the NF status of the monitored NF to "UNDISCOVERABLE" and notifies those NFs that subscribed to the NF profile changes of the selected / monitored NF.

[0004] A NF may request the NRF to update its NF profile in the NRF, for example to change its service parameters or to set its NF status to “UNDISCOVERABLE”. In this case, the NRF sends a notification to all NFs that subscribe to the NF profile change of that NF.

[0005] This document relates to a method for a NF to inform the NRF and / or other NFs of its planned removal and thereby trigger the reselection of a replacement NF to continue in service.

[0006] This document relates to methods and apparatus for continuing services when planned removal of NFs is required, and in particular to methods and apparatus for notifying planned removal of NFs and triggering reselection of replacement NFs to continue associated services.

[0007] The present disclosure relates to a wireless communication method used in a first network function (NF). The method includes: sending a NF update message to a network repositories function (NRF), the NF update message including planned removal information indicating that the first NF is planned to be removed.

[0008] Various embodiments may preferably implement the following features:

[0009] Preferably, the planned removal information includes at least one of the following: a planned removal indication, or a planned removal time indication.

[0010] Preferably, the planned removal indication includes an indication in a status value of the NF planned to be removed or an indication in a NF configuration file.

[0011] Preferably, the planned removal time indication indicates the time when the first NF is planned to be removed.

[0012] Preferably, the NF update message further includes a replacement NF candidate list configured to take over at least one user served by the first NF.

[0013] The present disclosure relates to a wireless communication method used in a network warehouse function (NRF). The method comprises:

[0014] receiving a NF update message from a first network function (NF), the NF update message including planned removal information indicating that the first NF is planned to be removed, and

[0015] A notification message is sent to at least one second NF, where the notification message includes planned removal information.

[0016] Various embodiments may preferably implement the following features:

[0017] Preferably, the wireless communication method further includes: recording the planned removal information in a NF configuration file of the first NF.

[0018] Preferably, the planned removal information includes at least one of the following: a planned removal indication, or a planned removal time indication.

[0019] Preferably, the planned removal indication includes an indication in a status value of the NF planned to be removed or an indication in a NF configuration file.

[0020] Preferably, the planned removal time indication indicates the time when the first NF is planned to be removed.

[0021] Preferably, the notification message further includes a list of replacement NF candidates configured to take over at least one user served by the first NF.

[0022] Preferably, the list of replacement NF candidates is determined by the NRF.

[0023] Preferably, the NF update message further includes a replacement NF candidate list configured to take over at least one user served by the first NF.

[0024] Preferably, at least one second NF subscribes to the NF state change or NF profile change of the first NF from the NRF.

[0025] The present disclosure relates to a wireless communication method used in a second network function (NF). The method includes:

[0026] receiving a notification message from a network repositories function (NRF), the notification message including planned removal information indicating that the first NF is planned to be removed, and

[0027] At least one replacement NF configured to take over at least one user served by the first NF is selected based on the planned removal information.

[0028] Various embodiments may preferably implement the following features:

[0029] Preferably, the planned removal information includes at least one of the following: a planned removal indication, or a planned removal time indication.

[0030] Preferably, the planned removal indication includes an indication in a status value of the NF planned to be removed or an indication in a NF configuration file.

[0031] Preferably, the planned removal time indication indicates the time when the first NF is planned to be removed.

[0032] Preferably, the notification message further includes a list of replacement NF candidates configured to take over at least one user served by the first NF.

[0033] Preferably, selecting at least one replacement NF configured to take over at least one user served by the first NF based on the planned removal information comprises:

[0034] At least one replacement NF is selected from a list of replacement NF candidates provided by the NRF.

[0035] Preferably, selecting at least one replacement NF configured to take over at least one user served by the first NF based on the planned removal information comprises:

[0036] A NF discovery process is performed to select at least one replacement NF.

[0037] Preferably, the wireless communication method further includes: transferring at least one user served by the first NF to at least one substitute NF.

[0038] Preferably, the wireless communication method further comprises: transferring at least one user served by the first NF to at least one replacement NF no later than the removal time.

[0039] Preferably, the removal time is indicated by the planned removal information.

[0040] Preferably, the removal time is determined by the second NF.

[0041] Preferably, the second NF subscribes to the NF state change or NF profile change of the first NF from the NRF.

[0042] The present disclosure relates to a wireless device for a first NF. The wireless device includes:

[0043] The communication unit is configured to send a NF update message to the NRF, wherein the NF update message includes planned removal information indicating that the first NF is planned to be removed.

[0044] Various embodiments may preferably implement the following features:

[0045] Preferably, the wireless device further comprises: a processor, wherein the processor is configured to execute any of the wireless communication methods mentioned above.

[0046] The present disclosure relates to a wireless device for NRF. The wireless device comprises:

[0047] A communication unit, the communication unit being configured to:

[0048] receiving a NF update message from the first NF, the NF update message including planned removal information indicating that the first NF is planned to be removed, and

[0049] A notification message is sent to at least one second NF, where the notification message includes planned removal information.

[0050] Various embodiments may preferably implement the following features:

[0051] Preferably, the wireless device further includes: a processor, wherein the processor is configured to execute any of the wireless communication methods mentioned above.

[0052] The present disclosure relates to a wireless device for a second NF. The wireless device includes:

[0053] a communication unit configured to receive a notification message from a network repositories function (NRF), the notification message including planned removal information indicating that the first NF is planned to be removed, and

[0054] A processor is configured to select at least one replacement NF configured to take over at least one user served by the first NF based on the planned removal information.

[0055] Various embodiments may preferably implement the following features:

[0056] Preferably, the processor is further configured to execute any of the wireless communication methods mentioned above.

[0057] The present disclosure relates to a computer program product, which includes a computer-readable program medium code stored thereon. When the code is executed by a processor, the processor is caused to implement any one of the wireless communication methods described above.

[0058] The exemplary embodiments disclosed herein are intended to provide features that will become apparent by reference to the following description when taken in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who have read this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0059] Therefore, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present disclosure. Therefore, it will be understood by those of ordinary skill in the art that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless otherwise expressly provided, the present disclosure is not limited to the specific order or hierarchy presented.

[0060] The above and other aspects and their embodiments are described in more detail in the drawings, the description and the claims.

[0061] Figure 1 A schematic diagram of a network according to an embodiment of the present disclosure is shown.

[0062] Figure 2 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0063] Figure 3 A schematic diagram showing a process according to an embodiment of the present disclosure is shown.

[0064] Figure 4 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown.

[0065] Figure 5 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown.

[0066] Figures 6 to 8 A flow chart of a method according to an embodiment of the present disclosure is shown.

[0067] Figure 1 A schematic diagram of a network (architecture) according to an embodiment of the present disclosure is shown. Figure 1In the network, there are the following network entities or network functions:

[0068] 1) UE (User Equipment):

[0069] UE corresponds to a mobile terminal accessing a 5G network.

[0070] 2)NG RAN (Next Generation Radio Access Network).

[0071] In a 5G network, NG RAN is an NR (New Radio) base station, also named gNB. In an embodiment, NG RAN may also be referred to as RAN or RAN node.

[0072] 3) NRF (Network Repository Function):

[0073] NRF provides a central registration point for all types of NFs and provides NF discovery capabilities.

[0074] 4)AMF (Access and Mobility Management Function):

[0075] The AMF provides access management and mobility management for the UE, such as registration with the network, registration during UE mobility, etc.

[0076] 5)SMF(Session Management Function):

[0077] SMF provides PDU session management for UE, such as IP address allocation, QoS flow establishment, etc.

[0078] 6) UPF (User Plane Function):

[0079] UPF provides IP traffic routing and forwarding management.

[0080] 7) PCF (Policy Control Function)

[0081] The PCF provides the QoS policy rules to the control plane function to implement the QoS policy rules.

[0082] 8)AF(Application Function):

[0083] The AF provides instructions to the PCF to affect QoS policy rules.

[0084] Figure 2 FIG. 1 is a schematic diagram showing a process of subscribing to and notifying NF status / configuration file changes according to an embodiment of the present disclosure. Figure 2 In NF, once a NF successfully registers with NRF, the NF can be discovered by another NF. The NF that discovers the registered NF can also subscribe to the NF status / profile changes of the registered NF from NRF. Figure 2 The process shown includes the following steps:

[0085] Step 201: NF1 (eg SMF) and NRF perform NF registration process.

[0086] In step 201a, NF1 sends a NF Registration Request to NRF, where the NF Registration Request includes the entire NF profile of NF1. At the same time, NF1 can also include a suggested timer (e.g., a heartbeat timer) in the request message for negotiation. If the request is accepted, in step 201b, NRF sends a NF Registration Response with the accepted (heartbeat) timer.

[0087] Once NF1 successfully registers with the NRF, the NF status of NF1 is set to “REGISTERED” (eg, discoverable) in the NRF.

[0088] Step 202: Similarly, in steps 202a and 202b, NF2 (eg, AMF) performs the NF registration process with the NRF.

[0089] Step 203: NF2 performs a NF discovery process to select an appropriate NF that can support the service requirement.

[0090] Specifically, in step 203a, NF2 sends a NF discovery request to NRF to indicate the target NF type to be discovered in the request message. In step 203b, NRF performs target NF filtering (process) and sends a NF discovery response. The response message contains / includes a candidate NF list by providing the NF profile of each candidate NF.

[0091] For example, in step 203, the AMF (i.e., NF2) wants to select a target SMF. The AMF indicates that the target NF type is "SMF" in the request message sent to the NRF. The NRF filters out the candidate SMFs and returns the candidate NF list to the AMF. Then, the AMF selects an SMF (e.g., NF1) from the returned candidate NF list.

[0092] In this embodiment, NF2 selects NF1 from the returned candidate NF list.

[0093] Step 204: NF2 and NRF perform the NF status subscription process to subscribe to the NF status change or NF configuration file change of NF1.

[0094] For example, in step 204a, NF2 sends a NF status subscription request to NRF, wherein the NF status subscription request indicates that NF1 is the target NF for subscription. In step 204b, NRF accepts the subscription and sends a NF status subscription response to NF2.

[0095] Step 205: NF1 and NRF perform the NF registration update process to update the NF status of NF1 or update the NF service parameters of NF1.

[0096] For example, if the heartbeat timer is about to expire, NF1 sends a NF Update Request to NRF in step 205a. In step 205b, NRF refreshes the heartbeat timer, maintains the state of NF1, and sends a NF Registration Response.

[0097] In an embodiment, if NF1 needs to update service parameters, then in step 205a, NF1 sends a NF update request to NRF, wherein the NF update request is sent together with the updated service parameters or the entire updated NF configuration file. In step 205b, NRF updates the NF configuration file accordingly and sends a NF update response.

[0098] In an embodiment, if NF1 needs to change the NF state of NF1 from the previous NF state registered in NRF to a new NF state, then in step 205a, NF1 sends a NF update request to NRF, wherein the NF update request is sent together with the new NF state. According to the NF update request, in step 205b, NRF updates the NF state in the NF profile of NF1 and sends a NF update response. For example, NF1 may want to exit the service and decide to set its own NF state to "UNDISCOVERABLE".

[0099] Step 206: The NRF keeps monitoring the NF state change or NF profile change of a NF (eg, NF1) whose NF state / profile change is subscribed by other NFs.

[0100] If an NF service parameter update of a monitored NF is detected, the NRF triggers a notification to those NFs that subscribe to the NF status change of the monitored NF.

[0101] If it is detected that a NF is no longer available (e.g., by checking the periodic heartbeat process), the NRF sets the NF state of that NF to "SUSPENDED". For example, if the NRF does not receive two or three consecutive heartbeats from a NF, the NRF may believe / determine that the NF is now faulty and sets the NF state of that NF to "SUSPENDED".

[0102] Step 207: NRF sends a notification to NF2 to inform NF1 of the NF status change or NF configuration file change.

[0103] In step 207a, the NRF sends a NF Status Notification Request to NF2, wherein the NF Status Notification Request includes the updated entire NF profile of NF1 and / or the updated NF service parameters (e.g., updated NF status) of NF1. In step 207b, NF2 thus acknowledges the notification and sends a NF Status Notification Response.

[0104] If NF2 (e.g. AMF) confirms the NF status change of NF1 (e.g. SMF) (e.g. change to "SUSPENDED"), NF2 can trigger another NF discovery process to NRF to select another suitable NF (e.g. another SMF) to continue the service.

[0105] Figure 2 The process shown supports monitoring and notification of NF service parameter changes / updates or NF status changes (e.g., NF fails, NF determines to exit service). Figure 2 The process shown may not be able to well support the situation where the NF is planned to be removed. In the present disclosure, the planned removal of the NF means that the NF is configured to exit the service after a configured period or at a specific time. Once the NF announces its planned removal, all existing users served by the NF are expected to be smoothly transferred to other NFs, which can provide equivalent services without causing a large amount of signaling in a short period of time. It is noted that during the configured period for the planned removal, or before the specific time of the planned removal, the NF can still serve the existing users served by the NF, but will not accept any new users. For a NF to be planned to be removed, if the NF state is set to "SUSPENDED" according to the existing mechanism, other NFs that receive the NF state notification from the NRF will immediately select an alternative NF to transfer users from the NF displayed as the "SUSPENDED" state. Such an immediate transfer of the entire users of the NF to be planned to be removed will definitely cause a large amount of signaling to the network in a short period of time. Therefore, the existing mechanism cannot well support the planned removal of a NF.

[0106] In an embodiment, planned removal is also referred to as scheduled removal.

[0107] In an embodiment, once a NF is configured / scheduled to have / perform a planned removal (i.e., exit / end service after a configured period or at a specified / given time), the NF may notify the NRF of the planned removal. The NRF may select a replacement NF and inform the related NFs subscribed to the NF state change configured to perform the planned removal of the NF.

[0108] Figure 3 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 3In the process, the NF configured to execute the planned removal notifies the NRF of the planned removal, and the associated notification process is triggered accordingly. Specifically, Figure 3 The process shown includes the following steps.

[0109] Step 301: NF1 (eg, SMF) and NRF perform NF registration process. Step 301 (ie, steps 301a and 301b) and Figure 2 The steps 201 shown (ie, steps 201a and 201b) are similar.

[0110] Step 302: NF2 (eg AMF) also performs the NF registration process with NRF. Step 302 (ie, steps 302a and 302b) may refer to Figure 2 Step 202 (ie, steps 202a and 202b) is shown.

[0111] Step 303: NF2 performs the NF discovery process and selects NF1, which is Figure 2 The steps 203 shown (ie, steps 303a and 303b) are similar.

[0112] Step 304: NF2 and NRF perform the NF status subscription process to subscribe to the NF status change or NF configuration file change of NF1. Step 304 (ie, steps 304a and 304b) can refer to Figure 2 Step 204 (ie, steps 204a and 204b) is shown.

[0113] Step 305: NF1 determines that a scheduled removal is scheduled / needed. That is, the NF will exit service after a configured period (e.g., 6 hours) or at a given time (e.g., GMT+8 16:00). Before the configured scheduled removal, NF1 is still able to serve existing users, but will not serve any new users. At the same time, NF1 expects that existing users served by NF1 will be smoothly transferred to (one or more) other replacement NFs.

[0114] Step 306: NF1 performs the NF registration update process to the NRF to indicate that it is planned to be removed.

[0115] In step 306a, NF1 sends a NF update request to NRF, wherein the NF update request includes planned removal information (i.e., information to be removed). The planned removal information may include at least one of the following:

[0116] (a) a planned removal instruction, or

[0117] (b) Indication of the planned removal time.

[0118] In an embodiment, the planned removal indication is used / configured to indicate that the NF is scheduled / configured to be removed after a certain configured period or at a given time. In an embodiment, the planned removal indication can be a NF status value indicating the planned removal (e.g., "PLANNED_REMOVAL") or a separate indication included in the NF configuration file.

[0119] In an embodiment, the planned removal time indication indicates the time of the planned removal. For example, the planned removal time indication may indicate a planned removal timer. The planned removal is expected to occur when / after the planned removal timer expires. The planned removal timer may be presented as a UTC time or a timestamp. As an alternative, the planned removal time indication may indicate a specified / given / specific time of the planned removal. The planned removal is expected to occur at / after the specified / given / specific time. In another embodiment, the planned removal time indication may indicate a time offset / period of the planned removal. In the present embodiment, the planned removal is configured / scheduled to occur after a planned removal time offset / period (e.g., 6 hours) after the current time (e.g., the time of sending / receiving an NF update request carrying the planned removal information).

[0120] In addition, in the NF update request sent in step 306a, NF1 may also include a list of replacement NFs that can take over the users served by NF1.

[0121] In step 306b, the NRF confirms that NF1 will be planned to be removed, records the planned removal information in the NF configuration file of NF1, and sends an NF update response to NF1.

[0122] Step 307: Upon / after receiving the planned removal information from NF1 in step 306, the NRF selects a replacement NF, and determines to trigger a notification to each of the related NFs that have subscribed to the NF status change of NF1.

[0123] If NF1 specifies / sends a replacement NF in step 306, the NRF may directly adopt the specified replacement NF as the selected replacement NF. Alternatively or additionally, the NRF may check the NF profile of NF1 to obtain possible replacement NFs (e.g., backup NFs registered in the NF profile and / or NFs belonging to the same NF set).

[0124] Step 308: NRF sends a notification to NF2 to inform that NF1 is scheduled to be removed.

[0125] In step 308a, the NRF sends a NF status notification request to NF2, wherein the NF status notification request includes the planned removal information of NF 1. The planned removal information of NF 1 may be included in the updated NF configuration file of NF 1, or presented as separate information outside the NF configuration file.

[0126] The planned removal information may include at least one of the following:

[0127] (a) a planned removal instruction, or

[0128] (b) Indication of the planned removal time.

[0129] In an embodiment, the planned removal indication is used / configured to indicate that the NF is scheduled / configured to be removed after a certain configured period or at a given time. In an embodiment, the planned removal indication can be a NF status value indicating the planned removal (e.g., "PLANNED_REMOVAL") or a separate indication included in the NF configuration file.

[0130] In an embodiment, the planned removal time indication indicates the time of the planned removal. For example, the planned removal time indication can be indicated as a planned removal timer. The planned removal is expected to occur when / after the planned removal timer expires. The planned removal timer can be presented as a UTC time or a timestamp. As an alternative, the planned removal time indication can indicate a specified / given / specific time of the planned removal. The planned removal is expected to occur at / after the specified / given / specific time. In another embodiment, the planned removal time indication can be indicated as a planned removal time offset / period. In the present embodiment, the planned removal is configured / scheduled to occur after a planned removal time offset / period (e.g., 6 hours) after the current time (e.g., the time of sending / receiving an NF update request carrying the planned removal information).

[0131] Confirming the planned removal information of NF1, NF2 sends a NF status notification response to NRF.

[0132] Step 309: After / when NF2 confirms the planned removal information of NF1, NF2 may reselect (one or more) replacement NFs to transfer the user to the new NF for continued service.

[0133] In an embodiment where the NF status notification message in step 308 includes a replacement NF list (e.g., SMF), NF2 selects one from the replacement NF list as a replacement NF and transfers the affected users (i.e., users served by NF1) to the selected replacement NF. If no replacement NF is indicated in step 308, NF2 may initiate a separate NF discovery to the NRF to find (one or more) replacement NFs.

[0134] In an embodiment where a planned removal time indication is provided in step 308, user transfer should be scheduled before the indicated planned removal time indicated by the planned removal time indication. Because the number of affected users (i.e., users served by NF1) may be huge, user transfer may be appropriately scheduled to avoid huge signaling overhead in a short period of time. In an embodiment, if no explicit planned removal time indication is provided in step 308, NF2 may determine an appropriate planned removal time based on, for example, a local policy to smoothly transfer affected users from the NF to be planned to be removed to other replacement NFs.

[0135] Figure 4 A schematic diagram of a wireless terminal 40 according to an embodiment of the present disclosure is provided. The wireless terminal 40 may be a user equipment (UE), a mobile phone, a laptop computer, a tablet computer, an e-book, or a portable computer system, and is not limited herein. The wireless terminal 40 may include a processor 400 (such as a microprocessor or an application-specific integrated circuit (ASIC)), a storage unit 410, and a communication unit 420. The storage unit 410 may be any data storage device that stores program code 412 accessed and executed by the processor 200. Embodiments of the storage unit 410 include, but are not limited to, a subscriber identity module (SIM), a read-only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, and an optical data storage device. The communication unit 420 may be a transceiver, and is used to send and receive signals (such as messages or packets) according to the processing results of the processor 400. In an embodiment, the communication unit 420 communicates with the communication unit 420 via Figure 4 At least one antenna 422 is shown for transmitting and receiving signals.

[0136] In an embodiment, the storage unit 410 and the program code 412 may be omitted, and the processor 400 may include a storage unit having stored program code.

[0137] Processor 400 may implement any of the steps of the exemplary embodiments for wireless terminal 40 , for example, by executing program code 412 .

[0138] The communication unit 420 may be a transceiver. Alternatively or additionally, the communication unit 420 may combine a transmitting unit and a receiving unit, both of which are configured to send signals to and receive signals from a wireless network node (eg, a base station), respectively.

[0139] Figure 5A schematic diagram of a radio network node 50 according to an embodiment of the present disclosure is provided. The radio network node 50 may be a satellite, a base station (BS), a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN) node, a next generation RAN (NG-RAN) node, a gNB, an eNB, a gNB central unit (gNB-CU), a gNB distributed unit (gNB-DU), a data network, a core network, or a radio network controller (RNC), and is not limited here. In addition, the wireless communication node 50 may include (execute) at least one network function, such as an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), an application function (AF), etc. The radio network node 50 may include a processor 500 (such as a microprocessor or an ASIC), a storage unit 510, and a communication unit 520. The storage unit 510 may be any data storage device that stores a program code 512 accessed and executed by the processor 500. Examples of the storage unit 510 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 520 may be a transceiver and is used to send and receive signals (e.g., messages or packets) according to the processing results of the processor 500. In an example, the communication unit 520 communicates with the processor 500 via Figure 5 At least one antenna 522 is shown for transmitting and receiving signals.

[0140] In an embodiment, the storage unit 510 and the program code 512 may be omitted. The processor 500 may include a storage unit having stored program code.

[0141] The processor 500 may implement any of the steps described in the exemplary embodiments for the radio network node 50 , for example, via executing the program code 512 .

[0142] The communication unit 520 may be a transceiver. Alternatively or additionally, the communication unit 520 may combine a transmitting unit and a receiving unit, both of which are respectively configured to send signals to and receive signals from a wireless terminal (eg, a user equipment or another wireless network node).

[0143] Figure 6 A flow chart of a method according to an embodiment of the present disclosure is shown. Figure 6 The method shown can be used in the first NF and comprises the following steps:

[0144] Step 601: Send an NF update message to an NRF, where the NF update message includes planned removal information indicating that a first NF is planned to be removed.

[0145] exist Figure 6In the embodiment of the present invention, the first NF may be scheduled / configured to exit / stop service and / or perform a planned removal. For example, the first NF may determine that a planned removal is needed / required / configured / scheduled. The first NF then sends a NF update message to the NRF, wherein the NF update message includes planned removal information (i.e., information that is planned to be removed), for example, to inform the NRF of the planned removal.

[0146] In an embodiment, the planned removal information includes a planned removal indication and / or a planned removal time indication.

[0147] In an embodiment, the planned removal indication may include a status value indicating the NF being planned for removal (eg, "PLANNEDREMOVAL") or an indication in a NF configuration file.

[0148] In an embodiment, the planned removal time indication indicates the time of the planned removal. For example, the planned removal time indication indicates the time of the planned removal (being executed or occurring) by indicating the planned removal timer (which can be presented in UTC time or timestamp). The (expected) planned removal occurs when / after the planned removal timer expires. As an alternative, the planned removal time indication may indicate a specified / given / specific time (e.g., UTC time) of the planned removal. The planned removal is expected to occur at / after the specified / given / specific time. As another alternative, the planned removal time indication may indicate a time offset / period of the planned removal. In the present embodiment, the planned removal is configured / scheduled to occur after a planned removal time offset / period (e.g., 6 hours) after the current time (e.g., the time of sending / receiving an NF update request carrying the planned removal information).

[0149] In an embodiment, the first NF may also include a replacement NF candidate list in the NF update message or send the replacement NF candidate list together with the NF update message. The replacement NF candidate list indicates the NF(s) configured to take over at least one user served by the first NF.

[0150] In an embodiment, the first NF may be / include at least one of SMF, SMSF (Short Message Service Function) or PCF.

[0151] In an embodiment, Figure 6 The method shown may be used / performed by a wireless device including / for a first NF. A wireless device including a first NF refers to a wireless device that performs at least a part of the functionality of the first NF.

[0152] Figure 7 A flow chart of a method according to an embodiment of the present disclosure is shown. Figure 7The method shown may be used in an NRF (e.g., a wireless device including / used in an NRF, or a wireless device performing at least part of the functionality of an NRF), and comprises the following steps:

[0153] Step 701: Receive a NF update message from a first NF, where the NF update message includes planned removal information indicating that the first NF is planned to be removed.

[0154] Step 702: Send a notification message to at least one second NF, where the notification message includes planned removal information.

[0155] exist Figure 7 In the embodiment of the present invention, the NRF receives an NF update message from a first NF. The NF update message includes planned removal information indicating that the first NF is planned to be removed. The NRF then sends a notification message including the planned removal information to at least one second NF, for example, to inform the at least one second NF of the planned removal of the first NF.

[0156] In an embodiment, after receiving the NF update message, the NRF records the planned removal information in the NF configuration file of the first NF.

[0157] In an embodiment, the planned removal information includes a planned removal indication and / or a planned removal time indication.

[0158] In an embodiment, the planned removal indication may include a status value indicating the NF being planned for removal (eg, "PLANNEDREMOVAL") or an indication in a NF configuration file.

[0159] In an embodiment, the planned removal time indication indicates the time of the planned removal. For example, the planned removal time indication indicates the time of the planned removal (being executed or occurring) by indicating the planned removal timer (which can be presented in UTC time or timestamp). The (expected) planned removal occurs when / after the planned removal timer expires. As an alternative, the planned removal time indication may indicate a specified / given / specific time (e.g., UTC time) of the planned removal. The planned removal is expected to occur at / after the specified / given / specific time. As another alternative, the planned removal time indication may indicate a time offset / period of the planned removal. In the present embodiment, the planned removal is configured / scheduled to occur after a planned removal time offset / period (e.g., 6 hours) after the current time (e.g., the time of sending / receiving an NF update request carrying the planned removal information).

[0160] In an embodiment, the notification message may also include a list of alternative NF candidates configured to take over at least one user served by the first NF. In an embodiment, the list of alternative NF candidates may be determined by the NRF. Alternatively or additionally, the list of alternative NF candidates is received from the first NF (e.g., in an NF update message).

[0161] In an embodiment, each second NF may subscribe to the NF state change or NF profile change of the first NF from the NRF. That is, the notification message may be (included in) the NF state notification request (eg, see step 308a).

[0162] In an embodiment, the first NF may be / include at least one of SMF, SMSF (Short Message Service Function) or PCF.

[0163] In an embodiment, the second NF may be / include at least one of AMF or SMF.

[0164] For example, the first NF may be an SMF or an SMSF, and the second NF may be an AMF. Alternatively, the first NF may be a PCF, and the second NF may be an AMF or an SMF.

[0165] Figure 8 A flow chart of a method according to an embodiment of the present disclosure is shown. Figure 8 The method shown may be used in a second NF (e.g., a wireless device including the second NF or a wireless device for the second NF, or a wireless device that performs at least part of the functionality of the second NF), and includes the following steps:

[0166] Step 801: Receive a notification message from an NRF, where the notification message includes planned removal information indicating that a first NF is planned to be removed.

[0167] Step 802: Select at least one replacement NF configured to take over at least one user served by the first NF based on the planned removal information.

[0168] exist Figure 8 In the embodiment of the present invention, the second NF receives a notification message from the NRF. The notification message includes planned removal information indicating that the first NF is planned to be removed. In response to / based on the planned removal information, the second NF selects / is configured to take over at least one replacement NF for at least one user (e.g., UE, wireless terminal, mobile device) served by the first NF based on the planned removal information.

[0169] In an embodiment, the planned removal information includes a planned removal indication and / or a planned removal time indication.

[0170] In an embodiment, the planned removal indication may include a status value indicating the NF being planned for removal (eg, "PLANNEDREMOVAL") or an indication in a NF configuration file.

[0171] In an embodiment, the planned removal time indication indicates the time of the planned removal. For example, the planned removal time indication indicates the time of the planned removal (being executed or occurring) by indicating the planned removal timer (which can be presented in UTC time or timestamp). The (expected) planned removal occurs when / after the planned removal timer expires. As an alternative, the planned removal time indication may indicate a specified / given / specific time (e.g., UTC time) of the planned removal. The planned removal is expected to occur at / after the specified / given / specific time. As another alternative, the planned removal time indication may indicate a time offset / period of the planned removal. In the present embodiment, the planned removal is configured / scheduled to occur after a planned removal time offset / period (e.g., 6 hours) after the current time (e.g., the time of sending / receiving an NF update request carrying the planned removal information).

[0172] In an embodiment, the second NF may determine a planned removal time for the first NF. In this embodiment, the notification message may not include a planned removal indication.

[0173] In an embodiment, the notification message also includes a list of alternative NF candidates configured to take over at least one user served by the first NF. The second NF can thus select (one or more) alternative NFs from the list of alternative NF candidates (provided by / received from the NRF).

[0174] In an embodiment, the second NF may perform a NF discovery process to select (one or more) replacement NFs (eg, see steps 203a and 203b). In this embodiment, the NRF may not provide a replacement NF candidate list for selecting (one or more) replacement NFs.

[0175] In an embodiment, after selecting (one or more) replacement NFs, the second NF transfers at least one user served by the first NF to the selected (one or more) replacement NFs. For example, the transfer may be completed no later than (i.e., before or at) the time when the first NF is scheduled to be removed. Note that the time of scheduled removal may be indicated by a scheduled removal time indication in the notification message, or determined by the second NF.

[0176] In an embodiment, the method further comprises subscribing to NF state changes or NF profile changes of the first NF from the NRF (e.g., see steps 204a and 204b). That is, the notification message may be (included in) an NF state notification request indicating a NF profile / state change associated with the first NF. For example, the first NF may be an SMF or SMSF, and the second NF may be an AMF. Alternatively, the first NF may be a PCF, and the second NF may be an AMF or SMF.

[0177] Although various embodiments of the present disclosure have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various diagrams may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present disclosure. However, these personnel will understand that the present disclosure is not limited to the illustrated example architectures or configurations, but may be implemented using a variety of alternative architectures and configurations. In addition, as will be understood by those of ordinary skill in the art, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.

[0178] It should also be understood that any reference to an element using names such as "first," "second," etc., herein generally does not limit the quantity or order of those elements. Instead, these names can be used herein as a convenient means of distinguishing between two or more elements or element instances. Therefore, reference to a first element and a second element does not mean that only two elements can be utilized, or that the first element must precede the second element in some way.

[0179] In addition, those skilled in the art will understand that information and signals may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, and symbols mentioned in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0180] Those of skill will further recognize that any of the various illustrative logical blocks, units, processors, devices, circuits, methods, and functions described in conjunction with the various aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of both), firmware, various forms of programs or design codes containing instructions (for convenience, may be referred to herein as "software" or "software units"), or any combination of these technologies.

[0181] In order to clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, units, circuits and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software or a combination of these technologies depends on the specific application and the design constraints imposed on the entire system. Skilled technicians can implement the described functionality in various ways for each specific application, but such implementation decisions will not result in departing from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc. can be configured to perform one or more functions described herein. As used herein with respect to a specific operation or function, the term "configured to" or "configured for" refers to a processor, device, component, circuit, structure, machine, unit, etc. that is physically constructed, programmed and / or arranged to perform a specific operation or function.

[0182] In addition, the technician will understand that the various illustrative logic blocks, units, devices, components and circuits described herein can be implemented or performed in an integrated circuit (IC), which can include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logic blocks, units and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. The general-purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or a combination of any other suitable configurations to perform the functions described herein. If implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein may be implemented as software stored on a computer-readable medium.

[0183] Computer readable media include both computer storage media and communication media, and the communication media include any media that can enable a computer program or code to be transferred from one place to another. The storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to store desired program codes in the form of instructions or data structures and can be accessed by a computer.

[0184] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purpose of discussion, various units are described as discrete units; however, it will be apparent to one of ordinary skill in the art that two or more units can be combined to form a single module that performs associated functions according to embodiments of the present disclosure.

[0185] In addition, in embodiments of the present disclosure, memories or other storage devices and communication components may be used. It will be appreciated that, for clarity, the above description has described embodiments of the present disclosure with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution between different functional units, processing logic elements, or processing domains may be used without departing from the present disclosure. For example, functionality described as being performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are only references to suitable devices for providing the described functionality, rather than indications of a strict logical or physical structure or organization.

[0186] Various modifications to the embodiments described in the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the claims. Therefore, the present disclosure is not intended to be limited to the embodiments shown herein, but should be given the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method used in a first network function (NF), the method comprising: A NF update message is sent to a network repositories function (NRF), wherein the NF update message includes planned removal information indicating that the first NF is planned to be removed.

2. The wireless communication method according to claim 1, wherein: The planned removal information includes at least one of the following: Plan to remove instructions, or Indication of scheduled removal time.

3. The wireless communication method according to claim 2, wherein: The planned removal indication includes an indication in a status value of the NF planned to be removed or an indication in a NF configuration file.

4. The wireless communication method according to claim 2 or 3, wherein: The planned removal time indication indicates the time when the first NF is planned to be removed.

5. The wireless communication method according to any one of claims 1 to 4, wherein: The NF update message also includes a replacement NF candidate list configured to take over at least one user served by the first NF.

6. A wireless communication method for use in a network warehousing function (NRF), the method comprising: receiving a NF update message from a first network function (NF), the NF update message including planned removal information indicating that the first NF is planned to be removed, and A notification message is sent to at least one second NF, where the notification message includes the planned removal information.

7. The wireless communication method according to claim 6, further comprising: The planned removal information is recorded in a NF configuration file of the first NF.

8. The wireless communication method according to claim 6 or 7, wherein: The planned removal information includes at least one of the following: Plan to remove instructions, or Indication of scheduled removal time.

9. The wireless communication method according to claim 8, wherein: The planned removal indication includes an indication in a state value of the NF planned to be removed or a network function configuration file.

10. The wireless communication method according to claim 8 or 9, wherein: The planned removal time indication indicates the time when the first NF is planned to be removed.

11. The wireless communication method according to any one of claims 6 to 10, wherein: The notification message also includes a list of replacement NF candidates configured to take over at least one user served by the first NF.

12. The wireless communication method according to claim 11, wherein: The replacement NF candidate list is determined by the NRF.

13. The wireless communication method according to any one of claims 6 to 11, wherein: The NF update message also includes a replacement NF candidate list configured to take over at least one user served by the first NF.

14. The wireless communication method according to any one of claims 6 to 13, wherein: The at least one second NF subscribes to the NF state change or NF profile change of the first NF from the NRF.

15. A wireless communication method for use in a second network function (NF), the method comprising: receiving a notification message from a network repositories function (NRF), the notification message including planned removal information indicating that the first NF is planned to be removed, and At least one replacement NF configured to take over at least one user served by the first NF is selected based on the planned removal information.

16. The wireless communication method according to claim 15, wherein: The planned removal information includes at least one of the following: Plan to remove instructions, or Indication of scheduled removal time.

17. The wireless communication method according to claim 16, wherein: The planned removal indication includes an indication in a state value of the NF planned to be removed or a network function configuration file.

18. The wireless communication method according to claim 16 or 17, wherein: The planned removal time indication indicates the time when the first NF is planned to be removed.

19. The wireless communication method according to any one of claims 15 to 18, wherein: The notification message also includes a list of replacement NF candidates configured to take over at least one user served by the first NF.

20. The wireless communication method according to any one of claims 15 to 19, wherein: Selecting the at least one replacement NF configured to take over at least one user served by the first NF based on the planned removal information comprises: selecting the at least one replacement NF from a list of replacement NF candidates provided by the NRF, or A NF discovery process is performed to select the at least one replacement NF.

21. The wireless communication method according to any one of claims 15 to 20, further comprising: The at least one user served by the first NF is transferred to the at least one substitute NF.

22. The wireless communication method according to claim 21, wherein: Transferring the at least one user served by the first NF to the at least one substitute NF comprises: No later than the removal time indicated by the planned removal information, the at least one user served by the first NF is transferred to the at least one replacement NF.

23. The wireless communication method according to any one of claims 15 to 22, wherein: The second NF subscribes to the NF state change or NF profile change of the first NF from the NRF.

24. A wireless device for a first network function (NF), the wireless device comprising: A communication unit, wherein the communication unit is configured to send a NF update message to a network repositories function (NRF), wherein the NF update message includes planned removal information indicating that the first NF is planned to be removed.

25. The wireless device of claim 24, further comprising: A processor, wherein the processor is configured to execute the wireless communication method according to any one of claims 2 to 5.

26. A wireless device for a network warehousing function (NRF), the wireless device comprising: A communication unit, wherein the communication unit is configured to: receiving a NF update message from a first network function (NF), the NF update message including planned removal information indicating that the first NF is planned to be removed, and A notification message is sent to at least one second NF, where the notification message includes the planned removal information.

27. The wireless device of claim 26, further comprising: A processor, wherein the processor is configured to execute the wireless communication method according to any one of claims 8 to 14.

28. A wireless device for a second network function (NF), the wireless device comprising: a communication unit configured to receive a notification message from a network repositories function (NRF), the notification message including planned removal information indicating that the first NF is planned to be removed, and A processor is configured to select at least one replacement NF configured to take over at least one user served by the first NF based on the planned removal information.

29. The wireless device of claim 28, wherein: The processor is further configured to perform the wireless communication method according to any one of claims 16 to 23.

30. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the wireless communication method according to any one of claims 1 to 23.

Images