WO2022098284A1 - Récupération de couverture dans des dispositifs sans fil à capacité réduite - Google Patents

Récupération de couverture dans des dispositifs sans fil à capacité réduite Download PDF

Info

Publication number
WO2022098284A1
WO2022098284A1 PCT/SE2021/051100 SE2021051100W WO2022098284A1 WO 2022098284 A1 WO2022098284 A1 WO 2022098284A1 SE 2021051100 W SE2021051100 W SE 2021051100W WO 2022098284 A1 WO2022098284 A1 WO 2022098284A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless device
message
reduced capability
network node
msg4
Prior art date
Application number
PCT/SE2021/051100
Other languages
English (en)
Inventor
Yi-Pin Eric Wang
Saeedeh MOLOUDI
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022098284A1 publication Critical patent/WO2022098284A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present disclosure relates to wireless communications, and in particular, to coverage recovery solutions for reduced capability wireless devices.
  • the Third Generation Partnership Project (3 GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems.
  • 4G Fourth Generation
  • 5G Fifth Generation
  • Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs.
  • FIG. 1 illustrates a 4-step contention-based random access (CBRA) procedure used in NR.
  • CBRA contention-based random access
  • Step 1 The WD initiates the random access procedure by transmitting a random-access preamble (also referred to as message 1 or Msgl) to a network node using a physical random-access channel (PRACH).
  • a random-access preamble also referred to as message 1 or Msgl
  • PRACH physical random-access channel
  • Step 2 The network node responds to the preamble by transmitting a random-access response (also referred to as message 2 or Msg2) to the WD.
  • the random access-response (RAR) includes an uplink grant that schedules a physical uplink shared channel (PUSCH).
  • Step 3 After receiving the RAR, the WD transmits a PUSCH transmission to the network node in accordance with the uplink grant.
  • This PUSCH transmission is also referred to as message 3 or Msg3.
  • Step 4 The network node responds to the PUSCH transmission by transmitting a contention resolution message (also referred to as message 4 or Msg4) to the WD.
  • a contention resolution message also referred to as message 4 or Msg4
  • ultra-reliable low latency communications was introduced in 3 GPP Release 15 for both LTE and NR.
  • NR URLLC is further enhanced in 3 GPP Release 16 within the enhanced URLLC (eURLLC) and Industrial Internet of Things (loT) work items.
  • eURLLC enhanced URLLC
  • LTE-MTC long term evolution for machine-type communication
  • NB-IoT narrowband Internet-of-Things
  • LTE-MTC long term evolution for machine-type communication
  • LTE-MTC long term evolution for machine-type communication
  • NR New Radio
  • 3 GPP Release 15 3 GPP Release 15 and focused mainly on enhanced mobile broadband (eMBB) and cMTC.
  • eMBB enhanced mobile broadband
  • 3GPP Release 17 an NR WD type with lower capabilities may be introduced since it is supported and proposed by many companies.
  • the intention is to have a reduced capability version of NR devices, i.e., Reduced capability NR devices (NR-RedCap), which is middle-end, filling the gap between eMBB NR and NB- loT/LTE-M. This is to provide more efficient inband operation with URLLC in industrial use cases.
  • NR-RedCap Reduced capability NR devices
  • NR-RedCap Reduced capability NR device
  • IMT International Mobile Telecommunications
  • a first aspect provides embodiments of a method implemented in a network node.
  • the method comprises receiving a message from a wireless device as part of a random access procedure, and transmitting a Msg4 message to the wireless device as part of the random access procedure.
  • the Msg4 message is transmitted with lower effective code rate if the received message indicates that the wireless device is a reduced capability wireless device than if the received message does not indicate that the wireless device is a reduced capability wireless device.
  • a second aspect provides embodiments of method implemented in a wireless device.
  • the method comprises transmitting a message to a network node as part of a random access procedure.
  • the transmitted message indicates whether the wireless device is a reduced capability wireless device.
  • the method also comprises receiving a Msg4 message from the network node as part of the random access procedure.
  • the Msg4 message is received with lower effective code rate if the transmitted message indicates that the wireless device is a reduced capability wireless device than if the transmitted message does not indicate that the wireless device is a reduced capability wireless device.
  • FIG. 1 illustrates a random access procedure
  • FIG. 2 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure
  • FIG. 3 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 4 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure
  • FIG. 5 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure
  • FIG. 6 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure
  • FIG. 7 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart of an exemplary process in a network node for coverage recovery solutions for RedCap-Msg4;
  • FIG. 9 is a flowchart of an exemplary process in a network node for coverage recovery.
  • FIG. 10 is a flowchart of an exemplary process in a wireless device for coverage recovery.
  • relational terms such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term, “in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • Coupled may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • network node can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (
  • BS base station
  • wireless device or a user equipment (UE) are used interchangeably.
  • the WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD).
  • the WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.
  • D2D device to device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • Tablet mobile terminals
  • smart phone laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles
  • CPE Customer Premises Equipment
  • LME Customer Premises Equipment
  • NB-IOT Narrowband loT
  • radio network node can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).
  • RNC evolved Node B
  • MCE Multi-cell/multicast Coordination Entity
  • IAB node IAB node
  • relay node access point
  • radio access point radio access point
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes.
  • the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
  • FIG. 2 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14.
  • a 3 GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14.
  • the access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18).
  • Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20.
  • a first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a.
  • a second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b.
  • wireless devices 22 While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.
  • a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16.
  • a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR.
  • WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.
  • the WD 22 may also be in communication with another WD in what is sometimes called sidelink communication. Note that some or all of the WDs 22 may be reduced capability WDs 22.
  • the communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30.
  • the intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network.
  • the intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).
  • the communication system of FIG. 2 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24.
  • the connectivity may be described as an over-the-top (OTT) connection.
  • the host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
  • a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.
  • a network node 16 may for example be configured to include a MCS selector 32 which is configured to select a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD, when the WD is a reduced capability WD.
  • MCS modulation and coding scheme
  • a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10.
  • the host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities.
  • the processing circuitry 42 may include a processor 44 and memory 46.
  • the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read- Only Memory).
  • memory 46 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read- Only Memory).
  • Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24.
  • Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein.
  • the host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24.
  • the instructions may be software associated with the host computer 24.
  • the software 48 may be executable by the processing circuitry 42.
  • the software 48 includes a host application 50.
  • the host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the host application 50 may provide user data which is transmitted using the OTT connection 52.
  • the “user data” may be data and information described herein as implementing the described functionality.
  • the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider.
  • the processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22.
  • the communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22.
  • the hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16.
  • the radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the communication interface 60 may be configured to facilitate a connection 66 to the host computer 24.
  • the connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.
  • the hardware 58 of the network node 16 further includes processing circuitry 68.
  • the processing circuitry 68 may include a processor 70 and a memory 72.
  • the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection.
  • the software 74 may be executable by the processing circuitry 68.
  • the processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16.
  • Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein.
  • the memory 72 is configured to store data, programmatic software code and/or other information described herein.
  • the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16.
  • processing circuitry 68 of the network node 16 may include the MCS selector unit 32 configured to select a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD, when the WD is a reduced capability WD.
  • MCS modulation and coding scheme
  • the communication system 10 further includes the WD 22 already referred to.
  • the WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located.
  • the radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the hardware 80 of the WD 22 further includes processing circuitry 84.
  • the processing circuitry 84 may include a processor 86 and memory 88.
  • the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 88 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22.
  • the software 90 may be executable by the processing circuitry 84.
  • the client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24.
  • an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the client application 92 may receive request data from the host application 50 and provide user data in response to the request data.
  • the OTT connection 52 may transfer both the request data and the user data.
  • the client application 92 may interact with the user to generate the user data that it provides.
  • the processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22.
  • the processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein.
  • the WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22.
  • the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 3 and independently, the surrounding network topology may be that of FIG. 2.
  • the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.
  • the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22.
  • the cellular network also includes the network node 16 with a radio interface 62.
  • the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.
  • the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16.
  • the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.
  • FIGS. 2 and 3 show various “units” such as MCS selector 32 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG. 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 2 and 3, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 3.
  • the host computer 24 provides user data (Block SI 00).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02).
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04).
  • the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06).
  • the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).
  • FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3.
  • the host computer 24 provides user data (Block SI 10).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50.
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12).
  • the transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the WD 22 receives the user data carried in the transmission (Block SI 14).
  • FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3.
  • the WD 22 receives input data provided by the host computer 24 (Block SI 16).
  • the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18).
  • the WD 22 provides user data (Block SI 20).
  • the WD provides the user data by executing a client application, such as, for example, client application 92 (Block SI 22).
  • client application 92 may further consider user input received from the user.
  • the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block SI 24).
  • the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 26).
  • FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 2, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 2 and 3.
  • the network node 16 receives user data from the WD 22 (Block SI 28).
  • the network node 16 initiates transmission of the received user data to the host computer 24 (Block SI 30).
  • the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).
  • RedCap reduced capability wireless devices
  • WD reduced capability wireless devices
  • coverage loss The impact of the complexity reduction is not identical on different physical channels, so the levels of the needed coverage recovery are likely different for different physical channels. The levels of the needed coverage recovery are also likely different for different deployment scenarios.
  • the impact of the complexity reduction may be more considerable on coverage of the downlink (DL) channels and messages than that of the uplink (UL) channels.
  • This DL coverage situation may become even more challenging in a micro-cell where the NR base station (gNB) power level is much lower compared to a macro cell.
  • gNB NR base station
  • DL coverage is more challenging in an FR2 band due to a lower network node power level that is allowed.
  • Msg4 is one of the DL random-access procedure messages whose coverage may be considerably affected by device complexity reduction and potentially can be a coverage limiting channel.
  • RedCap-Msg4 Reducing the number of the WD receive antennas for RedCap WDs, may have a considerable impact on the coverage of Msg4 for RedCap WDs (also referred to herein as RedCap-Msg4).
  • RedCap-Msg4 also referred to herein as RedCap-Msg4
  • Some embodiments advantageously provide methods, systems, and apparatuses for coverage recovery solutions for Msg4 for RedCap WDs.
  • the network node learns from UL message 1 on the physical random access channel (PRACH) or UL message 3 on the PRACH whether the WD is a RedCap device or NR WD. Therefore, the network node can use this knowledge to enhance the coverage for RedCap-Msg4 in two ways: 1) for RedCap WDs, the network node can use a modulation and coding scheme (MCS) table in which the MCS indices provide smaller spectral efficiencies and code rates and/or 2) the network node can consider new settings between transport block size (TBS) and the number of physical resource blocks (PRBs) for RedCap WDs.
  • MCS modulation and coding scheme
  • the coverage loss due to the complexity reduction can be at least partially compensated for RedCap-Msg4.
  • FIG. 8 is a flowchart of an exemplary process in a network node 16 for coverage recovery solutions for RedCap-Msg4.
  • One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the MCS Selector 32), processor 70, radio interface 62 and-/or communication interface 60.
  • Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to determine when a first message received from the WD on a physical random access channel (PRACH) indicates that the WD is a reduced capability WD (Block SI 34).
  • PRACH physical random access channel
  • the process also includes, when the WD is a reduced capability WD, selecting a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD (Block SI 36).
  • MCS modulation and coding scheme
  • FIG. 9 is a flowchart of an exemplary process in a network node 16 for coverage recovery.
  • the network node receives 901 a message from a wireless device 22 as part of a random access procedure, and transmits 902 a Msg4 message to the wireless device 16 as part of the random access procedure.
  • the Msg4 message is transmitted with lower effective code rate if the received message indicates that the wireless device 22 is a reduced capability wireless device than if the received message does not indicate that the wireless device 22 is a reduced capability wireless device.
  • FIG. 10 is a flowchart of an exemplary process in a wireless device 22 for coverage recovery.
  • the wireless device 22 transmits 1001 a message to a network node 16 as part of a random access procedure.
  • the transmitted message indicates whether the wireless device 22 is a reduced capability wireless device.
  • the wireless device 22 receives 1002 a Msg4 message from the network node 16 as part of the random access procedure.
  • the Msg4 message is received with lower effective code rate if the transmitted message indicates that the wireless device 22 is a reduced capability wireless device than if the transmitted message does not indicate that the wireless device 22 is a reduced capability wireless device.
  • N in f O One of the steps in determining the transport block size (TBS) is computing the so-called intermediate number of information bits, N in f O , as follows: info ⁇ R E R Qm V ’ wherein R, Q m , and v are code rate, modulation order, and the number of transmission layers, respectively.
  • the code rate and modulation order depend on the MCS index and can be looked up from one of the tables 5.1.3.1-1, 5.1.3.1-2 and 5.1.3.1-3 in 3GPP TS 38.214, vl6.3.0, “NR; Physical layer procedures for data (Release 16)”.
  • N RE is the number of the available resource elements in a slot, and can be computed as:
  • NRE min(156, /V R£ ) n PRB
  • n PRB show respectively the number of the subcarriers in a PRB, the number of orthogonal frequency division multiplexed (OFDM) symbols in a slot, the number of resource elements (REs) belong to demodulation reference signal (DM-RS) in a physical resource block (PRB), the overhead and the total number of the available PRBs.
  • OFDM orthogonal frequency division multiplexed
  • the TBS and PRB settings can be adapted to reduce the effective code rate in computing the N in f 0 or, in other words, considering transmitting a smaller number of information bits for a given number of PRBs.
  • a RedCap WD signals its WD type and identification in Msgl or Msg3. Therefore, the network node 16 can use this knowledge to transmit Msg4 to the RedCap WD 22 with smaller effective code rate than that of the NR WDs 22.
  • methods are proposed, based on which the effective code rate can be reduced specifically for transmission of Msg 4 to RedCap WDs 22. Different embodiments can be used separately or in combination with each other.
  • MCS tables 5.1.3.1-1, 5.1.3.1-2 and 5.1.3.1-3 in 3GPP TS 38.214, vl6.3.0, “NR; Physical layer procedures for data (Release 16)” one table may provide lower code rates and lower spectral efficiency.
  • the network node 16 may, after receiving Msg3 and identifying the WD 22 as a RedCap WD 22, consider using MCS indices from the table that provides smaller code rates.
  • a smaller TBS can be assigned to a given MCS and a given number of PRBs, by considering a TBS scaling factor in computing N in f 0 as: info ⁇ RER Qm v -
  • the scaling factor, S can be a constant value for RedCap WDs 22.
  • the scaling factor, S can be considered to be equal to that used in an earlier message, Msg2.
  • the scaling factor, S can be selected from a table, for example from the following Table 5.1.3.2-2 of the 3GPP Technical Standard (TS) 38.214, Release 16.
  • a new scaling factor table can be considered specifically for RedCap WDs 22, including new values for S.
  • the scaling factor, S can be parameterized as a function of the overall number of available PRBs, Ng ⁇ B , and the number of PRBs considered for NR WD Msg4, N ⁇ RB 4 . s an non-limiting example:
  • the network node 16 recognizes the RedCap WDs 22 by Msgl or Msg3. Therefore, the network node 16 can use this knowledge to improve the coverage of RedCap- Msg4.
  • Msgl or Msg3 indicates to the network node 16 that the WD 22 is a reduced capability WD 22 (RedCap WD)
  • the network node 16 can transmit the RedCap-Msg4 with a smaller effective code rate than that of the normal NR WDs 22.
  • a network node 16 is configured to communicate with a wireless device (WD) 22.
  • the network node 16 includes a radio interface 62 and/or processing circuitry 68 configured to: determine when a first message received from the WD 22 on a physical random access channel (PRACH) indicates that the WD 22 is a reduced capability WD 22; and when the WD 22 is a reduced capability WD 22, select a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD 22.
  • PRACH physical random access channel
  • MCS modulation and coding scheme
  • the first message is a New Radio (NR) reduced capability Msgl or Msg3.
  • NR New Radio
  • a transport block size (TBS) is determined based at least in part on the smaller coding rate.
  • the processing circuitry 68 is further configured to assign a TBS to the selected MCS and/or to a number of physical resource blocks (PRBs) based at least in part on a scaling factor used to determine an intermediate number of information bits.
  • the selected MCS having the smaller coding rate is selected for transmission of RedCap-Msg4.
  • a method implemented in a network node 16 includes determining when a first message received from the WD 22 on a physical random access channel (PRACH) indicates that the WD 22 is a reduced capability WD 22, and when the WD 22 is a reduced capability WD 22, selecting a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD 22.
  • the first message is a New Radio (NR) reduced capability Msgl or Msg3.
  • NR New Radio
  • a transport block size (TBS) is determined based at least in part on the smaller coding rate.
  • the method further includes assigning a TBS to the selected MCS and/or to a number of physical resource blocks (PRBs) based at least in part on a scaling factor used to determine an intermediate number of information bits.
  • PRBs physical resource blocks
  • the selected MCS having the smaller coding rate is selected for transmission of RedCap-Msg4.
  • the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
  • a network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: determine when a first message received from the WD on a physical random access channel (PRACH) indicates that the WD is a reduced capability WD; and when the WD is a reduced capability WD, select a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD.
  • PRACH physical random access channel
  • Embodiment A2 The network node of Embodiment Al, wherein the first message is a New Radio (NR) reduced capability Msgl or Msg3.
  • NR New Radio
  • Embodiment A3 The network node of any of Embodiments Al and A2, wherein a transport block size (TBS) is determined based at least in part on the smaller coding rate.
  • TBS transport block size
  • Embodiment A4 The network node of any of Embodiments Al and A2, wherein the processing circuitry is further configured to assign a TBS to the selected MCS and/or to a number of physical resource blocks (PRBs) based at least in part on a scaling factor used to determine an intermediate number of information bits.
  • PRBs physical resource blocks
  • Embodiment A5 The network node of any of Embodiments A1-A4, wherein the selected MCS having the smaller coding rate is selected for transmission of RedCap-Msg4.
  • Embodiment B A method implemented in a network node, the method comprising: determining when a first message received from the WD on a physical random access channel (PRACH) indicates that the WD is a reduced capability WD; and when the WD is a reduced capability WD, selecting a modulation and coding scheme (MCS) having a smaller coding rate and/or spectral efficiency than is selected for a non-reduced capability WD.
  • PRACH physical random access channel
  • MCS modulation and coding scheme
  • Embodiment B2 The method of Embodiment Bl, wherein the first message is a New Radio (NR) reduced capability Msgl or Msg3.
  • NR New Radio
  • Embodiment B3 The method of any of Embodiments Bl and B2, wherein a transport block size (TBS) is determined based at least in part on the smaller coding rate.
  • TBS transport block size
  • Embodiment B4 The method of any of Embodiments Bl and B2, further comprising assigning a TBS to the selected MCS and/or to a number of physical resource blocks (PRBs) based at least in part on a scaling factor used to determine an intermediate number of information bits.
  • PRBs physical resource blocks
  • Embodiment B5. The method of any of Embodiments Bl -B4, wherein the selected MCS having the smaller coding rate is selected for transmission of RedCap-Msg4.

