JP2024512734A - Methods and mechanisms for slice-based cell reselection - Google Patents

Abstract

A method and mechanism for slice-based cell reselection. Systems, methods, apparatus, and computer program products for cell reselection are provided. One method includes receiving radio mapping information between tracking area identifiers of tracking areas adjacent to the served cell and a list of physical cell identifiers associated with each tracking area associated with physical cell identifiers corresponding to adjacent cells of the served cell. may include doing. Slice assist information includes one or more network slices and one or more tracking area identifiers of a tracking area within a user equipment registration area, or a tracking area adjacent to a user equipment registration area that supports one or more network slices. may be received from a network entity associated with the device mapping at least one of the one or more tracking area identifiers of the device. Radio mapping information and slice assist information may be used in the cell reselection process. [Selection diagram] Figure 2

Description

Some example embodiments generally apply to mobile communications systems such as Long Term Evolution (LTE), fifth generation (5G) radio access technologies (RATs), new radio access technologies (NR), and/or other communication systems. or may relate to wireless telecommunications systems. For example, certain example embodiments may relate to systems and/or methods for cell reselection.

Examples of mobile or wireless communication systems include 5G RAT, Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro , NR access technology, and/or the MulteFire Alliance. 5G wireless systems refer to the next generation (NG) of wireless systems and network architectures. 5G systems are typically built on 5G NR, but 5G (or NG) networks may also be built on E-UTRA radios. NR is expected to be able to support service categories such as Enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), and Massive Machine Type Communications (mMTC). NR is expected to provide extreme broadband, ultra-robust and low-latency connectivity, and massive networking to support the Internet of Things (IoT). Next Generation Radio Access Network (NG-RAN) stands for 5G RAN and can provide NR, LTE, and LTE-A radio access. 5G nodes that provide radio access functionality to user equipment (e.g., similar to UTRAN Node Bs or LTE Evolved Node Bs (eNBs)), when built with NR radio, are called Next Generation Node Bs (gNBs). Note that when built with E-UTRA radios, it may be referred to as a Next Generation eNB (NG-eNB).

For a proper understanding of the exemplary embodiments, please refer to the accompanying drawings.
FIG. 1 is a diagram illustrating an example of the format of single network slice selection support information. FIG. 2 is an illustration of an example signaling diagram in accordance with certain embodiments. FIG. 3 is an illustration of an example flow diagram of a method in accordance with various embodiments. FIG. 4 shows an example of a flow diagram of another method according to some embodiments. FIG. 5 is an illustration of an example flow diagram of another method according to an embodiment. It is a figure which shows an example. FIG. 6 is a diagram illustrating examples of various network devices according to some embodiments. FIG. 7 is a diagram illustrating an example 5G network and system architecture according to an embodiment.

It will be readily appreciated that the components of certain exemplary embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Accordingly, the following detailed description of several exemplary embodiments of systems, methods, apparatus, and computer program products for cell reselection is not intended to limit the scope of particular embodiments. rather, they are representative of selected exemplary embodiments.

A key feature in the Fifth Generation (5G) of the Third Generation Partnership Project (3GPP) is the ability to support different services using the same underlying mobile network infrastructure through network slicing. Network slicing involves grouping devices with similar performance requirements such as delay, throughput, and transmission speed. In this way, the physical infrastructure of the network can be partitioned into logically separated virtual networks for Ultra Reliable Low Latency Communications (URLLC) and Enhanced Mobile Broadband (eMBB). Each network slice can be uniquely identified by single network slice selection assistance information (S-NSSAI), as shown in FIG.

Currently, 3GPP allows a UE to connect to and receive services from up to eight single network slice selection assistance information (S-NSSAIs), but one cell can connect to hundreds of S-NSSAIs. In some cases, one Tracking Area (TA) can support up to 1024 network slices. As shown in FIG. 1, each S-NSSAI may consist of a slice service type (SST) and an operator-defined slice differentiator (SD) field (32 bits long). It can be composed only of the SST field (8 bits long). The SST field can have standardized and non-standardized values ranging from 0 to 127. For example, an SST value of 1 may indicate that the network slice is compatible with 5G eMBB, and an SST value of 2 may indicate that the network slice is compatible with URLLC. Although network slicing offers many benefits, some enterprise/industrial scenarios may require service continuity when a UE moves to a neighboring cell where network slicing is not available. Therefore, in order to provide continuity of service, it is beneficial for the UE to not be interrupted from service of ongoing protocol data unit (PDU) sessions.

During idle/inactive mode, the UE may perform periodic cell reselection and may camp on a cell while selecting a more suitable cell. During cell reselection, the UE may detect neighboring cells, decode master information blocks (MIBs) from the detected neighboring cells, prioritize the detected neighboring cells, and select the optimal cell. The UE may then decode the selected best cell system information block (SIB1) to determine whether the selected best cell is a suitable cell.
Otherwise, the UE may evaluate the second priority cell by decoding the SIB1 of the second priority cell until the UE finds a suitable cell.

As mentioned above, the UE currently does not consider the network slices supported by neighboring cells during cell reselection. Therefore, when the UE enters the connected state, active PDU sessions are dropped and service continuity is lost. Furthermore, even if each cell broadcasts the network slice it supports, the UE needs to decode SIB1 for each cell, which wastes network resources and delays service continuity. Current cell reselection techniques do not take into account network slices supported by neighboring cells. Cell reselection in network slicing deployments has been considered for service continuity to maintain established PDU sessions in any slice, such as for UEs where RRC is not active. This is not supported as the UE is unaware of slice support in neighboring cells. Therefore, after cell reselection, the UE may select a cell that does not support network slices with PDU sessions. As a result, the UE has to attach to that cell and perform the registration area update procedure, but then the UE's PDU session may be disconnected because network slicing is not supported in that cell. . This challenge also applies to RRC idle UEs. That is, if the UE reselects a cell that does not have slice support for the UE's intended slice, e.g., a slice from a granted NSSAI (or a new slice that the UE chooses to connect to), the Unsupported network slices are not included in the allowed NSSAI in the Registration Acceptance message.

