METHODS AND DEVICES FOR ASSISTING CELL RESELECTION AND PAGING

[0001] The present disclosure is directed generally to wireless communications. Particularly, the present disclosure relates to methods for assisting cell reselection and paging.

[0002] Wireless communication technologies are moving the world toward an increasingly connected and networked society. High-speed and low-latency wireless communications rely on efficient network resource management and allocation between user mobile stations and wireless access network nodes (including but not limited to wireless base stations). A new generation network is expected to provide high speed, low latency and ultra-reliable communication capabilities and fulfil the requirements from different industries and users. In order to fulfil the low latency and high reliability requirements for the vertical industry as well as support the new generation network service, a dedicated wireless network, i.e., private network, attracts attention.

[0003] This document relates to methods, systems, and devices for wireless communication, and more specifically, for assisting cell reselection and paging.

[0004] In one embodiment, the present disclosure describes a method for wireless communication. The method includes transferring information of a private network on an interface between a central unit and a distributed unit by performing obtaining the information of the private network; sending a setup request from the distributed unit to the central unit; and sending a setup response based on the setup request from the central unit to the distributed unit.

[0005] In another embodiment, the present disclosure describes another method for wireless communication. The method includes transferring a list of at least one private network identifier (ID), or physical cell identifier (PCI) range information on an interface between a radio access network (RAN) node and a core network (CN) node by performing obtaining the PCI range information; sending the PCI range information from the RAN node to the CN node; and sending paging information from the CN node to the RAN node.

[0006] In another embodiment, the present disclosure describes another method for wireless communication. The method includes transferring a list of at least one private network identifier (ID) or physical cell identifier (PCI) range information on an interface between a source radio access network (RAN) node and a target RAN node by performing sending the list of at least one private network ID or the PCI range information from the source RAN node to the target RAN node.

[0007] In another embodiment, the present disclosure describes another method for wireless communication. The method includes transferring physical cell identifier (PCI) range information in a dedicated signal between a radio access network (RAN) node and a user equipment by performing: obtaining the PCI range information; and sending the dedicated signal from the RAN node to the user equipment, wherein the dedicated signal comprises the PCI range information.

[0008] In another embodiment, the present disclosure describes another method for wireless communication. The method includes receiving, by a user equipment (UE), a dedicated signal comprising physical cell identifier (PCI) range information; replacing, by the UE, previously received PCI range information by the PCI range information in the dedicated signal; using, by the UE, the PCI range information in the dedicated signal to assist cell reselection; determining, by the UE, whether a preset condition has occurred; and in response to determining that the preset condition has occurred, setting, by the UE, the PCI range information in the dedicated signal as invalid.

[0009] In some other embodiments, an apparatus for wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.

[0010] In some other embodiments, a device for wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.

[0011] In some other embodiments, a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods.

[0012] The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.

[0050] The present disclosure will now be described in detail hereinafter with reference to the accompanied drawings, which form a part of the present disclosure, and which show, by way of illustration, specific examples of embodiments. Please note that the present disclosure may, however, be embodied in a variety of different forms and, therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the embodiments to be set forth below.

[0051] Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment” or “in some embodiments” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment” or “in other embodiments” as used herein does not necessarily refer to a different embodiment. The phrase “in one implementation” or “in some implementations” as used herein does not necessarily refer to the same implementation and the phrase “in another implementation” or “in other implementations” as used herein does not necessarily refer to a different implementation. It is intended, for example, that claimed subject matter includes combinations of exemplary embodiments or implementations in whole or in part.

[0052] In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and”, “or”, or “and/or,” as used herein may include a variety of meanings that may depend at least in part upon the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” or “at least one” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a”, “an”, or “the”, again, may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” or “determined by” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.

[0053] The present disclosure describes methods and devices for assisting cell reselection and paging. The present disclosure addresses the issues with existing methods wherein during the reselection by a stand-alone non-public network (SNPN) user equipment (UE), the UE may need to read the master information block/system information block 1 (MIB/SIB1) of the higher ranked cells to check whether these cells are belong to the NPN member and thus may increase UE power consumption and prolong re-selection interval.

[0054] 5G network is expected to provide high speed, low latency and ultra-reliable communication capabilities and fulfil the requirements from different industries and users. In order to fulfil the low latency and high reliability requirements for the vertical industry as well as support 5G LAN-type service, a dedicated wireless network, i.e., private network, attracts attention and may be employed.

[0055] A Non-Public Network (NPN) is a 5GS deployed for non-public use. In one implementation, an NPN may be employed as a Stand-alone Non-Public Network (SNPN), i.e., operated by an NPN operator and not relying on network functions provided by a public land mobile network (PLMN). In another implementation, an NPN may be employed as a Public network integrated NPN, i.e., a non-public network deployed with the support of a PLMN.

[0056] A public network integrated NPN may be made available by means of, e.g., dedicated data network names (DNNs) or by one or more single network slice selection assistance informations (S-NSSAIs) allocated for it. A closed access group (CAG) may be optionally used in order to prevent user equipment (UEs) not allowed to access a public network integrated NPN from accessing the public network integrated NPN. The important enablers for the CAG in the non-access stratum (NAS) layer may include a CAG selection and provisioning of an allowed CAG list and, optionally, an indication that the UE is only allowed to access 5GS via CAG cells from network to UE via the generic UE configuration update procedure.