Landscapes

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

Abstract

Un nœud de réseau (16, 16a, 16b, 16c) reçoit un message en provenance d'un dispositif sans fil (22, 22a, 22b) dans le cadre d'une procédure d'accès aléatoire, et transmet un message Msg4 au dispositif sans fil dans le cadre de la procédure d'accès aléatoire. Si le message reçu indique que le dispositif sans fil est un dispositif sans fil à capacité réduite, le message Msg4 est transmis avec un débit de code effectif inférieur à celui utilisé lorsque le message reçu n'indique pas que le dispositif sans fil est un dispositif sans fil à capacité réduite.
PCT/SE2021/051100 2020-11-08 2021-11-04 Récupération de couverture dans des dispositifs sans fil à capacité réduite WO2022098284A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063111034P 2020-11-08 2020-11-08
US63/111,034 2020-11-08

Publications (1)

Publication Number Publication Date
WO2022098284A1 true WO2022098284A1 (fr) 2022-05-12

Family

ID=78621960

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2021/051100 WO2022098284A1 (fr) 2020-11-08 2021-11-04 Récupération de couverture dans des dispositifs sans fil à capacité réduite

Country Status (1)

Country Link
WO (1) WO2022098284A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10291378B1 (en) * 2018-04-05 2019-05-14 Qualcomm Incorporated Signaling of alternative modulation coding schemes

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10291378B1 (en) * 2018-04-05 2019-05-14 Qualcomm Incorporated Signaling of alternative modulation coding schemes

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
"New SID on support of reduced capability NR devices", 3GPP TSG RAN MEETING #86, 9 December 2019 (2019-12-09)
"NR; Physical layer procedures for data (Release 16", 3GPP TS 38.214
3GPP TECHNICAL STANDARD (TS) 38.214
CMCC: "Discussion on identification and access control for Reduced Capability NR", vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 16 October 2020 (2020-10-16), XP051939436, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_103-e/Docs/R1-2008020.zip R1-2008020.docx> [retrieved on 20201016] *
MEDIATEK INC: "Discussion on Modulation Enhancement", vol. RAN WG1, no. Sanya, China; 20180416 - 20180420, 3 April 2018 (2018-04-03), XP051412842, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F92b/Docs/> [retrieved on 20180403] *
QUALCOMM INCORPORATED: "Coverage Recovery for RedCap Devices", vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 26 October 2020 (2020-10-26), XP051947551, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_103-e/Docs/R1-2009310.zip R1-2009310 Coverage Recovery for RedCap Devices.docx> [retrieved on 20201026] *

