CN111108785A

CN111108785A - Network slice specific paging cycle for wireless networks

Info

Publication number: CN111108785A
Application number: CN201780095147.5A
Authority: CN
Inventors: 张延冀; 张元涛
Original assignee: Nokia Solutions and Networks Oy; Alcatel Lucent SAS
Current assignee: Nokia Solutions and Networks Oy; Alcatel Lucent SAS
Priority date: 2017-08-11
Filing date: 2017-08-11
Publication date: 2020-05-05
Anticipated expiration: 2037-08-11
Also published as: WO2019028838A1; CN111108785B

Abstract

One technique includes: receiving, by a user equipment within a wireless network, information identifying a slice-specific paging cycle for one or more network slices allowed for the user equipment; determining, by the user equipment, a minimum slice-specific paging cycle of the one or more slice-specific paging cycles; and receiving, by the user equipment, a paging message based on the minimum slice-specific paging cycle.

Description

Network slice specific paging cycle for wireless networks

Technical Field

This description relates to communications.

Background

A communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. The signals may be carried on wired or wireless carrier waves.

An example of a cellular communication system is an architecture that is being standardized by the third generation partnership project (3 GPP). The latest developments in this area are commonly referred to as the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology. E-UTRA (evolved UMTS terrestrial radio Access) is the air interface of 3GPP for LTE upgrade path of mobile networks. In LTE, a base station or Access Point (AP), called an enhanced node AP (enb), provides wireless access within a coverage area or cell. In LTE, a mobile device, or mobile station, is referred to as User Equipment (UE). LTE includes many improvements or developments.

The global bandwidth shortage faced by wireless operators has prompted consideration of the underutilized millimeter wave (mmWave) spectrum for future broadband cellular communication networks. For example, mmWave (or very high frequency) may include a frequency range between 30 and 300 gigahertz (GHz). For example, the wavelength of radio waves in this band may be 10 to 1 mm, and thus it is named as millimeter wave band or millimeter wave. In the next few years, the amount of wireless data may increase substantially. Various techniques have been used in an attempt to address this challenge, including obtaining more spectrum, having smaller cell sizes, and using improved techniques that achieve more bits/s/Hz. One element that can be used to obtain more frequency spectrum is to move to higher frequencies, for example above 6 GHz. For fifth generation wireless systems (5G), access architectures have been proposed for deploying cellular radios that employ cmWave radio spectrum. Other example frequency spectrums may also be used, such as the cmWave radio spectrum (e.g., 3-30 GHz).

Furthermore, 5G wireless networks may support network slicing, where a single physical network may be sliced into multiple virtual networks. Each network slice may include a set of logical network functions that may support the requirements of a particular use case.

Disclosure of Invention

According to an example implementation, a method, comprising: receiving, by a user equipment within a wireless network, information identifying a slice-specific paging cycle for each of one or more network slices allowed for the user equipment; determining, by the user equipment, a minimum slice-specific paging cycle of the one or more slice-specific paging cycles; and receiving, by the user equipment, a paging message based on the minimum slice-specific paging cycle.

According to an example implementation, an apparatus, comprising: at least one processor and at least one memory including computer instructions that, when executed by the at least one processor, cause the apparatus to: receiving, by a user equipment within a wireless network, information identifying a slice-specific paging cycle for each of one or more network slices allowed for the user equipment; determining, by the user equipment, a minimum slice-specific paging cycle of the one or more slice-specific paging cycles; and receiving, by the user equipment, a paging message based on the minimum slice-specific paging cycle.

According to an example implementation, a computer program product comprising a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method comprising: receiving, by a user equipment within a wireless network, information identifying a slice-specific paging cycle for each of one or more network slices allowed for the user equipment; determining, by the user equipment, a minimum slice-specific paging cycle of the one or more slice-specific paging cycles; and receiving, by the user equipment, a paging message based on the minimum slice-specific paging cycle.

According to an example implementation, a method, comprising: receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for one or more network slices allowed for the user equipment; selecting, by the base station, a paging cycle for the user equipment based on the received slice-specific paging cycle for the one or more network slices allowed for the user equipment; and transmitting, by the base station, a Radio Access Network (RAN) paging message to the user equipment based on the selected paging cycle for the user equipment.

According to an example implementation, an apparatus, comprising: at least one processor and at least one memory including computer instructions that, when executed by the at least one processor, cause the apparatus to: receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for one or more network slices allowed for the user equipment; selecting, by the base station, a paging cycle for the user equipment based on the received slice-specific paging cycle for the one or more network slices allowed for the user equipment; and transmitting, by the base station, a Radio Access Network (RAN) paging message to the user equipment based on the selected paging cycle for the user equipment.

According to an example implementation, a computer program product comprising a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method comprising: receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for one or more network slices allowed for the user equipment; selecting, by the base station, a paging cycle for the user equipment based on the received slice-specific paging cycle for the one or more network slices allowed for the user equipment; and transmitting, by the base station, a Radio Access Network (RAN) paging message to the user equipment based on the selected paging cycle for the user equipment.

According to an example implementation, a method, comprising: sending, by a core network entity, a core network paging message to a base station in a wireless network, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for one or more network slices allowed for the user equipment.

According to an example implementation, an apparatus, comprising: at least one processor and at least one memory including computer instructions that, when executed by the at least one processor, cause the apparatus to: sending, by a core network entity, a core network paging message to a base station in a wireless network, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for one or more network slices allowed for the user equipment.

According to an example implementation, a computer program product comprising a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method comprising: sending, by a core network entity, a core network paging message to a base station in a wireless network, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for one or more network slices allowed for the user equipment.

The details of one or more examples of an implementation are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.

Drawings

Fig. 1 is a block diagram of a wireless network according to an example implementation.

Fig. 2 is a diagram illustrating a registration procedure between a user equipment and a core network entity according to an example implementation.

Fig. 3 is a diagram illustrating a Protocol Data Unit (PDU) session establishment procedure between a user equipment and a core network entity according to an example implementation.

Fig. 4 is a diagram illustrating operation of a paging procedure based on slice-specific paging cycles according to an example implementation.

FIG. 5 is a flow diagram illustrating operation of a user device according to an example implementation.

Fig. 6 is a flow diagram illustrating operation of a base station according to an example implementation.