[0057] The existing non-public network procedures may be limited to support vertical and local area network (LAN) Services, from operator points of view, the solutions of public network integrated NPN may also be applicable for a much wider range of use cases, such as small office home office (SOHO) and residential, private network coverage deployments and so on.

[0058] Enhancements to the 5G system to support NPN may need to introduce new types of network identifiers (ID) for non-public networks, which may include Non-public network ID (NPN ID) and Closed Access Group (CAG) ID. To implement these private network functions on the radio access network (RAN) side, the following features/functions, such as non-public network identification, discovery, selection/reselection and access control, the non-public network related enhancements to mobility restrictions, the non-public network related enhancements to Xn and NG interfaces, may need to be supported.

[0059] The existing issues in the SNPN scenario may be described as below. In the SNPN scenario, the UE may only access the SNPN cell with the matched ID. When a same method is adopted for the SNPN cell, during the reselection, the SNPN UEs may ignore physical cell IDs (PCIs) that out of a reserved PCI range. Then the UE may execute the cell reselection among the cells with the matched PCI, and read the system information to check accessibility. Thus, the UE may need to read the MIB/SIB1 of the higher ranked cells to check whether these cells are belong to the NPN member. This prolonged process may lead to higher UE power consumption and increase re-selection interval.

[0060] The present disclosure describes methods and devices for assisting cell reselection and paging, thus addressing at least one of the existing issues described above.

[0061] FIG. 1 shows a wireless communication system 100 including one or more wireless network node (132 and 134) and one or more user equipment (UE) (152, 154, and 156). The wireless network node may be a base station, which may be a nodeB (NB, e.g., an eNB or gNB) in a mobile telecommunications context. Each of the UE may wirelessly communicate with the wireless network nodes via a plurality of radio channels 140. For example, a first UE 152 may wirelessly communicate with a first wireless network node 132 via a channel including a plurality of radio channels during a certain period of time, and the first UE 152 may also wirelessly communicate with a second wireless network node 134 via a channel including a plurality of radio channels during a certain period of time. Likewise, a second UE 154 and a third UE 156 may wirelessly communicate with the first and second wireless network nodes. The first wireless network node 132 and the second wireless network node 134 may communicate to each other via one or more channel 135.

[0062] In one implementation, referring to FIG. 1, the wireless communication system 100 may include another base station which functions as a central unit (CN) 110. The CN 110 may communicate with one or more wireless network node that functions as a distributed unit (DU) via one or more channel 120.

[0063] FIG. 2 shows an example base station 200. The example base station may include radio Tx/Rx circuitry 208 to receive and transmit with UEs and/or other base stations. The base station may also include network interface circuitry 209 to communicate the base station with other base stations and/or a core network, e.g., optical or wireline interconnects, Ethernet, and/or other data transmission mediums/protocols. The base station 200 may optionally include an input/output (I/O) interface 206 to communicate with an operator or the like.

[0064] The base station may also include system circuitry 204. System circuitry 204 may include processor(s) 221 and/or memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for the one or more of the processors 124 to preform the functions of the base station. The parameters 228 may include parameters to support execution of the instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and/or other parameters.

[0065] FIG. 3 shows an example UE 300. The UE 300 may be a mobile device, for example, a smart phone. The UE 300 may include communication interfaces 302, a system circuitry 304, an input/output interfaces (I/O) 306, a display circuitry 308, and a storage 309. The display circuitry may include a user interface 310. The system circuitry 304 may include any combination of hardware, software, firmware, or other logic/circuitry. The system circuitry 304 may be implemented, for example, with one or more systems on a chip (SoC), application specific integrated circuits (ASIC), discrete analog and digital circuits, and other circuitry. The system circuitry 304 may be a part of the implementation of any desired functionality in the UE 300. In that regard, the system circuitry 304 may include logic that facilitates, as examples, decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user inputs; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections for, as one example, internet connectivity; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310. The user interface 310 and the inputs/output (I/O) interfaces 306 may include a graphical user interface, touch sensitive display, haptic feedback or other haptic output, voice or facial recognition inputs, buttons, switches, speakers and other user interface elements. Additional examples of the I/O interfaces 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input/output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0066] Referring to FIG. 3, the communication interfaces 302 may include a Radio Frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 which handles transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceivers may be wireless transceivers that include modulation/demodulation circuitry, digital to analog converters (DACs), shaping tables, analog to digital converters (ADCs), filters, waveform shapers, filters, pre-amplifiers, power amplifiers and/or other logic for transmitting and receiving through one or more antennas, or (for some devices) through a physical (e.g., wireline) medium. The transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As one specific example, the communication interfaces 302 may include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA)+, and 4G/Long Term Evolution (LTE) standards. The techniques described below, however, are applicable to other wireless communications technologies whether arising from the 3rd Generation Partnership Project (3GPP), GSM Association, 3GPP2, IEEE, or other partnerships or standards bodies.

[0067] Referring to FIG. 3, the system circuitry 304 may include one or more processors 321 and memories 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to carry out desired functionality for the UE 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G or other data that the UE 300 will send, or has received, through the communication interfaces 302. In various implementations, a system power for the UE 300 may be supplied by a power storage device, such as a battery or a transformer.

[0068] The present disclosure describes several below embodiments, which may be implemented, partly or totally, on the network base station and/or the user equipment described above.

