[go: up one dir, main page]

WO2019028838A1 - Cycles de radiomessagerie spécifiques à une tranche de réseau pour réseaux sans fil - Google Patents

Cycles de radiomessagerie spécifiques à une tranche de réseau pour réseaux sans fil Download PDF

Info

Publication number
WO2019028838A1
WO2019028838A1 PCT/CN2017/097108 CN2017097108W WO2019028838A1 WO 2019028838 A1 WO2019028838 A1 WO 2019028838A1 CN 2017097108 W CN2017097108 W CN 2017097108W WO 2019028838 A1 WO2019028838 A1 WO 2019028838A1
Authority
WO
WIPO (PCT)
Prior art keywords
user device
slice
paging cycle
network
core network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/097108
Other languages
English (en)
Inventor
Yanji Zhang
Yuantao Zhang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to CN201780095147.5A priority Critical patent/CN111108785B/zh
Priority to PCT/CN2017/097108 priority patent/WO2019028838A1/fr
Publication of WO2019028838A1 publication Critical patent/WO2019028838A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel

Definitions

  • This description relates to communications.
  • a communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.
  • LTE Long-term evolution
  • UMTS Universal Mobile Telecommunications System
  • E-UTRA evolved UMTS Terrestrial Radio Access
  • LTE base stations or access points (APs)
  • APs access points
  • eNBs enhanced Node AP
  • UE user equipments
  • LTE has included a number of improvements or developments.
  • mmWave underutilized millimeter wave (mmWave) frequency spectrum for future broadband cellular communication networks
  • mmWave may, for example, include the frequency range between 30 and 300 gigahertz (GHz) .
  • Radio waves in this band may, for example, have wavelengths from ten to one millimeters, giving it the name millimeter band or millimeter wave.
  • the amount of wireless data will likely significantly increase in the coming years.
  • Various techniques have been used in attempt to address this challenge including obtaining more spectrum, having smaller cell sizes, and using improved technologies enabling more bits/s/Hz.
  • One element that may be used to obtain more spectrum is to move to higher frequencies, e.g., above 6 GHz.
  • 5G fifth generation wireless systems
  • 5G an access architecture for deployment of cellular radio equipment employing mmWave radio spectrum has been proposed.
  • Other example spectrums may also be used, such as cmWave radio spectrum (e.g., 3-30 GHz) .
  • 5G wireless networks may support network slicing, wherein 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.
  • a method includes: receiving, by a user device within a wireless network, information identifying a slice-specific paging cycle for each of one or more network slices allowed for the user device; determining, by the user device, a minimum slice-specific paging cycle among the one or more slice-specific paging cycles; and receiving, by the user device, a paging message based on the minimum slice-specific paging cycle.
  • an apparatus includes 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: receive, by a user device within a wireless network, information identifying a slice-specific paging cycle for each of one or more network slices allowed for the user device; determine, by the user device, a minimum slice-specific paging cycle among the one or more slice-specific paging cycles; and receive, by the user device, a paging message based on the minimum slice-specific paging cycle.
  • a computer program product includes 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 including: receiving, by a user device within a wireless network, information identifying a slice-specific paging cycle for each of one or more network slices allowed for the user device; determining, by the user device, a minimum slice-specific paging cycle among the one or more slice-specific paging cycles; and receiving, by the user device, a paging message based on the minimum slice-specific paging cycle.
  • a method includes: receiving, by a base station in a wireless network from a core network entity, a core network paging message that includes an identifier for a user device and a slice-specific paging cycle for one or more network slices that are allowed for the user device; selecting, by the base station, a paging cycle for the user device based on the received slice-specific paging cycle for the one or more network slices that are allowed for the user device; and sending, by the base station, a radio access network (RAN) paging message to the user device based on the selected paging cycle for the user device.
  • RAN radio access network
  • an apparatus includes 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: receive, by a base station in a wireless network from a core network entity, a core network paging message that includes an identifier for a user device and a slice-specific paging cycle for one or more network slices that are allowed for the user device; select, by the base station, a paging cycle for the user device based on the received slice-specific paging cycle for the one or more network slices that are allowed for the user device; and send, by the base station, a radio access network (RAN) paging message to the user device based on the selected paging cycle for the user device.
  • RAN radio access network
  • a computer program product includes 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 including: receiving, by a base station in a wireless network from a core network entity, a core network paging message that includes an identifier for a user device and a slice-specific paging cycle for one or more network slices that are allowed for the user device; selecting, by the base station, a paging cycle for the user device based on the received slice-specific paging cycle for the one or more network slices that are allowed for the user device; and sending, by the base station, a radio access network (RAN) paging message to the user device based on the selected paging cycle for the user device.
  • RAN radio access network
  • a method comprising: sending, by a core network entity to a base station in a wireless network, a core network paging message that includes an identifier for a user device and a slice-specific paging cycle for one or more network slices that are allowed for the user device.
  • an apparatus includes 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: send, by a core network entity to a base station in a wireless network, a core network paging message that includes an identifier for a user device and a slice-specific paging cycle for one or more network slices that are allowed for the user device.
  • a computer program product includes 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 including: sending, by a core network entity to a base station in a wireless network, a core network paging message that includes an identifier for a user device and a slice-specific paging cycle for one or more network slices that are allowed for the user device.
  • FIG. 1 is a block diagram of a wireless network according to an example implementation.
  • FIG. 2 is a diagram illustrating of registration procedure between a user device 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 device and a core network entity according to an example implementation.
  • PDU protocol data unit
  • FIG. 4 is a diagram illustrating operation of a paging procedure based on a slice-specific paging cycle according to an example implementation.
  • FIG. 5 is a flow chart illustrating operation of a user device according to an example implementation.
  • FIG. 6 is a flow chart illustrating operation of a base station according to an example implementation.
  • FIG. 7 is a flow chart 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 device) according to an example implementation.
  • a node or wireless station e.g., base station/access point or mobile station/user device
  • FIG. 1 is a block diagram of a wireless network 130 according to an example implementation.
  • user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs) may be connected (and in communication) 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.
  • BS base station
  • AP access point
  • eNB enhanced Node B
  • gNB which may be a 5G base station
  • BS base station
  • eNB Node B
  • BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices 131, 132, 133 and 135. Although only four user devices are shown as being connected or attached to BS 134, any number of user devices may be provided.
  • BS 134 is also connected to a core network 150 via an interface 151. This is merely one simple example of a wireless network, and others may be used.
  • a user device may refer to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM) , including, but not limited to, the following types of devices: a mobile station (MS) , a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA) , a handset, a device using a wireless modem (alarm or measurement device, etc. ) , a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples.
  • SIM subscriber identification module
  • MS mobile station
  • PDA personal digital assistant
  • a handset a device using a wireless modem (alarm or measurement device, etc. )
  • laptop and/or touch screen computer a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples.
  • a user device may also be a nearly exclusive uplink only device, of which an example is a camera or
  • core network 150 may be referred to as Evolved Packet Core (EPC) , which may include a mobility management entity (MME) which may handle or assist with mobility/handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • EPC Evolved Packet Core
  • MME mobility management entity
  • gateways may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • the 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.
  • 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 only as illustrative examples, and the 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 communications (URLLC) , Internet of Things (IoT) , enhanced mobile broadband, massive machine type communications (MMTC) , vehicle-to-vehicle (V2V) , vehicle-to-device, etc.
  • URLLC ultra-reliability low latency communications
  • IoT Internet of Things
  • MMTC massive machine type communications
  • V2V vehicle-to-vehicle
  • vehicle-to-device etc.
  • Each of these use cases, or types of UEs may have its own set of requirements.
  • a paging procedure may be used to inform a UE in Idle mode about an incoming call or data that is to be provided or transmitted to the UE.
  • the core network may request a 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 for the UE (e.g., temporary mobile subscriber identifier (TMSI) ) within a paging record provided within the paging message.
  • TMSI temporary mobile subscriber identifier
  • the UE may then initiate a service request procedure with the network (NW) to obtain the data, which may, for example, include performing random access with the NW, establishing a connection with the NW, and then receiving the data from the NW.
  • the network (NW) may include the core network (or one or more core network entities) and/or the BS (which is part of the radio access network or RAN) .
  • a paging cycle (or DRX cycle) may, e.g., be a period of time or a number of radio frames (RFs) between paging frames.
  • RFs radio frames
  • a paging frame for a UE may be a frame in which there may be paging message sent to the UE.
  • a paging frame may include one or more paging occasions, which may include a paging message to the UE.
  • a paging cycle may be used for a UE of, e.g., 32 RFs (radio frames) , 64 RFs, 128 RFs, 256 RFs, etc., or other number of radio frames.
  • a longer paging cycle may allow for greater battery savings (e.g., allowing for the UE to remain in a low power state for a longer period of time before waking to monitor for or detect any paging messages)
  • a shorter paging cycle may allow for a quicker data delivery (with shorter latency) to the UE at the expense of higher battery consumption (e.g., since the idle mode UE will remain in a low power state a shorter period of time for a shorter paging cycle) .
  • a UE may need to wake from a sleep state or low power state only every paging cycle (e.g., wake every 64 RFs or every 32 RFs) to monitor a downlink channel for any paging messages, and then determine if a received paging message includes a paging record with the UE’s identifier (e.g., the UE’s temporary mobile subscriber identifier (TMSI) ) . If the paging message includes the UE’s identifier (indicating that the network has data for the UE) , the UE may then initiate a service request procedure with the network (e.g., BS and/or core network) to obtain the data.
  • the service request procedure may include, e.g., the UE performing random access with the base station, establishing a connection with the base station, and then receiving the data.
  • 5G wireless networks may support network slicing, wherein 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 Slicing may allow differentiated treatment depending on requirements of different UEs or groups of UEs. With slicing (network slicing) , an operator can create networks for optimized solutions based on different service requirements, QoS (quality of service) , functionality, performance, etc.
  • a network slice may include, for example, a portion of one or more network resources at one or more network entities, such as a portion of, e.g., one or more of computational 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, for example, that may support a group of UEs or support a particular use case.
  • network entities such as a portion of, e.g., one or more of computational 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, for example, that may support a group of UEs or support a particular use case.
  • a UE and/or group of UEs 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 the network slice.
  • a network slice identifier or slice identifier
  • different UEs e.g., different type of UEs
  • each different group of UEs which may be assigned to different network slices, may have different service requirements.
  • different UEs and/or each of multiple groups of UEs may be assigned to a different network slice.
  • UEs e.g., different types of UEs
  • each group of UEs e.g., which may be assigned to a different network slice
  • paging requirements For example, mMTC (massive machine-type communications) devices may only need a small amount of data transmission, but may demand a very efficient handling of UE battery/power consumption and control signaling. Thus, a longer paging cycle may, at least in some cases, be desirable for mMTC devices.
  • Other UEs or different groups of UEs e.g., which may be allocated to a different network slice, may require very low latency and thus, may require different paging services.
  • URLLC UEs at least in some cases, may require a much shorter paging cycle in order to reduce latency for data delivery from the network to the UE, for example.
  • slice-specific paging cycles may be used in order to provide different paging cycles for different network slices (e.g., where different slices may have different requirements, including different paging requirements) .
  • 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 frames or other indicated length) based on the paging requirements for that slice.
  • a first slice-specific paging cycle of 32 RFs 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.
  • a UE may have a number of different applications and/or data flows (e.g., protocol data unit sessions) that may generate and/or receive traffic or data. Therefore, a UE may be allocated to multiple network slices, e.g., based on different types of traffic that may be transmitted to the UE, different applications running on a UE, or different use cases that the UE may support. Therefore, a UE may be allocated to or allowed to use a plurality of network slices. For example, in terms of downlink data, a 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, a 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.
  • a network entity e.g., by a network entity
  • a slice identifier may be or may include, for example, a single Network Slice Selection Assistance Information (S-NSSAI) , which may identify a slice.
  • S-NSSAI Network Slice Selection Assistance Information
  • a 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) .
  • a UE may receive information identifying a slice-specific paging cycle for each of one or more network slices allowed for the UE.
  • a UE may receive, such as from a core network entity (e.g., confirmation of) a paging cycle for each of one or more network slices allowed for the UE.
  • This information of paging cycle (s) may, for example, 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) .
  • a UE may be allowed by a core network entity to use a first network slice that has a first slice-specific paging cycle of 32 RFs, allowed to use a second network slice that has a second slice-specific paging cycle of 64 RFs, and allowed to use a third network slice that has a third slice-specific paging cycle of 128 RFs.
  • the UE may receive from a core network entity information identifying (or confirming) the paging cycles of 32 RFs, 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 minimum slice-specific paging cycle among the one or more slice-specific paging cycles for the UE. For example, the UE may determine, among the paging cycles for the three slices allowed for the UE, which of the slice-specific paging cycles is the minimum (e.g., least or shortest) slice-specific paging cycle among those slices allowed for the UE. In this example, the UE may compare the three paging cycles to each other in order to determine that that the paging cycle of 32 RFs (e.g., for the first network slice allowed for the UE) is the minimum (or least or shortest) among those three network slices allowed for the UE.
  • 32 RFs e.g., for the first network slice allowed for the UE
  • the UE may receive a paging message based on the minimum slice-specific paging cycle. For example, the UE may receive a paging message at a paging frame that may be determined based on the 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 every 32 nd radio frame for paging messages (e.g., with a minimum paging cycle of 32 RFs) , e.g., in order to receive paging messages with respect to any of the three slices allowed for the UE.
  • paging messages e.g., with a minimum paging cycle of 32 RFs
  • the BS may be aware of the minimum paging cycle for a UE, and may send RAN paging messages for any of the slices at the minimum paging cycle.
  • the UE may monitor paging messages for all three allowed slices if the UE monitors paging messages according to the minimum paging cycle among the plurality of slices allowed for the UE.
  • a UE may have a cell-specific paging cycle, and/or a UE-specific paging cycle, which are not specific to any slices.
  • the UE may use a minimum paging cycle among all the paging cycles assigned to or associated with the UE, e.g., the UE may use (e.g., monitor paging messages according to) the minimum paging cycle for the UE among the cell-specific, UE-specific and slice-specific paging cycles.
  • the UE may use (e.g., may monitor paging messages according to) the minimum slice-specific paging cycle among the one or more slices allowed or approved for the UE.
  • the UE may also receive data based on the paging message. For example, if the received slice-specific paging message includes the identifier (e.g., TMSI) for the UE, then the UE may receive data based on the paging message by initiating a service request procedure to obtain the data in response to receiving the paging message that identifies the UE/user device.
  • the identifier e.g., TMSI
  • the UE may send to the core network entity a first message including a slice identifier or a group of slice identifiers for one or more slices and a proposed paging cycle for each of the one or more network slices, and receive, by the UE from the core network entity, a second message indicating a slice identifier and a paging cycle associated with each of one or more network slices that are allowed or approved for the UE.
  • 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 either a registration procedure and/or a PDU session establishment procedure with a core network entity.
  • the 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 to a core network entity, a registration request to register with the network for one or more network slices, the registration request including a slice identifier or a group or vector of slice identifiers for 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 indicating a slice identifier and a paging cycle associated with each of one or more network slices allowed for the UE.
  • the 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 to a core network entity, a protocol data unit PDU session establishment request to request establishment of a PDU session associated with a network slice, the PDU session establishment request including a PDU session identifier that identifies a PDU session, a slice identifier that identifies a network slice associated with or assigned to the PDU session, and a proposed paging cycle for the PDU session; and receiving, by the UE from the core network entity, a PDU session establishment response including at least a slice identifier for the network slice that is associated with or assigned to the PDU session and a paging cycle for the PDU session for the UE.
  • a core network entity may determine or confirm one or more slice-specific paging cycles for one or more network slices allowed or approved for the UE.
  • the core network entity may receive requests to use and determine or assign a paging cycle for a slice from each ora plurality of UEs, including a different proposed paging cycle from each of multiple UEs for the same network slice.
  • the core network entity e.g., AMF
  • a core network entity may receive a registration request or PDU session establishment request, or other message from the UE, that includes a proposed paging cycle for a slice, and the core network entity may send a reply to the UE with a new or different proposed paging cycle for the slice.
  • the core network entity and the UE may negotiate the paging cycle for a slice, for example.
  • the core network entity may determine and inform the UE of a slice-specific paging cycle for one or more network slices that are approved or allowed for the UE.
  • the core network entity e.g., AMF
  • a BS e.g., via a core network paging message
  • the core network entity may determine a minimum slice-specific paging cycle for the slices allowed for the UE, and then may include the minimum slice-specific paging cycle for the UE in a core network paging message sent to a BS. In this manner, the core network may notify the BS of the minimum paging cycle for the UE (e.g., which may inform the BS the timing or cycle for sending radio access network (RAN) paging messages to the UE, since the UE will be monitoring the downlink control channel for paging messages according to this same minimum slice-specific paging cycle as well) .
  • RAN radio access network
  • the core network entity may send each (all) of the slice-specific paging cycles for the UE, e.g., send each slice-specific paging cycle for slices allowed for the UE to the BS.
  • the BS may then determine a minimum slice-specific paging cycle for the slices allowed for the UE.
  • example implementation 1) allows the core network entity to determine the minimum slice-specific paging cycle for the UE and then provide this information to the BS.
  • implementation 2) allows the BS to determine the minimum slice-specific paging cycle for the UE among the one or more received paging cycles for the UE.
  • the core network entity may send a core network paging message to the BS that includes a, a slice-specific paging cycle that is 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 with respect to the PDU session.
  • the core network entity may notify the BS of the slice-specific paging cycle for the PDU session (and slice) that triggered the paging of the UE (e.g., paging cycle of the PDU session and slice for which there is data at the core network for delivery to the UE) .
  • the BS may receive from a core network entity, a core network paging message that includes an identifier for a UE and a slice-specific paging cycle for one or more network slices that are 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 that are allowed for the UE.
  • the selected paging cycle may, for example, be either the only paging cycle that is received by the BS from the core network, such as either the minimum paging cycle or paging cycle for PDU session that triggered the paging; or the BS may select a paging cycle by determining a minimum paging cycle based on multiple paging cycles received from the core network entity. And, the BS may send a radio access network (RAN) paging message to the UE based on the selected paging cycle for the UE.
  • RAN radio access network
  • the BS may send a RAN paging message to the UE in accordance with the selected paging cycle for the UE, e.g., which may be (in accordance with the timing for) the minimum paging cycle for the UE, or a PDU session paging cycle for which data is to be delivered.
  • the selected paging cycle for the UE e.g., which may be (in accordance with the timing for) the minimum paging cycle for the UE, or a PDU session paging cycle for which data is to be delivered.
  • the BS receiving from a core network entity, a core network paging message that includes an identifier for a UE/user device and a slice-specific paging cycle for one or more network slices may include the BS receiving, from a core network entity, a core network paging message that includes an identifier for the UE, a minimum slice-specific paging cycle, among a plurality of slice specific paging cycles for network slices that are allowed for the UE; and wherein the selecting, by the BS (base station) , a paging cycle for the UE includes the BS selecting the received minimum slice-specific paging cycle for the UE.
  • the BS receiving from a core network entity, a core network paging message that includes an identifier for a UE/user device and a slice-specific paging cycle for one or more network slices may include the BS receiving a core network paging message that includes an identifier for a UE, a slice-specific paging cycle for each of a plurality of network slices that are allowed for the UE/user device; and wherein the selecting, by the base station, a paging cycle for the UE may include: selecting, by the BS, a minimum paging cycle for the UE among the slice-specific paging cycle for each of the plurality of network slices that are allowed for the UE.
  • the BS receiving from a core network entity, a core network paging message that includes an identifier for a UE and a slice-specific paging cycle for one or more network slices may include the BS receiving a core network paging message including an identifier for a UE, a slice-specific paging cycle that is 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 with respect to the PDU session; and wherein the selecting, by the base station, a paging cycle for the UE includes selecting, by the base station, the received slice-specific paging cycle that is associated with the PDU session.
  • PDU protocol data unit
  • FIG. 2 is a diagram illustrating of registration procedure between a UE and a core network entity according to an example implementation.
  • a registration procedure may be performed between a UE 210 and a core network entity (e.g., an Access and Mobility Management Function (AMF) 220 at the core network) .
  • the UE 210 may send a registration request including a group of one or more slice (network slice) identifiers (e.g., a NSSAI, which may indicate a 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.
  • the core network entity may send a registration response to the UE 210 that includes a group of one or more slice identifiers (e.g., NSSAI) for one or more slices allowed or approved for the UE, and a (confirmed) slice-specific paging cycle for each of the allowed slices for the UE.
  • slice identifiers e.g., NSSAI
  • FIG. 3 is a diagram illustrating a protocol data unit (PDU) session establishment procedure between a user device (UE) and a core network entity (e.g., AMF) according to an example implementation.
  • UE 210 sends a PDU session establishment request to request establishment of a PDU session associated with a network slice.
  • the PDU establishment request may include a PDU session identifier PDU session ID) that identifies a 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 establishment request) .
  • PDU session ID PDU session ID
  • slice identifier e.g., S-NSSAI
  • the UE 210 receives, from the core network entity (e.g., AMF 220) a PDU session establishment reply/acceptance that indicates the acceptance or establishment of the requested PDU session, a slice identifier of the slice associated with the PDU session, and a (e.g., a confirmed) slice-specific paging cycle for the slice and associated PDU session.
  • the core network entity e.g., AMF 220
  • a PDU session establishment reply/acceptance that indicates the acceptance or establishment of the requested PDU session
  • a slice identifier of the slice associated with the PDU session e.g., a confirmed slice-specific paging cycle for the slice and associated PDU session.
  • a different network slice may be associated with a different paging cycle (e.g., each slice may be associated with a respective paging cycle, which may be different from other slices, depending on the requirements of the service or QoS requirements for 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 during a PDU session establishment procedure between a UE and a core network entity (e.g., AMF) .
  • a core network entity e.g., AMF
  • there may be, two (or more) different example ways to configure a slice with a paging cycle such as, for example: 1) during UE registration, a UE may include a (proposed) paging cycle for each requested slice identifier, within a registration request; and, 2) during a UE PDU session establishment, the UE sends a PDU session establishment request to AMF, including a slice identifier (e.g., S-NSSAI) , a PDU session ID, and a (e.g., proposed) paging cycle for each of one or more requested PDU sessions, where each PDU session may be assigned to or associated with a respective network slice.
  • a slice identifier e.g., S-NSSAI
  • the core network entity or AMF may approve any proposed paging cycle, and may propose a different paging cycle to the UE (e.g., so that a slice, used by many UEs, will have a same paging cycle among the multiple UEs) .
  • the UE may propose a different paging cycle to replace the earlier agreed paging cycle for a slice, for example. For example, a first procedure of UE registration may be performed, followed by a second procedure of PDU session establishment.
  • the slice-specific paging cycle may, e.g., subsequently, be communicated to the gNB/BS from the core network entity (e.g., AMF) in a core network paging message (see FIG. 4) .
  • a slice-specific paging cycle may be configured for each approved or allowed slice for a UE, e.g., in addition to an existing UE- specific paging cycle.
  • the UE may negotiate with AMF/core network entity the paging cycle for each slice it requested.
  • the UE and AMF may exchange paging cycle configurations (paging cycle values) and decide whether to apply the UE specific paging cycle or the slice-specific paging cycle via registration procedure or/and PDU session setup procedure, e.g., whichever paging cycle is shorter or a minimum, for example.
  • the slice-specific paging cycle may typically (for example) be applied (or used for paging and monitoring of paging messages) instead of the UE specific paging cycle, for example.
  • the network may then provide (or confirm) the paging cycle for each slice identified by S-NSSAI in the allowed NSSAI in Registration Response 240 (FIG. 2) .
  • the paging cycle for the slice supported by a PDU session may be configured when the PDU session is setup.
  • FIG. 4 is a diagram illustrating operation of a paging procedure based on a slice-specific paging cycle according to an example implementation.
  • a BS (gNB) 410 is in communication with a UE 210 and core network entity (or AMF) 220.
  • AMF 220 may send a core network paging message to BS 410, including an identifier (e.g., TMSI) for the UE 210, and at least one slice-specific paging cycle.
  • TMSI identifier
  • AMF 220 may determine and then provide a minimum slice-specific paging cycle among the slice (s) allowed for the UE; 2) the AMF 22 0 (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 BS may then determine the minimum paging cycle among the received paging cycles for the UE) ; and 3) AMF 220 (or core network entity) may send a slice-specific paging cycle that is associated with a network slice and a PDU session, e.g., the paging cycle for the PDU data session (and associated slice) that caused or triggered the paging of the UE 210.
  • the BS may select (or determine) a paging cycle for the UE based on the received paging cycle (s) for the UE. For example, if only one paging cycle (e.g., minimum paging cycle or the paging cycle for the PDU session and slice that triggered or cause the paging of the UE 210) is received by the BS 410 for the UE 210 at 430, then this one received paging cycle will be selected by BS 410 for use for paging the UE.
  • a paging cycle e.g., minimum paging cycle or the paging cycle for the PDU session and slice that triggered or cause the paging of the UE 2
  • the BS 410 may determine a minimum paging cycle among these received paging cycles for the UE, and then may select this minimum paging cycle for use in paging the UE, for example (e.g., RAN paging messages may be sent by BS 410 to UE 210 based on timing of the selected paging cycle) .
  • the UE similarly determines a minimum paging cycle among the paging cycles for the one or more approved slices for the UE, and then the UE 210 monitors or listens for paging messages according to such minimum paging cycle for the UE.
  • BS 410 sends a RAN paging message to the UE 210 during a radio frame in accordance with the selected paging cycle for the UE.
  • the UE 210 may receive the RAN paging message, and may then obtain the data if its UE identifier is provided within the RAN paging message.
  • the core network paging message 420 from AMF 220 may provide or include a paging cycle for each slice supported by the UE.
  • the BS 410 may decide the paging cycle by choosing the minimum paging cycle from the paging cycles of the slices supported by the UE, and then page the UE 210 from the paging occasion derived accordingly (page during a paging occasion during a radio frame in accordance with minimum paging cycle for UE, for example) .
  • the AMF 220 may include a single paging cycle in core network paging message 420, where the single paging cycle indicated in the core network paging message may be, for example, either: 1) The minimum paging cycle among all the paging cycles of the slices supported by the UE; or 2) The paging cycle of the slice supported by the PDU session that the UE needs to use for receiving the MT data.
  • the UE may typically select the minimum paging cycle from the paging cycle of each slice allowed for the UE, and the UE monitors/listens for the RAN paging message (s) 450 on the paging occasion derived in accordance with the minimum paging cycle for the UE. For example, if UE has 3 PDU sessions (and a slice and paging cycle associated with each of these PDU session) , there may be at most 3 different paging cycles. For example:
  • PDU session 1 slice 1, paging cycle 128 rf (128 radio frames)
  • PDU session 2 slice 2, paging cycle 64rf
  • PDU session 3 slice 1, paging cycle 32rf
  • the paging cycle for the UE may be selected as the minimum paging cycle of all the slices.
  • the UE will apply paging cycle of 32rfs (32 radio frames) in this illustrative example.
  • a slice-specific paging cycle may be applied by a network and UE, for each of one or more network slices, where each slice-specific paging cycle may be tailored to or adjusted to meet the specific paging requirements of the slice (or to meet the performance requirements of the application or use case assigned to or associate with the slice) .
  • paging performance may be improved via a slice-specific paging cycle that may be adapted or for the varying performance requirements of different types of devices or use cases.
  • FIG. 5 is a flow chart illustrating operation of a user device according to an example implementation.
  • Operation 510 includes receiving, by a user device within a wireless network, information identifying a slice-specific paging cycle for one or more network slices allowed for the user device.
  • Operation 520 includes determining, by the user device, a minimum slice-specific paging cycle among the one or more slice-specific paging cycles.
  • operation 530 includes receiving, by the user device, a paging message based on the minimum slice-specific paging cycle.
  • Example 2 According to an example implementation of example 1, and further comprising: receiving, by the user device, data based on the paging message.
  • Example 3 According to an example implementation of any of examples 1-2, wherein the paging message includes a paging record that identifies the user device; wherein the receiving, by the user device, data based on the paging message comprises initiating, by the user device, a service request procedure to obtain the data in response to receiving the paging message that identifies the user device.
  • Example 4 According to an example implementation of any of examples 1-3, and further comprising: sending, by the user device to the core network entity, a first message including a slice identifier and a proposed paging cycle for one or more network slices; and receiving, by the user device 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 device.
  • Example 5 According to an example implementation of any of examples 1-4, wherein the receiving, by the user device within a wireless network, information identifying a slice-specific paging cycle for one or more network slices allowed for the user device comprises: sending, by the user device to a core network entity, a registration request 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 device, a registration response from the core network entity indicating a slice identifier and a paging cycle associated with one or more network slices allowed for the user device.
  • Example 6 According to an example implementation of any of examples 1-5, wherein the receiving, by the user device within a wireless network, information identifying a slice-specific paging cycle for one or more network slices allowed for the user device comprises: sending, by the user device to a core network entity, a protocol data unit PDU session establishment request to request establishment of a PDU session associated with a network slice, the PDU session establishment request including a PDU session identifier that identifies a PDU session, a slice identifier that identifies a network slice associated with or assigned to the PDU session, and a proposed paging cycle for the PDU session; and receiving, by the user device from the core network entity, a PDU session establishment response including at least a slice identifier for the network slice that is associated with or assigned to the PDU session and a paging cycle for the PDU session for the user device.
  • FIG. 6 is a flow chart illustrating operation of a user device according to an example implementation.
  • Operation 610 includes receiving, by a base station in a wireless network from a core network entity, a core network paging message that includes an identifier for a user device and a slice-specific paging cycle for one or more network slices that are allowed for the user device.
  • Operation 620 includes selecting, by the base station, a paging cycle for the user device based on the received slice-specific paging cycle for the one or more network slices that are allowed for the user device.
  • operation 630 includes sending, by the base station, a radio access network (RAN) paging message to the user device based on the selected paging cycle for the user device.
  • RAN radio access network
  • Example 8 According to an example implementation of example 7, wherein the receiving comprises: receiving, by a base station in a wireless network from a core network entity, a core network paging message that includes an identifier for a user device, a minimum slice-specific paging cycle, among a plurality of slice specific paging cycles for network slices that are allowed for the user device; and wherein the selecting, by the base station, a paging cycle for the user device comprises: selecting the received minimum slice-specific paging cycle for the user device.
  • Example 9 According to an example implementation of any of examples 7-8, wherein the receiving comprises: receiving, by a base station in a wireless network from a core network entity, a core network paging message that includes an identifier for a user device, a slice-specific paging cycle for each of a plurality of network slices that are allowed for the user device; and wherein the selecting, by the base station, a paging cycle for the user device comprises: selecting, by the base station, a minimum paging cycle for the user device among the slice-specific paging cycle for each of the plurality of network slices that are allowed for the user device.
  • Example 10 According to an example implementation of any of examples 7-9, wherein the receiving comprises: receiving, by a base station in a wireless network from a core network entity, a core network paging message including an identifier for a user device, a slice-specific paging cycle that is 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 device with respect to the PDU session; and wherein the selecting, by the base station, a paging cycle for the user device comprises: selecting, by the base station, the received slice-specific paging cycle that is associated with the PDU session.
  • PDU protocol data unit
  • Example 11 According to an example implementation of any of examples 7-10, and further comprising: sending, by the base station, data to the user device in response to a service request procedure initiated by the user device in response to the RAN paging message.
  • FIG. 7 is a flow chart illustrating operation of a core network entity according to an example implementation.
  • Operation 710 includes sending, by a core network entity to a base station in a wireless network, a core network paging message that includes an identifier for a user device and a slice-specific paging cycle for one or more network slices that are allowed for the user device.
  • Example 13 According to an 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 that are allowed for the user device; and sending, by a core network entity to a base station in a wireless network, a core network paging message that includes an identifier for a user device, and the minimum slice-specific paging cycle, among a plurality of slice specific paging cycles for network slices that are allowed for the user device.
  • Example 14 According to an example implementation of any of examples 12-13, wherein the sending comprises: sending, by a core network entity to a base station in a wireless network, a core network paging message that includes an identifier for a user device, and a slice-specific paging cycle for each of a plurality of network slices that are allowed for the user device.
  • Example 15 According to an example implementation of any of examples 12-14, wherein the sending comprises: sending, by a core network entity to a base station in a wireless network, a core network paging message including an identifier for a user device, a slice-specific paging cycle that is 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 device with respect to the PDU session.
  • a core network paging message including an identifier for a user device, a slice-specific paging cycle that is 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 device with respect to the PDU session.
  • PDU protocol data unit
  • Example 16 According to an example implementation of any of examples 12-15, and further comprising: receiving, by the core network entity from the user device, a first message including a slice identifier and a proposed paging cycle for one or more network slices; and sending, by the core network entity to the user device, a second message indicating a slice identifier and a paging cycle associated with one or more network slices allowed or approved for the user device.
  • Example 17 According to an example implementation of any of examples 12-16, wherein the first message comprises at least one of the following: a registration request; and a protocol data unit (PDU) session establishment request; and wherein the second message comprises at least one of the following: a registration response; and a PDU session establishment response.
  • PDU protocol data unit
  • Example 18 An apparatus comprising means for performing a 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 a method of any of examples 1-17.
  • Example 20 An apparatus comprising a computer program product including 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 a method of any of examples 1-17.
  • FIG. 8 is a block diagram of a wireless station (e.g., AP, BS, eNB, UE or user device) 1000 according to an example implementation.
  • the 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 transmission and receptions of signals, and a memory 1006 to store data and/or instructions.
  • 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.
  • Processor 1004 which may be a baseband processor, for example, 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 the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 1002, for example) .
  • 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 that executes software or firmware, and/or any combination of these.
  • processor 1004 and transceiver 1002 together may be considered as a wireless transmitter/receiver system, for example.
  • 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., display, keypad) , and/or may execute software for one or more applications that may be provided on wireless station 1000, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
  • a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 1004, or other controller or processor, performing one or more of the functions or tasks described above.
  • RF or wireless transceiver (s) 1002A/1002B may receive signals or data and/or transmit or send signals or data.
  • Processor 1004 (and possibly transceivers 1002A/1002B) may control the RF or wireless transceiver 1002A or 1002B to receive, send, broadcast or transmit signals or data.
  • 5G Another example of a suitable communications system is the 5G concept. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input -multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept) , including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input -multiple output
  • NFV network functions virtualization
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized.
  • radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be 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, a 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 a non-transitory medium.
  • Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software implementations that are downloadable via the Internet or other network (s) , either wired networks and/or wireless networks.
  • implementations may be provided via machine type communications (MTC) , and also via an Internet of Things (IOT) .
  • MTC machine type communications
  • IOT Internet of Things
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • implementations of the various techniques described herein may use a cyber-physical system (CPS) (asystem of collaborating computational elements controlling physical entities) .
  • CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, ... ) embedded in physical objects at different locations.
  • ICT devices sensors, actuators, processors microcontrollers, ...
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various implementations of techniques described herein may be provided via one or more of these teclmologies.
  • 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 part of it 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 computer program portions 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) .
  • FPGA field programmable gate array
  • 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 chipset.
  • 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.
  • a computer also may 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, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
  • the processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
  • 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.
  • a display device e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor
  • a user interface such as a keyboard and a pointing device, e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., 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 be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes 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.
  • 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) , e.g., the Internet.
  • LAN local area network
  • WAN wide area network

