WO2023066392A1

WO2023066392A1 - Non-public network processing method and apparatus, device, and storage medium

Info

Publication number: WO2023066392A1
Application number: PCT/CN2022/126817
Authority: WO
Inventors: 王睿炜; 彦楠
Original assignee: 大唐移动通信设备有限公司
Priority date: 2021-10-22
Filing date: 2022-10-21
Publication date: 2023-04-27
Also published as: CN116017503A

Abstract

The present application provides a non-public network (NPN) processing method and apparatus, a device, and a storage medium. The method comprises: when determining that a terminal device fails, generating a failure-related report; and sending the failure-related report to a network device. In the present application, when failure occurs, the terminal device can record related information of a NPN in a failure-related report, so that when analyzing the cause of the failure, the network device can determine, on the basis of the related information of the NPN, whether different RRC connection re-establishment cells are caused by access restrictions of the NPN, so as to determine a proper handover target cell for handover of the terminal device in a public network and a NPN, thereby facilitating optimization of handover parameters, and improving the handover success rate of the terminal device.

Description

Non-public network processing method, device, equipment and storage medium

This disclosure is required to be submitted to the China Patent Office on October 22, 2021, the application number is 202111236258.8, and the application name is "non-public network optimization method, device, equipment, and storage medium" and it is submitted to the China Patent Office on July 28, 2022. The priority of the Chinese patent application No. 202210899882.4, titled "Non-public network processing method, device, equipment and storage medium", the entire content of which is incorporated in this disclosure by reference.

technical field

The present disclosure relates to the technical field of communications, and in particular, to a non-public network processing method, device, device, and storage medium.

Background technique

In the 5G communication system, the R16 version introduces a new type of network - non-public network (non-public network, NPN). In the existing technology, the network may be either a non-public network, a public network, or both. Both non-public and public networks are supported, and the terminal devices that access the network may be terminal devices that only support non-public networks, terminal devices that only support public networks, or terminal devices that support both public and non-public networks.

Different network configurations and terminal equipment capabilities may cause the terminal equipment to select a different RRC connection to re-establish a cell after a failure occurs. After a failure occurs, the terminal device records the failure information in the RLF report, handover failure report, handover success report, or random access report for the network to optimize network parameter configuration.

However, for a terminal device that supports a non-public network, the failure information recorded by the current terminal device does not contain information related to the non-public network. When the network device analyzes different RRC connections to re-establish a cell after a handover failure, it cannot accurately determine which RRC connection The re-established cell is the handover target cell that the terminal equipment should really select, which may lead to easy handover failure and reduce the handover success rate.

The above information disclosed in this Background section is only for enhancement of understanding of the background of the disclosure and therefore it may contain information that does not form the prior art that is already known in the art to a person of ordinary skill in the art.

Contents of the invention

The present disclosure provides a non-public network processing method, device, equipment and storage medium to solve the problems existing in the prior art.

In a first aspect, the present disclosure provides a method for processing a non-public network, which is applied to a terminal device, and the method includes:

When determining that the terminal device fails, generate a failure-related report, where the failure-related report includes non-public network-related information corresponding to the terminal device;

Sending a report related to the failure to a network device.

In some embodiments, the non-public network-related information includes the current access network information corresponding to the terminal device, access network restriction information, and network information for radio resource control RRC connection re-establishment or re-access after the terminal device fails one or more of.

In some embodiments, the current access network information includes the network type of the terminal device's current access network and the network identification information of the current access network; the network information of the RRC connection re-establishment or re-access Including the network type of RRC connection re-establishment or re-access;

Wherein, the network type includes any one of: an independently deployed non-public network SNPN, a public network integrated non-public network PNI-NPN, or a public network.

In some embodiments, the access network restriction information includes a network type of a network accessible to the terminal device and network identification information of the accessible network;

Wherein, the network type includes any one of SNPN network, PNI-NPN network or public network or a combination of at least two.

In some embodiments, if the network type is an SPN network, the network identification information includes a public land mobile network PLMN and a network identification code NID value.

In some embodiments, if the network type is a PNI-NPN network, the network identification information includes a PLMN and a closed access group CAG value.

In some embodiments, if the network type is an external authentication network, the network identification information includes a network selection group identity identification GIN value.

In some embodiments, determining that the terminal device has failed includes:

When the cell handover failure or radio link failure occurs on the terminal device, it is determined that the terminal device fails.

In some embodiments, the failure-related reports include any one or at least two of a radio link failure RLF report, a handover failure report, a handover success report, or a random access report.

In some embodiments, the method also includes:

sending an RRC connection re-establishment or re-access request message to the network device, the request message is used to trigger the network device to send a failure indication message between different network nodes, and the failure indication message is used to notify that a failure occurs network nodes to optimize network parameters.

In a second aspect, the present disclosure provides a method for processing a non-public network, which is applied to a network device, and the method includes:

receiving a failure-related report sent by the terminal device, where the failure-related report includes non-public network-related information corresponding to the terminal device;

A parameter optimization process is performed according to the non-public network-related information.

In some embodiments, the network device includes a plurality of network nodes; the method further includes:

When the first network node among the network nodes receives the radio resource control RRC connection re-establishment or re-access request message sent by the terminal device, and does not receive a failure-related report, the first network node Sending a failure indication message to the second network node where the failure occurred; wherein, the failure indication message is used to support the second network node to perform parameter optimization analysis, and the failure indication message includes the occurrence of RRC connection re-establishment or re-access A cell identity, the identity of the cell where RRC connection re-establishment or re-access occurs is a global cell identity.

In some embodiments, the method also includes:

When the failed second network node receives the failure indication message and determines that other network nodes need to perform parameter optimization analysis, it sends a handover report message to the other network nodes, and the handover report message is used to indicate to the other network nodes Nodes optimize network parameters;

Wherein, the handover report message includes the handover source cell identity, the target cell identity and the identity of the cell where RRC connection re-establishment or re-access occurs, and the identity of the cell where RRC connection re-establishment or re-access occurs is a global cell identity.

In a third aspect, the present disclosure provides a terminal device, including a memory, a transceiver, and a processor:

The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

Sending a report related to the failure to a network device.

In a fourth aspect, the present disclosure provides a network device, including a memory, a transceiver, and a processor:

In a fifth aspect, the present disclosure provides a non-public network processing device, which is applied to a terminal device, including:

A generating module, configured to generate a failure-related report when determining that a failure occurs in the terminal device, the failure-related report including non-public network-related information corresponding to the terminal device;

A sending module, configured to send the failure-related report to the network device.

In a sixth aspect, the present disclosure provides a non-public network processing device applied to network equipment, including:

A receiving module, configured to receive a failure-related report sent by the terminal device, where the failure-related report includes non-public network-related information corresponding to the terminal device;

An optimization module, configured to perform parameter optimization processing according to the non-public network related information.

In a seventh aspect, the present disclosure provides a processor-readable storage medium, where a computer program is stored in the processor-readable storage medium, and the computer program is used to enable the processor to execute the above non-public network processing method.