[0069] The present disclosure describe an embodiment of a method for transferring information of a stand-alone non-public network (SNPN) on an interface between a central unit (CU) and a distributed unit (DU). The method may be performed by a network including the CU and the DU. the network may optionally include more than one DUs.

[0070] Referring to FIG. 4A, the method 400 may include step 410: obtaining the information of the SNPN; step 420; sending a request from the distributed unit to the central unit; and step 430: sending a response based on the request from the central unit to the distributed unit.

[0071] Referring to FIG. 5, a DU may include a gNB-DU 510, and a CU may include a gNB-CU 520. The gNB-DU 510 may send a F1 setup request 530 to the gNB-CU 520. The F1 setup request may include a first portion of the information of the SNPN. For one example, the F1 setup request may include at least one elements in Table 1. The gNB-CU 520 may send a F1 setup response 540 to the gNB-DU 510. The F1 setup response may depend on the F1 setup request. The F1 setup response may include a second portion of the information of the SNPN. For one example, the F1 setup response may include at least one elements in Table 2.

TABLE 1
An example of F1 Setup Request
			IE type and	Semantics
IE/Group Name	Presence	Range	reference	description
NR CGI	M		9.3.1.12
. . .
. . .
. . .
Served SNPNs		1 . . . <maxnoofB		Broadcast
		SNPNs>		SNPNs
>PLMN Identity	M		9.3.1.14
>SNPN NID list
Served CAG List		1 . . . <maxnoofB		Broadcast
		CAGs>		CAGs
>PLMN Identity	M		9.3.1.14
>CAG ID list
Neighbor SNPNs		1 . . . <maxnoofN		Neighbor
		SNPNs>		SNPNs
>PLMN Identity	M		9.3.1.14
>SNPN NID list
Neighbor CAG		1 . . . <maxnoofN		Neighbor
List		CAGs>		CAGs
>PLMN Identity	M		9.3.1.14
>CAG ID list

[0072] Referring to FIG. 4B, the method 400 may optionally include step 440: transferring an configuration update message on the interface between the central unit and the distributed unit. The configuration update message may include same or different information as the setup request or the setup response.

TABLE 2
An example of F1 Setup Response
			IE type and	Semantics		Assigned
IE/Group Name	Presence	Range	reference	description	Criticality	Criticality
Message Type	M		9.3.1.1		YES	reject
Transaction ID	M		9.3.1.23		YES	reject
gNB-CU Name	O		PrintableString	Human readable	YES	ignore
			(SIZE(1..150,...))	name of the
				gNB-CU.
Cells to be Activated		0.. 1			YES	reject
List
>Cells to be		1..		List of cells to be	EACH	reject
Activated List Item		<maxCellingNBDU>		activated
...
>>Available	O				YES	ignore
SNPN List
>>Available CAG	O				YES	ignore
List

[0073] In step 410, as shown in Tables 1 and 2, the information of the SNPN may include at least one of the following:

[0074] SNPN identifier (SNPN ID) information for at least one served cell,

[0075] SNPN ID information for at least one neighbor cell,

[0076] physical cell identifier (PCI) information for the SNPN, or

[0077] synchronisation signal block measurement timing configuration (SMTC) information for the SNPN.

[0078] In one implementation, the PCI information for the SNPN may include information for each SNPN ID, or information for all SNPN cells.

[0079] In another implementation, the PCI information for the SNPN may include PCI range information, for example, a list of PCIs, a range of PCIs, or a list of ranges of PCIs. For one example, the PCI range information may include PCI range for all of the SNPN as shown in Table 3. For another example, the PCI range information may include range information for each SNPN ID as shown in Table 4.

TABLE 3
PCI range for all of the SNPN
			IE type and	Semantics
IE/Group Name	Presence	Range	reference	description
PCI Range for SNPN	O

TABLE 4
PCI range per SNPN ID
			IE type and	Semantics
IE/Group Name	Presence	Range	reference	description
PCI Range list for SNPN	O
>PCI Range list for	1 . . .
SNPN item	<maxSNPN
	ID>
>>SNPN ID
>>PCI Range

[0080] Referring to FIG. 4C, the method 400 may optionally include step 450: configuring the PCI information based on at least one of a list of information. In one implementation, the PCI information may be configured as common for all SNPN cells. In another implementation, the PCI information may be configured for an SNPN ID, a public land mobile network identifier (PLMN ID), or a combination of an SNPN ID and a PLMN ID. In another implementation, the PCI information may be configured for a frequency as common for all SNPN cells on the frequency. In another implementation, the PCI information may be configured for a frequency for an SNPN ID, a PLMN ID, or a combination of an SNPN ID and a PLMN ID on the frequency.

[0081] In another implementation, the PCI information may be configured in a positive way. The positive way may mean a list of PCIs which are allowed and capable cell. For example, the PCI information may be configured to include a PCI or a list of PCIs of an SNPN capable cell.

[0082] In another implementation, the PCI information may be configured in a negative way. The negative way may mean a list of PCIs which are not-allowed or non-capable cell. For example, the PCI information may be configured to include a PCI or a list of PCIs of an SNPN non-capable cell.

[0083] Referring to FIG. 4D, the method 400 may optionally include step 460: providing the SNPN ID information. In one implementation, the SNPN ID information may include more than one SNPN IDs for each cell, or for each PLMN and each cell. In another implementation, the SNPN ID information may include one or more SNPN ID for each PLMN.