Landscapes

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

Abstract

L'invention concerne une technique consistant à recevoir, en provenance d'un dispositif utilisateur dans un réseau sans fil, des informations identifiant un cycle de radiomessagerie spécifique à une tranche pour une ou plusieurs tranches de réseau autorisées pour le dispositif utilisateur; à déterminer, par le dispositif utilisateur, un cycle de radiomessagerie spécifique à une tranche minimal parmi lesdits cycles de radiomessagerie spécifiques à une tranche; et à recevoir, en provenant du dispositif utilisateur, un message de radiomessagerie sur la base du cycle de radiomessagerie spécifique à une tranche minimal.
PCT/CN2017/097108 2017-08-11 2017-08-11 Cycles de radiomessagerie spécifiques à une tranche de réseau pour réseaux sans fil Ceased WO2019028838A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201780095147.5A CN111108785B (zh) 2017-08-11 2017-08-11 用于无线网络的网络切片特定寻呼周期
PCT/CN2017/097108 WO2019028838A1 (fr) 2017-08-11 2017-08-11 Cycles de radiomessagerie spécifiques à une tranche de réseau pour réseaux sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/097108 WO2019028838A1 (fr) 2017-08-11 2017-08-11 Cycles de radiomessagerie spécifiques à une tranche de réseau pour réseaux sans fil