The non-public network processing method, device, device, and storage medium provided by the disclosure include: when determining that a terminal device fails, generating a failure-related report, the failure-related report includes non-public network-related information corresponding to the terminal device; sending failure-related Report to network device. In this disclosure, when a failure occurs, the terminal device can record the relevant information of the NPN network in reports such as the RLF report, the handover failure report, the handover success report, or the random access report, so that the network device can analyze the cause of the failure based on the NPN Relevant information of the network to determine whether different RRC connection re-establishment cells are caused by the access restrictions of the NPN network, so that the appropriate handover target cell can be determined for the handover of the terminal equipment under the public network and the non-public network, which is convenient for handover parameter optimization , so as to improve the handover success rate of the terminal equipment.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description serve to explain the principles of the disclosure.

FIG. 1 is a schematic diagram of a non-public network processing method applied to a terminal device provided by an embodiment of the present disclosure;

FIG. 2 is a schematic diagram of a non-public network processing method applied to a network device provided by an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of an application scenario of the technical solution of the present disclosure;

FIG. 4 is a schematic diagram of another application scenario of the technical solution of the present disclosure;

FIG. 5 is a schematic diagram of another application scenario of the technical solution of the present disclosure;

FIG. 6 is a schematic diagram of another application scenario of the technical solution of the present disclosure;

FIG. 7 is a schematic diagram of another application scenario of the technical solution of the present disclosure;

FIG. 8 is a flowchart of a handover report message in the technical solution of the present disclosure;

FIG. 9 is a schematic diagram of a terminal device provided by an embodiment of the present disclosure;

FIG. 10 is a schematic diagram of a network device provided by an embodiment of the present disclosure;

FIG. 11 is a schematic diagram of a non-public network processing device applied to a terminal device provided by an embodiment of the present disclosure;

FIG. 12 is a schematic diagram of a non-public network processing apparatus applied to a network device provided by an embodiment of the present disclosure.

By means of the above-mentioned drawings, certain embodiments of the present disclosure have been shown and will be described in more detail hereinafter. These drawings and written description are not intended to limit the scope of the disclosed concept in any way, but to illustrate the disclosed concept for those skilled in the art by referring to specific embodiments.

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments It is a part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of this application.

The terminology used in the embodiments of the present disclosure is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms "a" and "the" used in the embodiments of the present disclosure are also intended to include plural forms unless the context clearly indicates otherwise.

It should be understood that the term "and/or" used herein is only an association relationship describing associated objects, which means that there may be three relationships, for example, A and/or B, which may mean that A exists alone, and A and B exist simultaneously. B, there are three situations of B alone. In addition, the characters "three" in this paper generally indicate that the contextual objects are an "or" relationship.

Depending on the context, the words "if", "if" as used herein may be interpreted as "at" or "when" or "in response to determining" or "in response to detecting". Similarly, depending on the context, the phrases "if determined" or "if detected (the stated condition or event)" could be interpreted as "when determined" or "in response to the determination" or "when detected (the stated condition or event) )" or "in response to detection of (a stated condition or event)".

It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a good or system comprising a set of elements includes not only those elements but also includes items not expressly listed. other elements of the product, or elements inherent in the commodity or system. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the article or system comprising said element.

In the 5G communication system, a new type of network-non-public network (non-public network, NPN) is introduced. The typical application scenario of the NPN network is that it is used as a private network for only one private entity (such as an enterprise). Only authorized terminal devices are allowed to access the NPN network, while unauthorized terminal devices cannot access the NPN network.

The NPN network can be deployed in a variety of ways, for example, it can be deployed independently from the existing 5G public network, that is, the Stand-alone Non-Public Network (SNPN) can be deployed independently, or it can be deployed in the existing 5G network in a shared manner. On the 5G public network, that is, the public network integrated non-public network (Public network integrated NPN, PNI-NPN).

A network node can support public network and non-public network at the same time, for example, a cell of a certain base station can support any of public network, SNPN network, PNI-NPN network, or support public network, SNPN network, PNI-NPN network A combination of at least two of them, such as a public network and an SNPN network, can be supported at the same time.

Terminal equipment can access any one of public network, SNPN network, and PNI-NPN network according to capabilities and settings, or can access a combination of at least two of public network, SNPN network, and PNI-NPN network. Access to public networks and SNPN networks, etc.

Among them, the SNPN network is identified by the Identity document (ID) of the Public Land Mobile Network (PLMN) and the Network identifier (NID). A network node can support one or more combinations of PLMN ID and NID, and broadcast them in the system information broadcast.

For example, the network nodes of the SNPN network can support PLMN ID1+NID1, can also support PLMN ID2+NID2, and can also support PLMN ID3+NID3, etc.

The terminal equipment supporting the SNPN network will be configured with subscription information, and the subscription information includes the combination of PLMN and NID supported by the terminal equipment. If a terminal device supporting the SNPN network is set to SNPN mode, the terminal device can only access the SNPN network and cannot access the public network. When the terminal device accesses the network, it reads the broadcast information of the cell. If the combination of the PLMN ID and NID of the cell in the broadcast information is a combination supported by the terminal device, the terminal device can select the cell for access.

For example, the combination of the PLMN ID and NID of the cell of the SNPN network includes: PLMN ID1+NID1, PLMN ID2+NID2, PLMN ID3+NID3, wherein, PLMN ID2+NID2 is the combination supported by the terminal device, and the terminal device can access the district.

The PNI-NPN network is deployed based on the existing public network PLMN, and defines a method for access control of terminal devices - Closed Access Groups (CAG), CAG is used to allow only authorized terminal devices Access to PNI-NPN network, prevent unauthorized terminal equipment from accessing PNI-NPN network. Each CAG has an identifier (CAG ID) to distinguish it from other CAGs.

When a cell supports a PNI-NPN network, the cell corresponds to a combination of PLMN and one or more CAGs, and the combination of multiple CAGs supported by the cell forms a CAG list (Cell CAG list), which is used to indicate each CAG it supports. The CAG list is broadcast in the system information of the cell.

A terminal device supporting a PNI-NPN network can support a combination of one or more PLMNs and one or more CAGs, and each terminal device corresponds to an Allowed CAG list (Allowed CAG list), which is used to indicate which CAGs the terminal device can access . If the terminal device supporting PNI-NPN network is set to CAG-ONLY mode, the terminal device can only access the PNI-NPN network and cannot access the public network. When the terminal device accesses the network, it reads the broadcast information of the cell. If the CAG list of the cell in the broadcast information overlaps with the CAG allowed list of the terminal device, that is, the cell supports the CAG that the terminal device can access, the terminal device can select this cell for access.

For example, the CAG list of a cell includes CAG1, CAG2, CAG3, and CAG4, and the CAG allowed list of a terminal device includes CAG3, CAG4, and CAG8. If the above two lists include both CAG3 and CAG4, the terminal device can select this cell for access.

When the terminal device initially accesses, the network device will also judge the access legitimacy of the terminal device. The core network judges whether the terminal device can access the network according to the contract information of the terminal device. The network information is sent to the base station, and the network information includes the combination of PLMN and NID, the combination of PLMN and CAG supported by the terminal equipment, whether it supports access to the public network, etc.