Certain embodiments described herein may have various advantages and/or advantages to overcome at least the disadvantages noted above, as well as other problems that may not be described herein. be. For example, certain embodiments may avoid sending duplicate identifiers, such as group IDs. Also, some embodiments may enable size-limited broadcasting of information and enable fast cell reselection. Additionally, various example embodiments may enable continuation of PDU sessions and enable continuation of service with slices supporting cell reselection. Accordingly, certain embodiments described below are directed to improvements in computer-related technology.

According to one embodiment, a fifth generation core (5GC) network is supported by a tracking area (TA) adjacent to the current registration area (RA);
A list of network slices in the UE configuration NSSAI and/or UE granted NSSAI that are supported at the TA in the current RA may be sent to the UE. This list of network slices allows the UE to select the best cell, if radio conditions permit, thereby maximizing service continuity or the ability to accept the requested slice.

FIG. 2 shows an example signaling diagram depicting cell reselection, according to an embodiment. Note that in some embodiments, NE 240 and NE 250 may be similar to NE 610 illustrated in FIG. 6, and UE 230 may be similar to UE 620 illustrated in FIG. Further, in some embodiments, 5GC 260 can be similar to the network illustrated in FIG.

In one embodiment, at 201, NE 250 may send NG setup message(s) to 5GC 260 that includes information similar to that described below for NE 240. At 203, for intra-frequency cell reselection information, the NE 240 includes a list of per-TAC PCIs of TACs adjacent to the current UE RA and a list of per-TAC PCIs belonging to the current UE RA or the current RA. may be sent to UE 230. At 205, for inter-frequency cell reselection information, the NE 250 includes a list of frequency bands for TACs adjacent to the current RA and/or a list of PCIs per frequency band per TAC and A list of frequency bands for TACs belonging to the RA and/or a list of PCIs for each frequency band may be sent to the UE 230. At 207, the NE 240 may send an NG setup message to the 5GC 260 that includes a list of supported TACs and neighboring TACs of the supported TACs (such as TA1 and neighboring TA3), and a list of NSSAIs supported by the neighboring TACs. can.

In various example embodiments, UE 230 may determine which network slices are supported by each neighboring cell. Prioritization of candidate cells during cell reselection may also take into account the information of any of the example embodiments described above. In some embodiments, the list of S-NSSAIs may be a prioritized list and/or priority information may be assigned to different lists that UE 230 may consider during cell reselection.

Furthermore, it is noted that the TAC may be replaced with a CAG identifier in any of the example embodiments described herein. Furthermore, the exact encoding of the information may vary according to the particular embodiment. For example, instead of sending a list of slices per TA or CAG, a list of TAs per slice in an allowed or configured NSSAI can be sent.

In a further embodiment, at 209, UE 230 may send at least one register request to 5GC 260. At 211, the 5GC 260 may determine that the UE registration area (RA) includes multiple TAs, such as TA1 and TA2. At 213, 5GC 260 may send one or more register accept messages, such as a NAS register accept message, to UE 230 during a register update procedure. In some embodiments, the register accept message may include slice assist information. In one embodiment, this slice assist information may include the allowed NSSAI, an indication of the UE RA including TA1 and TA2 supporting a list of slices, and/or a third TA (TA3) indicating a list of slices. . Alternatively, for each TA (TA1, TA2, etc.), the 5GC 260 sends a list of supported slices for all TAs in the RA and a list of supported slices for all TAs adjacent to the RA (TA3, etc.) can do.

In some further embodiments, the 5GC 260 includes, as slice assist information, their tracking area codes (TACs) and/or their network slices in the UE 230's authorized and/or configured NSSAI, or in the UE 230's authorized and/or configured NSSAI. associated with the requested NSSAI (also for border TAC). For example, if only authorized NSSAIs are concerned for service continuity, only network slices supported by tracking areas adjacent to the current RA may be transmitted.

In various further exemplary embodiments, the 5GC 260 may send TAC border information only for network slices that are not part of the authorized NSSAI (i.e., delta) in the slice assist information. As an example, the information may include delta encoding in place of the allowed NSSAI. For example, an empty list of network slices provided for a border TAC or a TAC within an RA means that the same network slices as the allowed NSSAI are supported at the border TA or a TA within the current RA. In some embodiments, negative deltas may also be used in the slice assist information, for example, a S-NSSAI SST=15 delta will cause all slices in the allowed NSSAI except S-NSSAI SST=15 to Indicates authorized NSSAI for supporting TACs. Similar considerations apply to the configured NSSAI delta, and only negative deltas can be applied to the configured NSSAI since there is no need to signal additional slices that are not in the configured NSSAI.

In some embodiments, the 5GC 260 may send an indication of the trajectory of the UE 230 based on artificial intelligence (AI)/machine learning (ML) for a portion of the TAC boundary information, for example. Additionally, in certain embodiments, the TAC may be replaced with a closed access group (CAG) identifier.