Fig. 7 is a flow diagram illustrating operation of a core network entity according to an example implementation.

Fig. 8 is a block diagram of a node or wireless station (e.g., base station/access point or mobile station/user equipment/UE) implemented according to an example.

Detailed Description

Fig. 1 is a block diagram of a wireless network 130 according to an example implementation. In the wireless network 130 of fig. 1, user equipment 131, 132, 133, and 135, which may also be referred to as Mobile Stations (MSs) or User Equipment (UEs), may connect with (and communicate with) a Base Station (BS)134, which may also be referred to as an Access Point (AP), an enhanced node b (enb), a gNB, which may be a 5G base station, or a network node. At least a portion of the functionality of an Access Point (AP), Base Station (BS), or (e) Node B (eNB) may also be performed by any Node, server, or host that may be operatively coupled to a transceiver, such as a remote radio head. BS (or AP)134 provides wireless coverage within cell 136, including to user devices 131, 132, 133, and 135. Although only four user devices are shown connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to core network 150 via interface 151. This is only a simple example of a wireless network and other examples may be used.

User equipment (user terminal, User Equipment (UE)) may refer to portable computing devices including wireless mobile communication devices operating with or without a Subscriber Identity Module (SIM), including, for example and without limitation, the following device types: mobile Station (MS), mobile phone, cellular phone, smart phone, Personal Digital Assistant (PDA), cell phone, device using wireless modem (alarm or measurement device, etc.), notebook and/or touch screen computer, tablet, game console, notebook, and multimedia device. It should be understood that the user equipment may also be an almost exclusive uplink-only device, an example of which is a camera or camcorder that loads images or video clips to the network.

In LTE (as an example), the core network 150 may be referred to as an Evolved Packet Core (EPC), which may include a Mobility Management Entity (MME) that may handle or assist mobility/handover of user equipment between: a BS, one or more gateways that can forward data and control signals between the BS and a packet data network or the internet, and other control functions or blocks.

Various example implementations may be applied to a wide variety of wireless technologies, wireless networks, such as LTE, LTE-a, 5G (new radio, or NR), cmWave, and/or mmWave band networks, or any other wireless network or use case. LTE, 5G, cmWave, and mmWave band networks are provided as illustrative examples only, and various example implementations may be applied to any wireless technology/wireless network. The various example implementations may also be applied to a variety of different applications, services, or use cases, such as, for example, ultra-reliability low latency communication (URLLC), internet of things (IoT), enhanced mobile broadband, large machine type communication (MMTC), vehicle-to-vehicle (V2V), vehicle-to-device, and so forth. Each of these use cases (or UE types) may have its own set of requirements.

The paging procedure may be used to notify a UE in idle mode of an incoming call or data to be provided or transmitted to the UE. For example, the core network may request the BS to page the UE. The BS may then page the UE by transmitting a Radio Access Network (RAN) paging message. The paging message may include an identifier of the UE (e.g., a Temporary Mobile Subscriber Identifier (TMSI)) within a paging record provided within the paging message. If the UE detects its identifier within the paging message, the UE may then initiate a service request procedure with the Network (NW) to obtain the data, which may include, for example, performing random access with the NW, establishing a connection with the NW, and then receiving the data from the NW. In one example implementation, the Network (NW) may include a core network (or one or more core network entities) and/or a BS (which is part of a radio access network or RAN).

In addition, battery conservation is an important issue in mobile communications. The UE may implement Discontinuous Reception (DRX), for example, where the UE may only monitor paging messages during paging frames every paging cycle (or every DRX cycle), rather than requiring the idle mode UE to monitor Radio Access Network (RAN) paging messages from the BS every radio frame. According to an illustrative example implementation, the paging cycle (or DRX cycle) may be, for example, a period of time or a number of Radio Frames (RFs) between paging frames. The paging frame for the UE may be a frame in which there may be a paging message transmitted to the UE. For example, a paging frame may include one or more paging occasions, which may include a paging message to a UE. For example, the paging cycle may be used for UEs such as 32RFs (radio frames), 64 RFs, 128 RFs, 256 RFs, etc., or other number of radio frames. A longer paging cycle may allow greater battery savings (e.g., allow the UE to remain in a low power state for a longer period of time before waking up to monitor or detect any paging messages), while a shorter paging cycle may allow faster data transfer (with shorter delay) to the UE at the expense of higher battery consumption (e.g., because the idle mode UE will remain in a low power state for a shorter period of time during a shorter paging cycle). Thus, to conserve battery power, the UE may only need to wake up from a sleep state or a low power state every paging cycle (e.g., every 64 RFs or every 32 RFs) to monitor for any paging messages in the downlink channel and then determine whether the received paging message includes a paging record with an identifier of the UE (e.g., a Temporary Mobile Subscriber Identifier (TMSI) of the UE). If the paging message includes an identifier of the UE (indicating that the network has data for the UE), the UE may then initiate a service request procedure with the network (e.g., a BS and/or core network) to obtain the data. For example, the service request procedure may include, for example, the UE performing random access with the base station, establishing a connection with the base station, and then receiving data.

Furthermore, 5G wireless networks may support network slicing, where a single physical network may be sliced into multiple virtual networks. Each network slice may include, for example, a set of logical network functions that may support the requirements of a particular use case. Network slices may allow differentiated processing according to the requirements of different UEs or a group of UEs. With slicing (network slicing), operators can create networks for optimized solutions based on different service requirements, QoS (quality of service), functionality, performance, etc. By way of illustrative example, a network slice may include a portion of one or more network resources, e.g., at one or more network entities, such as a portion of one or more of computing resources, memory resources, hardware resources, software or functional resources, and/or other network resources at a BS and/or at one or more core network entities, e.g., that may support a set of UEs or support a particular use case.

According to example implementations, a UE and/or a group of UEs, e.g., having similar QoS requirements or running the same or similar applications, providing common features or functionality for particular use cases or other common aspects, may support a network slice or may be allocated or assigned to a network slice, e.g., where a network slice identifier (or slice identifier) may identify a network slice. However, different UEs (e.g., different types of UEs) that may be assigned to different network slices and/or each different group of UEs may have different service requirements. According to example implementations, different UEs and/or each of multiple UE groups may be assigned to different network slices.

