WO2023170611A1 - Signaling slice to slice group mapping to a user equipment device - Google Patents

Abstract

Apparatuses, methods, and systems are disclosed for signaling slice to slice group mapping to a user equipment device. An apparatus (400) includes processor (405) and a memory (410) coupled to the processor (405). The memory (410) includes instructions executable by the processor (405) to cause the apparatus (400) to receive, from a network, for each pair of slice group and frequency, one or more of an allow list of cells, a block list of cells, and a flag indicating how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the system information block ("SIB1") information of the cell, determine whether a highest ranked cell is listed in the block list of cells for a corresponding slice group and frequency pair and determine slice groups that are supported by the highest ranked cell in the block list.

Description

SIGNALING SLICE TO SLICE GROUP MAPPING TO A USER EQUIPMENT

DEVICE

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of United States Provisional Patent Application Number 63/317,919 entitled “SIGNALING SLICE TO SLICE GROUP MAPPING TO A USER EQUIPMENT DEVICE” and filed on March 8, 2022, for Prateek Basu Mallick, et al., which is incorporated herein by reference.

FIELD

[0002] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to signaling slice to slice group mapping to a user equipment (“UE”) device.

BACKGROUND

[0003] In certain wireless networks, 5G network slicing is a network architecture that enables the multiplexing of virtualized and independent logical networks on the same physical network infrastructure. Each network slice may be an isolated end-to-end network tailored to fulfil diverse requirements requested by a particular application. As such, this technology assumes a central role to support 5G mobile networks that are designed to efficiently embrace a plethora of services with very different service level requirements (“SLRs”). The realization of this service- oriented view of the network leverages on the concepts of software-defined networking (“SDN”) and network function virtualization (“NFV”) that allow the implementation of flexible and scalable network slices on top of a common network infrastructure.

BRIEF SUMMARY

[0004] Disclosed are procedures for signaling slice to slice group mapping to a user equipment device. The procedures may be implemented by apparatus, systems, methods, or computer program products.

[0005] In one embodiment, a first apparatus includes a processor and a memory coupled to the processor. In one embodiment, the memory includes instructions that are executable by the processor to cause the apparatus to receive, from a network, for each pair of slice group and frequency, one or more of an allow list of cells, a block list of cells, and a flag indicating how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the system information block (“SIB1”) information of the cell. In one embodiment, the instructions are further executable by the processor to cause the apparatus to determine whether a highest ranked cell is listed in the block list of cells for a corresponding slice group and frequency pair and, in response to the highest ranked cell being listed in the block list, determine slice groups that are supported by the highest ranked cell in the block list.

[0006] In one embodiment, a first method receives, from a network, for each pair of slice group and frequency, one or more of an allow list of cells, a block list of cells, and a flag indicating how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the SIB1 information of the cell. In one embodiment, the first method determines whether a highest ranked cell is listed in the block list of cells for a corresponding slice group and frequency pair and, in response to the highest ranked cell being listed in the block list, determines slice groups that are supported by the highest ranked cell in the block list.

[0007] In one embodiment, a second apparatus includes a processor and a memory coupled to the processor. In one embodiment, the memory includes instructions that are executable by the processor to cause the apparatus to determine an allow-list of physical cell identities for each frequency supporting a slice group, determine a block-list of physical cell identities for each frequency supporting a slice group, determine a value of a flag indicating to a UE how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the SIB 1 information of the cell, and transmit the allow-list, the block -list, and the flag to the UE.

[0008] In one embodiment, a second method determines an allow-list of physical cell identities for each frequency supporting a slice group, determines a block-list of physical cell identities for each frequency supporting a slice group, and determines a value of a flag indicating to a UE how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the SIB1 information of the cell. In one embodiment, the second method transmits the allow-list, the block-list, and the flag to the UE.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0010] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for signaling slice to slice group mapping to a UE device;

[0011] Figure 2 is one example of cell and frequency deployment; [0012] Figure 3 is one embodiment of a procedure flow for requesting mapping information for mapping slices to their slice group identifiers for a tracking area;

[0013] Figure 4 is a block diagram illustrating one embodiment of a UE apparatus that may be used for signaling slice to slice group mapping to a UE device;

[0014] Figure 5 is a block diagram illustrating one embodiment of a network equipment apparatus that may be used for signaling slice to slice group mapping to a UE device;

[0015] Figure 6 is a block diagram illustrating one embodiment of a first method for signaling slice to slice group mapping to a UE device; and

[0016] Figure 7 is a block diagram illustrating one embodiment of a second method for signaling slice to slice group mapping to a UE device.

DETAILED DESCRIPTION

[0017] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.

[0018] For example, the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.

[0019] Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non- transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0020] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0021] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc readonly memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0022] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object- oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)).

[0023] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0024] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0025] As used herein, a list with a conjunction of “and/or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and/or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one or more of’ includes any single item in the list or a combination of items in the list. For example, one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one of’ includes one and only one of any single item in the list. For example, “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C. As used herein, “a member selected from the group consisting of A, B, and C,” includes one and only one of A, B, or C, and excludes combinations of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof’ includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.

[0026] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the fimctions/acts specified in the flowchart diagrams and/or block diagrams.

[0027] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart diagrams and/or block diagrams.

[0028] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the fimctions/acts specified in the flowchart diagrams and/or block diagrams.

[0029] The flowchart diagrams and/or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and/or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0030] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0031] Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0032] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0033] Generally, the present disclosure describes systems, methods, and apparatuses for signaling slice to slice group mapping to a UE device. In certain embodiments, the methods may be performed using computer code embedded on a computer-readable medium. In certain embodiments, an apparatus or system may include a computer-readable medium containing computer-readable code which, when executed by a processor, causes the apparatus or system to perform at least a portion of the below described solutions.

[0034] In general, when performing slice-based cell reselection procedure, if the best/highest ranked cell on a certain frequency does not support a selected slice group, it remains unclear how UE determines which slice groups are supported by the cell. It is very signaling inefficient to separately broadcast slice groups, in addition to the slice Info, supported by each neighboring cell. As another problem, when the mapping information for mapping slices (NSSAIs or S-NSSAIs) to slice group ID is to be provided on a per tracking area basis, an efficient signaling method needs to be designed.

[0035] As described herein, a UE determines the slice group supported by a cell using the information already available in Slice Info. In addition, the subject matter herein describes enabling efficient signaling of slice-to-slice group mapping using Registration Accept message, as one example.

[0036] In one conventional solution, slice support information of each cell on each neighboring frequency can be provided by the serving cell but it can be very signaling inefficient since there can be as many as 96 such entries (12 cells * 8 frequencies) for which slice group support would need to be indicated. Other conventional solutions include mapping information for mapping Slices (NSSAIs or S-NSSAIs) to Slice Group Id can be provided by a UE performing TAU (Tracking Area Update) procedure even when the TA of a new cell which is even part of the T A-list of the registration area. This will be an overkill since TAUs need a UE to transition to RRC Connected state, thus consuming too much UE battery.

