A network node and a method for updating network functionality in a wireless communication network.

Abstract

Embodiments of this specification may relate, for example, to a method implemented by a first network node (13) for handling a test process related to a third network (15) node in a wireless communication network (1). The first network node acquires instance identification information of an updated or started third network node (15) and stores one or more identification information of one or more UEs to be used during the test process, mapped to the acquired instance identification information. When a session establishment of a UE (10) is detected, the first network node checks whether the identification information of the UE (10) matches one or more stored identification information of one or more UEs (10), and if the identification information of the UE (10) matches one of the one or more stored identification information of one or more UEs, the first network node (13) uses the instance identification information mapped to the matching identification information to initiate NF discovery toward the second network node (14).

Description

Technical Field

[0001] Embodiments of the present specification relate to a first network node, a second network node, a third network node in wireless communication, and methods implemented in those network nodes. Further, a computer program product and a computer-readable storage medium are also provided herein. In particular, embodiments of the present specification relate to handling communication, such as handling or enabling testing of a third network node that has been started or updated, in a wireless communication network.

Background Art

[0002] In a general wireless communication network, a user equipment (UE), also known as a wireless communication device, a mobile station, a station (STA) and / or a wireless device, communicates with one or more core networks (CNs) via a radio access network (RAN). The RAN covers a geographical area that is divided into service areas or cells, and each service area or cell is served by a wireless network node, such as a Wi-Fi access point or a radio base station (RBS), which may be called, in some networks, an access node, such as Node B, gNode B, or eNode B. A service area or cell is a geographical area where wireless coverage is provided by a wireless network node. The wireless network node operates on a radio frequency to communicate with the UE via an air interface within the range of the wireless network node. The wireless network node communicates with the UE via the downlink (DL), and the UE communicates with the wireless network node via the uplink (UL).

[0003] The Universal Mobile Telecommunications System (UMTS) is a third-generation (3G) communication network that evolved from the second-generation (2G) GSM (Global System for Mobile Communications). The UMTS Terrestrial Radio Access Network (UTRAN) is essentially a RAN that uses Wideband Code Division Multiple Access (WCDMA) and / or High-Speed ​​Packet Access (HSPA) for communication with user equipment. A forum known as the Third Generation Partnership Project (3GPP) allows communication suppliers to propose and agree on standards for current and future generations of networks, investigating, for example, extended data rates and radio capacity. In some RANs, such as UMTS, several radio network nodes may be connected to a controller node, such as a Radio Network Controller (RNC) or Base Station Controller (BSC), by landline or microwave, for example. The controller node monitors and coordinates the various activities of multiple radio network nodes connected to it. The RNC is typically connected to one or more core networks.

[0004] The specifications for the Evolved Packet System (EPS) have been finalized within 3GPP, and the next 3GPP releases, such as New Radio (NR), will address them. EPS comprises an Extended Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) Radio Access Network, and an Evolved Packet Core (EPC), also known as the System Architecture Evolution (SAE) Core Network. E-UTRAN / LTE is a 3GPP radio access technology in which radio network nodes are directly connected to the EPC core network. Therefore, the RAN of EPS has an essentially "flat" architecture, with radio network nodes directly connected to one or more core networks.

[0005] In newer 5G technologies such as NR, the use of a very large number of transmit and receive antenna elements can be important because it allows for the utilization of beamforming, such as transmit-side and receiver-side beamforming. Transmitter-side beamforming means that a transmitter can amplify the transmit signal in one or more selected directions and suppress the transmit signal in other directions. Similarly, on the receiver side, a receiver can amplify the signal from one or more selected directions and suppress unwanted signals from other directions.

[0006] Figure 1 shows the 5G reference architecture defined by 3GPP. The network functions (NFs) shown in Figure 1 are explained below.

[0007] An Application Function (AF) or Application Server (AS) interacts with the 3GPP core network, enabling external parties to use public application programming interfaces (APIs) provided by the network operator. The AF provides session relationship information to other nodes in the 5G core network (5GC).

[0008] The Network Exposure Function (NEF) supports different features, and NEF supports different exposure APIs.

[0009] The Network Repository Function (NRF) acts as the registration center for National Factories (NFs).

[0010] The Unified Data Repository (UDR) stores subscription-related information, i.e., data grouped into separate sets: subscription data, policy data, structured data for publication, and application data.

[0011] The Session Management Function (SMF) supports different functions; for example, the SMF receives policy and billing control (PCC) rules from the Policy Control Function (PCF) and configures the User Plane Function (UPF) accordingly.

[0012] The User Plane Function (UPF) supports handling of user plane traffic based on rules received from the SMF, such as packet inspection and different enforcement actions including quality of service (QoS) handling.

[0013] PCF supports an integrated policy framework to govern network behavior. Specifically, PCF provides PCC rules to the Policy and Billing Enforcement Function (PCEF), which enforces policy and billing decisions according to provisioned PCC rules for SMF / UPF.

[0014] The Access and Mobility Management Function (AMF) manages, for example, UE access and UE mobility modes when UEs are connected through different access networks.

[0015] The billing function (CHF) manages billing for services and / or features. The CHF includes the online billing function (OCF), as specified in TS32.296 v17.0.0, which provides quota management functionality under credit control terminology, and the billing data function (CDF), as specified in Section 4.3.1.2 32.240 v18.0.0, which provides billing data record (CDR) generation functionality for billing events.

[0016] The unshown Network Slice Selection Function (NSSF) selects a Network Slicing Instance (NSI), determines the enabled Network Slice Selection Assistance Information (NSSAI), and sets the AMF to serve the UE.

[0017] The overall SMF selection was part of the 3GPP specification from the beginning. See TS23.502 v.17.5.0.

[0018] The SMF selection function, described in section 6.3.2 of TS23.501 v.17.5.0, is supported by AMF and is used to assign an SMF that manages a Protocol Data Unit (PDU) session.

[0019] The SMF selection function described in this section does not apply to SMF selection for emergency services. SMF selection for emergency services is described in section 5.16.4.5 of TS23.501 v.17.5.0.

[0020] Two main branching points in the development scenarios to consider: - Non-roaming and roaming with local breakout. See section 4.3.2.2.3.2 in TS23.502 v.17.5.0. - Home-routed roaming. See section 4.3.2.2.3.3 in TS23.502 v.17.5.0.

[0021] For non-roaming and local breakout scenarios, there are two operational scenarios that depend on the AMF configuration and the NSSF deployment options in the Serving Public Land Mobile Network (PLMN).

[0022] For home-routed flights, there are two main options, depending on the operator's selection, regarding the involvement of the NRF and NSSF, and the establishment of the AMF. The decision of which option to use is part of the roaming agreement. Note: The use of NSI IDs and multiple NRFs in the network is optional and depends on the operator's deployment selection.

[0023] Non-roaming and roaming with local breakout.

[0024] Figure 2 shows SMF choices for non-roaming and roaming with local breakout scenarios.

[0025] This procedure may be completely skipped if SMF information is available in AMF by other means, for example, locally configured; otherwise, - When the Serving AMF is aware of the appropriate NRF to be used to select the NF / service within the corresponding NSI, based on the configuration or network slice selection information received during registration, only steps 3 and 4 in the following procedure are performed, as illustrated in Figure 2. - When the serving AMF is unaware of the appropriate NRF that should be used to select the NF / service within the corresponding NSI, all steps in the following procedure are performed, as illustrated in Figure 2. 1. The AMF invokes the Nnssf_NSSelection_Get service operation from the NSSF on the serving PLMN, using the serving(S)-NSSAI of the serving PLMN requested by the UE, the PLMN ID of the subscription persistent identifier (SUPI), the UE's tracking area identifier (TAI), and an instruction that the request is within the procedure for establishing a PDU session in either a non-roaming or roaming with local breakout scenario. 2. The NSSF in the Serving PLMN selects an NSI, determines and returns the appropriate NRF to be used to select NF / services within the selected NSI, and optionally returns the NSI ID corresponding to the NSI. 3. The AMF queries the appropriate NRF in the serving PLMN by issuing an Nnrf_NFDiscovery_Request which includes at least the S-NSSAI of the serving PLMN for this PDU session from the enabled NSSAI, the PLMN ID of the SUPI, the data network name (DNN), and, if the AMF remembers the NSI ID for the S-NSSAI of the serving PLMN for this PDU session from the enabled NSSAI, the NSI ID. Note: A list of parameters for SMF selection is defined in section 6.3.2 of TS23.501 v.17.5.0. For I-SMF selection, see section 5.34.3 of TS23.501 17.5.0. 4. The NRF in the serving PLMN provides the AMF, for example, in the Nnrf_NFDiscovery_Request response message, with the fully qualified domain name (FQDN) or IP address of the discovered (one or more) SMF instance or set of (one or more) endpoint addresses of the (one or more) SMF service instances, and, optionally, the NSI ID for the selected NSI corresponding to the S-NSSAI for subsequent NRF queries.

