Techniques for performing minimization of drive tests

Abstract

A technique for performing minimization of drive tests (MDT) and performing out-of-service (OOS) or arbitrary cell selection state reporting is described. One exemplary wireless communication method includes receiving, by a user equipment, a first message indicating that the user equipment is to record and provide membership information of one or more neighboring cells, where the user equipment is camped on a cell that is outside of the one or more neighboring cells, where the membership information indicates whether a first set of network identifiers (IDs) of the one or more neighboring cells belong to a second set of network IDs of a registered network or a selected network, and where the user equipment is configured to connect to the registered network or the selected network; and sending a second message including the membership information of the one or more neighboring cells detected by the user equipment.

Description

Technical Field

[0001] This disclosure is generally directed to digital wireless communications. Background Technology

[0002] Mobile communication technologies are propelling the world toward an increasingly interconnected and networked society. Compared to existing wireless networks, next-generation systems and wireless communication technologies will need to support a wider range of use case characteristics and provide more complex and sophisticated access requirements and flexibility.

[0003] LTE (Long Term Evolution) is a wireless communication standard for mobile devices and data terminals developed by the 3rd Generation Partnership Project (3GPP). LTE Evolution (LTE-A) is a wireless communication standard that enhances the LTE standard. The fifth-generation wireless system, known as 5G, advances the LTE and LTE-A wireless standards and aims to support higher data rates, massive connectivity, ultra-low latency, high reliability, and other emerging service requirements. Summary of the Invention

[0004] A technique for performing Minimized Drive Testing (MDT) and for operating a Self-Organizing Network (SON) for a Non-Public Network (NPN) (such as for a Standalone Non-Public Network (SNPN)) is disclosed, which can be deployed by a private operator and can share the same frequency as a public network.

[0005] An exemplary embodiment for providing membership information of a network cell includes: receiving a first message by a user equipment, the first message instructing the user equipment to record and provide membership information of one or more neighboring cells, wherein the user equipment resides on a cell other than the one or more neighboring cells, wherein the membership information indicates whether a first set of network identifiers (IDs) of the one or more neighboring cells belongs to a second set of network IDs of a registered network or a selected network, and wherein the user equipment is configured to connect to the registered network or the selected network; and sending a second message, the second message including the membership information of the one or more neighboring cells detected by the user equipment.

[0006] In some embodiments, the membership information of the one or more neighboring cells is determined by the user equipment by comparing a second set of network IDs with a first set of network IDs broadcast in system information. In some embodiments, the second set of network IDs is provided by the upper layer of the user equipment. In some embodiments, the second set of network IDs includes a standalone non-public network (SNPN) ID, which is equal to the public terrestrial mobile network (PLMN) plus the network ID. In some embodiments, the second set of network IDs includes the public terrestrial mobile network (PLMN) ID. In some embodiments, the second set of network IDs includes a public network integrated non-public network (PNI-NPN) ID, which is equal to the PLMN plus the closed access group (CAG) ID.

[0007] In some embodiments, upon receiving the first message, the method further includes: storing a configuration indicating a request for membership information in a first local variable in the user equipment; after obtaining membership information from one or more neighboring cells, performing a recording operation, wherein the recording operation includes storing the membership information in a second local variable in the user equipment; sending a third message indicating that the membership information is available; and wherein the second message is sent in response to the user equipment receiving a fourth message triggering the user equipment to report membership information. In some embodiments, the third message includes a Radio Resource Control (RRC) reconfiguration complete message, an RRC establishment complete message, an RLC recovery complete message, or an RRC re-establishment complete message.

[0008] In some embodiments, the membership information in the second message includes the Physical Cell Identifier (PCI) of at least one neighboring cell, the measurement quality results of at least one neighboring cell, the number of Synchronization Signal Blocks (SSBs) received from at least one neighboring cell, or the membership indicator of at least one neighboring cell. In some embodiments, the second message includes the Physical Cell Identifier (PCI) of at least one neighboring cell. In some embodiments, the first message includes one or more Physical Cell Identifier (PCI) ranges, and the second message includes membership information of one or more neighboring cells having one or more frequencies within one or more PCI ranges. In some embodiments, each of the one or more PCI ranges is associated with an Absolute Radio Frequency Channel Number (ARFCN). In some embodiments, each of the one or more PCI ranges is associated with a first group of one or more frequencies.

[0009] In some embodiments, the first group of one or more frequencies includes any one or more within and between frequencies. In some embodiments, the first message is included in a System Information Block (SIB) or a Private Radio Resource Control (RRC) message.

[0010] An exemplary embodiment for performing Minimum Drive Test (MDT) includes a user equipment receiving a message restricting the area where the user equipment can perform MDT, wherein the user equipment is configured to operate on a non-public network (NPN), and wherein the message includes: one or more independent non-public network (SNPN) identifiers, the one or more independent non-public network (SNPN) identifiers being equal to a public terrestrial mobile network (PLMN) identifier plus a network identifier; a Closed Access Group (CAG) list, the Closed Access Group (CAG) list including one or more PLMN identifiers associated with the CAG list; a CAG-only indicator, the CAG-only indicator indicating that the user equipment is requested to perform MDT only on a set of CAGs identified by the CAG list; and a CAG-exclude indicator, the CAG-exclude indicator indicating that the user equipment is requested to perform MDT on all cells including public cells and CAG cells other than the set of CAG cells identified by the CAG list; and, based on the message, performing measurements for MDT.