[0084] Referring to step 420 in FIG. 4A, when a distributed unit sends a setup request or a configuration update message to a central unit, the distributed unit may indicate at least one of the following to the central unit:

[0085] at least one served SNPN,

[0086] at least one available SNPN,

[0087] the PCI information for the SNPN, or

[0088] the SMTC information for the SNPN.

[0089] Referring to step 430 in FIG. 4A, when a central unit sends a setup response or a configuration update message to a distributed unit, the central unit may indicate or update at least one of the following to the distributed unit:

[0090] at least one served SNPN,

[0091] at least one available SNPN,

[0092] the PCI information for the SNPN, or

[0093] the SMTC information for the SNPN.

[0094] Referring to FIG. 4E, the method 400 may optionally include step 470: sending paging information from a central unit to a distributed unit. In one implementation, the paging information comprises at least one of the following:

[0095] the PCI information,

[0096] the SNPN ID, or

[0097] a list of at least one SNPN ID.

[0098] The present disclosure describes another embodiment of a method for transferring information of a closed access group (CAG) on an interface between a central unit (CU) and a distributed unit (DU). In one implementation, this embodiment may be implemented on a same network as the previous embodiment and work together with the previous embodiment. In another implementation, this embodiment may be implemented on a different network as the previous embodiment and may work independently from the previous embodiment. In another implementation, this embodiment may be implemented on a same network as the previous embodiment and may work parallel to the previous embodiment.

[0099] Referring to FIG. 6A, a method 600 for transferring information of a closed access group (CAG) on an interface between a central unit (CU) and a distributed unit (DU) may further include step 610: obtaining the information of a closed access group (CAG); step 620; sending a setup request from the distributed unit to the central unit; and step 630: sending a setup response based on the setup request from a central unit (CU) to a distributed unit (DU).

[0100] Referring to FIG. 5, a DU may include a gNB-DU 510, and a CU may include a gNB-CU 520. The gNB-DU 510 may send a F1 setup request 530 to the gNB-CU 520. The F1 setup request may include a first portion of the information of the CAG. For one example, the F1 setup request may include at least one elements in Table 1. The gNB-CU 520 may send a F1 setup response 540 to the gNB-DU 510. The F1 setup response may depend on the F1 setup request. The F1 setup response may include a second portion of the information of the CAG. For one example, the F1 setup response may include at least one elements in Table 2.

[0101] Referring to FIG. 6B, the method 600 may optionally include step 640: transferring an configuration update message on the interface between the central unit and the distributed unit. The configuration update message may include same or different information as the setup request or the setup response.

[0102] In step 610, as shown in Tables 1 and 2, the information of the CAG may include at least one of the following:

[0103] CAG identifier (CAG ID) information for each public land mobile network (PLMN) for each served cells,

[0104] CAG ID information for each PLMN for at least one neighbor cell,

[0105] physical cell identifier (PCI) information for the CAG, or

[0106] synchronisation signal block measurement timing configuration (SMTC) information for the CAG.

[0107] In one implementation, the PCI information for the CAG may include information for each CAG ID, or information for all CAG cells.

[0108] In another implementation, the PCI information for the CAG may include PCI range information, for example, a list of PCIs, a range of PCIs, or a list of ranges of PCIs. For one example, the PCI range information may include PCI range for all of the CAG as shown in Table 5. For another example, the PCI range information may include range information for each CAG ID as shown in Table 6.

TABLE 5
PCI range for all of the CAG
			IE type and	Semantics
IE/Group Name	Presence	Range	reference	description
PCI Range for CAG	O

TABLE 6
PCI range per CAG ID
			IE type and	Semantics
IE/Group Name	Presence	Range	reference	description
PCI Range list for CAG	O
>PCI Range list for	1 . . .
CAG item	<maxCAG
	ID>
>> CAG	ID
>>PCI Range

[0109] Referring to FIG. 6C, the method 600 may optionally include step 650: configuring the PCI information based on at least one of a list of information. In one implementation, the PCI information may be configured as common for all CAG cells. In another implementation, the PCI information may be configured for a CAG ID, a public land mobile network identifier (PLMN ID), or a combination of a CAG ID and a PLMN ID. In another implementation, the PCI information may be configured for a frequency as common for all CAG cells on the frequency. In another implementation, the PCI information may be configured for a frequency for a CAG ID, a PLMN ID, or a combination of a CAG ID and a PLMN ID on the frequency.

[0110] In another implementation, the PCI information may be configured in a positive way. The positive way may mean a list of PCI of allowed and capable cell. For example, the PCI information may be configured to include a PCI or a list of PCIs of a CAG capable cell.

[0111] In another implementation, the PCI information may be configured in a negative way. The negative way may mean a list of PCI of not-allowed or non-capable cell. For example, the PCI information may be configured to include a PCI or a list of PCIs of a CAG non-capable cell.

[0112] Referring to step 620 in FIG. 6A, when a distributed unit sends a setup request or a configuration update message to a central unit, the distributed unit may indicate at least one of the following to the central unit:

[0113] at least one served CAG of each cell,

[0114] at least one served CAG of each PLMN,

[0115] at least one available CAG of each cell,

[0116] at least one available CAG of each PLMN,

[0117] the PCI information for the CAG, or