[0026] The input parameters to Nnrf_NFDiscovery_Request that are used to determine the correct SMF instance are described in detail in 3GPP TS29.510 v.17.6.0 (note that this is not a complete list and is only the parameters that can be or are used for SMF selection in a non-private network without roaming). TIFF2026512942000002.tif255169TIFF2026512942000003.tif255168TIFF2026512942000004.tif255168TIFF2026512942000005.tif255168TIFF2026512942000006.tif32170

[0027] However, there are also aspects of the NF status of the actual SMF instance that should be taken into account when the NRF "selects" one or more SMF candidates.

[0028] 6.1.6.3.7 Enumeration: NFStatus TIFF2026512942000007.tif82170

Summary of the Invention

[0029] As part of developing embodiments of this specification, one or more problems have been identified. There are several use case scenarios addressed herein for updating or starting up NFs in wireless communication networks. These include when an NF is upgraded with new software (SW), or when an NF is started up, i.e., powered on for the first time, restarted, or connected to a wireless communication network. These use cases may be one or more of the following: • Customers want to try out the new software delivery for NF using their actual UE. • At the same time, the customer does not want other UEs to ultimately reach this NF until the new SW passes all verifications. If the test passes, a smooth re-implementation of network functionality may be possible. • In-Service Software Upgrade (ISSU) also requires other UEs to attempt an upgrade without using an upgraded NF such as SMF.

[0030] Conventional solutions: • The first part, assigning a specific UE to a specific NF, can today be achieved by adding a new DNN in the NF and / or by Unified Data Management (UDM) / UDR. The latter part, preventing all other UEs from attempting to establish PDU sessions toward a particular NF, is much more difficult but achievable. However, assuming the current 3GPP specification, there is no easy way to achieve this without affecting many configurations. As an example, one could remove all slice and DNN relation settings and configure an upgraded NF to support only a single (S)-NSSAI(slice)+DNN, and / or remove all geographically related settings, e.g., smfInfoList, and support connectivity only for a single TAI.

[0031] 3GPP TS29.510 v.17.6.0 provides an example where NF is SMF. TIFF2026512942000008.tif92170

[0032] In that case, the problem is that once the verification is successful, all removed settings must be restored. This reset has one or more of the following drawbacks: • There is a higher risk of misconfiguration. • For operators, or other operational departments that handle upgrades, such as those managing services, there will be increased costs. • It takes more time to coordinate and align new software, i.e., a longer time to market (TTM).

[0033] The objective of this specification is to provide a mechanism for efficiently handling the implementation or updating of NFs, such as SMF, PCF, or CHF, in wireless communication networks.

[0034] In one embodiment, the objective is achieved by providing a method, implemented by a first network node, such as an NF node, for handling a test process related to a third network node in a wireless communication network, according to embodiments of this specification. The first network node acquires instance identification information of an updated or started third network node and stores one or more identification information of one or more UEs to be used during the test process, mapped to the acquired instance identification information. When a session establishment of a UE is detected, the first network node checks whether the UE's identification information matches one or more stored identification information of one or more UEs, and if the UE's identification information matches one of the one or more stored identification information of one or more UEs, the first network node uses the instance identification information mapped to the matching identification information to initiate NF discovery toward the second network node.

[0035] In another embodiment, the objective is achieved by providing a method, implemented by a second network node, such as an NF node, for handling a test process related to a third network node in a wireless communication network, according to embodiments of this specification. The second network node obtains instance identification information of an updated or started third network node and uses the instance identification information to receive a request from the first network node relating to NF discovery. The second network node generates a response based on the instance identification information, a status indication of the third network node, a condition indication, an indication received from the first network node, and / or previously stored status information, the response indicating a profile of the updated or started third network node. The second network node then transmits the generated response to the first network node.

[0036] In another embodiment, the objective is achieved by providing a method, performed by a third network node, such as an NF node, e.g., SMF, PCF, or CHF, for handling a test process related to a third network node in a wireless communication network, according to embodiments of this specification. The third network node provides the second network node with a status indication of the third network node, along with profile information of the third network node, the indication indicating a status related to testing, maintenance, or updating the third network node.

[0037] In yet another embodiment, the objective is achieved by providing a first network node, a second network node, and a third network node, each configured to carry out the method herein, according to embodiments herein.

[0038] Accordingly, in one embodiment, the objective is achieved by providing a first network node, such as an NF node, e.g., an AMF, for handling a test process related to a third network node in a wireless communication network, according to embodiments of this specification. The first network node is configured to acquire instance identification information of an updated or started third network node and to store one or more identification information of one or more UEs to be used during the test process, mapped to the acquired instance identification information. The first network node is configured to check whether the UE's identification information matches one or more stored identification information of one or more UEs when a session establishment of a UE is detected, and if the UE's identification information matches one or more of the stored identification information of one or more UEs, the first network node is configured to initiate NF discovery toward the second network node using the instance identification information mapped to the matching identification information.

[0039] In another embodiment, the objective is achieved by providing a second network node, such as an NF node, e.g., an NRF, for handling a test process related to a third network node in a wireless communication network, according to embodiments of this specification. The second network node is configured to acquire instance identification information of an updated or started third network node and to use the instance identification information to receive requests from the first network node relating to NF discovery. The second network node is configured to generate a response based on the instance identification information, status indications of the third network node, condition indications, indications received from the first network node, and / or previously stored status information, the response indicating a profile of the updated or started third network node. The second network node is configured to transmit the generated response to the first network node.

[0040] In another embodiment, the objective is achieved by providing a third network node, such as an NF node, e.g., an SMF, PCF, or CHF, for handling test processes related to the third network node in a wireless communication network, according to embodiments of this specification. The third network node is configured to provide the second network node with status indications of the third network node, along with profile information of the third network node, the indications of status related to testing, maintenance, or updating the third network node.

[0041] Furthermore, the following computer program product is provided herein, which, when executed on at least one processor, comprises instructions causing at least one processor to perform the method described herein, as performed by a first network node, a second network node, or a third network node, respectively. Furthermore, the following computer-readable storage medium is provided herein, which stores the computer program product, which, when executed on at least one processor, comprises instructions causing at least one processor to perform the method described herein, as performed by a first network node, a second network node, or a third network node, respectively.

[0042] Embodiments of this specification provide a mechanism that allows a first network node, such as an AMF, to select a specific, predetermined third network node, i.e., an NF, such as an SMF, that is in maintenance mode, enabling it to perform drive tests on that third network node and, at the same time, ensure that commercial / live traffic is not directed to that third network node.

[0043] By further including conditional instructions, an NF, such as a third network node, may indicate whether it can be discovered and selected by other NFs under one or more conditions, which makes it possible to enable the gradual redeployment of a target (newly upgraded) NF, controlled by that NF itself.

[0044] Therefore, embodiments of this specification provide a mechanism that makes it possible to direct only a specific UE to a specific NF, - Provide at a low OPEX cost for the operator. - Offered with a low risk of misconfiguration. - Provide with minimal collaborative effort.

[0045] Therefore, this can result in faster TTM for new software, which means that older versions will have less time to market and thus lower maintenance costs. Accordingly, embodiments herein provide a mechanism for handling the implementation or updating of network functions, such as SMF, PCF, or CHF, in an efficient manner in a wireless communication network.

[0046] Next, embodiments will be described in more detail with reference to the enclosed drawings. [Brief explanation of the drawing]

[0047] [Figure 1] This diagram shows the architecture using conventional technology. [Figure 2] This diagram shows a conventional signaling method. [Figure 3a] This figure shows a wireless communication network according to an embodiment of this specification. [Figure 3b] A combined signaling scheme and flowchart according to embodiments of this specification. [Figure 4] This figure shows a signaling scheme according to an embodiment of this specification. [Figure 5] This figure shows a signaling scheme according to an embodiment of this specification. [Figure 6a] This figure shows a signaling scheme according to an embodiment of this specification. [Figure 6b] This figure shows a signaling scheme according to an embodiment of this specification. [Figure 6c] This figure shows a signaling scheme according to an embodiment of this specification. [Figure 7] This figure shows a method implemented by a first network node according to an embodiment of this specification. [Figure 8] This figure shows a method implemented by a second network node according to an embodiment of this specification. [Figure 9]This figure shows a method implemented by a third network node according to an embodiment of this specification. [Figure 10] This figure shows upgrade example 1(2) regarding upgrading SMF. [Figure 11] This figure shows upgrade example 2(2) regarding upgrading SMF. [Figure 12] This is a block diagram of a first network node according to an embodiment of this specification. [Figure 13] This is a block diagram showing a second network node according to an embodiment of this specification. [Figure 14] This is a block diagram showing a third network node according to an embodiment of this specification. [Modes for carrying out the invention]