[0011] In some embodiments, the user equipment (UE) is registered under an SNPN network or a PNI-NPN network. In some embodiments, for the PLMN and for the UE registered under the PNI-NPN network: the UE belongs to a first type of PNI-NPP UE, where the UE is only permitted to camp under a CAG cell, or the UE belongs to a second type of PNI NPN UE, where the UE is permitted to camp under both CAG cells and public cells. In some embodiments, the UE registered under the SNPN network uses one or more SNPN identifiers to restrict the area where the UE performs MDT measurements. In some embodiments, the UE registered under the PNI-NPN network uses a CAG list, a CAG-only indicator, or a CAG-excluded indicator to restrict the area where the UE performs MDT measurements.

[0012] In some embodiments, the user equipment (UE) belongs to a first type of PNI-NPN UE, wherein the UE is only allowed to camp under a CAG cell, and for both the PLMN and the first type of PNI-NPN UE, the UE performs MDT measurements only in one or more cells broadcast as included in one of the CAG IDs in the CAG list. In some embodiments, the UE belongs to a second type of PNI-NPN UE, wherein the UE is allowed to camp under both CAG cells and public cells, and for both the PLMN and the second type of PNI-NPN UE, only the CAG indicator instructs the UE to perform MDT measurements only in one or more cells broadcast as included in one of the CAG IDs in the CAG list.

[0013] In some embodiments, the method further includes, when it is determined that no CAG-only indication exists for the PLMN and for the second type of PNI-NPN UE, the UE performs MDT measurements in one or more cells broadcast as included in one of the CAG IDs in the CAG list and in public cells under the PLMN. In some embodiments, the user equipment is a second type of PNI-NPN user equipment, wherein the user equipment is allowed to camp under CAG cells and public cells, and for the PLMN and for the second type of PNI-NPN UE, a CAG exclusion indicator indicates that the UE will perform MDT measurements on all cells including public cells and CAG cells other than the set of CAG cells identified by the CAG list. In some embodiments, the user equipment is a first type of PNI-NPN user equipment, wherein the user equipment is only allowed to camp under CAG cells, and for the PLMN and for the first type of PNI-NPN UE, a CAG exclusion indicator indicates that the UE will perform MDT measurements on all cells included in the allowed CAG cells configured by the upper layer, except for the set of CAG cells identified by the CAG list.

[0014] In some embodiments, the message includes a list of global cell identifiers, a list of tracking area codes, and a list of tracking area identifiers. In some embodiments, the message is received via private radio resource control (RRC) signaling or broadcast RRC signaling.

[0015] An exemplary embodiment for identifying a reason for an arbitrary cell selection state includes a user equipment performing a first determination that all available frequencies are blocked because one or more cells operating on all available frequencies have the highest or best signal quality and the one or more cells do not belong to a registered network or a selected network; in response to the first determination, performing a second determination to enter an arbitrary cell selection state, in which the user equipment is configured to perform cell selection to find a cell to camp on; and recording information including the identified reason for the arbitrary cell selection state. In some embodiments, the identified reason for the arbitrary cell selection state indicates a blocking reason indicating that the user equipment has entered an arbitrary cell selection state in which the user equipment is blocked from accessing available frequencies. In some embodiments, the identified reason for the arbitrary cell selection state indicates a weak signal indicating that the user equipment is outside coverage. In some embodiments, the identified reason for the arbitrary cell selection state indicates that the user equipment is blocked from accessing frequencies due to non-access stratum reasons.

[0016] In yet another exemplary aspect, the above-described method is embodied in processor-executable code and stored in a non-transient computer-readable storage medium. When executed by a processor, the code included in the computer-readable storage medium causes the processor to implement the method described in this patent application.

[0017] In yet another exemplary embodiment, a device configured or operable to perform the above-described methods is disclosed.

[0018] The above and other aspects and their embodiments will be described in more detail in the drawings, description and claims. Attached Figure Description

[0019] Figure 1 An example scenario of user equipment (UE) located at the edges of two cells is shown.

[0020] Figure 2 The report structure for reporting measurement results obtained by performing Minimum Drive Test (MDT) to neighboring cells is shown.

[0021] Figure 3 Example scenarios are shown that indicate different PCI ranges for different frequencies.

[0022] Figure 4 The structure of a region configuration is shown, in which the network configures one or more regions for the UE to perform MDT.

[0023] Figure 5A An exemplary flowchart is shown for a method of providing membership information for a network cell.

[0024] Figure 5B An exemplary flowchart for performing Minimum Drive Test (MDT) is shown.

[0025] Figure 5C An exemplary flowchart of a method for identifying the cause of an arbitrary cell selection state is shown.

[0026] Figure 6 An exemplary block diagram of a hardware platform that may be part of a network node or a user device is shown. Detailed Implementation

