configuration indication

Abstract

An apparatus is provided that includes means for performing: receiving a first message, the first message indicating information for at least one network slice identification in one or more radio network areas; receiving a second message, the second message indicating configuration information for one or more network slices; determining, based on the first message and the second message, a configuration to be used for a given network slice.

Description

Technical Field

[0001] Various example embodiments generally relate to configuration instructions in networks including network slices. Background Technology

[0002] 5G networks are designed to support highly diverse and extreme requirements for latency, throughput, capacity, and availability. Network slicing provides a solution to meet the requirements of all use cases in public network infrastructure. A network slice can be described as a network architecture capable of multiplexing and virtualizing independent logical networks on the same physical network infrastructure. Each network slice can be viewed as an independent end-to-end network specifically designed to meet the diverse requirements requested by a particular application. Therefore, network slices can use the same underlying mobile network infrastructure to support different services. Network slices can differ in their service requirements, such as Ultra-Reliable Low-Latency Communication (URLLC) and Enhanced Mobile Broadband (eMBB), and also in the tenants providing these services.

[0003] Different network slices can benefit from the use of dedicated configurations. However, at the same time, to avoid fraud, the provision of configurations cannot be too transparent. For example, to access a network, a user equipment can use a random access (RA) procedure. This procedure includes, for example, sending an RA preamble in the uplink on RA resources. Some network slices can benefit from being associated with predetermined RA configurations or resources. Summary of the Invention

[0004] The subject matter of the independent claims is provided according to several aspects. Additional aspects are defined in the dependent claims. Embodiments not falling within the scope of the claims are to be interpreted as examples that aid in understanding this disclosure. Attached Figure Description

[0005] The invention will now be described in more detail with reference to embodiments and accompanying drawings, in which... Figure 1 A communication network according to one embodiment is shown;

[0006] Figure 2A An example of how to identify network slices is shown;

[0007] Figure 2B A random access procedure according to one embodiment is illustrated;

[0008] Figure 3 , Figure 4A and Figure 4B Methods according to some embodiments are shown;

[0009] Figures 5 and 6 illustrate the contents that a first message and a second message may include according to some embodiments;

[0010] Figure 7 A signaling flowchart according to one embodiment is shown; and

[0011] Figure 8 and Figure 9 An apparatus according to some embodiments is shown. Detailed Implementation