[0037] The solutions proposed below include determining whether the best ranked cell (Cl) on that frequency (fl) does not support the slice group SI, to determine which slice groups are supported by Cl, the UE may either Read SIB1 of cell Cl or Check individually for all slice groups supported on fl and build a list of slice groups supported by cell Cl in the following way: Cl does not support a certain slice group if Cl is listed in the block-list for the slice group; or if the allow-list is signaled but Cl is not listed in it and/or Cl supports a certain slice group if cell Cl is listed in the allow-list for the slice group; or if block-list is signaled but Clis not listed in it.

[0038] In one embodiment, in a Registration Accept message, the network (AMF) provides more than one TA-sub-lists to the UE as part of its registration area, rather than just one TA-list as in the current-art. For each of the included multiple TA-sub-lists, network provides a mapping information for mapping Slices (NSSAIs or S-NSSAIs) to Slice Group Id. [0039] Figure 1 depicts a wireless communication system 100 for signaling slice to slice group mapping to a UE device, according to embodiments of the disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may be composed of a base unit 121 with which the remote unit 105 communicates using wireless communication links 123. Even though a specific number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 105, base units 121, wireless communication links 123, RANs 120, and mobile core networks 140 may be included in the wireless communication system 100.

[0040] In one implementation, the RAN 120 is compliant with the 5G system specified in the Third Generation Partnership Project (“3GPP”) specifications. For example, the RAN 120 may be a Next Generation Radio Access Network (“NG-RAN”), implementing New Radio (“NR”) Radio Access Technology (“RAT”) and/or Long-Term Evolution (“LTE”) RAT. In another example, the RAN 120 may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers (“IEEE”) 802. 11 -family compliant WLAN). In another implementation, the RAN 120 is compliant with the LTE system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access (“WiMAX”) or IEEE 802.16-family standards, among other networks. The present disclosure is not intended to be limited to the implementation of any wireless communication system architecture or protocol.

[0041] In one embodiment, the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. In some embodiments, the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 105 may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (“WTRU”), a device, or by other terminology used in the art. In various embodiments, the remote unit 105 includes a subscriber identity and/or identification module (“SIM”) and the mobile equipment (“ME”) providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM). In certain embodiments, the remote unit 105 may include a terminal equipment (“TE”) and/or be embedded in an appliance or device (e.g., a computing device, as described above).

[0042] The remote units 105 may communicate directly with one or more of the base units 121 in the RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals may be carried over the wireless communication links 123. Here, the RAN 120 is an intermediate network that provides the remote units 105 with access to the mobile core network 140. As described in greater detail below, the base unit(s) 121 may provide a cell operating using a first frequency range and/or a cell operating using a second frequency range.

[0043] In some embodiments, the remote units 105 communicate with an application server 151 via a network connection with the mobile core network 140. For example, an application 107 (e.g., web browser, media client, telephone and/or Voice-over-Intemet-Protocol (“VoIP”) application) in a remote unit 105 may trigger the remote unit 105 to establish a protocol data unit (“PDU”) session (or other data connection) with the mobile core network 140 via the RAN 120. The mobile core network 140 then relays traffic between the remote unit 105 and the application server 151 in the packet data network 150 using the PDU session. The PDU session represents a logical connection between the remote unit 105 and the User Plane Function (“UPF”) 141.

[0044] To establish the PDU session (or PDN connection), the remote unit 105 must be registered with the mobile core network 140 (also referred to as “attached to the mobile core network” in the context of a Fourth Generation (“4G”) system). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 140. As such, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and/or other communication peers.

[0045] In the context of a 5G system (“5GS”), the term “PDU Session” refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between the remote unit 105 and a specific Data Network (“DN”) through the UPF 141. A PDU Session supports one or more Quality of Service (“QoS”) Flows. In certain embodiments, there may be a one-to-one mapping between a QoS Flow and a QoS profile, such that all packets belonging to a specific QoS Flow have the same 5G QoS Identifier (“5QI”). [0046] In the context of a 4G/LTE system, such as the Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also referred to as EPS session) provides E2E UP connectivity between the remote unit and a PDN. The PDN connectivity procedure establishes an EPS Bearer, e.g., a tunnel between the remote unit 105 and a Packet Gateway (“PGW”, not shown) in the mobile core network 140. In certain embodiments, there is a one-to-one mapping between an EPS Bearer and a QoS profde, such that all packets belonging to a specific EPS Bearer have the same QoS Class Identifier (“QCI”).

[0047] The base units 121 may be distributed over a geographic region. In certain embodiments, a base unit 121 may also be referred to as an access terminal, an access point, a base, abase station, aNode-B (“NB”), an Evolved Node B (abbreviated as eNodeB or “eNB,” also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), a 5G/NR Node B (“gNB”), a Home Node-B, a relay node, a RAN node, or by any other terminology used in the art. The base units 121 are generally part of a RAN, such as the RAN 120, that may include one or more controllers communi cably coupled to one or more corresponding base units 121. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The base units 121 connect to the mobile core network 140 via the RAN 120.

[0048] The base units 121 may serve a number of remote units 105 within a serving area, for example, a cell or a cell sector, via a wireless communication link 123. The base units 121 may communicate directly with one or more of the remote units 105 via communication signals. Generally, the base units 121 transmit DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the wireless communication links 123. The wireless communication links 123 may be any suitable carrier in licensed or unlicensed radio spectrum. The wireless communication links 123 facilitate communication between one or more of the remote units 105 and/or one or more of the base units 121. Note that during NR operation on unlicensed spectrum (referred to as “NR- U”), the base unit 121 and the remote unit 105 communicate over unlicensed (e.g., shared) radio spectrum.

[0049] In one embodiment, the mobile core network 140 is a 5GC or an Evolved Packet Core (“EPC”), which may be coupled to a packet data network 150, like the Internet and private data networks, among other data networks. A remote unit 105 may have a subscription or other account with the mobile core network 140. In various embodiments, each mobile core network 140 belongs to a single mobile network operator (“MNO”). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0050] The mobile core network 140 includes several network functions (“NFs”). As depicted, the mobile core network 140 includes at least one UPF 141. The mobile core network 140 also includes multiple control plane (“CP”) functions including, but not limited to, an Access and Mobility Management Function (“AMF”) 143 that serves the RAN 120, a Session Management Function (“SMF”) 145, a Location Management Function (“LMF”) 144, a Unified Data Management function (“UDM””) and a User Data Repository (“UDR”). Although specific numbers and types of network functions are depicted in Figure 1, one of skill in the art will recognize that any number and type of network functions may be included in the mobile core network 140.

[0051] The UPF(s) 141 is/are responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interconnecting Data Network (DN), in the 5G architecture. The AMF 143 is responsible for termination of non-access stratum (“NAS”) signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The SMF 145 is responsible for session management (e.g., session establishment, modification, release), remote unit (e.g., UE) IP address allocation & management, DE data notification, and traffic steering configuration of the UPF 141 for proper traffic routing.