When the terminal device performs handover, the network device will judge whether the target cell meets the non-public network access requirements of the terminal device, specifically:

1) When a terminal device accesses the SNPN network, the combination of PLMN and NID cannot be changed during handover, that is, the target cell must support this combination before it can be used as a target cell for candidate handover.

2) When a terminal device accesses a PNI-NPN network, if the terminal device only supports the PNI-NPN network, the CAG list supported by the access target cell and the CAG allowable list supported by the terminal device need to have an intersection; if the terminal device supports PNI at the same time - NPN network and public network PLMN, if the target cell can meet the PNI-NPN network access requirements or meet the public network access requirements, then the target cell can be used as a candidate target cell.

In addition, the 3rd Generation Partnership Project (3GPP) introduced an external authentication network in the R17 version, that is, the NPN network currently connected to the terminal device does not save user authentication information, and needs to use other external networks for authentication. User authentication. In this case, the system information broadcast on the current network does not include the PLMN, NID and CAG information supported by the user, and the user cannot access it under normal circumstances. In order to allow users to choose to access the network, GIN (Group ID for Network Selection) is introduced. Each cell may support the configuration of a group of GINs, and terminal devices are also pre-configured to support certain GINs. If the GINs supported by the cell and the terminal device’s If there is an intersection, the terminal device can access the network.

When a terminal device fails, the terminal device records a corresponding Radio Link Failure (RLF) report. The RLF report mainly covers two recording scenarios: handover failure and wireless link failure, and one RLF report can only represent the records of one scenario.

Among them, the RLF report contains the following content:

- Measurement results of one serving cell on the terminal device

- The terminal device confirms the neighbor cell measurement results after handover failure or radio link failure

- Terminal device location information

- Terminal device failure cell identification information, such as CGI (Cell Global Identity)/PCI (Physical Cell Identity) + frequency point

-The terminal device re-establishes the cell identification information

-Terminal device reporting timer: the time period from the last time the terminal device confirmed receiving the handover initiation message to the connection failure

- Reason for connection failure, handover failure or wireless link failure

- Cell Radio Network Temporary Identifier (C-RNTI) used when the terminal device fails to connect

- Sub-causes of wireless link failure, T310 timeout or random access problem or RLC layer reaches maximum retransmission or beam recovery failure (Beam Failure Recovery Failure, BFRF)

-The time elapsed after the terminal device confirms the connection failure until the terminal device reports the RLF report

-Tracking Area Code (TAC) of the failed cell

- Bluetooth (Blue Tooth, BT) related record results

-Wireless Local Area Network (WLAN)

After the terminal device records the RLF report, it notifies the network device to obtain it in the radio resource control (Radio Resource Control, RRC) connection establishment completion, RRC connection reconfiguration completion, RRC connection re-establishment completion or RRC recovery completion message. The network device sends a terminal device information request message to the terminal device, and the terminal device sends an RLF report to the network device through a terminal device information response message.

The Mobility Robustness Optimization (MRO) of network equipment is mainly used to solve the failure problem in the process of terminal equipment mobility, so as to assist in the network optimization of terminal equipment. In case of handover failure or RLF, the terminal device will record the RLF report. After the handover fails, the terminal device selects a cell, and then re-connects to the network through RRC connection re-establishment or RRC connection establishment, and notifies the network device that the RLF report is reserved in the terminal device, and the network device obtains it from the terminal device when needed for Network optimization for end devices.

The MRO feature is mainly used to discover and solve parameter configuration problems in the mobility process, and defines three failure types: handover too early, handover too late, and handover to the wrong cell.

(1) Handover is too late: After the terminal device has been stably staying in the source cell for a period of time, a radio link failure occurs, and the terminal device attempts to access a different cell through RRC connection re-establishment.

(2) Premature handover: During the handover process, the terminal equipment fails to access the target cell, or the terminal equipment successfully accesses the target cell but the radio link fails soon, and the terminal equipment re-establishes the RRC connection and tries to access the source cell.

(3) Handover to the wrong cell: During the handover process, the terminal equipment fails to access the target cell, or the terminal equipment successfully accesses the target cell but the radio link fails soon, and the terminal equipment re-establishes the RRC connection and tries to access a different cell than the handover target. cell and other cells of the source cell.

In addition to the RLF report, the terminal device also records other reports, such as a random access report and a handover success report. Wherein, the random access report includes relevant information about the successful random access of the terminal device. The handover success report is the information recorded by the terminal device during the handover process. Although the handover is successful, there may be some critical success or critical failure information. After the terminal device records, it assists the network in optimizing the handover parameters.

After the terminal device records the random access report or handover success report, the terminal device notifies the network device to obtain it in the RRC connection establishment completion, RRC connection reconfiguration completion, RRC connection re-establishment completion or RRC recovery completion message. The network device sends a terminal device information request message to the terminal device, and the terminal device sends a random access report and/or a handover success report to the network device through a terminal device information response message, so as to assist the network device in parameter optimization.

In the existing technology, the network may be either a non-public network or a public network, or support both a non-public network and a public network, and the terminal devices that access the network may be terminal devices that only support non-public The terminal equipment of the network, or the terminal equipment that supports public network and non-public network at the same time.

The technical solutions provided by the present disclosure aim to solve the above technical problems in the prior art.

The main concept of the disclosed solution is: when a failure occurs, the terminal device can record the relevant information of the NPN network in the RLF report, the handover failure report, the handover success report or the random access report, so that the network device can analyze the cause of the failure. Based on the relevant information of the NPN network, it can be determined whether the different RRC connection re-establishment cells are caused by the access restrictions of the NPN network, so that a suitable handover target cell can be determined for the handover of the terminal device under the public network and the non-public network, which is convenient Handover parameters are optimized to improve the handover success rate of the terminal equipment.

The technical solution of the present disclosure and how the technical solution of the present disclosure solves the above technical problems will be described in detail below with specific embodiments. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present disclosure will be described below with reference to the accompanying drawings.

It can be understood that the processing steps of the non-public network processing method in the present disclosure may be implemented by a terminal device or a network device.

Among them, the network equipment can be a base station, specifically, it can be a base station (Base Transceiver Station, BTS for short) in Global System of Mobile communication (GSM for short) or Code Division Multiple Access (CDMA for short), and / or a base station controller, and may also be a base station (NodeB, NB for short) and/or a radio network controller (Radio Network Controller, RNC for short) in Wideband Code Division Multiple Access (WCDMA for short), and It can be an evolved base station (Evolutional Node B, referred to as eNB or eNodeB) in Long Term Evolution (LTE for short), or a relay station or access point, or in a 5G network/other future networks (such as 6G network, etc.) The base station (gNB), etc., are not limited in this embodiment of the present disclosure.