In addition, different UEs (e.g., different types of UEs) and/or groups of UEs (e.g., which may be assigned to different network slices) may also have different paging requirements. For example, mtc (large scale machine type communication) devices may require only a small amount of data transmission, but may need to handle UE battery/power consumption and control signaling very efficiently. Thus, a longer paging cycle may be desirable for mtc devices, at least in some cases. For example, other UEs or different groups of UEs that may be allocated to different network slices may require very low latency and, therefore, may require different paging services. For example, a URLLC UE may require a much shorter paging cycle, at least in some cases, to reduce delays in data delivery, e.g., from the network to the UE.

Thus, according to example implementations, slice-specific paging cycles (e.g., different paging cycles for each of a plurality of different network slices) may be used to provide different paging cycles for different network slices (e.g., where different slices may have different requirements, including different paging requirements). Thus, each slice-specific paging cycle may be specific to or associated with a particular slice, e.g., each slice-specific paging cycle may have a length (e.g., in radio frame number or other indicated length) based on the paging requirements of that slice. For example, a first slice-specific paging cycle of 32RFs may be used for a first slice; a second paging cycle of 64 RFs may be used for a second network slice; and a third paging cycle of 128 RFs may be used for a third network slice.

Further, a UE may have multiple different applications and/or data flows (e.g., protocol data unit sessions) that may generate and/or receive traffic or data. Thus, a UE may be assigned to multiple network slices, e.g., based on different types of traffic that may be transmitted to the UE, different applications running on the UE, or different use cases that the UE may support. Thus, a UE may be assigned or allowed to use multiple network slices. For example, in terms of downlink data, the UE may receive data of a first type or for a first application or use case via a first network slice and may receive data of a second type or for a second application or use case via a second network slice. Thus, the UE may be allowed or approved, e.g., by a network entity, to use multiple different network slices, and each of these different network slices may have a different slice-specific paging cycle.

According to an example implementation, the slice identifier may be or may include, for example, a single network slice selection assistance information (S-NSSAI) that may identify the slice. The Network Slice Selection Assistance Information (NSSAI) may include or identify a group or vector of slice identifiers (e.g., may include or identify a group or vector of S-NSSAIs).

According to an example implementation, a UE may receive information identifying a slice-specific paging cycle for each of one or more network slices allowed for the UE. For example, the UE may receive a paging cycle (e.g., an acknowledgement thereof) for each of one or more network slices allowed for the UE, such as from a core network entity. For example, this information for the paging cycle may be received by the UE from a core network entity as part of a registration procedure with the core network and/or as part of a PDU session establishment procedure with the core network (e.g., where each PDU session may be allocated or may be associated with a network slice, and thus, each PDU session may have an associated paging cycle for the UE). For example, the core network entity may allow the UE to use a first network slice with a first slice-specific paging cycle of 32RFs, a second network slice with a second slice-specific paging cycle of 64 RFs, and a third network slice with a third slice-specific paging cycle of 128 RFs. Accordingly, the UE may receive information from the core network entity identifying (or confirming) paging cycles of 32RFs, 64 RFs, and 128 RFs for the first network slice, the second network slice, and the third network slice, respectively.

The UE may also determine a smallest slice-specific paging cycle of the one or more slice-specific paging cycles for the UE. For example, the UE may determine which of the slice-specific paging cycles is the smallest (e.g., the fewest or shortest) of the three slices allowed for the UE among the paging cycles allowed for the UE. In this example, the UE may compare three paging cycles to each other to determine that the 32RF paging cycle (e.g., for the first network slice allowed for the UE) is the smallest (or least or shortest) of the three network slices allowed for the UE.

And, the UE may receive the paging message based on the minimum slice-specific paging cycle. For example, the UE may receive the paging message at a paging frame, which may be determined based on a minimum slice-specific paging cycle for the UE. For example, the UE may monitor radio frames based on its minimum slice-specific paging cycle. In this example, the UE may monitor for paging messages (e.g., a minimum paging cycle with 32 RFs), for example, every 32 th radio frame, in order to receive paging messages for any of the three slices allowed for the UE. The BS may know a minimum paging cycle for the UE and may transmit a RAN paging message for any slice at the minimum paging cycle. Thus, in this example, if the UE monitors for paging messages according to the minimum paging cycle for a plurality of slices allowed for the UE, the UE may monitor for paging messages for all three allowed slices.

Further, for example, the UE may have a cell-specific paging cycle, and/or a UE-specific paging cycle, which is not specific to any slice. Thus, in one example implementation, the UE may use (e.g., monitor for paging messages according to) a minimum paging cycle of all paging cycles assigned to or associated with the UE, e.g., the UE may use a minimum paging cycle for the UE of a cell-specific paging cycle, a UE-specific paging cycle, and a slice-specific paging cycle. In another example implementation, if one or more slice-specific paging cycles are assigned to or associated with the UE, the UE may use (e.g., may monitor for paging messages in accordance with) a smallest slice-specific paging cycle of the one or more slices that is allowed or approved for the UE.

In addition, the UE may also receive data based on the paging message. For example, if the received slice-specific paging message includes an identifier of the UE (e.g., TMSI), the UE may receive data based on the paging message by: a service request procedure is initiated in response to receiving a paging message identifying the UE/user equipment to obtain data.

In an example implementation, for example, via a registration procedure and/or a PDU session establishment procedure with a core network entity or via other procedures, a UE may send a first message to the core network entity, the first message including a slice identifier or a set of slice identifiers for one or more slices and a proposed paging cycle for each of the one or more network slices, and receive a second message from the core network entity by the UE indicating a slice identifier and a paging cycle associated with each of the one or more network slices that are allowed or approved for the UE.

As described above, the UE may receive information identifying a slice-specific paging cycle for each of one or more network slices allowed for the UE, e.g., via a registration procedure and/or a PDU session establishment procedure with a core network entity. For example, receiving, by the UE, information identifying a slice-specific paging cycle for each of one or more network slices allowed for the UE may include: sending, by the UE, a registration request to a core network entity to register with the network for the one or more network slices, the registration request including a slice identifier or a group or vector of slice identifiers for the one or more slices and a proposed paging cycle for each of the one or more network slices; and receiving, by the UE, a registration response from the core network entity, the registration response indicating a slice identifier and a paging cycle associated with each of the one or more network slices allowed for the UE.