[0048] The embodiments described herein generally relate to wireless communication networks. Figure 3a is an overview of wireless communication network 1. Wireless communication network 1 comprises one or more RANs and one or more CNs. Wireless communication network 1 may use one or more different technologies. While the embodiments described herein relate to recent technological trends of particular interest in the NR context, the embodiments are also applicable to existing wireless communication systems and their developments, such as LTE or WCDMA.

[0049] In the wireless communication network 1, there are wireless devices UEs 10, as exemplified herein, such as mobile stations, non-access point (non-AP) stations (STAs), STAs, and / or wireless terminals, which communicate with one or more access networks (ANs), such as one or more CNs via a RAN. It should be understood by those skilled in the art that "UE" is a non-limiting term meaning any terminal, wireless communication terminal, user equipment, narrowband Internet of Things (NB-IoT) device, machine-type communication (MTC) device, D2D (device-to-device) terminal, or node, such as a smartphone, laptop computer, mobile phone, sensor, relay, mobile tablet, or even a small base station, that is capable of communicating with a wireless network node using wireless communication within an area served by a wireless network node.

[0050] The wireless communication network 1 comprises wireless network nodes 12 that provide wireless coverage over a geographical area, a first service area 11, or a first cell of a first radio access technology (RAT), such as NR, LTE, or similar. The wireless network nodes 12 may be transmit and receive points, such as access nodes, access controllers, base stations, wireless base stations such as g-node B (gNB), evolved node B (eNB, e-node B), node B, base station transceiver stations, wireless remote units, access point base stations, base station routers, wireless local area network (WLAN) access points or access point stations (AP STA), wireless base station transmission arrangements, standalone access points, or any other network units or nodes capable of communicating with wireless devices in the area served by the wireless network nodes, depending on the first radio access technology and terminology used. The wireless network nodes may be called serving wireless network nodes, the service area may be called serving cells, and the serving network nodes communicate with UEs in the form of DL transmissions to UEs and UL transmissions from UEs. Please note that service areas may be expressed as cells, beams, beam groups, or similar to define the area of ​​radio coverage.

[0051] The wireless communication network further comprises several CN / NF nodes, such as a first network node 13, a second network node 14 such as AMF, NRF, etc., and a third network node 15 such as SMF, CHF, or PCF. Network nodes are exemplified herein according to NR terminology, but it should be noted that embodiments may be implemented in systems of other RATs, such as LTE or similar.

[0052] According to embodiments of this specification, the first network node 13 selects a third network node 15 for a particular UE, which is in maintenance or test mode, enabling it to perform drive tests and, at the same time, ensure that commercial and / or live traffic is not directed to the third network node 15.

[0053] Embodiments of this specification may include the following: A configuration in the first network node 13 that allows one (or several) specific UE10s, identified by UE identification information such as SUPI, to tag and / or link to a given NF, such as an SMF, identified by instance identification information (NfInstanceId), when the UE10 attempts to establish a PDU session. This is made possible by storing the UE identification information for testing and mapping the instance identification information to maintenance / test scenarios. TIFF2026512942000009.tif26170

[0054] Furthermore, in 3GPP 29.571 v.17.0.0: TIFF2026512942000010.tif27170

[0055] RFC4122: This specification defines a uniform resource name namespace for Universally Unique Identifiers (UUIDs), also known as Globally Unique Identifiers (GUIDs). UUIDs are 128 bits long and can guarantee uniqueness across space and time. UUIDs were originally used in the Apollo Network Computing Systems, later in the Open Software Foundation's (OSF) Distributed Computing Environment (DCE), and subsequently in the Microsoft Windows platform.

[0056] Therefore, an "instance" can be exactly the same as a "physical node."

[0057] In this example, the first network node 13 checks the above settings and selects the configured NfInstanceId for that particular SUPI.

[0058] Three options are suggested herein when the first network node 13 is an AMF and the third network node 15 is an SMF. - The AMF sends the NF discovery to the NRF, i.e., the second network node 14, which includes the S-NSSAI, DNN, a new value or attribute value pair (AVP), for example, "maintenance mode," and a target-nf-instance-id set to the same value defined in the target SMF. NfInstanceId is a required parameter in the NF registration procedure and is set manually on each SMF. The new AVP "maintenance mode" is generally a Boolean. The NRF checks the incoming qualifying parameters, and if the NF status is undiscoverable and the maintenance mode AVP is true, an SMF with an NfInstanceId is returned to the AMF, and the procedure continues toward that SMF. - The SMF sends an NF update with a new value for the NF status, called maintenance or test. The AMF sends an NF discovery to the NRF, which includes the S-NSSAI, the DNN, and the target-nf-instance-id, which is set to the same value specified in the target SMF. NfInstanceId is a required parameter in the NF registration procedure and is set manually on each SMF. The NRF checks the incoming qualifying parameters, and if the NF status is Maintenance or Test and the AVP target-nf-instance-id contains a single value, the SMF with the NfInstanceId is returned to the AMF, and the procedure continues toward that SMF. - SMF sends an NF update with a new value for the NF status, called Maintenance or Test. AMF sends an NF discovery to NRF, including S-NSSAI and DNN. NRF checks the incoming parameters and returns the SMF to AMF if the NF status == Registered, Test or Maintenance, and the other query parameters (S-NSSAI and DNN) also match. In a canary test case, the AMF selects an SMF instance whose NF status is Test or Maintenance, and the procedure proceeds to that SMF. Canary testing refers to testing a new software version or new feature in a live environment using an actual UE.

[0059] Next, further extensions to NFProfile may be required for re-implementation. TIFF2026512942000011.tif22170

[0060] Embodiments of this specification may include one or more of the following: - Introduce a new NFStatus value ("Test"). - Introduce one or more conditions (or sets of conditions), for example, a set of UEs, to indicate whether the NF under test state should be selected first when those conditions are met, but not when those conditions are not met.

[0061] Figure 3b shows a combined flowchart and signaling scheme according to the embodiments of this specification.

[0062] Action 301. The third network node 15 is updated, i.e., upgraded with new SW, or started, i.e., powered on for the first time, restarted, or connected to the wireless communication network. For example, the third network node 15 performs an upgrade procedure and verifies that the configuration to support the test UE exists on the third network node 15. The third network node 15 may set its status to "undiscoverable" via a command on the third network node 15.

[0063] Action 302. The first network node 13 obtains instance identification information for the upgraded or started third network node 15. For example, once the instance identification information is set by the third network node 15, the third network node 15 is registered, and the first network node 13 selects it, the first network node 13 may subscribe to changes to that instance identification information, such as status changes.

[0064] Action 303. The first network node 13 stores the identification information of the UE 10 to be tested, which is mapped to the instance identification information. Previously, the first network node 13 may have obtained the identification information of one or more UEs, and it may be locally configured in the first network node 13 which UE should be used to test the NF in maintenance mode.

[0065] Action 304. UE10 initiates session establishment.

[0066] Action 305. The first network node 13 checks the identification information of UE 10 to see if it matches the stored UE identification information.

[0067] Action 306. If the identification information of UE10 matches the stored identification information, the first network node 13 initiates NF discovery toward the second network node using the instance identification information mapped to the stored identification information. The first network node 13 may also transmit a flag indicating "maintenance mode," such as a flag set to true. Thus, when the identification information of UE10 matches the stored identification information, the first network node 13 may include a value indicating the status of maintenance, test, or update.

[0068] Action 307. The second network node 14 generates a response based on the instance identification information, flags, conditions met, and / or previously stored status information. For example, if a flag is included and set to true, the second network node 14 may return an NF profile corresponding to the instance identification information to the first network node 13, even if the NF status is equal to "undiscoverable". In another example, if the instance identification information is set to a status as test or maintenance at the second network node 14, the second network node 14 may provide the first network node 13 with an NF profile corresponding to the instance identification information. Alternatively, the second network node 14 may check one or more parameters in the NF discovery request for a match, and if a match is found, then provide the first network node 13 with instructions for one or more NF profiles whose status is equal to "registered", "test", or "maintenance". The status of each NF profile may be indicated in the message carrying the instructions for one or more NF profiles.

[0069] Action 308. The second network node sends a response to the first network node 13.