The terminal equipment may be a wireless terminal equipment or a wired terminal equipment. The wireless terminal device may be a device that provides voice and/or other business data connectivity to the user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. Wireless terminal equipment can communicate with one or more core network equipment via a radio access network (Radio Access Network, referred to as RAN), and wireless terminal equipment can be mobile terminal equipment, such as mobile phones (or called "cellular" phones) and Computers with mobile terminals, which can be, for example, portable, pocket, hand-held, computer-integrated or vehicle-mounted mobile devices, exchange speech and/or data with the radio access network. For another example, the wireless terminal device may also be a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) Station, personal digital assistant (Personal Digital Assistant, referred to as PDA) and other equipment. Wireless terminal equipment can also be called system, subscriber unit (Subscriber Unit), subscriber station (Subscriber Station), mobile station (Mobile Station), mobile station (Mobile), remote station (Remote Station), remote terminal equipment (Remote Terminal) , Access Terminal, User Terminal, User Agent, and User Device or User Equipment are not limited here. Optionally, the above-mentioned terminal devices may also be devices such as smart watches and tablet computers.

In some embodiments, a non-public network processing method is provided, which is applied to a terminal device.

FIG. 1 is a schematic diagram of a non-public network processing method applied to a terminal device provided by an embodiment of the present disclosure. As shown in FIG. 1, the method mainly includes the following steps:

S110. When it is determined that the terminal device fails, generate a failure-related report, where the failure-related report includes non-public network-related information corresponding to the terminal device;

Specifically, when the terminal device determines that it has failed, it generates and records a corresponding failure-related report, the failure-related report includes non-public network-related information corresponding to the terminal device, and the non-public network-related information can be used to assist the network device to target The network parameter optimization processing of the terminal equipment is carried out systematically.

Optionally, when a cell handover failure or a radio link failure occurs on the terminal device, it is determined that the terminal device fails. The terminal device may determine whether a cell handover failure or a radio link failure occurs through an existing detection method, which will not be described in detail in this embodiment.

Optionally, the failure-related report includes any one or at least two of a radio link failure RLF report, a handover failure report, a handover success report, or a random access report. In addition, the failure-related reports may also be other reports that will be added in the future and are used to record information about terminal device failures.

S120. Send a failure-related report to the network device.

Wherein, the failure related report is used to instruct the network device to perform parameter optimization processing according to the non-public network related information.

After generating the failure-related report, the terminal device sends the failure-related report to the network device. Regarding the sending timing of the failure-related report, after the network device sends the terminal device information request message to the terminal device, the terminal device sends the failure-related report to the network device through the terminal device information response message. In addition, the terminal device can also be active Send a report about the failure to the network device.

Since the failure-related report includes non-public network-related information corresponding to the terminal device, the network device can perform parameter optimization processing according to the non-public network-related information to improve the handover success rate of the terminal device.

This embodiment provides a non-public network processing method. When a failure occurs, the terminal device can record the relevant information of the NPN network in a report such as an RLF report, a handover failure report, a handover success report, or a random access report, so that the network device is performing When analyzing the cause of the failure, it can be determined based on the relevant information of the NPN network whether the different RRC connection re-establishment cells are caused by the access restrictions of the NPN network, so that the appropriate handover can be determined for the handover of the terminal equipment under the public network and the non-public network The target cell is convenient for handover parameter optimization, thereby improving the handover success rate of the terminal equipment.

In some embodiments, the non-public network-related information includes one of the current access network information corresponding to the terminal device, access network restriction information, and network information for radio resource control RRC connection re-establishment or re-access after the terminal device fails. item or multiple items.

Wherein, the current access network information corresponds to the relevant information of the network that the terminal device accesses when the failure occurs; the access network restriction information corresponds to the relevant information of the network that the terminal device can access.

The non-public network-related information may include only the current access network information corresponding to the terminal device, or only include the access network restriction information corresponding to the terminal device, or include both the current access network information and the access network information corresponding to the terminal device. Incoming network restriction information.

In some embodiments, the current access network information includes the network type of the terminal device's current access network and the first network identification information corresponding to the current access network; the RRC connection re-establishment or re-access network information includes the RRC connection The type of network re-established or re-connected;

Wherein, the network type includes: any one of independent deployment non-public network SNPN, public network integrated non-public network PNI-NPN or public network, or a combination of at least two. In addition, the first network identification information is used to identify the current access network, and the first network identification information can definitely indicate the current access network corresponding to the terminal device.

In some embodiments, when the current access network includes an SNPN network, the first network identification information includes a combination of a public land mobile network PLMN of the current access network and a network identification code NID value.

Specifically, when the network currently accessed by the terminal device is a non-public network, and the non-public network type is specifically an SNPN network, since the SNPN network is identified by the combination of the PLMN ID and NID value, the corresponding The first network identification information includes the combination of the PLMN and the NID value of the currently accessed network. Optionally, the number of combinations of PLMN and NID values may be one or more.

In some embodiments, when the current access network includes a PNI-NPN network, the first network identification information includes a combination of a PLMN of the current access network and a closed access group CAG value.

Specifically, when the network currently accessed by the terminal device is a non-public network, and the type of the non-public network is specifically a PNI-NPN network, since the PNI-NPN network is identified by the combination of the ID of the PLMN and the CAG value, the currently connected The first network identification information corresponding to the access network includes a combination of the PLMN and the CAG value of the currently access network. Optionally, the number of combinations of PLMN and CAG values may be one or more.

In some embodiments, when the current access network is an external authentication network, the first network identification information further includes a network selection identifier GIN value of the current access network.

Specifically, when the network currently accessed by the terminal device is a non-public network, and the non-public network type is specifically any of the SNPN network or the PNI-NPN network, if the current access network is an external authentication network, then The NPN network that the terminal device is currently connected to does not store user authentication information, and needs to authenticate users through other external networks. Therefore, the first network identification information corresponding to the current access network includes the GIN value of the current access network. Optionally, the number of GIN values can be one or more.

In some embodiments, the access network restriction information includes the network type of the network that the terminal device can access and the second network identification information corresponding to the accessible network;

Wherein, the network type includes any one of SNPN network, PNI-NPN network or public network or a combination of at least two. In addition, the second network identification information is used to identify a network that the terminal device can access, and the second network identification information can definitely indicate an accessible network corresponding to the terminal device.

In some embodiments, when the accessible network includes an SNPN network, the second network identification information includes a combination of a PLMN and an NID value of the accessible network.

Specifically, when the network that the terminal device can access is a non-public network, and the non-public network type is specifically an SNPN network, since the SNPN network is identified by the combination of the ID and NID value of the PLMN, the corresponding The second network identification information includes a combination of a PLMN and an NID value of an accessible network. Optionally, the number of combinations of PLMN and NID values may be one or more.

In some embodiments, when the accessible network includes a PNI-NPN network, the second network identification information includes a combination of a PLMN and a CAG value of the accessible network.

Specifically, when the network that the terminal device can access is a non-public network, and the non-public network type is specifically a PNI-NPN network, since the PNI-NPN network is identified by the combination of the ID of the PLMN and the CAG value, it is possible to access The second network identification information corresponding to the incoming network includes a combination of the PLMN and the CAG value of the accessible network. Optionally, the number of combinations of PLMN and CAG values may be one or more.

In some embodiments, when the accessible network is an external authentication network, the second network identification information further includes a GIN value of the accessible network.