In a further embodiment, at 215, the 5GC 260 may send an NG context setup message to the NE 240, such as a Next Generation Application Protocol (NGAP) initial context setup request or an NGAP handover request. In various exemplary embodiments, the NG context setup message described above may include slice assist information. In some embodiments, this slice assist information includes a UE RA with a list of S-NSSAI(s), or a per-TA S-NSSAI of RA and TA3 associated with a list of S-NSSAI(s). May contain a list of NSSAI(s). At 217, NE 240 may store the information received at 215. At 219, the NE 240 may send a handover (HO) request to the NE 250, which includes a list of S-NSSAIs, or a list of S-NSSAIs per TA of the RA, and The UE RA may include an indication of TA3 (TA adjacent to the RA) including a list of TA3 (TA adjacent to the RA). At 221, NE 250 may send a radio resource control (RRC) release message to UE 230, which may include slice assist information. In some embodiments, this is a UE RA containing a list of S-NSSAI(s), or a list of S-NSSAI(s) per TA of the RA, and a list of S-NSSAI(s). TA3 (TA adjacent to RA) may include an indication of TA3 (TA adjacent to RA). In some embodiments, NE 250 may send information to UE 230 during PDU session establishment/modification of a network slice associated with the PDU session.

In some further embodiments,
5GC 260 transmits at 215 only those TACs and/or those network slices associated with UE 230's authorized and/or configured NSSAI, or UE 230's requested NSSAI (also for border TACs). be able to. For example, if only authorized NSSAIs are concerned for service continuity, only network slices supported by tracking areas adjacent to the current RA may be transmitted.

In various further exemplary embodiments, the 5GC 260 may send information only for network slices that are not part of the authorized NSSAI (i.e., delta) in the slice assist information at the TAC boundary. As an example, the information may include a delta that encodes an empty list of network slices provided for a border TAC or a TAC within an RA in place of the authorized NSSAI. This means that the same network slices that are in the allowed NSSAI are supported in the border TA and TAC in the RA. For example, S-NSSAI SST=15 delta indicates that the authorized NSSAI for the TAC supports all slices in the authorized NSSAI except S-NSSAI SST=15. Similar considerations apply to the configured NSSAI delta, and only negative deltas can be applied to the configured NSSAI since there is no need to signal additional slices that are not in the configured NSSAI.

In some further example embodiments, the 5GC 260 may send an indication of the trajectory of the UE 230 based on the AI/ML of only a portion of the TAC boundary information, for example. Additionally or alternatively, slice assist information may be sent to the UE 230 in the border TA with an indication that all border TAs support the allowed NSSAI slices. Similarly, an indication that all network slices within the configured NSSAI are supported at the RA's TA and/or border TA may be sent in the slice assist information. UE 230 may receive slice support for border TAs around the RA, or may also be provided slice support for TAs within the RA of UE 230.

FIG. 3 illustrates an example flow diagram of a method that may be performed by a UE, such as UE 620 illustrated in FIG. 6, in accordance with various example embodiments. As shown in the example of FIG. 3, at 301, the UE identifies the TA identifiers of the TAs adjacent to the served cell and the physical cell identifiers associated with each TA associated with the physical cell identifiers corresponding to neighboring cells of the served cell. Wireless mapping information to and from the list can be received.

At 303, the UE has a TA identifier of a TA adjacent to the served cell and a physical cell identifier corresponding to at least one neighbor cell of the served cell configured for use by at least one frequency band adjacent to the served cell. Radio mapping information may be received that includes a mapping between a list of physical cell identifiers associated with each of the tracking areas.

At 305, the UE receives from a network entity one or more network slices and one or more TA identifiers of a tracking area within the UE RA, or of a tracking area adjacent to the UE RA that supports one or more network slices. Slice assist information associated with a device mapping at least one of the one or more TA identifiers can be received.

At 307, the UE may use the radio mapping information and slice assist information in the cell reselection process. In some embodiments, radio mapping information and slice assist information may be used in the cell reselection process only if multiple neighboring cells are considered appropriate. Additionally, radio mapping information may be received by the served cell via the SIB. Furthermore, slice assist information may be inversely encoded as a mapping between a list of tracking area identifiers and at least one network slice supported by each of the corresponding TAs, where the TAs It may be at least one of a tracking area or a tracking area adjacent to the TA of the UE RA.

In various embodiments, the slice assist information includes a list of slices requested by the UE during a registration update procedure, a list of requested slices granted by the network during a registration update procedure, or configured in the user equipment by the network. may indicate a network slice corresponding to at least one of a list of configured network slices. Furthermore, the slice assist information may consist only of network slices that do not belong to the set of network slices that were reported as allowed by the network in the registration update procedure. In another embodiment, the tracking area identifier may consist of a closed access group identifier.

FIG. 4 illustrates an example flow diagram of a method that may be performed by a 5GC, such as the network shown in FIG. 7, in accordance with various example embodiments. As shown in the example of FIG. 4, at 401, the 5GC may determine at least one tracking area within the UE RA. At 403, the 5GC identifies one or more network slices and one or more TA identifiers of tracking areas within the UE RA, or one or more tracking areas adjacent to the UE RA that support one or more network slices. Slice assist information may be sent that includes a slice (of an authorized or configured NSSAI) associated with the UE indicating a mapping between the UE and at least one of the TA identifiers of the UE.

In certain embodiments, each network slice included in the slice assist information may indicate at least one of SST and SD for each of the one or more network slices. Additionally or alternatively, slice assist information may be sent to at least one user equipment. Additionally, slice assist information can be sent during a registration update procedure.

In some embodiments, the slice assist information includes a list of network slices requested by the user equipment during a registration update procedure, a list of requested network slices granted by the network during a registration update procedure, and/or The network slice may consist of at least one of a list of network slices configured to the user equipment by the network. Further, in embodiments, the one or more tracking area identifiers of the slice assist information may consist only of tracking area identifiers of tracking areas adjacent to the user equipment registration area. The list of network slices in the slice assist information may consist of multiple network slices allowed by the network during the registration update procedure.