[0118] the SMTC information for the CAG.

[0119] Referring to step 630 in FIG. 6A, when a central unit sends a setup response or a configuration update message to a distributed unit, the central unit may indicate or update at least one of the following to the distributed unit:

[0120] at least one served CAG of each cell,

[0121] at least one served CAG of each PLMN,

[0122] at least one available CAG of each cell,

[0123] at least one available CAG of each PLMN,

[0124] the PCI information for the CAG, or

[0125] the SMTC information for the CAG

[0126] Referring to FIG. 6D, the method 600 may optionally include step 660: sending paging information from a central unit to a distributed unit. In one implementation, the paging information comprises at least one of the following:

[0127] the PCI information,

[0128] the CAG ID, or

[0129] a list of at least one CAG ID.

[0130] In another embodiment, the method 400 may include one or more steps in the method 600. For example, a portion of or all steps in the method 600 may be implemented on a same network as the method 400 and may be a part of the method 400. It is understood that this embodiment is merely an example rather than a limitation.

[0131] The present disclosure describes an embodiment of a method for transferring a list of at least one SNPN ID, a list of at least one allowed closed access group (CAG), and physical cell identifier (PCI) range information on an interface between a radio access network (RAN) node and a core network (CN) node.

[0132] Referring to FIG. 7, one embodiment of a method 700 may include step 710: obtaining the PCI range information; step 720: sending the PCI range information from the RAN node to the CN node; and step 730: sending paging information from the CN node to the RAN node.

[0133] Referring to FIG. 8, another embodiment of a method 800 may include step 810: obtaining the PCI range information; step 815: determining whether dedicated signal includes the PCI range information; step 820: in response to determining that dedicated signal includes the PCI range information, sending the PCI range information from the RAN node to the CN node; and step 830: sending paging information from the CN node to the RAN node.

[0134] In one implementation, the PCI range information may include information for each SNPN ID, or information for all SNPN cells. Optionally, the PCI range Information may include a list of PCIs, a range of PCIs, or a list of ranges of PCIs.

[0135] In another implementation, the PCI range information may include a PCI range of each network identifier, or a PCI range for each network type. A network identifier may include an SNPN identifier, or a CAG identifier; and a network type may include an SNPN type, or a CAG type.

[0136] Optionally, the PCI information is provided based on at least one of the following:

[0137] the PCI information is provided as common for all SNPN cells,

[0138] the PCI information is provided for an SNPN ID, a public land mobile network identifier (PLMN ID), or a combination of an SNPN ID and a PLMN ID,

[0139] the PCI information is provided for a frequency as common for all SNPN cells on the frequency, or

[0140] the PCI information is provided for a frequency for an SNPN ID, a PLMN ID, or a combination of an SNPN ID and a PLMN ID on the frequency.

[0141] Referring to either Step 720 in FIG. 7 or Step 820 in FIG. 8, a RAN node may send PCI range information to a CN. As shown in FIG. 9A, in 950, a RAN node 910 may send a path switch with PCI range information to a CN 920. The RAN node 910 may indicate the PCI range information to the CN 920 in response to a determination that the RAN node indicates the PCI range information is included in the dedicated signal. Optionally in another implementation, in 960, the RAN node 910 may send the PCI range information in dedicated signal to a user equipment (UE) 930.

[0142] Referring to either Step 730 in FIG. 7 or Step 830 in FIG. 8, a CN node may send paging information to a RAN node. As shown in FIG. 9B, in 970, a CN node 920 may send paging information with PCI range information to a RAN node 910. The CN node 920 may indicate the PCI range information to the RAN node 910 when the paging information is sent to the RAN node. Optionally in another implementation, the paging information may include a list of allowed CAG or eSNPN.

[0143] The present disclosure describes an embodiment of a method for transferring a list of at least one SNPN ID, a list of at least one allowed closed access group (CAG), or physical cell identifier (PCI) range information on an interface between a source radio access network (RAN) node and a target RAN node.

[0144] In one implementation, the PCI range information may include information for each SNPN ID, or information for all SNPN cells. Optionally, the PCI range Information may include a list of PCIs, a range of PCIs, or a list of ranges of PCIs.

[0145] In another implementation, the PCI range information may include a PCI range of each network identifier, or a PCI range for each network type. A network identifier may include an SNPN identifier, or a CAG identifier; and a network type may include an SNPN type, or a CAG type.

[0146] Referring to FIG. 10A, the method 1000 may include step 1010: sending the list of at least one SNPN, the list of at least one allowed CAG, or the PCI range information from the source RAN node to the target RAN node. In one implementation during a handover procedure between the source RAN node and the target RAN node, Step 1010 may include sending the list of at least one SNPN, the list of at least one allowed CAG, or the PCI range information from the source RAN node to the target RAN node. In another implementation when the target RAN node retrieves user equipment (UE) context from the source RAN node, Step 1010 may include sending the list of at least one SNPN, the list of at least one allowed CAG, or the PCI range information from the source RAN node to the target RAN node.

[0147] Referring to FIG. 10B, the method 1000 may optionally include step 1020: sending new PCI range information from the target RAN node to a UE. Referring to FIG. 10C, the method 1000 may optionally include step 1030: sending paging information from a RAN node to one or more other RAN nodes according to the list of at least one SNPN, the list of at least one allowed CAG, or the PCI range information.