[0070] Action 309. If the response includes status indications for multiple profiles, the first network node 13 may select one NF profile with a status indicating maintenance, test, or update for the configuration on the first network node 13, indicating which one or more UEs are testing the NF in test or maintenance mode. The first network node 13 may select one NF profile based on instance identification information mapped to the UE, i.e., according to the local configuration.

[0071] Action 310. The UE10 may then run one or more tests using the updated or started third network node 15. Note that the UE10 itself may not know that it is a test scenario, and only the operator who set up the logical link and / or connection between the UE10 and the third network node 15, as set up in Action 303 at the first network node 13, would know this.

[0072] Action 311. If one or more tests are successful, for example, if a test passes a preset threshold or similar, the third network node 15 may change its status to registered and send an instruction to the second network node 14 designating the third network node 15 as a registered third network node. That is, the test results as successful are managed in the test object list and can be managed and executed, for example, by an operator.

[0073] Action 312. The second network node 14 may then store in the second network node 14 an instruction that the third network node 15 is a new status, such as a registered third network node.

[0074] Required changes for 3GPP TS29.510 v17.6.0 (underlined) 6.1.6.3.6 Enumeration: NotificationEventType TIFF2026512942000012.tif47170

[0075] 6.1.9 Features supported by the NFManagement service The syntax for the supportedFeatures attribute is specified in section 5.2.2 of 3GPP TS29.571 [7]. The following characteristics are defined for the Nnrf_NFManagement service. TIFF2026512942000013.tif113170

[0076] Figure 4 shows the SMF selection, alternative form 1, for the canary test. Referring to Figure 3, the first network node 13 is exemplified as an AMF, the second network node 14 is exemplified as an NRF, and the third network node 15 is exemplified as an SMF. 41. Legacy: Standard upgrade procedures as described in the CPI 42. Legacy: Verify that s-nssai+DNN configuration exists in SMF to support test UEs. 43. Legacy: Set the NF status to "Undiscoverable" via a command in SMF. 44. New: Retrieve the NfInstanceId for the upgraded SMF. For example, an operator may retrieve the NfInstanceId and then use that NfInstanceId in the next step for local configuration. 45. New: AMF establishes a link between test UE identification information such as SUPI and the upgraded SMF (NfInstanceId). The value NfInstanceId, which was extracted from the SMF in step 44, will be used for these tests. 46. ​​New: When UE10 initiates the PDU session establishment procedure, AMF shall check against local settings. If SUPI is found in the list, AMF shall use a specific NF discovery query to NRF that includes the "target-nf-instance-id" information, the same value as the set NfInstancId value, and a new flag called "Maintenance Mode" (Boolean), which is set to true. 47. New: If the New flag is included and set to true, the NRF shall return the SMF NF profile (as directed to the AMF by "target-nf-instance-id"), even if the NF status is equal to "undiscoverable". 48. Legacy: Run all tests 49. New: Once all tests are passed, set the NF status to "Registered" via a command in SMF. This can then be provided to NRF.

[0077] Required changes to 3GPP 29.510 v.17.6.0 for Alternative Form 1 (add the underlined ones) TIFF2026512942000014.tif52170TIFF2026512942000015.tif92170

[0078] Figure 5 shows SMF selection, alternative form 2 for the canary test. Referring to Figure 3, the first network node 13 is exemplified as an AMF, the second network node 14 is exemplified as an NRF, and the third network node 15 is exemplified as an SMF. 51. Legacy: The standard upgrade procedure described in the legacy procedure. 52. Legacy: Verify that s-nssai+DNN configuration exists in SMF to support test UEs. 53. New: Set the NF status to "Test" via a command in SMF. 54. New: Retrieve the NfInstanceId for the upgraded SMF. 55. New: In AMF, set up a link between the test UE identification information and the upgraded SMF (NfInstanceId). The value NfInstanceId, which was extracted from the SMF in step 54, will be used for these tests. 56. New: When UE10 initiates the PDU session establishment procedure, AMF shall check against local settings. For example, if SUPI is found in the list, AMF shall use a specific NF discovery query directed to NRF that includes the "target-nf-instance-id" information and the same value as the configured NfInstancId value. 57. New: If the NF status of "target-nf-instance-id" is set to "Maintenance" in the NRF, the NRF will provide its SMF NF profile to the AMF. 58. Legacy: Run all tests 59. New: Once all tests are passed, set the NF status to "Registered" via a command in SMF. This can then be provided to NRF.

[0079] Required changes to 3GPP 29.510 v.17.6.0 for Alternative Form 2 (add the underlined ones) TIFF2026512942000016.tif128170

[0080] Figure 6a shows SMF selection, alternative form 3 for the canary test. Referring to Figure 3, the first network node 13 is exemplified as an AMF, the second network node 14 is exemplified as an NRF, and the third network node 15 is exemplified as an SMF. 61. Legacy: Standard upgrade procedures as described in the CPI 62. Legacy: Verify that s-nssai+DNN configuration exists in SMF to support test UEs. 63. New: Set the NF status to "Test" via a command in SMF. 64. New: Retrieve the NfInstanceId for the upgraded SMF. 65. New: AMF establishes a link between the Test UE Identifier (SUPI) and the upgraded SMF (NfInstanceId). The value NfInstanceId, which was extracted from the SMF in step 464, will be used for these tests. 66. Legacy: When UE10 initiates the PDU session establishment procedure, AMF shall operate according to legacy handling and send a “normal” NF discovery. 67. New: NRF will check all query parameters, examine their matches, and provide AMF with a list of all SMF NF profiles, including the NF status, where the NF status is equal to "Registered," "Test," or "Maintenance." 68. New: When AMF receives a response from NRF, it will check the local configuration and if SUPI=xyz, which means the user is for canary testing, AMF should select an SMF instance with status=Maintenance. 69. Legacy: Run all tests. 70. New: Once all tests are passed, set the NF status to "Registered" via a command in SMF. This can then be provided to NRF.

[0081] Required changes to 3GPP 29.510 v.17.6.0 for Alternative Form 3 (add the underlined ones) TIFF2026512942000017.tif128170

[0082] Figure 6b shows the SMF selection, alternative form 4, for the canary test. Referring to Figure 3, the first network node 13 is exemplified as an AMF, the second network node 14 is exemplified as an NRF, and the third network node 15 is exemplified as an SMF. 71. Legacy: Standard upgrade procedures as described in the CPI 72. Legacy: Verify that s-nssai+DNN configuration exists in SMF to support test UEs. 73. New: Set the NF status to "Test" and the NF selection condition to "Subscriber" via a command in SMF. The condition instruction specifies one or more conditions under which an NF instance with an NFStatus value set to "Test" may be selected by an NF service consumer. 74. New: AMF establishes a link between Test UE Identifier (SUPI) and NFProfiles, which hold NF Status=Test and NF Selection Criteria=Subscriber. 75. New: When UE10 initiates the PDU session establishment procedure, AMF shall comply with 3GPP. 76. When NRF returns suitable NFProfiles (for all SMFs, including those with NF status = test), AMF shall look at the local configuration and select the SMFs that will undergo canary testing. 77. Legacy: Run all tests. 78. New: Once all tests are passed, set the NF status to "Registered" via a command in SMF.

[0083] Figure 6c shows the SMF selection, alternative form 5, for the canary test. Referring to Figure 3, the first network node 13 is exemplified as an AMF, the second network node 14 is exemplified as an NRF, and the third network node 15 is exemplified as an SMF. 81. Legacy: Standard upgrade procedures as described in the CPI 82. Legacy: Verify that s-nssai+DNN configuration exists in SMF to support test UEs. 83. New: Set the NF status to "Test" and the NF selection condition to "TAIRange" via a command in SMF. The condition instruction specifies one or more conditions, a range of tracking area identifiers, under which an NF instance with an NFStatus value set to "Test" may be selected by an NF service consumer. 84. New: AMF establishes a link between Test UE Identifier (SUPI) and NFProfiles, which hold NF Status=Test and NF Selection Criteria=Subscriber. 85. New: When UE10 initiates the PDU session establishment procedure, AMF shall comply with 3GPP. 86. When NRF returns suitable NFProfiles (for all SMFs, including those with NF status = test), AMF shall look at the local configuration and select the SMFs that will undergo canary testing. 87. Legacy: Run all tests 88. New: Once all tests are passed, set the NF status to "Registered" via a command in SMF.

[0084] Required changes to 3GPP 29.510 v.17.6.0 for alternative forms 4 and 5 (add the underlined ones)

[0085] 6.1.6.2.x Type: NFSelectionConditions TIFF2026512942000018.tif93170

[0086] Next, according to the embodiment, method actions performed by the first network node 13, such as an AMF, for handling a test process related to the third network node 15 in the wireless communication network 1, for example, testing the updated or started third network node 15, will be described with reference to the flowchart shown in Figure 7. The actions do not have to be taken in the order described below and may be taken in any preferred order. Dashed boxes indicate optional features.