In various exemplary embodiments, slice assist information may be inversely encoded as a mapping between a list of tracking area identifiers and network slices supported in each of the corresponding tracking areas. The tracking area may be comprised of one or more tracking areas of the user equipment registration area and/or one or more tracking areas adjacent to the tracking area of the user equipment registration area. Further, according to some embodiments, slice assist information may consist only of network slices that do not belong to the set of network slices reported as allowed by the network in the registration update procedure. In some embodiments, slice assist information may be associated with the trajectory of the user equipment. In some embodiments, the mapping information (both radio mapping and slice assist information) may include at least one closed access group identifier instead of a tracking area identifier.

FIG. 5 illustrates an example flow diagram of a method that may be performed by a network entity, such as NE 610 illustrated in FIG. 6, in accordance with various example embodiments. As shown in the example of FIG. 5, at 501, the NE supports one or more network slices and one or more TA identifiers of TAs in the UE RA and/or one or more network slices. Slice assist information associated with the user equipment may be received indicating a mapping between one or more tracking area identifiers of tracking areas adjacent to the user equipment.

At 503, the NE can store slice assist information. At 505, the NE can send a radio resource control release message to the UE that includes slice assist information. At 507, the NE can transfer the stored slice assistance information to a network entity in response to at least one handover procedure.

In some embodiments, the method may further include forwarding the stored slice assist information to the network entity in response to at least one handover procedure. Furthermore, the radio resource control release message may be configured to place the user equipment into a radio resource control inactive state. Additionally or alternatively, each network slice included in the slice assist information may indicate at least one of SST and SD.

In certain embodiments, slice assist information may be received from a core network.
Additionally, in some embodiments, slice assist information may be received in an NGAP initial context setup request message or an NGAP handover request message.

In various exemplary embodiments, the method further comprises: causing the user equipment to be associated with each tracking area associated with a tracking area identifier of a tracking area adjacent to the served cell and a physical cell identifier corresponding to a neighboring cell of the served cell. and/or mapping information between a tracking area identifier of a tracking area adjacent to the served cell and a list of physical cell identifiers adjacent to the served cell configured to be used by at least one frequency band adjacent to the served cell. transmitting wireless mapping information comprising a mapping between a physical cell identifier corresponding to at least one of the cells and a list of physical cell identifiers associated with each of the tracking areas; Additionally, in some embodiments, radio mapping information may be transmitted via system information broadcast by the served cell.

FIG. 6 is a diagram illustrating an example system according to an example embodiment. In an example embodiment, the system may include one or more devices, such as, for example, NE 610 and/or UE 620.

The NE 610 may be a base station such as an eNB or gNB, a serving gateway, a server, an access point, a transmit/receive point (TRP), a citizen broadband wireless service device (CBSD), and/or any other access or wireless node, or Can be one or more of a combination.

In embodiments where NE 610 may be a gNB, NE 610 may further include at least one gNB-CU that may be associated with at least one gNB-DU. At least one gNB-CU and at least one gNB-DU may communicate via at least one F1 interface, at least one Xn-C interface, and/or at least one NG interface via 5GC.

The UE620 is a mobile device such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, a navigation unit such as a digital camera, pocket camcorder, video game console, Global Positioning System (GPS) device, It may include one or more of a desktop or laptop computer, an IoT device, a single location device such as a sensor or smart meter, or any combination thereof.

NE 610 and/or UE 620 may include at least one processor shown as 611 and 621, respectively. Processors 611 and 621 may be embodied by any computing or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or equivalent apparatus. A processor can be implemented as a single controller or multiple controllers or processors.

At least one memory may be provided in one or more devices, as shown at 612 and 622. Memory may be fixed or removable. Memory may include computer program instructions or computer code contained therein. Memories 612 and 622 may independently be any suitable storage devices such as non-transitory computer readable media. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memory can be combined on a single integrated circuit as a processor, or it can be separate from one or more processors. Additionally, computer program instructions that may be stored in memory and processed by a processor may be computer program code in any suitable form, such as, for example, a compiled or interpreted computer program written in any suitable programming language. Good too.

Processors 611 and 621, memories 612 and 622, and any subset thereof may be configured to provide means corresponding to the various blocks of FIGS. 2-5.
Although not shown, the device may also include positioning hardware, such as GPS or microelectromechanical systems (MEMS) hardware. Other sensors are also permitted and can be configured to determine position, altitude, speed, heading, etc., such as a barometer, compass, etc.

As shown in FIG. 6, transceivers 613 and 623 may be provided, and the one or more devices may also include at least one antenna, illustrated as 614 and 624, respectively. A device may include multiple antennas, such as an array of antennas configured for multiple-input multiple-output (MIMO) communications, or multiple antennas for multiple RATs. For example, other configurations of these devices may be provided. Transceivers 613 and 623 can be transmitters, receivers, both transmitters and receivers, or units or devices that can be configured to both transmit and receive.

The memory and computer program instructions, along with a processor for a particular device, may be configured to cause a hardware device, such as a UE or NE, to perform any of the processes described above (i.e., FIGS. 2-5). Accordingly, in certain embodiments, a non-transitory computer-readable medium is encoded with computer instructions that, when executed in hardware, perform a process, such as one of the processes described herein. can be done. Alternatively, certain embodiments can be implemented entirely in hardware.