According to another example implementation, receiving, by the UE, information identifying a slice-specific paging cycle for each of one or more network slices allowed for the UE may include: sending, by the UE, a protocol data unit, PDU, session establishment request to a core network entity to request establishment of a PDU session associated with a network slice, the PDU session establishment request including a PDU session identifier identifying the PDU session, a slice identifier identifying the network slice associated with or assigned to the PDU session, and a proposed paging cycle for the PDU session; and receiving, by the UE, a PDU session setup response from the core network entity, the PDU session setup response including at least a slice identifier for a network slice associated with or assigned to the PDU session, and a paging cycle for the PDU session for the UE.

As described above, a core network entity (e.g., such as an access and mobility management function (AMF)) may determine or confirm one or more slice-specific paging cycles for one or more network slices allowed or approved for a UE. The core network entity may receive a request from each UE of the plurality of UEs to use and determine or assign a paging cycle for the slice, including a different proposed paging cycle from for each UE of the plurality of UEs for the same network slice. The core network entity (e.g., AMF) may thus control or assign or determine a paging cycle for a slice, which may be allowed to be used by multiple UEs. Thus, the core network entity may receive a registration request or PDU session setup request or other message from the UE that includes a proposed paging cycle for slicing, and the core network entity may send a reply to the UE with a new or different proposed paging cycle for slicing. Thus, the core network entity and the UE may for example negotiate a paging cycle for slicing.

Thus, the core network entity may determine and inform the UE of the slice-specific paging cycle for one or more network slices approved or allowed for the UE. In addition, a core network entity (e.g., AMF) may inform the BS of one or more slice-specific paging cycles for the UE, e.g., via a core network paging message. The core network entity may provide the slice-specific paging cycle information to the BS using a variety of techniques:

1) in a first example implementation, the core network entity may determine a minimum slice-specific paging cycle for slices allowed for the UE, and may then include the minimum slice-specific paging cycle for the UE in a core network paging message sent to the BS. In this way, the core network may inform the BS of the minimum paging cycle for the UE (e.g., this may inform the BS of the timing or period for sending Radio Access Network (RAN) paging messages to the UE, as the UE will also monitor the downlink control channel's paging messages according to this same minimum slice-specific paging cycle).

2) In a second example implementation, the core network entity (e.g., the AMF) may send each (all) slice-specific paging cycle for the UE to the BS, e.g., send each slice-specific paging cycle for the slices allowed for the UE. The BS may then determine a minimum slice-specific paging cycle for the slices allowed for the UE. Thus, example implementations 1) allow the core network entity to determine the minimum slice-specific paging cycle for the UE and then provide this information to the BS. And implementation 2) allows the BS to determine a minimum slice-specific paging cycle for the UE among the received one or more paging cycles for the UE.

3) According to a third example implementation, a core network entity (e.g., an AMF) may send a core network paging message to a BS, the core network paging message including a slice-specific paging cycle associated with a network slice and a Protocol Data Unit (PDU) session, wherein the network slice is associated with the PDU session, and wherein the core network entity has data for delivery to the UE regarding the PDU session. Thus, the core network entity may inform the BS of the slice-specific paging cycle for PDU sessions (and slices) that triggered the paging of the UE (e.g., the paging cycle for PDU sessions and slices at the core network where there is data to deliver to the UE).

Thus, according to an example implementation, a BS may receive a core network paging message from a core network entity, the core network paging message including an identifier for a UE and a slice-specific paging cycle for one or more network slices allowed for the UE. The BS may select a paging cycle for the UE based on the received slice-specific paging cycle for the one or more network slices allowed for the UE. Thus, for example, the selected paging cycle may be the only paging cycle received by the BS from the core network, such as the minimum paging cycle or the paging cycle for PDU sessions that triggered paging; or the BS may select the paging cycle by: a minimum paging cycle is determined based on a plurality of paging cycles received from a core network entity. And, the BS may transmit a Radio Access Network (RAN) paging message to the UE based on the selected paging cycle for the UE. For example, the BS may send a RAN paging message to the UE according to a paging cycle selected for the UE, e.g., which may be the minimum paging cycle for the UE (according to the timing for it) or a PDU session paging cycle for which data is to be communicated.

According to an example implementation, the BS receiving a core network paging message from a core network entity including an identifier for the UE/user equipment and a slice-specific paging cycle for one or more network slices may include: receiving, by the BS, a core network paging message from a core network entity, the core network paging message including an identifier for the UE, a minimum slice-specific paging cycle of a plurality of slice-specific paging cycles for network slices allowed for the UE; and wherein selecting, by the BS (base station), the paging cycle for the UE comprises: the BS selects the minimum slice-specific paging cycle received for the UE.

According to an example implementation, the BS receiving a core network paging message from a core network entity including an identifier for the UE/user equipment and a slice-specific paging cycle for one or more network slices may include: the BS receiving a core network paging message comprising an identifier for the UE, a slice-specific paging cycle for each of a plurality of network slices allowed for the UE/user equipment; and wherein the base station selecting the paging cycle for the UE may comprise: a minimum paging cycle is selected by the BS for the UE in a slice-specific paging cycle for each of a plurality of network slices allowed for the UE.

According to an example implementation, the BS receiving a core network paging message from a core network entity including an identifier for the UE and a slice-specific paging cycle for one or more network slices may include: the BS receiving a core network paging message comprising an identifier for the UE, a slice-specific paging cycle associated with a network slice and a Protocol Data Unit (PDU) session, wherein the network slice is associated with the PDU session, and wherein a core network entity has data to be delivered to the UE with respect to the PDU session; and wherein selecting, by the base station, the paging cycle for the UE comprises: the received slice-specific paging cycle associated with the PDU session is selected by the base station.

Fig. 2 is a diagram illustrating a registration procedure between a UE and a core network entity according to an example implementation. As shown in fig. 2, a registration procedure may be performed between a UE210 and a core network entity, such as an access and mobility management function (AMF)220 at the core network. At 230, the UE210 may transmit a registration request that includes a group of one or more slice (network slice) identifiers (e.g., NSSAIs), which may indicate the group of one or more slices for which the UE is requesting support or requesting to join. The registration request at 230 may include a (proposed) slice-specific paging cycle (or list of one or more paging cycles) for each identified network slice. At 240, the core network entity (AMF 220) may send a registration response to the UE210, the registration response including a set of one or more slice identifiers (e.g., NSSAIs) allowed or approved for one or more slices of the UE, and a (acknowledged) slice-specific paging cycle for each allowed slice of the UE.