[0012] The following embodiments are exemplary. Although the specification may refer to "an," "one," or "some" embodiments in several places in the text, this does not necessarily mean that each reference relates to the same embodiment or that a particular feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments. For the purposes of this disclosure, the phrases "A or B" and "A and / or B" refer to (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A, B, and / or C" refer to (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0013] The described embodiments can be implemented in radio systems, such as radio systems including at least one of the following radio access technologies (RATs): Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, and Enhanced LTE (eLTE). The term "eLTE" here refers to LTE evolution connected to the 5G core. LTE is also known as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN). The term "resource" can refer to radio resources, such as Physical Resource Blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. The terms "transmit" and / or "receive" can refer to wireless transmission and / or reception over radio resources via a radio propagation channel.

[0014] However, the embodiments are not limited to the system / RAT given as an example, but those skilled in the art can apply this solution to other communication systems with the necessary characteristics. An example of a suitable communication system is the 5G system. The 3GPP solution for 5G is called New Radio (NR). 5G has been envisioned using multiple-input multiple-output (MIMO) multi-antenna transmission technology, deploying more base stations or nodes than current LTE networks (the so-called small cell concept), including macro sites operating in cooperation with smaller LAN access nodes, and potentially employing various radio technologies to achieve better coverage and enhanced data rates. 5G can consist of more than one radio access technology / radio access network (RAT / RAN), each optimized for specific use cases and / or spectrum. 5G mobile communications can have a wider range of use cases and associated applications, including video streaming, augmented reality, different data sharing methods, and various forms of machine-type applications, including vehicle safety, different sensors, and real-time control. 5G is expected to have multiple radio interfaces, namely sub-6GHz, cmWave, and mmWave, and can be integrated with existing legacy radio access technologies such as LTE.

[0015] The current architecture in LTE networks is distributed across radios and centralized in the core network. Low-latency applications and services in 5G require content to be closer to the radio, leading to local bursts and multiple access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the data source. This approach requires leveraging resources that may not have continuous network connectivity, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It also enables the storage and processing of content near cellular subscribers for faster response times. Edge computing encompasses a wide range of technologies, such as wireless sensor networks, mobile data acquisition, mobile signature analytics, collaborative distributed peer-to-peer ad hoc networks and processing (which can also be categorized as local cloud / fog computing and grid / mesh computing), dew computing, mobile edge computing, cloud, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (IoT) (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications). Edge cloud can be brought into the RAN using Network Functions Virtualization (NVF) and Software-Defined Networking (SDN). Using edge cloud allows access node operations to be performed at least partially within a server, host, or node that is operatively coupled to a remote radio head or base station, including radio components. Network slicing allows the creation of multiple virtual networks over a shared public physical infrastructure. These virtual networks can then be customized to meet the specific needs of applications, services, devices, customers, or operators.

[0016] In radio communications, node operations can be performed at least partially in a central / centralized unit (CU) (e.g., a server, host, or node) operatively coupled to a distributed unit (DU) (e.g., a radio headend / node). Node operations can also occur separately among multiple servers, nodes, or hosts. It should also be understood that the workload distribution between core network operations and base station operations can vary depending on the implementation. Therefore, 5G network architectures can be based on so-called CU-DU splitting. One gNB-CU controls several gNB-DUs. The term "gNB" in 5G can correspond to the eNB in ​​LTE. One or more gNBs can communicate with one or more UEs. A gNB-CU (central node) can control multiple spatially separated gNB-DUs, which at least act as transmit / receive (Tx / Rx) nodes. However, in some embodiments, the gNB-DU (also known as DU) may include, for example, the Radio Link Control (RLC), Media Access Control (MAC) layer, and Physical (PHY) layer, while the gNB-CU (also known as CU) may include layers above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Internet Protocol (IP) layer. Other functional splits are also possible. Those skilled in the art are believed to be familiar with the OSI model and the functions within each layer.

[0017] In one embodiment, the server or CU can generate a virtual network through which the server communicates with radio nodes. Typically, a virtual network can involve the process of combining hardware and software network resources and functions into a single software-based management entity (virtual network). Such a virtual network can provide flexible operational allocation between the server and the radio head end / node. In practice, any digital signal processing task can be performed in the CU or DU, and the boundary for transferring responsibilities between the CU and DU can be chosen depending on the implementation.

[0018] Some other technological advancements that might be used include Software-Defined Networking (SDN), big data, and all-IP, to name just a few non-limiting examples. For instance, network slicing can be a form of virtual network architecture that uses the same principles behind Software-Defined Networking (SDN) and Network Functions Virtualization (NFV) in fixed networks. SDN and NFV can provide greater network flexibility by allowing traditional network architectures to be divided into virtual elements that can be linked (also via software). Network slicing allows the creation of multiple virtual networks on top of a shared physical infrastructure. These virtual networks can then be customized to meet the specific needs of applications, services, devices, customers, or operators.

[0019] Multiple gNBs (access points / nodes) (each comprising a CU and one or more DUs) can connect to each other via the Xn interface, through which the gNBs negotiate. The gNBs can also connect to the 5G core network (5GC) via a next-generation (NG) interface, which can be the 5G equivalent of the LTE core network. This 5G CU-DU split architecture can be implemented using a cloud / server architecture, allowing the higher-level CU to reside in the cloud, while the DU is closer to or includes the actual radio and antenna units. Similar plans are underway for LTE / LTE-A / eLTE. When both eLTE and 5G use a similar architecture in the same cloud hardware (HW), the next step could be a combined software (SW) architecture, enabling a single common SW to control both radio access networks / technologies (RAN / RAT). This allows for new ways to control radio resources for both RANs. Furthermore, configurations can exist where the entire protocol stack is controlled by the same HW as the CU and processed by the same radio units as the CU.

[0020] It should also be understood that the operational distribution between core network operations and base station operations may differ from, or even not exist at all, the LTE operational distribution. Some other technological advancements that may be used include big data and all-IP, which could potentially alter how networks are structured and managed. 5G (or New Radio) networks are designed to support multiple hierarchical structures, where MEC servers can be placed between the core and base stations or Node Bs (gNBs). It should be understood that MEC can also be applied to 4G networks.

[0021] 5G can also leverage satellite communications to enhance or supplement the coverage of 5G services, for example, by providing backhaul. Possible use cases include providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on board vehicles, or ensuring the availability of critical communications and future rail / maritime / aviation communications. Satellite communications can utilize geostationary orbit (GEO) satellite systems, as well as low Earth orbit (LEO) satellite systems, particularly mega-constellations (systems deploying hundreds of (nano) satellites). Each satellite in a mega-constellation can cover several satellite network entities that create a ground cell. Ground cells can be created via ground relay nodes or by gNBs located on the ground or in satellites.

[0022] The embodiments can also be applied to narrowband (NB) Internet of Things (IoT) systems, which enable the connection of various devices and services using cellular telecommunications bands. NB-IoT is a narrowband radio technology designed for the Internet of Things (IoT) and is one of the technologies standardized by the 3rd Generation Partnership Project (3GPP). Other 3GPP IoT technologies also suitable for implementing the embodiments include Machine Type Communication (MTC) and eMTC (enhanced Machine Type Communication). NB-IoT focuses on low cost, long battery life, and enabling a large number of connected devices. NB-IoT technology is deployed "in-band" in the spectrum allocated to Long Term Evolution (LTE)—using resource blocks within ordinary LTE carriers, or deployed in unused resource blocks within the guard band of LTE carriers—or "standalone" in dedicated spectrum.

[0023] The embodiments can also be applied to device-to-device (D2D), machine-to-machine, and peer-to-peer (P2P) communications. The embodiments can also be applied to vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and infrastructure-to-vehicle (I2V), or generally to V2X or X2V communications.

[0024] Figure 1 An example of a communication system to which embodiments of the present invention can be applied is shown. The system may include a control node 110 providing one or more cells (such as cell 100) and a control node 112 providing one or more other cells (such as cell 102). For example, each cell may be a macro cell, micro cell, femtocell, or picocell. From another perspective, a cell may define the coverage area or service area of ​​a corresponding access node. Control nodes 110 and 112 may be an evolved Node B (eNB) in LTE and LTE-A, eLTE in 5G, ng-eNB in ​​gNB, or any other device capable of controlling radio communications and managing radio resources within the cell. Control nodes 110 and 112 may be referred to as a base station, network node, or access node.

[0025] The system can be a cellular communication system consisting of a radio access network of access nodes, with each access node controlling one or more corresponding cells. Access node 110 can provide user equipment (UE) 120 (one or more UEs) with radio access to other networks such as the Internet. Radio access can include downlink (DL) communication from the control node to UE 120 and uplink (UL) communication from UE 120 to the control node.

[0026] Furthermore, although not shown, one or more LAN access nodes may be arranged such that the cell provided by the LAN access node at least partially overlaps with the cell of access nodes 110 and / or 112. The LAN access node may provide radio access within a sub-cell. Examples of sub-cells may include microcells, picocells, and / or femtocells. Typically, a sub-cell provides a hotspot within a macrocell. The operation of the local access node may be controlled by an access node, under which the sub-cell is provided. Typically, the control node for a small cell may also be referred to as a base station, network node, or access node.

[0027] Multiple UEs 120 and 122 can exist in this system. Each of them can be served by the same or different control nodes 110 and 112. UEs 120 and 122 can communicate with each other if a D2D communication interface is established between them.

[0028] The term "terminal device" or "UE" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal equipment", "communication equipment", "terminal", "user equipment" and "UE" are used interchangeably.

[0029] In a communication network with multiple access nodes, these nodes can connect to each other via an interface. The LTE specification refers to such an interface as the X2 interface. For IEEE 802.11 networks (i.e., WLAN, WiFi), access points can provide a similar interface, Xw. The interface between an eLTE access point and a 5G access point, or between two 5G access points, can be referred to as Xn. Other communication methods between access nodes are also possible. Access nodes 110 and 112 can also connect to the core network 116 of the cellular communication system via another interface. The LTE specification designates the core network as an Evolved Packet Core (EPC), and the core network can include a Mobility Management Entity (MME) and gateway nodes. The MME can handle the mobility of terminal devices in a tracking area comprising multiple cells and handle signaling connections between terminal devices and the core network. Gateway nodes can handle data routing within the core network and data routing to / from terminal devices. The 5G specification designates the core network as the 5G Core (5GC), which can include, for example, Access and Mobility Management Functions (AMF) and User Plane Functions / Gateways (UPF), to name a few. AMF can handle non-access stratum (NAS) signaling termination, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. For example, UPF nodes can support packet routing and forwarding, packet inspection, and QoS processing.

[0030] Network slicing in 5G aims to address services with varying requirements while improving network efficiency. Some services demand low latency and need to process local service content, some require high mobility, while others are closer to the characteristics of current mobile broadband types and have no specific requirements for reliability or latency. The slicing principle in 5G allows a UE to be associated with multiple slices while still maintaining only a single signaling connection with the network.

[0031] When a UE registers with the network (via NAS signaling), it is provided with information about available slices, and a single UE can access up to eight different slices simultaneously. Once a PDU session is established, the UE is signaled with Network Slice Selection Assistance Information (NSSAI). Based on this information, the network selects an appropriate slice instance (and associated resources), where the AMF coordinates the actions on the 5G core side. There exists an AMF that is common to all slices owned by a single UE. This AMF obtains information about which slices are allowed for a given subscription by interfacing with the Network Slice Selection Function (NSSF).

[0032] Network slicing allows for consideration of customers requiring different service levels. Network slices are uniquely identified by a slice ID called S-NSSAI (Single Network Slice Selection Auxiliary Information). Current 3GPP specifications allow UEs to connect and be served simultaneously by up to eight S-NSSAIs. On the other hand, each cell can support dozens or even hundreds of S-NSSAIs; for example, in the current specification, a tracking area can support up to 1024 network slices.

[0033] S-NSSAI can include both a 32-bit fragmentation service type (SST) field and a fragmentation differential (SD) field, such as... Figure 2A As shown, it may include only the SST field portion, in which case the S-NSSAI length is only 8 bits. The S-NSSAI identifies each slice configured for the UE. The S-NSSAI's SD portion can only be defined by the operator. The SST field can have normalized and non-normalized values. Values ​​from 0 to 127 belong to the normalized SST range. For example, an SST value "1" can indicate that the slice is suitable for handling 5G eMBB, an SST value "2" can indicate that the slice is used for handling URLLC, and so on.

[0034] One type of channel in a communication network is the so-called Physical Random Access Channel (PRACH is referred to as the Physical Channel and / or RACH as the Transport Channel). The PRACH process, or more generally the RA process, is a process called Contention-Based Random Access (CBRA). This process can consist of two or four steps, depending on the higher-layer configuration. In this application, although the proposed solution is also applicable to two-step variants including MsgA and MsgB, the focus is on the four-step variant used for illustration. Hereinafter, random access is abbreviated as RA.

[0035] During initial access, the RA procedure occurs after the gNB and UE (such as gNB 110 and UE 120) perform a preliminary set of operations. The preliminary set of operations includes, for example, a DL synchronization signal block (SSB) beam scan. In this step, gNB 110 transmits a sequence of beamformed SSBs. UE 120 then uses a specific receive (RX) beam to measure the reference signal received power (RSRP) of all received SSB beams. Finally, UE 120 selects the index of the preferred SSB and decodes its contents, such as the Master Information Block (MIB) and / or System Information Block 1 (SIB1).

[0036] Let's take a brief look. Figure 2B The common RA procedure between UE 120 and gNB 110 is shown. Although applicable to many networks, for simplicity, we will focus primarily on 5G (NR) in the following examples.

[0037] During the CBRA process, such as Figure 2B As shown, during beam scanning, UE 120 selects an available PRACH preamble from a maximum of 64 available preambles based on the selected SSB beam index, and sends it to gNB 110 in message (Msg) 1 using a specific time and frequency resource called Random Access Opportunity (RO). UE 120 also needs to provide an identifier to the network so that the network can address it in the next step. The identifier used by the UE is called RA-RNTI (Random Access Radio Network Temporary Identifier).

[0038] In the next step, gNB 110 detects the preamble, calculates the provisional C-RNTI associated with the RO and the timing advance (TA), and issues a PUSCH uplink grant to the UE, the preamble having already been received via the RO. This is called a Random Access Response (RAR), which is issued as Msg2 to the UE 120 addressed to the associated RA-RNTI. Msg2 can carry the following information by default: the provisional C-RNTI, which is another identifier given to the UE 120; the TA value, which provides the UE with a means to compensate for round-trip delay caused by the distance between the UE and gNB 110; and the UL granted resources, which are allocated as the initial resources for the UE to use the Physical Uplink Shared Channel (PUSCH).

[0039] Then, by using the uplink shared channel, UE 120 sends Msg3 to the network on the PUSCH using the scheduled uplink resources. This Msg3 can be referred to as an "RRC Connection Request Message". At this point, UE 110 is identified by a temporary C-RNTI.

[0040] Subsequently, the gNB can send Msg4 to the UE for contention resolution. After the RRC connection request of Msg3 is processed, the gNB 110 will send an RRC response to the UE 120. In one embodiment, although not shown, the RRC message (e.g., RRC connection establishment message) can be multiplexed with Msg4 (i.e., sent with MAC contention resolution CE).

[0041] In a contention-based RA procedure, there is a possibility that multiple UEs may send PRACHs with the same signature. This could mean that the same PRACH preamble from multiple UEs arrives at the network (e.g., gNB) simultaneously. Due to such overlap / collision, the RACH procedure of one or more UEs simultaneously attempting a RACH procedure with the same preamble may fail. Therefore, the network may need to rely on contention resolution for Msg4. UEs that fail due to contention (i.e., collision) caused by simultaneously selecting the same preamble from different UEs can repeat the RA procedure.

[0042] Another possibility for avoiding conflicts is the existence of a dedicated preamble for the UE. The network may have already informed the UE which preambles it should use for signing. This RACH procedure is called a contention-free random access (CFRA) procedure. In this case, the UE issues a dedicated preamble (after selecting one from a pool of dedicated preambles), and the network responds with a random access response (RAR, see Msg2 above). The contention-free RA procedure ensures that no two UEs use the same preamble simultaneously, thus avoiding conflicts and contention resolution. Although the description is written from the perspective of CFRA, CFRA is within the scope of this application.

[0043] The aforementioned ROs are resources specified in the time and frequency domains that can be used for RACH preamble transmission. For example, in 3GPP New Radio (NR / 5G), SSB indexes are associated with ROs via higher-layer signaling. The mapping is quite flexible to accommodate different network deployments and loads.

[0044] One of the issues identified in the 3GPP RAN Slicing Study Project in Release 17 is that some enterprise / industrial scenarios have access resource isolation requirements to provide guaranteed resources for pre-defined sensitive slices, for example, in the case of Random Access (RA) resources or generally RO. Another issue is that UEs may not differ from the network side, for example, in the case of initial access, while some slices may need to be prioritized during initial access, for example, in the case of RA procedures.

[0045] Therefore, initial access resources (e.g., RA resources in 5G slicing scenarios or in general RA configurations) are proposed to be categorized for different slices. However, currently, UEs supporting and requesting a particular slice cannot distinguish between different RACH configurations of different slices because the RA procedure and its gNB configuration are currently slice information unknown.

[0046] If the same RA resource pool is used for all UEs, threat sources cannot be differentiated between users, cannot be identified / tracked based on initial access resource usage, or can target specific slices. In this scenario, a threat source could potentially attack the entire cell, which OAM should detect quickly because the entire access to the cell would be compromised. Furthermore, the threat source's objective might not be to attack, but rather to identify, locate, and track certain slice UEs. If the resource pool is identical, it becomes impossible to easily identify and track slice-specific UEs.

[0047] At least in the case of Mobile Origin (MO) access, the only way to know the initial access resources (e.g., RACH resources) specific to a slice will be through system information. This is transparent (e.g., plaintext) information and may not be suitable for all purposes. Dedicated signaling may be infeasible because resource allocation can change across different cells, for example, taking into account geographical UE distribution and UE mobility. For example, system information indicating that slice “X” can / should be accessed by random access with RO “Y” may not work because such information fully reveals what resources are used for which slice, and an observer can easily identify and track UEs in that slice by observing random access usage. This poses a risk to devices in mission-critical / sensitive slices because the slice and / or the devices associated with it can be easily identified, tracked, and blocked. Furthermore, slice-specific traffic and mobility can be monitored and analyzed by unauthorized parties (e.g., threat actors).

[0048] Introducing resource isolation for mission-critical slices (e.g., vertical UEs) is beneficial, as latency and initial access requirements are typically more stringent for these slices. While, for example, MBB slices may be network-wide available, mission-critical slices may not be. Therefore, if a cell cannot provide such a mission-critical service, it may not be possible to substitute it with another cell, as in the case of an MBB slice. However, for the purpose of resource isolation, if slice-specific RACH resources are transparent to all UEs, the system may become more vulnerable to service-specific and / or slice-specific threats.

[0049] To address this issue at least partially, a solution for slice-specific random access resource isolation is proposed. While applicable to many networks, for simplicity, we will focus on 5G and eLTE in the following examples.

[0050] Figure 3 An example method is shown. This method can be executed by the UE, such as... Figure 1 UE 120. Therefore, as Figure 3As shown, UE 120 may receive a first message in step 300. The first message indicates information for at least one network slice identifier in one or more radio network areas (also referred to in this specification as slice mapping information or mapping information). For example, the first message may also be referred to as a first input or a first indicator. The first message may be pre-configured in the UE. The first message can be received via a radio interface. The first message can be received from a base station such as the currently serving gNB 110 (assuming the UE is connected to gNB 110). The first message may be received as a dedicated encrypted message that is only receivable by the UE. Alternatively, the first message may be a multicast message receivable by any UE in a multicast group. For example, the multicast group may share similar parameters regarding network slice requirements.

[0051] In step 302, UE 120 receives a second message indicating configuration information for one or more network slices. The second message can be received via a radio interface. The second message / input / indicator can be received when the UE is in RRC idle mode or RRC inactive mode. The second message can be received from a base station (e.g., gNB 112) providing the cell in which the UE currently camps (e.g., cell 102). The second message can be received as a broadcast message receivable by any UE in cell 102.

[0052] In step 304, UE 120 determines the configuration to be used for a given network slice based on the first and second messages. That is, by combining the information provided in the messages, UE 120 can determine the configuration that the UE should use when accessing network slice X in, for example, cell 102 (assuming cell 102 supports network slice X). Thereafter, for example, UE 120 can apply the determined configuration in operations with gNB 112 (such as PRACH).

[0053] Let's take a closer look at step 300 and the first message.

[0054] In one embodiment, the radio network area is a tracking area (TA) or includes a tracking area (TA). In other words, the granularity or validity area of ​​the first message is the TA. Therefore, the first message is given for the TA. A TA may include multiple cells / gNBs.

[0055] In another embodiment, the radio network area is at least one cell or includes at least one cell. In other words, the granularity or validity area of ​​the first message is at least one cell. Therefore, the first message is given for at least one cell.

[0056] In another embodiment, the radio network region is at least one beam or includes at least one beam. In other words, the granularity or validity region of the first message is at least one beam. Therefore, the first message is given for at least one beam.

[0057] In another embodiment, the first message may indicate a mapping of more than one TA, such as the current TA of the serving cell and one or more neighboring TAs. If the first message is invalid for a particular TA, for example, if UE 120 roams to another TA, UE 120 may fall back to default / normal behavior, where receiving the first message is not a prerequisite for UE operation.

[0058] In another embodiment, the radio network region is a notification region (RNA) or registration region based on the RAN, or includes a notification region (RNA) or registration region based on the RAN. For example, the first message includes mapping information for all TAs in the RNA or registration region. On the other hand, it should be noted that a TA-specific first input can provide more consistent granularity because the RNA and registration region can differ for different UEs and may require their coordination.

[0059] In one embodiment, the validity region of the first message is explicitly indicated by associating the first message with (multiple) TAIs or (multiple) TACs. In other embodiments, it is assumed that the first message is valid for TAs, RNAs, or registration regions in which the first message is received without any explicit indication. In yet another embodiment, the validity region of the first message is explicitly indicated by associating the first message with (multiple) cell IDs and / or (multiple) beam IDs.

[0060] In one embodiment, UE 120 receives the first input via an encrypted unicast / dedicated message. In one embodiment, the first message is an RRC message. In one embodiment, the RRC message may be an RRC release message or a paging message during a state transition to an inactive or idle state, to name just a few non-limiting examples. In another embodiment, the first message is a NAS message. For example, NAS signaling may be used when the first message is provided by the core network (CN), while RRC signaling may be used when the first message is provided by the radio access network (RAN).

[0061] In one embodiment, when CN signaling is used to provide, for example, first input for a registration area, the CN may notify or update the index used to the RAN (e.g., gNB 110). In another embodiment, RAN signaling is used to provide, for example, first input for a TA or RNA. When the RAN (e.g., gNB 110) provides first input for a registration area, the CN may need to explicitly notify the RAN of the UE 120's registration area. This may be done, for example, via core network assistance information. In one embodiment, where only one TA is indicated in the first message, the message may be provided by the RAN node (e.g., gNB 110) without information from the CN, although some coordination regarding the index used in the first input may be required at the RAN level. In one embodiment, the RAN may need to receive from the CN what indexes can be used or how index mapping is performed within the TA.

[0062] In one embodiment, the first message has a predetermined validity period. That is, the indicated first input is only valid for a specific time period (e.g., during an existing T320 timer or another timer). In one embodiment, a new timer may be defined for storing the first input. In another embodiment, it may be an additional or alternative event-triggered storage device, such that the UE 120 stores the contents of the first message in memory until it receives the next configuration, or until the UE 120 is disconnected from the network, or until the subscription data changes.

[0063] When using a timer, if the timer expires before receiving a new first input, UE 120 can also fall back to default / normal behavior unrelated to the use of the first message. In one embodiment, if the first input needs to be updated, UE 120 is notified / paged by the network because UE 120 may need to return to connected mode in order to receive the first input.

[0064] Now, let's compare Figures 5A to 5C Let's take a closer look at the example content of the first message. For example... Figure 5A and Figure 5B As shown, for each of one or more radio network areas, the mapping information indicates how a given network slice is indexed in a second message within that given radio network area. For example, this mapping can be pre-configured in each radio network area (e.g., TA), or the CN can define the mapping.

[0065] In some embodiments, the first input indicates how the SST (Slice / Service Type) and SD (Slice Differentiator) values ​​are indexed by system information within the TA, RNA, or registration region. Indexing can be performed such that the (S-NSSAI) SST / SD values ​​are scrambled and anonymized in each region. In one embodiment, different network slices are identified in the system information by slice identifiers. A slice identifier (ID) includes at least one of the slice / service type (SST) and slice differentiator (SD).

[0066] Figure 5A Two columns are shown. The left column represents the slice ID, which in Figure 5 includes the SST of S-NSSAI. It is assumed that a slice can be identified individually by its SST. The right column shows how each slice ID maps to a specific slice index in one or more TAs. For example, from Figure 5A Read from the table, slice ID 2 corresponds to / maps to slice index 1 in TA 0, slice index 3 in TA 1, and slice index 2 in TA 2.

[0067] Figure 5B and Figure 5A The difference is that the slice ID is identified by both SST and SD. For example, the slice ID of SST=1 and SD 0 (= the third row of Table 5B) is mapped to slice index 2 in TA 0, slice index 1 in TA 1 and slice index 0 in TA 2.

[0068] Figure 5C An embodiment is shown in which, for each of one or more radio network areas, mapping information indicates how a given network slice is indexed in a second message within a given radio network area, and which configuration is associated with which network slice. The table includes a third column indicating the configuration index in the corresponding TA for a given slice ID. For example, looking at the second row of the table, slice ID 0 corresponds to / maps to slice index 0 and configuration index 1 in TA 0, slice index 2 and configuration index 0 in TA 1, and slice index 3 and configuration index 4 in TA 2.

[0069] In addition to the slice identifier (ID), an identifier can also be assigned to the slice group, and a mapping can indicate how the slice group is mapped to the slice index, and possibly to the configuration index in each radio network area (TA in Tables 5A-5C for simplicity). Slice groups can be identified simply by SST, such as... Figure 5A and Figure 5C As shown, a single slice can be identified using SST+SD, such as... Figure 5B As shown.

[0070] In one embodiment, a list / table of all slices available in the relevant TA, and their mapping to indexes, are notified to the UE 120 in a first message. A disadvantage of this embodiment is that the amount of information can be substantial. However, this can be tolerable because it is provided in a dedicated message.

[0071] In another embodiment, the mapping information given to UE 120 is limited to a subset of all network slices available in (multiple) TAs. For example, this subset may only include the slices required by the UE 120. From an operator's perspective, this may be desirable, as some operators may not want to disclose a complete list of slices.

[0072] In one embodiment, the network only provides an index for the allowed NSSAIs of a specific UE 120. If a UE has a subscription to a slice that is not currently in an allowed NSSAI, and therefore the UE is not provided with an index mapped to that slice in the first message, the UE can fall back to default / traditional behavior. This may happen, for example, when the UE does not include a slice ID during registration, or when the network rejects it during registration. Default / traditional operation does not include slice-specific configurations using the first and second messages. Instead, traditional operation includes using the common resource pool for all other traditional UEs.

[0073] Let's now look at step 302. In one embodiment, in step 302, UE 120 receives the second input via an unencrypted broadcast message. Here, the broadcast message may be a System Information Block (SIB) message, such as in SIB1.

[0074] In one embodiment, the second message is slice-specific, while in another embodiment, the second message can be used for more than one slice. In the latter case, the same second message can be broadcast for slices with similar slice characteristics (such as slice priority).

[0075] In one embodiment, the second input is valid for the cell or gNB. This can be advantageous because each cell can support a different set of slices. In one embodiment, it is simply assumed that the second input is valid for the cell or gNB in ​​which it is received. In other embodiments, the second input can be valid for more than one cell or more than one gNB, and this can be explicitly indicated along with the second input by including, for example, Physical Cell ID (PCI) or similar ID information. When the content of the second message is valid for multiple cells / nodes, inter-gNB coordination (between cells / nodes) regarding the broadcast second message may be required between the relevant gNBs.

[0076] In one embodiment, similar to the content of the first message, the content of the second message may have an expiration period; that is, the content may be considered valid only for a specific time period (e.g., while a timer is running). In one embodiment, a new timer may be defined for storing the second input. In another embodiment, it may be an additional or alternative event-triggered storage, such as the first message. In one embodiment, the expiration period may have a certain periodicity. For example, the configuration may be valid within a certain time interval. In one embodiment, the second input is valid, and the first input is valid. When using a timer, if the timer expires before a new second input is received, the UE 120 may fall back to default / legacy behavior.

[0077] Let's talk about Figures 6A to 6C Let's take a closer look at the example content of the second message. For example... Figure 6A and Figure 6B As shown, the configuration information in the second message indicates the mapping between different configurations and different network slices, where each network slice is identified in the second message by an index specific to the radio network area where the second message is received. The index and its mapping to the slice ID are obtained from the first message, for example, as referenced above. Figures 5A-5C As stated above.

[0078] exist Figures 6A-6C In the connection, it is assumed that the configuration index refers to the PRACH configuration. In other words, the second message may indicate, for example, a PRACH resource configuration (e.g., resource allocation and format) mapped to an index value (or more than one index value) representing at least one of SST and SD, i.e., a given network slice. In one embodiment, the random access configuration includes dedicated random access resources for a given network slice. This ensures that a UE attempting to access a cell on a particular slice is more likely to access that cell compared to when the UE is forced to use public resources or contention-based resources.

[0079] However, it should be noted that, in addition to PRACH configuration, the embodiments are also applicable to indicating other configurations. For example, the second input may be slice-specific radio resource configurations other than PRACH resources, such as Media Access Control (MAC) configurations (e.g., configuration parameters regarding power control) and / or Physical Layer (PHY) configurations (e.g., configuration parameters regarding the Physical Layer Digital Basic configuration) and / or generally radio resource management (RRM) related configurations (e.g., configuration parameters regarding radio resource allocation for data transmission). In cases where multiple configurations are indicated for a slice, Figure 5C First message or Figures 6A-6BThe second message can be enhanced by mapping slice indexes to additional columns of the additional configuration. Alternatively, a configuration index can correspond to a combination of configurations, in which case additional columns are not needed in the table.

[0080] In one embodiment, the configuration (e.g., PRACH configuration) is identified by an index. The UE can know what the configuration index in the cell refers to. For example, a configuration index could refer to a configuration available for certain time / frequency resources. As a non-limiting example, a specific PRACH configuration index indicated in a second message could define that the UE will transmit a PRACH preamble in a specific time and / or frequency resource, or that it needs to use a specific preamble signature for the preamble. Such mapping information between configuration indices and radio resources can be predefined in the UE, or signaled to the UE in advance, or received, for example, in system information. Alternatively, although... Figures 6A-6C Not shown, but the configuration mapping information in the second message may include, for example, system frame, subframe, and preamble format configuration information for each PRACH configuration index. Each cell may have its own configuration available for certain slices, and these configurations may be determined by the cell's control node (e.g., gNB 112).

[0081] Figure 6A This illustrates an example of how to map a PRACH resource index to a slice index received in the first message as a second input. This configuration mapping information, based on the second message, is located in TA 1, and we want to access, for example, slice ID 0 (which is based on the content of the first message, see...). Figure 5A For UE 120 corresponding to slice index 2 in TA 1, the row corresponding to slice index 2 determines whether UE 120 can use configuration indices 0, 1, 2, or 3. That is, in this cell, there are four different configurations available for slice ID 0. For example, each configuration index can be mapped to a specific time / frequency resource used for PRACH preamble transmission. The number of configurations available for each slice index / slice ID is configurable by the network, and... Figures 6A-6B The configuration shown is a non-restrictive example.

[0082] Figure 6A The row representation of the slice index [0,2] is available for both slice indices 0 and 2 in PRACH configuration 3. Based on the information from the first message, these two slice indices 0 and 2 correspond to slice IDs 2 and 3 in TA 1.

[0083] Figure 6B It shows the relationship with Figure 6A The table contains the same content, but in a compressed format. For example, Figure 6BThe third line containing slice index "1" indicates that slice index "1" is associated with, or mapped to, at least PRACH configuration 4 and possible other configurations ([...]), such as... Figure 6A As shown in line 6 (and line 7 [...]).

[0084] Figure 6C Another embodiment is shown, which can be used with Figure 5C The combination of embodiments. In this Figure 6C In this embodiment, the second input may include one or more index values ​​(corresponding to one or more specific slice IDs, as given in the first message). The broadcast indexes in the second message may only include those slice indexes supported in the cell where the UE is currently located. Figure 6C In this example, the gNB that sends the second message (e.g., gNB 112) only supports slice indices 0 and 3. Assuming cell 102 is in TA 2, these slice indices correspond to slice IDs 1 and 0, respectively.

[0085] Such as combination Figure 5C As shown, the slice index (in the first message) is also linked to the configuration index. Therefore, a given slice index in the second message also corresponds to one or more configurations.

[0086] It should be noted that within a TA, each cell can support a different set of slices. For example, in TA 0, cell 1 can support slice 2 with PRACH resources from 0 to 5; and in the same TA 0, cell 2 can support slice 2 with PRACH resources from 3 to 8. This means that cell 1 and cell 2 will need to broadcast different index values, even though both support slice 2. This is because random access resource allocation can be different in each cell. In another embodiment, within a TA, each cell can support different combinations of resources.

[0087] In one embodiment, the first message can be modified so that the validity area is the cell, rather than the TA. This allows the UE to determine which configuration to use when it knows in which cell the second message is received. However, in one embodiment, each cell in the TA (or the validity area used) has the same PRACH configuration for a given slice. In this case, Figure 5C and Figure 6C The input is sufficient for UE 120.

[0088] As described above, in step 304, the first and second inputs are then used by the UE 120 as the basis for the UE 120 to obtain the appropriate configuration for the required slice, such as the basis for determining the correct PRACH resource allocation dedicated to the required network slice.

[0089] In one embodiment, UE 120 determines the radio network area where it is currently located within one or more radio network areas of the first message. The configuration determination in step 304 may be further based on the determined radio network area where UE 120 is currently located.

[0090] Figure 7 A signaling flowchart according to one embodiment is shown. Assume that in step 700, UE 120 connects to gNB 110 providing cell 100. In step 704, gNB 110 may send a first message to UE 120 in an RRC release message. In this example embodiment, the first message at least indicates that slice ID X corresponds to slice index Y in TA Z.

[0091] In step 706, the UE moves to RRC idle or RRC inactive mode. It is also assumed that in step 706, the UE moves to the coverage area of ​​cell 102 provided by gNB 112, such as... Figure 1 As shown. Assume cell 102 belongs to TA Z.

[0092] In step 708, gNB 112 broadcasts a second message. This second message is detectable and receivable by UE 120. The second message indicates at least that slice index Y corresponds to PRACH configuration A in cell 102. Although this message is also receivable by other UEs in the cell, UEs that have not yet received the first message cannot understand the mapping from slice index to slice ID.

[0093] In step 710, the UE decides to move to an RRC connected state on slice ID X (= slice index Y). Therefore, as indicated in the second message, UE 120 determines in step 712 to use PRACH configuration A. In step 714, the UE sends a PRACH preamble on the resources based on the determined PRACH configuration A. The receiving gNB 112 can detect that the UE wants to connect on slice ID X. However, other UEs or tracking entities do not know which slice ID UE 120 is currently using because these UEs or tracking entities have not yet received the first message. In step 716, UE 120 is in connected mode with gNB 112 on slice ID X.

[0094] Figure 4AThe proposal is shown from the perspective of a network node (such as gNB 110). In step 400, gNB 110 provides a first message to a user equipment (e.g., UE 120) indicating information for at least one network slice in one or more radio network areas. As mentioned above, the first message may be an encrypted private message. More specifically, for each of the one or more radio network areas (also referred to as validity areas), the first message may at least indicate how a given network slice is indexed in a second message within that given radio network area. Figure 4B The proposal is shown from the perspective of a network node (such as gNB 112). In step 402, gNB 112 provides a second message to the user equipment (e.g., UE 120) indicating configuration mapping information for one or more network slices. As mentioned above, the second message can be an unencrypted broadcast message. The second message can indicate, for example, a mapping between different configurations and different network slices, where each network slice is identified in the second message by an index specific to the radio network area where the second message is received. In step 404, gNB 112 detects a random access preamble from the user equipment regarding a random access configuration, where the configuration is at least partially determined by the UE based on the second message. The UE 120's determination of the configuration can be further based on a first message, which can be received from this gNB or from another gNB. In step 406, gNB 112 determines the network slices required by the user equipment based on the random access configuration.

[0095] In one embodiment, in Figure 4A and Figure 4B The actions performed are executed by the same network node. This can be the case when UE 120 stays or returns to the same cell.

[0096] Although described in conjunction with network slicing, these embodiments are applicable, from a broader perspective, to use in UE-specific resource allocation. For example, embodiments applicable to resource allocation based on Access Class (AC). In this case, an Access Class ID or a set of Class IDs replaces the Slice ID, and a first message maps the AC ID to an AC index, while a second message maps the AC index to a configuration index in a different validity region (= radio network region / geographic region). When using Access Classes, operator-defined Access Classes can also be used. In this case, the Access Class can be mapped to a Slice; for example, the Access Class Number can be mapped to a Slice ID, and such mapping can be used by the various embodiments presented herein.

[0097] For example, some advantages of the embodiments may include the ability to allocate initial access resources, such as those for random access, in a manner that is not easily used by third parties to track, identify, and attack mission-critical UEs. Therefore, the embodiments can improve the resilience of (mission-critical) networks deploying (multiple) mission-critical slices.

[0098] Traditionally, a cell can broadcast the slice IDs it supports (e.g., SST, SD), but these are not linked to any slice-specific configurations provided in the first and second messages. Due to this solution, slice-specific configurations are associated with slice indices regardless of how supported slices are broadcast. However, in order to understand which slice indices correspond to SST and SD, the UE will benefit from receiving a first message where each slice ID (SST, SD) is mapped to a slice index, followed by a second message. In other words, without the first message, the second message is useless because the slice index itself does not indicate which slice ID it is mapped to.

[0099] like Figure 8 As shown, one embodiment provides an apparatus 10 including a control circuitry system (CTRL) 12 (such as at least one processor) and at least one memory 14 including computer program code (software), wherein the at least one memory and the computer program code (software) are configured together with the at least one processor to cause the apparatus to perform any of the processes described above. The memory can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The memory may include a database for storing data. The database of the memory can be used to store information carried, for example, in a first message and a second message.

[0100] In one embodiment, device 10 may include a terminal device of a communication system, such as a user terminal (UT), computer (PC), laptop, tablet, cellular phone, mobile phone, communicator, smartphone, handheld computer, mobile transportation equipment (such as a car), home appliance, or any other communication device, generally referred to as UE in the specification. Alternatively, the device is included within such a terminal device. Furthermore, the device may be or include a module providing connectivity (to be attached to the UE), such as a plug-in unit, a "USB dongle," or any other type of unit. This unit may be installed inside the UE or attached to the UE via a connector or even wirelessly.

[0101] In one embodiment, device 10 is UE 120 or is included in UE 120. This device can be configured to perform some of the functions described above, such as... Figure 3 The steps.

[0102] The device may also include a radio interface (TRX) 16, which includes hardware and / or software for implementing a communication connection according to one or more communication protocols. The TRX can be used, for example, for receiving first and second messages. For instance, the TRX can provide the device with the communication capability to access a radio access network.

[0103] The device may also include a user interface 18, including, for example, at least one keypad, microphone, touch display, display, speaker, etc. The user interface can be used by a user to control the device.

[0104] According to any embodiment, the control circuitry system 12 may include a slice determination circuitry system 20 for determining which slices the device supports or requires. Each slice ID may be defined by SST or SST+SD. According to any embodiment, the control circuitry system 12 may also include a configuration determination circuitry system 22 for determining a configuration for a given index based on a first message and a second message. According to any embodiment, the control circuitry system 12 may also include a random access circuitry system 24 for performing random access on a particular slice on the determined configuration.

[0105] like Figure 9 As shown, one embodiment provides an apparatus 50 including a control circuitry system (CTRL) 52 (such as at least one processor) and at least one memory 54 including computer program code (software), wherein the at least one memory and the computer program code (software) are configured together with the at least one processor to cause the apparatus to perform any of the processes described above. The memory can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The memory may include a database for storing data. The stored data may include, for example, slice mapping information and / or configuration mapping information.

[0106] In one embodiment, device 50 may be a network node or be included in a network node, such as in a 5G gNB / gNB-CU / gNB-DU. In one embodiment, the device is network node 110 or network node 112, or is included in network node 110 or network node 112. The device may be configured to perform some of the functions described above, such as Figure 4A and / or Figure 4B The steps.

[0107] In one embodiment, a CU-DU (Central Unit-Distributed Unit) architecture is implemented. In this case, device 50 may be included in a central unit (e.g., a control unit, an edge cloud server, a server) operatively coupled (e.g., via a wireless or wired network) to a distributed unit (e.g., a remote radio head / node). That is, the central unit (e.g., the edge cloud server) and the radio nodes may be separate devices communicating with each other via a radio path or via a wired connection. Alternatively, they may be in the same entity communicating via a wired connection, etc. The edge cloud or edge cloud server may serve multiple radio nodes or a radio access network. In one embodiment, at least some of the described processes may be performed by the central unit. In another embodiment, the device may instead be included in a distributed unit, and at least some of the described processes may be performed by the distributed unit. In one embodiment, the execution of at least some functions of device 50 may be shared between two physically separate devices (DU and CU) forming an operating entity. Thus, the device can be considered as depicting an operating entity comprising one or more physically separate devices for performing at least some of the described processes. In one embodiment, the device controls the execution of these processes regardless of the location of the device or where the process / function is performed.

[0108] The device may also include a communication interface (TRX) 56, which includes hardware and / or software for implementing a communication connection according to one or more communication protocols. For example, the TRX can provide the device with the communication capability to access a radio access network. The TRX can be used, for example, to send a first message and / or a second message.

[0109] The device may also include a user interface 58, including, for example, at least one keypad, microphone, touch display, monitor, speaker, etc. The user interface can be used to control the device by a user.

[0110] According to any embodiment, control circuitry 52 may include a slice mapping circuitry 60 for determining / acquiring a mapping between slice IDs and slice indices that may exist in different TAs. Control circuitry 52 may include, for example, a configuration determination circuitry 62 for determining a cell-specific configuration provided by the device. For example, gNB 112 (as device 50) may define that slice ID X in cell 102 can use configurations A and B. Control circuitry 52 may include, for example, an access control circuitry 64 for controlling UE access to the cell. According to any embodiment, circuitry 64 may be configured to determine the slice ID that the UE is requesting based on the RACH configuration used by the UE.

[0111] In one embodiment, an apparatus for performing at least some of the described embodiments includes at least one processor and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to perform the functions according to any of the described embodiments. According to one aspect, when the at least one processor executes the computer program code, the computer program code causes the apparatus to perform the functions according to any of the described embodiments. According to another embodiment, an apparatus for performing at least some embodiments includes at least one processor and at least one memory including computer program code, wherein the at least one processor and the computer program code perform at least some of the functions according to any of the described embodiments. Thus, at least one processor, memory, and computer program code form a processing component for performing at least some of the described embodiments. According to yet another embodiment, an apparatus for performing at least some of the embodiments includes a circuit system including at least one processor and at least one memory including computer program code. When activated, the circuit system causes the apparatus to perform at least some of the functions according to any of the described embodiments.

[0112] As used in this application, the term "circuit system" refers to all of the following: (a) hardware circuit implementations only, such as implementations only in analog and / or digital circuit systems; and (b) combinations of circuits and software (and / or firmware), such as (if applicable): (i) combinations of (multiple) processors, or (ii) portions of (multiple) processors / software, including (multiple) digital signal processors, software, and (multiple) memories, which work together to cause a device to perform various functions; and (c) circuits, such as (multiple) microprocessors or portions of (multiple) microprocessors, which require software or firmware to operate, even if the software or firmware is not physically present. This definition of "circuit system" applies to all uses of the term in this application. As another example, as used in this application, the term "circuit system" will also cover only an implementation of a processor (or multiple processors) or a portion of a processor and its accompanying software and / or firmware. For example, if applicable to a particular element, the term "circuit system" will also cover a baseband integrated circuit or application processor integrated circuit of a mobile phone, or a similar integrated circuit in a server, cellular network device, or another network device.

[0113] In one embodiment, at least some of the described processes can be performed by an apparatus comprising corresponding components for performing at least some of the described processes. Some example components for performing the processes may include at least one of the following: a detector, a processor (including dual-core and multi-core processors), a digital signal processor, a controller, a receiver, a transmitter, an encoder, a decoder, a memory, RAM, ROM, software, firmware, a display, a user interface, a display circuit system, a user interface circuit system, user interface software, display software, circuitry, an antenna, an antenna circuit system, and a circuit system.

[0114] The techniques and methods described herein can be implemented in various ways. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (more than one module), or a combination thereof. For hardware implementation, the embodiments may be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or combinations thereof. For firmware or software, implementation may be implemented by a module (e.g., process, function, etc.) of at least one chipset that performs the functions described herein. Software code may be stored in memory cells and executed by a processor. Memory cells may be implemented within the processor or external to the processor. In the latter case, as is known in the art, it may be communicatively coupled to the processor in various ways. Furthermore, the components of the systems described herein may be rearranged and / or supplemented by additional components to facilitate the illustration of achievements of the various aspects described with respect to it, and they are not limited to the precise configurations illustrated in the given figures.

[0115] The described embodiments can also be performed as a computer process defined by a computer program or parts thereof. Embodiments of the described methods can be implemented by executing at least a portion of a computer program including corresponding instructions. The computer program can be in source code form, object code form, or some intermediate form, and it can be stored on some kind of carrier, which can be any entity or device capable of carrying the program. For example, the computer program can be stored on a computer or processor-readable computer program distribution medium. The computer program medium can be, for example, but not limited to, recording media, computer memory, read-only memory, electrical carrier signals, telecommunication signals, and software distribution packages. The computer program medium can be a non-transitory medium. The coding of the software used to perform the embodiments shown and described is entirely within the scope of those skilled in the art.

[0116] Although the invention has been described above with reference to the accompanying drawings and examples, it is clear that the invention is not limited thereto, but can be modified in various ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly, and are intended to illustrate rather than limit the embodiments. It will be apparent to those skilled in the art that the inventive concept can be implemented in various ways as technology advances. Furthermore, it will be apparent to those skilled in the art that the described embodiments can, but are not required to, be combined with other embodiments in various ways.

Claims

1. A user equipment, comprising a component configured to: Receive (300) a first message from a first network node as an encrypted message dedicated to the user equipment, the first message indicating information for at least one network slice in one or more radio network areas, wherein for each of the one or more radio network areas, the information in the first message indicates how a given network slice is indexed in a second message in a given radio network area; (302) Receive a second message as a broadcast message from a second network node, the second message indicating configuration information for one or more network slices, wherein the configuration information in the second message indicates a mapping between different configurations and different network slices, wherein each network slice is identified in the second message by an index specific to the radio network area in which the second message is received, and the configuration information in the second message indicates a random access configuration for a given network slice in the radio network area in which the second message is received; Based on the first message and the second message, determine (304) the configuration to be used for a given network slice.

2. The user equipment of claim 1, wherein the component is further configured to perform: Among the one or more radio network areas, the radio network area where the user equipment is currently located is determined, wherein the determination of the configuration is further based on the determined radio network area.

3. The user equipment according to claim 1, wherein the radio network area is a tracking area.

4. The user equipment according to claim 1, wherein the radio network area is one of the following: a RAN-based notification area, a registration area, a cell, or a beam.

5. The user equipment of claim 1, wherein for each of the one or more radio network areas, the information in the first message indicates how a given network slice is indexed in the second message in the given radio network area, and which configuration is associated with which network slice.

6. The user equipment according to claim 1, wherein the information in the first message includes only: A subset of all network slices available in the one or more radio network areas.

7. The user equipment of claim 6, wherein the subset of network slices includes only those network slices that the user equipment is permitted to use.

8. The user equipment according to claim 1, wherein at least one of the first message or the second message has a predetermined validity period.

9. The user equipment according to any one of the preceding claims, wherein the first network node is a core network node, and the first message is received as a non-access stratum message, and the second network node is a radio access network node.

10. A method performed by a user equipment, comprising: Receive (300) a first message from a first network node as an encrypted message dedicated to the user equipment, the first message indicating information for at least one network slice in one or more radio network areas, wherein for each of the one or more radio network areas, the information in the first message indicates how a given network slice is indexed in a second message in a given radio network area; (302) Receive a second message as a broadcast message from a second network node, the second message indicating configuration information for one or more network slices, wherein the configuration information in the second message indicates a mapping between different configurations and different network slices, wherein each network slice is identified in the second message by an index specific to the radio network area in which the second message is received, and the configuration information in the second message indicates a random access configuration for a given network slice in the radio network area in which the second message is received; Based on the first message and the second message, determine (304) the configuration to be used for a given network slice.

Images