In particular embodiments, an apparatus may include circuitry configured to perform any of the processes or functions shown in FIGS. 2-5. For example, the circuit may be a hardware-only circuit implementation, such as an analog circuit and/or a digital circuit. In another example, a circuit is a combination of analog and/or digital hardware circuitry and software or firmware, and/or any portion of a hardware processor and software (including a digital signal processor), software, and device. It may be a combination of hardware circuitry and software, such as at least one memory that cooperate to cause the computer to perform various processes or functions. In yet another example, the circuit may be a hardware circuit and/or processor, such as a microprocessor or portion of a microprocessor, that includes software such as firmware for operation. Software in a circuit may be absent if it is not required for the operation of the hardware.

FIG. 7 illustrates an example 5G network and system architecture according to certain embodiments. A number of network functions are shown that can be implemented as software operating as part of a network device or dedicated hardware, as the network device itself or dedicated hardware, or as virtual functions operating as a network device or dedicated hardware. The NE and UE illustrated in FIG. 7 may be similar to NE 610 and UE 620, respectively. User Plane Functions (UPF) provide intra-RAT and inter-RAT mobility, data packet routing and forwarding, packet inspection,
Services such as user plane quality of service (QoS) processing, downlink packet buffering, and/or downlink data notification triggering may be provided. Application functions (AFs) may interface with the core network primarily to facilitate application usage of traffic routing and interact with policy frameworks.

The features, structures, or characteristics of the example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments.
For example, the use of "various embodiments,""particularembodiments,""someembodiments," or other similar phrases throughout this specification refers to example embodiments. refers to the fact that a particular feature, structure, or characteristic described herein may be included in at least one exemplary embodiment. Therefore, the appearances of "in various embodiments,""in particular embodiments,""in some embodiments," or other similar phrases throughout this specification do not necessarily all refer to the same exemplary implementation. Rather than referring to a group of forms, the described features, structures, or characteristics may be combined in any suitable manner in one or more exemplary embodiments.

Furthermore, if desired, the different functions or procedures described above can be performed in different orders and/or concurrently with each other. Furthermore, one or more of the described features or procedures may be optional or combined if desired. Accordingly, the above description should be considered as illustrative of the principles and teachings of the particular exemplary embodiments, and not as limiting the same.

Those skilled in the art will readily appreciate that the exemplary embodiments described above may be implemented using a different order of procedures and/or a different configuration of hardware elements than those disclosed. Therefore, while some embodiments have been described based on these exemplary embodiments, certain modifications, variations, and alternative constructions may be apparent while remaining within the spirit and scope of the exemplary embodiments. This is obvious to those skilled in the art.

According to a first embodiment, a method includes a list of tracking area identifiers of tracking areas adjacent to a served cell and physical cell identifiers associated with each tracking area associated with physical cell identifiers corresponding to adjacent cells of the served cell. may include receiving wireless mapping information between. The method further includes: a tracking area identifier of a tracking area adjacent to the served cell; and a physical cell identifier corresponding to at least one adjacent cell of the served cell configured for use by at least one frequency band adjacent to the served cell. and a list of physical cell identifiers associated with each of the tracking areas. The method includes, from a network entity, one or more network slices;
mapping at least one of one or more tracking area identifiers of a tracking area within the user equipment registration area or one or more tracking area identifiers of a tracking area adjacent to the user equipment registration area supporting one or more network slices; The method may further include receiving slice assist information related to the device. The method may further include using radio mapping information and slice assist information in a cell reselection process.

In a variant, radio mapping information and slice assist information may be used in the cell reselection process only if multiple neighboring cells are considered suitable.

In a variant, the radio mapping information can be received via system information broadcast by the served cell.

In a variant, the slice assist information may be inversely encoded as a mapping between a list of tracking area identifiers and at least one network slice(s) supported in each of the corresponding tracking areas; The tracking area is at least one of a tracking area of the user equipment registration area or a tracking area adjacent to the tracking area of the user equipment registration area.

In a variant, the slice assist information includes a list of slices requested by the user equipment during the registration update procedure, a list of requested slices granted by the network during the registration update procedure, and a list of slices requested by the user equipment by the network. A network slice corresponding to at least one of the configured list of configured network slices may be indicated.

In a variant, the slice assist information may only include network slices that do not belong to the set of network slices reported as authorized by the network in the registration update procedure.

In a variant, the tracking area identifier may consist of a closed access group identifier.

According to a second embodiment, a method may include determining at least one tracking area within a user equipment registration area. The method further includes one or more network slices and one or more tracking area identifiers of a tracking area within a user equipment registration area, or a tracking area adjacent to a user equipment registration area that supports one or more network slices. and transmitting slice assist information associated with the user equipment indicating a mapping between the one or more tracking area identifiers of the user equipment.

In variations, each network slice may include slice assist information indicating at least one of a slice service type and a slice differentiator for each of the one or more network slices.

In a variant, the slice assist information may be sent to at least one user equipment.

In a variant, slice assist information may be sent during a registration update procedure.

In a variant, the slice assist information includes a list of network slices requested by the user equipment during the registration update procedure, a list of requested network slices granted by the network during the registration update procedure, and a list of requested network slices granted by the network to the user equipment by the network. It may include at least one of a list of configured network slices.

In a variant, the one or more tracking area identifiers in the slice assist information can consist only of tracking area identifiers of tracking areas adjacent to the user equipment registration area, and the list of network slices is not updated during the registration update procedure. consists of multiple network slices allowed by the network.

In a variant, the slice assist information may be encoded inversely as a mapping between a list of tracking area identifiers and the network slices supported by each of the corresponding tracking areas, where the tracking areas are It comprises at least one of one or more tracking areas of the registration area or one or more tracking areas adjacent to the tracking area of the user equipment registration area.