[0052] The LMF 144 receives positioning measurements or estimates from RAN 120 and the remote unit 105 (e.g., via the AMF 143) and computes the position ofthe remote unit 105. The UDM is responsible for generation of Authentication and Key Agreement (“AKA”) credentials, user identification handling, access authorization, subscription management. The UDR is a repository of subscriber information and may be used to service a number of network functions. For example, the UDR may store subscription data, policy-related data, subscriber-related data that is permitted to be exposed to third party applications, and the like. In some embodiments, the UDM is co-located with the UDR, depicted as combined entity “UDM/UDR” 149.

[0053] In various embodiments, the mobile core network 140 may also include a Policy Control Function (“PCF”) (which provides policy rules to CP functions), a Network Repository Function (“NRF”) (which provides Network Function (“NF”) service registration and discovery, enabling NFs to identify appropriate services in one another and communicate with each other over Application Programming Interfaces (“APIs”)), a Network Exposure Function (“NEF”) (which is responsible for making network data and resources easily accessible to customers and network partners), an Authentication Server Function (“AUSF”), or other NFs defined for the 5GC. When present, the AUSF may act as an authentication server and/or authentication proxy, thereby allowing the AMF 143 to authenticate a remote unit 105. In certain embodiments, the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.

[0054] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a “network slice” refers to a portion of the mobile core network 140 optimized for a certain traffic type or communication service. For example, one or more network slices may be optimized for enhanced mobile broadband (“eMBB”) service. As another example, one or more network slices may be optimized for ultra-reliable low- latency communication (“URLLC”) service. In other examples, a network slice may be optimized for machine-type communication (“MTC”) service, massive MTC (“mMTC”) service, Intemet- of-Things (“loT”) service. In yet other examples, a network slice may be deployed for a specific application service, a vertical service, a specific use case, etc.

[0055] A network slice instance may be identified by a single-network slice selection assistance information (“S-NSSAI”) while a set of network slices for which the remote unit 105 is authorized to use is identified by network slice selection assistance information (“NSSAI”). Here, “NSSAI” refers to a vector value including one or more S-NSSAI values. In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF 145 and UPF 141. In some embodiments, the different network slices may share some common network functions, such as the AMF 143. The different network slices are not shown in Figure 1 for ease of illustration, but their support is assumed.

[0056] In one embodiment, as used herein, a sidelink connection 115 allows remote units 105 to communicate directly with each other (e.g., device-to-device communication) using sidelink (e.g., V2X communication) signals.

[0057] While Figure 1 depicts components of a 5G RAN and a 5G core network, the described embodiments for signaling slice to slice group mapping to a UE device apply to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM”, e.g., a 2G digital cellular network), General Packet Radio Service (“GPRS”), Universal Mobile Telecommunications System (“UMTS”), LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, and the like.

[0058] Moreover, in an LTE variant where the mobile core network 140 is an EPC, the depicted network functions may be replaced with appropriate EPC entities, such as a Mobility Management Entity (“MME”), a Serving Gateway (“SGW”), a PGW, a Home Subscriber Server (“HSS”), and the like. For example, the AMF 143 may be mapped to an MME, the SMF 145 may be mapped to a control plane portion of a PGW and/or to an MME, the UPF 141 may be mapped to an SGW and a user plane portion of the PGW, the UDM/UDR 149 may be mapped to an HSS, etc.

[0059] In the following descriptions, the term “RAN node” is used for the base station but it is replaceable by any other radio access node, e.g., gNB, ng-eNB, eNB, Base Station (“BS”), Access Point (“AP”), etc. Further, the operations are described mainly in the context of 5G NR. However, the proposed solutions/methods are also equally applicable to other mobile communication systems supporting signaling slice to slice group mapping to a UE device.

[0060] As background, 5G network slicing is a network architecture that enables the multiplexing of virtualized and independent logical networks on the same physical network infrastructure. Each network slice is an isolated end-to-end network tailored to fulfd diverse requirements requested by a particular application.

[0061] For this reason, this technology assumes a central role to support 5G mobile networks that are designed to efficiently embrace a plethora of services with very different SLRs. The realization of this service-oriented view of the network leverages on the concepts of SDN and NFV that allow the implementation of flexible and scalable network slices on top of a common network infrastructure.

[0062] Strong demand in wireless communication has been expected in vertical markets, as connectivity and mobility empower the transformation and innovation in industries such as manufacturing, transportation, energy and civil services, healthcare, and many more. These diverse vertical services bring about a wide range of performance requirements in throughput, capacity, latency, mobility, reliability, position accuracy, or the like. NR technology promises a common RAN platform to meet the challenges of current and future use cases and services, not only for those that we can envision today but also for those that we cannot yet imagine. And the works of network slicing in Rel-15 further advance network architecture towards more flexibility and higher scalability for a multitude of services of disparate requirements.

[0063] While Rel-15 specifications may provide the foundation of a common connectivity platform for various services, more efforts should be made in Rel-17 on RAN support of network slicing, to make it a tool that network operators can apply to meet the challenge of opening new source of revenue in addition to the one derived from customer subscription. More particularly, the new works should provide technical tools in RAN for network operators to get application providers involved in customizing RAN’s design, deployment and operation for better support of the applications providers’ business. [0064] The 3GPP work item on network slicing (RP-210912, incorporated herein by reference) sets one of the work objectives as: i. Support slice-based cell reselection, specify mechanisms and signaling including:

1. To assist cell reselection, broadcast the supported slice info of the current cell and neighbor cells, and cell reselection priority per slice in system information message.

2. To assist cell reselection, include slice info (with similar information as in SI message) in RRCRelease message.

[0065] RAN2 discusses the slice (S-NSSAI) based cell reselection and the following solution principles are included for cell reselection for the normative phase: i. RAN2 confirm the working assumption on option A without formula. ii. The UE should determine the frequency priority order according to the following rules:

1. Considering the slice/slice group priority provided by NAS, the frequencies that support higher priority slice/slice group have higher slice-based frequency priority than the frequencies that support lower priority slice/slice group;

2. Among the frequencies supporting a slice/slice group with the same priority, the UE should follow the slice specific frequency priority received in SIB or RRCRelease (if configured);

3. Among the frequencies supporting the same slice/slice group, the frequency not configured with slice specific reselection priority should be considered as lower priority than other frequencies configured with slice specific re selection priority;

4. The frequencies that support any slice/slice group have higher slice-based frequency priority than the frequencies that support none of slice/slice group;