[0148] Referring to Step 1010 in FIG. 10A, a source node may send information to a target code, and the information may include the list of at least one SNPN, the list of at least one allowed CAG, or the PCI range information.

[0149] Referring to FIG. 11, in 1170, when a target RAN node 1110 retrieves UE context from a source RAN node 1120, the source RAN node 1120 may indicate to the target RAN node 1110 the eSNPN list/SNPN ID, allowed CAG lit or PCI range information. Optionally in one implementation, before the target RAN node 1110 retrieves the UE context response, in 1160, the target RAN node 1110 may send the retrieve UE context request to the source RAN node 1120. Optionally in another implementation, in 1150, a UE 1130 may send RRC resume request to the target RAN node 1110. Optionally in another implementation, the target node 1110 may indicate new PCI information to the UE; and when the target RAN node 1110 fails to indicate the new PCI information to the UE 1130, in 1180, the target node 1110 may send RAN paging on the cells according to the eSNPN list/SNPN ID, the allowed CAG list, or the PCI range information.

[0150] Referring to FIG. 12, in 1250, a first node 1210 may send paging information to a second node. The paging information may include PCI information, CAG information, or SNPN information. The first node 1210 and the second node 1220 may respectively include CU and DU, gNB1 and gNB2, CN and gNB, CU-user plan (UP) and CU-control plane (CP), CN and eLTE node, eLTE node 1 and eLTE node 2.

[0151] The present disclosure describes an embodiment of a method for transferring physical cell identifier (PCI) range information in dedicated signal between a radio access network (RAN) node and a user equipment (UE).

[0152] Referring to FIG. 13, the method 1300 may include step 1310: obtaining the PCI range information; step 1320: sending the dedicated signal from the RAN node to the user equipment, wherein the dedicated signal comprises the PCI range information.

[0153] In one implementation, the dedicated signal may include a radio resource control (RRC) release message (or RRCRelease Msg). Optionally in another implementation, the PCI range information may include a PCI range for an intra-frequency or at least one inter-frequencies.

[0154] One example of RRC release message may include a PCI range on a current frequency for an intra-frequency:

-- ASN1START
-- TAG-RRCRELEASE-START
RRCRelease ::=	SEQUENCE {
rrc-TransactionIdentifier	,
criticalExtensions	CHOICE {
rrcRelease	RRCRelease-IEs,
criticalExtensions Future	SEQUENCE { }
}
}
RRCRelease-IEs ::=	SEQUENCE{
...
nonCriticalExtension	RRCRelease-v1540-IEs
OPTIONAL
}
RRCRelease-v1540-IEs ::=	SEQUENCE {
waitTime	RejectWaitTime
OPTIONAL, -- Need N
nonCriticalExtension	RRCRelease-v16xy-IEs
OPTIONAL
}
RRCRelease-v16xy-IEs ::=	SEQUENCE {
physCellIdRangePhysCellIdRange	OPTIONAL, --Cond NPN
nonCriticalExtension	SEQUENCE { }
OPTIONAL
}
PhysCellIdRange ::=SEQUENCE {
startPhysCellId,
rangeENUMERATED {
n2,n4, n8, n12, n16, n24, n32, n48, n64, n84,
n96, n128, n168, n252, n504, n1008,spare2,
spare1} }
...
-- TAG-RRCRELEASE-STOP
-- ASN1STOP

[0155] Another example of RRC release message may include a PCI range on at least one different frequency, i.e., for at least one inter-frequencies:

-- ASN1START
-- TAG-RRCRELEASE-START
RRCRelease ::=	SEQUENCE {
rrc-TransactionIdentifier	,
criticalExtensions	CHOICE {
rrcRelease	RRCRelease-IEs,
criticalExtensions Future	SEQUENCE { }
}
}
RRCRelease-IEs ::=	SEQUENCE {
...
nonCriticalExtension	RRCRelease-v1540-IEs
OPTIONAL
}
RRCRelease-v1540-IEs ::=	SEQUENCE {
waitTime	RejectWaitTime
OPTIONAL, -- Need N
nonCriticalExtension	RRCRelease-v16xy-IEs
OPTIONAL
}
RRCRelease-v16xy-IEs ::=	SEQUENCE {
physCellIdRangeListPhysCellIdRangeList   OPTIONAL, --Cond
NPN
nonCriticalExtension	SEQUENCE { }
OPTIONAL
}
PhysCellIdRangeList ::= SEQUENCE (SIZE (1..maxFreq)) OF
PhysCellIdRange OPTIONAL, --Cond NPN
PhysCellIdRange ::=SEQUENCE {
carrierFreq	ARFCN-ValueNR,
startPhysCellId,
rangeENUMERATED {
n2, n4, n8, n12, n16, n24, n32, n48, n64, n84,
n96, n128, n168, n252, n504, n1008,spare2,
spare1} }
}
...
-- TAG-RRCRELEASE-STOP
-- ASN1STOP

[0156] As shown in the above examples, a size of the PCI range may be enumerated, for example 2 cells for n2, 4 cells for n4, 48 cells for n48, and etc. The PCI range may include a list of PCIs, a range of PCIs, or a list of ranges of PCIs. For one example, when the cell begins at cell 1 and a size of a PCI range is n2, the PCI range is cell 1 and cell 2. For another example, when the cell begins at cell 3 and a size of a PCT range is n4, the PCI range is cell 2, cell 3, cell 4, and cell 5.