[0027] 3GPP standard Rel-16 describes two types of private networks: Standalone Non-Public Networks (SNPNs) and Public Network Integrated Non-Public Networks (PNI-NPNs). For PNI-NPNs, the concept of Closed Access Groups (CAGs) for access control at the Access Layer (AS) is introduced. Meanwhile, for public networks, Minimum Drive Test (MDT) and Self-Organizing Networks (SON) are described. However, MDT can also be very useful for non-public networks (NPNs), and it can raise different issues compared to MDT in public networks. For example, differences between MDT in public networks and MDT in NPNs might include issues such as how to select the Physical Cell Identifier (PCI) for the SNPN network and how to configure MDT areas.

[0028] For public networks, different operators can deploy networks on different frequencies. However, for NPNs, without NPN-specific frequencies, there will be interference between the public network and the NPN. These interferences can be considered during the deployment phase. For example, how to select the PCI range for a given NPN network can be considered. If the CAG network and the public network are deployed by the same operator, the CAG network knows the neighboring cell information of the public network. However, when the SNPN selects the PCI range, the SNPN does not know any PCI information of neighboring CAGs or public cells. At least in this case, the SNPN network can employ techniques to avoid PCI confusion or conflict. The gNB can detect the synchronization signals of neighboring cells (e.g., primary and secondary synchronization signals), where the gNB can obtain the PCI of neighboring cells from the synchronization signals. However, there may be some situations, such as... Figure 1 As shown, cell 1 cannot detect the PCI of cell 2. However, in Figure 1 In this scenario, the UE can detect cells 1 and 2, which have the same PCI but originate from different operators. Therefore, such issues should be avoided when determining the PCI range of a cell.

[0029] In current networks, such technical problems can be addressed by employing two methods that can be used simultaneously: (1) avoiding the use of the same PCI for adjacent cells during the deployment phase; and (2) requesting the UE to report the Cell Global Identifier (CGI) in the connected state. However, as mentioned above, method (1) cannot be easily adopted for SNPN due to different operators. Therefore, some improvements can be described to describe techniques for assisting PCI range selection, at least for SNPN networks. According to the current MDT structure, for adjacent cells, the UE reports adjacent cell information, such as... Figure 2 As shown.

[0030] like Figure 2As shown in the report structure, the network receiving neighbor cell information cannot determine whether the reported cell comes from a different operator, at least because different operators can deploy different SNPNs with the same (or overlapping) PCI ranges, making it possible for, for example, that the first SNPN might not know whether the PCI belongs to the first SNPN or the second SNPN. Therefore, some improvements can be described as techniques added to the MDT function to assist in PCI range selection.

[0031] The example headings in the following sections are used to facilitate understanding of the disclosed subject matter and do not limit the scope of the claimed subject matter in any way. Therefore, one or more features of one example section may be combined with one or more features of another example section. Furthermore, the term "5G" is used for clarity, but the technology disclosed in this application is not limited to 5G technology and can be used in wireless systems implementing other protocols.

[0032] I. Technical solutions for PCI range selection:

[0033] In one exemplary technical solution, the UE can report membership information to the network. For example, during a reselection period, when the UE determines that the highest-ranked cell is not a member cell, the UE can record the event and related information. The UE can determine the highest-ranked or best cell by determining one or more metrics (e.g., RSRP, RSRQ, etc.) associated with signal quality from one or more cells, where the highest-ranked or best cell has a metric indicating the highest (or best) signal quality. SNPNs can be identified by a combination of PLMN identifier (ID) and network ID (NID). When the network identifier (e.g., SNPN ID or PLMN ID) of the highest-ranked or best cell is determined not to be a registered or selected SNPN, the UE can determine that the highest-ranked or best cell is not a member cell. Registered or selected SNPNs may include SNPNs that allow the UE to camp on or to which the UE can connect.

[0034] Solution 1:

[0035] The UE can report membership information to the network to indicate whether a detected PCI belongs to a registered SNPN (RSNPN) or a selected SNPN network. The UE determines whether a cell belongs to an RSNPN or a selected SNPN network by determining whether the identifier for the RSNPN or the selected SNPN (e.g., network ID) is included in the system information. The UE can check the broadcast network ID in the system information, and if the identifiers for the RSNPN and the selected SNPN (which may be provided by upper layers) are included in the system information, then the RSNPN or selected SNPN cell is a member cell; otherwise, it is not a member cell.

[0036] Typically, an SNPN cell can collect PCI information from neighboring cells, and the UE can report this PCI information. Then, to avoid unnecessary reporting, the SNPN cell can indicate a reserved PCI range to the UE in a loggedMeasConfig message sent to the UE. The loggedMeasConfig message can include, for example, the PCI range for each Absolute Radio Channel Number (ARFCN). On the UE side, when it is determined that the PCI of one or more cells is included in the PCI range indicated in the loggedMeasConfig message, the UE can report membership information for one or more cells. This membership information can indicate whether one or more neighboring cells are member cells (e.g., whether the identifier of an RSNPN or selected SNPN is included in the system information).