Publications (1)

Publication Number Publication Date
WO2019028838A1 true WO2019028838A1 (fr) 2019-02-14

Family

ID=65273151

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/097108 Ceased WO2019028838A1 (fr) 2017-08-11 2017-08-11 Cycles de radiomessagerie spécifiques à une tranche de réseau pour réseaux sans fil

Country Status (2)

Country Link
CN (1) CN111108785B (fr)
WO (1) WO2019028838A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220408333A1 (en) * 2020-02-27 2022-12-22 Ofinno, Llc Session Management for Edge Computing

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022126457A1 (fr) * 2020-12-16 2022-06-23 Oppo广东移动通信有限公司 Procédé de radiomessagerie, ainsi qu'équipement utilisateur et dispositif de réseau
WO2022165630A1 (fr) * 2021-02-02 2022-08-11 Qualcomm Incorporated Signalisation pour indiquer des informations de tranche voulue en radiorecherche

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160381146A1 (en) * 2015-06-29 2016-12-29 Huawei Technologies Co., Ltd. System and method for connectivity management
CN106792739A (zh) * 2016-11-17 2017-05-31 北京邮电大学 网络切片方法、装置和设备
WO2017118489A1 (fr) * 2016-01-08 2017-07-13 Telefonaktiebolaget Lm Ericsson (Publ) Nœuds d'accès radio, et procédés mis en œuvre dans ceux-ci
CN106993329A (zh) * 2016-01-21 2017-07-28 中兴通讯股份有限公司 寻呼的方法、装置及系统
WO2017135857A1 (fr) * 2016-02-05 2017-08-10 Telefonaktiebolaget Lm Ericsson (Publ) Nœud de réseau central, nœud de réseau radio, dispositif sans fil et procédés exécutés dans ceux-ci

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8971933B2 (en) * 2008-11-18 2015-03-03 Qualcomm Incorporated Method and apparatus for determining DRX cycle used for paging
CN102413566B (zh) * 2010-09-25 2014-04-02 电信科学技术研究院 一种寻呼方法及装置
CN104125612B (zh) * 2013-04-28 2019-09-24 中兴通讯股份有限公司 非连续接收周期同步方法，系统和设备
KR102513274B1 (ko) * 2015-08-21 2023-03-24 삼성전자주식회사 무선 통신 시스템에서 복합 재전송을 수행하는 방법 및 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160381146A1 (en) * 2015-06-29 2016-12-29 Huawei Technologies Co., Ltd. System and method for connectivity management
WO2017118489A1 (fr) * 2016-01-08 2017-07-13 Telefonaktiebolaget Lm Ericsson (Publ) Nœuds d'accès radio, et procédés mis en œuvre dans ceux-ci
CN106993329A (zh) * 2016-01-21 2017-07-28 中兴通讯股份有限公司 寻呼的方法、装置及系统
WO2017135857A1 (fr) * 2016-02-05 2017-08-10 Telefonaktiebolaget Lm Ericsson (Publ) Nœud de réseau central, nœud de réseau radio, dispositif sans fil et procédés exécutés dans ceux-ci
CN106792739A (zh) * 2016-11-17 2017-05-31 北京邮电大学 网络切片方法、装置和设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220408333A1 (en) * 2020-02-27 2022-12-22 Ofinno, Llc Session Management for Edge Computing
US12389296B2 (en) * 2020-02-27 2025-08-12 Ofinno, Llc Session management for edge computing