5. For the frequencies that do not support any slice/slice group, the UE should follow the legacy cell reselection priority received in SIB, FFS when only legacy priority received in RRCRelease,' iii. RAN2 confirms that if the UE is configured with slice specific frequency priority via RRCRelease message, the UE shall ignore all the slice specific priorities provided in system information. iv. The legacy procedure (e.g., UE first enters any cell selection state and performs cell selection) should be reused when the UE cannot find a suitable cell using any cell reselection priorities (including slice-based and legacy (non-slice based) priorities) if the UE is configured with slice based dedicated priority. v. Inter-RAT frequencies are not configured with slice specific frequency priority, but inter-RAT frequencies can be considered using legacy cell reselection frequency priority after all NR frequencies that support any slice/slice group. vi. The slice specific cell reselection information provided by the network in SIB is slice group specific. vii. Reuse the legacy T320 timer for slice specific frequency priority in RRCRelease . viii. RAN sharing can be supported for slice based cell reselection and random access channel (“RACH”) by network implementation (e.g. dedicated priorities in RRCRelease). ix. The slice group specific cell reselection information can be provided by the network in RRCRelease. x. Re-sorting is defined as a change of frequency priority for reselection of a certain frequency requiring the UE to re-sort the ordered list of frequencies. This follows the earlier agreed principles for slice-specific reselection. Change of priority for slice-specific reselection does not impact existing RAN4 RRM requirements. xi. RAN2 agree that a re-sorting is applied if the UE performs slice-based cell reselection and if the highest ranked cell of the said frequency, according to neighboring cell information, does not support the highest priority slice supported by its frequency. xii . UE behavior for frequencies determined as “equal priority” is defined similar to UE behavior for the case of equal priority NR frequencies. xiii. PCI list per slice group per frequency can be provided in system information.

1. Network can indicate whether the PCI list is block-list (“cells not supporting the corresponding slice group”) or allow-list (“cells supporting the corresponding slice group”). xiv. RAN2 assumes (based on majority views in RAN2) that the mapping of slice to the slice groups for cell reselection are per TA.

[0066] The above principles, applied to Figure 2, govern how the UE performs a slicebased reselection procedure. [0067] In one embodiment, there are two problems that the subject matter herein presents solutions to:

[0068] As a first problem, for a UE performing slice-based cell reselection, if a cell (e.g., with cell identity Cl on frequency fl) fulfils the reselection criteria for cell reselection based on slice-based reselection priority for the frequency fl for a slice group SI, but this cell does not support the slice group (SI), the UE shall re-derive a reselection priority for the frequency by considering the slice group(s) supported by this cell (rather than those of the corresponding NR frequency).

[0069] This reselection priority may be used until the highest ranked cell changes on the frequency, or new slice priorities are received from NAS. For a frequency for each of its supported slice groups as configured in slice info, an allow-list (or include-list) and/or a block-list (or except- list or exclude-list) of cells can be provided to the UE where the former (e.g., the allow-list) indicates cells on that frequency that support a given slice and the latter (e.g., the block-list) indicates cells on that frequency that do not support a given slice. If the best ranked cell (Cl) on that frequency (fl) does not support the slice group (SI), it remains unclear how to determine which slice groups are supported by the best ranked cell (Cl) since it is inefficiently signaling to separately listed slices (slice groups) supported by each cell.

[0070] As a second problem, if the mapping information for mapping slices (e.g., NSSAIs or S-NSSAIs) to slice group ID is to be provided on a per tracking area (“TA”) basis, an efficient signaling method needs to be designed to avoid sending excessive and repeated information to the UE.

[0071] In one conventional solution, for the first problem, slice support information of each cell on each neighboring frequency can be provided by the serving cell but it can be very signaling inefficient since there can be as many as 96 such entries (12 cells * 8 frequencies) for which slice group support would need to be indicated.

[0072] In another conventional solution, for the second problem, mapping information for mapping slices (e.g., NSSAIs or S-NSSAIs) to slice group ID can be provided by a UE performing a Tracking Area Update (“TAU”) procedure even when the TA of a new cell, which is part of the T A-list of the registration area. This may be excessive because TAUs need a UE to transition to an RRC Connected state, thus consuming excessive UE battery.