Fig. 3 is a diagram illustrating a Protocol Data Unit (PDU) session establishment procedure between a User Equipment (UE) and a core network entity (e.g., an AMF) according to an example implementation. At 320, the UE210 sends a PDU session setup request to request setup of a PDU session associated with the network slice. The PDU setup request may include a PDU session identifier (PDU session ID) identifying the PDU session, a slice identifier (e.g., S-NSSAI), and a (proposed) slice-specific paging cycle for the identified slice and associated PDU session (also identified in the PDU session setup request). At 330, the UE210 receives a PDU session setup answer/acceptance from a core network entity (e.g., the AMF 220) indicating acceptance or establishment of the requested PDU session, a slice identifier of a slice associated with the PDU session, and a slice-specific paging cycle (e.g., acknowledged) for the slice and associated PDU session.

Thus, according to example implementations, different network slices may be associated with different paging cycles (e.g., each slice may be associated with a respective paging cycle, which may be different from other slices depending on the service requirements or QoS requirements of the slice). Some slices may require more frequent paging, while other slices may require less frequent paging.

The configuration of paging cycles associated with different slices may be exchanged during a registration procedure or PDU session establishment procedure between the UE and a core network entity (e.g., AMF). Thus, for example, there may be two (or more) different example ways to configure slices with paging cycles, such as, for example: 1) during UE registration, the UE may include a (proposed) paging cycle for each requested slice identifier within the registration request; and 2) during UE PDU session establishment, the UE sends a PDU session establishment request to the AMF, the PDU session establishment request including a slice identifier (e.g., S-NSSAI), a PDU session ID, and a (e.g., proposed) paging cycle for each of the one or more requested PDU sessions, wherein each PDU session may be assigned to or associated with a respective network slice. Because, for example, many UEs may propose paging cycles for the same slice, the core network entity or AMF may approve any proposed paging cycle and may propose different paging cycles to the UEs (e.g., so that slices used by many UEs will have the same paging cycle among multiple UEs).

According to an example implementation, if the UE and AMF have agreed during the registration procedure for the paging cycle of one or more slices, the UE may propose a different paging cycle later during PDU session establishment instead of the earlier agreed paging cycle for the slice, for example. For example, a first procedure for UE registration may be performed followed by a second procedure for PDU session establishment. The slice-specific paging cycle may be transmitted, for example, subsequently from the core network entity (e.g., AMF) to the gbb/BS in a core network paging message (see fig. 4).

According to an example implementation, slice-specific paging cycles may be configured for each slice that is approved or allowed for a UE, e.g., in addition to existing UE-specific paging cycles. If the UE has the capability to support network slice and slice-specific paging, the UE may negotiate its requested paging cycle for each slice with the AMF/core network entity. The UE and the AMF may exchange paging cycle configurations (paging cycle values) and decide whether to apply a UE-specific paging cycle or a slice-specific paging cycle (e.g., as long as the paging cycle is shorter or smallest) via a registration procedure or/and a PDU session setup procedure.

For example, if the paging cycle for each slice identified by the S-NSSAI (slice identifier) in the requested NSSAI is present in the registration request 230 (fig. 2) from the UE to the AMF, then slice-specific paging cycles (or paging and monitoring for paging messages) may typically be applied, for example, rather than UE-specific paging cycles. The network may then provide (or acknowledge) a paging cycle in registration response 240 (fig. 2) for each slice identified by the S-NSSAI in the allowed NSSAI.

Furthermore, since a PDU session, e.g., per PLMN (public land mobile network) or network, only belongs to or is associated with one particular network slice instance, the paging cycle for slicing supported by the PDU session may be configured when setting up the PDU session.

Fig. 4 is a diagram illustrating operation of a paging procedure based on slice-specific paging cycles according to an example implementation. The bs (gnb)410 communicates with the UE210 and the core network entity (or AMF) 220. At 420, when MT data (mobile terminal data or data to be delivered to the UE 210) is present, the AMF 220 may send a core network paging message to the BS 410, the core network paging message including an identifier (e.g., TMSI) for the UE210 and at least one slice-specific paging cycle. As described above, the AMF 220 may have various implementations or techniques to provide slice-specific paging cycles to the BS 410, including: 1) the AMF 220 (or core network entity) may determine and then provide a minimum slice-specific paging cycle for the slices allowed for the UE; 2) the AMF 220 (or core network entity) may send each (or all) of the slice-specific paging cycles for the slices allowed for the UE to the BS 410 (where the BS may then determine a minimum paging cycle among the received paging cycles for the UE); and 3) the AMF 220 (or core network entity) may send slice-specific paging cycles associated with network slices and PDU sessions, e.g., paging cycles for PDU data sessions (and associated slices) that cause or trigger paging of the UE 210.

At 430, the BS may select (or determine) a paging cycle for the UE based on the received paging cycle for the UE. For example, if at 430 BS 410 receives only one paging cycle (e.g., a minimum paging cycle or a paging cycle for PDU sessions and slices that triggers or causes paging of UE 210) for UE210, then BS 410 will select the one received paging cycle for paging the UE. However, if BS 410 receives slice-specific paging cycles for multiple slices allowed or approved for UE210, for example, BS 410 may determine a minimum paging cycle of the received paging cycles for the UE, and may then select the minimum paging cycle for paging the UE (e.g., a RAN paging message may be sent by BS 410 to UE210 based on the timing of the selected paging cycle).

At 440, the UE similarly determines a minimum paging cycle of paging cycles for the UE for the one or more approved slices, and then the UE210 monitors or listens for paging messages according to such minimum paging cycle for the UE.

At 450, BS 410 sends a RAN paging message to UE210 during a radio frame according to the selected paging cycle for the UE. The UE210 may receive the RAN paging message and may then obtain the data if its UE identifier is provided within the RAN paging message.

Thus, in the illustrative example, the core network paging message 420 from the AMF 220 may provide or include a paging cycle supported by the UE for each slice when MT data (mobile/UE terminated data, or data directed to the UE) is present. BS 410 may decide the paging cycle by choosing the minimum paging cycle from the sliced paging cycles supported by the UE, and then page UE210 from the accordingly derived paging occasion (e.g., page during the paging occasion during a radio frame according to the minimum paging cycle for the UE).