Similar Documents

Publication Publication Date Title
US20220124788A1 (en) Downlink control information (dci) size handling
US12003309B2 (en) Beam selection priority
EP3759859B1 (fr) Procédés et appareils de signalisation d&#39;un décalage de fréquence dans un réseau tdd nb-iot
US20220272583A1 (en) Long term evolution-m resource reservation using bitmap
US20210359827A1 (en) Multiplexing of iab-node links
US20230122456A1 (en) Early indication for reduced capability devices
US20210360545A1 (en) Methods and apparatuses for synchronization signal (ss) rasters and overlapping bands
US20220322335A1 (en) Overheating configuration in (ng) en-dc
US20210028815A1 (en) Physical uplink shared channel (pusch) frequency hopping allocation
US20230353294A1 (en) Network slicing in cellular systems
JP7382502B2 (ja) 最小スケジューリングオフセットアプリケーション遅延を決定する方法
US20220337365A1 (en) Flexible reconfiguration of the sounding reference signal
US20220377804A1 (en) Sharing of physical random channel resources among different radio access technologies
US20220376858A1 (en) Sharing of sounding reference signals (srs) resources between new radio and long term evolution
WO2022098284A1 (fr) Récupération de couverture dans des dispositifs sans fil à capacité réduite
US11546904B2 (en) Methods and apparatuses for at least reducing an image interference for uplink transmission
EP3714567A1 (fr) Définition de mesure explicite
US20220210826A1 (en) Methods of prioritized two-step radio access channel (rach) in new radio (nr)
US20240223432A1 (en) Methods, network node, wireless device, media for tbs index range interpretation for 16-qam in different deployment modes
US20230300819A1 (en) Uplink scheduling coordination for dual connectivity networking
WO2024172715A1 (fr) Améliorations de positionnement concernant une collision de transmission dans un saut de fréquence srs
WO2024171167A1 (fr) Indication de saut de fréquence srs ul et améliorations de procédure de positionnement
WO2024095042A1 (fr) Estimation d&#39;interférence de liaison descendante (dl) de nouvelle radio (nr) pour partage de spectre
WO2023165744A1 (fr) Adaptation de débit autour de signaux de référence
WO2021191660A1 (fr) Précodage mu-mimo à base de matrice de projection

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: 21807304

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: 21807304

Country of ref document: EP

Kind code of ref document: A1