[0073] As used herein, “slice info” is defined as frequency priority mapping for each of the slices (slice -> frequency(ies) -> absolute priority of each of the frequency) and therefore consists of the following elements - slice, frequency, and absolute frequency priority. The slice info (e.g., for a slice or slice group) is provided to the UE (e.g., as outlined in the RAN2 meeting#! 13e) using both broadcast and dedicated signaling. Slice info is provided for the serving frequency as well as neighboring frequencies.

[0074] As used herein, “slice support” is used to signify the slice (s)/slice group(s) supported in a particular cell or frequency.

[0075] In one embodiment, the described methods/embodiments herein are equally applicable to both “slices” or “slice groups.” A slice group, in one embodiment, consists of one or multiple slices, where one slice belongs to one and only one slice group for cell reselection purposes (so, there may be another slice-to-slice group mapping for RACH configuration and partitioning purpose) and each slice group is uniquely identified by a slice group identifier. This can avoid publishing slice identities (e.g., S-NSSAIs) in System Information, which may alleviate security concerns and SI size concerns. In one embodiment, according to conventional methods, the signaling of such slice grouping and slice group identity would be indicated in NAS signaling to the UE.

[0076] In a first embodiment related to the first problem described above, for a UE performing slice-based cell reselection, if a cell (e.g., a cell with cell identity Cl on frequency fl) fulfils the reselection criteria for cell reselection based on slice-based reselection priority for the frequency (fl) for a slice group (SI), but this cell does not support the slice group (SI), the UE shall re-derive a reselection priority for the frequency by considering the slice group(s) supported by this cell (rather than those of the corresponding NR frequency).

[0077] In one embodiment, this reselection priority shall be used until the highest ranked cell changes on the frequency or new slice priorities are received from NAS. For a frequency for each of its supported slice groups as configured in slice info, an allow-list (or include-list) and/or a block-list (or except-list or exclude-list) of cells can be provided to the UE where the former (e.g., allow-list) indicates all cells on that frequency that support a given slice and the latter (e.g., block-list) indicates all cells on that frequency that do not support a given slice. If the best ranked cell (Cl) on that frequency (fl) does not support the slice group (SI), to determine which slice groups are supported by (Cl), the UE may either: i. Option 1 : Read SIB1 (or any other SIB that contains the slice group list supported by the cell) of cell Cl; or ii. Option 2: Check individually for all slice groups supported on fl and build a list of slice groups supported by cell Cl in the following way:

1. Cl does not support a certain slice group if Cl is listed in the block-list for the slice group, or if the allow-list is signaled, but Cl is not listed in it; 2. Cl supports a certain slice group if cell Cl is listed in the allow-list for the slice group, or if the block -list is signaled, but Cl is not listed in it.

[0078] In one implementation, an alternative for Option 2, the UE may only consider the slice group information it receives from its NAS layer (e.g., not for all slice groups supported on fl).

[0079] In one alternative implementation of this embodiment, the network signals to the UE which of the above two options it should apply. This can be done by using a Boolean flag, e.g., “readSIB 1 -of-BlockCell” in the Slice Info. The network may signal the UE to use Option 1 (e.g., by setting “readSIB 1 -of-BlockCell” to TRUE) when it knows that the slice support information for each cell is not exhaustively provided in the slice info; otherwise, the network sets the flag, e.g., “readSIB 1 -of-BlockCell” to FALSE.

[0080] In a second embodiment related to Problem 2, in a registration accept message, the network (e.g., the AMF) provides more than one TA-sub-lists to the UE as part of its registration area, rather than just one TA-list as in the current-art. For each of the included multiple TA-sub- lists, the network provides mapping information for mapping slices (e.g., NSSAIs or S-NSSAIs) to slice group IDs. In one embodiment, the UE shall determine that the mapping information for mapping slices (e.g., NSSAIs or S-NSSAIs) to slice group IDs is the same across all TA(s) of a TA-sub-list included in that TA-sub-list. In one embodiment, this does not impact the total number of TAs signaled to the UE, e.g., if a network signals a total of ‘N’ TAs to a UE inside a TA-list, the total number of TAs included in all TA-sub-list is still ‘N’.

[0081] In a third embodiment related to Problem 2, the network (e.g., AMF) provides one TA-list, but indicates for which of the TAs included in the TA-list mapping information for mapping slices (e.g., NSSAIs or S-NSSAIs) to slice group IDs is being provided. In one implementation, this can be implemented by including a Boolean flag for each TA included in the TA-list, indicating whether the provided mapping information for mapping slices (e.g., NSSAIs or S-NSSAIs) to slice group IDs is applicable for the corresponding TA or not.

[0082] For example, in Table 1, there are 4 TAs included in the TA-list to the UE, but the mapping information is applicable only for TA-1 and TA-2 as the flag “Mapping-info-available” is set to TRUE only for these two tracking areas.

Table 1: Information included in the Registration Accept message [0083] The mapping information can be provided to the UE separately in the same Registration Accept message.

Table 1: Information included in the Registration Accept message. Slices b and c are mapped to the same Slice group (Id 2)

[0084] When the UE reselects a cell of the Tracking Areas TA-3 or TA-4, it sends a request to the network to provide the mapping information for mapping slices (a, b, c and d) to their Slice Group Id(s).

[0085] A fourth embodiment related to Problem 2 provides means to request the mapping information for mapping Slices (a, b, c and d) to their Slice Group Id(s) for TAs for which it does not already have the mapping. In one embodiment, this could be initiated based on certain conditions, shown as “Triggers” (see block 302) in Figure 3. In one example, this could be the tracking area of a new reselected cell; as another example this could be done even prior to a reselection to a cell of a different TA when the source cell quality is below a certain threshold.

[0086] In one implementation this is done using a RRC procedure (see block 304), where a gNB or gNB + AMF is the “Network” 303. In another implementation this is done using a NAS procedure, where an AMF is the “Network” 303. The NAS procedure could be a new procedure or embedded in one of the existing procedures like Routing Area Update/Tracking Area Update procedure. In any case, as shown in Figure 3, a Slice Mapping Information Request message (see messaging 306) is used by the UE 301 to request mapping information. This message may contain one or more Tracking areas and/or Slice Identities (e.g., NSSAI, S-NSSAI) that the UE 301 is requesting the mapping for. The network 303 determines this information (e.g., gNB requests AMF for the information) and provides the information to the UE 301 in Slice Mapping Information message (see messaging 308).

[0087] Figure 4 depicts a UE apparatus 400 that may be used for signaling slice to slice group mapping to a UE device, according to embodiments of the disclosure. In various embodiments, the UE apparatus 400 is used to implement one or more of the solutions described above. The UE apparatus 400 may be one embodiment of the remote unit 105 and/or the UE 205, described above. Furthermore, the UE apparatus 400 may include a processor 405, a memory 410, an input device 415, an output device 420, and a transceiver 425. [0088] In some embodiments, the input device 415 and the output device 420 are combined into a single device, such as a touchscreen. In certain embodiments, the UE apparatus 400 may not include any input device 415 and/or output device 420. In various embodiments, the UE apparatus 400 may include one or more of: the processor 405, the memory 410, and the transceiver 425, and may not include the input device 415 and/or the output device 420.

[0089] As depicted, the transceiver 425 includes at least one transmitter 430 and at least one receiver 435. In some embodiments, the transceiver 425 communicates with one or more cells (or wireless coverage areas) supported by one or more base units 121. In various embodiments, the transceiver 425 is operable on unlicensed spectrum. Moreover, the transceiver 425 may include multiple UE panels supporting one or more beams. Additionally, the transceiver 425 may support at least one network interface 440 and/or application interface 445. The application interface(s) 445 may support one or more APIs. The network interface(s) 440 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 440 may be supported, as understood by one of ordinary skill in the art.

[0090] The processor 405, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 405 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 405 executes instructions stored in the memory 410 to perform the methods and routines described herein. The processor 405 is communicatively coupled to the memory 410, the input device 415, the output device 420, and the transceiver 425.

[0091] In various embodiments, the processor 405 controls the UE apparatus 400 to implement the above-described UE behaviors. In certain embodiments, the processor 405 may include an application processor (also known as “main processor”) which manages applicationdomain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.

[0092] The memory 410, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 410 includes volatile computer storage media. For example, the memory 410 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 410 includes non-volatile computer storage media. For example, the memory 410 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 410 includes both volatile and non-volatile computer storage media. [0093] In some embodiments, the memory 410 stores data related to signaling slice to slice group mapping to a UE device. For example, the memory 410 may store various parameters, panel/beam configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 410 also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus 400.

[0094] The input device 415, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 415 may be integrated with the output device 420, for example, as a touchscreen or similar touch -sensitive display. In some embodiments, the input device 415 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 415 includes two or more different devices, such as a keyboard and a touch panel.

[0095] The output device 420, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 420 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 420 may include, but is not limited to, a Liquid Crystal Display (“LCD”), a Light- Emitting Diode (“LED”) display, an Organic LED (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 420 may include a wearable display separate from, but communicatively coupled to, the rest of the UE apparatus 400, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 420 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0096] In certain embodiments, the output device 420 includes one or more speakers for producing sound. For example, the output device 420 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 420 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all, or portions of the output device 420 may be integrated with the input device 415. For example, the input device 415 and output device 420 may form atouchscreen or similar touch-sensitive display. In other embodiments, the output device 420 may be located near the input device 415.

[0097] The transceiver 425 communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver 425 operates under the control of the processor 405 to transmit messages, data, and other signals and to receive messages, data, and other signals. For example, the processor 405 may selectively activate the transceiver 425 (or portions thereof) at times to send and receive messages.

[0098] The transceiver 425 includes at least transmitter 430 and at least one receiver 435. One or more transmitters 430 may be used to provide UL communication signals to a base unit 121, such as the UL transmissions described herein. Similarly, one or more receivers 435 may be used to receive DL communication signals from the base unit 121, as described herein. Although only one transmitter 430 and one receiver 435 are illustrated, the UE apparatus 400 may have any suitable number of transmitters 430 and receivers 435. Further, the transmitter(s) 430 and the receiver(s) 435 may be any suitable type of transmitters and receivers. In one embodiment, the transceiver 425 includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.

[0099] In certain embodiments, the first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components. For example, certain transceivers 425, transmitters 430, and receivers 435 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 440.

[0100] In various embodiments, one or more transmitters 430 and/or one or more receivers 435 may be implemented and/or integrated into a single hardware component, such as a multitransceiver chip, a system -on-a-chip, an Application-Specific Integrated Circuit (“ASIC”), or other type of hardware component. In certain embodiments, one or more transmitters 430 and/or one or more receivers 435 may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface 440 or other hardware components/circuits may be integrated with any number of transmitters 430 and/or receivers 435 into a single chip. In such embodiment, the transmitters 430 and receivers 435 may be logically configured as a transceiver 425 that uses one more common control signals or as modular transmitters 430 and receivers 435 implemented in the same hardware chip or in a multi-chip module.

[0101] In one embodiment, the memory 410 includes instructions that are executable by the processor 405 to cause the apparatus 400 to receive, from a network, for each pair of slice group and frequency, one or more of an allow list of cells, a block list of cells, and a flag indicating how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the SIB1 information of the cell. In one embodiment, the instructions are further executable by the processor 405 to cause the apparatus 400 to determine whether a highest ranked cell is listed in the block list of cells for a corresponding slice group and frequency pair and, in response to the highest ranked cell being listed in the block list, determine slice groups that are supported by the highest ranked cell in the block list.

[0102] In one embodiment, the instructions are further executable by the processor 405 to cause the apparatus 400 to acquire the SIB 1 of the highest ranked cell listed in the corresponding block list in response to the flag set to TRUE.

[0103] In one embodiment, in response to the flag being absent or set to FALSE, the instructions are further executable by the processor 405 to cause the apparatus 400 to check individually for slice groups supported on a frequency of the highest ranked cell and prepares a list of slice groups supported by the highest ranked cell by concluding that the highest ranked cell does not support a certain slice group in response to the highest ranked cell being listed in the block-list for the slice group and/or the allow-list is signaled but the highest ranked cell is not listed in it and the highest ranked cell supports a certain slice group in response to the highest ranked cell being listed in the allow-list for the slice group and/or the block-list is signaled but the highest ranked cell is not listed in it.

[0104] In one embodiment, the instructions are further executable by the processor 405 to cause the apparatus 400 to consider slice group information received from its NAS layer.

[0105] In one embodiment, the instructions are further executable by the processor 405 to cause the apparatus 400 to receive a plurality of TA sub-lists from the network in a registration accept message, each of the TA sub-lists comprising mapping information for mapping slices to slice group identifiers.

[0106] In one embodiment, the instructions are further executable by the processor 405 to cause the apparatus 400 to receive an indication of which of the TAs in a received TA sub-list is provided with mapping information for mapping slices to slice group identifiers.

[0107] In one embodiment, the instructions are further executable by the processor 405 to cause the apparatus 400 to transmit a request to the network for mapping information for mapping slices to slice group identifiers for a TA for which a mapping is unknown.

[0108] Figure 5 depicts a network apparatus 500 that may be used for signaling slice to slice group mapping to a UE device, according to embodiments of the disclosure. In one embodiment, network apparatus 500 may be one implementation of a RAN node, such as the base unit 121 and/or the RAN node 210, as described above. Furthermore, the base network apparatus 500 may include a processor 505, a memory 510, an input device 515, an output device 520, and a transceiver 525.

[0109] In some embodiments, the input device 515 and the output device 520 are combined into a single device, such as a touchscreen. In certain embodiments, the network apparatus 500 may not include any input device 515 and/or output device 520. In various embodiments, the network apparatus 500 may include one or more of: the processor 505, the memory 510, and the transceiver 525, and may not include the input device 515 and/or the output device 520.

[0110] As depicted, the transceiver 525 includes at least one transmitter 530 and at least one receiver 535. Here, the transceiver 525 communicates with one or more remote units 175. Additionally, the transceiver 525 may support at least one network interface 540 and/or application interface 545. The application interface(s) 545 may support one or more APIs. The network interface(s) 540 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 540 may be supported, as understood by one of ordinary skill in the art.

[0111] The processor 505, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 505 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller. In some embodiments, the processor 505 executes instructions stored in the memory 510 to perform the methods and routines described herein. The processor 505 is communicatively coupled to the memory 510, the input device 515, the output device 520, and the transceiver 525.

[0112] In various embodiments, the network apparatus 500 is a RAN node (e.g., gNB) that communicates with one or more UEs, as described herein. In such embodiments, the processor 505 controls the network apparatus 500 to perform the above-described RAN behaviors. When operating as a RAN node, the processor 505 may include an application processor (also known as “main processor”) which manages application-domain and OS functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.

[0113] The memory 510, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 510 includes volatile computer storage media. For example, the memory 510 may include a RAM, including DRAM, SDRAM, and/or SRAM. In some embodiments, the memory 510 includes non-volatile computer storage media. For example, the memory 510 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 510 includes both volatile and nonvolatile computer storage media. [0114] In some embodiments, the memory 510 stores data related to signaling slice to slice group mapping to a UE device. For example, the memory 510 may store parameters, configurations, resource assignments, policies, and the like, as described above. In certain embodiments, the memory 510 also stores program code and related data, such as an operating system or other controller algorithms operating on the apparatus 500.

[0115] The input device 515, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 515 may be integrated with the output device 520, for example, as a touchscreen or similar touch -sensitive display. In some embodiments, the input device 515 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 515 includes two or more different devices, such as a keyboard and a touch panel.

[0116] The output device 520, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 520 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 520 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 520 may include a wearable display separate from, but communicatively coupled to, the rest of the network apparatus 500, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 520 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0117] In certain embodiments, the output device 520 includes one or more speakers for producing sound. For example, the output device 520 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 520 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all, or portions of the output device 520 may be integrated with the input device 515. For example, the input device 515 and output device 520 may form atouchscreen or similar touch-sensitive display. In other embodiments, the output device 520 may be located near the input device 515.

