CN117768915A

CN117768915A - Node in wireless communication system and method for performing the same

Info

Publication number: CN117768915A
Application number: CN202310802039.4A
Authority: CN
Inventors: 王妍茹; 许丽香; 王弘; 汪巍崴
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2022-08-03
Filing date: 2023-06-30
Publication date: 2024-03-26

Abstract

The present disclosure provides a node in a wireless communication system and a method performed by the same, wherein a method may include: receiving, from the second node, at least one of second information including non-public network NPN support capability information of the second node and/or the third node, fourth information including NPN access requirement information of the user equipment UE, sixth information including neighbor cell NPN support capability information of the second node and/or the third node and/or additional NPN support capability information of the second node and/or the third node, ninth information including a resource status and/or a load condition of the NPN associated with the second node and/or the third node, and twelfth information including NPN information of the NPN associated with the second node and/or the third node; making a network self-optimization decision based on the at least one information and/or sending the at least one information to other nodes; wherein the third node is at least one of the other nodes than the second node.

Description

Node in wireless communication system and method for performing the same

Technical Field

The present disclosure relates to the field of wireless communication technology, and more particularly, to a node in a wireless communication system and a method performed by the same.

Background

In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi 5G communication systems. Therefore, a 5G or quasi 5G communication system is also referred to as a "super 4G network" or a "LTE-after-system".

Wireless communication is one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeds 50 billion and continues to grow rapidly. As smartphones and other mobile data devices (e.g., tablet computers, notebook computers, netbooks, e-book readers, and machine type devices) become increasingly popular among consumers and businesses, the demand for wireless data services is rapidly growing. To meet the high-speed growth of mobile data services and support new applications and deployments, it is important to improve the efficiency and coverage of the wireless interface.

A Non-Public Network (NPN) is a Network that is distinguished from a Public Network in that it serves a particular user and may generally include the following two types:

an independent networking NPN network (snan), which is independent of the PLMN network and operated by the snan operator.

A non-independently networked NPN network (Public network integrated NPN, PNI-NPN) that relies on the PLMN network and is operated by a legacy operator.

The SNPN supports the UE to access the SNPN with certificates acquired by certificate holders (Credentials Holder, CH) other than the SNPN. The SNPN supports the UE to access a bootstrap network (Onboarding Network) to provision the UE with a certificate of the SNPN for initial authentication for the UE to access a target/desired SNPN.

Disclosure of Invention

Embodiments of the present disclosure provide a method performed by a first node in a wireless communication system, comprising: receiving, from a second node, at least one of second information including non-public network NPN support capability information of the second node and/or a third node, fourth information including NPN access requirement information of a user equipment UE, sixth information including neighbor cell NPN support capability information of the second node and/or a third node and/or additional NPN support capability information of the second node and/or a third node, ninth information including a resource status and/or a load condition of an NPN associated with the second node and/or a third node, twelfth information including NPN information of an NPN associated with the second node and/or a third node, and fourteenth information including a result of NPN function activation of the second node; making a network self-optimization decision based on the at least one information and/or sending the at least one information to other nodes; wherein the third node is at least one of the other nodes in the wireless communication system than the second node.

Embodiments of the present disclosure provide a method performed by a second node in a wireless communication system, comprising: transmitting, to a first node, at least one of second information including non-public network NPN support capability information of the second node and/or a third node, twelfth information including NPN access requirement information of a user equipment UE, sixth information including neighbor cell NPN support capability information of the second node and/or a third node and/or additional NPN support capability information of the second node and/or a third node, ninth information including a resource status and/or a load condition of an NPN associated with the second node and/or the third node, twelfth information including NPN information of an NPN associated with the second node and/or the third node, and fourteenth information including a result of NPN function activation of the second node, wherein the third node is at least one of other nodes in the wireless communication system than the second node.

Embodiments of the present disclosure provide a first node device in a wireless communication system, comprising: a transceiver configured to transmit and receive signals; and a processor coupled with the transceiver and configured to perform a method performed by a first node in a wireless communication system according to an embodiment of the disclosure.

Embodiments of the present disclosure provide a second node apparatus in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled with the transceiver and configured to perform a method performed by a second node in a wireless communication system according to an embodiment of the disclosure.

Embodiments of the present disclosure provide a computer readable medium having stored thereon computer readable instructions which, when executed by a processor, are for implementing a method performed by a first node and/or a second node in a wireless communication system according to embodiments of the present disclosure.

The method performed by a first node and/or a second node in a wireless communication system enables self-optimizing decisions or updating configurations to be made at the network side by interacting information related to non-public networks between nodes.

Drawings

The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:

FIG. 1 is an exemplary system architecture 100 for System Architecture Evolution (SAE);

FIG. 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure;

Fig. 3 illustrates a flow chart of a method 300 performed by a first node in a wireless communication system in accordance with an embodiment of the disclosure;

fig. 4 illustrates a flow chart of a method 400 performed by a second node in a wireless communication system in accordance with an embodiment of the disclosure;

FIG. 5A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 5B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 6A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 6B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 6C illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure;

FIG. 7A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 7B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 7C illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 8A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 8B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 9A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 9B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 9C illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure;

FIG. 9D illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure;

FIG. 9E illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure;

FIG. 9F illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure;

FIG. 9G illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure;

fig. 10 shows a schematic diagram of a first node 1000 according to an embodiment of the disclosure;

fig. 11 shows a schematic diagram of a second node 1100 according to an embodiment of the disclosure;

FIG. 12A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure; and is also provided with

Fig. 12B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure.

Detailed Description

The following description with reference to the accompanying drawings is provided to facilitate a thorough understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. The description includes various specific details to facilitate understanding but should be considered exemplary only. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and phrases used in the following specification and claims are not limited to their dictionary meanings, but are used only by the inventors to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following descriptions of the various embodiments of the present disclosure are provided for illustration only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more such surfaces.

The terms "comprises" or "comprising" may refer to the presence of a corresponding disclosed function, operation or component that may be used in various embodiments of the present disclosure, rather than to the presence of one or more additional functions, operations or features. Furthermore, the terms "comprises" or "comprising" may be interpreted as referring to certain features, numbers, steps, operations, constituent elements, components, or combinations thereof, but should not be interpreted as excluding the existence of one or more other features, numbers, steps, operations, constituent elements, components, or combinations thereof.

The term "or" as used in the various embodiments of the present disclosure includes any listed term and all combinations thereof. For example, "a or B" may include a, may include B, or may include both a and B.

Unless defined differently, all terms (including technical or scientific terms) used in this disclosure have the same meaning as understood by one of ordinary skill in the art to which this disclosure pertains. The general terms as defined in the dictionary are to be construed to have meanings consistent with the context in the relevant technical field, and should not be interpreted in an idealized or overly formal manner unless expressly so defined in the present disclosure.

According to an embodiment of the present disclosure, the method performed by the first node in the wireless communication system further comprises: transmitting first information comprising a request for non-public network NPN support capability information of a second node and/or a third node to the second node before receiving the at least one information from the second node, wherein the second information is transmitted by the second node to the first node based on the first information, wherein the first information comprises one or more of: the method comprises the steps of sending a node identifier, receiving the node identifier, an NPN identifier corresponding to the requested information, the content requested to be reported, the reporting type, the reporting registration request, the reporting interval and the triggering event.

According to an embodiment of the present disclosure, the method performed by the first node in the wireless communication system further comprises: transmitting third information comprising a request for NPN access requirement information of the user equipment UE to a second node before receiving the at least one information from the second node, wherein the fourth information is transmitted to the first node by the second node based on the third information, wherein the third information comprises one or more of: the method comprises the steps of sending node identification, receiving node identification, UE identification, reporting a registration request and requesting the reported NPN access demand content.

According to an embodiment of the present disclosure, the method performed by the first node in the wireless communication system further comprises: transmitting fifth information including a request for neighbor cell NPN support capability information of the second node and/or a third node and/or additional NPN support capability information of the second node and/or third node to the second node before receiving the at least one information from the second node, wherein the sixth information is transmitted to the first node by the second node based on the fifth information, wherein the fifth information includes one or more of: the method comprises the steps of sending a node identifier, receiving the node identifier, requesting to report the NPN supporting capability information of a neighboring cell and/or a neighboring node, requesting to report the identifier of the NPN corresponding to the information, requesting to report additional NPN supporting capability information, reporting a type, reporting a registration request, reporting a section and triggering an event.

According to an embodiment of the present disclosure, the method performed by the first node in the wireless communication system further comprises: transmitting seventh information comprising a request for a resource status and/or load condition of an NPN associated with the second node and/or a third node to the second node before receiving the at least one information from the second node, and receiving eighth information comprising a response to the request for a resource status and/or load condition of an NPN associated with the second node and/or the third node from the second node, wherein the ninth information is transmitted to the first node by the second node based on the seventh information, wherein the seventh information comprises one or more of: transmitting a node identifier, receiving a node identifier, an NPN identifier, requested content, a reporting type, a reporting registration request, a reporting interval, a triggering event, and wherein the eighth information includes one or more of: the method comprises the steps of sending a node identifier, receiving the node identifier, reporting an NPN identifier corresponding to information, reporting content, not reporting the NPN identifier corresponding to the information, not reporting the content and requesting reasons of failure.

According to an embodiment of the present disclosure, the method performed by the first node in the wireless communication system further comprises: transmitting, to a second node, eleventh information comprising a request for NPN information of NPN associated with the second node and/or a third node, prior to receiving the at least one information from the second node, wherein the twelfth information is transmitted by the second node to the first node based on the eleventh information, wherein the eleventh information comprises one or more of: the method comprises the steps of a UE mark, a sending node mark, a receiving node mark, an NPN information request, an NPN report request, an NPN failure information request, an NPN mark corresponding to a report requested to be reported, an NPN mark corresponding to information requested to be reported, an indication of a report about to timeout and/or about to be discarded requested to be reported, an indication of information about to timeout and/or about to be discarded requested to be reported, a request for reporting a report corresponding to a specific time, a request for reporting information corresponding to a specific time, a request for reporting a report corresponding to a specific configuration, and a request for reporting information corresponding to a specific configuration.

According to an embodiment of the present disclosure, the method performed by the first node in the wireless communication system further comprises: before sending eleventh information to the second node including a request for NPN information of an NPN associated with the second node and/or a third node, receiving tenth information from the second node indicating that NPN information of an NPN associated with the second node and/or the third node is available, wherein the eleventh information is sent to the second node by the first node based on the tenth information, wherein the tenth information includes one or more of: the method comprises the steps of identifying a UE, sending a node identification, receiving the node identification, enabling NPN information, enabling NPN report, enabling NPN failure information, enabling NPN report, enabling NPN identification corresponding to the NPN report, NPN identification corresponding to the NPN failure report, NPN identification corresponding to the NPN information, NPN identification corresponding to the NPN failure information, an identification about to timeout and/or about to discard of the NPN report, an identification about to timeout and/or about to discard of the NPN failure report, an identification about to timeout and/or about to discard of the NPN information, a time corresponding to the NPN report, a time corresponding to the NPN failure information, a configuration corresponding to the NPN report, a configuration corresponding to the NPN failure report, a configuration corresponding to the NPN information and a configuration corresponding to the NPN failure information.

According to an embodiment of the present disclosure, the method performed by the first node in the wireless communication system further comprises: transmitting thirteenth information including an NPN function activation request to a second node before receiving the at least one information from the second node, wherein the fourteenth information is transmitted to the first node by the second node based on the thirteenth information, wherein the thirteenth information includes one or more of: the method comprises the steps of sending a node identifier, receiving the node identifier, activating a request identifier, an NPN identifier, requesting to activate a guiding function, requesting to activate a function accessed by a certificate acquired by a certificate holder, and requesting a reason for activation.

According to an embodiment of the present disclosure, the fourteenth information includes one or more of the following: the method comprises the steps of sending node identification, receiving node identification, activating request identification, activating successful NPN identification, activating NPN identification of a successful boot function, activating NPN identification of a function accessed by a certificate acquired by a successful certificate holder, activating successful identification of the boot function, activating successful identification of the function accessed by the certificate acquired by the certificate holder, activating successful time, activating failed NPN identification of the boot function, activating failed identification of the NPN of the function accessed by the certificate acquired by the certificate holder, activating failed identification of the boot function, activating failed identification of the function accessed by the certificate acquired by the certificate holder, activating failed time, activating successful reason and activating failed reason.

According to an embodiment of the present disclosure, the at least one information is used for at least one of the first node, the second node and other nodes to make network self-optimization decisions, wherein the network self-optimization decisions comprise at least one of network power saving, load balancing, coverage optimization, mobility optimization and/or management, network configuration formulation and/or network configuration update.

According to an embodiment of the present disclosure, the second information includes one or more of the following: the method comprises the steps of sending a node identifier, receiving the node identifier, an NPN identifier, a guide support identifier, an identifier for accessing a certificate acquired by a certificate holder, a group identifier for network selection, an indication of whether the NPN has the capability of guide support, an indication of whether the NPN has the capability of accessing the certificate acquired by the certificate holder, an indication of whether the guide support is opened, an indication of whether the certificate acquired by the certificate holder is opened, a triggering event and a reason that NPN support capability information cannot be reported.

According to an embodiment of the present disclosure, the fourth information includes one or more of the following: the method comprises the steps of sending a node identifier, receiving the node identifier, a UE identifier, an NPN identifier, a reason for accessing the NPN by the UE, whether guiding is needed, whether guiding is supported, whether accessing is needed by using a certificate acquired by a certificate holder, whether accessing is supported by using the certificate acquired by the certificate holder, the purpose of accessing the NPN by the UE, a guiding request, accessing request by using the certificate acquired by the certificate holder, a target NPN and/or an expected NPN identifier, a group identifier which corresponds to a network accessed by the UE and is used for network selection and/or a list of group identifiers used for network selection, and a reason that NPN access requirement information of the UE cannot be reported.

According to an embodiment of the present disclosure, the sixth information includes one or more of the following: the method comprises the steps of sending node identification, receiving node identification, neighbor cell and/or neighbor node NPN supporting capability information, supported NPN identification, additional guiding supporting identification, additional access supporting identification by using a certificate acquired by a certificate holder, additional supporting corresponding group identification for network selection and triggering event.

According to an embodiment of the present disclosure, the ninth information includes one or more of the following: the method comprises the steps of sending a node identifier, receiving the node identifier, reporting NPN identifier corresponding to the reported information, reporting content and triggering event.

According to an embodiment of the present disclosure, the twelfth information includes one or more of the following: the method comprises the steps of a UE identifier, a node identifier, a cell identifier, an NPN identifier, a time from access to reporting, a time from access failure to reporting, a time from access attempt to reporting, a time from switch to reporting, a reason for UE access to NPN, a purpose of UE access and/or registration of NPN, a mode of access and/or registration of NPN, a reconnection NPN identifier, a reconnection cell identifier, an indication of whether to switch from NPN to a common cell, an indication of whether to switch from a common cell to NPN, a group identifier for network selection of an access cell, a group identifier for network selection of a neighboring cell, a target NPN and/or an expected NPN identifier, a network selection mode, a reason for access and/or switch failure and/or a reason for service failure.

According to an embodiment of the present disclosure, the method performed by the second node in the wireless communication system further comprises: receiving, from the first node, first information comprising a request for non-public network NPN support capability information of the second node and/or a third node, prior to sending the at least one piece of information to the first node, wherein the second information is sent by the second node to the first node based on the first information, wherein the first information comprises one or more of: the method comprises the steps of sending a node identifier, receiving the node identifier, an NPN identifier corresponding to the requested information, the content requested to be reported, the reporting type, the reporting registration request, the reporting interval and the triggering event.

According to an embodiment of the present disclosure, the method performed by the second node in the wireless communication system further comprises: receiving third information comprising a request for NPN access requirement information of the user equipment UE from the first node before transmitting the at least one information to the first node, wherein the fourth information is transmitted to the first node by the second node based on the third information, wherein the third information comprises one or more of: the method comprises the steps of sending node identification, receiving node identification, UE identification, reporting a registration request and requesting the reported NPN access demand content.

According to an embodiment of the present disclosure, the method performed by the second node in the wireless communication system further comprises: receiving fifth information from the first node comprising a request for neighbor cell NPN support capability information of the second node and/or third node and/or additional NPN support capability information of the second node and/or third node before transmitting the at least one information to the first node, wherein the sixth information is transmitted by the second node to the first node based on the fifth information, wherein the fifth information comprises one or more of: the method comprises the steps of sending a node identifier, receiving the node identifier, requesting to report the NPN supporting capability information of a neighboring cell and/or a neighboring node, requesting to report the identifier of the NPN corresponding to the information, requesting to report additional NPN supporting capability information, reporting a type, reporting a registration request, reporting a section and triggering an event.

According to an embodiment of the present disclosure, the method performed by the second node in the wireless communication system further comprises: receiving seventh information comprising a request for a resource status and/or load condition of an NPN associated with the second node and/or third node from the first node before sending the at least one information to the first node, and eighth information comprising a response to the request for a resource status and/or load condition of an NPN associated with the second node and/or third node to the first node, wherein the ninth information is sent to the first node by the second node based on the seventh information, wherein the seventh information comprises one or more of: transmitting a node identifier, receiving a node identifier, an NPN identifier, requested content, a reporting type, a reporting registration request, a reporting interval, a triggering event, and wherein the eighth information includes one or more of: the method comprises the steps of sending a node identifier, receiving the node identifier, reporting an NPN identifier corresponding to information, reporting content, not reporting the NPN identifier corresponding to the information, not reporting the content and requesting reasons of failure.