[0087] Action 701. The first network node 13 retrieves the instance identifier of the updated or started third network node 15. This can be manually retrieved from the third network node 15 and set in the first network node 13 to create a link between the UE identifier and the instance identifier. For example, once the instance identifier is set by the third network node 15, the third network node 15 is registered, and the first network node 13 selects it, the first network node 13 can subscribe to changes to that instance identifier, such as a status change. Thus, the first network node 13 can receive instance identifiers from the second network node 14 or the third network node 15.

[0088] Action 702. The first network node 13 may obtain UE identification information for one or more UEs that are to be used during testing, i.e., UEs related to updates or startups. The first network node 13 may obtain identification information for one or more UEs that are to be locally configured at the first network node 13 and indicate which one or more UEs are testing the NF in maintenance mode. Thus, the first network node 13 may obtain identification information for one or more UEs that are to be used during the test process, mapped to the obtained instance identification information during local configuration.

[0089] Action 703. The first network node 13 stores one or more (obtained) UE identifiers of one or more UEs to be used during the test process, which are mapped to instance identifiers.

[0090] Action 704. Upon detecting the establishment of a session for UE10, the first network node 13 checks whether the identification information of UE10 matches one or more stored identification information for UE10.

[0091] Action 705. If the identification information of UE10 matches one or more stored identification information of one or more UEs, the first network node 13 initiates NF discovery toward the second network node 14 using the retrieved instance identification information mapped to the matched identification information. The first network node 13 may further send instructions to the second network node 14, such as a request, indicating a requested status related to the test, maintenance, or update mode of the third network node 15, such as test mode, maintenance, or updated status. The instructions may include a flag value set to true. Thus, when the identification information of a UE matches a stored identification information in the first network node 13, the first network node 13 may include a value indicating a maintenance, test, or update status in the NF discovery message. The first network node 13 may evaluate or determine whether the UE identification information matches the stored UE identification information. If there is a match, the first network node 13 activates the NRF discovery network function for the third network node 15, which is in maintenance mode. If there is no match, the first network node 13 activates a legacy implementation, such as SMF, to discover the third network node 15.

[0092] Action 706. The first network node 13 may receive a response from the second network node 14 indicating a profile of the updated or started third network node 15. For example, the first network node 13 may receive an NF profile associated with instance identification information even if the status of the third network node 15 is equal to “Undiscoverable”. In another example, the first network node 13 may receive an NF profile associated with instance identification information, where the instance identification information is associated with a status as maintenance, test, or update at the second network node 14. Alternatively, the first network node 13 may receive instructions for one or more NF profiles whose status is equal to “Registered”, “Test”, or “Maintenance” at the second network node 14. The status of each NF profile may be indicated in the message carrying the instructions for one or more NF profiles. The instructions may be the value or index of the NF profile. Therefore, the first network node 13 can receive one or more instructions for one or more profiles of one or more third network nodes 15, and the status of each profile is indicated in the response carrying one or more instructions.

[0093] Action 707. The first network node 13 may select one profile with a status indicating test, maintain, or update. For example, if the response includes a status indication, the first network node 13 may select one or more profiles, such as an SMF NF profile with a status indicating test, maintain, or update, for the configuration on the first network node 13, indicating which one or more UEs are testing the NF in maintenance mode.

[0094] Action 708. The first network node 13 may then handle signaling in the test process based on the response. The first network node 13 may, for example, direct the UE session of the UE using a profile indicated or selected in the response.

[0095] Next, according to the embodiment, method actions performed by a second network node 14, such as an NRF, for handling a test process related to a third network node 15 in the wireless communication network 1, for example, testing an updated or started third network node 15, will be described with reference to the flowchart shown in Figure 8. The actions do not have to be taken in the order described below and may be taken in any preferred order. Dashed boxes indicate optional features.

[0096] Action 801. The second network node 14 may obtain a status indication of the third network node 15. The second network node 14 may obtain, for example, a status indication from the third network node 15 indicating that the third network node 15 is undiscoverable or in a status related to testing, maintenance, or updating, such as test mode or maintenance mode. The second network node 14 may, in addition or alternatively, obtain a condition indication. A status indication may include a value, index, or flag. The second network node 14 may also receive a condition indication indicating conditions for NF selection. A condition indication may indicate one or more conditions under which an NF instance with an NFStatus value set to "Test" may be selected by an NF service consumer.

[0097] Action 802. The second network node 14 obtains the instance identification information of the updated or started third network node 15. For example, the second network node 14 may receive instance identification information from the third network node 15. The third network node 15 may set the instance identification information during the NF registration procedure. The instance identification information may be used as input for local configuration at the first network node 13.

[0098] Action 803. The second network node 14 receives requests related to NF discovery from the first network node 13 using instance identification information. The second network node 14 receives instructions, such as flags or values, requesting the status of the third network node 15 regarding testing, maintenance, or updating, such as "maintenance mode" or "test mode," and may receive, for example, a flag value set to true.

[0099] Action 804. The second network node 14 generates a response based on instance identification information, status indications for the third network node 15, conditional indications, instructions received from the first network node 13, and / or previously stored status information, the response indicating the updated or started profile of the third network node 15. For example, the second network node 14 may apply one or more indications for one or more profiles of one or more third network nodes 15 to the response, the status of each profile being indicated in the response carrying one or more instructions.

[0100] Action 805. The second network node 14 sends or transmits the generated response to the first network node 13. For example, if a flag is included and set to true, the second network node 14 may return an NF profile corresponding to the instance identifier to the first network node 13, even if the NF status is equal to "undiscoverable". In another example, if the instance identifier is set to a status as maintenance or test at the second network node 14, the second network node 14 may provide the first network node 13 with an NF profile corresponding to the instance identifier. Alternatively, the second network node may check one or more parameters in the NF discovery request for a match, and if a match is found, then provide the first network node 13 with instructions for one or more NF profiles whose status is equal to "registered", "test", or "maintenance". The status of each NF profile may be indicated in the message carrying the instructions for one or more NF profiles. The instructions may be the value or index of the NF profile.

[0101] Next, according to the embodiment, a method action performed by the third network node 15, such as an SMF, PCF, or CHF, for handling a test process related to the third network node 15 in the wireless communication network 1, for example, testing the updated or started third network node 15, will be described with reference to the flowchart shown in Figure 9. The actions do not have to be taken in the order described below and may be taken in any preferred order. Dashed boxes indicate optional features.

[0102] Action 901. The third network node 15 may perform an upgrade or startup.

[0103] Action 902. The third network node 15 may verify that the configuration to support the test exists on the third network node 15.

[0104] Action 903. The third network node 15 provides the second network node 14 with a status indication of the third network node 15, along with the third network node 15's profile information. This indication may be called a status indication and may describe a status related to testing, maintenance, or updating the third network node 15. The third network node 15 may send a status indication to the second network node 14 indicating that the third network node is undiscoverable or in a test-related status, such as test mode or maintenance mode. The status indication may be a status value or index. The third network node 15 may also provide or send a condition indication to the second network node 14. A condition indication may describe a selection condition for UEs based on a set of UEs or a set of tracking areas. Conditional directives may specify a set of subscription persistent identifiers (SUPIs) that an NF instance under test status should be selected, a set of publicly accessible subscription identifiers (GPSIs) that an NF instance under test status should be selected, a set of persistent device identifiers (PEIs) for a UE that an NF instance under test status should be selected, or a set of TAIs that an NF instance under test status should be selected for a given UE. Conditional directives may specify conditions for NF selection. Conditional directives may be subscriber or TAIrange values ​​or indices.

[0105] Action 904. The third network node 15 may then handle the test process of UE10. For example, the third network node 15 may handle the tests, such as handling the PCCs related to the test process.

[0106] Action 905. If the test process is successful, the third network node 15 may send an instruction to the second network node 14 indicating the status of the third network node 15 as a registered third network node 15. For example, if one or more tests are successful, for example, if the tests pass a preset threshold or similar, the third network node 15 may send an instruction to the second network node 14 indicating that the third network node 15 has a new status, such as being a registered third network node. That instruction may be a status value or index. If the tests fail, the third network node 15 may not change its status to registered.

[0107] Figure 10 shows upgrade example 1(2) for upgrading a second network node such as an SMF.

[0108] Create a PCC backup and export it. If the upgrade fails, the operator can reinstall the PCC for source release. Kubernetes configuration and certificate files must be saved and exported from the source PCC for reinstallation. - Save Kubernetes files from source PCC Non-default settings, such as values, configMaps content, and secrets, must be saved and reapplied on the target PCC. Ericsson recommends retaining the YAML files used during source PCC deployment for later reuse. - Save the source PCC settings To save the source PCC settings: Collect PCC settings - Save the PC-SM certificate file