Specifically, when the network that the terminal device can access is a non-public network, and the non-public network type is specifically any of the SNPN network or the PNI-NPN network, if the accessible network is an external authentication network, then The NPN network that terminal devices can access does not store user authentication information, and needs to authenticate users through other external networks. Therefore, the second network identification information corresponding to the accessible network includes the GIN value of the accessible network. Optionally, the number of GIN values can be one or more.

In some embodiments, an RRC connection re-establishment or re-access request message is sent to the network device, the request message is used to trigger the network device to send a failure indication message between different network nodes, and the failure indication The message is used to notify the failed network node to optimize the network parameters.

In some embodiments, a non-public network processing method is provided, which is applied to a network device.

FIG. 2 is a schematic diagram of a non-public network processing method applied to a network device provided by an embodiment of the present disclosure. As shown in FIG. 2, the method mainly includes the following steps:

S210. Receive a failure-related report sent by the terminal device, where the failure-related report includes non-public network-related information corresponding to the terminal device;

Wherein, the failure-related report is generated by the terminal device when a failure occurs, and the failure-related report includes non-public network-related information corresponding to the terminal device, and the non-public network-related information can be used to assist the network device to carry out targeted Network parameter optimization processing.

S220. Execute parameter optimization processing according to the non-public network related information.

After receiving the failure-related report, the network device performs parameter optimization processing of the terminal device according to the non-public network-related information in the failure-related report, such as optimizing the relevant non-public network mobility parameters according to the non-public network type, etc., to Improve the handover success rate of terminal equipment.

In some embodiments, the current access network information includes the network type of the terminal device's current access network and the network identification information of the current access network;

In some embodiments, the method also includes:

If the network type corresponding to any one of the source cell identity, the target cell identity, and the RRC connection re-establishment or re-access cell identity is an independently deployed non-public network SNPN, the network identity information corresponding to the SNPN includes public land Mobile network PLMN and network identification code NID value;

If the network type corresponding to any one of the source cell ID, the target cell ID, and the RRC connection re-establishment or re-access cell ID is the public network integrated non-public network PNI-NPN, the network corresponding to the PNI-NPN Identification information includes PLMN and closed access group CAG value;

If the network type corresponding to any one of the source cell identity, the target cell identity, and the RRC connection re-establishment or re-access cell identity is an external authentication network, the network identity information corresponding to the external authentication network includes network Select the group identity GIN value.

It should be understood that although the steps in the flow charts in the above embodiments are shown sequentially as indicated by the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figure may include multiple sub-steps or multiple stages, these sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and the execution order is not necessarily sequential Instead, it may be performed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

In some embodiments, specific application examples of the technical solutions of the present disclosure are provided for different application scenarios.

Figure 3 is a schematic diagram of an application scenario of the technical solution of the present disclosure, which corresponds to the scenario of RRC connection re-establishment or re-access in case of handover failure, as shown in Figure 3, cell 0, cell 1 and cell 3 all support public network and Public network, cell 2 is a public network cell, that is, a non-public network is deployed based on the existing PLMN in the region below the dotted line in the figure. The moving direction of the terminal equipment UE is from cell 0 to cell 1, as shown by the arrow direction in the figure.

Assuming that the terminal equipment UE0 is a public network user, during the process of moving from cell 0 to cell 1, the target cell 1 is selected as the handover target cell. If the handover fails, the cell 2 is selected for RRC connection re-establishment or re-access. The terminal equipment UE0 records the failure-related report and sends it to the network equipment. After the network equipment conducts failure analysis based on the failure-related report, it finds that it is the wrong type of handover to the wrong cell, that is, the terminal equipment UE0 should select cell 2 as the target cell for handover.

Assuming that UE1 is a non-public network user, during the process of moving from cell 0 to cell 1, the target cell 1 is selected as the handover target cell. If the handover fails, cell 3 is selected for RRC connection re-establishment or re-access. The terminal equipment UE1 records the failure-related report and sends it to the network equipment. After the network equipment conducts failure analysis according to the failure-related report, it finds that it is the wrong type of handover to the wrong cell, that is, the terminal equipment UE1 should select cell 3 as the target cell for handover.

Based on the prior art, the current network equipment cannot determine whether the terminal equipment should select the target cell 2 or the target cell 3 as the target cell for handover. By analyzing the difference between cell 2 and cell 3, network devices can guess that cell 2 can only support public networks and cannot support non-public networks. However, it may also be caused by different trajectories of different terminal devices, or Network coverage and other reasons. Therefore, because there are many possible reasons, the network device cannot determine the specific reason, so targeted parameter optimization cannot be performed.

Based on the technical solution of the present disclosure, the terminal device may add current access network information and/or access network restriction information and/or RRC connection re-establishment or re-access network information corresponding to the terminal device in the failure related report.

Wherein, the current access network information includes the network type of the terminal device's current access network and the first network identification information corresponding to the current access network, and the RRC connection re-establishment or re-access network information includes RRC connection re-establishment or re-access The type of network accessed; the type of network currently accessed by the terminal device and the network type of RRC connection re-establishment or re-access include: SNPN network, public network or PNI-NPN network. When accessing the SNPN network, the first network identification information is the combination of the PLMN and NID value of the current access network; when accessing the PNI-NPN network, the first network identification information is the combination of the PLMN and the CAG value of the current access network combination. In addition, the access network restriction information includes the network type of the network that the terminal device can access and the second network identification information corresponding to the accessible network. The network type that the terminal device can access includes: SNPN network, public network or PNI-NPN network . When it is an accessible SNPN network, the second network identification information is a combination of the PLMN and NID value of the accessible network; when it is an accessible PNI-NPN network, the second network identification information is the PLMN of the accessible network and CAG value combination. Among them, the type of network where the UE undergoes RRC connection re-establishment or re-access, including: SNPN network, public network or PNI-NPN network; when accessing the SNPN network, it is necessary to record the currently accessed PLMN and NID values; when accessing When using a PNI-NPN network, it may be necessary to record the PLMN and CAG values supported by the current cell.

Based on the failure-related reports sent by terminal devices, network devices can determine when performing failure analysis:

(1) Terminal equipment UE0 currently accesses the public network in cell 0 and only supports public network access. If the handover from cell 0 to cell 1 fails, it selects cell 2 for RRC connection re-establishment or re-access, because the signal of cell 2 Good quality.

(2) The terminal equipment UE1 currently accesses a non-public network in cell 0 and only supports access to non-public networks. When the handover from cell 0 to cell 1 fails and selects cell 3 for RRC connection re-establishment or re-access, it is because Although the signal in cell 2 is good, it cannot access the public network, and cannot choose RRC connection re-establishment or re-access. The next best option is to select cell 3 for RRC connection re-establishment or re-access.

Therefore, when the network device optimizes network parameters, when UE0, a terminal device that only supports public networks, is handed over from cell 0 to cell 1, the network device can optimize the handover configuration parameters to make it easier for the terminal device to switch to cell 2; when only supporting non-public networks When UE1 is handed over from cell 0 to cell 1, the network device can optimize the handover configuration parameters to make it easier for the terminal device to switch to cell 3.