In a variant, the slice assist information may only include network slices that do not belong to the set of network slices reported as authorized by the network in the registration update procedure.

In variations, the slice assist information may be associated with the trajectory of the user equipment.

In a variant, the mapping information may include at least one closed access group identifier instead of a tracking area identifier.

According to a third embodiment, the method includes a list of tracking area identifiers of tracking areas adjacent to the served cell and physical cell identifiers associated with each tracking area associated with physical cell identifiers corresponding to neighboring cells of the served cell. and a tracking area identifier of a tracking area adjacent to the served cell; and at least one of the adjacent cells of the served cell configured for use in at least one frequency band adjacent to the served cell. transmitting at least one radio mapping information to the user equipment, comprising radio mapping information of a mapping between a list of physical cell identifiers associated with each of said tracking areas with one corresponding physical cell identifier; can include.

In a variant, the method may further include forwarding the stored slice assist information to the network entity in response to at least one handover procedure.

In a variant, the radio resource control release message may be configured to place the user equipment into a radio resource control inactive state.

In variations, each network slice may be included in slice assist information including at least one of a slice service type and a slice differentiator.

In variations, slice assist information may be received from the core network.

In variations, the slice assist information may be received in a Next Generation Application Protocol Initial Context Setup Request message or a Next Generation Application Protocol Handover Request message.

In a variant, the method includes one or more network slices and one or more tracking area identifiers of a tracking area within a user equipment registration area supporting one or more network slices or tracking adjacent to the user equipment registration area. receiving slice assist information associated with the user equipment indicating a mapping between the area and at least one of the one or more tracking area identifiers. The method may further include storing slice assist information. The method may further include transmitting a radio resource control release message including slice assist information to the user equipment.

In a variant, the radio mapping information can be transmitted via system information broadcast by the served cell.

According to fourth, fifth, and sixth embodiments, the apparatus may include at least one processor and at least one memory containing computer program code. The at least one memory and the computer program code may be configured to cause at least the apparatus, by the at least one processor, to perform the method according to the first embodiment and any of its variants.

According to a third embodiment, the apparatus may include means for carrying out the method according to the first embodiment and any of its variants.

According to the seventh, eighth and ninth embodiments, the computer program product is encoded with instructions for performing a process comprising the method according to the first embodiment and any of its variants. Can be done.

According to the tenth, eleventh, and twelfth embodiments, the non-transitory computer-readable medium, when executed in hardware, according to any of the first embodiment and variations thereof, It can have instructions stored thereon to execute a process including a method.

According to the thirteenth, fourteenth and fifteenth embodiments, the computer program code may include instructions for carrying out the method according to the first embodiment and any of its variants.

According to the sixteenth, seventeenth and eighteenth embodiments, the apparatus may include a circuit configured to perform a process comprising the method according to the first embodiment and any of its variants.

Partial Glossary 3GPP: Third Generation Partnership Project 5G: Fifth Generation 5GC: Fifth Generation Core 5GS: Fifth Generation System 5QI: Fifth Generation Quality Indicator Service AI: Artificial Intelligence AMF: Access and Mobility Management Function ASIC : Application-Specific Integrated Circuit BS: Base Station CAG: Closed Access Group CBSD: Citizen Broadband Radio Service Device CN: Core Network CPU: Central Processing Unit DL: Downlink DMRS: Demodulation Reference Signal DRB: Data Radio Bearer eMBB: Enhanced Mobile broadband eMTC: Enhanced machine type communication eNB: Evolved Node B
eOLLA: Enhanced External Loop Link Adaptation EPS: Evolved Packet System gNB: Next Generation Node B
GPS: Global Positioning System HDD: Hard Disk Drive HO: Handover LTE: Long Term Evolution LTE-A: Advanced Long Term Evolution MAC: Media Access Control MBS: Multicast and Broadcast System MCS: Modulation and Coding Scheme MEMS:
Micro Electromechanical Systems MIB: Master Information Block MIMO: Multiple Input Multiple Output ML: Machine Learning MME: Mobility Management Entity mMTC: Massive Equipment Type Communication NAS: Non-Access Stratum NB-IoT: Narrowband Internet of Things NE: Network entity NG: Next generation NGAP: Next generation application protocol NG-eNB: Next generation evolved base station NG-RAN: Next generation radio access network NR: New radio NR-U: Unauthorized use new radio communication OFDM: Orthogonal frequency division multiplexing OLLA: External loop link adaptation PBR: Preferred bit rate PCI: Physical cell identifier PDA: Personal digital assistant PDU: Protocol data unit PRACH: Physical random access RA: Registration area RACH: Random access channel RAM: Random access memory RAN: Radio Access Network RAT: Radio Access Technology RRC: Radio Resource Control SD: Slice Identifier SIB: System Information Block S-NSSAI: Single Network Slice Assist Information SST: Slice Service Type TAC: Tracking Area Code TR: Technical Report TS: Technology Specifications UE: User Equipment UL: Uplink UMTS: Universal Mobile Communication System URLLC: Ultra Reliable and Low Latency Communication UTRAN: Universal Mobile Communication System Terrestrial Radio Access Network WLAN: Wireless Local Area Network

Claims (54)