[0109] Prepare for the upgrade. The following preparations may be required before upgrading your PCC: Prepare the custom values ​​set during installation for PCC preparation.

[0110] 4.3 Redirect UE traffic away from the source PCC. To avoid traffic disruption, traffic must be redirected away from the source PCC's Serving Gateway (SGW) Control Plane Function (C) and the combined SMF and PGW-C. 4.3.1 Redirect UE traffic away from SGW-C To redirect UE traffic away from SGW-C: Step Log in to your provider Block the creation of new user sessions. End the idle session. Monitor the end of idle sessions. End non-idle session 4.3.2 Redirect UE traffic away from combined SMF and PGW-C To redirect UE traffic away from the combined SMF and PGW-C: Step - Log in to your provider - Make SMF services undiscoverable in NRF - Block the creation of new PGW-C and SMF user sessions. - Terminate idle PGW-C and SMF sessions. The value of the idle-monitor-timerSMF software setting indicates the maximum time in seconds that a session is allowed to remain idle without an uplink payload. For example, a value of 10 will terminate sessions that have been idle for 10 seconds, i.e., sessions without an uplink payload for 10 seconds. - Monitor the end of idle sessions - Terminates non-idle PGW-C and SMF sessions. Terminating PGW-C and SMF sessions removes the corresponding UEs in SGW-C, MME, and AMF. - Unregister SMF from NRF.

[0111] Figure 11 shows upgrade example 2(2) of upgrading SMF. In the upgraded SMF, 1. Verify that the {S-NSSAI,DNN} that the test UE will use is configured correctly. 2. Print / show the NfInstanceId for "your own" SMF (for example, initially set locally via epg pgw sbi smf-services nf-instance-id). In AMF (which requires implementation in AMF), • Configure the mapping between the test UE (SUPI) and the SMF NfInstanceId. Based on SUPI, detect when the test UE initiates the PDU session establishment procedure. • NF discovery (SMF selection) uses the parameter "target-nf-instance-id" with a configured value (in some cases, NRF implementation may be required).

[0112] 6.3 Redirect UE traffic back to the target PCC After upgrading the PCC, redirect the UE traffic back to the combined SMF and PGW-C. 6.3.2 Direct UE traffic to the combined SMF and PGW-C Step 1. Log in to the provider pod. 2. Make the SMF service discoverable in the NRF. This initiates the Nnrf_NFUpdate service operation with the NRF. AMF uses SMF for new UEs during the discovery request procedure with NRF. 3. Unblock the creation of new PGW-C and SMF user sessions. MME begins selecting this PGW-C for new UEs when the timer specified by the PgwTempUnavailableDuration parameter times out. By default, that timer is set to 1200 seconds.

[0113] Canary execution, alternative form 1: Run the command that will report nf-status as undiscoverable. Use the test UE and the upgraded SMF to run the desired tests. Once all tests are passed, the upgraded SMF will... Run the command that states "nf-status registered".

[0114] Canary execution, alternative form 2: Run the command that says nf-status maintenance / test. Use the test UE and the upgraded SMF to run the desired tests. Once all tests are passed, the upgraded SMF will... Run the command that states "nf-status registered".

[0115] Figure 12 is a block diagram showing an embodiment of a first network node 13, such as an AMF, for handling a test process related to a third network node 15 in a wireless communication network 1, according to an embodiment of this specification.

[0116] The first network node 13 may include a processing circuit 1201, for example, one or more processors, configured to carry out the method of this specification.

[0117] The first network node 13 and / or processing circuit 1201 are configured to obtain instance identification information of the updated or started third network node 15.

[0118] The first network node 13 and / or processing circuit 1201 are configured to store one or more identifiers of one or more UEs (each) to be used during the test process. The one or more identifiers are mapped to the acquired instance identifiers.

[0119] The first network node 13 and / or processing circuit 1201 are configured to check whether the identification information of UE 10 matches one or more stored identification information of one or more UEs when a session establishment of UE 10 is detected. If the identification information of UE matches one or more stored identification information of one or more UEs, the first network node 13 and / or processing circuit 1201 are configured to initiate NF discovery toward the second network node 14 using the acquired instance identification information mapped to the matching identification information. The first network node 13 and / or processing circuit 1201 may also be configured to initiate NF discovery by sending an instruction to the second network node 14 indicating a requested status related to the test, maintenance, or update mode of the third network node 15. Thus, the first network node 13 and / or processing circuit 1201 may be configured to send an instruction which is a flag indicating maintenance mode or test mode. The first network node 13 and / or processing circuit 1201 may be configured to evaluate or determine whether the identification information of UE 10 matches the stored UE identification information. If there is a match, the first network node 13 and / or processing circuit 1201 may be configured to activate the NRF discovery network function for the third network node 15, which is in maintenance mode or test mode. If there is no match, the first network node 13 and / or processing circuit 1201 may be configured to activate a legacy implementation to discover the third network node, such as SMF.

[0120] The first network node 13 and / or processing circuit 1201 may be configured to receive a response from the second network node 14 indicating the profile of the updated or started third network node 15.

[0121] The first network node 13 and / or processing circuit 1201 may be configured to receive responses by receiving one or more instructions for one or more profiles of one or more third network nodes. The status of each profile may be indicated in the response carrying one or more instructions.

[0122] The first network node 13 and / or processing circuit 1201 may be configured to select one profile with a status indicating test, maintenance, or update.

[0123] The first network node 13 and / or processing circuit 1201 may be configured to obtain the identification information of one or more UEs to be used during the test process, which are mapped to the instance identification information obtained during local configuration.

[0124] The first network node 13 may include a memory 1206. The memory 1206 includes one or more units to be used to store data, such as data packets, subscription data, mappings, instructions, status instructions, instance identification information, UE identification information, mobility events, measurements, events, and applications for implementing the methods disclosed herein when in operation, and the like. Furthermore, the first network node 13 may include a communication interface 1207 which includes something like a transmitter, receiver, transceiver and / or one or more antennas.

[0125] Each method according to the embodiments described herein for the first network node 13 is implemented by, for example, a computer program product 1208 or a computer program, which comprises instructions, i.e., software code portions, that cause at least one processor to perform the actions described herein, which are performed by the first network node 13, when executed on at least one processor. The computer program product 1208 may be stored on a computer-readable storage medium 1209, for example, a disk, a Universal Serial Bus (USB) stick, or the like. The computer-readable storage medium 1209 storing the computer program product may comprise instructions that, when executed on at least one processor, cause at least one processor to perform the actions described herein, which are performed by the first network node 13. In some embodiments, the computer-readable storage medium may be temporary or non-temporary computer-readable storage medium. Accordingly, embodiments of this specification may disclose a first network node 13 for handling tests in a wireless communication network, the first network node 13 comprising a processing circuit and a memory, the memory comprising instructions executable by the processing circuit, thereby enabling the first network node to operate to carry out any of the methods of this specification.

[0126] Figure 13 is a block diagram showing an embodiment of a second network node 14, such as an NRF, for handling a test process related to a third network node 15 in a wireless communication network 1, according to an embodiment of this specification.

[0127] The second network node 14 may include a processing circuit 1301, for example, one or more processors, configured to carry out the method of this specification.

[0128] The second network node 14, and / or the processing circuit 1301, are configured to obtain instance identification information of the updated or started third network node 15.

[0129] The second network node 14 and / or processing circuit 1301 are configured to receive requests related to NF discovery from the first network node 13 using instance identification information.

[0130] The second network node 14, and / or the processing circuit 1301, are configured to generate a response based on instance identification information, status indications for the third network node 15, conditional indications, instructions received from the first network node 13, and / or previously stored status information. The response indicates the profile of the updated or started third network node 15.

[0131] The second network node 14 and / or processing circuit 1301 are configured to send the generated response to the first network node.

[0132] The second network node 14, and / or the processing circuit 1301, may be configured to receive requests by receiving instructions from the first network node 13 indicating the status of testing, maintenance, or updating the third network node 15. These instructions may include a flag called "test mode" or "maintenance mode" (Boolean), which is set to true.

[0133] The second network node 14 and / or the processing circuit 1301 may be configured to receive status instructions from the third network node 15 indicating that the third network node 15 is undiscoverable or in a status related to testing, maintenance, or updating. Thus, the second network node 14 may set the NF status to "test" or "maintenance" initiated via a command in the third network node 15. The second network node 14 and / or the processing circuit 1301 may be configured to receive condition instructions. The second network node 14 and / or the processing circuit 1301 may be configured to receive condition instructions from the third network node 15 indicating one or more conditions that can be selected by an NF service consumer, i.e., an NF instance with an NFStatus value set to "test".