[0037] In an exemplary embodiment, such as Figure 3 As shown, the UE can report cell information with PCIs belonging to one or more cells within PCI range x via ARFCN1, and simultaneously report cell information with PCIs belonging to one or more cells within PCI range y via ARFCN2. The UE can perform inter-frequency and intra-frequency cell measurements and reporting simultaneously. For each of the one or more cells, the cell information may include the cell's PCI, the cell's measurement quality results, the number of good SSBs, and the cell's membership information. PCI range x and PCI range y can be indicated in the loggedMeasConfig message.

[0038] Solution 1.1:

[0039] To avoid unnecessary reporting, the cell can indicate the reserved PCI range for the region (e.g., the PCI range for each frequency) to the UE in the loggedMeasConfig. Then, on the UE side, the UE can report the membership information of the PCIs included in the PCI range. Frequency can be intra-frequency or inter-frequency.

[0040] On the other hand, SNPN may also impact CAG or Public Terrestrial Mobile Network (PLMN). For example, SNPN may be deployed on the same frequency as the public network / PNI-NPN network, or the public network / PNI-NPN network may eventually be deployed on the same frequency as SNPN, since the public network and SNPN may not know each other's PCI. Therefore, the techniques described in Solution 1 and Solution 1.1 can also be applied to public network / PNI-NPN networks to avoid the impact of overlapping PCI between SNPN and public network / PNI-NPN networks.

[0041] Example of PCI range selection:

[0042] Example 1:

[0043] Corresponding to Solution 1: The network can instruct the UE to report membership information in a LoggedMeasurementConfiguration message (also referred to as a loggedMeasConfig message in this patent application), as shown below. The UE can then report the membership information to the network to indicate whether the detected PCI belongs to an RSNPN or a selected SNPN network. For example, the LoggedMeasurementConfiguration message can include a memberShipRequired field.

[0044] LoggedMeasurementConfiguration message

[0045]

[0046] The information shown above in LoggedMeasurementConfiguration can also be indicated in broadcast system information (e.g., SIB1) as shown below. For example, if a cell belonging to a certain SNPNx network can broadcast a memberShipRequired indication in the system information, then all UEs within the broadcast range of that cell and registered in SNPNx can record membership information of neighboring cells. UEs registered in SNPNx are member UEs that can send measurement reports (e.g., MDTs) to the network when the UE is in a connected state.

[0047]

[0048] Upon receiving this configuration, the UE can store the received membershipRequired configuration in VarLogMeasConfig. The UE variable VarLogMeasConfig includes the configuration for measurement recordings performed by the UE in RRC_IDLE and RRC_INACTIVE.

[0049]