An apparatus comprising at least one processor and at least one memory containing a computer program code, wherein the at least one memory and the computer program code are configured to operate the apparatus using the at least one processor at least: receiving radio mapping information between tracking area identifiers of tracking areas adjacent to a served cell and a list of physical cell identifiers associated with each tracking area associated with a physical cell identifier corresponding to a neighboring cell of the served cell; and,
a tracking area identifier of a tracking area adjacent to the served cell;
a physical cell identifier associated with each of said tracking areas, with a physical cell identifier corresponding to at least one of said served cell's neighboring cells configured for use by at least one frequency band adjacent to said served cell; receiving wireless mapping information including a mapping between a list of
from a network entity, one or more network slices;
one or more tracking area identifiers of a tracking area within a user equipment registration area or one or more tracking area identifiers of a tracking area adjacent to said user equipment registration area supporting said one or more network slices; receiving slice assist information associated with the device mapping at least one;
using the radio mapping information and the slice assist information in a cell reselection process;
A device configured to perform. The apparatus of claim 1, wherein the radio mapping information and the slice assist information are used in the cell reselection process when multiple neighboring cells are considered appropriate. The apparatus of claim 1, wherein the radio mapping information is received via system information broadcast by the served cell. The slice assist information is inversely encoded as a mapping between a list of tracking area identifiers and at least one network slice supported in each of the corresponding tracking areas, where the tracking areas are defined by the user equipment registration area. 2. The apparatus of claim 1, wherein the apparatus is at least one of a tracking area of the user equipment registration area, or a tracking area adjacent to a tracking area of the user equipment registration area. The slice assist information includes the list of slices requested by the user equipment during a registration update procedure, the list of requested slices granted by the network during the registration update procedure, or the slices configured on the user equipment by the network. 2. The apparatus of claim 1, wherein the apparatus indicates a network slice corresponding to at least one of the list of network slices. 5. The apparatus of claim 4, wherein the slice assist information includes only network slices that do not belong to a set of network slices reported as authorized by the network in a registration update procedure. The apparatus of claim 1, wherein the tracking area identifier includes a closed access group identifier. An apparatus comprising at least one processor and at least one memory containing computer program code, the apparatus comprising:
The at least one memory and the computer program code cause the device, using at least one processor, to: determine at least one tracking area within a user equipment registration area;
one or more network slices and one or more tracking area identifiers of tracking areas within said user equipment registration area or one or more tracking areas adjacent to said user equipment registration area supporting one or more network slices; transmitting slice assist information associated with the user equipment indicating a mapping between the tracking area identifier and at least one of the tracking area identifiers;
A device configured to perform. 9. The apparatus of claim 8, wherein each network slice included in the slice assist information indicates at least one of a slice service type or a slice differentiator for each of the one or more network slices. 9. The apparatus of claim 8, wherein the slice assist information is transmitted to at least one user equipment. 9. The apparatus of claim 8, wherein the slice assist information is sent during a registration update procedure. The slice assist information may include a list of network slices requested by the user equipment during a registration update procedure, a list of requested network slices granted by a network during a registration update procedure, or a list of requested network slices configured on the user equipment by the network. 9. The apparatus of claim 8, comprising at least one of a list of network slices. The one or more tracking area identifiers of the slice assist information include tracking area identifiers of tracking areas adjacent to the user equipment registration area, and the list of network slices is authorized by the network during the registration update procedure. 12. The apparatus of claim 11, comprising a plurality of network slices. The slice assist information is inversely encoded as a mapping between a list of tracking area identifiers and the network slices supported in each of the corresponding tracking areas, where the tracking areas are defined as one of the user equipment registration areas. 9. The apparatus of claim 8, comprising at least one of one or more tracking areas or one or more tracking areas adjacent to a tracking area of the user equipment registration area. 15. The apparatus of claim 14, wherein the slice assist information includes only network slices that do not belong to the set of network slices reported as authorized by the network in a registration update procedure. 9. The apparatus of claim 8, wherein the slice assist information is associated with a trajectory of the user equipment. 9. The apparatus of claim 8, wherein the mapping information includes at least one closed access group identifier. An apparatus comprising at least one processor and at least one memory containing a computer program code, the at least one memory and the computer program code being transmitted to the apparatus using the at least one processor at least:
User equipment comprising mapping information between tracking area identifiers of tracking areas adjacent to a served cell and a list of physical cell identifiers associated with each tracking area associated with physical cell identifiers corresponding to adjacent cells of the served cell. or the tracking area identifier of a tracking area adjacent to the served cell; and at least one of the adjacent cells of the served cell configured to be used by at least one frequency band adjacent to the served cell. configured to transmit at least one of the wireless mapping information of a mapping between said list of physical cell identifiers associated with each of the tracking areas having a corresponding physical cell identifier; equipment. 19. The apparatus of claim 18, wherein the radio mapping information is transmitted via system information broadcast by the served cell. at least one memory and computer program code receiving at least slice assist information associated with user equipment to the apparatus using the at least one processor;
one or more network slices and one or more tracking area identifiers of a tracking area within a user equipment registration area, or one or more tracking areas adjacent to a user equipment registration area supporting one or more network slices; indicating a mapping between at least one of the area identifiers;
storing the slice assist information;
transmitting a radio resource control release message including the slice assist information to the user equipment;
19. The apparatus of claim 18, further configured to perform. The at least one memory and the computer program code are configured to transfer the stored slice assist information to a network entity using the at least one processor, at least to the device, in response to at least one handover procedure. 21. The apparatus of claim 20, further configured to perform. 21. The apparatus of claim 20, wherein the radio resource control release message is configured to cause the user equipment to enter a radio resource control inactive state. 21. The apparatus of claim 20, wherein each network slice included in the slice assist information includes at least one of a slice service type or a slice differentiation factor. 21. The apparatus of claim 20, wherein the slice assist information is received from a core network. 21. The apparatus of claim 20, wherein the slice assist information is received in a Next Generation Application Protocol Initial Context Configuration Request message or a Next Generation Application Protocol Handover Request message. receiving radio mapping information between tracking area identifiers of tracking areas adjacent to a served cell and a list of physical cell identifiers associated with each tracking area associated with a physical cell identifier corresponding to a neighboring cell of the served cell; and,
Tracking having a tracking area identifier of a tracking area adjacent to the served cell and a physical cell identifier corresponding to at least one neighbor cell of the served cell configured to be used by at least one frequency band adjacent to the served cell. receiving wireless mapping information including a mapping between the list of physical cell identifiers associated with each of the areas;
From a network entity, one or more network slices and one or more tracking area identifiers of a tracking area within a user equipment registration area, or one or more tracking areas adjacent to a user equipment registration area supporting one or more network slices. receiving slice assist information associated with the apparatus mapping at least one of more than one tracking area identifier;
using the radio mapping information and the slice assist information in a cell reselection process;
including methods. 27. The method of claim 26, wherein the radio mapping information and the slice assist information are used in the cell reselection process when multiple neighboring cells are considered appropriate. 27. The method of claim 26, wherein the radio mapping information is received by the served cell via a system information broadcast. The slice assist information is inversely encoded as a mapping between a list of tracking area identifiers and at least one network slice supported in each of the corresponding tracking areas, where the tracking areas are defined as user equipment registration areas. 27. The method of claim 26, wherein at least one of a tracking area or a tracking area adjacent to a tracking area of the user equipment registration area. The slice assist information may include a list of slices requested by the user equipment during a registration update procedure, a list of requested slices granted by the network during the registration update procedure, or a network slice configured on the user equipment by the network. 27. The method of claim 26, indicating network slices corresponding to at least one of the list of . 30. The method of claim 29, wherein the network slices comprise only network slices that do not belong to a set of network slices reported as authorized by the network in a registration update procedure. 27. The method of claim 26, wherein the tracking area identifier includes a closed access group identifier. determining at least one tracking area within the user equipment registration area;
one or more network slices and one or more tracking area identifiers of tracking areas within a user equipment registration area, or one or more tracking areas adjacent to said user equipment registration area that support said one or more network slices; transmitting slice assist information associated with the user equipment indicating a mapping between the tracking area identifier and the at least one tracking area identifier;
including methods. 34. The method of claim 33, wherein each network slice included in the slice assist information indicates at least one of a slice service type or a slice differentiator for each of the one or more network slices. 34. The method of claim 33, wherein the slice assist information is sent to at least one user equipment. 34. The method of claim 33, wherein the slice assist information is sent during a registration update procedure. The slice assist information includes a list of network slices requested by the user equipment during a registration update procedure;
a list of requested network slices granted by the network during the registration update procedure;
a list of network slices configured by the network in the user equipment;
37. The method of claim 36, comprising at least one of: the one or more tracking area identifiers of the slice assist information include tracking area identifiers of tracking areas adjacent to the user equipment registration area;
the list of network slices includes a plurality of network slices granted by the network during the registration update procedure;
37. The method of claim 36. the slice assist information is inversely encoded as a mapping between the list of tracking area identifiers and the network slices supported in each of the corresponding tracking areas;
The tracking area comprises at least one of one or more tracking areas of the user equipment registration area and one or more tracking areas adjacent to the tracking area of the user equipment registration area.
34. The method of claim 33. 40. The method of claim 39, wherein the slice assist information includes only network slices that do not belong to the set of network slices reported as authorized by the network in a registration update procedure. 34. The method of claim 33, wherein the slice assist information is associated with a trajectory of the user equipment. 34. The method of claim 33, wherein the mapping information includes at least one closed access group identifier. radio mapping information comprising mapping information between a tracking area identifier of a tracking area adjacent to the served cell and a list of physical cell identifiers associated with each tracking area associated with a physical cell identifier corresponding to a neighboring cell of the served cell; ,
a tracking area identifier of a tracking area adjacent to the served cell; and a physical cell identifier corresponding to at least one of the neighboring cells of the served cell configured to be used by at least one frequency band adjacent to the served cell. and radio mapping information of a mapping between the list of physical cell identifiers associated with each of the tracking areas;
A method comprising transmitting at least one of: 44. The method of claim 43, wherein the radio mapping information is transmitted via system information broadcast by the served cell. one or more network slices and one or more tracking area identifiers of a tracking area within a user equipment registration area, or one of the tracking areas adjacent to said user equipment registration area that supports said one or more network slices; receiving slice assist information associated with the user equipment indicating a mapping between the tracking area identifier and at least one of the above tracking area identifiers;
storing the slice assist information;
Sending a radio resource control release message including the slice assistance information to a user equipment;
44. The method of claim 43, further comprising: 44. The method of claim 43, further comprising forwarding stored slice assist information to a network entity in response to at least one handover procedure. 44. The method of claim 43, wherein the radio resource control release message is configured to cause the user equipment to enter a radio resource control inactive state. 44. The method of claim 43, wherein each network slice included in the slice assist information includes at least one of a slice service type or a slice differentiation factor. 44. The method of claim 43, wherein the slice assist information is received from a core network. 44. The method of claim 43, wherein the slice assist information is received in a Next Generation Application Protocol Initial Context Configuration Request message or a Next Generation Application Protocol Handover Request message. Apparatus comprising means for carrying out a method according to any one of claims 26 to 50. 51. A non-transitory computer-readable medium comprising program instructions for carrying out the method of any one of claims 26-50. 51. A device comprising circuitry configured to cause the device to perform a method according to any one of claims 26 to 50. A computer program product encoding instructions for carrying out a method according to any one of claims 26 to 50.

Images