[0118] The transceiver 525 includes at least transmitter 530 and at least one receiver 535. One or more transmitters 530 may be used to communicate with the UE, as described herein. Similarly, one or more receivers 535 may be used to communicate with network functions in the PLMN and/or RAN, as described herein. Although only one transmitter 530 and one receiver 535 are illustrated, the network apparatus 500 may have any suitable number of transmitters 530 and receivers 535. Further, the transmitter(s) 530 and the receiver(s) 535 may be any suitable type of transmitters and receivers.

[0119] In one embodiment, the memory 510 includes instructions that are executable by the processor 505 to cause the apparatus 500 to determine an allow-list of physical cell identities for each frequency supporting a slice group, determine a block-list of physical cell identities for each frequency supporting a slice group, determine a value of a flag indicating to a UE how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the SIB1 information of the cell, and transmit the allow-list, the block-list, and the flag to the UE.

[0120] In one embodiment, the allow-list contains a list of physical cell identities that support the slice group on a given frequency.

[0121] In one embodiment, the block-list contains a list of physical cell identities that do not support the slice group on a given frequency.

[0122] In one embodiment, the instructions are further executable by the processor 505 to cause the apparatus 500 to transmit slice group information to the UE on the UEs NAS layer.

[0123] In one embodiment, the instructions are further executable by the processor 505 to cause the apparatus 500 to transmit a plurality of TA sub-lists from the network in a registration accept message, each of the TA sub-lists comprising mapping information for mapping slices to slice group identifiers.