Therefore, the network device can improve the network switching success rate of the terminal device by optimizing the network parameters of the terminal device.

Figure 4 is a schematic diagram of another application scenario of the technical solution of the present disclosure, corresponding to the scenario of RRC connection re-establishment or re-access in case of radio link failure, as shown in Figure 4, cell 0 and cell 3 both support public network and non-public network Public network, cell 2 is a public network cell, that is, a non-public network is deployed based on the existing PLMN in the area below the dotted line in the figure, and the terminal equipment UE is located at the edge of cell 0.

Assuming that UE0 is a public network user, because it is located at the edge of cell 0, handover is not triggered but a radio link failure occurs, and cell 2 is selected for RRC connection re-establishment or re-access. The terminal equipment UE0 records the failure-related report and sends it to the network equipment. After the network equipment conducts failure analysis according to the failure-related report, it finds that it is a late handover failure type, and cell 2 should be selected as the target cell for handover.

Assuming that UE1 is a user of a non-public network, since it is located at the edge of cell 0, handover is not triggered but a radio link failure occurs, and cell 3 is selected for RRC connection re-establishment or re-access. The terminal equipment UE1 records the failure-related report and sends it to the network equipment. After the network equipment conducts failure analysis according to the failure-related report, it finds that it is a late handover failure type, and cell 3 should be selected as the target cell for handover.

Based on the prior art, the current network equipment cannot determine whether the terminal equipment should select the target cell 2 or the target cell 3 as the target cell for handover.

Based on the technical solution of the present disclosure, the terminal device can add the current access network information and/or access network restriction information corresponding to the terminal device in the failure-related report. For specific principles, please refer to the relevant description in the previous application scenario. Here No longer.

Figure 5 is a schematic diagram of another application scenario of the technical solution of the present disclosure, which corresponds to the scenario of RRC connection re-establishment or re-access in the PNI-NPN network. As shown in Figure 5, the four cells in the figure are all PNI- In an NPN network, cell 0 and cell 1 support CAG0 and CAG1, cell 2 supports CAG0, and cell 3 supports CAG1.

Assuming that the terminal equipment UE0 only supports the PNI-NPN network CAG0, during the process of moving from cell 0 to cell 1, it selects target cell 1 as the handover target cell. If the handover fails, it selects cell 2 for RRC connection re-establishment or re-access. The terminal equipment UE0 records the failure-related report and sends it to the network equipment. After the network equipment conducts failure analysis based on the failure-related report, it finds that it is the wrong type of handover to the wrong cell, and cell 2 should be selected as the target cell for handover.

Assuming that UE1 only supports PNI-NPN network CAG1, during the process of moving from cell 0 to cell 1, it selects target cell 1 as the target cell for handover, and if the handover fails, it selects cell 3 for RRC connection re-establishment or re-access. The terminal equipment UE1 records the failure-related report and sends it to the network equipment. After the network equipment conducts failure analysis according to the failure-related report, it finds that it is the wrong type of handover to the wrong cell, and cell 3 should be selected as the target cell for handover.

Similar to the scenario where RRC connection re-establishment or re-access occurs due to handover failure, in this scenario, the network device can understand the reason why the terminal device fails to select a different cell for RRC connection re-establishment or re-access by analyzing the failure-related reports, and obtain the terminal device The supported CAG information is the CAG allowed list of the terminal device. Therefore, according to the CAG information supported by the terminal device, the network device can optimize the network parameters of the terminal device, which can improve the network switching success rate of the terminal device. It is also necessary to record the network type for RRC connection re-establishment or re-access, including the CAG allowed list supported by the cell performing RRC connection re-establishment or re-access.

Figure 6 is a schematic diagram of another application scenario of the technical solution of the present disclosure, corresponding to the scenario of RRC connection re-establishment or re-access in case of handover failure in the external authentication network, as shown in Figure 6, all four cells in the figure support external authentication In the right network, cell 0 and cell 1 support GIN0 and GIN1, cell 2 supports GIN0, and cell 3 supports GIN1.

Assuming that UE0 only supports GIN0, during the process of moving from cell 0 to cell 1, it selects target cell 1 as the handover target cell, and if the handover fails, it selects cell 2 for RRC connection re-establishment or re-access. The terminal equipment UE0 records the failure-related report and sends it to the network equipment. After the network equipment conducts failure analysis based on the failure-related report, it finds that it is the wrong type of handover to the wrong cell, and cell 2 should be selected as the target cell for handover.

Assuming that UE1 only supports GIN1, during the process of moving from cell 0 to cell 1, it selects target cell 1 as the handover target cell, and if the handover fails, it selects cell 3 for RRC connection re-establishment or re-access. The terminal equipment UE1 records the failure-related report and sends it to the network equipment. After the network equipment conducts failure analysis according to the failure-related report, it finds that it is the wrong type of handover to the wrong cell, and cell 3 should be selected as the target cell for handover.

Similar to the scenario where handover fails and RRC connection re-establishment occurs in the PNI-NPN network, in this scenario, the network device can understand the reason why the terminal device fails to handover and select a different cell for RRC connection re-establishment by analyzing the failure-related reports, and obtain the GIN supported by the terminal device. information, so that the network device can optimize the network parameters of the terminal device according to the GIN information supported by the terminal device, and can improve the network switching success rate of the terminal device.

Figure 7 is a schematic diagram of another application scenario of the technical solution of the present disclosure, corresponding to the information interaction scenario between network nodes, as shown in Figure 7, in the figure, cell 0, cell 1 and cell 3 support public and private networks, and cell 2 is The public network, that is, the public network and private network are supported below the dotted line, and only the public network is supported above the dotted line.

As shown in conjunction with FIG. 8 , FIG. 8 is a flowchart of a handover report message in the technical solution of the present disclosure. As described above in the embodiment corresponding to Figure 3 to the embodiment corresponding to Figure 6, the network obtains the RLF report/handover failure report, handover success report, random access report or other newly added reports recorded by the UE for network optimization. In addition, there is another situation. Traditionally, after the network receives the RRC connection re-establishment request message sent by the UE, if the RLF report recorded by the UE is not obtained, the network will also send a failure indication (that is, a failure indication) between network nodes. ) message to notify the failed node to perform MRO analysis. If the analysis of the failed node requires other network nodes to optimize parameters, it will send a handover report (ie, handover report) message to the node to be optimized.

Specifically, the interaction process between the UE and the 5G radio access network (NG Radio Access Network, NG-RAN) is as follows: UE is successfully handed over from NG-RAN1 to NG-RAN2; RLF occurs soon after the handover is successful; Send an RRC connection re-establishment or re-access request message; the failed base station is NG-RAN2, and sends a failure indication message to NG-RAN2; NG-RAN2 analyzes and finds that the RLF failure is due to the unreasonable target cell selected by NG-RAN1 handover , that is, the failure type of switching to the wrong cell, NG-RAN3 should be selected, and a handover report message should be sent to notify NG-RAN1.