According to an embodiment of the present disclosure, the method performed by the second node in the wireless communication system further comprises: receiving, from the first node, eleventh information comprising a request for NPN information of NPN associated with the second node and/or a third node, prior to transmitting the at least one information to the first node, wherein the twelfth information is transmitted to the first node by the second node based on the eleventh information, wherein the eleventh information comprises one or more of: the method comprises the steps of a UE mark, a sending node mark, a receiving node mark, an NPN information request, an NPN report request, an NPN failure information request, an NPN mark corresponding to a report requested to be reported, an NPN mark corresponding to information requested to be reported, an indication of a report about to timeout and/or about to be discarded requested to be reported, an indication of information about to timeout and/or about to be discarded requested to be reported, a request for reporting a report corresponding to a specific time, a request for reporting information corresponding to a specific time, a request for reporting a report corresponding to a specific configuration, and a request for reporting information corresponding to a specific configuration.

According to an embodiment of the present disclosure, the method performed by the second node in the wireless communication system further comprises: before receiving, from the first node, eleventh information comprising a request for NPN information of an NPN associated with the second node and/or a third node, the tenth information indicating that NPN information of an NPN associated with the second node and/or the third node is available to the first node, wherein the eleventh information is transmitted to the second node by the first node based on the tenth information, wherein the tenth information comprises one or more of: the method comprises the steps of identifying a UE, sending a node identification, receiving the node identification, enabling NPN information, enabling NPN report, enabling NPN failure information, enabling NPN report, enabling NPN identification corresponding to the NPN report, NPN identification corresponding to the NPN failure report, NPN identification corresponding to the NPN information, NPN identification corresponding to the NPN failure information, an identification about to timeout and/or about to discard of the NPN report, an identification about to timeout and/or about to discard of the NPN failure report, an identification about to timeout and/or about to discard of the NPN information, a time corresponding to the NPN report, a time corresponding to the NPN failure information, a configuration corresponding to the NPN report, a configuration corresponding to the NPN failure report, a configuration corresponding to the NPN information and a configuration corresponding to the NPN failure information.

According to an embodiment of the present disclosure, the method performed by the second node in the wireless communication system further comprises: receiving thirteenth information including an NPN function activation request from the first node before transmitting the at least one information to the first node, wherein the fourteenth information is transmitted to the first node by the second node based on the thirteenth information, wherein the thirteenth information includes one or more of: the method comprises the steps of sending a node identifier, receiving the node identifier, activating a request identifier, an NPN identifier, requesting to activate a guiding function, requesting to activate a function accessed by a certificate acquired by a certificate holder, and requesting a reason for activation.

Figures 1 through 12B, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will appreciate that the principles of the present disclosure may be implemented in any suitably arranged system or device.

Fig. 1 is an exemplary system architecture 100 for System Architecture Evolution (SAE). A User Equipment (UE) 101 is a terminal device for receiving data. An evolved universal terrestrial radio access network (E-UTRAN) 102 is a radio access network including macro base stations (enodebs/nodebs) providing an access radio network interface for UEs. The Mobility Management Entity (MME) 103 is responsible for managing the UE's mobility context, session context and security information. Serving Gateway (SGW) 104 mainly provides the functions of the user plane, and MME 103 and SGW 104 may be in the same physical entity. The packet data network gateway (PGW) 105 is responsible for charging, lawful interception, etc. functions, and may also be in the same physical entity as the SGW 104. A Policy and Charging Rules Function (PCRF) 106 provides quality of service (QoS) policies and charging criteria. The general packet radio service support node (SGSN) 108 is a network node device in the Universal Mobile Telecommunications System (UMTS) that provides a route for the transmission of data. A Home Subscriber Server (HSS) 109 is a home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the service node, user security information, packet data context of the user equipment, etc.

Fig. 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of this disclosure.

A User Equipment (UE) 201 is a terminal device for receiving data. The next generation radio access network (NG-RAN) 202 is a radio access network including base stations (gnbs or enbs connected to a 5G core network 5GC, also called NG-gnbs) providing access radio network interfaces for UEs. An access control and mobility management function (AMF) 203 is responsible for managing the mobility context of the UE, and security information. The User Plane Function (UPF) 204 mainly provides the functions of the user plane. The session management function entity SMF205 is responsible for session management. The Data Network (DN) 206 contains services such as operators, access to the internet, and third party traffic, among others.

The entities and/or nodes described in this disclosure may include: a gNB, gNB centralized Unit (gNB-CU), gNB distribution Unit (gNB Distributed Unit, gNB-DU), gNB centralized Unit Control Plane (gNB CU-CP), gNB centralized Unit User Plane (gNB CU-UP), en-gNB, eNB, ng-eNB, UE, access and mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), mobility management entity (Mobility Management Entity, MME) and other network entities or network logic units.

The signal strength and/or signal quality described in this disclosure may be a received signal strength indication (Received Signal Strength Indicator, RSSI), a reference signal received power (Reference Signal Receiving Power, RSRP), a reference signal received quality (Reference Signal Receiving Quality, RSRQ), a signal to interference plus noise ratio (Signal to Interference plus Noise Ratio, SINR), and the like.

In the prior art, a node cannot acquire information related to guidance (on) of a neighboring node and/or information related to support for access by using a certificate acquired by a CH, so that a suitable handover target node cannot be selected for a UE to meet the requirement of the UE. The prior art also cannot provide NPN related information for network self-optimization, so that the problems of NPN related configuration and the like cannot be optimized.

Next, fig. 3 illustrates a flow chart of a method 300 performed by a first node in a wireless communication system according to an embodiment of the disclosure.

As shown in fig. 3, in step S301, a method 300 performed by a first node in a wireless communication system according to an embodiment of the present disclosure may include: the first node receives at least one of second information including non-public network NPN support capability information of the second node and/or third node, fourth information including NPN access requirement information of a user equipment UE, sixth information including neighbor cell NPN support capability information of the second node and/or third node and/or additional NPN support capability information of the second node and/or third node, ninth information including a resource status and/or load condition of an NPN associated with the second node and/or third node, twelfth information including NPN information of an NPN associated with the second node and/or third node, and fourteenth information including a NPN function activation result of the second node from the second node and/or third node. Additionally or alternatively, the method 300 may include: in step S302, the first node makes a network self-optimization decision based on the at least one information and/or sends the at least one information to other nodes. Herein, the third node may be at least one of any other nodes in the wireless communication system than the second node, which may obtain information associated therewith by any means. Further, the first node, second node, third node, and other nodes described herein may be any of the example nodes exemplified above or newly introduced nodes in the future, without limitation. In some embodiments, the at least one information may be determined by the second node itself, or may be received by the second node from another node. In some embodiments, the second node may or may not perform network self-optimization based on the at least one information.

Additionally or alternatively, the method 300 may further comprise: the first node sends first information comprising a request for non-public network NPN support capability information of the second node and/or the third node to the second node before receiving the at least one information from the second node. In some embodiments, the second information described above may be sent to the first node autonomously by the second node or based on the first information.

Additionally or alternatively, the method 300 may further comprise: the first node sends third information comprising a request for NPN access requirement information of the user equipment UE to the second node before receiving the at least one information from the second node. In some embodiments, the fourth information described above may be sent to the first node autonomously by the second node or based on the third information.

Additionally or alternatively, the method 300 may further comprise: before receiving the at least one piece of information from the second node, the first node transmits fifth information including a request for neighbor cell NPN support capability information of the second node and/or the third node and/or additional NPN support capability information of the second node and/or the third node to the second node. In some embodiments, the sixth information described above may be sent to the first node autonomously by the second node or based on the fifth information. The "additional NPN support capability" of a particular node described herein may refer to the capability of the particular node to provide NPN support functionality in other ways than directly utilizing its own NPN support capability, such as utilizing other nodes or NPN support capabilities of nodes other than the particular node, as will be described in detail below in connection with specific example fields.

Additionally or alternatively, the method 300 may further comprise: the first node, prior to receiving the at least one piece of information from the second node, sends seventh information to the second node comprising a request for a resource status and/or load condition of an NPN associated with the second node and/or the third node, and the first node receives eighth information from the second node comprising a response to the request for a resource status and/or load condition of an NPN associated with the second node and/or the third node. In some embodiments, the ninth information described above may be sent to the first node autonomously by the second node or based on the seventh information.

Additionally or alternatively, the method 300 may further comprise: the first node sends, to the second node, eleventh information comprising a request for NPN information of a NPN associated with the second node and/or the third node, before receiving the at least one information from the second node. In some embodiments, the twelfth information described above may be sent to the first node autonomously by the second node or based on the eleventh information.

Additionally or alternatively, the method 300 may further comprise: before sending the eleventh information to the second node, the first node receives tenth information from the second node indicating that NPN information associated with the second node and/or the third node is available. In some embodiments, the eleventh information described above may be sent to the second node autonomously by the first node or based on tenth information. Herein, the NPN associated with a particular node may refer to an NPN that may be accessed by the particular node or an NPN of which the particular node forms a part, or an NPN of which the particular node may acquire NPN information in any manner.

Fig. 4 illustrates a flow chart of a method 400 performed by a second node in a wireless communication system in accordance with an embodiment of the disclosure.

As shown in fig. 4, in step S401, a method 400 performed by a first node in a wireless communication system according to an embodiment of the present disclosure may include: the second node transmits to the first node second information including non-public network NPN support capability information of the second node and/or third node, fourth information including NPN access requirement information of the user equipment UE, sixth information including neighbor cell NPN support capability information of the second node and/or third node and/or additional NPN support capability information of the second node and/or third node, ninth information including a resource status and/or load condition of an NPN associated with the second node and/or third node, twelfth information including NPN information of an NPN associated with the second node and/or third node, and fourteenth information including a NPN function activation result of the second node. Herein, the third node may be at least one of any other nodes in the wireless communication system than the second node, which may obtain information associated therewith by any means. Further, the first node, second node, third node, and other nodes described herein may be any of the example nodes exemplified above or newly introduced nodes in the future, without limitation. In some embodiments, the at least one information may be determined by the second node itself, or may be received by the second node from another node. In some embodiments, the second node may or may not perform network self-optimization based on the at least one information.

Additionally or alternatively, the method 400 may further comprise: the second node receives, from the first node, first information comprising a request for non-public network NPN support capability information of the second node and/or the third node, before sending the at least one information to the first node. In some embodiments, the second information described above may be sent to the first node autonomously by the second node or based on the first information.

Additionally or alternatively, the method 400 may further comprise: the second node receives third information comprising a request for NPN access requirement information of the user equipment UE from the first node before sending the at least one information to the first node. In some embodiments, the fourth information described above may be sent to the first node autonomously by the second node or based on the third information.

Additionally or alternatively, the method 400 may further comprise: the second node receives fifth information from the first node comprising a request for neighbor cell NPN support capability information of the second node and/or third node and/or additional NPN support capability information of the second node and/or third node before sending the at least one information to the first node. In some embodiments, the sixth information described above may be sent to the first node autonomously by the second node or based on the fifth information. The "additional NPN support capability" of a particular node described herein may refer to the capability of the particular node to provide NPN support functionality in other ways than directly utilizing its own NPN support capability, such as utilizing other nodes or NPN support capabilities of nodes other than the particular node, as will be described in detail below in connection with specific example fields.

Additionally or alternatively, the method 400 may further comprise: the second node receives seventh information comprising a request for a resource status and/or load condition of an NPN associated with the second node and/or the third node from the first node before sending the at least one information to the first node, and the second node sends eighth information comprising a response to the request for a resource status and/or load condition of an NPN associated with the second node and/or the third node to the first node. In some embodiments, the ninth information described above may be sent to the first node autonomously by the second node or based on the seventh information.

Additionally or alternatively, the method 400 may further comprise: the second node receives, from the first node, eleventh information comprising a request for NPN information of NPN associated with the second node and/or the third node, before sending the at least one information to the first node. In some embodiments, the twelfth information described above may be sent to the first node autonomously by the second node or based on the eleventh information.

Additionally or alternatively, the method 400 may further comprise: prior to receiving, from the first node, eleventh information comprising a request for NPN information of an NPN associated with the second node and/or third node, the second node transmits tenth information indicating that NPN information of an NPN associated with the second node and/or third node is available to the first node. In some embodiments, the eleventh information described above may be sent to the second node autonomously by the first node or based on tenth information. Herein, the NPN associated with a particular node may refer to an NPN that may be accessed by the particular node or an NPN of which the particular node forms a part, or an NPN of which the particular node may acquire NPN information in any manner.

The various steps or operations included in the methods 300 and 400 according to embodiments of the present disclosure as described above may be performed individually or in any combination, collectively, and may be performed in any order, e.g., concurrently or in reverse order from that listed. In addition, the various steps or operations and various information described above will be further described below in connection with specific examples.

Methods performed by a first node and/or a second node in a wireless communication system according to embodiments of the present disclosure will be described in various aspects further in conjunction with specific examples. More generally, a method performed by a first node and/or a second node in a wireless communication system according to embodiments of the present disclosure may also be referred to as a method supporting non-public network self-optimization.

Example one

One example of the present disclosure proposes a method of supporting non-public network self-optimization, which may include: the first node sends first information containing an NPN supporting capability information request to the second node so as to request the second node to report the NPN supporting capability information, so that the first node can request to acquire the NPN supporting capability information (of the second node and/or the third node) of the second node, and the first node can perform self-optimization decision and/or update relevant configuration and the like based on the acquired NPN supporting capability information so as to improve network performance, such as ensuring the performance of a user after switching.