[0157] The present disclosure describes an embodiment of a method for receiving PCI range information in dedicated signal by a user equipment (UE). The method may be performed by a UE, for example, a smart phone.

[0158] Referring to FIG. 14, the method 1400 may include step 1410: receiving, by a user equipment (UE), a dedicated signal comprising physical cell identifier (PCI) range information; step 1420: replacing, by the UE, previously received PCI range information by the PCI range information in the dedicated signal, and step 1430: using, by the UE, the PCI range information in the dedicated signal to assist cell reselection, and step 1440: determining, by the UE, whether a preset condition has occurred; step 1450: in response to determining that the preset condition has occurred, setting, by the UE, the PCI range information in the dedicated signal as invalid.

[0159] Referring to step 1420 and/or step 1430, when any of the preset conditions has not occurred, the UE is configured to replace any previously received PCI range information with the PCI range information in the dedicated signal, and is configured to use the PCI range information in the dedicated signal to assist the cell reselection.

[0160] Referring to FIG. 17, the present disclosure describes one implementation for step 1420. In 1730, a UE 1720 may receive system information. The system information may be sent by a RAN node 1710. For example, the system information may include a PCI range 1 on a first frequency (f1) and a PCI range 2 on a second frequency (f2). At 1732, the present PCI range information for the UE may include the PCI range 1 on f1 and PCI range 2 on f2.

[0161] In 1740, the UE may receive dedicated signal as RRC release message. The RRC release message may be sent by the RAN node 1710. For example, the RRC release message may include a PCI range 3 on f1 and a PCI range 4 on f2. In response to receiving the dedicated signal, the UE may delete or ignore the previously received PCI range 1 on f1 and PCI range 2 on f2, and may replace the present PCI range information with the PCI range 3 on f1 and PCI range 4 on f2. Then, the UE may use the PCI range 3 on f1 and PCI range 4 on f2 for the cell reselection on f1 and f2 respectively.

[0162] Referring to FIG. 15, step 1430 of using, by the UE, the PCI range information in the dedicated signal to assist cell reselection may include step 1510: setting, by the UE, a range of PCIs in the PCI range information as candidate cells; step 1520: obtaining, by the UE, ranking information for each cell in the candidate cells; step 1530: ranking, by the UE, the candidate cells based on the ranking information and check the accessibility from the best ranked cell, ignore the cell from the candidates to obtain modified candidate cells when it fails the accessibility check; and step 1540: obtaining, by the UE, a cell with best rank in the modified candidate cells and matched private network ID (e.g., SNPN ID or CAG ID) as the cell reselection.

[0163] Referring to step 1520 in FIG. 15, the ranking information may include one or more physical and/or environmental parameters for a cell. For example, the ranking information may include a physical signal strength and signal quality of the cell.

[0164] Referring to step 1530 in FIG. 15, in one implementation, when a UE performs step 1530 and finds any unsuitable cell, the UE may record the status of the unsuitable cell, for example setting up a status flag for the unsuitable cell. Then, the UE may exclude the known unsuitable cell from the candidate cells during ranking process to save time. In another implementation, the UE may exclude the known unsuitable cell from obtaining ranking information to save time and improve efficiency.

[0165] An unsuitable cell may include any cell not in member cells of a stand-alone non-public network (SNPN), may also include any cell not in the member cells of an allowed closed access group (CAG), or may include any cell not allowed to access by the UE. Referring to FIG. 16A, step 1530 may optionally further include step 1610: for any CAG cell that is known by the UE not to be a CAG member cell, excluding the CAG cell from the candidate cells during ranking the candidate cells. Referring to FIG. 16B, step 1530 may optionally further include step 1620: for any SNPN cell that is known by the UE not to be a member cell of the SNPN, excluding the SNPN cell from the candidate cells during ranking the candidate cells. Referring to FIG. 16C, step 1530 may optionally further include step 1630: for any SNPN cell that is known by the UE not allowed to access, excluding the SNPN cell from the candidate cells during ranking the candidate cells.

[0166] Referring to FIGS. 18A-18C, the present disclosure describes one example of the method 1400 for a UE which is configured to use PCI range information to assist intra-frequency cell reselection. In FIG. 18A, the UE may receive a PCI range 1810 in PCI range information of from 1 to 4 (i.e., PCI=1, 2, 3, and 4) on a current frequency (for example, frequency 0) from cell 1 which enters into an idle or inactive state. The present PCI range on the UE may be the PCI range from 1 to 4.