The above-mentioned traditional inter-node messages need to be enhanced in the private network. As shown in Figure 6, UE0 is a user that only supports the public network. It is handed over from cell 0 to cell 1. RLF occurs soon after the handover is successful, and it is sent in cell 2. RRC connection re-establishment request message, re-establishment failed; UE1 is a user that only supports private network, handover from cell 0 to cell 1, RLF occurs soon after the handover is successful, and sends RRC connection re-establishment or re-access request in cell 3 message, Re-establishment failed;

The network needs to know the private network related information before parameter optimization can be performed. Public network users fail to switch from cell 0 to cell 1. In fact, cell 2 should be selected because cell 2 supports the public network; private network users fail to switch from cell 0 to cell 1. , you should actually select cell 3, because cell 3 supports private networks. Otherwise, the network cannot judge which cell should be selected as the candidate cell for the subsequent handover after the handover fails, and needs to add private network related information in the inter-node message.

Specifically, the inter-node message flow is:

After cell 2 receives the RRC connection re-establishment request message, it sends a failure indication message to the network node where cell 1 is located. There is no RLF report in the message, and notifies cell 1 of information related to RRC connection re-establishment. After cell 1 analyzes the failure indication message, if it thinks that cell 0 should perform parameter optimization, it sends a handover report message to the network node where cell 0 is located.

Among them, the failure indication message includes the identity of the cell where RRC connection re-establishment or re-access occurs. The cell identity where RRC connection re-establishment or re-access occurs is currently the global cell identity, but this identity cannot indicate that cell 3 is a private network The community needs to be expanded, specifically:

When cell 3 is an SNPN network, it is also necessary to record the currently accessed PLMN and NID values; when cell 3 is a PNI-NPN network, it is necessary to record the PLMN and CAG values supported by the cell; when cell 3 is an external authentication network, The GIN value supported by the cell needs to be recorded.

The handover report message contains the identity of the source cell, the identity of the target cell, and the identity of the cell where RRC connection re-establishment or re-access occurs. The identity of the cell where RRC connection re-establishment or re-access occurs is currently the global cell identity, but this identity cannot Indicate that cell 0, cell 1, and cell 3 are private network cells and need to be expanded, specifically:

When the cell is an SNPN network, it is also necessary to record the currently accessed PLMN and NID values; when the cell is a PNI-NPN network, it is necessary to record the PLMN and CAG values supported by the cell; when the cell is an external authentication network, it is necessary to record the cell Supported GIN values.

In some embodiments, a terminal device is provided.

FIG. 9 is a schematic diagram of a terminal device provided by an embodiment of the present disclosure. As shown in FIG. 9 , the terminal device includes: a memory 91 , a transceiver 92 , and a processor 93 .

Among them, the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

When it is determined that the terminal device fails, a failure-related report is generated, and the failure-related report includes information about the non-public network corresponding to the terminal device;

Send failure-related reports to network devices.

In some embodiments, determining that the terminal device has failed includes:

In some embodiments, the processor is further configured to perform the following operations:

In some embodiments, a network device is provided.

FIG. 10 is a schematic diagram of a network device provided by an embodiment of the present disclosure. As shown in FIG. 10 , the network device includes a memory 101 , a transceiver 102 , and a processor 103 .

a memory for storing a computer program; a transceiver for sending and receiving data under the control of the processor; a processor for reading the computer program in the memory and performing the following operations:

Receive the failure-related report sent by the terminal device, and the failure-related report includes the non-public network-related information corresponding to the terminal device;

A parameter optimization process is performed based on non-public network related information.

In some embodiments, the network device includes multiple network nodes; the processor is further configured to perform the following operations:

In some embodiments, an apparatus for processing a non-public network is provided, which is applied to a terminal device.

FIG. 11 is a schematic diagram of a non-public network processing device applied to a terminal device provided by an embodiment of the present disclosure. As shown in FIG. 11 , the device includes:

The generating module 111 is configured to generate a failure-related report when determining that the terminal device fails, and the failure-related report includes non-public network-related information corresponding to the terminal device;

The sending module 112 is configured to send a failure related report to the network device, where the failure related report is used to instruct the network device to perform parameter optimization processing according to non-public network related information.

In some embodiments, determining that the terminal device has failed includes:

In some embodiments, the apparatus also includes a processing model; a processing module for:

In some embodiments, a non-public network processing apparatus is provided, which is applied to a network device.

FIG. 12 is a schematic diagram of a non-public network processing device applied to network equipment provided by an embodiment of the present disclosure. As shown in FIG. 12 , the device includes:

The receiving module 121 is configured to receive a failure-related report sent by the terminal device, where the failure-related report includes non-public network-related information corresponding to the terminal device;

The optimization module 122 is configured to perform parameter optimization processing according to non-public network related information.

In some embodiments, the network device includes a plurality of network nodes; the device further includes: a processing module; the processing module is configured to:

In some embodiments, the processing module is further configured to:

In some embodiments, the processing module is also used for:

For specific limitations on the non-public network processing device, refer to the above-mentioned limitations on the non-public network processing method, which will not be repeated here. Each module in the above-mentioned non-public network processing device may be implemented in whole or in part by software, hardware or a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, and can also be stored in the memory of the computer device in the form of software, so that the processor can invoke and execute the corresponding operations of the above-mentioned modules.

In the above devices, the memory and the processor are electrically connected directly or indirectly to realize data transmission or interaction. For example, these components may be electrically connected to each other through one or more communication buses or signal lines, for example, they may be connected through a bus. Computer-executed instructions for implementing the data access control method are stored in the memory, including at least one software function module that can be stored in the memory in the form of software or firmware. The processor runs the software programs and modules stored in the memory to execute various Functional application and data processing.

The memory can be, but not limited to, random access memory (Random Access Memory, RAM), read-only memory (Read Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), erasable only Read memory (Erasable Programmable Read-Only Memory, EPROM), Electric Erasable Programmable Read-Only Memory (EEPROM), etc. Wherein, the memory is used to store programs, and the processor executes the programs after receiving execution instructions. Further, the software programs and modules in the memory may also include an operating system, which may include various software components and/or drivers for managing system tasks (such as memory management, storage device control, power management, etc.), and may Communicate with various hardware or software components to provide an operating environment for other software components.

The processor can be an integrated circuit chip with signal processing capabilities. Above-mentioned processor can be general-purpose processor, comprises central processing unit (Central Processing Unit, CPU), network processor (Network Processor, NP) etc. Various methods, steps and logic block diagrams disclosed in the embodiments of the present disclosure may be implemented or executed. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

In some embodiments, a processor-readable storage medium is provided, the processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the steps of the method embodiments of the present disclosure.

In some embodiments, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps of the various method embodiments of the present disclosure are implemented.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented through computer programs to instruct related hardware. The computer programs can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it may include the procedures of the embodiments of the above-mentioned methods. Wherein, any reference to memory, storage, database or other media used in various embodiments provided by the present disclosure may include non-volatile and/or volatile memory. Nonvolatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Chain Synchlink DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

Other embodiments of the disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the applications disclosed herein. The present disclosure is intended to cover any modification, use or adaptation of the present disclosure. These modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure. . The specification and examples are to be considered exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It should be understood that the present disclosure is not limited to the precise constructions which have been described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