[0050] After receiving the LoggedMeasurementConfiguration, the UE can log and report a cell with a mismatched SNPN ID (e.g., RSNPN or the selected SNPN is not included in the system information) once it detects such a cell. This cell with a mismatched SNPN ID is a non-member cell. The UE can record the cell information of this non-member cell by storing its cell information (e.g., the cell's PCI, measurement quality results, number of good SSBs, and membership information) in the UE variable VarLogMeasReport (which includes the recorded measurement information).

[0051]

[0052] When a UE establishes a connection or performs a handover from another RAT, the UE can indicate membership availability information to the network via the RRCResumeComplete / RRCSetupComplete / RRestablishMentComplete / RRCReconfiguration Msg messages. An example of the RRCSetupComplete message is as follows:

[0053]

[0054] If the network includes logMemberShipInfoReq in the UE Information Request message, the UE can include membership-related information in the UE Information Response message as in Solution 1.2.

[0055]

[0056] In the current scheme, a recorded MDT is configured for each UE via dedicated signaling. However, for certain situations (e.g., the cell wants all UEs with MDT capabilities to perform MDT), the network can broadcast the MDT configuration instead of dedicated signaling (or dedicated configuration). In the system information, the network can also instruct different MDT configurations for different UE types (e.g., UEs with reduced capabilities, such as industrial sensors or wearable devices). This MDT configuration may include, for example, an indication of whether the network wants the UE to provide cell membership information (e.g., by including a memberShipRequired field), as explained above in this patent application.

[0057] Solution 1.2:

[0058] The UE can indicate membership information to the network, as shown in the example UEInformationResponse message below. In the UEInformationResponse message, the memberShipInfolist field can indicate cell information detected by the UE, such as indicating one or more cells that do not belong to the current network, and the memberShip field can be used to indicate whether neighboring cells are member cells of the current network. The current network can be an RSNPN or a selected SNPN, an allowed CAG list, etc. If the memberShip field is missing from the UEInformationResponse message, it may mean that neighboring cells do not belong to the current network.

[0059]

[0060] In some embodiments, as shown in the example UEInformationResponse message below, the UE may indicate only the PCI adopted by another operator, where PCIInfoOfotherOperator indicates the PCI used or adopted by another operator:

[0061]

[0062] Solution 1.3:

[0063] Corresponding to Solution 1.1: To avoid unnecessary reporting, the reserved PCI range for a region (e.g., the PCI range for each ARFCN) can be indicated in the loggedMeasConfig. Then, on the UE side, the UE can report membership-related information for PCIs included in the corresponding PCI range. The frequency can be intra-frequency and / or inter-frequency. For example, as shown in the LoggedMeasurementConfiguration message below, the AreaConfigPCIRangeInfo field indicates that, for a specific frequency indicated by dl-CarrierFreq, the UE can report cell information for the PCI of the cell belonging to the PCI range of the frequency indicated by dl-CarrierFreq.

[0064] LoggedMeasurementConfiguration message

[0065]

[0066] II. Technical issues related to NPN regional configuration:

[0067] In current public network MDT (Multi-Targeting Theory), the network configures one or more regions for the UE to perform MDT. The UE will only report serving / neighboring cell information when it is camped in one or more of the configured regions. Currently, the region configuration is constructed as follows: Figure 4 As shown.

[0068] for Figure 4 The areaConfiguration shown does not consider NPN-related issues. Furthermore, at least because the SNPN ID can be indicated in the serving cell configuration (e.g., in TrackingAreaIdentityList) and / or can be included in the reporting message, SNPN is not significantly different from NPN. For CAG (i.e., PNI-NPN), in some cases, the network may only want CAG cell-related information, but the current network cannot indicate such information. Therefore, more granularity can be allowed when configuring areas for NPN networks. Additionally, for a specific PLMN, there can be at least several types of UEs: CAG-only UEs (for which the UE only camps on the CAG) and UEs camping on both the CAG and the PLMN.

[0069] Technical solutions for NPN regional configuration:

[0070] For a PLMN where the UE can only camp on a CAG cell, the network can configure this type of UE with all or part of the CAG list for each PLMN, so that this type of UE can perform MDT in one or more CAG cells, because this type of UE can only camp on the CAG cell for the corresponding PLMN.

[0071] The network can configure the UE to implicitly perform MDT across all allowed CAG lists. For example, if the network does not indicate any CAG information for the PLMN, a CAG-only UE will only consider CAG cells included in the allowed CAG list (indicated by the upper layer (NAS), which can be read from the SIM card or indicated by the network via a NAS message). For example, as shown in Example 2 below, the cagareaConfigForServing field in the LoggedMeasurementConfiguration message can indicate the allowed CAG list for which the UE is requested to perform measurement logging.

[0072] Example 2:

[0073]

[0074] Example 2.1:

[0075] In some embodiments, the UE can also be configured to implicitly perform MDT on indexed regions using the following three example steps:

[0076] Step 1: The UE NAS indicates the list of allowed CAGs to the UE access layer (AS).

[0077] Step 2: The network, based on the list of allowed CAGs in the mobility restriction information, indicates the CAG of the service area by indexing. The mobility restriction information is indicated by the CN.

[0078] Step 3: The UE obtains the CAG ID based on the list of allowed CAGs indicated by the UE NAS layer and index, so that the UE can determine one or more CAGs / PLMNs for which the UE is requested to perform measurement recording (e.g., MDT).

[0079]

[0080] The network (or cell) can also be combined with an existing areaConfigForServing configuration to configure a service area, as shown below:

[0081]

[0082] For SNPN, SNPN ID = PLMN_ID + NID can be used to replace the PLMN ID in the existing areaConfigForServing mentioned above.

[0083] The above information related to AreaConfigForServing can be indicated in Radio Resource Control (RRC) messages (including private RRC messages or broadcast RRC messages) sent by the cell to the UE.

[0084] For a PLMN that supports both CAG and PLMN, the UE can be configured as follows: PLMN only; CAG only; a portion of the allowed CAG list; and all PLMN cells except for some CAG cells.

[0085] Example 3 - For UE types that can simultaneously reside on both CAG and public networks:

[0086] The cell can send the following example logged measurement configuration message to the UE. The cagareaConfigForServing field indicates the list of CAGs for which the UE is requested to perform measurement logging, the cagareaOnly field indicates that only CAGs included in the CAG-IdentityList are requested to perform measurement logging, and the cagareaExcept field indicates that all cells other than those belonging to the "cag-IdentityList" are requested to perform measurement logging.

[0087]

[0088]

[0089] For a PLMN that supports both CAG and PLMN for the UE, if the network wants to indicate the entire PLMN, the network can also set the cagareaConfigForServing-rxy field to not exist, and then the UE can refer to the traditional cagareaConfigForServing.

[0090] If the network wants to configure only the list of allowed CAGs, it can indicate a CAG-only indication. If the network wants to configure PLMNs other than certain CAGs, it can indicate an exceptCag indication.

[0091] III. Description of technical issues regarding Out of Service (OOS) / Any Cell Selection Status Reporting:

[0092] In the current MDT, the UE only reports service outage (OOS) events / arbitrary cell selection status, as shown below:

[0093]

[0094] However, arbitrary cell selection can occur for different reasons. In one scenario, if the UE determines that the strongest or highest-ranking cell across all frequencies is unsuitable because it is associated with a mismatched network ID (i.e., a non-member cell), the UE can ban all frequencies, for example, for five minutes, based on the highest-ranking or best-ranking cell selection or reselection criteria. In another scenario, arbitrary cell selection may occur when the UE is outside coverage area. In both of these different cases, if the UE indicates the same information to the network, the network will not obtain the correct coverage information.

[0095] Technical solutions for arbitrary cell selection status reporting:

[0096] In some embodiments, the arbitrary cell selection state event field can provide detailed reasons for arbitrary cell selection states, such as banned or weak signal strength.

[0097] To provide more information, the UE can report information about the nearest highest-ranking or best-ranking cell on each frequency. In some embodiments, when a UE is blocked on a specific frequency because "the strongest / highest-ranking cell among all frequencies is not suitable for a mismatched network ID," the UE can record the event and provide the signal strength of the strongest / highest-ranking cell. If the UE determines that another cell exists on another frequency where it can camp, the UE may not enter an arbitrary cell selection state.

[0098] Example of reporting the status of arbitrary cell selection:

[0099] Example 4:

[0100] In some embodiments, such as when a UE is disabled due to "the strongest / highest priority cell across all frequencies is not suitable for a mismatched network ID" and enters an arbitrary cell selection state, the UE can indicate details of the reason for the arbitrary cell selection state, as shown below. In the example shown below, Bar indicates that the UE is disabled and enters an arbitrary cell selection state because "the strongest / highest priority cell across all frequencies is not suitable for a mismatched network ID"; WeakSignal means the UE is outside coverage; and Other means the UE is disabled for a non-AS reason. As mentioned above, ueOOSCause can be included in the "LogMeasReport" of the UEInformationResponse message. ueOOSCause can indicate the detailed reason that caused the UE to enter the arbitrary cell selection state.

[0101]

[0102]

[0103] Example 5: When a frequency is banned, the UE records the signal strength and serving cell information of the strongest / highest-level cell.

[0104] barringInfoReport:

[0105] When at least one frequency is blocked due to "the strongest / highest-ranked cell among all frequencies is not suitable for a mismatched network ID," the UE records the best / highest-ranked cell information. This can be recorded once a frequency is blocked, or when the UE is blocked on all frequencies. Simultaneously, the UE can also record serving cell information before the reselection evaluation. The UE can include this recorded information in dedicated RRC signaling (e.g., UEInformationResponse).

[0106] In the example barringinfoReport message shown below, anyCellSelectionDetected indicates that the UE entered the anyCellselection state because "the strongest / highest-ranked cell among all frequencies is not suitable for a mismatched network ID"; servingCellInfo indicates the serving cell information before the reselection evaluation; and bestNeighborCellInfoList indicates the best / highest-ranked cell information when a frequency is blocked because "the strongest / highest-ranked cell among all frequencies is not suitable for a mismatched network ID". ueOOSCause can indicate the detailed reason that caused the UE to enter the anyCellSelection state.

[0107]

[0108]

[0109] Figure 5A An exemplary flowchart of a method 500A for providing membership information for a network cell is shown. Operation 502 includes: receiving a first message from a user equipment (UE) instructing the UE to record and provide membership information for one or more neighboring cells, wherein the UE resides on a cell other than the one or more neighboring cells, wherein the membership information indicates whether a first set of network identifiers (IDs) of the one or more neighboring cells belongs to a second set of network IDs of a registered network or a selected network, and wherein the UE is configured to connect to the registered network or the selected network. Operation 504 includes: sending a second message including the membership information for the one or more neighboring cells detected by the UE.

[0110] In some embodiments of method 500A, membership information of one or more neighboring cells is determined by the user equipment by comparing a second set of network IDs with a first set of network IDs broadcast in system information. In some embodiments of method 500A, the second set of network IDs is provided by the upper layer of the user equipment. In some embodiments of method 500A, the second set of network IDs includes a separate non-public network (SNPN) ID, which is equal to the public terrestrial mobile network (PLMN) plus the network ID. In some embodiments of method 500A, the second set of network IDs includes the public terrestrial mobile network (PLMN) ID. In some embodiments of method 500A, the second set of network IDs includes a public network integrated non-public network (PNI-NPN) ID, which is equal to the PLMN plus the closed access group (CAG) ID.

[0111] In some embodiments of method 500A, upon receiving the first message, the method further includes: storing a configuration indicating a request for membership information in a first local variable in the user equipment; after obtaining membership information from one or more neighboring cells, performing a recording operation, wherein the recording operation includes storing the membership information in a second local variable in the user equipment; sending a third message indicating that the membership information is available; and wherein the second message is sent in response to the user equipment receiving a fourth message triggering the user equipment to report membership information. In some embodiments of method 500A, the third message includes a Radio Resource Control (RRC) reconfiguration complete message, an RRC establishment complete message, an RLC recovery complete message, or an RRC re-establishment complete message.

[0112] In some embodiments of method 500A, the membership information in the second message includes the Physical Cell Identifier (PCI) of at least one neighboring cell, the measurement quality result of at least one neighboring cell, the number of Synchronization Signal Blocks (SSBs) received from at least one neighboring cell, or the membership indicator of at least one neighboring cell. In some embodiments of method 500A, the second message includes the Physical Cell Identifier (PCI) of at least one neighboring cell. In some embodiments of method 500A, the first message includes one or more Physical Cell Identifier (PCI) ranges, while the second message includes membership information of one or more neighboring cells having one or more frequencies within one or more PCI ranges. In some embodiments of method 500A, each of the one or more PCI ranges is associated with an Absolute Radio Frequency Channel Number (ARFCN). In some embodiments of method 500A, each of the one or more PCI ranges is associated with a first group of one or more frequencies.

[0113] In some embodiments of method 500A, the first group of one or more frequencies includes any one or more within and between frequencies. In some embodiments of method 500A, the first message is included in a System Information Block (SIB) or a Private Radio Resource Control (RRC) message.

[0114] Figure 5B An exemplary flowchart of method 500B for performing Minimum Drive Test (MDT) is shown. Operation 512 includes: receiving a message from a user equipment (UE) restricting the area where the UE can perform MDT, wherein the UE is configured to operate on a non-public network (NPN), and wherein the message includes: one or more independent non-public network (SNPN) identifiers, the one or more independent non-public network (SNPN) identifiers being equal to a public terrestrial mobile network (PLMN) identifier plus a network identifier; a Closed Access Group (CAG) list, the CAG list including one or more PLMN identifiers associated with the CAG list; a CAG-only indicator, the CAG-only indicator indicating that the UE is requested to perform MDT only on a set of CAGs identified by the CAG list; and a CAG-exclude indicator, the CAG-exclude indicator indicating that the UE is requested to perform MDT on a set of CAG cells, including public cells and CAG cells other than the set of CAG cells identified by the CAG list. Operation 514 includes: performing measurements for MDT based on the message.

[0115] In some embodiments of method 500B, the user equipment is registered under an SNPN network or under a PNI-NPN network. In some embodiments of method 500B, for the PLMN and for the user equipment registered under the PNI-NPN network: the user equipment belongs to a first type of PNI-NPP user equipment, wherein the user equipment is only allowed to camp under a CAG cell, or the user equipment belongs to a second type of PNI NPN user equipment, wherein the user equipment is allowed to camp under both CAG cells and public cells. In some embodiments of method 500B, the user equipment registered under the SNPN network uses one or more SNPN identifiers to restrict the area where the UE performs MDT measurements. In some embodiments of method 500B, the user equipment registered under the PNI-NPN network uses a CAG list, a CAG-only indicator, or a CAG-excluded indicator to restrict the area where the UE performs MDT measurements.

[0116] In some embodiments of method 500B, the user equipment belongs to a first type of PNI-NPN user equipment, wherein the user equipment is only allowed to camp under a CAG cell, and for the PLMN and for the first type of PNI-NPN UE, the UE performs MDT measurements only in one or more cells broadcast as included in one of the CAG IDs in the CAG list. In some embodiments of method 500B, the user equipment belongs to a second type of PNI-NPN user equipment, wherein the user equipment is allowed to camp under both CAG cells and public cells, and for the PLMN and for the second type of PNI-NPN UE, only the CAG indicator instructs the UE to perform MDT measurements only in one or more cells broadcast as included in one of the CAG IDs in the CAG list.

[0117] In some embodiments, method 500B further includes, when it is determined that no CAG-only indication exists for the PLMN and for the second type of PNI-NPN UE, the UE performs MDT measurements in one or more cells broadcast as included in one of the CAG IDs in the CAG list and in public cells under the PLMN. In some embodiments of method 500B, the user equipment is a second type of PNI-NPN user equipment, wherein the user equipment is allowed to camp under CAG cells and public cells, and for the PLMN and for the second type of PNI-NPN UE, a CAG exclusion indicator indicates that the UE will perform MDT measurements on all cells including public cells and CAG cells other than the set of CAG cells identified by the CAG list. In some embodiments of method 500B, the user equipment is a first type of PNI-NPN user equipment, wherein the user equipment is only allowed to camp under CAG cells, and for the PLMN and for the first type of PNI-NPN UE, a CAG exclusion indicator indicates that the UE will perform MDT measurements on all cells including all cells in the allowed CAG cells configured by the upper layer, except for the set of CAG cells identified by the CAG list.

[0118] In some embodiments of method 500B, the message includes a list of global cell identifiers, a list of tracking area codes, and a list of tracking area identifiers. In some embodiments of method 500B, the message is received via dedicated radio resource control (RRC) signaling or broadcast RRC signaling.

[0119] Figure 5CAn exemplary flowchart of a method 500C for identifying the cause of an arbitrary cell selection state is shown. Operation 522 includes: a user equipment performing a first determination that all available frequencies are blocked because one or more cells operating on all available frequencies have the highest or best signal quality and the one or more cells do not belong to a registered network or a selected network. Operation 524 includes: in response to the first determination, performing a second determination to enter an arbitrary cell selection state, in which the user equipment is configured to perform cell selection to find a cell to camp on. Operation 526 includes: recording (e.g., storing or transmitting) information including the identified cause of the arbitrary cell selection state. In some embodiments of method 500C, the identified cause of the arbitrary cell selection state indicates a blocking cause indicating that the user equipment has entered an arbitrary cell selection state in which access to available frequencies is blocked. In some embodiments of method 500C, the identified cause of the arbitrary cell selection state indicates a weak signal indicating that the user equipment is outside coverage. In some embodiments of method 500C, the identified reason for any cell selection state indicates that the user equipment is prohibited from accessing the frequency due to non-access stratum reasons.

[0120] Figure 6 An exemplary block diagram of a hardware platform 600, which may be part of a network node (e.g., a cell or network) or a user equipment, is shown. The hardware platform 600 includes at least one processor 610 and a memory 605 having instructions stored thereon. The instructions executed by the processor 610 configure the hardware platform 600 to perform... Figure 1-5C The operations described herein and the operations in the various embodiments described in this patent application. Transmitter 615 transmits or sends information or data to another node. For example, a network node transmitter may send an SIB message to a user equipment. Receiver 620 receives information or data transmitted or sent by another node. For example, a user equipment may receive a LoggedMeasurementConfiguration message from a network node.

[0121] In this document, the term “exemplary” is used to mean “an example of…” and, unless otherwise stated, does not imply an ideal or preferred embodiment.

[0122] Some embodiments described herein are described in the general context of methods or processes that may be implemented in one embodiment by a computer program product embodied in a computer-readable medium, the computer program product including computer-executable instructions such as program code that are executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile optical disc (DVD), etc. Therefore, the computer-readable medium may include non-transitory storage media. Typically, program modules may include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing the steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents examples of corresponding behaviors for implementing the functionality described in these steps or processes.

[0123] Some of the disclosed embodiments may be implemented using devices or modules that utilize hardware circuitry, software, or a combination thereof. For example, hardware circuitry implementations may include discrete analog and / or digital components integrated, for example, as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs). Some implementations additionally or alternatively include digital signal processors (DSPs), which are dedicated microprocessors with an architecture optimized for the operational requirements of digital signal processing associated with the functions disclosed herein. Similarly, the various components or sub-components within each module may be implemented as software, hardware, or firmware. Connections between modules and / or components within modules may be provided using any of the connection methods and media known in the art, including but not limited to communication via the Internet, wired, or wireless networks using appropriate protocols.