As another alternative, the AMF 220 may include a single paging cycle in the core network paging message 420, where the single paging cycle indicated in the core network paging message may be, for example: 1) a minimum paging cycle among all paging cycles of a slice supported by the UE; or 2) the paging cycle of the slice supported by the PDU session that the UE needs to receive MT data.

The UE may typically select a minimum paging cycle from the paging cycles allowed for each slice of the UE, and the UE monitors/listens for RAN paging messages 450 on paging occasions derived from the minimum paging cycle for the UE. For example, if the UE has 3 PDU sessions (and the slice and paging cycle associated with each of these PDU sessions), there may be up to 3 different paging cycles. For example:

PDU session 1: slice 1, paging cycle 128rf (128 radio frames)

PDU session 2: slice 2, paging cycle 64rf

PDU session 3: slice 1, paging cycle 32rf

According to an example implementation, the paging cycle for the UE may be selected as the minimum paging cycle for all slices. Thus, in this illustrative example, the UE would apply a paging cycle of 32rfs (32 radio frames).

In this manner, slice-specific paging cycles may be applied by the network and the UE for each of one or more network slices, where each slice-specific paging cycle may be tailored or adjusted to meet slice-specific paging requirements (or to meet performance requirements assigned to the slice or an application or use case associated with the slice). In this manner, paging performance may be improved via slice-specific paging cycles that may be adapted or adapted to varying performance requirements of different types of devices or use cases.

Example 1: FIG. 5 is a flow diagram illustrating operation of a user device according to an example implementation. Operation 510 comprises receiving, by a user equipment within a wireless network, information identifying a slice-specific paging cycle for one or more network slices allowed for the user equipment. Operation 520 comprises determining, by the user equipment, a minimum slice-specific paging cycle of the one or more slice-specific paging cycles. And, operation 530 comprises receiving, by the user equipment, a paging message based on the minimum slice-specific paging cycle.

Example 2: the example implementation described in example 1, and further comprising: receiving, by the user equipment, data based on the paging message.

Example 3: the example implementation of any one of examples 1 to 2, wherein the paging message includes a paging record, the paging record identifying the user equipment; wherein receiving, by the user equipment, data based on the paging message comprises: a service request procedure is initiated by the user equipment to obtain data in response to receiving a paging message identifying the user equipment.

Example 4: the example implementation of any of examples 1-3, and further comprising: transmitting, by a user equipment, a first message to a core network entity, the first message comprising a slice identifier for one or more network slices and a proposed paging cycle; and receiving, by the user equipment from the core network entity, a second message indicating a slice identifier and a paging cycle associated with one or more network slices that are allowed or approved for the user equipment.

Example 5: the example implementation of any one of examples 1 to 4, wherein receiving, by a user equipment within a wireless network, information identifying slice-specific paging cycles allowed for one or more network slices of the user equipment comprises: sending, by a user equipment, a registration request to a core network entity to register with a network for one or more network slices, the registration request including a slice identifier and a proposed paging cycle for the one or more network slices; and receiving, by the user equipment, a registration response from the core network entity, the registration response indicating a slice identifier and a paging cycle associated with the one or more network slices allowed for the user equipment.

Example 6: the example implementation of any one of examples 1 to 5, wherein receiving, by a user equipment within a wireless network, information identifying slice-specific paging cycles allowed for one or more network slices of the user equipment comprises: sending, by a user equipment, a protocol data unit, PDU, session establishment request to a core network entity to request establishment of a PDU session associated with a network slice, the PDU session establishment request including a PDU session identifier identifying the PDU session, a slice identifier identifying the network slice associated with or assigned to the PDU session, and a proposed paging cycle for the PDU session; and receiving, by the user equipment, a PDU session setup response from the core network entity, the PDU session setup response comprising at least a slice identifier for a network slice associated with or assigned to the PDU session, and a paging cycle for the PDU session for the user equipment.

Example 7: FIG. 6 is a flow diagram illustrating operation of a user device according to an example implementation. Operation 610 includes receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for one or more network slices allowed for the user equipment. Operation 620 comprises selecting, by the base station, a paging cycle for the user equipment based on the received slice-specific paging cycle for the one or more network slices allowed for the user equipment. And, operation 630 comprises transmitting, by the base station, a Radio Access Network (RAN) paging message to the user equipment based on the selected paging cycle for the user equipment.

Example 8: the example implementation of example 7, wherein receiving comprises: receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message comprising an identifier for a user equipment, a smallest slice-specific paging cycle of a plurality of slice-specific paging cycles for network slices allowed for the user equipment; and wherein selecting, by the base station, a paging cycle for the user equipment comprises: the received minimum slice-specific paging cycle is selected for the user equipment.

Example 9: the example implementation of any one of examples 7 to 8, wherein receiving comprises: receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message including an identifier for a user equipment, a slice-specific paging cycle for each of a plurality of network slices allowed for the user equipment; and wherein selecting, by the base station, a paging cycle for the user equipment comprises: selecting, by the base station, a minimum paging cycle for the user equipment in a slice-specific paging cycle for each of a plurality of network slices allowed for the user equipment.

Example 10: the example implementation of any one of examples 7 to 9, wherein receiving comprises: receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message including an identifier for a user equipment, a slice-specific paging cycle associated with a network slice and a Protocol Data Unit (PDU) session, wherein the network slice is associated with the PDU session, and wherein the core network entity has data for delivery to the user equipment with respect to the PDU session; and wherein selecting, by the base station, a paging cycle for the user equipment comprises: the received slice-specific paging cycle associated with the PDU session is selected by the base station.

Example 11: the example implementation of any of examples 7 to 10, and further comprising: transmitting, by a base station, data to a user equipment in response to: a service request procedure is initiated by the user equipment in response to the RAN paging message.

Example 12: fig. 7 is a flow diagram illustrating operation of a core network entity according to an example implementation. Operation 710 comprises transmitting, by a core network entity, a core network paging message to a base station in a wireless network, the core network paging message comprising an identifier for a user equipment and a slice-specific paging cycle for one or more network slices allowed for the user equipment.