Also Published As

Publication number Publication date
CN111108785A (zh) 2020-05-05
CN111108785B (zh) 2022-11-25

Similar Documents

Publication Publication Date Title
EP3827619B1 (fr) Transmission de contraintes de tranchage de réseau dans des réseaux sans fil
US11071088B2 (en) Network slice-specific paging for wireless networks
US10966271B2 (en) Connection setup recovery for wireless networks
CN111869273B (zh) 用于监视寻呼消息的方法和设备
US20240214879A1 (en) Physical cell identity collision resolution for wireless networks
WO2020135019A1 (fr) Procédé de communications et dispositif associé
EP3925130B1 (fr) Appareil, procédé et programme informatique
CN115152282A (zh) 侧链无线通信的同步优先级
US20240023186A1 (en) Network method for small data transmission termination and signaling
CN114071615B (zh) 小区切换方法和终端
US20200196234A1 (en) Handling ue context upon inactivity
US11582631B2 (en) User equipment indication for adaptive scheduling restrictions
EP3790323B1 (fr) Déclenchement d'informations d'état de canal en dehors du temps actif
US20220322238A1 (en) Exploitation of transmitter (tx) power for each band dual up-link (ul) carrier aggregation (ca)
CN111108785B (zh) 用于无线网络的网络切片特定寻呼周期
WO2019030576A1 (fr) Procédé, dispositif et support lisible par ordinateur pour une communication de dispositif à dispositif (d2d)
WO2015197121A1 (fr) Déchargement d'une authentification de nœud sans fil avec un réseau central
EP4240100A1 (fr) Restauration de service de diffusion pour service de diffusion/multidiffusion lors d'une défaillance ou d'un redémarrage d'un noeud d'accès radio
WO2024165342A1 (fr) Gestion de reconfiguration conditionnelle pendant une opération musim dans des réseaux sans fil
US20240236793A1 (en) Bi-layered mobility for ng-ran
US20240406833A1 (en) Scg-maintained conditional handover in dual connectivity with scg failure
US20240357434A1 (en) Efficient handover for point-to-multipoint communication
US12506577B2 (en) Enhanced use of deactivated secondary cell group in dual-RX/dual-TX MUSIM operation
US20240113824A1 (en) Enhanced use of deactivated secondary cell group in dual-rx/dual-tx musim operation
WO2024093394A1 (fr) Récupération d'informations système

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17921413

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17921413

Country of ref document: EP

Kind code of ref document: A1