[0167] Referring to FIG. 18B, the UE may trigger an intra-frequency reselection and the UE may detect a range 1820 of cells from 2 to 10 (i.e., PCI=2, 3, 4, 5, 6, 7, 8, 9, and 10). The UE may set the PCI range in the PCI range information as candidate cells, and thus set the PCI range from cell 2 to cell 4 ((i.e., PCI=2, 3, and 4) as the candidate cells 1825 because the detected cell 2, cell 3, and cell 4 are in the PCI range 1810 in the PCI range information.

[0168] After the UE sets the candidate cells 1825, the UE may obtain ranking information for each cell in the candidate cells 1825. For example, the UE may obtain or calculate the ranking information of cell 2, cell 3, and cell 4, and may find that cell 4 is highest ranked. The UE may read a master information block/system information block 1 (MIB/SIB1). For example, referring to FIG. 18C, when the UE obtains that cell 4 does not broadcast a matched network ID, the UE may ignore cell 4 or remove cell 4 from the candidate cells to obtain modified candidate cells 1835, and then the UE may move on to evaluate reselection based on ranking information from the modified candidate cells 1835, for this example, between cell 2 and cell 3.

[0169] Optionally, in one implementation, when the UE reselects cell 2 and triggers the intra-frequency reselection, the UE may exclude cell 4 from the candidate cells during ranking the candidate cells, because cell 4 is known by the UE not to be a member cell of the SNPN. In this implementation, the UE only obtain or calculate ranking information for cell 1 and cell 3.

[0170] Referring to FIGS. 19A-19B, the present disclosure describes one example of the method 1400 for a UE, which uses PCI range information to assist inter-frequency cell reselection. In FIG. 19A, the UE may receive PCI range information from cell 1 on a frequency 0. The PCI range information may include a PCI range 1911 from 4 to 5 (i.e., PCI=4 and 5) on a frequency 1 and a PCI range 1912 from 4 to 7 (i.e., PCI=4, 5, 6, and 7) on a frequency 2. Cell 1 on the frequency 0 may enter into an idle or inactive state. The present PCI range on the UE may be the PCI range 1911 on the frequency 1 and the PCI range 1912 on the frequency 2.

[0171] Referring to FIG. 19B, the UE may trigger an inter-frequency reselection and the UE may detect a range 1921 of cells from 2 to 10 (i.e., PCI=2, 3, 4, 5, 6, 7, 8, 9, and 10) on the frequency 1 and a range 1922 of cells from 3 to 10 (i.e., PCI=3, 4, 5, 6, 7, 8, 9, and 10) on the frequency 2. On the frequency 1, the UE may set cell 4 and cell 5 as candidate cells, because the detected cell 4 and cell 5 are in the PCI range 1911 in the PCI range information. On the frequency 2, the UE may set cell 4, cell 5, cell 6, and cell 7 as candidate cells, because the detected cell 4, cell 5, cell 6, and cell 7 are in the PCI range 1912 in the PCI range information.

[0172] Referring to step 1420 in FIG. 14, the preset condition may include whether a timer (for example, a validity timer) expires, whether a new public land mobile network (PLMN) or SNPN selection is performed on a request by a non-access stratum (NAS), or whether the UE changes a current state.

[0173] FIG. 20A shows one example wherein the UE determines whether a validity timer expires. In 2030, a UE 2020 may receive a RRC release message. The RRC release message may include PCI range information. The RRC release message may be sent by a RAN node 2010. In response to receiving the RRC release message, in 2040, the UE may store the PCI range information and begin/start a timer (or a validity timer). The UE may include a timer threshold, which may be a per-determined value or an adjustable value based on current conditions of the UE and/or the RAN node. The current conditions may include a data transmission rate, an idle rate, etc. The timer threshold may be, for example but not limited to, one millisecond, ten milliseconds, one second, and ten seconds. In 2045, when the timer reaches the timer threshold, the timer expires. In 2080, in response to determining that the timer expires, the UE may delete the PCI range information.

[0174] FIG. 20B shows one example wherein the UE determines whether a new public land mobile network (PLMN) or SNPN selection is performed on a request by a non-access stratum (NAS). In 2030, the UE 2020 may receive a RRC release message. The RRC release message may include PCI range information. The RRC release message may be sent by a RAN node 2010. In response to receiving the RRC release message, in 2040, the UE may store the PCI range information and begin/start a timer (or a validity timer). In 2055, the UE may receive a PLMN/SNPN selection from a NAS layer, and the new PLMN/SNPN selection may be requested by the NAS. In 2090, in response to determining that a new PLMN/SNPN selection is requested from the NAS, the UE may stop the validity timer and delete the PCI range information.

[0175] FIG. 20C shows one example wherein the UE determines whether the UE changes a current state. In 2030, the UE 2020 may receive a RRC release message. The RRC release message may include PCI range information. The RRC release message may be sent by a RAN node 2010. In response to receiving the RRC release message, in 2040, the UE may store the PCI range information and begin/start a timer (or a validity timer). In 2065, the UE may changes the current state, for example, entering into a RRC connected state in response to that NAS/AS layer triggers a procedure. In 2090, in response to determining that the UE changes the current state, the UE may stop the validity timer and delete the PCI range information. Optionally, in 2070, the UE 2020 may communicate with the RAN node 2010 related to RRC setup or resume procedure.

[0176] The present disclosure describes methods, apparatus, and computer-readable medium for wireless communication. The present disclosure addressed the issues with performing cell reselection and paging. The methods, devices, and computer-readable medium described in the present disclosure may facilitate the performance of cell reselection and paging. The methods, devices, and computer-readable medium described in the present disclosure may also reduce UE's power consumption and time needed to perform cell reselection and paging, thus improving efficiency and overall performance. The methods, devices, and computer-readable medium described in the present disclosure may improves the overall efficiency of the wireless communication systems.

[0177] Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present solution should be or are included in any single implementation thereof. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of the features and advantages, and similar language, throughout the specification may, but do not necessarily, refer to the same embodiment.

[0178] Furthermore, the described features, advantages and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. One of ordinary skill in the relevant art will recognize, in light of the description herein, that the present solution can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.