Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/16—Discovering, processing access restriction or access information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
  • H04W24/02—Arrangements for optimising operational condition
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
  • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/20—Selecting an access point
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
  • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events

Definitions

• Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE), fifth generation (5G) radio access technology (RAT), new radio (NR) access technology, and/or other communications systems.
• LTE Long Term Evolution
• RAT fifth generation
• NR new radio
• Some example embodiments may relate to systems and/or methods for cell re-selection.
• Examples of mobile or wireless telecommunication systems may include 5G RAT, the 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 MulteFire Alliance.
• 5G wireless systems refer to the next generation (NG) of radio systems and network architecture.
• NG next generation
• a 5G system is typically built on a 5G NR, but a 5G (or NG) network may also be built on E-UTRA radio.
• NR can support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency-communication (URLLC), and massive machine type communication (mMTC).
• eMBB enhanced mobile broadband
• URLLC ultra-reliable low-latency-communication
• mMTC massive machine type communication
• NG-RAN represents the RAN for 5G, which may provide radio access for NR, LTE, and LTE-A.
• FIG. 1 illustrates an example of a format of single-network slice selection assistance information.
• FIG.2 illustrates an example of a signaling diagram according to certain embodiments.
• FIG.3 illustrates an example of a flow diagram of a method according to various embodiments.
• FIG. 4 illustrates an example of a flow diagram of another method according to some embodiments.
• FIG. 5 illustrates an example of a flow diagram of another method according to certain embodiments.
• FIG.6 illustrates an example of various network devices according to some embodiments.
• FIG. 7 illustrates an example of a 5G network and system architecture according to certain embodiments. DETAILED DESCRIPTION: [0011] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations.
• Each network slice can be uniquely identified by single-network slice selection assistance information (S-NSSAI), as illustrated in FIG.1.
• S-NSSAI single-network slice selection assistance information
• 3GPP allows a UE to connect to and be served by a maximum of eight single network slice selection assistance information (S-NSSAIs), while a single cell may support hundreds of S-NSSAIs, with a single tracking area (TA) able to support up to 1024 network slices.
• S-NSSAI may comprise slice service type (SST) and operator-defined slice differentiator (SD) fields (32-bit length), or just an SST field (8-bit length).
• SST field may have standardized and non-standardized values, ranging from 0 to 127.
• an SST value of 1 may indicate that the network slice is compatible with 5G eMBB
• an SST value of 2 may indicate that the network slice is compatible with URLLC.
• network slices provide numerous benefits, some enterprise/industrial scenarios may require service continuity when the UE moves into neighboring cells where the network slice is unavailable. Thus, it would be beneficial for a UE to have uninterrupted service of on-going protocol data unit (PDU) sessions in order to provide service continuity.
• PDU protocol data unit
• the UE While in idle/inactive mode, the UE may perform periodic cell re-selection, and may camp on a cell while selecting a more suitable cell.
• the UE may detect neighboring cells, decode the master information block (MIB) from the detected neighboring cells, prioritize the detected neighboring cells, and select the best cell. The UE may then decode the system information block (SIB1) of the selected best cell to determine if the selected best cell is a suitable cell. If not, the UE may evaluate the second prioritized cell by decoding the SIB1 of the second prioritized cell until the UE finds a suitable cell.
• MIB master information block
• SIB1 system information block
• the UE would need to decode SIB1 for every cell, needlessly consuming network resources and delaying service continuity.
• Current cell re-selection techniques do not consider network slices supported in neighboring cells.
• Cell re-selection in network slicing deployments has been considered for service continuity, which comprises retaining established PDU sessions on any slice, e.g., for RRC inactive UEs. This is not supported since the UE is unaware of the slice support of any neighbor cell. Thus, after cell re-selection, the UE may select a cell that does not support the network slice having a PDU session.
• the UE connects with the cell, and has to perform a registration area update procedure, after which the PDU session of the UE may be dropped as the network slice is not supported in that cell.
• This challenge also applies to RRC-idle UEs, i.e., when the UEs re-select a cell without the slice support for the intended slice of the UE, e.g., a slice from allowed NSSAI (or a new slice the UE has chosen to connect), the non-supported network slice in the TA of the cell will not be included in the allowed NSSAI in the registration accept message.
• Certain embodiments described herein may have various benefits and/or advantages to overcome at least the disadvantages described above, as well as other problems that may not be described herein. For example, certain embodiments may avoid transmitting duplicative identifiers, such as group ID. Some embodiments may also enable broadcasting of information that is limited in size, and enable fast cell re-selection. Various example embodiments may also enable PDU session continuity, enabling service continuity through slice supporting cell re-selection. Thus, certain embodiments discussed below are directed to improvements in computer-related technology.
• a fifth generation core (5GC) network may transmit, to a UE, a list of network slices in the UE-configured NSSAI and/or UE-allowed NSSAI supported by tracking areas (TAs) neighboring the current registration area (RA), and supported in TAs in the current RA.
• This list of network slices can allow the UE to select the best cell, if radio conditions allow, thereby maximizing the service continuity or the ability to accept the requested slices.
• FIG.2 illustrates an example of a signalling diagram depicting cell reselection, according to an embodiment.
• 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.6.
• 5GC 260 may be similar to the network illustrated in FIG.7.
• NE 250 may transmit to 5GC 260 NG setup message(s) with similar information as described below for NE 240.
• NE 240 may transmit to UE 230 lists of PCIs per TAC for TACs neighboring the current UE RA and list of PCIs for the current UE RA or per TAC belonging to the current RA.
• NE 250 may transmit to UE 230 lists of frequency bands and/or a list of PCIs per frequency bands per TAC for TACs neighboring the current RA and list of frequency bands and/or a list of PCIs per frequency bands for the current RA or per TAC belonging to the current RA.
• NE 240 may transmit to 5GC 260 a NG setup message including the list of supported TACs and neighbor TACs of supported TACs, (such as TA1 and neighboring TA3), as well as a list of NSSAI(s) supported by the neighboring TACs.
• UE 230 may determine which network slices are supported by each neighbor cell.
• the prioritization of candidate cells during cell re-selection may also consider the information in any of the example embodiments described above.
• the lists of S- NSSAI may be prioritized lists, and/or priority information may be assigned to different lists that UE 230 may consider during cell reselection.
• TAC may be replaced by CAG identifiers in any of the example embodiments described herein.
• the exact encoding of the information may vary according to certain embodiments; for example, instead of sending a list of slices per TA or CAG, a list of TAs per slice in the allowed NSSAI or configured NSSAI may be transmitted.
• UE 230 may transmit at least one register request to 5GC 260.
• 5GC 260 may determine that a UE registration area (RA) includes a plurality of TAs, such as TA1 and TA2.
• RA UE registration area
• 5GC 260 may transmit to UE 230 one or more register accept messages, such as a NAS Register Accept message during a register update procedure.
• the register accept messages may include slice assistance information.
• this slice assistance information may include allowed NSSAI, an indication of the UE RA including TA1 and TA2 with supported list of slices, and/or a third TA (TA3) indicating a list of slices.
• 5GC 260 may transmit the list of supported slices for all TAs of the RA per TA (such as TA1, TA2), as well as the list of supported slices for all TAs neighboring the RA (such as TA3).
• 5GC 260 may transmit in the slice assistance information those tracking area codes (TAC) and/or those network slices associated with allowed NSSAI and/or configured NSSAI of UE 230, or requested NSSAI of UE 230 (also for border TAC). For example, if just allowed NSSAI is of concern for service continuity, then just the network slices supported by the tracking areas neighboring the current RA may be sent.
• TAC tracking area codes
• 5GC 260 may transmit in the slice assistance information TAC border information for just those network slices which are not part of the allowed NSSAI (i.e., delta).
• the information may include a delta encoding instead of the allowed NSSAI.
• an empty list of network slices provided for a border TAC or a TAC in the RA would mean that the same network slices are supported in the border TAs or the TA in current RA as in the allowed NSSAI.
• configured NSSAI deltas wherein just negative deltas can apply on the configured NSSAI as there is no need to signal additional slices that are not in the configured NSSAI.
• 5GC 260 may transmit indications of the trajectory of UE 230, for example, based on artificial intelligence (AI)/machine learning (ML) for a part of the TAC border information.
• AI artificial intelligence
• ML machine learning
• TAC may be replaced by closed access group (CAG) identifiers.
• CAG closed access group
• 5GC 260 may transmit to NE 240 NG context setup messages, such as a next generation application protocol (NGAP) initial context setup request or NGAP handover request.
• the above NG context setup messages may include the slice assistance information.
• this slice assistance information may include UE RA with a list of S-NSSAI(s), or list of S-NSSAI(s) per TA of the RA and TA3 associated with a list of S- NSSAI.
• NE 240 may store the information received at 215.
• NE 240 may transmit a handover (HO) request to NE 250, which may include the UE RA with the list of S-NSSAI(s), or list of S-NSSAI(s) per TA of the RA, and indications of the TA3 (TA neighboring the RA) including the list of S-NSSAI(s).
• NE 250 may transmit to UE 230 a radio resource control (RRC) release message, which may include the slice assistance information.
• RRC radio resource control
• this may include UE RA with the list of S-NSSAI(s), or list of S-NSSAI(s) per TA of the RA, and indications of the TA3 (TA neighboring the RA) including the list of S-NSSAI(s).
• NE 250 may transmit the information to UE 230 during PDU session establishment/modification for the network slice associated with the PDU session.
• 5GC 260 may transmit at 215 just those TAC and/or just those network slices associated with allowed NSSAI and/or configured NSSAI of UE 230, or requested NSSAI of UE 230 (also for border TAC).
• 5GC 260 may transmit in the slice assistance information at TAC border information for just those network slices which are not part of the allowed NSSAI (i.e., delta).
• the information may include a delta encoding, instead of the allowed NSSAI, an empty list of network slices provided for a border TAC or a TAC in the RA. This would mean the same network slices supported in the border TAs and in TAC in the RA as there are in the allowed NSSAI.
• configured NSSAI deltas wherein just negative deltas can apply on the configured NSSAI as there is no need to signal additional slices that are not in the configured NSSAI.
• 5GC 260 may transmit indications of the trajectory of UE 230, for example, based on AI/ML for just a part of the TAC border information.
• border TA may be transmitted to UE 230 with an indication that all border TAs support the allowed NSSAI slices.
• indications may be transmitted in the slice assistance information that all the network slices in the configured NSSAI are supported in the TAs of the RA and/or border TAs.
• UE 230 may receive the slice support of the border TAs around the RA, or the slice support of the TAs in the RA of UE 230 may also be provided.
• FIG.3 illustrates an example of a flow diagram of a method that may be performed by a UE, such as UE 620 illustrated in FIG. 6, according to various example embodiments.
• the UE may receive radio mapping information between TA identifiers of TAs neighboring a served cell and a list of physical cell identifiers associated with each TA associated with physical cell identifiers corresponding to a neighbor cell of the served cell.
• the UE may receive radio mapping information comprising a mapping between the TA identifiers of TAs neighboring the served cell and the list of physical cell identifiers associated with each of the tracking areas with physical cell identifiers corresponding to at least one of the neighbor cells of the served cell configured for use by at least one frequency band neighboring the served cell.
• the UE may receive, from a network entity, slice assistance information associated with the apparatus mapping one or more network slices and at least one of one or more TA identifiers of tracking areas in a UE RA or one or more TA identifiers of tracking areas neighboring the UE RA supporting the one or more network slices.
• the UE may use the radio mapping information and the slice assistance information in a cell re-selection process.
• the radio mapping information and the slice assistance information may be used in the cell re-selection process only when multiple neighbor cells are considered as suitable.
• the radio mapping information may be received via SIB by the served cell.
• the slice assistance information may be encoded reversely as the mapping between a list of tracking area identifiers and at least one network slice supported in each of the corresponding TAs, wherein the TAs may be at least one of a tracking area of the UE RA or a tracking area neighboring a TA of the UE RA.
• the slice assistance information may indicate network slices corresponding to at least one of the list of slices requested by a UE during a registration update procedure, the list of requested slices which have been allowed by the network during a registration update procedure or the list of configured network slices which have been configured by the network to a user equipment.
• FIG. 4 illustrates an example of a flow diagram of a method that may be performed by a 5GC, such as the network illustrated in FIG. 7, according to various example embodiments. As illustrated in the example of FIG. 4, at 401, the 5GC may determine at least one tracking area in a UE RA.
• the 5GC may transmit slice assistance information comprising slices (of allowed NSSAI or configured NSSAI) associated with a UE indicating a mapping between one or more network slices and at least one of one or more TA identifiers of tracking areas in the UE RA, or one or more TA identifiers of tracking areas neighboring the UE RA that support the one or more network slices.
• each network slice included in the slice assistance information may indicate at least one of SST and SD for each of the one or more network slices.
• the slice assistance information may be transmitted to at least one user equipment.
• the slice assistance information may be transmitted during a registration update procedure.
• the slice assistance information may comprise at least one of a list of network slices requested by a user equipment during a registration update procedure, a list of requested network slices allowed by a network during a registration update procedure, and/or a list of network slices configured by the network to a user equipment.
• the one or more tracking area identifiers of the slice assistance information may comprise just tracking area identifiers of tracking areas neighboring the user equipment registration area.
• the list of network slices in the slice assistance information may comprise a plurality of network slices allowed by the network during the registration update procedure.
• the slice assistance information may be encoded reversely as the mapping between a list of tracking area identifier(s) and the network slices which are supported in each of the corresponding tracking areas.
• the tracking areas may comprise one or more tracking areas of the user equipment registration area and/or one or more tracking areas neighboring a tracking area of the user equipment registration area.
• the slice assistance information may comprise just network slices which do not belong to the set of network slices reported as allowed by the network in a registration update procedure.
• the slice assistance information may be associated with a trajectory of the user equipment.
• the mapping information may comprise at least one closed access group identifier(s) in replacement of the tracking area identifiers.
• FIG. 5 illustrates an example of a flow diagram of a method that may be performed by a network entity, such as NE 610 illustrated in FIG.6, according to various example embodiments.
• the NE may receive slice assistance information associated with a user equipment indicating a mapping between one or more network slices and one or more TA identifiers of TAs in a UE RA and/or one or more tracking area identifiers of tracking areas neighboring the UE RA that support the one or more network slices.
• the NE may store the slice assistance information.
• the NE may transmit a radio resource control release message comprising the slice assistance information to a UE.
• the NE may transfer the stored slice assistance information to a network entity in response to at least one handover procedure.
• the method may further comprise transferring the stored slice assistance information to a network entity in response to at least one handover procedure.
• the radio resource control release message may be configured to cause the user equipment to enter a radio resource control inactive state.
• each network slice included in the slice assistance information may indicate at least one of SST and SD.
• the slice assistance information may be received from a core network.
• the slice assistance information may be received in a NGAP initial context setup request message or a NGAP handover request message.
• the method may further comprise transmitting, to a user equipment, radio mapping information comprising mapping information between tracking area identifiers of tracking areas neighboring a served cell and a list of physical cell identifiers associated with each tracking area associated with physical cell identifiers corresponding to a neighbor cell of the served cell, and/or radio mapping information of a mapping between the tracking area identifiers of tracking areas neighboring the served cell and the list of physical cell identifiers associated with each of the tracking areas with physical cell identifiers corresponding to at least one of the neighbor cells of the served cell configured for use by at least one frequency band neighboring the served cell.
• FIG. 6 illustrates an example of a system according to certain example embodiments.
• a system may include one or more devices, such as, for example, NE 610 and/or UE 620.
• NE 610 may be one or more of a base station, such as an eNB or gNB, a serving gateway, a server, an access point, a transmission-reception point (TRP), citizens broadband radio service device (CBSD), and/or any other access or radio node or combination thereof.
• NE 610 may be a gNB
• NE 610 may further comprise at least one gNB-CU, which may be associated with at least one gNB-DU.
• the at least one gNB-CU and the at least one gNB-DU may be in communication via at least one F1 interface, at least one X n -C interface, and/or at least one NG interface via a 5GC.
• UE 620 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, IoT device, single-location device, such as a sensor or smart meter, or any combination thereof.
• a mobile device such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, IoT device, single-location device, such as a sensor or smart meter, or any combination thereof.
• GPS global positioning system
• NE 610 and/or UE 620 may include at least one processor, respectively indicated as 611 and 621.
• Processors 611 and 621 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific
• the processors may be implemented as a single controller, or a plurality of controllers or processors.
• At least one memory may be provided in one or more of the devices, as indicated at 612 and 622.
• the memory may be fixed or removable.
• the memory may include computer program instructions or computer code contained therein.
• Memories 612 and 622 may independently be any suitable storage device, such as a non-transitory computer-readable medium.
• a hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used.
• the memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors.
• the computer program instructions stored in the memory may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
• 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.
• the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device.
• MEMS micro electrical mechanical system
• Other sensors are also permitted, and may be configured to determine location, elevation, velocity, orientation, and so forth, such as barometers, compasses, and the like.
• transceivers 613 and 623 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 614 and 624.
• the device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple RATs. Other configurations of these devices, for example, may be provided.
• Transceivers 613 and 623 may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.
• the memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE or NE, to perform any of the processes described above (i.e., FIGS. 2-5). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments may be performed entirely in hardware. [0053] In certain embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIGS. 2-5. For example, circuitry may be hardware-only circuit implementations, such as analog and/or digital circuitry.
• circuitry may be a combination of hardware circuits and software, such as a combination of analog and/or digital hardware circuitry with software or firmware, and/or any portions of hardware processors with software (including digital signal processors), software, and at least one memory that work together to cause an apparatus to perform various processes or functions.
• circuitry may be hardware circuitry and or processors, such as a microprocessor or a portion of a microprocessor, that includes software, such as firmware, for operation. Software in circuitry may not be present when it is not needed for the operation of the hardware.
• FIG. 7 illustrates an example of a 5G network and system architecture according to certain embodiments.
• the NE and UE illustrated in FIG.7 may be similar to NE 610 and UE 620, respectively.
• the user plane function may provide services such as intra-RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of downlink packets, and/or triggering of downlink data notifications.
• the application function may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.
• a method may include receiving radio mapping information between tracking area identifiers of tracking areas neighboring a served cell and a list of physical cell identifiers associated with each tracking area associated with physical cell identifiers corresponding to a neighbor cell of the served cell.
• the method may further include receiving radio mapping information comprising a mapping between the tracking area identifiers of tracking areas neighboring the served cell and the list of physical cell identifiers associated with each of the tracking areas with physical cell identifiers corresponding to at least one of the neighbor cells of the served cell configured for use by at least one frequency band neighboring the served cell.
• the method may further include receiving, from a network entity, slice assistance information associated with the apparatus mapping one or more network slices and at least one of one or more tracking area identifiers of tracking areas in a user equipment registration area or one and more tracking area identifiers of tracking areas neighboring the user equipment registration area supporting the one or more network slices.
• the method may further include using the radio mapping information and the slice assistance information in a cell re-selection process.
• the radio mapping information and the slice assistance information may be used in the cell re-selection process only when multiple neighbor cells are considered as suitable.
• the radio mapping information may be received via system information broadcast by the served cell.
• the slice assistance information may be encoded reversely as the mapping between a list of tracking area identifiers and at least one network slice(s) supported in each of the corresponding tracking areas, wherein the tracking areas are at least one of a tracking area of the user equipment registration area or a tracking area neighboring a tracking area of the user equipment registration area.
• the slice assistance information may indicate network slices corresponding to at least one of the list of slices requested by a user equipment during a registration update procedure, the list of requested slices which have been allowed by the network during a registration update procedure and the list of configured network slices which have been configured by the network to a user equipment.
• the slice assistance information may comprise only network slices which do not belong to the set of network slices reported as allowed by the network in a registration update procedure.
• the tracking area identifiers may comprise closed access group identifiers.
• a method may include determining at least one tracking area in a user equipment registration area.
• the method may further include transmitting slice assistance information associated with a user equipment indicating a mapping between one or more network slices and at least one of one or more tracking area identifiers of tracking areas in the user equipment registration area, or one or more tracking area identifiers of tracking areas neighboring the user equipment registration area that support the one or more network slices.
• each network slice may be included in the slice assistance information indicates at least one of slice service type and slice differentiator for each of the one or more network slices.
• the slice assistance information may be transmitted to at least one user equipment.
• the slice assistance information may be transmitted during a registration update procedure.
• the slice assistance information may comprise at least one of a list of network slices requested by a user equipment during a registration update procedure, a list of requested network slices allowed by a network during a registration update procedure, and a list of network slices configured by the network to a user equipment.
• the one or more tracking area identifiers of the slice assistance information may only comprise tracking area identifiers of tracking areas neighboring the user equipment registration area, wherein the list of network slices comprise a plurality of network slices allowed by the network during the registration update procedure.
• the slice assistance information may be encoded reversely as the mapping between a list of tracking area identifier(s) and the network slices which are supported in each of the corresponding tracking areas, wherein the tracking areas comprise at least one of one or more tracking areas of the user equipment registration area or one or more tracking areas neighboring a tracking area of the user equipment registration area.
• the slice assistance information may comprise only network slices which do not belong to the set of network slices reported as allowed by the network in a registration update procedure.
• the slice assistance information may be associated with a trajectory of the user equipment.
• the mapping information may comprise at least one closed access group identifier in replacement of the tracking area identifiers.
• a method may include transmitting at least one of radio mapping information to a user equipment comprising mapping information between tracking area identifiers of tracking areas neighboring a served cell and a list of physical cell identifiers associated with each tracking area associated with physical cell identifiers corresponding to a neighbor cell of the served cell, and radio mapping information of a mapping between the tracking area identifiers of tracking areas neighboring the served cell and the list of physical cell identifiers associated with each of the tracking areas with physical cell identifiers corresponding to at least one of the neighbor cells of the served cell configured for use by at least one frequency band neighboring the served cell.
• the method may further comprise transferring the stored slice assistance information to a network entity in response to at least one handover procedure.
• the radio resource control release message may be configured to cause the user equipment to enter a radio resource control inactive state.
• each network slice may be included in the slice assistance information comprises at least one of slice service type and slice differentiator.
• the slice assistance information may be received from a core network.
• the slice assistance information may be received in a next generation application protocol initial context setup request message or a next generation application protocol handover request message.
• the method may further comprise receiving slice assistance information associated with a user equipment indicating a mapping between one or more network slices and at least one of one or more tracking area identifiers of tracking areas in a user equipment registration area or one or more tracking area identifiers of tracking areas neighboring the user equipment registration area that support the one or more network slices.
• the method may further comprise storing the slice assistance information.
• the method may further comprise transmitting a radio resource control release message comprising the slice assistance information to a user equipment.
• the radio mapping information may be transmitted via system information broadcast by the served cell.
• an apparatus may include at least one processor and at least one memory including computer program code.
• the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus at least to perform a method according to the first embodiment and any of its variants.
• an apparatus may include means for performing the method according to the first embodiment and any of its variants.
• a computer program product may be encoded with instructions for performing a process including a method according to the first embodiment and any of its variants.
• a non-transitory, computer- readable medium may have instructions stored thereon that, when executed in hardware, perform a process including a method according to the first embodiment and any of its variants.
• computer program code may include instructions for performing a method according to the first embodiment and any of its variants.
• an apparatus may include circuitry configured to perform a process including a method according to the first embodiment and any of its variants.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=80446631

Family Applications (1)

Country Status (4)

Family Cites Families (3)

• 2022
  • 2022-02-03 WO PCT/IB2022/050961 patent/WO2022208176A1/en active Application Filing
  • 2022-02-03 CN CN202280020464.1A patent/CN117063531A/zh active Pending
  • 2022-02-03 JP JP2023560628A patent/JP2024512734A/ja active Pending
  • 2022-02-03 EP EP22703989.8A patent/EP4315997A1/en active Pending

Also Published As

Similar Documents

Legal Events