[0134] The second network node 14 and / or processing circuit 1301 may be configured to generate a response by applying one or more instructions of one or more profiles of one or more third network nodes to the response. The status of each profile may be indicated in the response carrying one or more instructions. The second network node 14 and / or processing circuit 1301 may be configured to generate and navigate a list of profiles, each with its indicated status.

[0135] The second network node 14 may include a memory 1306. The memory 1306 includes one or more units to be used to store data, such as data packets, subscription data, mappings, instructions, status instructions, instance identification information, UE identification information, mobility events, measurements, events, and applications for implementing the methods disclosed herein when in operation, and the like. Furthermore, the second network node 14 may include a communication interface 1307, such as a transmitter, receiver, transceiver and / or one or more antennas.

[0136] Each method according to the embodiments described herein for the second network node 14 is implemented by, for example, a computer program product 1308 or a computer program, which comprises instructions, i.e., software code portions, that cause at least one processor to perform the actions described herein, which are performed by the second network node 14, when executed on at least one processor. The computer program product 1308 may be stored on a computer-readable storage medium 1309, for example, a disk, a USB stick, or the like. The computer-readable storage medium 1309 storing the computer program product may comprise instructions that, when executed on at least one processor, cause at least one processor to perform the actions described herein, which are performed by the second network node 14. In some embodiments, the computer-readable storage medium may be temporary or non-temporary computer-readable storage medium. Accordingly, embodiments of this specification may disclose a second network node for handling tests in a wireless communication network, the second network node comprising a processing circuit and a memory, the memory comprising instructions executable by the processing circuit, thereby enabling the second network node to operate to carry out any of the methods of this specification.

[0137] Figure 14 is a block diagram showing an embodiment of a third network node 15, such as an SMF, PCF, or CHF, for handling a test process related to the third network node 15 in a wireless communication network 1, according to embodiments of this specification.

[0138] The third network node 15 may include a processing circuit 1401, for example, one or more processors, configured to carry out the method of this specification.

[0139] The third network node 15, and / or the processing circuit 1401, is configured to provide the second network node 14 with a status indication of the third network node 15, along with its profile information, which indicates a status related to testing, maintenance, or updating the third network node 15. The third network node 15, and / or the processing circuit 1401, may be configured to provide conditional indications to the second network node 14, such as by sending them. Conditional indications may indicate selection conditions for UEs based on a set of UEs or a set of tracking areas. For example, a set of SUPIs stating that NF instances under test status are selected, a set of GPSIs stating that NF instances under test status are selected, a set of PEIs for UEs stating that NF instances under test status are selected, and / or a set of TAIs stating that NF instances under test status are selected for a given UE. Conditional indications may indicate one or more conditions under which an NF instance with an NFStatus value set to "test," i.e., the third network node 15, may be selected.

[0140] The third network node 15 and / or processing circuit 1401 may be configured to handle the test process of the UE 10, and if the test process is successful, the third network node 15 and / or processing circuit 1401 may be configured to send an instruction to the second network node 14 indicating the status of the third network node 15 as a registered third network node.

[0141] The third network node 15 may include a memory 1406. The memory 1406 includes one or more units to be used to store data such as data packets, subscription data, mappings, instructions, status instructions, instance IDs, UE IDs, mobility events, measurements, events, and applications for implementing the methods disclosed herein when in operation, and the like. Furthermore, the third network node 15 may include a communication interface 1407 which includes something like a transmitter, receiver, transceiver and / or one or more antennas.

[0142] Each method according to the embodiments described herein for the third network node 15 is implemented by, for example, a computer program product 1408 or a computer program, which comprises instructions, i.e., software code portions, that cause at least one processor to perform the actions described herein, which are performed by the third network node 15, when executed on at least one processor. The computer program product 1408 may be stored on a computer-readable storage medium 1409, for example, a disk, a USB stick, or the like. The computer-readable storage medium 1409 storing the computer program product may comprise instructions that, when executed on at least one processor, cause at least one processor to perform the actions described herein, which are performed by the third network node 15. In some embodiments, the computer-readable storage medium may be temporary or non-temporary computer-readable storage medium. Accordingly, embodiments of this specification may disclose a third network node 15 for handling tests in a wireless communication network, the third network node 15 comprising a processing circuit and a memory, the memory comprising instructions executable by the processing circuit, thereby enabling the third network node to operate to carry out any of the methods of this specification.

[0143] Please note that "transmitting to" and "receiving from" also cover embodiments in which the message is sent via some intermediate node; that is, "to" can be interpreted as "towards" and "from" can be interpreted as "transmitted by" (not necessarily directly to or from).

[0144] In some embodiments, the more general term “network node” is used, and the term “network node” can refer to any type of radio network node or any network node that communicates with a radio device and / or another network node. Examples of network nodes include node B, MeNB, SeNB, network nodes belonging to a master cell group (MCG) or secondary cell group (SCG), base stations (BS), MSR radio nodes such as multi-standard radio (MSR) BS, e-node B, g-node B, network controllers, RNCs, BSCs, relays, donor node control relays, base station transceiver stations (BTS), access points (APs), transmit points, transmit nodes, remote radio units (RRUs), remote radio heads (RRHs), and nodes in distributed antenna systems (DAS).

[0145] In some embodiments, the non-limiting term "wireless device" or "UE" is used, and the term "wireless device" or "UE" refers to any type of wireless device that communicates with network nodes and / or other wireless devices in a cellular or mobile communication system. Examples of UEs include target devices, D2D UEs, proximity-enabled UEs (also known as ProSe UEs), machine-type UEs or machine-to-machine (M2M) communication-capable UEs, tablets, mobile terminals, smartphones, laptop embedded equipment (LEEs), laptop-mounted equipment (LMEs), USB dongles, and the like.

[0146] The embodiments are applicable to any RAT or multi-RAT system in which a wireless device receives and / or transmits signals (e.g., data), such as NR, Wi-Fi, LTE, LTE Advanced, WCDMA, GSM / GSM Evolutionary High Speed ​​Data Rate (GSM / EDGE), Global Interoperability for Microwave Access (WiMAX), or Ultra Mobile Broadband (UMB), to name just a few possible implementations.

[0147] As readily understood by those familiar with communications design, the functional means or circuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, some or all of the various functions may be implemented together in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Some of the functions may be implemented, for example, on a processor shared with other functional components of a wireless device or network node.

[0148] Alternatively, some of the functional elements of the processing means described may be provided by using dedicated hardware, while other functional elements may be provided in conjunction with appropriate software or firmware, along with hardware for running the software. Therefore, the terms “processor” or “controller” as used herein may implicitly include, but are not limited to, hardware capable of running software, digital signal processor (DSP) hardware and / or program or application data. Other conventional and / or custom hardware may also be included. Designers of communication devices should be aware of the cost, performance, and maintenance trade-offs inherent in these design selections.

[0149] Any suitable step, method, feature, function, or benefit disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuits, which may include one or more microprocessors or microcontrollers, and other digital hardware, which may include DSPs, dedicated digital logic, etc. The processing circuits may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory may include program instructions for executing one or more communication and / or data communication protocols, and instructions for performing one or more of the techniques described herein. In some implementations, the processing circuits may be used to cause each functional unit to perform the corresponding function according to one or more embodiments of the Disclosure.

[0150] It will be understood that the above description and accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. Therefore, the apparatus and techniques taught herein are not limited by the above description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents. JPEG2026512942000019.jpg255170JPEG2026512942000020.jpg255170JPEG2026512942000021.jpg255170JPEG2026512942000022.jpg255170JPEG2026512942000023.jpg255170JPEG2026512942000024.jpg255170JPEG2026512942000025.jpg255170JPEG2026512942000026.jpg255170JPEG2026512942000027.jpg255170JPEG2026512942000028.jpg255170JPEG2026512942000029.jpg255170JPEG2026512942000030.jpg255170JPEG2026512942000031.jpg255170JPEG2026512942000032.jpg255170JPEG2026512942000033.jpg255170JPEG2026512942000034.jpg255170JPEG2026512942000035.jpg255170JPEG2026512942000036.jpg255170JPEG2026512942000037.jpg255170JPEG2026512942000038.jpg255170JPEG2026512942000039.jpg255170JPEG2026512942000040.jpg255170JPEG2026512942000041.jpg255170JPEG2026512942000042.jpg255170JPEG2026512942000043.jpg255170JPEG2026512942000044.jpg255170JPEG2026512942000045.jpg255170JPEG2026512942000046.jpg255170JPEG2026512942000047.jpg255170JPEG2026512942000048.jpg255170JPEG2026512942000049.jpg255170JPEG2026512942000050.jpg255170JPEG2026512942000051.jpg255170JPEG2026512942000052.jpg255170JPEG2026512942000053.jpg255170JPEG2026512942000054.jpg255170JPEG2026512942000055.jpg255170JPEG2026512942000056.jpg255170JPEG2026512942000057.jpg255170JPEG2026512942000058.jpg255170JPEG2026512942000059.jpg255170JPEG2026512942000060.jpg255170JPEG2026512942000061.jpg255170JPEG2026512942000062.jpg255170JPEG2026512942000063.jpg255170JPEG2026512942000064.jpg255170JPEG2026512942000065.jpg255170JPEG2026512942000066.jpg255170JPEG2026512942000067.jpg255170JPEG2026512942000068.jpg255170JPEG2026512942000069.jpg255170JPEG2026512942000070.jpg255170JPEG2026512942000071.jpg47170.