[0124] In one embodiment, the instructions are further executable by the processor 505 to cause the apparatus 500 to transmit an indication of which of the TAs in a received TA sub-list is provided with mapping information for mapping slices to slice group identifiers.

[0125] In one embodiment, the instructions are further executable by the processor 505 to cause the apparatus 500 to receive a request to the network for mapping information for mapping slices to slice group identifiers for a TA for which a mapping is unknown.

[0126] Figure 6 depicts one embodiment of a method 600 for signaling slice to slice group mapping to a UE device, according to embodiments of the disclosure. In various embodiments, the method 600 is performed by a UE device in a mobile communication network, such as the remote unit 105, the UE 205, and/or the UE apparatus 400. In some embodiments, the method 600 is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0127] In one embodiment, the method 600 begins and receives 605, from a network, for each pair of slice group and frequency, one or more of an allow list of cells, a block list of cells, and a flag indicating how to determine the slice groups supported by a cell listed as a non- supporting cell of a slice group without reading the SIB1 information of the cell. In one embodiment, the method 600 determines 610 whether a highest ranked cell is listed in the block list of cells for a corresponding slice group and frequency pair. In one embodiment, the method 600, in response to the highest ranked cell being listed in the block list, determines 615 slice groups that are supported by the highest ranked cell in the block list, and the method 600 ends.

[0128] Figure 7 depicts one embodiment of a method 700 for signaling slice to slice group mapping to a UE device, according to embodiments of the disclosure. In various embodiments, the method 700 is performed by a network equipment apparatus 500, such as base unit 121. In some embodiments, the method 700 is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0129] In one embodiment, the method 700 begins and determines 705 an allow-list of physical cell identities for each frequency supporting a slice group. In one embodiment, the method 700 determines 710 a block -list of physical cell identities for each frequency supporting a slice group. In one embodiment, the method 700 determines 715 a value of a flag indicating to a UE how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the SIB1 information of the cell. In one embodiment, the method 700 transmits 720 the allow-list, the block-list, and the flag to the UE, and the method 700 ends.

[0130] Disclosed herein is a first apparatus for signaling slice to slice group mapping to a UE device, according to embodiments of the disclosure. The first apparatus may be implemented by a UE device in a mobile communication network, such as the remote unit 105, the UE 205, and/or the UE apparatus 400. In one embodiment, the first apparatus is implemented by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0131] In one embodiment, the first apparatus includes a processor and a memory coupled to the processor. In one embodiment, the memory includes instructions that are executable by the processor to cause the apparatus to receive, from a network, for each pair of slice group and frequency, one or more of an allow list of cells, a block list of cells, and a flag indicating how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the SIB1 information of the cell. In one embodiment, the instructions are further executable by the processor to cause the apparatus to determine whether a highest ranked cell is listed in the block list of cells for a corresponding slice group and frequency pair and, in response to the highest ranked cell being listed in the block list, determine slice groups that are supported by the highest ranked cell in the block list. [0132] In one embodiment, the instructions are further executable by the processor to cause the apparatus to acquire the SIB 1 of the highest ranked cell listed in the corresponding block list in response to the flag set to TRUE.

[0133] In one embodiment, in response to the flag being absent or set to FALSE, the instructions are further executable by the processor to cause the apparatus to check individually for slice groups supported on a frequency of the highest ranked cell and prepares a list of slice groups supported by the highest ranked cell by concluding that the highest ranked cell does not support a certain slice group in response to the highest ranked cell being listed in the block-list for the slice group and/or the allow-list is signaled but the highest ranked cell is not listed in it and the highest ranked cell supports a certain slice group in response to the highest ranked cell being listed in the allow-list for the slice group and/or the block-list is signaled but the highest ranked cell is not listed in it.

[0134] In one embodiment, the instructions are further executable by the processor to cause the apparatus to consider slice group information received from its NAS layer.

[0135] In one embodiment, the instructions are further executable by the processor to cause the apparatus to receive a plurality of TA sub-lists from the network in a registration accept message, each of the TA sub-lists comprising mapping information for mapping slices to slice group identifiers.

[0136] In one embodiment, the instructions are further executable by the processor to cause the apparatus to receive an indication of which of the TAs in a received TA sub-list is provided with mapping information for mapping slices to slice group identifiers.

[0137] In one embodiment, the instructions are further executable by the processor to cause the apparatus to transmit a request to the network for mapping information for mapping slices to slice group identifiers for a TA for which a mapping is unknown.

[0138] Disclosed herein is a first method for signaling slice to slice group mapping to a UE device, according to embodiments of the disclosure. The first method is performed by a UE device in a mobile communication network, such as the remote unit 105, the UE 205, and/or the UE apparatus 400, described above. In some embodiments, the first method is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0139] In one embodiment, the first method receives, from a network, for each pair of slice group and frequency, one or more of an allow list of cells, a block list of cells, and a flag indicating how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the SIB1 information of the cell. [0140] In one embodiment, the first method determines whether a highest ranked cell is listed in the block list of cells for a corresponding slice group and frequency pair and, in response to the highest ranked cell being listed in the block list, determines slice groups that are supported by the highest ranked cell in the block list.

[0141] In one embodiment, the first method acquires the SIB1 of the highest ranked cell listed in the corresponding block list in response to the flag set to TRUE.

[0142] In one embodiment, in response to the flag being absent or set to FALSE, the first method checks individually for slice groups supported on a frequency of the highest ranked cell and prepares a list of slice groups supported by the highest ranked cell by concluding that the highest ranked cell does not support a certain slice group in response to the highest ranked cell being listed in the block-list for the slice group and/or the allow-list is signaled but the highest ranked cell is not listed in it and the highest ranked cell supports a certain slice group in response to the highest ranked cell being listed in the allow-list for the slice group and/or the block -list is signaled but the highest ranked cell is not listed in it.

[0143] In one embodiment, the first method only considers slice group information received from its NAS layer.

[0144] In one embodiment, the first method receives a plurality of TA sub-lists from the network in a registration accept message, each of the TA sub-lists comprising mapping information for mapping slices to slice group identifiers.