Example 13: the example implementation of example 12, wherein the sending comprises: determining a minimum slice-specific paging cycle among a plurality of slice-specific paging cycles for network slices allowed for a user equipment; and transmitting, by the core network entity, a core network paging message to a base station in the wireless network, the core network paging message comprising an identifier for the user equipment and a smallest slice-specific paging cycle of the plurality of slice-specific paging cycles for network slices allowed for the user equipment.

Example 14: the example implementation of any one of examples 12 to 13, wherein the sending comprises: sending, by a core network entity, a core network paging message to a base station in a wireless network, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for each of a plurality of network slices allowed for the user equipment.

Example 15: the example implementation of any one of examples 12 to 14, wherein the sending comprises: sending, by a core network entity, a core network paging message to a base station in a wireless network, the core network paging message comprising an identifier for a user equipment, a slice-specific paging cycle associated with a network slice and a Protocol Data Unit (PDU) session, wherein the network slice is associated with the PDU session, and wherein the core network entity has data for delivery to the user equipment with respect to the PDU session.

Example 16: the example implementation of any of examples 12 to 15, and further comprising: receiving, by a core network entity, a first message from a user equipment, the first message comprising a slice identifier for one or more network slices and a proposed paging cycle; and transmitting, by the core network entity, a second message to the user equipment, the second message indicating a slice identifier and a paging cycle associated with one or more network slices that are allowed or approved for the user equipment.

Example 17: the example implementation of any one of examples 12 to 16, wherein the first message includes at least one of: a registration request; and a Protocol Data Unit (PDU) session establishment request; and wherein the second message comprises at least one of: registering a response; and a PDU session setup response.

Example 18: an apparatus comprising means for performing the method of any of examples 1-17.

Example 19: an apparatus comprising at least one processor and at least one memory including computer instructions that, when executed by the at least one processor, cause the apparatus to perform the method of any of examples 1-17.

Example 20: an apparatus comprising a computer program product comprising a non-transitory computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform the method according to any of examples 1 to 17.

Fig. 8 is a block diagram of a wireless station (e.g., AP, BS, eNB, UE, or user equipment) 1000 implemented according to an example. Wireless station 1000 may include, for example, one or two RF (radio frequency) or

wireless transceivers

1002A, 1002B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit/entity (controller) 1004 to execute instructions or software and control the transmission and reception of signals, and a memory 1006 to store data and/or instructions.

The processor 1004 may also make decisions or determinations, generate frames, packets, or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. For example, processor 1004, which may be a baseband processor, may generate messages, packets, frames, or other signals for transmission via wireless transceiver 1002(1002A or 1002B). Processor 1004 may control transmission of signals or messages over a wireless network, and may control reception of signals or messages via a wireless network, etc. (e.g., after being down-converted by wireless transceiver 1002). The processor 1004 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 1004 may be (or may include), for example, hardware, programmable logic, a programmable processor executing software or firmware, and/or any combination of these. For example, using other terminology, the processor 1004 and the transceiver 1002 together may be considered a wireless transmitter/receiver system.

Additionally, referring to fig. 8, a controller (or processor) 1008 may execute software and instructions and may provide overall control for the station 1000, and may provide control for other systems not shown in fig. 8, such as controlling input/output devices (e.g., displays, keypads), and/or may execute software for one or more applications that may be provided on the wireless station 1000, such as, for example, email programs, audio/video applications, a word processor, voice over IP applications, or other applications or software.

Additionally, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may cause the processor 1004, or other controller or processor, to perform one or more of the functions or tasks described above.

According to another example implementation, RF or wireless transceivers 1002A/1002B may receive signals or data and/or transmit signals or data. Processor 1004 (and possibly transceivers 1002A/1002B) may control RF or

wireless transceivers

1002A or 1002B to receive, transmit, broadcast, or transmit signals or data.

However, the embodiments are not limited to the systems given as examples, and a person skilled in the art may apply the solution to other communication systems. Another example of a suitable communication system is the 5G concept. It is assumed that the network architecture in 5G will be very similar to that of LTE-advanced. 5G may use multiple input-multiple output (MIMO) antennas, many more base stations or nodes than LTE (the so-called small cell concept), including macro-stations operating in cooperation with smaller stations, and perhaps also employ various radio technologies to achieve better coverage and enhanced data rates.

It should be understood that future networks will most likely utilize Network Function Virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions as "building blocks" or entities that may be operably connected or linked together to provide services. A Virtualized Network Function (VNF) may comprise one or more virtual machines running computer program code using standard or generic type servers instead of custom hardware. Cloud computing or data storage may also be utilized. In radio communication, this may mean that node operations may be performed at least partially in a server, host or node operatively coupled to a remote radio head. Node operations may also be distributed among multiple servers, nodes, or hosts. It should also be understood that the labor allocation between core network operation and base station operation may be different than that of LTE, or even non-existent.

Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Implementations may also be provided on a computer-readable medium or computer-readable storage medium, which may be non-transitory media. Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or program and/or software implementations downloadable via the internet or other networks (wired and/or wireless). Additionally, implementations may be provided via Machine Type Communication (MTC), and also via internet of things (IOT).

The computer program may be in source code form, object code form, or in some intermediate form, and may be stored in some carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. Such carriers include, for example, record media, computer memory, read-only memory, electro-optical and/or electrical carrier signals, telecommunication signals, and software distribution packages. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or may be distributed over a plurality of computers.

Further, implementations of the various techniques described herein may use a Cyber Physical System (CPS) (a system of cooperating computing elements that control physical entities). CPS may enable the implementation and utilization of a large number of interconnected ICT devices (sensors, actuators, processor microcontrollers) embedded in physical objects at different locations. The mobile network physical systems in which the physical system in question has an inherent mobility are a sub-category of network physical systems. Examples of mobile physical systems include mobile robots and electronic devices transported by humans or animals. The popularity of smart phones has increased interest in the area of mobile network physical systems. Thus, various implementations of the techniques described herein may be provided via one or more of these techniques.

A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or portion suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

Method steps may be performed by one or more programmable processors executing a computer program or portion of a computer program to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chip set. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, implementations may be implemented on a computer having a display device (e.g., a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD) monitor) for displaying information to the user and a user interface (such as a keyboard and a pointing device, e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.

Implementations may include a back-end component (e.g., as a data server), or include a middleware component (e.g., an application server), or include a front-end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation), or any combination of such back-end, middleware, or front-end components. The components may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a Local Area Network (LAN) and a Wide Area Network (WAN), such as the Internet.