Claims

1. A method performed by a first network node (13) for handling a test process related to a third network node (15) in a wireless communication network (1), wherein the method is: - Obtaining instance identification information of the updated or started third network node (15) (701), - To store the identification information of one or more UEs to be used during the test process, which is mapped to the acquired instance identification information (703), - When the establishment of a session for UE(10) is detected, check whether the identification information of the UE(10) matches the one or more stored identification information of the one or more UE(10) (704), - On the condition that the identification information of the UE (10) matches one of the stored identification information of one or more UEs, initiating network function (NF) discovery toward the second network node (14) using the acquired instance identification information mapped to the matching identification information (705) Methods that include...

2. The method according to claim 1, wherein initiating the NF discovery (705) includes sending an instruction to the second network node (14) indicating a requested status related to a test, maintenance, or update mode of the third network node (15).

3. - Receiving a response from the second network node (14) indicating the profile of the updated or started third network node (15) (706) The method according to claim 1 or 2, further comprising:

4. The method according to claim 3, wherein receiving the response (706) includes receiving one or more instructions for one or more profiles of one or more third network nodes, the status of each profile is indicated in the response carrying the one or more instructions.

5. - Select one profile with a status indicating testing, maintenance, or updating (707) The method according to claim 4, further comprising:

6. The method according to any one of claims 1 to 5, further comprising obtaining the identification information of one or more UEs to be used during the test process, which is mapped to the obtained instance identification information during local configuration (702).

7. The method according to any one of claims 1 to 6, wherein the first network node (13) is equipped with an access and mobility management function (AMF).

8. A method performed by a second network node (14) for handling a test process related to a third network node (15) in a wireless communication network, wherein the method is: - Obtaining instance identification information of the updated or started third network node (15) (802), - Using the instance identification information, receive a request related to network function (NF) discovery from the first network node (13) (803), - Generating a response (804) based on the instance identification information, the status indication of the third network node (15), the condition indication, the indication received from the first network node (13), and / or previously stored status information, wherein the response indicates the profile of the updated or started third network node (15), - Sending the generated response to the first network node (13) (805) Methods that include...

9. The method according to claim 8, wherein receiving the request (803) includes receiving an instruction from the first network node (13) indicating the status of testing, maintenance or updating the third network node (15).

10. - To acquire (801), ○ The status indication from the third network node (15) that the third network node (15) is undiscoverable or in a status related to testing, maintenance or updating, and / or ○ The above condition instruction To obtain (801) The method according to claim 8 or 9, further comprising:

11. The method according to any one of claims 8 to 10, wherein generating the response (804) includes applying to the response one or more instructions of one or more profiles of one or more third network nodes, the status of each profile is indicated in the response carrying the one or more instructions.

12. The method according to any one of claims 8 to 11, wherein the second network node (14) is equipped with a network repository function (NRF).

13. A method performed by a third network node (15) for handling a test process related to the third network node (15) in a wireless communication network, wherein the method is: - Providing the second network node (14) with a status indication of the third network node (15) along with the profile information of the third network node (15) (903), wherein the indication specifies a status related to testing, maintenance, or updating the third network node (15) (903). Methods that include...

14. - Handling the UE (10) test process (904), - If the test process is successful, send an instruction to the second network node (14) indicating the status of the third network node (15) as a registered third network node (15) (905) The method according to claim 13, further comprising:

15. The method according to claim 13 or 14, wherein the third network node further provides conditional instructions to the second network node (14).

16. The method according to claim 15, wherein the condition instruction specifies the selection criteria for a UE based on a set of UEs or a set of tracking areas.

17. The method according to any one of claims 13 to 16, wherein the third network node (15) includes a session management function (SMF), a policy control function (PCF), or a billing function (CHF).

18. A first network node (13) for handling a test process related to a third network node (15) in a wireless communication network, wherein the first network node (13) is Obtaining instance identification information of the updated or started third network node (15), The process involves storing the identification information of one or more UEs to be used during the test process, which is mapped to the acquired instance identification information. When the establishment of a session for UE(10) is detected, it is checked whether the identification information of UE(10) matches the one or more identification pieces of stored information of the one or more UEs, The condition that the identification information of the UE (10) matches one of the stored identification information of one or more UEs, and the instance identification information mapped to the matching identification information is used to initiate network function (NF) discovery toward the second network node (14). A first network node (13) configured to perform the following actions.

19. A first network node (13) according to claim 18, configured to carry out the method described in any one of claims 2 to 7.

20. A second network node (14) for handling a test process related to a third network node (15) in a wireless communication network, wherein the second network node (14) is Obtaining instance identification information of the updated or started third network node (15), Using the aforementioned instance identification information, a request related to network function (NF) discovery is received from the first network node (13), To generate a response based on the instance identification information, the status indication of the third network node (15), the condition indication, the indication received from the first network node (13), and / or previously stored status information, wherein the response indicates the profile of the updated or started third network node (15), The generated response is transmitted to the first network node (13). A second network node (14) configured to perform the following actions.

21. The second network node (14) according to claim 20, wherein the second network node (14) is configured to carry out the method described in any one of claims 9 to 12.

22. A third network node (15) is for handling test processes related to the third network node (15) in a wireless communication network, and the third network node (15) is To provide a second network node (14) with a status indication of the third network node (15), along with the profile information of the third network node (15), wherein the indication specifies a status related to testing, maintenance, or updating the third network node (15). A third network node (15) configured to perform the following actions.

23. The third network node (15) according to claim 22, wherein the third network node (15) is configured to carry out the method described in any one of claims 14 to 17.

24. A first network node (13) for handling a test process related to a third network node (15) in a wireless communication network, comprising a processor and memory, wherein the memory contains instructions executable by the processor, and thereby, The first network node (13) is Obtaining instance identification information of the updated or started third network node (15), The process involves storing the identification information of one or more UEs to be used during the test process, which is mapped to the acquired instance identification information. When the establishment of a session for UE(10) is detected, it is checked whether the identification information of UE(10) matches the one or more identification pieces of stored information of the one or more UEs, The condition that the identification information of the UE (10) matches one of the stored identification information of one or more UEs, and the instance identification information mapped to the matching identification information is used to initiate network function (NF) discovery toward the second network node (14). It is operable to perform the following: The first network node (13).

25. A second network node (14) for handling a test process related to a third network node (15) in a wireless communication network, comprising a processor and memory, wherein the memory contains instructions executable by the processor, and thereby, The second network node (14) is Obtaining instance identification information of the updated or started third network node (15), Using the aforementioned instance identification information, a request related to network function (NF) discovery is received from the first network node (13), To generate a response based on the instance identification information, the status indication of the third network node (15), the condition indication, the indication received from the first network node (13), and / or previously stored status information, wherein the response indicates the profile of the updated or started third network node (15), The generated response is transmitted to the first network node (13). It is operable to perform the following: The second network node (14).

26. A third network node (15) for handling test processes related to the third network node (15) in a wireless communication network, comprising a processor and memory, wherein the memory contains instructions executable by the processor, thereby, The third network node (15) is To provide a second network node (14) with a status indication of the third network node (15), along with the profile information of the third network node (15), wherein the indication specifies a status related to testing, maintenance, or updating the third network node (15). It is operable to perform the following: The third network node (15).

27. A computer program product, when executed on at least one processor, comprising instructions that cause the at least one processor to perform the method according to any one of claims 1 to 17, which is performed by a first network node (13), a second network node (14), or a third network node (15), respectively.

28. A computer-readable storage medium storing a computer program product that, when executed on at least one processor, stores instructions causing the at least one processor to perform the method according to any one of claims 1 to 17, which is performed by a first network node (13), a second network node (14), or a third network node (15), respectively.

Images