[0145] In one embodiment, the first method receives an indication of which of the TAs in a received TA sub-list is provided with mapping information for mapping slices to slice group identifiers.

[0146] In one embodiment, the first method transmits a request to the network for mapping information for mapping slices to slice group identifiers for a TA for which a mapping is unknown.

[0147] Disclosed herein is a second apparatus for signaling slice to slice group mapping to a UE device, according to embodiments of the disclosure. The second apparatus may be implemented by a network function and/or a network equipment apparatus 500, such as a base unit 121. In one embodiment, the second apparatus is implemented by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0148] In one embodiment, the second apparatus includes a processor and a memory coupled to the processor. In one embodiment, the memory includes instructions that are executable by the processor to cause the apparatus to determine an allow-list of physical cell identities for each frequency supporting a slice group, determine a block-list of physical cell identities for each frequency supporting a slice group, determine a value of a flag indicating to a UE how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the SIB 1 information of the cell, and transmit the allow-list, the block -list, and the flag to the UE.

[0149] In one embodiment, the allow-list contains a list of physical cell identities that support the slice group on a given frequency.

[0150] In one embodiment, the block-list contains a list of physical cell identities that do not support the slice group on a given frequency.

[0151] In one embodiment, the instructions are further executable by the processor to cause the apparatus to transmit slice group information to the UE on the UEs NAS layer.

[0152] In one embodiment, the instructions are further executable by the processor to cause the apparatus to transmit a plurality of TA sub-lists from the network in a registration accept message, each of the TA sub-lists comprising mapping information for mapping slices to slice group identifiers.

[0153] In one embodiment, the instructions are further executable by the processor to cause the apparatus to transmit an indication of which of the TAs in a received TA sub-list is provided with mapping information for mapping slices to slice group identifiers.

[0154] In one embodiment, the instructions are further executable by the processor to cause the apparatus to receive a request to the network for mapping information for mapping slices to slice group identifiers for a TA for which a mapping is unknown.

[0155] Disclosed herein is a second method for signaling slice to slice group mapping to a UE device, according to embodiments of the disclosure. The second method is performed by a network function and/or a network equipment apparatus 500, such as a base unit 121. In some embodiments, the second method is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0156] In one embodiment, the second method determines an allow-list of physical cell identities for each frequency supporting a slice group, determines a block-list of physical cell identities for each frequency supporting a slice group, and determines a value of a flag indicating to a UE how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the SIB1 information of the cell. In one embodiment, the second method transmits the allow-list, the block-list, and the flag to the UE.

[0157] In one embodiment, the allow-list contains a list of physical cell identities that support the slice group on a given frequency.

[0158] In one embodiment, the block-list contains a list of physical cell identities that do not support the slice group on a given frequency. [0159] In one embodiment, the second method transmits slice group information to the UE on the UEs NAS layer.

[0160] In one embodiment, the second method transmits a plurality of TA sub-lists from the network in a registration accept message, each of the TA sub-lists comprising mapping information for mapping slices to slice group identifiers.

[0161] In one embodiment, the second method transmits an indication of which of the TAs in a received TA sub-list is provided with mapping information for mapping slices to slice group identifiers.

[0162] In one embodiment, the second method receives a request to the network for mapping information for mapping slices to slice group identifiers for a TA for which a mapping is unknown.

[0163] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

CLAIMS An apparatus, comprising: a processor; and a memory coupled to the processor, the memory comprising instructions executable by the processor to cause the apparatus to: receive, from a network, for each pair of slice group and frequency, one or more of an allow list of cells, a block list of cells, and a flag indicating how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the system information block (“SIB1”) information of the cell; determine whether a highest ranked cell is listed in the block list of cells for a corresponding slice group and frequency pair; and in response to the highest ranked cell being listed in the block list, determine slice groups that are supported by the highest ranked cell in the block list. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to acquire the SIB1 of the highest ranked cell listed in the corresponding block list in response to the flag set to TRUE. The apparatus of claim 1, wherein, in response to the flag being absent or set to FALSE, the instructions are further executable by the processor to cause the apparatus to check individually for slice groups supported on a frequency of the highest ranked cell and prepares a list of slice groups supported by the highest ranked cell by concluding that: the highest ranked cell does not support a certain slice group in response to the highest ranked cell being listed in the block-list for the slice group and/or the allow-list is signaled but the highest ranked cell is not listed in it; and the highest ranked cell supports a certain slice group in response to the highest ranked cell being listed in the allow-list for the slice group and/or the block -list is signaled but the highest ranked cell is not listed in it. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to consider slice group information received from its NAS layer. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to receive a plurality of tracking area (“TA”) sub-lists from the network in a registration accept message, each of the TA sub-lists comprising mapping information for mapping slices to slice group identifiers. The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to receive an indication of which of the TAs in a received tracking area (“TA”) sub-list is provided with mapping information for mapping slices to slice group identifiers. The apparatus of claim 6, wherein the instructions are further executable by the processor to cause the apparatus to transmit a request to the network for mapping information for mapping slices to slice group identifiers for a TA for which a mapping is unknown. An apparatus, comprising: a processor; and a memory coupled to the processor, the memory comprising instructions executable by the processor to cause the apparatus to: determine an allow-list of physical cell identities for each frequency supporting a slice group; determine a block-list of physical cell identities for each frequency supporting a slice group; determine a value of a flag indicating to a user equipment (“UE”) how to determine the slice groups supported by a cell listed as a nonsupporting cell of a slice group without reading the system information block (“SIB1”) information of the cell; and transmit the allow-list, the block-list, and the flag to the UE. The apparatus of claim 8, wherein the allow-list contains a list of physical cell identities that support the slice group on a given frequency. The apparatus of claim 8, wherein the block-list contains a list of physical cell identities that do not support the slice group on a given frequency. The apparatus of claim 8, wherein the instructions are further executable by the processor to cause the apparatus to transmit slice group information to the UE on the UEs NAS layer. The apparatus of claim 8, wherein the instructions are further executable by the processor to cause the apparatus to transmit a plurality of tracking area (“TA”) sub-lists from the network in a registration accept message, each of the TA sub-lists comprising mapping information for mapping slices to slice group identifiers. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to transmit an indication of which of the TAs in a received tracking area (“TA”) sub-list is provided with mapping information for mapping slices to slice group identifiers. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to receive a request to the network for mapping information for mapping slices to slice group identifiers for a TA for which a mapping is unknown. A method, comprising: receiving, from a network, for each pair of slice group and frequency, one or more of an allow list of cells, a block list of cells, and a flag indicating how to determine the slice groups supported by a cell listed as a non-supporting cell of a slice group without reading the system information block (“SIB1”) information of the cell; determining whether a highest ranked cell is listed in the block list of cells for a corresponding slice group and frequency pair; and in response to the highest ranked cell being listed in the block list, determining slice groups that are supported by the highest ranked cell in the block list.