While certain features of the described implementations have been illustrated as described herein, many modifications, substitutions, changes, and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the various embodiments.

Claims

1. A method, comprising:

receiving, by a user equipment within a wireless network, information identifying a slice-specific paging cycle for one or more network slices allowed for the user equipment;

determining, by the user equipment, a minimum slice-specific paging cycle of the one or more slice-specific paging cycles; and

receiving, by the user equipment, a paging message based on the minimum slice-specific paging cycle.

2. The method of claim 1, and further comprising:

receiving, by the user equipment, data based on the paging message.

3. The method of any of claims 1-2:

wherein the paging message comprises a paging record, the paging record identifying the user equipment;

wherein receiving, by the user equipment, the data based on the paging message comprises: initiating, by the user equipment, a service request procedure to obtain the data in response to receiving the paging message identifying the user equipment.

4. The method of any of claims 1-3, and further comprising:

sending, by the user equipment, a first message to the core network entity, the first message comprising a slice identifier for one or more network slices and a proposed paging cycle; and

receiving, by the user equipment, a second message from the core network entity, the second message indicating a slice identifier and a paging cycle associated with one or more network slices that are allowed or approved for the user equipment.

5. The method of any of claims 1-4, wherein receiving, by the user equipment within the wireless network, the information identifying the slice-specific paging cycles allowed for the one or more network slices of the user equipment comprises:

sending, by the user equipment, a registration request to a core network entity to register with the network for one or more network slices, the registration request including a slice identifier and a proposed paging cycle for the one or more network slices; and

receiving, by the user equipment, a registration response from the core network entity, the registration response indicating a slice identifier and a paging cycle associated with one or more network slices allowed for the user equipment.

6. The method of any of claims 1-5, wherein receiving, by the user equipment within the wireless network, the information identifying the slice-specific paging cycles allowed for the one or more network slices of the user equipment comprises:

sending, by the user equipment, a protocol data unit, PDU, session establishment request to a core network entity to request establishment of a PDU session associated with a network slice, the PDU session establishment request including a PDU session identifier identifying the PDU session, a slice identifier identifying the network slice associated with or assigned to the PDU session, and a proposed paging cycle for the PDU session; and

receiving, by the user equipment, a PDU session setup response from the core network entity, the PDU session setup response including at least a slice identifier for the network slice associated with or assigned to the PDU session and a paging cycle for the PDU session for the user equipment.

7. A method, comprising:

receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for one or more network slices allowed for the user equipment;

selecting, by the base station, a paging cycle for the user equipment based on the received slice-specific paging cycle for the one or more network slices allowed for the user equipment; and

transmitting, by the base station, a Radio Access Network (RAN) paging message to the user equipment based on the paging cycle selected for the user equipment.

8. The method of claim 7, wherein the receiving comprises:

receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message comprising an identifier for a user equipment, a smallest slice-specific paging cycle of a plurality of slice-specific paging cycles for a network slice allowed for the user equipment; and

wherein selecting, by the base station, the paging cycle for the user equipment comprises:

selecting the minimum slice-specific paging cycle received for the user equipment.

9. The method of any of claims 7 to 8, wherein the receiving comprises:

receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message including an identifier for a user equipment, a slice-specific paging cycle for each of a plurality of network slices allowed for the user equipment; and

selecting, by the base station, a minimum paging cycle for the user equipment in the slice-specific paging cycle for each of the plurality of network slices allowed for the user equipment.

10. The method of any of claims 7 to 9, wherein the receiving comprises:

receiving, by a base station in a wireless network, a core network paging message from a core network entity, the core network paging message comprising an identifier for a user equipment, a slice-specific paging cycle associated with a network slice and a Protocol Data Unit (PDU) session, wherein the network slice is associated with the PDU session, and wherein the core network entity has data for delivery to the user equipment with respect to the PDU session; and

selecting, by the base station, the received slice-specific paging cycle associated with the PDU session.

11. The method of any of claims 7 to 10, and further comprising:

transmitting, by the base station, data to the user equipment in response to: initiating, by the user equipment, a service request procedure in response to the RAN paging message.

12. A method, comprising:

sending, by a core network entity, a core network paging message to a base station in a wireless network, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for one or more network slices allowed for the user equipment.

13. The method of claim 12, wherein the sending comprises:

determining a minimum slice-specific paging cycle among a plurality of slice-specific paging cycles for network slices allowed for the user equipment; and

sending, by a core network entity, a core network paging message to a base station in a wireless network, the core network paging message comprising an identifier for a user equipment and the minimum slice-specific paging cycle of a plurality of slice-specific paging cycles for network slices allowed for the user equipment.

14. The method of any of claims 12 to 13, wherein the sending comprises:

sending, by a core network entity, a core network paging message to a base station in a wireless network, the core network paging message including an identifier for a user equipment and a slice-specific paging cycle for each of a plurality of network slices allowed for the user equipment.

15. The method of any of claims 12 to 14, wherein the sending comprises:

sending, by a core network entity, a core network paging message to a base station in a wireless network, the core network paging message comprising an identifier for a user equipment, a slice-specific paging cycle associated with a network slice and a Protocol Data Unit (PDU) session, wherein the network slice is associated with the PDU session, and wherein the core network entity has data for delivery to the user equipment with respect to the PDU session.

16. The method according to any one of claims 12 to 15, and further comprising:

receiving, by the core network entity, a first message from the user equipment, the first message comprising a slice identifier for one or more network slices and a proposed paging cycle; and

sending, by the core network entity, a second message to the user equipment indicating a slice identifier and a paging cycle associated with one or more network slices that are allowed or approved for the user equipment.

17. The method of claim 16, wherein the first message comprises at least one of:

a registration request; and

a Protocol Data Unit (PDU) session establishment request; and is

Wherein the second message comprises at least one of:

registering a response; and

a PDU session establishment response.

18. An apparatus comprising means for performing the method of any one of claims 1-17.

19. An apparatus comprising at least one processor and at least one memory including computer instructions that, when executed by the at least one processor, cause the apparatus to perform the method of any of claims 1-17.

20. An apparatus comprising a computer program product comprising a non-transitory computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform the method of any of claims 1 to 17.