[0124] Although this application contains numerous details, these details should not be construed as limiting the scope of the claimed invention or the content that may be claimed, but rather as descriptions of specific features of particular embodiments. Certain features described herein in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although the foregoing features may be described as operating in a particular combination, and even initially claimed to be so, in some cases one or more features from the claimed combination may be removed from the claimed combination, and the claimed combination may be for sub-combinations or variations thereof. Similarly, although operations are described in a specific order in the drawings, this should not be construed as requiring these operations to be performed in the specific order or sequential sequence shown, or requiring the performance of all illustrated operations to achieve the desired result.

[0125] This document describes only some implementation methods and examples. Other implementation methods, improvements and variations can be made based on the content described and illustrated in this disclosure.

Claims

1. A wireless communication method, comprising: The user equipment receives a message restricting the area where it can perform a minimum drive test (MDT). The user equipment is configured to operate on a non-public network (NPN), and The messages mentioned include: One or more independent non-public network SNPN identifiers, wherein the one or more independent non-public network SNPN identifiers are equal to the public terrestrial mobile network (PLMN) identifier plus the network identifier, or A Closed Access Group (CAG) list, wherein the CAG list includes one or more PLMN identifiers associated with the CAG list; and Based on the message, a measurement is performed on the MDT.

2. The method according to claim 1, wherein, The user equipment is registered under an independent non-public network SNPN, or the user equipment is registered under a non-public network PNI-NPN integrated with a public network.