A method for processing a non-public network, which is applied to a terminal device, and the method includes:

When determining that the terminal device fails, generate a failure-related report, where the failure-related report includes non-public network-related information corresponding to the terminal device;

Sending a report related to the failure to a network device.
The method according to claim 1, wherein the non-public network-related information includes current access network information corresponding to the terminal device, access network restriction information, radio resource control RRC connection re-establishment or re-connection after the terminal device fails One or more of the entered network information.
The method according to claim 2, wherein the current access network information includes the network type of the terminal device's current access network and the network identification information of the current access network;

The network information of the RRC connection re-establishment or re-access includes the network type of the RRC connection re-establishment or re-access;

Wherein, the network type includes any one of: an independently deployed non-public network SNPN, a public network integrated non-public network PNI-NPN, or a public network.
The method according to claim 2, wherein the access network restriction information includes the network type of the network accessible to the terminal device and the network identification information of the accessible network;

Wherein, the network type includes any one of SNPN network, PNI-NPN network or public network or a combination of at least two.
The method according to claim 3 or 4, wherein, if the network type is an SNPN network, the network identification information includes a public land mobile network (PLMN) and a network identification code (NID) value.
The method according to claim 3 or 4, wherein, if the network type is a PNI-NPN network, the network identification information includes PLMN and closed access group CAG value.
The method according to claim 3 or 4, wherein, if the network type is an external authentication network, the network identification information includes a network selection group identity identification GIN value.
The method according to claim 1, wherein determining that the failure of the terminal device comprises:

When the cell handover failure or radio link failure occurs on the terminal device, it is determined that the terminal device fails.
The method according to claim 1, wherein the failure-related reports include any one or at least two of a radio link failure RLF report, a handover failure report, a handover success report, or a random access report.
The method according to claim 1, wherein the method further comprises:

sending an RRC connection re-establishment or re-access request message to the network device, the request message is used to trigger the network device to send a failure indication message between different network nodes, and the failure indication message is used to notify that a failure occurs network nodes to optimize network parameters.
A method for processing a non-public network, which is applied to a network device, and the method includes:

receiving a failure-related report sent by the terminal device, where the failure-related report includes non-public network-related information corresponding to the terminal device;

A parameter optimization process is performed according to the non-public network-related information.
The method of claim 11, wherein the network device comprises a plurality of network nodes;

The method also includes:

When the first network node among the network nodes receives the radio resource control RRC connection re-establishment or re-access request message sent by the terminal device, and does not receive a failure-related report, the first network node Sending a failure indication message to the second network node where the failure occurred; wherein, the failure indication message is used to support the second network node to perform parameter optimization analysis, and the failure indication message includes the occurrence of RRC connection re-establishment or re-access A cell identity, the identity of the cell where RRC connection re-establishment or re-access occurs is a global cell identity.
The method according to claim 11 or 12, wherein the method further comprises:

When the failed second network node receives the failure indication message and determines that other network nodes need to perform parameter optimization analysis, it sends a handover report message to the other network nodes, and the handover report message is used to indicate to the other network nodes Nodes optimize network parameters;

Wherein, the handover report message includes the handover source cell identity, the target cell identity and the identity of the cell where RRC connection re-establishment or re-access occurs, and the identity of the cell where RRC connection re-establishment or re-access occurs is a global cell identity.
A terminal device, including a memory, a transceiver, and a processor:

The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

When determining that the terminal device fails, generate a failure-related report, where the failure-related report includes non-public network-related information corresponding to the terminal device;

Sending a report related to the failure to a network device.
The terminal device according to claim 14, wherein the non-public network-related information includes current access network information corresponding to the terminal device, access network restriction information, radio resource control RRC connection re-establishment or re-establishment after the terminal device fails One or more of the accessed network information.
The terminal device according to claim 14, wherein the processor is further configured to perform the following operations:

When the cell handover failure or radio link failure occurs on the terminal device, it is determined that the terminal device fails.
The terminal device according to claim 14, wherein the failure-related reports include any one or at least two of a radio link failure RLF report, a handover failure report, a handover success report, or a random access report.
The terminal device according to claim 14, wherein the processor is further configured to perform the following operations:

sending an RRC connection re-establishment or re-access request message to the network device, the request message is used to trigger the network device to send a failure indication message between different network nodes, and the failure indication message is used to notify that a failure occurs network nodes to optimize network parameters.
A network device, including a memory, a transceiver, and a processor:

The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

receiving a failure-related report sent by the terminal device, where the failure-related report includes non-public network-related information corresponding to the terminal device;

A parameter optimization process is performed according to the non-public network-related information.
A non-public network processing device, which is applied to terminal equipment, including:

A generating module, configured to generate a failure-related report when determining that a failure occurs in the terminal device, the failure-related report including non-public network-related information corresponding to the terminal device;

A sending module, configured to send the failure-related report to the network device.
The apparatus according to claim 20, wherein the non-public network-related information includes current access network information corresponding to the terminal device, access network restriction information, radio resource control RRC connection re-establishment or re-connection after the terminal device fails. One or more of the entered network information.
The device according to claim 20, wherein said device is further configured to:

When the cell handover failure or radio link failure occurs on the terminal device, it is determined that the terminal device fails.
The apparatus according to claim 20, wherein the failure-related reports include any one or at least two of a radio link failure RLF report, a handover failure report, a handover success report, or a random access report.
The device according to claim 20, wherein the device further comprises a processing model; a processing module, configured to:

sending an RRC connection re-establishment or re-access request message to the network device, the request message is used to trigger the network device to send a failure indication message between different network nodes, and the failure indication message is used to notify that a failure occurs network nodes to optimize network parameters.
A non-public network processing device, which is applied to network equipment, including:

A receiving module, configured to receive a failure-related report sent by the terminal device, where the failure-related report includes non-public network-related information corresponding to the terminal device;

An optimization module, configured to perform parameter optimization processing according to the non-public network related information.
The device according to claim 25, wherein the network device comprises a plurality of network nodes; the device further comprises: a processing module; a processing module configured to:

When the first network node among the network nodes receives the radio resource control RRC connection re-establishment or re-access request message sent by the terminal device, and does not receive a failure-related report, the first network node Sending a failure indication message to the second network node where the failure occurred; wherein, the failure indication message is used to support the second network node to perform parameter optimization analysis, and the failure indication message includes the occurrence of RRC connection re-establishment or re-access A cell identity, the identity of the cell where RRC connection re-establishment or re-access occurs is a global cell identity.
The method according to claim 25 or 26, wherein the processing module is further used for:

When the failed second network node receives the failure indication message and determines that other network nodes need to perform parameter optimization analysis, it sends a handover report message to the other network nodes, and the handover report message is used to indicate that the other network nodes Nodes optimize network parameters;

Wherein, the handover report message includes the handover source cell identity, the target cell identity and the identity of the cell where RRC connection re-establishment or re-access occurs, and the identity of the cell where RRC connection re-establishment or re-access occurs is a global cell identity.
A processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to make the processor execute the method according to any one of claims 1-13.