In some embodiments, the first information may be contained in one or more of: an Xn SETUP REQUEST (Xn SETUP REQUEST) message or an Xn SETUP reply (XN SETUP RESPONSE) message, which may be Xn; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or may be an F1 SETUP REQUEST (F1 SETUP REQUEST) message or an F1 SETUP RESPONSE (F1 SETUP RESPONSE) message or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU configuration update awareness (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update (GNB-CU CONFIGURATION UPDATE) message or a GNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-DU resource coordination REQUEST (GNB-DU RESOURCE COORDINATION REQUEST) message or a GNB-DU resource coordination RESPONSE (GNB-DU RESOURCE COORDINATION RESPONSE) message of F1; it may also be a GNB-CU-UP E1 SETUP REQUEST (GNB-CU-UP E1 SETUP REQUEST) message or a GNB-CU-UP E1 SETUP RESPONSE (GNB-CU-UP E1 SETUP RESPONSE) message or a GNB-CU-CP E1 SETUP REQUEST (GNB-CU-CP E1 SETUP REQUEST) message or a GNB-CU-CP E1 SETUP RESPONSE (GNB-CU-CP E1 SETUP RESPONSE) message or a GNB-CU-UP configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a GNB-CU-UP configuration update aware (GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-CP configuration update (GNB-CU-CP CONFIGURATION UPDATE) message or a GNB-CU-CP configuration update aware (GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE) message of E1; a resource status request (RESOURCE STATUS REQUEST) message of X2 or Xn or F1 or E1, or an EN-DC resource status request (EN-DC RESOURCE STATUS REQUEST) message of X2; an upstream RAN configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, which may also be NG, a downstream RAN configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message; but may also be an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the first information may include one or more of the following fields or related information:

transmitting node identity: an identification of the node that sent the first information.

Receiving node identity: an identification of a node that receives the first information.

NPN identity corresponding to the requested information: for identifying the NPN to which the requested information corresponds. May be one or more of the following: public Land mobile network (Public Land MobileNetwork, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, a combination of PLMN identity and NID, a combination of PLMN identity and CAG identity, and the like.

Requested report content: for identifying the content and/or list of content that needs to be reported. May include one or more of the following: a bootstrapping (bootstrapping) support identity, identity of access with CH-available credentials, group identity (Group IDs forNetwork selection, GINs) for network selection, capability of bootstrapping support, capability of access with CH-available credentials, bootstrapping support on, access with CH-available credentials on, etc. In one embodiment, a guidance support identifier is used to represent the NPN support guidance; the identifier that can be accessed by the certificate acquired by the CH is used for indicating whether the NPN supports the access by the certificate acquired by the CH; the capability of guidance support indicates whether the NPN has the capability of supporting guidance; the access of the certificate acquired by the CH indicates whether the NPN has the capability of accessing the certificate acquired by the CH; whether the boot support is turned on indicates whether the NPN has the boot support capability and the support function is turned on; whether access with a CH-available certificate is open indicates whether the support function is open in the case where the NPN has the capability to access with a CH-available certificate.

Reporting type: for indicating the type of reporting, for example, may include On-demand (On-

demand), single report, periodic report, event trigger, etc.

Report registration request: for indicating the start, end, new addition, etc. of the report.

Reporting interval: and the reporting time interval is used for representing periodic reporting.

Trigger event: for indicating an event that can trigger reporting, reporting is performed when the trigger event is satisfied, for example, NPN support capability information change, etc.

In some embodiments, the second node may send, to the first node, second information including NPN support capability information according to its own situation and/or according to the received first information including NPN support capability information request, so that the first node may obtain NPN support capability information (of the second node and/or of the third node), and the first node may make a self-optimization decision and/or update a relevant configuration based on the obtained NPN support capability information, so as to improve network performance, for example, ensure performance of a user after handover, and so on. In some embodiments, the first node selects, when making a handover decision for the UE, a node of the NPN that can support access by the UE as a handover target node.

In some implementations, the second information may be included in one or more of: an Xn SETUP REQUEST (Xn SETUP REQUEST) message or an Xn SETUP reply (XN SETUP RESPONSE) message, which may be Xn; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or may be an F1 SETUP REQUEST (F1 SETUP REQUEST) message or an F1 SETUP RESPONSE (F1 SETUP RESPONSE) message or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU configuration update awareness (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update (GNB-CU CONFIGURATION UPDATE) message or a GNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-DU resource coordination REQUEST (GNB-DU RESOURCE COORDINATION REQUEST) message or a GNB-DU resource coordination RESPONSE (GNB-DU RESOURCE COORDINATION RESPONSE) message of F1; it may also be a GNB-CU-UP E1 SETUP REQUEST (GNB-CU-UP E1 SETUP REQUEST) message or a GNB-CU-UP E1 SETUP RESPONSE (GNB-CU-UP E1 SETUP RESPONSE) message or a GNB-CU-CP E1 SETUP REQUEST (GNB-CU-CP E1 SETUP REQUEST) message or a GNB-CU-CP E1 SETUP RESPONSE (GNB-CU-CP E1 SETUP RESPONSE) message or a GNB-CU-UP configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a GNB-CU-UP configuration update aware (GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-CP configuration update (GNB-CU-CP CONFIGURATION UPDATE) message or a GNB-CU-CP configuration update aware (GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE) message of E1; a resource status request (RESOURCE STATUS REQUEST) message of X2 or Xn or F1 or E1, or an EN-DC resource status request (EN-DC RESOURCE STATUS REQUEST) message of X2; an upstream RAN configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, which may also be NG, a downstream RAN configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message; but may also be an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the second information may include one or more of the following fields or related information: transmitting node identity: an identification of the node that sent the second information.

Receiving node identity: an identification of a node that receives the second information.

NPN identification: for identifying the NPN to which the second information corresponds. May be one or more of the following

The following steps: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed AccessGroup, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

Guide (onboard) support identification: for indicating whether or not the NPN supports bootstrapping (Onboarding), and whether or not the bootstrapping (Onboarding) NPN allows registration in the cell for the purpose of bootstrapping (Onboarding). The field may be represented by a single bit, e.g., when the bit is 1, it indicates that the NPN supports booting (onboard), and when the bit is 0, it indicates that the NPN does not support booting (onboard); the NPN support guidance (onboard) may be indicated when the bit is 0, and the NPN support guidance (onboard) may be indicated when the bit is 1.

Identity of access with a certificate acquired by CH: for indicating whether the NPN supports access with the certificate acquired with the CH. The field may be represented by a single bit, for example, when the bit is 1, it indicates that the NPN supports access with the certificate acquired by the CH, and when the bit is 0, it indicates that the NPN does not support access with the certificate acquired by the CH; when the bit is 0, it may indicate that the NPN supports access with the CH acquired certificate, and when the bit is 1, it may indicate that the NPN does not support access with the CH acquired certificate.

Group identification (Group IDs for Network selection, GINs) for network selection:

and the list is used for indicating the GINs and/or the GINs corresponding to the guidance (on) access and/or the access by using the certificate acquired by the CH.

Capability of (indication of) guidance support: for indicating whether the NPN has support for booting

Whether or not to allow the ability to register in a cell for the purpose of bootstrapping (Onboarding). The field may be represented by a single bit, e.g., when the bit is 1, indicating that the NPN has the capability to support booting, and when the bit is 0, indicating that the NPN has the capability to not support booting; the NPN may be capable of supporting guidance when the bit is 0, and the NPN may be capable of not supporting guidance when the bit is 1.

Capability of access with CH-acquired credentials (indication): indicating whether the NPN has access to the certificate available for CH. The field may be represented by a single bit, for example, when the bit is 1, it indicates that the NPN has the capability of accessing with the certificate acquired by the CH, and when the bit is 0, it indicates that the NPN has no capability of accessing with the certificate acquired by the CH; when the bit is 0, it may indicate that the NPN has the capability of accessing the certificate acquired by the CH, and when the bit is 1, it may indicate that the NPN does not have the capability of accessing the certificate acquired by the CH.

Guide support (indication of) whether or not to turn on: for indicating whether the support function is turned on or not in the case where the NPN has the guidance support capability. The field may be represented by a single bit, e.g., when the bit is 1, it indicates that the NPN turns on the support function, and when the bit is 0, it indicates that the NPN does not turn on the support function; when the bit is 0, it may indicate that the NPN has turned on the support function, and when the bit is 1, it may indicate that the NPN has not turned on the support function. In one embodiment, if the load of the cell or the node is too heavy, the NPN may close the guidance support function to ensure that the user accessing the NPN or the NPN needs to access the NPN to obtain the service requirement of the NPN service user. In another embodiment, the bootstrapping support function may be turned off if the cell or the node wants to reduce power consumption to achieve the goal of saving energy.

An indication of whether access is open or not with a certificate acquired by the CH: for indicating whether the support function is enabled in case the NPN has access to the certificate available for CH. The field may be represented by a single bit, e.g., when the bit is 1, it indicates that the NPN turns on the support function, and when the bit is 0, it indicates that the NPN does not turn on the support function; when the bit is 0, it may indicate that the NPN has turned on the support function, and when the bit is 1, it may indicate that the NPN has not turned on the support function. In one embodiment, if the load of the cell or the node is too heavy, the NPN may close the support function to ensure that the user accessing the NPN or the NPN needs to access the NPN to obtain the service requirement of the NPN service user. In another embodiment, the support function may be turned off if the cell or the node wants to reduce power consumption to achieve the goal of saving energy.

Triggering events: for example, the event for triggering the report may be an NPN support capability information change.

Reasons for failure to report: the method is used for indicating the reason that the NPN supporting capability information cannot be reported. May include one or more of the following: no NPN support capability information, no NPN support, no SNPN support, no PNI-NPN support, etc.

Example two

One example of the present disclosure proposes a method of supporting non-public network self-optimization, which may include: the first node sends third information including a UE-related NPN access requirement information request (for example, a request for NPN access requirement information of a specific UE) to the second node, so as to request the second node to report the UE-related NPN access requirement information, so that the first node may request to acquire the UE-related NPN access requirement information (for example, the NPN access requirement information of the specific UE), and the first node may perform a self-optimization decision and/or update related configuration based on the acquired UE-related NPN access requirement information, so as to improve network performance, for example, ensure performance of a user after handover, and the like.

In some embodiments, the third information may be included in one or more of: an Xn SETUP REQUEST (Xn SETUP REQUEST) message or an Xn SETUP reply (XN SETUP RESPONSE) message, which may be Xn; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or may be an F1 SETUP REQUEST (F1 SETUP REQUEST) message or an F1 SETUP RESPONSE (F1 SETUP RESPONSE) message or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU configuration update awareness (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update (GNB-CU CONFIGURATION UPDATE) message or a GNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-DU resource coordination REQUEST (GNB-DU RESOURCE COORDINATION REQUEST) message or a GNB-DU resource coordination RESPONSE (GNB-DU RESOURCE COORDINATION RESPONSE) message of F1; it may also be a GNB-CU-UP E1 SETUP REQUEST (GNB-CU-UP E1 SETUP REQUEST) message or a GNB-CU-UP E1 SETUP RESPONSE (GNB-CU-UP E1 SETUP RESPONSE) message or a GNB-CU-CP E1 SETUP REQUEST (GNB-CU-CP E1 SETUP REQUEST) message or a GNB-CU-CP E1 SETUP RESPONSE (GNB-CU-CP E1 SETUP RESPONSE) message or a GNB-CU-UP configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a GNB-CU-UP configuration update aware (GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-CP configuration update (GNB-CU-CP CONFIGURATION UPDATE) message or a GNB-CU-CP configuration update aware (GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE) message of E1; a resource status request (RESOURCE STATUS REQUEST) message of X2 or Xn or F1 or E1, or an EN-DC resource status request (EN-DC RESOURCE STATUS REQUEST) message of X2; an upstream RAN configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, which may also be NG, a downstream RAN configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message; or may be a HANDOVER request aware (HANDOVER REQUEST ACKNOWLEDGE) message of X2 or Xn, or a get UE context request (RETRIEVE UE CONTEXT REQUEST) message, or a HANDOVER SUCCESS (HANDOVER SUCCESS) message; a second eNB addition request awareness (SENB ADDITION REQUEST ACKNOWLEDGE) message or a second gNB addition request awareness (SGNB ADDITION REQUEST ACKNOWLEDGE) message that may also be X2; an auxiliary node of Xn can also be added with a request awareness (S-NODE ADDITION REQUEST ACKNOWLEDGE) message; but may also be an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the third information may include one or more of the following fields or related information:

transmitting node identity: an identification of a node that sent the third information.

Receiving node identity: an identification of a node that receives the third information.

UE identity: and identifying the UE to which the requested NPN access requirement information belongs.

Requested reported NPN access requirement content:

an oNPN label: and the identifier is used for representing the corresponding NPN accessed by the UE. May be one or more of the following: the public land mobile network (Public Land Mobile Network,

PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, a combination of PLMN identity and NID, a combination of PLMN identity and CAG identity, etc.

Cause and/or access cause and/or registration cause: the cause of the UE to access and/or register NPN may be a cause of handover and/or a need for handover, may be a cause of adding a node and/or modifying a node and/or releasing a node, may be a cause of adding an auxiliary node and/or modifying an auxiliary node and/or releasing an auxiliary node, may be a cause of mobility decision, or the like. May include one or more of the following: bootstrapping (Onboarding), access using credentials acquired by CH, normal access, etc.

Whether or not to need and/or support onboard

Whether access purposes using a certificate acquired by a CH are needed and/or supported: indicating the purpose of the UE to access the NPN. May include one or more of the following: bootstrapping (Onboarding), access using credentials acquired by CH, normal access, etc.

Target NPN and/or desired NPN identity: representing the identity of the NPN network that the UE actually wants to access. May be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

Requirements of guidance (onboard): indicating whether the UE requests to access and/or register the NPN for the purpose of bootstrapping (Onboarding). This field may be represented by a single bit, for example, when the bit is 1, it indicates that access to the NPN for the purpose of bootstrapping (Onboarding) is requested, and when the bit is 0, it indicates that access to the NPN for the purpose of bootstrapping (Onboarding) is not requested; when the bit is 0, it may indicate that an access to the NPN for the purpose of guidance (on) is requested, and when the bit is 1, it may indicate that an access to the NPN for the purpose of guidance (on) is not requested.

Requirements for access using certificates acquired by CH: indicating whether the UE requests access using the certificate acquired by the CH. This field may be represented by a single bit, for example, when the bit is 1, it indicates that access is requested to be made with the CH-acquired certificate, and when the bit is 0, it indicates that access is not requested to be made with the CH-acquired certificate; if the bit is 0, it may indicate that access is requested to be performed by a certificate acquired by the CH, and if the bit is 1, it may indicate that access is not requested to be performed by a certificate acquired by the CH.

o accesses the corresponding GIN(s): GIN(s) and +/for representing network to which UE accesses

Or GIN(s) list.

In some embodiments, the second node may request, according to its own situation (autonomously) and/or according to the received NPN access requirement information, fourth information including UE-related NPN access requirement information to the first node, so that the first node may acquire UE-related NPN access requirement information, and the first node may perform a self-optimization decision and/or update related configuration based on the acquired UE-related NPN access requirement information, so as to improve network performance, for example, ensure performance of a user after handover, and so on. In some embodiments, the first node may carry (e.g., send) NPN access requirement information (e.g., NPN access requirement information of the UE) when making a handover request to the UE, and the target node accepts and/or rejects the handover request according to the NPN access requirement information, e.g., may accept the handover request when the target node may support the NPN access requirement; and when the target node cannot support the NPN access requirement, rejecting the switching request. It should be appreciated that the UE-related NPN access requirement information described herein may be NPN access requirement information of any UE that the second node and/or the third node can obtain.

In some implementations, the fourth information may be included in one or more of: an Xn SETUP REQUEST (Xn SETUP REQUEST) message or an Xn SETUP reply (XN SETUP RESPONSE) message, which may be Xn; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or may be an F1 SETUP REQUEST (F1 SETUP REQUEST) message or an F1 SETUP RESPONSE (F1 SETUP RESPONSE) message or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU configuration update awareness (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update (GNB-CU CONFIGURATION UPDATE) message or a GNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-DU resource coordination REQUEST (GNB-DU RESOURCE COORDINATION REQUEST) message or a GNB-DU resource coordination RESPONSE (GNB-DU RESOURCE COORDINATION RESPONSE) message of F1; it may also be a GNB-CU-UP E1 SETUP REQUEST (GNB-CU-UP E1 SETUP REQUEST) message or a GNB-CU-UP E1 SETUP RESPONSE (GNB-CU-UP E1 SETUP RESPONSE) message or a GNB-CU-CP E1 SETUP REQUEST (GNB-CU-CP E1 SETUP REQUEST) message or a GNB-CU-CP E1 SETUP RESPONSE (GNB-CU-CP E1 SETUP RESPONSE) message or a GNB-CU-UP configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a GNB-CU-UP configuration update aware (GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-CP configuration update (GNB-CU-CP CONFIGURATION UPDATE) message or a GNB-CU-CP configuration update aware (GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE) message of E1; a resource status request (RESOURCE STATUS REQUEST) message of X2 or Xn or F1 or E1, or an EN-DC resource status request (EN-DC RESOURCE STATUS REQUEST) message of X2; an upstream RAN configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, which may also be NG, a downstream RAN configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message; x2 or Xn HANDOVER REQUEST message or get UE context response (RETRIEVE UE CONTEXT RESPONSE) message or get UE context failure (RETRIEVE UE CONTEXT FAILURE) message; a second eNB addition request (SENB ADDITION REQUEST) message or a second gNB addition request (SGNB ADDITION REQUEST) message that may also be X2; or an Xn auxiliary node addition request (S-NODE ADDITION REQUEST) message; a bearer context setup request (BEARER CONTEXT SETUP REQUEST) message of E1; but may also be an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the fourth information may include one or more of the following fields or related information:

transmitting node identity: an identification of the node that sent the fourth information.

Receiving node identity: an identification of a node that receives the fourth information.

NPN label: and the identifier is used for indicating the NPN corresponding identifier which needs to be accessed by the UE. May be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

Whether or not booting (onboard) is required and/or supported

Guidance (onboard) request: indicating that the UE requests to access and/or register the NPN for the purpose of bootstrapping (Onboarding). This field may be represented by a single bit, for example, when the bit is 1, it indicates that access to the NPN for the purpose of bootstrapping (Onboarding) is requested, and when the bit is 0, it indicates that access to the NPN for the purpose of bootstrapping (Onboarding) is not requested; when the bit is 0, it may indicate that an access to the NPN for the purpose of guidance (on) is requested, and when the bit is 1, it may indicate that an access to the NPN for the purpose of guidance (on) is not requested. Access request is performed by using the certificate acquired by CH: indicating that the UE requests access using the credentials acquired by the CH. This field may be represented by a single bit, for example, when the bit is 1, it indicates that access is requested to be made with the CH-acquired certificate, and when the bit is 0, it indicates that access is not requested to be made with the CH-acquired certificate; if the bit is 0, it may indicate that access is requested to be performed by a certificate acquired by the CH, and if the bit is 1, it may indicate that access is not requested to be performed by a certificate acquired by the CH.

Access to the corresponding GIN(s): and the GIN(s) and/or the GIN(s) list corresponding to the network accessed by the UE are/is used for representing.

Reasons for failure to report: the method is used for indicating the reason that the NPN access requirement information of the UE cannot be reported. May include one or more of the following: the method comprises the steps of no UE related NPN access requirement information, UE not supporting NPN access, UE not supporting SNPN access, UE not supporting PNI-NPN access and the like.

Example three

One example of the present disclosure proposes a method of supporting non-public network self-optimization, which may include: the first node sends fifth information containing the adjacent cell NPN supporting capability information and/or additional NPN supporting capability information request to the second node so as to request the second node to report the adjacent cell NPN supporting capability information and/or additional NPN supporting capability information, so that the first node can request to acquire the adjacent cell NPN supporting capability information and/or additional NPN supporting capability information, and the first node can perform network selection and the like according to the received adjacent cell NPN supporting capability information and/or additional NPN supporting capability information, thereby reducing network selection errors, ensuring that the selected network cannot meet requirements and the like. The neighbor cell support capability information described herein may be neighbor cell NPN support capability information of the second node and/or the third node, and the additional NPN support capability information may be additional NPN support capability information of the second node and/or the third node.

In some embodiments, the fifth information may be included in one or more of: an Xn SETUP REQUEST (Xn SETUP REQUEST) message or an Xn SETUP reply (XN SETUP RESPONSE) message, which may be Xn; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or may be an F1 SETUP REQUEST (F1 SETUP REQUEST) message or an F1 SETUP RESPONSE (F1 SETUP RESPONSE) message or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU configuration update awareness (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update (GNB-CU CONFIGURATION UPDATE) message or a GNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-DU resource coordination REQUEST (GNB-DU RESOURCE COORDINATION REQUEST) message or a GNB-DU resource coordination RESPONSE (GNB-DU RESOURCE COORDINATION RESPONSE) message of F1; it may also be a GNB-CU-UP E1 SETUP REQUEST (GNB-CU-UP E1 SETUP REQUEST) message or a GNB-CU-UP E1 SETUP RESPONSE (GNB-CU-UP E1 SETUP RESPONSE) message or a GNB-CU-CP E1 SETUP REQUEST (GNB-CU-CP E1 SETUP REQUEST) message or a GNB-CU-CP E1 SETUP RESPONSE (GNB-CU-CP E1 SETUP RESPONSE) message or a GNB-CU-UP configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a GNB-CU-UP configuration update aware (GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-CP configuration update (GNB-CU-CP CONFIGURATION UPDATE) message or a GNB-CU-CP configuration update aware (GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE) message of E1; a resource status request (RESOURCE STATUS REQUEST) message of X2 or Xn or F1 or E1, or an EN-DC resource status request (EN-DC RESOURCE STATUS REQUEST) message of X2; an upstream RAN configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, which may also be NG, a downstream RAN configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message; but may also be an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the fifth information may include one or more of the following fields or related information:

transmitting node identity: an identification of a node that transmits the fifth information.

Receiving node identity: an identification of a node that receives the fifth information.

NPN support capability information of the neighbor cell and/or neighbor node requested to report:

o neighbor cell identity: the identity of the neighboring cell.

o adjacent node identification: the identity of the neighboring node.

NPN identification supported by o: for identifying NPN identities and/or lists of identities supported by neighboring cells and/or neighboring nodes. The identification may be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed AccessGroup, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

o-bootstrapping (onboard) supports identification: for indicating whether or not the NPN supports bootstrapping (Onboarding), and whether or not the bootstrapping (Onboarding) NPN allows registration in the cell for the purpose of bootstrapping (Onboarding).

o identity accessible with the certificate obtained by CH: for indicating whether NPN is supported or not

And accessing the certificate acquired by the CH.

NPN identification corresponding to the information requested to be reported: and the identifier and/or the identifier list are used for identifying the NPN corresponding to the information requested to be reported. The identification may be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

Additional NPN support capability information requested to be reported:

identification supported by o additional guidance (onboard): for indicating whether the node is available

Identification of guidance (onboard) support is provided by other means. Other ways may be to select other nodes to support the bootstrapping (Onboarding) function. In some embodiments, for example, other bootstrapping (onboard) supporting nodes may be selected as one of the nodes in the dual connection (e.g., may be a primary node and/or a secondary node, etc.) to make up the dual connection, thereby providing bootstrapping (onboard) support. In some embodiments, for example, the node may be accessed first, then a handoff may be performed from the node to other nodes supporting bootstrapping (Onboarding), thereby providing bootstrapping (Onboarding) support, and so on.

o additional identification of access support with CH acquired credentials: for indicating that the node is

Whether support for access with credentials acquired with the CH may be provided by other means. Other ways may be to select other nodes to support access with credentials acquired with the CH.

In some embodiments, for example, other nodes supporting access with CH-acquired credentials may be selected as one of the nodes in the dual connection (e.g., may be a primary node and/or a secondary node, etc.) to form the dual connection, thereby providing support for access with CH-acquired credentials. In some embodiments, for example, the node may be accessed first, then a handoff may be performed from the node to other nodes supporting access with the CH-acquired credentials, thereby providing support for access with the CH-acquired credentials, and so on.

o additionally supports corresponding group identities (Group IDs for Networkselection, GINs) for network selection: for indicating that additional support is provided, booting (OnBoard)

Accessing and/or using the certificate acquired by CH to access the corresponding GINs and/or GINs list. The additional support may be whether the node may support bootstrapping by other means

(onboard) access and/or access with CH-acquired credentials, for example, other ways may be to select other nodes as one of the nodes in the dual connection (e.g., may be a primary node and/or a secondary node, etc.) to form the dual connection, thereby providing a bootstrap

(onboard) access and/or support for access with credentials acquired by the CH. In some embodiments, for example, the node may be accessed first and then a handoff may be performed from the node to other nodes supporting bootstrapping (onboard) access and/or access with credentials acquired by the CH, thereby providing bootstrapping (onboard) access and/or the like

Or support for access with CH acquired credentials, etc.

demand), single report, periodic report, event trigger, etc.

Trigger event: the reporting unit is used for indicating an event which can trigger reporting, and reporting is performed when the triggering event is met, for example, the neighbor NPN supporting capability information is changed, the additional NPN supporting capability information is changed, and the like.

In some embodiments, the second node may send and/or broadcast sixth information including the neighboring cell NPN support capability information and/or additional NPN support capability information (e.g., of the second node and/or the third node) to the first node according to its own situation (autonomously) and/or based on the received neighboring cell NPN support capability information and/or additional NPN support capability information request, so that the first node may acquire the neighboring cell NPN support capability information and/or additional NPN support capability information, and the first node may perform network selection according to the received neighboring cell NPN support capability information and/or additional NPN support capability information, so as to reduce network selection errors, make the selected network unable to meet requirements, and so on. In some embodiments, the base station broadcasts NPN support capability information to the UE, and after receiving the broadcast information, the UE selects a cell that can support NPN access requirements associated with the UE for access.

In some embodiments, the sixth information may be included in one or more of: system information block (System Information Block, SIB) of RRC; an Xn SETUP REQUEST (Xn SETUP REQUEST) message or an Xn SETUP reply (XN SETUP RESPONSE) message, which may be Xn; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or may be an F1SETUP REQUEST (F1 SETUP REQUEST) message or an F1SETUP RESPONSE (F1 SETUP RESPONSE) message or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU configuration update awareness (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update (GNB-CU CONFIGURATION UPDATE) message or a GNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-DU resource coordination REQUEST (GNB-DU RESOURCE COORDINATION REQUEST) message or a GNB-DU resource coordination RESPONSE (GNB-DU RESOURCE COORDINATION RESPONSE) message of F1; it may also be a GNB-CU-UP E1 SETUP REQUEST (GNB-CU-UP E1 SETUP REQUEST) message or a GNB-CU-UP E1 SETUP RESPONSE (GNB-CU-UP E1 SETUP RESPONSE) message or a GNB-CU-CP E1 SETUP REQUEST (GNB-CU-CP E1 SETUP REQUEST) message or a GNB-CU-CP E1 SETUP RESPONSE (GNB-CU-CP E1 SETUP RESPONSE) message or a GNB-CU-UP configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a GNB-CU-UP configuration update aware (GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-CP configuration update (GNB-CU-CP CONFIGURATION UPDATE) message or a GNB-CU-CP configuration update aware (GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE) message of E1; a resource status request (RESOURCE STATUS REQUEST) message of X2 or Xn or F1 or E1, or an EN-DC resource status request (EN-DC RESOURCE STATUS REQUEST) message of X2; an upstream RAN configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, which may also be NG, a downstream RAN configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message; but may also be an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the sixth information may include one or more of the following fields or related information:

transmitting node identity: an identification of a node that transmitted the sixth information.

Receiving node identity: an identification of a node that receives the sixth information.

NPN support capability information of neighboring cells and/or neighboring nodes:

o neighbor cell identity: the identity of the neighboring cell.

o adjacent node identification: the identity of the neighboring node.

o-bootstrapping (onboard) supports identification: for indicating whether NPN supports booting

(on board) whether or not the bootstrapping (on board) NPN allows registration in the cell for bootstrapping (on board) purposes. The field may be represented by a single bit, e.g., when the bit is 1, it indicates that the NPN supports booting (onboard), and when the bit is 0, it indicates that the NPN does not support booting (onboard); the NPN support guidance (onboard) may be indicated when the bit is 0, and the NPN support guidance (onboard) may be indicated when the bit is 1.

o identity accessible with the certificate obtained by CH: for indicating whether the NPN supports access with the certificate acquired with the CH. The field may be represented by a single bit, for example, when the bit is 1, it indicates that the NPN supports access with the certificate acquired by the CH, and when the bit is 0, it indicates that the NPN does not support access with the certificate acquired by the CH; when the bit is 0, it may indicate that the NPN supports access with the CH acquired certificate, and when the bit is 1, it may indicate that the NPN does not support access with the CH acquired certificate.

NPN label: for identifying supported NPN identifications and/or identification lists. The identification may be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

Identification of additional guidance (onboard) support: an identification indicating whether the node may provide guidance (onboard) support in other ways. Other ways may be to select other nodes to support the bootstrapping (Onboarding) function. In some embodiments, for example, other bootstrapping (onboard) supporting nodes may be selected as one of the nodes in the dual connection (e.g., may be a primary node and/or a secondary node, etc.) to make up the dual connection, thereby providing bootstrapping (onboard) support. In some embodiments, for example, the node may be accessed first, then a handoff may be performed from the node to other nodes supporting bootstrapping (Onboarding), thereby providing bootstrapping (Onboarding) support, and so on. The field may be represented by a single bit, e.g., when the bit is 1, it may provide additional guidance (on) support, and when the bit is 0, it may not provide additional guidance (on) support; it may also be that the bit is 0, indicating that additional guidance (on) support is available, and the bit is 1, indicating that additional guidance (on) support is not available.

Identification of access support with additional credentials acquired by CH: for indicating whether the node may otherwise provide support for access with credentials acquired by the CH. Other ways may be to select other nodes to support access with credentials acquired with the CH. In some embodiments, for example, other nodes supporting access with CH-acquired credentials may be selected as one of the nodes in the dual connection (e.g., may be a primary node and/or a secondary node, etc.) to form the dual connection, thereby providing support for access with CH-acquired credentials. In some embodiments, for example, the node may be accessed first, then a handoff may be performed from the node to other nodes supporting access with the CH-acquired credentials, thereby providing support for access with the CH-acquired credentials, and so on. The field may be represented by a single bit, for example, when the bit is 1, it indicates that the additional CH-acquired certificate may be provided for access support, and when the bit is 0, it indicates that the additional CH-acquired certificate may not be provided for access support; if the bit is 0, it may indicate that the additional CH-acquired certificate is available for access support, and if the bit is 1, it may indicate that the additional CH-acquired certificate is not available for access support.

Additional support of corresponding group identities (Group IDs for Networkselection, GINs) for network selection: for indicating that additional support is provided, booting (OnBoard)

Accessing and/or using the certificate acquired by CH to access the corresponding GINs and/or GINs list. The additional support may be whether the node may support bootstrapping (onboard) access and/or access with credentials acquired by the CH by other means, e.g., by selecting other nodes as one of the dual connectivity nodes (e.g., may be a master node and/or a secondary node, etc.) to form a dual connectivity, thereby providing bootstrapping (onboard)

Access and/or support for access with credentials acquired by the CH. In some embodiments, for example, the node may be accessed first, then a handoff may be performed from the node to other nodes supporting bootstrapping (Onboarding) access and/or access with credentials acquired by the CH, thereby providing support for bootstrapping (Onboarding) access and/or access with credentials acquired by the CH, and so on.

Trigger event: for example, the event triggering the reporting may be a change in the NPN support capability information of the neighboring area and/or a change in the additional NPN support capability information.

By means of interaction of the additional NPN support information between the nodes, the problems that when neighbor cells cannot support NPNs which are needed to be accessed by the UE, the quality of a wireless link is poor due to mobility of the UE, but the node cannot switch the UE and/or other operations cause wireless link failure and the like can be avoided. Based on the additional NPN support information interacted between the nodes, the node may switch the UE to a cell (for example, cell a) that may provide the NPN service to be accessed through an indirect manner and/or the node, after the UE is switched to cell a, the node where cell a is located adds the cell and/or the node that support the NPN service to be accessed by the UE as an auxiliary node of the UE, so as to achieve that the UE may access the NPN service to be accessed, or the node where cell a is located performs subsequent switching on the UE, and switches to a cell that supports the NPN service to be accessed by the UE, so as to achieve that the UE may access the NPN service to be accessed.

Example four

One example of the present disclosure proposes a method of supporting non-public network self-optimization, which may include: the first node sends seventh information containing the NPN resource state and/or load condition request to the second node to request the second node to report the NPN resource state and/or load condition information to the first node so as to inspire the requested measurement, so that the first node can acquire the NPN resource state and/or load condition of the second node and/or other nodes to make self-optimization decisions for the first node to provide reference information. In some implementations, the resource status and/or load condition request of the NPN may be a request for a resource status and/or load condition of the NPN associated with the second node and/or a third node other than the second node.

The seventh information may be included in one or more of: a resource status request (RESOURCE STATUS REQUEST) message for X2 or Xn or F1 or E1; an EN-DC resource status request (EN-DC RESOURCE STATUS REQUEST) message of X2; or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the seventh information may include one or more of the following fields or related information:

transmitting node identity: an identification of a node that transmits the seventh information.

Receiving node identity: an identification of a node that receives the seventh information.

NPN identification: for representing the identity and/or list of identities of the NPN to which the requested information corresponds. The identification may be one or more of the following: public land mobile network (Public LandMobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

Requested content: and the parameter indicating module is used for indicating parameters to be reported and/or measurement targets to be reported. This field may also be named a reporting feature. Reporting parameters and/or measurement targets includes one or more of: NPN resource status and/or load information, transport network layer (TransportNetwork Layer (TNL)) capacity indication, radio resource status, integrated available capacity set, integrated available resource set, number of active user terminals, radio resource control (RadioResource Control (RRC)) connection count, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (Almost BlankSubframe (ABS)) status, reference signal received power (Reference Signal ReceivedPower (RSRP)) measurement report list, reference signal received quality (Reference Signal Receiving Quality (RSRQ)) measurement report, signal to interference plus noise ratio (Signal to Interference plus Noise Ratio (SINR)) measurement report, channel status information (Channel State Information (CSI)) report, cell report indication, channel occupancy (Channel Occupancy) time scale, energy Detection (Energy Detection) threshold, signal strength and/or signal quality, channel busy scale, scale for access with a pilot (onboard) as a purpose, scale for access with a CH acquired credential, energy consumption (Energy Comsumption), energy efficiency (Energy Efficiency), and whether a respective content parameter (jiter) is a single overload or not, whether a single overload or a special parameter is high or low, an overload, a single overload or a special parameter is indicated or a low overload, an overload, a single overload, or a special overload is assessed, or a low overload, or a special overload is indicated or a low overload, or a single overload is above. Where the jitter condition may be the variance or standard deviation of the parameters. The parameter may be a self-situation, a neighboring cell situation, a situation of another coexistence technique (for example, WLAN, bluetooth, etc.), a sum of a self-situation and a neighboring cell situation, or an average value of a self-situation and a neighboring cell situation. The parameters may be uplink, downlink, uplink and downlink. The requested content may be either a true value or a predicted value. Whether the load is too high and/or whether the load is too low may be an evaluation of the overall situation or may be a separate evaluation of the parameters described above. The parameter may be a load condition and/or a resource status of one or more NPN, a load condition and/or a resource status of an NPN accessed for guidance (onboard) among the one or more NPN, or a load condition and/or a resource status of an NPN accessed by a certificate acquired by a CH among the one or more NPN. The field may be represented in the form of a bitmap, each position of the bitmap corresponding to a measurement object, the bit indicating when reporting is required, indicating that the corresponding measurement object is required to be reported. NPN special resource cases include one or more of the following: a resource condition for supporting bootstrapping occupied, a resource condition for supporting access with a CH acquired credential, a proportion of resources for supporting bootstrapping, a proportion of resources for supporting access with a CH acquired credential, etc., wherein the resources and/or resource condition may be one or more of the above parameters.

Reporting type: the type of report may be represented, for example, by On-demand (On-demand), single report, periodic report, event trigger, etc.

Reporting a registration request: for indicating the start, end, new addition, etc. of the report.

Trigger event: for indicating an event that may trigger reporting, reporting may include, for example, one or more of the following when the triggering event is satisfied: the change of the resource state and/or the load condition of the NPN is larger than and/or equal to a certain threshold value, the load is overlarge, the predicted change of the resource state and/or the load condition of the NPN is larger than and/or equal to a certain threshold value, the predicted load is overlarge, and the like.

In some embodiments, the second node may send eighth information including a response to the request for the NPN resource status and/or load condition to the first node according to the request, for feeding back to the first node whether reporting is possible, e.g., all and/or part of the measurement targets may be successfully inspired, and/or all and/or part of the measurement targets may not be inspired.

In some embodiments, the eighth information may be included in one or more of: a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message for X2 or Xn or F1 or E1; or an EN-DC resource status response (EN-DC RESOURCE STATUS RESPONSE) message or an EN-DC resource status failure (EN-DC RESOURCE STATUS FAILURE) message of X2; or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the eighth information may include one or more of the following fields or related information:

transmitting node identity: an identification of a node that transmitted the eighth information.

Receiving node identity: an identification of a node that receives the eighth information.

NPN identification corresponding to the information which can be reported: and representing the NPN identifiers and/or the identifier lists corresponding to the resource states and/or the load conditions which can be reported. The identification may be one or more of the following:

public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

Content that can be reported: representing content and/or a list of content and/or measurement targets and/or a list of measurement targets that may be reported may include one or more of the following: NPN resource status and/or load information, transport network layer (Transport Network Layer (TNL)) capacity indication, radio resource status, integrated available capacity set, integrated available resource set, number of active user terminals, radio resource control (Radio Resource Control (RRC)) connection count, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (Almost Blank Subframe (ABS)) status, reference signal received power (Reference Signal Received Power (RSRP)) measurement report list, reference signal received quality (Reference Signal Receiving Quality (RSRQ)) measurement report, signal to interference plus noise ratio (Signal to Interference plus Noise Ratio (SINR)) measurement report, channel status information (Channel State Information (CSI)) report, cell report indication, channel occupancy (Channel Occupancy) time scale, energy Detection (Energy Detection) threshold, signal strength and/or signal quality, channel busy scale, scale for access with a pilot (onboard) as a purpose, scale for access with a CH acquired credential, energy consumption (Energy Comsumption), energy efficiency (Energy Efficiency), and whether a respective content parameter (jiter) is a single overload or not, a single overload or a low overload, a single overload, a special overload, a low overload, or a single overload, an overload, or a special overload, an above-state, or an evaluation, and the like. Where the jitter condition may be the variance or standard deviation of the parameters. The parameter may be a self-situation, a neighboring cell situation, a situation of another coexistence technique (for example, WLAN, bluetooth, etc.), a sum of a self-situation and a neighboring cell situation, or an average value of a self-situation and a neighboring cell situation. The parameters may be uplink, downlink, uplink and downlink. The reportable content can be a true value or a predicted value. Whether the load is too high and/or whether the load is too low may be an evaluation of the overall situation or may be a separate evaluation of the parameters described above. The parameter may be a load condition and/or a resource status of one or more NPN, a load condition and/or a resource status of an NPN accessed for guidance (onboard) among the one or more NPN, or a load condition and/or a resource status of an NPN accessed by a certificate acquired by a CH among the one or more NPN. The field may be represented in the form of a bitmap, each position of the bitmap corresponding to a measurement object, the bit indicating that the corresponding measurement object may be reported when it is possible to report. NPN special resource cases include one or more of the following: a resource condition for supporting bootstrapping occupied, a resource condition for supporting access with a CH acquired credential, a proportion of resources for supporting bootstrapping, a proportion of resources for supporting access with a CH acquired credential, etc., wherein the resources and/or resource condition may be one or more of the above parameters. NPN identification corresponding to unrepresentable information: and the NPN identifiers and/or the identifier list corresponding to the resource state and/or the load condition which cannot be reported are indicated. The identification may be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

The non-reportable content: representing non-reportable content and/or lists and/or measurement targets and/or measurement target lists may include one or more of the following: NPN resource status and/or load information, transport network layer (Transport Network Layer (TNL)) capacity indication, radio resource status, integrated available capacity set, integrated available resource set, number of active user terminals, radio resource control (Radio Resource Control (RRC)) connection count, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (Almost Blank Subframe (ABS)) status, reference signal received power (Reference Signal Received Power (RSRP)) measurement report list, reference signal received quality (Reference Signal Receiving Quality (RSRQ)) measurement report, signal to interference plus noise ratio (Signal to Interference plus Noise Ratio (SINR)) measurement report, channel status information (Channel State Information (CSI)) report, cell report indication, channel occupancy (Channel Occupancy) time scale, energy Detection (Energy Detection) threshold, signal strength and/or signal quality, channel busy scale, scale for access with a pilot (onboard) as a purpose, scale for access with a CH acquired credential, energy consumption (Energy Comsumption), energy efficiency (Energy Efficiency), and whether a Jitter (jter) is a single parameter or a single parameter, whether an overload or a single parameter is high or low, an overload, a single parameter or a single overload, a special parameter is assessed, a high or a low overload, or a single overload, or a low overload, or a special parameter. Where the jitter condition may be the variance or standard deviation of the parameters. The parameter may be a self-situation, a neighboring cell situation, a situation of another coexistence technique (for example, WLAN, bluetooth, etc.), a sum of a self-situation and a neighboring cell situation, or an average value of a self-situation and a neighboring cell situation. The parameters may be uplink, downlink, uplink and downlink. The non-reportable content may be a true value or a predicted value. Whether the load is too high and/or whether the load is too low may be an evaluation of the overall situation or may be a separate evaluation of the parameters described above. The parameter may be a load condition and/or a resource status of one or more NPN, a load condition and/or a resource status of an NPN accessed for guidance (onboard) among the one or more NPN, or a load condition and/or a resource status of an NPN accessed by a certificate acquired by a CH among the one or more NPN. The field may be represented in the form of a bitmap, each position of the bitmap corresponding to a measurement object, the bit indicating that the corresponding measurement object cannot be reported when it is not possible to report. NPN special resource cases include one or more of the following: a resource condition for supporting bootstrapping occupied, a resource condition for supporting access with a CH acquired credential, a proportion of resources for supporting bootstrapping, a proportion of resources for supporting access with a CH acquired credential, etc., wherein the resources and/or resource condition may be one or more of the above parameters.

Reason for: for indicating reasons for failure and/or non-reporting of requests, e.g. no NPN-corresponding resource status and/or load situation, no predictive power, no NPN-corresponding resource status and

and/or predictive capability of load conditions, etc.

In some embodiments, the second node may autonomously send the ninth information including the NPN resource status and/or load condition to the first node according to the NPN resource status and/or load condition request and/or due to the second node's own condition (e.g., the NPN resource status and/or load condition associated therewith is too high or too low) for the first node to obtain the NPN resource status and/or load condition of the second node and/or other nodes, so that the first node may obtain the reference information for the first node to make a self-optimization decision, e.g., apply the measure of reducing the overload.

In some embodiments, the ninth information may be included in one or more of: a resource status update (RESOURCE STATUS UPDATE) message, which may be X2 or Xn or F1 or E1; an EN-DC resource status update (EN-DC RESOURCE STATUS UPDATE) message for X2; gNB-DU status indication (GNB-DU STATUS INDICATION) message which may also be F1; gNB-CU-UP status indication (GNB-CU-UP STATUS INDICATION) message which may also be E1; or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the ninth information may include one or more of the following fields or related information:

transmitting node identity: an identification of a node that transmitted the ninth information.

Receiving node identification: an identification of a node that receives the ninth information.

Reporting NPN identification corresponding to the information: and representing the NPN identifier and/or the identifier list corresponding to the reported resource state and/or load condition. The identification may be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

Reporting the content: parameters for indicating the status of the resource and/or the load situation and/or the measurement results of the measurement targets. The parameters include one or more of the following: NPN resource status and/or load information, transport network layer (Transport Network Layer (TNL)) capacity indication, radio resource status, integrated available capacity set, integrated available resource set, number of active user terminals, radio resource control (Radio Resource Control (RRC)) connection count, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (Almost Blank Subframe (ABS)) status, reference signal received power (Reference Signal Received Power (RSRP)) measurement report list, reference signal received quality (Reference Signal Receiving Quality (RSRQ)) measurement report, signal to interference plus noise ratio (Signal to Interference plus Noise Ratio (SINR)) measurement report, channel status information (Channel State Information (CSI)) report, cell report indication, channel occupancy (Channel Occupancy) time scale, energy Detection (Energy Detection) threshold, signal strength and/or signal quality, channel busy scale, scale for access with a pilot (onboard) as a purpose, scale for access with a CH acquired credential, energy consumption (Energy Comsumption), energy efficiency (Energy Efficiency), and whether a respective content parameter (jitters) is a single overload or not, whether a single overload or not, a single overload or a low overload, a single overload, a special overload, a single overload, a low overload, a single overload, or a special overload, or a low overload, an above-overload, or a special overload, and/or a low overload, an above-state, an above-mentioned. Where the jitter condition may be the variance or standard deviation of the parameters. The parameter may be a self-situation, a neighboring cell situation, a situation of another coexistence technique (for example, WLAN, bluetooth, etc.), a sum of a self-situation and a neighboring cell situation, or an average value of a self-situation and a neighboring cell situation. The parameters may be uplink, downlink, uplink and downlink. The report content can be a true value or a predicted value. Whether the load is too high and/or whether the load is too low may be an evaluation of the overall situation or may be a separate evaluation of the parameters described above. The parameter may be a load condition and/or a resource status of one or more NPN, a load condition and/or a resource status of an NPN accessed for guidance (onboard) among the one or more NPN, or a load condition and/or a resource status of an NPN accessed by a certificate acquired by a CH among the one or more NPN. NPN special resource cases include one or more of the following: a resource condition for supporting bootstrapping occupied, a resource condition for supporting access with a CH acquired credential, a proportion of resources for supporting bootstrapping, a proportion of resources for supporting access with a CH acquired credential, etc., wherein the resources and/or resource condition may be one or more of the above parameters.

Trigger event: for example, the event used to indicate triggering the report may include one or more of the following: the change of the resource state and/or the load condition of the NPN is larger than and/or equal to a certain threshold value, the load is overlarge, the predicted change of the resource state and/or the load condition of the NPN is larger than and/or equal to a certain threshold value, the predicted load is overlarge, and the like.

Example five

One example of the present disclosure proposes a method of supporting non-public network self-optimization, which may include: the second node transmits tenth information containing information indicating that the NPN information is available to the first node to notify the first node that the second node stores the NPN information so that the first node can select whether the information needs to be acquired.

In some implementations, the tenth information can be included in one or more of: UE measurement available for RRC (UE-MeasurementsAvailable), RRC setup complete (rrcsetup complete), RRC reestablishment complete (RRCReestablishmentComplete), RRC reconfiguration complete (RRCReconfigurationComplete), RRC resume complete (rrcrescendcomple); or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the tenth information may include one or more of the following fields or related information:

UE identity: an identity of the UE associated with the available NPN information.

Transmitting node identity: an identification of a node that transmitted the tenth information.

Receiving node identification: an identification of a node that receives tenth information.

NPN information is available: indicating that NPN information is available, indicating that NPN information is available. The field may be represented by a single bit, where the bit is 1, indicating that NPN information is available, where the bit is 0, indicating that NPN information is not available, or where the bit is 0, indicating that NPN information is available, and where the bit is 1, indicating that NPN information is not available.

NPN reporting is available: indicating that an NPN report is available, indicating that an NPN report is available. The field may be represented by a single bit, when the bit is 1, indicating that the NPN report is available, when the bit is 0, indicating that the NPN report is not available, or when the bit is 0, indicating that the NPN report is available, and when the bit is 1, indicating that the NPN report is not available.

NPN failure information is available: and the NPN failure information is used for indicating that the NPN failure information is available, and the NPN failure information is available. The field may be represented by a single bit, where the bit is 1, indicates that NPN failure information is available, where the bit is 0, indicates that NPN failure information is not available, or where the bit is 0, indicates that NPN failure information is available, and where the bit is 1, indicates that NPN failure information is not available.

NPN failure reporting is available: indicating that an NPN failure report is available, indicating that an NPN failure report is available. The field may be represented by a single bit, where the bit is 1, indicates that an NPN failure report is available, where the bit is 0, indicates that an NPN failure report is not available, or where the bit is 0, indicates that an NPN failure report is available, and where the bit is 1, indicates that an NPN failure report is not available.

Reporting and/or NPN identification corresponding to information: for identifying the NPN to which the report and/or message corresponds. May be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc. The NPN information may be an NPN identifier corresponding to the NPN information availability, an NPN identifier corresponding to the NPN report availability, an NPN identifier corresponding to the NPN failure information availability, an NPN identifier corresponding to the NPN failure report availability, or the like. The identifier may be an NPN identifier corresponding to NPN information, an NPN identifier corresponding to NPN report, an NPN identifier corresponding to NPN failure information, an NPN identifier corresponding to NPN failure report, or the like. Wherein the report may be a connection establishment failure (Connection Establishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (Radio Link Failure, RLF) report, or a measurement report, other radio connection related report, an NPN-related report, as described above. Wherein the information may be NPN related information as described above. The receiving node of the information may select the requested report and/or information based on the information, and may avoid unnecessary reporting of the report and/or information. Reporting and/or information is about to timeout and/or about to discard identification: for indicating that the stored report and/or information is about to timeout and/or about to discard (discard), or for indicating that there is an about to timeout and/or about to discard report and/or information in the stored report and/or information. Wherein the report may be a connection establishment failure (Connection Establishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (Radio Link Failure, RLF) report, or a measurement report, other radio connection related report, an NPN-related report, as described above. Wherein the information may be NPN related information as described above. In one embodiment, this information is reported if the time at which the report was stored will reach the stored time threshold. The information may be used for the receiving node and/or entity of the information to know that the report and/or information is about to timeout and/or discard, to acquire the report and/or information before the timeout and/or discard, to avoid loss and Waste (Waste) of the report and/or information.

Reporting and/or time corresponding to the information: the report and/or information used to represent the report and/or information is for and/or recorded at one or more points in time and/or time periods. In one implementation, reporting and/or information the content occurs at one or more points in time and/or time periods. The report and/or information may be available report and/or information or may be a report and/or information that is about to timeout and/or discard. Wherein the report may be a connection establishment failure (Connection Establishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (Radio Link Failure, RLF) report, or a measurement report, other radio connection related report, an NPN-related report, as described above. Wherein the information may be NPN related information as described above. The receiving node of the information may select the requested report and/or information based on the information, and may avoid unnecessary reporting of the report and/or information.

Configuration of reporting and/or information correspondence: the report and/or information used to represent the report and/or information is for one or more configurations. In one implementation, reporting and/or information the content occurs in a configuration or configurations. In one implementation, the configuration may be represented by an index. The index may be mobile information (MobilityInformation). The report and/or information may be available report and/or information or may be a report and/or information that is about to timeout and/or discard. Wherein the report may be a connection establishment failure (Connection Establishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (Radio Link Failure, RLF) report, or a measurement report, other radio connection related report, an NPN-related report, as described above. Wherein the information may be NPN related information as described above. The receiving node of the information may select the requested report and/or information based on the information, and may avoid unnecessary reporting of the report and/or information.

In some embodiments, the first node may send eleventh information including an NPN information request to the second node according to a self-situation (autonomously) and/or according to information received indicating that NPN information is available, so as to request the second node to report NPN information, so that the first node may request to acquire NPN information and make a self-optimization decision.

The eleventh information may be included in one or more of: RRC user information request (ueinfo request); or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the eleventh information may include one or more of the following fields or related information:

UE identity: an identity of the UE associated with the requested NPN information.

Transmitting node identity: an identification of a node that transmits the eleventh information.

Receiving node identity: an identification of a node receiving the eleventh information.

NPN information request: for requesting NPN information and/or indicating whether NPN information needs to be reported. The field may be represented by a single bit, where the bit is 1, indicates that NPN information is requested and/or NPN information needs to be reported, where the bit is 0, indicates that NPN information is not requested and/or NPN information does not need to be reported, or where the bit is 0, indicates that NPN information and NPN information need to be requested

And/or the NPN information needs to be reported, and when the bit is 1, the NPN information is not required to be requested and/or the NPN information does not need to be reported.

NPN report request: for requesting an NPN report and/or indicating whether reporting of an NPN report is required. The field may be represented by a single bit, where the bit is 1, and when the bit is 0, it indicates that the NPN report is requested and/or the NPN report needs to be reported, or when the bit is 0, it indicates that the NPN report is requested and/or the NPN report needs to be reported, and when the bit is 1, it indicates that the NPN report is not requested and/or the NPN report does not need to be reported.

NPN failure information request: the method is used for requesting NPN failure information and/or indicating whether the NPN failure information needs to be reported. The field may be represented by a single bit, where the bit is 1, and the bit is 0, and where the bit does not request NPN failure information and/or does not need to report NPN failure information, and where the bit is 0, and where the bit is 1, the bit does not request NPN failure information and/or does not need to report NPN failure information.

NPN failure report request: for requesting an NPN failure report and/or indicating whether reporting of an NPN failure report is required. The field may be represented by a single bit, where the bit is 1, and where the bit is 0, and where the bit is not 0, and where the bit is 1, and where the bit is not 0.

Request reporting report and/or NPN identification corresponding to information: for identifying the requested report and/or NPN to which the requested information corresponds. May be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc. The NPN identifier may be an NPN identifier corresponding to the NPN information request, an NPN identifier corresponding to the NPN report request, an NPN identifier corresponding to the NPN failure information request, an NPN identifier of the NPN failure report availability request, or the like. Wherein the report may be a connection establishment failure (Connection Establishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (Radio Link Failure, RLF) report, or a measurement report, other radio connection related report, an NPN-related report, as described above. Wherein the information may be NPN related information as described above. The information may be used for the node and/or entity receiving the information to report only a portion of the report and/or information (e.g., report the report and/or information corresponding to the NPN identification indicated by the request), not all of the stored report and/or information, interface resources may be saved, and unnecessary reporting of the report and/or information may be avoided.

An indication of a report and/or information that is about to timeout and/or about to discard is requested to be reported: reports and/or information indicating that the request is about to timeout and/or about to discard (discard). Wherein the report may be a connection establishment failure (Connection Establishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (Radio Link Failure, RLF) report, or a measurement report, other radio connection related report, an NPN-related report, as described above. Wherein the information may be NPN related information as described above. This information may be used for reporting reports and/or information that are about to timeout and/or discard by the receiving node and/or entity of the information to avoid loss and Waste (Waste) of reports and/or information.

Request to report reports and/or information corresponding to a particular time (or specified time): for indicating that the requested report and/or information is a report and/or information directed to and/or recorded at a particular time (or a specified time). In one implementation, the request may include an indication requesting reporting of a report and/or information corresponding to a particular time (or specified time), and/or information related to the particular time (or specified time). The particular time (or specified time) may be some point in time and/or period of time. In one implementation, what is described in the requested report and/or information occurs at some point in time and/or time period or periods. The report and/or information may be available report and/or information or may be a report and/or information that is about to timeout and/or discard. Wherein the report may be a connection establishment failure (Connection Establishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (Radio Link Failure, RLF) report, or a measurement report, other radio connection related report, an NPN-related report, as described above. Wherein the information may be NPN related information as described above. The information may be used for nodes and/or entities receiving the information to report only a portion of the report and/or information (e.g., report and/or information corresponding to a particular time (or a specified time)), not all of the stored report and/or information, interface resources may be saved, and unnecessary reporting of reports and/or information may be avoided.

Request to report reports and/or information corresponding to a particular configuration (or specified configuration): the report and/or information used to indicate that the requested report and/or information is for a particular configuration (or a specified configuration, e.g., one or more configurations). In one implementation, the request may include an indication requesting reporting of reports and/or information corresponding to a particular configuration (or specified configuration), and/or information related to the particular configuration (or specified configuration). In one implementation, the requested reporting and/or information occurs in a configuration or configurations. In one implementation, the configuration may be represented by an index. The index may be movement information (Mobility Information). The report and/or information may be available report and/or information or may be a report and/or information that is about to timeout and/or discard. Wherein the report may be a connection establishment failure (ConnectionEstablishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (RadioLink Failure, RLF) report, or a measurement report, other radio connection related report, an NPN-related report, as described above. Wherein the information may be NPN related information as described above. The information may be used for nodes and/or entities receiving the information to report only a portion of the report and/or information (e.g., report reports and/or information corresponding to a particular configuration (or a specified configuration)) and not all of the stored report and/or information, interface resources may be conserved, and unnecessary reporting of reports and/or information may be avoided.

In some embodiments, the second node may send twelfth information containing NPN information to the first node in accordance with its own situation (autonomously) and/or in accordance with the NPN information request to provide reference information for the first node to make a self-optimizing decision.

In some implementations, the twelfth information may be included in one or more of: RRC user information response (ueinformation response), secondary cell group failure information (SCGFailureInformation), primary cell group failure information (MCGFailureInformation); a failure indication (FAILURE INDICATION) message for Xn, a HANDOVER REPORT (HANDOVER) message, an access and mobility indication (ACCESS AND MOBILITY INDICATION) message, a secondary node modification request (S-NODE MODIFICATION REQUEST) message, a secondary gNB modification request (SgNB MODIFICATION REQUEST) message, a secondary cell group failure information REPORT (SCG FAILURE INFORMATION REPORT) message, an RRC transfer (RRC TRANSFER) message; f1 access and mobility indication (ACCESS AND MOBILITY INDICATION) message; the uplink RAN configuration of NG forwards (UPLINK RAN CONFIGURATION TRANSFER) the message and the downlink RAN configuration forwards (DOWNLINK RAN CONFIGURATION TRANSFER) the message; or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message. This information may be included in a report, which may be a connection establishment failure (Connection Establishment Failure, CEF) report, or a Random Access (Random Access) report, or a successful handover (Successful Handover) report, or a radio connection failure (Radio Link Failure, RLF) report, or a measurement report, or other report related to the radio connection. The report may also be a new report, for example, one or more of the following: NPN failure reporting, NPN reporting, continuous NPN failure reporting, etc.

In some implementations, the twelfth information may include one or more of the following fields or related information:

UE identity: for identifying the UE performing NPN access.

Node identification: and the node identifier is used for identifying the node identifier corresponding to the NPN access of the UE.

Cell identity: and the cell identifier is used for identifying the cell identifier corresponding to the NPN access of the UE.

NPN identification: and the NPN is used for identifying the access of the UE. May be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

Time of access to report: and the time for reporting the NPN information when the UE performs NPN access is indicated. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time of access failure to reporting: and the time from the occurrence of the NPN access failure to the reporting of the NPN information is used for indicating. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time of access attempt to report: and the time from the attempt to access the NPN to the reporting of the NPN information is used for representing. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Time to switch to reporting: and the time for indicating the occurrence of switching to reporting of NPN information. The handover may include a handover from an NPN to an NPN, a handover from a normal cell to a normal cell, a handover from an NPN to a normal cell, a handover from a normal cell to an NPN, etc. In one implementation, this time may be used for self-optimization, such as the node and/or entity finding the relevant configuration, the node and/or entity may perform configuration updates on the relevant configuration, and so on.

Purpose and/or purpose of access and/or registration: the purpose of the UE to access and/or register NPN may be the purpose of handover, the purpose of adding a node and/or modifying a node and/or releasing a node, the purpose of adding a secondary node and/or modifying a secondary node and/or releasing a secondary node, the purpose of mobility decision, etc. May include one or more of the following: bootstrapping (Onboarding), access using credentials acquired by CH, normal access, etc. Access and/or registration of NPN: indicating how the UE accesses and/or registers the NPN. May include: bootstrapping (Onboarding), access using credentials acquired by CH, normal access, etc. The manner in which the UE accesses and/or registers the cell in which the radio link failure occurs may be represented, and the manner in which the UE accesses and/or registers the last connected cell may be represented. The normal access may also be a normal access. In one implementation, this information may be used for nodes and/or entities to analyze whether configuration is appropriate and/or to decide whether it is appropriate. For example, if the UE needs to access a desired NPN by bootstrapping, the cell for handover and/or access may only be selected among cells supporting UE bootstrapping and/or supporting UE access to the desired NPN. The field may include one or more of the following:

o whether to register and/or access NPN through bootstrapping

o whether to access and/or register an NPN for the purpose of directing access to other NPN

o whether to register and/or access NPN with CH acquired certificate

o is normal access

Reconnected NPN identity: and the NPN is used for identifying the re-access of the UE. May be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc. In one implementation, this information may be used for node and/or entity analysis of whether the target node and/or cell selection is appropriate, and/or whether the selection of the handover opportunity is appropriate, and/or analysis of the cause of the handover failure and/or radio link failure (e.g., premature handover, too late handover, handover to the wrong cell, handover error, unnecessary handover, handover ping-pong, etc.), and/or self-optimization of the handover and/or configuration update, etc.

Reconnection cell identity: an identity for identifying the NPN and/or cell to which the UE re-accesses. Wherein the NPN identification may be one or more of: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc. In one implementation, this information may be used for node and/or entity analysis of whether the target node and/or cell selection is appropriate, and/or whether the selection of the handover opportunity is appropriate, and/or analysis of the cause of the handover failure and/or radio link failure (e.g., premature handover, too late handover, handover to the wrong cell, handover error, unnecessary handover, handover ping-pong, etc.), and/or self-optimization of the handover and/or configuration update, etc.

An indication of whether to switch from NPN to normal cell: for indicating whether to switch from NPN to normal cell.

An indication of whether to switch from a normal cell to NPN: for indicating whether to switch from the normal cell to the NPN.

Group identification (Group IDs for Network selection, GINs) for network selection: and the list is used for indicating the GINs and/or the GINs corresponding to the guidance (on) access and/or the access by using the certificate acquired by the CH. In one implementation, this information is used by the node and/or entity to determine whether the selection of the target node and/or cell is appropriate and whether an update or self-optimization is required.

GINs of access cells: in one implementation, this information may be used for the node and/or entity to analyze whether mobility decisions are appropriate and/or update the formulation and/or configuration of mobility decisions, e.g., may analyze whether the selection of a target cell and/or cell is appropriate and whether an update or self-optimization is required.

GINs of neighbor cells: in one implementation, this information may be used for node and/or entity analysis mobility decisions as to whether they are appropriate and/or updating mobility decision making and/or configuration. For example, this information may be used by the node and/or entity to analyze whether the target node selection is appropriate and whether updating of decision making and/or configuration is required.

Target NPN and/or desired NPN identity: representing the identity of the NPN network that the UE actually wants to access. May be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed Access Group, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc. In one implementation, this information may be used for node and/or entity analysis mobility decisions as to whether they are appropriate and/or updating mobility decision making and/or configuration. For example, this information may be used for node and/or entity analysis target node and/or cell selection. In one implementation, the target node may only select among cells and/or nodes that support the user's acquisition of the target NPN and/or the desired NPN.

Network selection mode: may include one or more of the following: manual selection, automatic selection, etc. The reason is that: indicating the reason for the access and/or handover failure and/or the reason for the radio link failure and/or random access failure and/or failure to provide the required service. The reasons may include one or more of the following: the target cell and/or neighbor cell and/or one or more specific cells and/or serving cells do not support bootstrapping (onboard), the no-cell support bootstrapping, the target cell and/or neighbor cell and/or one or more specific cells and/or serving cells do not support access using credentials acquired by CH, the no-cell support access using credentials acquired by CH, the GIN of the target cell and/or neighbor cell and/or one or more specific cells and/or serving cells is different from the source cell and/or serving cell, the GIN of the no-cell is different from the source cell and/or serving cell, the GIN of the target cell and/or neighbor cell and/or one or more specific cells and/or serving cells does not support access to the target NPN and/or desired NPN identity the GIN of the cell-less support for accessing the target NPN and/or the desired NPN identity, the GIN of the target cell and/or the neighbor cell and/or the one or more specific cells and/or the serving cell does not support for accessing the target NPN and/or the desired NPN, the cell-less support for accessing the target NPN and/or the desired NPN, the target cell and/or the neighbor cell and/or the one or more specific cells and/or the serving cell cannot establish the NPN corresponding protocol data unit session (Protocol Data Unit Session), the cell-less can establish the NPN corresponding protocol data unit session, the target cell and/or the neighbor cell and/or the one or more specific cells and/or the serving cell cannot establish the NPN corresponding data radio bearer (Data Radio Bearer), the cell-less can establish the NPN corresponding data radio bearer, the target cell and/or neighbor cell and/or one or more specific cells and/or serving cells may not establish a NPN-corresponding quality of service flow (Quality of Service Flow), no cells may establish a NPN-corresponding quality of service flow, etc. In one implementation, the information may help the node and/or entity analyze the cause of the radio link failure, etc., for the node and/or entity to configure and/or make decision updates based on the analyzed cause. Events: representing an event that occurs, which may be an event that occurs at a point in time and/or within a period of time. The event may include one or more of the following: the target cell and/or neighbor cell and/or one or more specific cells and/or serving cells do not support bootstrapping (onboard), the target cell and/or neighbor cell and/or one or more specific cells and/or serving cells do not support access using credentials acquired by CH, the target cell and/or neighbor cell and/or one or more specific cells and/or serving cells have GIN different from the source cell and/or serving cell, the GIN of the non-cell is the same as the source cell and/or serving cell, the GIN of the target cell and/or neighbor cell and/or one or more specific cells and/or serving cells do not support access to the target NPN and/or desired NPN identity the GIN of the non-cell supports access to the target NPN and/or the desired NPN identity, the GIN of the target cell and/or the neighbor cell and/or the one or more specific cells and/or the serving cell does not support access to the target NPN and/or the desired NPN, the non-cell supports access to the target NPN and/or the desired NPN, the target cell and/or the neighbor cell and/or the one or more specific cells and/or the serving cell cannot establish the NPN corresponding protocol data unit session (Protocol Data Unit Session), the non-cell can establish the protocol data unit session of the NPN corresponding, the target cell and/or the neighbor cell and/or the one or more specific cells and/or the serving cell cannot establish the NPN corresponding data radio bearer (Data Radio Bearer), the non-cell can establish the NPN corresponding data radio bearer, the target cell and/or neighbor cell and/or one or more specific cells and/or serving cells cannot establish a NPN-corresponding quality of service flow (Quality of Service Flow), no cells establish a NPN-corresponding quality of service flow, etc. In one implementation, the information may help the node and/or entity analyze the cause of the radio link failure, etc., for the node and/or entity to configure and/or make decision updates based on the analyzed cause.

Signal strength and/or signal quality measurements: the signal strength and/or signal quality measurements may be measurements at a point in time and/or within a period of time, or may be measurements corresponding to the events and/or reasons described above.

In some embodiments, when the signal strength and/or signal quality measurement is greater than and/or equal to and/or less than a threshold value for one or more cells and/or neighbors, and/or the NPN access requirement is not met, e.g., no bootstrapping (onboard) is supported, no access with a certificate acquired by a CH is supported, GIN is different from the source cell and/or serving cell, GIN does not support access to a target NPN and/or desires NPN, an NPN-corresponding protocol data unit session cannot be established (Protocol Data Unit Session), an NPN-corresponding data radio bearer cannot be established (Data Radio Bearer), an NPN-corresponding quality of service flow cannot be established (Quality of Service Flow), etc., the node may not record the relevant NPN information. For example, if the user measures that the signal strength and/or the signal quality of the cell is greater than and/or equal to the threshold value, but the cell does not support the NPN access requirement of the node, the user does not record the cell information, so as to avoid misjudging the self-optimization decision error by the service node and/or other nodes, for example, the reason that the radio link of the user fails is that the neighbor cell does not support the NPN access requirement of the user and cannot perform handover, but not that the neighbor cell does not perform timely handover, so that the service node and/or other nodes do not need to update their handover decisions to avoid that unnecessary update affects the network performance.

In some embodiments, after the first node collects NPN information of the NPN of the second node (and/or the third node), the first node may make a self-optimization decision and/or update configuration, or the like, or the first node may send the collected NPN information to other nodes, and provide reference information for the other nodes to make the self-optimization decision and/or update configuration, or the like.

Example six

One example of the present disclosure proposes a method of supporting non-public network self-optimization, which may include: the first node sends thirteenth information containing a function activation request of the NPN to the second node to request the second node to activate some or all functions of the NPN. In some embodiments, for example, the second node informs the first node of the NPN function of the second node, for example, the first node may be informed by the second information, and the first node may request that the function not opened by the second node be opened in some cases. Some situations may be that the first node needs to switch the user to the second node, or that the first node needs to switch the user to the second node due to energy saving, or that the first node needs to switch part of the users to the second node due to load balancing. Therefore, energy conservation can be realized under the condition that the performance is satisfied, and the influence on the performance due to energy conservation is avoided.

In some embodiments, the thirteenth information may be included in one or more of: a cell activation request (CELL ACTIVATION REQUEST) message or cell activation response (CELL ACTIVATION RESPONSE) message or cell activation failure (CELL ACTIVATION FAILURE) message, which may be Xn; an Xn SETUP REQUEST (Xn SETUP REQUEST) message or an Xn SETUP reply (XN SETUP RESPONSE) message, which may be Xn; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or may be an F1SETUP REQUEST (F1 SETUP REQUEST) message or an F1SETUP RESPONSE (F1 SETUP RESPONSE) message or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU configuration update awareness (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update (GNB-CU CONFIGURATION UPDATE) message or a GNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-DU resource coordination REQUEST (GNB-DU RESOURCE COORDINATION REQUEST) message or a GNB-DU resource coordination RESPONSE (GNB-DU RESOURCE COORDINATION RESPONSE) message of F1; it may also be a GNB-CU-UP E1 SETUP REQUEST (GNB-CU-UP E1 SETUP REQUEST) message or a GNB-CU-UP E1 SETUP RESPONSE (GNB-CU-UP E1 SETUP RESPONSE) message or a GNB-CU-CP E1 SETUP REQUEST (GNB-CU-CP E1 SETUP REQUEST) message or a GNB-CU-CP E1 SETUP RESPONSE (GNB-CU-CP E1 SETUP RESPONSE) message or a GNB-CU-UP configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a GNB-CU-UP configuration update aware (GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-CP configuration update (GNB-CU-CP CONFIGURATION UPDATE) message or a GNB-CU-CP configuration update aware (GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE) message of E1; a resource status request (RESOURCE STATUS REQUEST) message of X2 or Xn or F1 or E1, or an EN-DC resource status request (EN-DC RESOURCE STATUS REQUEST) message of X2; an upstream RAN configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, which may also be NG, a downstream RAN configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message; but may also be an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the thirteenth message may include one or more of the following fields or related information:

transmitting node identity: an identification of the node that sent the thirteenth information.

Receiving node identity: an identification of a node receiving the thirteenth information.

Activation request identification: for identifying the request.

NPN identification: for identifying the NPN requested to be activated. May be one or more of the following:

Request activation guidance (onboard) function: for requesting activation of the boot function of the NPN,

registration in the cell for the purpose of bootstrapping (Onboarding) is allowed.

A function of requesting activation of access with a certificate acquired by the CH: the function for requesting activation of the NPN access with the CH-acquired certificate allows registration and/or access in the cell with the CH-acquired certificate.

The reason for the request activation: may include energy savings, excessive loads, etc.

In some embodiments, the second node may send the fourteenth information including the NPN function activation result (e.g., of the second node) to the first node according to the self situation and/or according to the thirteenth information including the received NPN function activation request, so as to inform the first node of the NPN function activation result in the second node.

In some implementations, the fourteenth information may be included in one or more of: a cell activation request (CELL ACTIVATION REQUEST) message or cell activation response (CELL ACTIVATION RESPONSE) message or cell activation failure (CELL ACTIVATION FAILURE) message, which may be Xn; an Xn SETUP REQUEST (Xn SETUP REQUEST) message or an Xn SETUP reply (XN SETUP RESPONSE) message, which may be Xn; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or may be an F1SETUP REQUEST (F1 SETUP REQUEST) message or an F1SETUP RESPONSE (F1 SETUP RESPONSE) message or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU configuration update awareness (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update (GNB-CU CONFIGURATION UPDATE) message or a GNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-DU resource coordination REQUEST (GNB-DU RESOURCE COORDINATION REQUEST) message or a GNB-DU resource coordination RESPONSE (GNB-DU RESOURCE COORDINATION RESPONSE) message of F1; it may also be a GNB-CU-UP E1 SETUP REQUEST (GNB-CU-UP E1 SETUP REQUEST) message or a GNB-CU-UP E1 SETUP RESPONSE (GNB-CU-UP E1 SETUP RESPONSE) message or a GNB-CU-CP E1 SETUP REQUEST (GNB-CU-CP E1 SETUP REQUEST) message or a GNB-CU-CP E1 SETUP RESPONSE (GNB-CU-CP E1 SETUP RESPONSE) message or a GNB-CU-UP configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a GNB-CU-UP configuration update aware (GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-CP configuration update (GNB-CU-CP CONFIGURATION UPDATE) message or a GNB-CU-CP configuration update aware (GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE) message of E1; a resource status request (RESOURCE STATUS REQUEST) message of X2 or Xn or F1 or E1, or an EN-DC resource status request (EN-DC RESOURCE STATUS REQUEST) message of X2; an upstream RAN configuration forwarding (UPLINK RAN CONFIGURATION TRANSFER) message, which may also be NG, a downstream RAN configuration forwarding (DOWNLINK RAN CONFIGURATION TRANSFER) message; but may also be an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message.

In some implementations, the fourteenth message may include one or more of the following fields or related information:

transmitting node identity: an identification of a node that transmitted the fourteenth information.

Receiving node identity: an identification of a node that receives the fourteenth information.

Activation request identification: for identifying the request.

NPN identification of successful activation: an identification for identifying an NPN that was successfully activated. May be one or more of the following: public land mobile network (Public Land Mobile Network PLMN)

An identity, a network identity (Network Identifier, NID), a closed access group (ClosedAccess Group, CAG) identity, a combination of PLMN identity and NID, a combination of PLMN identity and CAG identity, etc.

NPN identification of activation of successful boot function: the NPN used to identify successful activation of the bootstrapping function indicates that registration in the cell for bootstrapping (Onboarding) purposes is allowed. May be one or more of the following: public land mobile network (Public Land Mobile Network PLMN)

Identity of NPN activating function accessed by certificate acquired by the functional CH: the NPN used to identify the function of activating successfully an access with a CH-acquired certificate indicates that registration and/or access with a CH-acquired certificate is allowed in the cell. May be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity, network identity (Network Identifier, NID), closed access group (Closed AccessGroup, CAG) identity, combination of PLMN identity and NID, combination of PLMN identity and CAG identity, etc.

Identification of successful activation of the boot (onboard) function: the bootstrapping function for identifying NPN is successfully activated, allowing registration in the cell for bootstrapping (Onboarding) purposes.

Identity of successful activation of the function of access with the certificate acquired by the CH: the function for identifying the access of the NPN with the certificate acquired by the CH is successfully activated, and the registration and/or the access in the cell are allowed by utilizing the certificate acquired by the CH.

Time of activation success: indicating the point in time and/or period of time at which activation was successful.

NPN identification of activation failure: an identification of the NPN for identifying the activation failure. May be one or more of the following: public land mobile network (Public Land Mobile Network PLMN)

NPN identification of activation failure boot function: an NPN for identifying a failed activation of the bootstrapping function indicates that registration in the cell for bootstrapping (Onboarding) purposes is not allowed. May be one or more of the following: public land mobile network (Public Land Mobile Network PLMN)

Identity of NPN activating function that failed access with certificate acquired by CH: the NPN, which is used to identify the function of activating failed CH-acquired credentials for access, indicates that registration and/or access with CH-acquired credentials in the cell is not allowed. May be one or more of the following: public land mobile network (Public Land Mobile Network, PLMN) identity,

Network identification (Network Identifier, NID), closed access group (Closed AccessGroup, CAG) identification, a combination of PLMN identification and NID, a combination of PLMN identification and CAG identification, etc.

Identification of failed boot (onboard) function activation: the bootstrapping function for identifying NPN fails to activate, allowing registration in the cell for bootstrapping (Onboarding) purposes.

Identity of functional activation failure with access to the certificate acquired by CH: the activation of the function for identifying the access of NPN with the CH acquired certificate fails, allowing registration and/or access in the cell with the CH acquired certificate.

Time of activation failure: indicating the point in time and/or period of time at which activation failed.

Reasons for activation success

Cause of activation failure: energy savings, unavailability of the function, non-support of the function, etc. may be included.

Methods performed by a first node and/or a second node in a wireless communication system according to embodiments of the present disclosure may be used for network self-optimization decisions. The network self-optimization decisions described in this disclosure may include at least one of network power saving, load balancing, coverage optimization, mobility optimization and/or management, network configuration formulation, and/or network configuration update, etc.

Further, results and reports in this disclosure may refer to each other.

The target NPN and/or the desired NPN in this disclosure may be identified as the NPN network that the UE actually wants to access. For example, in the case of bootstrapping (Onboarding) access, the NPN whose certificate (certificate) is intended to be acquired is the target NPN and/or the NPN identity is intended. For example, in the case where a certificate acquired by a Certificate Holder (CH) is used to access a network, an NPN actually intended to be accessed is a target NPN and/or a desired NPN identity.

In this disclosure, an access network may be used interchangeably with a registration network.

In the present disclosure, the cause may indicate the purpose, or the manner in which it is used.

In this disclosure, a field and/or information may be a measured value, a true value, a predicted value, a maximum value, a minimum value, an average value, a latest value, etc. of the information.

In this disclosure, open may refer to each other with activation, and unopened may refer to each other with deactivation and/or deactivation.

In this disclosure, a node and/or entity may also refer to a cell managed by the node and/or entity.

In the present disclosure, normal access and/or normal access means access without bootstrapping access, access without using a certificate acquired by CH, access without bootstrapping access, and the like. In one implementation, normal access and/or normal access means that access is performed using a certificate of the present NPN to obtain services of the present NPN network.

Further, in the present disclosure, time may be represented by one or more of the following: timestamp, point in time, time interval, timer, time period, length of time, period of time, interval of time, etc. Wherein the time length may be a time length from a point in time, which may be the current time. The time may be a relative time or an absolute time. In one implementation, the time period may be represented by a separate field, e.g., a combination of start time and end time, or a combination of start time and time period.

Exemplary embodiments of the present disclosure are further described below with reference to the accompanying drawings.

The text and drawings are provided as examples only to aid in the understanding of the present disclosure. They should not be construed as limiting the scope of the disclosure in any way. While certain embodiments and examples have been provided, it will be apparent to those of ordinary skill in the art from this disclosure that variations can be made to the embodiments and examples shown without departing from the scope of the disclosure.

Fig. 5A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 5A illustrates a process of interacting NPN support capability information between two nodes, so that a first node may obtain NPN support capability information and make a self-optimization decision and/or update configuration, etc. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 501A: the second node transmits NPN support capability information to the first node. The NPN support capability information may be the aforementioned second information.

Step 502A: the first node makes a self-optimizing decision and/or updates configuration, etc., based on the obtained NPN support capability information. In some embodiments, the first node selects, when making a handover decision for the UE, a node of the NPN that can support access by the UE as a handover target node.

Fig. 5B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 5B illustrates a process of interacting NPN support capability information between two nodes, so that a first node may obtain NPN support capability information and make a self-optimization decision and/or update configuration, etc. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 501B: the first node sends an NPN support capability information request to the second node. The NPN support capability information request may be the aforementioned first information.

Step 502B: the second node transmits NPN support capability information to the first node. The NPN support capability information may be the aforementioned second information.

Step 503B: the first node makes a self-optimizing decision and/or updates configuration, etc., based on the obtained NPN support capability information. In some embodiments, the first node selects, when making a handover decision for the UE, a node of the NPN that can support access by the UE as a handover target node.

Fig. 6A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 6A illustrates a process of interacting NPN access requirement information of a UE between two nodes, so that a first node may obtain the NPN access requirement information and make a self-optimization decision and/or update configuration. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 601A: the second node sends NPN access requirement information of the UE to the first node. The NPN access requirement information may be the fourth information described above.

Step 602A: the first node makes a self-optimizing decision and/or updates configuration and the like based on the acquired NPN access demand information. In some embodiments, the first node carries (e.g., sends) NPN access requirement information when making a handover request to the UE, and the target node accepts and/or rejects the handover request according to the NPN access requirement information, e.g., may accept the handover request when the target node may support the NPN access requirement; and when the target node cannot support the NPN access requirement, rejecting the switching request.

Fig. 6B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 6B illustrates a process of interacting NPN access requirement information of a UE between two nodes, so that a first node may obtain NPN access requirement information of the UE and make a self-optimization decision and/or update configuration. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 601B: the first node sends an NPN access requirement information request to the second node. The NPN access requirement information request may be the aforementioned third information.

Step 602B: the second node sends NPN access requirement information to the first node. The NPN access requirement information may be the fourth information described above.

Step 603B: the first node makes a self-optimizing decision and/or updates configuration and the like based on the acquired NPN access demand information. In some embodiments, the first node carries (e.g., sends) NPN access requirement information when making a handover request to the UE, and the target node accepts and/or rejects the handover request according to the NPN access requirement information, e.g., may accept the handover request when the target node may support the NPN access requirement; and when the target node cannot support the NPN access requirement, rejecting the switching request.

Fig. 6C illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 6C illustrates a process of interacting NPN access requirement information of a UE between two nodes, so that a first node may obtain NPN access requirement information of the UE and make a self-optimization decision and/or update configuration. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 601C: the second node sends NPN access requirement information to the first node. The NPN access requirement information may be the fourth information described above. The NPN access requirement information may be sent through a Handover Request (Handover Request) and/or a secondary node addition Request message.

Step 602C: the first node responds according to the NPN access requirement information and the self NPN supporting capability information. For example, the response may be that when the first node may support the NPN access requirement, a handover request and/or an auxiliary node addition request is accepted; and when the first node cannot support the NPN access requirement, rejecting the switching request and/or the auxiliary node adding request. The response may be sent via a handover request awareness (Handover Request Acknowledgement) and/or a secondary node addition request awareness (e.g., S-NODE ADDITION REQUEST ACKNOWLEDGE, SENB ADDITION REQUEST ACKNOWLEDGE, or SGNB ADDITION REQUEST ACKNOWLEDGE, etc.) and/or a handover preparation failure (HANDOVER PREPARATION FAILURE) and/or a secondary node addition request rejection (e.g., S-NODE ADDITION REQUEST REJECT, SENB ADDITION REQUEST REJECT, or SGNB ADDITION REQUEST REJECT, etc.) message.

Fig. 7A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 7A illustrates a process of interacting neighboring cell NPN support capability information and/or additional NPN support capability information between two nodes so that a first node may obtain the NPN support capability information and make a self-optimization decision and/or update configuration and/or select a cell, etc. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 701A: the second node transmits neighbor cell NPN support capability information and/or additional NPN support capability information of the second node (and/or third node) to the first node. The neighbor cell NPN support capability information and/or the additional NPN support capability information may be the aforementioned sixth information.

Step 702A: the first node makes a self-optimizing decision and/or updates a configuration and/or selects a cell or the like based on the acquired neighboring cell NPN support capability information and/or additional NPN support capability information. In some embodiments, for example, the first node is a UE and the second node is a base station, and after receiving the NPN support capability information and/or the additional NPN support capability information of the neighboring cell broadcast by the base station, the UE selects a cell that can support NPN access requirements of the UE for access.

Fig. 7B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure. In particular, fig. 7B illustrates a process of interacting neighboring cell NPN support capability information and/or additional NPN support capability information between two nodes so that a first node may obtain the NPN support capability information and make a self-optimization decision and/or update configuration and/or select a cell, etc. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 701B: the first node sends neighbor cell NPN support capability information and/or an additional NPN support capability information request to the second node. The neighbor cell NPN support capability information and/or the additional NPN support capability information request may be the fifth information described above.

Step 702B: the second node sends neighboring cell NPN support capability information and/or additional NPN support capability information to the first node. The neighbor cell NPN support capability information and/or the additional NPN support capability information may be the aforementioned sixth information.

Step 703B: the first node makes a self-optimizing decision and/or updates a configuration and/or selects a cell or the like based on the acquired neighboring cell NPN support capability information and/or additional NPN support capability information. In some embodiments, for example, the first node is a UE and the second node is a base station, and after receiving the NPN support capability information and/or the additional NPN support capability information of the neighboring cell broadcast by the base station, the UE selects a cell that can support NPN access requirements of the UE for access.

Fig. 7C illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 7C illustrates a process of interacting NPN support capability information with NPN support capability information of neighboring cells and/or additional NPN support capability information between nodes and between a node and a UE, so that the UE may acquire the NPN support capability information, select a suitable cell, and so on. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB, the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB, and the third node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB.

Step 701C: the second node transmits NPN support capability information of the second node to the first node. The NPN support capability information may be the aforementioned second information.

Step 702C: the third node transmits NPN support capability information of the third node to the first node. The NPN support capability information may be the aforementioned second information.

Step 703C: the first node formulates neighbor cell NPN support capability information and/or additional NPN support capability information based on the received NPN support capability information of the neighbor cell/node (e.g., second node, third node). The first node transmits NPN support capability information and/or neighboring cell NPN support capability information and/or additional NPN support capability information to the UE. The NPN support capability information may be the aforementioned second information. The neighbor cell NPN support capability information and/or the additional NPN support capability information may be the aforementioned sixth information.

Step 704C: and the UE selects a proper network for access. In some embodiments, after receiving the NPN support capability information and/or the NPN support capability information of the neighboring cell and/or the additional NPN support capability information, the UE selects a cell that can support an NPN access requirement of the UE for access.

Step 705C: and the UE transmits the NPN access requirement information to the first node. The NPN access requirement information may be the fourth information described above.

Step 706C: the first node makes a self-optimization decision according to the received NPN access requirement information of the UE, for example, other nodes are added as auxiliary nodes in dual connection, and the like. As one example, a first node sends a secondary node addition request message to a second node.

Fig. 8A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 8A illustrates a process of interacting a resource state and/or a load condition of an NPN between two nodes, so that a first node may obtain the resource state and/or the load condition of the NPN of a second node and/or other nodes to make a self-optimization decision for the first node to provide reference information.

In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 801A: the first node sends a resource status and/or load condition request of the NPN to the second node. The NPN resource status and/or load condition request may be the seventh information described above.

Step 802A: the second node sends a resource status and/or load condition request response of the NPN to the first node. The NPN resource status and/or load condition request response may be the eighth information described above.

Step 803A: the second node collects the resource status and/or load conditions of the NPN.

Step 804A: the second node transmits the NPN resource status and/or load condition to the first node. The NPN resource status and/or load condition may be the aforementioned ninth information.

Step 805A: the first node performs network self-optimization decision setting and/or forwards the network self-optimization decision setting to other nodes and the like based on the acquired NPN resource state and/or load condition.

If the request message in step 801A requires the second node to periodically report, steps 803A and 804A are periodically performed.

Fig. 8B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 8B illustrates a process of interacting a resource state and/or a load condition of an NPN between two nodes, so that a first node may obtain the resource state and/or the load condition of the NPN of a second node and/or other nodes to make a self-optimization decision for the first node to provide reference information.

Step 801B: the second node collects the resource status and/or load conditions of the NPN.

Step 802B: the second node transmits the NPN resource status and/or load condition to the first node. The NPN resource status and/or load condition may be the aforementioned ninth information.

Step 803B: the first node performs network self-optimization decision setting and/or forwards the network self-optimization decision setting to other nodes and the like based on the acquired NPN resource state and/or load condition.

Fig. 9A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 9A illustrates a process of interacting NPN information between two nodes, so that a first node may obtain NPN information and make self-optimization decisions and/or update configurations, etc. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 901A: the second node transmits NPN information to the first node. The NPN information may be the twelfth information described above.

Step 902A: the first node makes a self-optimizing decision and/or updates configuration, etc., based on the obtained NPN information.

Fig. 9B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization in accordance with an embodiment of the present disclosure. Specifically, fig. 9B illustrates a process of interacting NPN information between two nodes, so that a first node may obtain NPN information and make self-optimization decisions and/or update configurations, etc. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 901B: the first node sends an NPN information request to the second node. The NPN information request may be the aforementioned eleventh information.

Step 902B: the second node reports NPN information to the first node. The NPN information may be the twelfth information described above.

Step 903B: the first node makes a self-optimizing decision and/or updates configuration, etc., based on the obtained NPN information.

Fig. 9C illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 9C illustrates a process of interacting NPN information between two nodes, so that a first node may obtain NPN information and make self-optimization decisions and/or update configurations, etc. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 901C: the second node transmits information indicating that NPN information is available to the first node to inform the first node that the second node has NPN information. The information indicating that NPN information is available may be the aforementioned tenth information.

Step 902C: the first node sends an NPN information request to the second node. The NPN information request may be the aforementioned eleventh information.

Step 903C: the second node reports NPN information to the first node. The NPN information may be the twelfth information described above.

Step 904C: the first node makes a self-optimizing decision and/or updates configuration, etc., based on the obtained NPN information.

Fig. 9D illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 9D shows a process of interacting NPN information among a user, a node, and a last service node, so that the last service node may obtain NPN information, so that the last service node may perform configuration adjustment, make a self-optimization decision, and so on. As described above, the node may be a base station, which may include a Concentration Unit (CU) and a Distribution Unit (DU), and CU may further include a User Plane (UP) and a Control Plane (CP).

Step 901D: the UE performs an NPN access procedure with the last serving node (or may be the CU of the last serving node and/or the DU of the last serving node).

Step 902D: the UE performs RRC setup and/or re-establishment procedures with the node (or CU of the node).

Step 903D: the UE sends information indicating that NPN information is available to the node (or CU of the node) to inform the node (or CU of the node) that NPN information is present at the UE. The information indicating that NPN information is available may be the aforementioned tenth information. The information indicating that NPN information is available may be transmitted through an RRC setup complete (rrcsetup complete) message.

Step 904D: the node (or CU of the node) sends an NPN information request to the UE to request the UE to report NPN information. The NPN information request may be the aforementioned eleventh information. The NPN information request may be transmitted through a UE information request (ueinfo request) message.

Step 905D: the UE sends NPN information to the node (or CU of the node). The NPN information may be the twelfth information described above. The NPN information may be transmitted through a UE information response (ueinfo response) message.

Step 906D: the node (or CU of the node) sends NPN information to the last serving node (or CU of the last serving node). The NPN information may be the twelfth information described above. The NPN information may include all and/or part of the information in step 905D. The NPN information may be sent via a failure indication (Failure Indication) and/or a Handover Report (Handover Report) and/or an access and mobility indication (Access And Mobility Indication) message.

Step 907D: the CU of the last service node transmits NPN information to the last service node DU. The NPN information may be the twelfth information described above. The NPN information may include all and/or part of the information in step 906D. The NPN information may be sent via access and mobility indication (Access And Mobility Indication) messages.

The last service node (or a CU of the last service node, or a DU of the last service node) may make a self-optimizing decision and/or update a configuration based on the received NPN information.

Fig. 9E illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 9E shows a process of performing NPN access by the UE and the auxiliary node in the dual-connection case, where NPN information is interacted among the UE, the main node, and the auxiliary node, so that the auxiliary node may obtain NPN information, so that the auxiliary node may perform configuration adjustment, make a self-optimization decision, and so on.

Step 901E: the UE performs an NPN access procedure with the secondary node (or a CU of the secondary node and/or a DU of the secondary node).

Step 902E: the UE transmits NPN information to the master node (or CU of the master node). The NPN information may be the twelfth information described above. The NPN information may be transmitted through a SCG failure information (SCGFailureInformation) message.

Step 903E: the master node (or a CU of the master node) transmits NPN information to the slave node (or a CU of the slave node). The NPN information may be the twelfth information described above. The NPN information may include all and/or part of the information in step 902E. The NPN information may be sent via a secondary node modification request (SgNB Modification Request) and/or an SCG failure information report (SCG Failure Information Report) message.

Step 904E: the CU of the secondary node transmits NPN information to the DU of the secondary node. The NPN information may be the twelfth information described above. The NPN information may include all and/or part of the information in step 903E. The NPN information may be sent via access and mobility indication (Access And Mobility Indication) messages.

The master node (or a CU of the master node) and the slave node (or a CU of the slave node or a DU of the slave node) may make self-optimization decisions and/or update configurations based on the received NPN information.

Fig. 9F illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 9F shows a process of performing NPN access between the UE and the master node and interacting NPN information among the UE, the master node, and the slave node in the dual-connection case, so that the master node may obtain NPN information, so that the master node may perform configuration adjustment, make a self-optimization decision, and so on.

Step 901F: the UE performs an NPN access procedure with the master node (or CU of the master node).

Step 902F: the UE transmits NPN information to the secondary node (or a CU of the secondary node). The NPN information may be the twelfth information described above. The NPN information may be transmitted through a primary cell group (Master Cell Group) failure information (msgfailurenformation) message.

Step 903F: the secondary node (or a CU of the secondary node) sends NPN information to the primary node (or a CU of the primary node and/or a DU of the primary node). The NPN information may be the twelfth information described above. The NPN information may include all and/or part of the information in step 902F. The NPN information may be transmitted through an RRC Transfer (RRC Transfer) message.

Step 904F: the CU of the master node transmits NPN information to the DU of the master node. The NPN information may be the twelfth information described above. The NPN information may include all and/or part of the information in step 903F. The NPN information may be sent via access and mobility indication (Access And Mobility Indication) messages.

The master node (either a CU of the master node or a DU of the master node) may make self-optimization decisions and/or update configurations based on the received NPN information.

Fig. 9G illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 9G illustrates a process of interacting NPN information among a user, a node, a last service node, and an AMF, so that the last service node may obtain NPN information, so that the last service node may perform configuration adjustment, make a self-optimization decision, and so on.

Step 901G: the UE performs an NPN access procedure with the last serving node (or CU of the last serving node).

Step 902G: the UE performs RRC setup and/or re-establishment procedures with the node (or CU of the node).

Step 903G: the UE sends information indicating that NPN information is available to the node (or CU of the node) to inform the node (or CU of the node) that NPN information is present at the UE. The information indicating that NPN information is available may be the aforementioned tenth information. The information indicating that NPN information is available may be transmitted through an RRC setup complete (rrcsetup complete) message.

Step 904G: the node (or CU of the node) sends an NPN information request to the UE to request the UE to report NPN information. The NPN information request may be the aforementioned eleventh information. The NPN information request may be transmitted through a UE information request (ueinfo request) message.

Step 905G: the UE sends NPN information to the node (or CU of the node). The NPN information may be the twelfth information described above. The NPN information may be transmitted through a UE information response (ueinfo response) message.

Step 906G: the node (or CU of the node) sends NPN information to the AMF. The NPN information may be the twelfth information described above. The NPN information may include all and/or part of the information in step 905G. The NPN information may be sent via an uplink RAN configuration forwarding (Uplink RAN Configuration Transfer) message.

Step 907G: the AMF sends NPN information to the last serving node (or CU of the last serving node). The NPN information may be the twelfth information described above. The NPN information may include all and/or part of the information in step 906G. The NPN information may be sent via a downlink RAN configuration forwarding (Downlink RAN Configuration Transfer) message.

The CU of the last service node may also send all and/or part of the received NPN information to the DU of the last service node.

Finally, the serving node (or a CU of the secondary node or a DU of the secondary node) may make a self-optimizing decision and/or update the configuration based on the received NPN information.

Fig. 12A illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 12A illustrates a process of interacting an NPN activation result between two nodes, so that a first node may obtain NPN activation result information and make a self-optimization decision and/or update configuration, etc. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 1201A: the second node sends the NPN capability activation result to the first node. The NPN capability activation result may be the aforementioned fourteenth information.

Step 1202A: the first node makes a self-optimizing decision and/or updates configuration, etc., based on the obtained NPN capability activation result. In some embodiments, the first node selects, when making a handover decision for the UE, a node of the NPN that can support access by the UE as a handover target node.

Fig. 12B illustrates a schematic diagram of one aspect of a method of supporting non-public network self-optimization, in accordance with an embodiment of the present disclosure. Specifically, fig. 12B illustrates a process of interacting an NPN activation request and an activation result between two nodes, so that a first node may request a second node to activate an NPN function, obtain an NPN activation result of the second node, and make a self-optimization decision and/or update configuration. In some embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a UE. In other embodiments, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be an AMF or SMF or MME and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In further embodiments, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB and the second node may be an AMF or SMF or MME.

Step 1201B: the first node sends an NPN function activation request to the second node. The NPN function activation request may be the thirteenth information described above.

Step 1202B: the second node sends the NPN function activation result to the first node. The NPN function activation result may be the fourteenth information described above.

Step 1203B: the first node makes a self-optimizing decision and/or updates configuration, etc., based on the obtained NPN function activation result. In some embodiments, the first node selects, when making a handover decision for the UE, a node of the NPN that can support access by the UE as a handover target node.

In one embodiment, the steps shown in FIG. 12 may occur after the steps shown in FIG. 5A or FIG. 5B. The first node activates the NPN function of the second node using the steps of fig. 12 while knowing the function and/or on state of the second node through the steps of fig. 5A and/or 5B.

Next, fig. 10 shows a schematic diagram of a first node 1000 according to an embodiment of the disclosure.

As shown in fig. 10, a first node (or first node device) 1000 in accordance with an embodiment of the present disclosure may include a transceiver 1010 and a processor 1020. The transceiver 1010 may be configured to transmit and receive signals. The processor 1020 may be coupled with the transceiver 1010 and may be configured (e.g., to control the transceiver 1010) to perform a method performed by the first node according to an embodiment of the present disclosure.

Fig. 11 shows a schematic diagram of a second node 1100 according to an embodiment of the disclosure.

As shown in fig. 11, a second node (or second node device) 1100 according to embodiments of the present disclosure may include a transceiver 1110 and a processor 1120. Transceiver 1110 may be configured to transmit and receive signals. The processor 1120 may be coupled with the transceiver 1110 and may be configured (e.g., to control the transceiver 1110) to perform a method performed by the second node according to embodiments of the present disclosure. The processor may also be referred to as a controller.

Embodiments of the present disclosure also provide a computer readable medium having stored thereon computer readable instructions, which when executed by a processor may be used to implement any method according to embodiments of the present disclosure.

Various embodiments of the present disclosure may be implemented as computer readable code embodied on a computer readable recording medium from a particular perspective. The computer readable recording medium is any data storage device that can store data which can be read by a computer system. Examples of the computer readable recording medium may include a read-only memory (ROM), a random-access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, a carrier wave (e.g., data transmission via the internet), and so forth. The computer-readable recording medium can be distributed by a computer system connected via a network, and thus the computer-readable code can be stored and executed in a distributed manner. Moreover, functional programs, codes, and code segments for accomplishing the various embodiments of the present disclosure may be easily construed by one skilled in the art to which the embodiments of the present disclosure are applied.

It will be understood that embodiments of the present disclosure may be implemented in hardware, software, or a combination of hardware and software. The software may be stored as program instructions or computer readable code executable on a processor on a non-transitory computer readable medium. Examples of the non-transitory computer readable recording medium include magnetic storage media (e.g., ROM, floppy disks, hard disks, etc.) and optical recording media (e.g., CD-ROMs, digital Video Disks (DVDs), etc.). The non-transitory computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. The medium may be readable by a computer, stored in a memory, and executed by a processor. The various embodiments may be implemented by a computer or a portable terminal including a controller and a memory, and the memory may be an example of a non-transitory computer-readable recording medium adapted to store a program(s) having instructions to implement the embodiments of the present disclosure. The present disclosure may be implemented by a program having codes for embodying the apparatus and method described in the claims, the program being stored in a machine (or computer) readable storage medium. The program may be carried electronically on any medium, such as communication signals conveyed via a wired or wireless connection, and the disclosure suitably includes equivalents thereof.

The foregoing is merely a specific embodiment of the present disclosure, but the scope of the present disclosure is not limited thereto, and any person skilled in the art may make various changes or substitutions within the technical scope of the present disclosure, and such changes or substitutions are intended to be included in the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims

1. A method performed by a first node in a wireless communication system, comprising:

receiving, from a second node, at least one of second information including non-public network NPN support capability information of the second node and/or a third node, fourth information including NPN access requirement information of a user equipment UE, sixth information including neighbor cell NPN support capability information of the second node and/or a third node and/or additional NPN support capability information of the second node and/or a third node, ninth information including a resource status and/or a load condition of an NPN associated with the second node and/or a third node, twelfth information including NPN information of an NPN associated with the second node and/or a third node, and fourteenth information including a result of NPN function activation of the second node;

Making a network self-optimization decision based on the at least one information and/or sending the at least one information to other nodes;

wherein the third node is at least one of the other nodes in the wireless communication system than the second node.

2. The method of claim 1, further comprising, prior to receiving the at least one information from the second node:

transmitting first information comprising a request for non-public network NPN support capability information of the second node and/or a third node to the second node,

wherein the second information is sent by the second node to the first node based on the first information,

wherein the first information includes one or more of:

the method comprises the steps of sending a node identifier, receiving the node identifier, an NPN identifier corresponding to the requested information, the content requested to be reported, the reporting type, the reporting registration request, the reporting interval and the triggering event.

3. The method of claim 1, further comprising, prior to receiving the at least one information from the second node:

transmitting third information comprising a request for NPN access requirement information of the user equipment UE to the second node,

Wherein the fourth information is transmitted by the second node to the first node based on the third information,

wherein the third information includes one or more of:

the method comprises the steps of sending node identification, receiving node identification, UE identification, reporting a registration request and requesting the reported NPN access demand content.

4. The method of claim 1, further comprising, prior to receiving the at least one information from the second node:

transmitting fifth information comprising a request for neighbor cell NPN support capability information of the second node and/or third node and/or additional NPN support capability information of the second node and/or third node to the second node,

wherein the sixth information is transmitted by the second node to the first node based on the fifth information,

wherein the fifth information includes one or more of:

the method comprises the steps of sending a node identifier, receiving the node identifier, requesting to report the NPN supporting capability information of a neighboring cell and/or a neighboring node, requesting to report the identifier of the NPN corresponding to the information, requesting to report additional NPN supporting capability information, reporting a type, reporting a registration request, reporting a section and triggering an event.

5. The method of claim 1, further comprising, prior to receiving the at least one information from the second node:

transmitting seventh information including a request for a resource status and/or a load condition of an NPN associated with the second node and/or a third node to the second node, and

receive eighth information from the second node comprising a response to the request for a resource status and/or load condition of an NPN associated with the second node and/or a third node,

wherein the ninth information is transmitted by the second node to the first node based on the seventh information,

wherein the seventh information includes one or more of:

transmitting node identification, receiving node identification, NPN identification, requested content, reporting type, reporting registration request, reporting interval, triggering event, and

wherein the eighth information includes one or more of:

the method comprises the steps of sending a node identifier, receiving the node identifier, reporting an NPN identifier corresponding to information, reporting content, not reporting the NPN identifier corresponding to the information, not reporting the content and requesting reasons of failure.

6. The method of claim 1, further comprising, prior to receiving the at least one information from the second node:

Transmitting eleventh information comprising a request for NPN information of NPN associated with the second node and/or third node to the second node,

wherein the twelfth information is transmitted by the second node to the first node based on the eleventh information,

wherein the eleventh information includes one or more of:

the method comprises the steps of a UE mark, a sending node mark, a receiving node mark, an NPN information request, an NPN report request, an NPN failure information request, an NPN mark corresponding to a report requested to be reported, an NPN mark corresponding to information requested to be reported, an indication of a report about to timeout and/or about to be discarded requested to be reported, an indication of information about to timeout and/or about to be discarded requested to be reported, a request for reporting a report corresponding to a specific time, a request for reporting information corresponding to a specific time, a request for reporting a report corresponding to a specific configuration, and a request for reporting information corresponding to a specific configuration.

7. The method of claim 6, further comprising, prior to sending the eleventh information to the second node comprising a request for NPN information of NPN associated with the second node and/or a third node:

Tenth information indicating that NPN information associated with the second node and/or a third node is available is received from the second node,

wherein the eleventh information is transmitted by the first node to the second node based on the tenth information,

wherein the tenth information includes one or more of the following:

the method comprises the steps of identifying a UE, sending a node identification, receiving the node identification, enabling NPN information, enabling NPN report, enabling NPN failure information, enabling NPN report, enabling NPN identification corresponding to the NPN report, NPN identification corresponding to the NPN failure report, NPN identification corresponding to the NPN information, NPN identification corresponding to the NPN failure information, an identification about to timeout and/or about to discard of the NPN report, an identification about to timeout and/or about to discard of the NPN failure report, an identification about to timeout and/or about to discard of the NPN information, a time corresponding to the NPN report, a time corresponding to the NPN failure information, a configuration corresponding to the NPN report, a configuration corresponding to the NPN failure report, a configuration corresponding to the NPN information and a configuration corresponding to the NPN failure information.

8. The method according to claim 1,

wherein the network self-optimization decision comprises at least one of network energy saving, load balancing, coverage optimization, mobility optimization and/or management, network configuration formulation and/or network configuration update.

9. The method of claim 1, wherein the second information comprises one or more of:

the method comprises the steps of sending a node identifier, receiving the node identifier, an NPN identifier, a guide support identifier, an identifier for accessing a certificate acquired by a certificate holder, a group identifier for network selection, an indication of whether the NPN has the capability of guide support, an indication of whether the NPN has the capability of accessing the certificate acquired by the certificate holder, an indication of whether the guide support is opened, an indication of whether the certificate acquired by the certificate holder is opened, a triggering event and a reason that NPN support capability information cannot be reported.

10. The method of claim 1, wherein the fourth information comprises one or more of:

the method comprises the steps of sending a node identifier, receiving the node identifier, a UE identifier, an NPN identifier, a reason for accessing the NPN by the UE, whether guiding is needed, whether guiding is supported, whether accessing is needed by using a certificate acquired by a certificate holder, whether accessing is supported by using the certificate acquired by the certificate holder, the purpose of accessing the NPN by the UE, a guiding request, accessing request by using the certificate acquired by the certificate holder, a target NPN and/or an expected NPN identifier, a group identifier which corresponds to a network accessed by the UE and is used for network selection and/or a list of group identifiers used for network selection, and a reason that NPN access requirement information of the UE cannot be reported.

11. The method of claim 1, wherein the sixth information comprises one or more of:

the method comprises the steps of sending node identification, receiving node identification, neighbor cell and/or neighbor node NPN supporting capability information, supported NPN identification, additional guiding supporting identification, additional access supporting identification by using a certificate acquired by a certificate holder, additional supporting corresponding group identification for network selection and triggering event.

12. The method of claim 1, wherein the ninth information comprises one or more of:

the method comprises the steps of sending a node identifier, receiving the node identifier, reporting NPN identifier corresponding to the reported information, reporting content and triggering event.

13. The method of claim 1, wherein the twelfth information comprises one or more of:

the method comprises the steps of a UE identifier, a node identifier, a cell identifier, an NPN identifier, a time from access to reporting, a time from access failure to reporting, a time from access attempt to reporting, a time from switch to reporting, a reason for UE access to NPN, a purpose of UE access and/or registration of NPN, a mode of access and/or registration of NPN, a reconnection NPN identifier, a reconnection cell identifier, an indication of whether to switch from NPN to a common cell, an indication of whether to switch from a common cell to NPN, a group identifier for network selection of an access cell, a group identifier for network selection of a neighboring cell, a target NPN and/or an expected NPN identifier, a network selection mode, a reason for access and/or switch failure and/or a reason for service failure.

14. A method performed by a second node in a wireless communication system, comprising:

transmitting to a first node at least one of second information including non-public network NPN support capability information of the second node and/or third node, fourth information including NPN access requirement information of a user equipment UE, sixth information including neighbor cell NPN support capability information of the second node and/or third node and/or additional NPN support capability information of the second node and/or third node, ninth information including a resource status and/or load condition of an NPN associated with the second node and/or third node, twelfth information including NPN information of an NPN associated with the second node and/or third node, and fourteenth information including a result of NPN function activation of the second node,

15. A node apparatus in a wireless communication system, comprising:

a transceiver; and

a processor coupled with the transceiver and configured to perform the method of any of claims 1-14.