3. The method according to claim 1 or 2, wherein, User equipment registered under a separate, non-public network (SNPN) uses one or more SNPN identifiers to restrict the area in which the user equipment performs the MDT measurements.

4. The method according to claim 1 or 2, wherein, User equipment registered under a public network integrated with a non-public network (PNI-NPN) uses a CAG list to restrict the area in which the user equipment performs the MDT measurements.

5. The method according to claim 1, wherein, The message includes a list of global cell identifiers, a list of tracking area codes, and a list of tracking area identifiers.

6. The method according to claim 1, wherein, The message was received via Dedicated Radio Resource Control (RRC) signaling.

7. An apparatus for wireless communication, comprising a processor configured to: Receive a message restricting the area where the device performs Minimum Drive Test (MDT). The device is configured to operate on a non-public network (NPN), and The messages mentioned include: One or more independent non-public network SNPN identifiers, wherein the one or more independent non-public network SNPN identifiers are equal to the public terrestrial mobile network (PLMN) identifier plus the network identifier, or Closed Access Group (CAG) list, wherein the CAG list includes one or more PLMN identifiers associated with the CAG list; as well as Based on the message, a measurement is performed on the MDT.

8. The apparatus according to claim 7, wherein, The device is registered under an independent non-public network SNPN, or the device is registered under a public network integrated non-public network PNI-NPN.

9. The apparatus according to claim 7 or 8, wherein, Devices registered under a separate, non-public network SNPN use one or more SNPN identifiers to restrict the area in which the device performs the MDT measurements.

10. The apparatus according to claim 7 or 8, wherein, Devices registered under a public network integrated with a non-public network (PNI-NPN) use a CAG list to restrict the area in which the device performs the MDT measurements.

11. The apparatus according to claim 7, wherein, The message includes a list of global cell identifiers, a list of tracking area codes, and a list of tracking area identifiers.

12. The apparatus according to claim 7, wherein, The message was received via Dedicated Radio Resource Control (RRC) signaling.

13. A computer-readable program storage medium storing code that, when executed by a processor, causes the processor to implement the wireless communication method of any one of claims 1 to 6.

Images