US10939360B2 - Method, network device and terminal device for remaining minimum system information - Google Patents

Method, network device and terminal device for remaining minimum system information Download PDF

Info

Publication number
US10939360B2
US10939360B2 US16/920,305 US202016920305A US10939360B2 US 10939360 B2 US10939360 B2 US 10939360B2 US 202016920305 A US202016920305 A US 202016920305A US 10939360 B2 US10939360 B2 US 10939360B2
Authority
US
United States
Prior art keywords
rmsi
periodicity
terminal device
repeated
burst set
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.)
Active
Application number
US16/920,305
Other languages
English (en)
Other versions
US20200351759A1 (en
Inventor
Zhipeng Lin
Pål Frenger
Asbjörn Grövlen
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Assigned to TELEFONAKTIEBOLAGET LM ERICSSON (PUBL) reassignment TELEFONAKTIEBOLAGET LM ERICSSON (PUBL) ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: GROVLEN, ASBJORN, LIN, Zhipeng, FRENGER, PAL
Publication of US20200351759A1 publication Critical patent/US20200351759A1/en
Priority to US17/186,010 priority Critical patent/US11696217B2/en
Application granted granted Critical
Publication of US10939360B2 publication Critical patent/US10939360B2/en
Priority to US18/322,583 priority patent/US20230308988A1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
    • H04J11/0069—Cell search, i.e. determining cell identity [cell-ID]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H04W72/1289—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • Embodiments of the disclosure generally relate to wireless communication, and, more particularly, to method, network device and terminal device for remaining minimum system information (RMSI).
  • RMSI remaining minimum system information
  • a terminal device or user equipment In order to connect to a wireless network such as new radio (NR), a terminal device or user equipment (UE) needs to acquire network synchronization signals such as a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) and obtain essential system information (SI).
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • SI essential system information
  • the SI may be included in master information block (MIB) and remaining minimum system information (RMSI).
  • MIB master information block
  • RMSI remaining minimum system information
  • the synchronization signals are used for adjusting the frequency of the UE relative to the network, and for finding proper timing of the received signal from the network.
  • a synchronization and access procedure may involve several signals:
  • a number of (typically rather close in time) SS/PBCH blocks constitute a SS burst set.
  • a SS burst set is transmitted periodically with the periodicity configured in RMSI or by higher layer signaling.
  • a 20 ms SS burst set periodicity is assumed for initial access.
  • FIG. 2 schematically shows SS/PBCH block symbols in slots for different SCSs in NR.
  • each small box denotes an orthogonal frequency division multiplexing (OFDM) symbol.
  • OFDM orthogonal frequency division multiplexing
  • a length of the slot may be different though for the purpose of illustration, it is shown as the same for some SCSs.
  • the number and first symbol indexes for candidate SS/PBCH blocks are determined according to the SCS of SS/PBCH blocks as follows.
  • FIG. 3 schematically shows SS burst set mapping to slots within 5 ms for different SCSs in NR.
  • the candidate SS/PBCH blocks in a half frame are indexed in an ascending order in time from 0 to L ⁇ 1.
  • L the UE shall determine the 3 most significant bit (MSB) bits of the SS/PBCH block index per half frame from higher layer parameter SSB-index-explicit.
  • MSB most significant bit
  • RMSI is carried in physical downlink shared channel (PDSCH) scheduled by physical downlink control channel (PDCCH) and contains the remaining subset of minimum system information, e.g. a bit map of the actually transmitted SS/PBCH blocks.
  • PDSCH physical downlink shared channel
  • PDCCH physical downlink control channel
  • RMSI can have 15 kHz, 30 kHz, 60 kHz or 120 kHz SCS.
  • UE may try to decode a corresponding RMSI to get remaining minimum system information based on the RMSI configurations in PBCH.
  • CORESET RMSI control resource set
  • type 2 and type 3 are only supported in over-6 GHz frequency bands.
  • a kHz in ⁇ A kHz, B kHz ⁇ denotes SSB SCS and B kHz in ⁇ A kHz, B kHz ⁇ denotes RMSI SCS.
  • the CORESET and the PDSCH may be transmitted in the same frequency band range but their frequency bands may be different.
  • a RMSI transmission time interval (TTI) is agreed to be 160 ms, there's no RMSI periodicity indicated in PBCH and a RMSI scheduling periodicity is up to gNB implementation. Therefore, it would be desirable to provide a solution for RMSI in the wireless network such as NR.
  • a method for transmitting remaining minimum system information (RMSI) in a wireless network wherein a physical broadcast channel (PBCH) provides a first subset of minimum system information for random access and configurations for fetching the remaining subset of the minimum system information, the RMSI, a number of synchronization signal (SS)/PBCH blocks constitute a SS burst set which is transmitted periodically with a first periodicity, the method comprises: determining whether a SS/PBCH block in the SS burst set configures the RMSI; in response to that the SS/PBCH block configures the RMSI, transmitting one or more repeated RMSI within the first periodicity.
  • PBCH physical broadcast channel
  • SS synchronization signal
  • a method for receiving remaining minimum system information (RMSI) in a wireless network wherein a physical broadcast channel (PBCH) provides a subset of minimum system information for random access and configurations for fetching the other subset of the minimum system information in the RMSI, a number of synchronization signal (SS)/PBCH blocks constitute a SS burst set which is transmitted periodically with a first periodicity, the method comprises: determining whether a SS/PBCH block in the SS burst set configures the RMSI; in response to that the SS/PBCH block configures the RMSI, receiving one or more repeated RMSI within the first periodicity.
  • RMSI remaining minimum system information
  • a network device comprising: a processor; and a memory, the memory containing instructions executable by the processor, whereby the apparatus is operative to: determine whether a SS/PBCH block in the SS burst set configures the RMSI; in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, transmit one or more repeated RMSI within the first periodicity.
  • a terminal device comprising: a processor; and a memory, the memory containing instructions executable by the processor, whereby the apparatus is operative to: determine whether a SS/PBCH block in the SS burst set configures the RMSI; in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, receive one or more repeated RMSI within the first periodicity.
  • the computer program product comprises instructions which when executed by at least one processor, cause the at least one processor to determine whether a SS/PBCH block in the SS burst set configures the RMSI; in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, transmit one or more repeated RMSI within the first periodicity.
  • a computer readable storage medium comprises instructions which when executed by at least one processor, cause the at least one processor to determine whether a SS/PBCH block in the SS burst set configures the RMSI; in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, transmit one or more repeated RMSI within the first periodicity.
  • the computer program product comprises instructions which when executed by at least one processor, cause the at least one processor to determine whether a SS/PBCH block in the SS burst set configures the RMSI; in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, receive one or more repeated RMSI within the first periodicity.
  • a computer readable storage medium comprises instructions which when executed by at least one processor, cause the at least one processor to determine whether a SS/PBCH block in the SS burst set configures the RMSI; in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, receive one or more repeated RMSI within the first periodicity.
  • a method implemented in a communication system including a host computer, a network device and a terminal device, the method comprising: at the host computer, receiving user data originating from a transmission from a terminal device to a network device, wherein the network device is operative to configured to perform the method as described above, wherein the terminal device is operative to configured to perform the method as described above.
  • a method implemented in a communication system including a host computer, a network device and a terminal device, the method comprising: at the host computer, initiating a transmission carrying user data to the terminal device via the network device, wherein the network device is operative to configured to perform the method as described above, wherein the terminal device is operative to configured to perform the method as described above.
  • a communication system including a host computer comprising: a processing circuitry configured to provide user data; and a communication interface configured to receive user data originating from a transmission from a terminal device to a network device, wherein the network device comprises a processor and a memory, the memory containing instructions executable by the processor, whereby the network device is operative to configured to perform the method as described above, wherein the terminal device comprises a processor and a memory, the memory containing instructions executable by the processor, whereby the terminal device is operative to configured to perform the method as described above.
  • a communication system including a host computer comprising: a processing circuitry configured to provide user data; and a communication interface configured to initiate a transmission carrying user data to a terminal device via a network device, wherein the network device comprises a processor and a memory, the memory containing instructions executable by the processor, whereby the network device is operative to configured to perform the method as described above, wherein the terminal device comprises a processor and a memory, the memory containing instructions executable by the processor, whereby the terminal device is operative to configured to perform the method as described above.
  • a method for transmitting RMSI comprising: transmitting PDCCH scheduling information; determining whether a slot-based or non-slot-based scheduling on PDSCH is predefined based on the transmitted PDCCH scheduling information, wherein the RMSI is to be carried in the PDSCH; determining location of the PDSCH according to the determination of a slot-based or non-slot-based scheduling on PDSCH by which the RMSI to be carried, and multiplexing pattern between SS/PBCH block and CORESET; and transmitting the RMSI through the PDSCH.
  • a corresponding apparatus is also provided.
  • a method for receiving RMSI comprising: receiving PDCCH scheduling information; determining whether a slot-based or non-slot-based scheduling on PDSCH is predefined based on the received PDCCH scheduling information, wherein the RMSI is to be carried in the PDSCH; determining location of the PDSCH according to the determination of a slot-based or non-slot-based scheduling on PDSCH by which the RMSI to be carried, and multiplexing pattern between SS/PBCH block and CORESET; and monitoring location of PDSCH carrying the RMSI.
  • a corresponding apparatus is also provided.
  • FIG. 1 depicts a schematic communication system, in which some embodiments of the present disclosure can be implemented
  • FIG. 2 schematically shows SS/PBCH block symbols in slots for different SCSs in NR;
  • FIG. 3 schematically shows SS burst set mapping to slots within 5 ms for different SCSs in NR;
  • FIG. 4 schematically shows multiplexing types between SS/PBCH block and RMSI control resource set (CORESET);
  • FIG. 5 is a flow chart depicting a method according to an embodiment of the present disclosure.
  • FIG. 6 shows the bitmap of one or more time windows within the first periodicity according to an embodiment of the present disclosure
  • FIG. 7 is a flow chart depicting a method according to another embodiment of the present disclosure.
  • FIG. 8 is a flow chart depicting a method according to an embodiment of the present disclosure.
  • FIG. 9 is a flow chart depicting a method according to another embodiment of the present disclosure.
  • FIG. 10 is a block diagram illustrating a network device according to an embodiment of the disclosure.
  • FIG. 11 is a block diagram illustrating a terminal device according to an embodiment of the disclosure.
  • FIG. 12 is a flow chart depicting a method implemented in a communication system according to an embodiment of the disclosure.
  • FIG. 13 is a flow chart depicting a method implemented in a communication system according to another embodiment of the disclosure.
  • wireless communication network refers to a network following any suitable communication standards, such as LTE-Advanced (LTE-A), LTE, Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and so on.
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • the communications between a terminal device and a network device in the wireless communication network may be performed according to any suitable generation communication protocols, including, but not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable, and/or other suitable the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the future fifth generation (5G) communication protocols such as NR, wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, and/or ZigBee standards, and/or any other protocols either currently known or to be developed in the future.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • the term “network device” refers to a device in a wireless communication network via which a terminal device accesses the network and receives services therefrom.
  • the network device refers a base station (BS), an access point (AP), or any other suitable device in the wireless communication network.
  • the BS may be, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), or gNB, a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low power node such as a femto, a pico, and so forth.
  • the network device may include multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission nodes transmission nodes.
  • the network device may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a terminal device access to the wireless communication network or to provide some service to a terminal device that has accessed the wireless communication network.
  • terminal device refers to any end device that can access a wireless communication network and receive services therefrom.
  • the terminal device refers to a mobile terminal, user equipment (UE), or other suitable devices.
  • the UE may be, for example, a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT).
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, wearable terminal devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE) and the like.
  • portable computers image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances
  • a mobile phone a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal
  • a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3rd Generation Partnership Project
  • a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and/or operates the relevant device.
  • a terminal device may be configured to transmit and/or receive information without direct human interaction.
  • a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the wireless communication network.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.
  • the terminal device may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or network equipment.
  • the terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine-type communication
  • the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • NB-IoT narrow band internet of things
  • a terminal device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a downlink, DL transmission refers to a transmission from the network device to a terminal device
  • an uplink, UL transmission refers to a transmission in an opposite direction.
  • references in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the RMSI TTI is agreed to be 160 ms, there's no RMSI periodicity indicated in PBCH, and the RMSI scheduling periodicity is up to gNB implementation.
  • One-to-one association between one SS/PBCH block and one RMSI in wideband operation is assumed in 3GPP release 15.
  • the number of RMSI repetitions will be no more than the additional SS/PBCH block, considering that some SS/PBCH block in some SS burst set may have no RMSI associated.
  • the SS burst set periodicity may be too long, the SS burst set might even be only transmitted every other SSB TTI (such as 80 ms) and probably in later 3GPP releases there could be more-to-one association between SSB and RMSI, thus the performance of the RMSI might not be acceptable without additional repetitions for soft combining with same or different redundancy versions.
  • RMSI or other data channel scheduling if the RMSI messages are transmitted without some defined patterns (e.g. beam patterns, redundancy version patterns) especially when it's not necessary to have as many RMSI messages as SS/PBCH blocks. And in this case if slot-based scheduling of RMSI is used, it may take more time per sweep on RMSI transmission than what is needed for SSB transmission.
  • some defined patterns e.g. beam patterns, redundancy version patterns
  • the present disclosure proposes a solution for RMSI in the wireless network such as NR. It may overcome at least one of the drawbacks mentioned above and/or other drawbacks not mentioned above. It is noted that though the embodiments are mainly described in the context of the NR system, they are not limited to this but can be applied to any suitable wireless system.
  • FIG. 1 depicts a schematic communication system, in which some embodiments of the present disclosure can be implemented.
  • the communication system 100 comprises a network device 110 such as a cellular base station, for example a gNB in NR.
  • the network device 110 may refer to a function element on the network side as compared to a terminal device or UE.
  • the network device 110 may comprise an eNB, a Home eNode B, a femto Base Station, a pico BS, gNB or any other node capable to serve terminal devices 104 - 10 n in the system 100 .
  • a cellular radio system may comprise a network of radio cells each served by a transmitting station, known as a cell site or base transceiver station.
  • the radio network provides wireless communications service for a plurality of transceivers (in most cases mobile).
  • the network of network devices working in collaboration allows for wireless service which is greater than the radio coverage provided by a single network device.
  • the individual network device may be connected by another network (in many cases a wired network, not shown), which includes additional controllers for resource management and in some cases access to other network systems (such as the Internet) or metropolitan area networks (MANs).
  • the circle 130 schematically indicates a coverage range of the network device 110 .
  • the communication system 100 may comprise one or more UEs or terminal devices 104 - 10 n , each of which may operably communicate with the network device 110 such as a cellular base station through a wireless link, such as link 120 and 124 .
  • the terminal devices 104 - 10 n can be fixed or moveable.
  • Terminal devices 104 - 10 n may include, but not limited to, cellular telephones, smart phones, and computers, whether desktop, laptop, or otherwise, as well as mobile devices or terminals such as cellular network UEs, machine type communication devices, handheld computers, personal digital assistants (PDAs), wireless sensors, wearable devices, video cameras, set-top boxes, personal media devices, or any combinations of the foregoing, which may be provided with wireless communication functionality and run with any kind of operating system including, but not limited to, Windows, Linux, UNIX, Android, iOS and their variants.
  • Windows Windows
  • Linux UNIX
  • Android iOS and their variants.
  • the terminal devices may receive signals from each of the two or more network devices.
  • the network device 110 may be connected to a host computer 150 , 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.
  • Host computer 150 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.
  • a connection 140 between the network device 110 and the host computer 150 may extend directly from core network to the host computer 150 or may go via an optional intermediate network (not shown).
  • the intermediate network may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network, if any, may be a backbone network or the Internet; in particular, the intermediate network may comprise two or more sub-networks (not shown).
  • the communication system 100 as a whole enables connectivity between the connected UEs 104 - 10 n and the host computer 150 .
  • the connectivity may be described as an over-the-top (OTT) connections ⁇ 124, 140 ⁇ and ⁇ 120, 140 ⁇ .
  • the host computer 150 and the connected UEs 104 - 10 n are configured to communicate data and/or signaling via OTT connections, using an access network (not shown), a core network (not shown), any intermediate network (not shown) and possible further infrastructure (not shown) as intermediaries.
  • the OTT connections ⁇ 124, 140 ⁇ and ⁇ 120, 140 ⁇ may be transparent in the sense that the participating communication devices through which the OTT connections passes are unaware of routing of uplink and downlink communications.
  • the network device 110 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 150 to be forwarded (e.g., handed over) to a connected UE 104 .
  • the host computer 150 need not be aware of the future routing of an outgoing uplink communication originating from the UE 104 towards the host computer 150 .
  • host computer 150 comprises hardware including communication interface 152 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 100 .
  • Host computer 150 further comprises processing circuitry 154 , which may have storage and/or processing capabilities.
  • processing circuitry 154 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 150 further comprises software 156 , which is stored in or accessible by host computer 150 and executable by processing circuitry 154 .
  • Software 156 includes host application.
  • Host application may be operable to provide a service to a remote user, such as terminal device 104 connecting via OTT connection ⁇ 120, 140 ⁇ terminating at terminal device 104 and host computer 150 .
  • host application may provide user data which is transmitted using OTT connection ⁇ 120, 140 ⁇ .
  • the communication interface 152 is configured to receive user data originating from a transmission from the terminal device to the network device.
  • the communication interface 152 is configured to initiate a transmission carrying user data to the terminal device via the network device.
  • FIG. 5 is a flow chart depicting a method for transmitting RMSI in a wireless network according to an embodiment of the present disclosure, which may be performed at an apparatus such as the network device 110 of FIG. 1 .
  • the network device 110 may provide means for accomplishing various parts of the method 500 as well as means for accomplishing other processes in conjunction with other components.
  • the wireless network may be NR or other suitable wireless network where the RMSI is required to be transmitted.
  • the PBCH may provide a subset of minimum system information for random access and configurations for fetching the other subset of the minimum system information in the RMSI, a number of synchronization signal (SS)/PBCH blocks constitute a SS burst set which is transmitted periodically with a first periodicity configured in the RMSI or via higher layer parameters.
  • the first periodicity may be 20 ms, 40 ms, 80 ms or other suitable value.
  • the method 500 may start at block 502 where the network device 110 determines whether a SS/PBCH block in the SS burst set configures the RMSI.
  • the SS/PBCH block in the SS burst set may configure RMSI control resource set (CORESET) which may indicate the location of RMSI physical downlink shared channel (PDSCH) comprising the RMSI in NR.
  • CORESET RMSI control resource set
  • the SS/PBCH block may or may not configure the RMSI due to some possible reasons.
  • the network device 110 in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, transmit, one or more repeated RMSI within the first periodicity.
  • the network device 110 may transmit one or more repeated RMSI within the first periodicity by using any suitable approaches.
  • the network device 110 may transmit one or more repeated RMSI within the first periodicity based on at least one of a second periodicity, a first redundancy version pattern, a first beam pattern, a bitmap of one or more time windows within the first periodicity.
  • a bit in the bitmap indicates whether one of the one or more repeated RMSIs is transmitted in a corresponding time window and the at least one of the second periodicity, the first redundancy version pattern, the first beam pattern, the bitmap is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • the predefined value may be 20 ms or any other suitable value.
  • the network device 110 can transmit only one or more repeated RMSI PDSCHs comprising the RMSI based on at least one of the second periodicity, the first redundancy version pattern, the first beam pattern and the bitmap.
  • the CORESET may be not transmitted.
  • the network device 110 can transmit both the CORESETs and the RMSI PDSCHs, wherein the CORESETs may be transmitted based on at least one of the second periodicity, the first redundancy version pattern, the first beam pattern and the bitmap.
  • the locations of the RMSI PDSCHs are indicated by the CORESETs.
  • the network device 110 can transmit both the repeated CORESETs and the repeated RMSI PDSCHs based on at least one of the second periodicity, the first redundancy version pattern, the first beam pattern and the bitmap.
  • the network device 110 in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, transmits, one or more repeated RMSI within the first periodicity, based on the second periodicity.
  • the second periodicity may comprise 20 ms, 40 ms, 80 ms or any other suitable value.
  • the second periodicity may be indicated by a RMSI repetition field RMSI_repAdd, which may occupy any suitable number of bits such as 2 bits.
  • RMSI_repAdd may be defined as below:
  • the value of RMSI_repAdd can be, for example, confined in a set of values shown in below table I:
  • the value of RMSI_repAdd can be set as 00, which means no additional repetition.
  • the value of RMSI_repAdd can be set as 00 or 01, which means no additional repetition or repeating with 20 ms periodicity.
  • the network device 110 in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, transmit, one or more repeated RMSI within the first periodicity, based on the bitmap of one or more time windows within the first periodicity.
  • the size of the time windows may be 20 ms or any other suitable value.
  • FIG. 6 shows the bitmap of one or more time windows within the first periodicity according to an embodiment of the present disclosure. As shown in FIG.
  • the SS burst set periodicity (i.e., the first periodicity) is 40 ms and RMSI TTI can be evenly divided to 8 time windows, each of which is 20 ms, and the 1st 20 ms is the time window in which RMSI is firstly received based on the RMSI configuration in one SSB.
  • Additional RMSI repetition bits, RMSI_repAdd_bitmap e.g. 7 bits (B6, B5, B4, B3, B2, B1 and B0), may be used to indicate which of the 20 ms time windows in the latter seven 20 ms periods in the RMSI TTI has additional RMSI (including RMSI CORESET or RMSI PDSCH only) or not.
  • B1 may be set as 1 which means additional RMSI (including CORESET or PDSCH only) is transmitted in the 20 ms period corresponding to B1.
  • the one of the two or more time windows within the first periodicity is used to transmit the RMSI, the one of the two or more time windows is not used to transmit the repeated RMSI.
  • Bn can be set as 0 if the corresponding 20 ms period includes one SS burst set. Within the time window such as 20 ms, the timing frequency relative position of the one or more repeated RMSIs can be same as the one indicated by the SSB.
  • more signaling can also be indicated in RMSI or higher layer messages to provide redundancy version (RV) patterns and/or beam patterns of the one or more repeated RMSIs.
  • RV redundancy version
  • some fixed RV/beam pattern of the one or more repeated RMSIs can be predefined without any extra explicit signaling.
  • the first 20 ms period could contain a first transmission of ⁇ SSB1, SSB2, SSB3, SSB4 ⁇ during 2 slots followed by slot-based RMSI repetitions containing a redundancy version (denoted by RV1) of RMSI repetitions ⁇ RMSI1-RV1, RMSI2-RV1, RMSI3-RV1, RMSI4-RV1 ⁇ during 2 slots.
  • RV1 redundancy version
  • the next 20 ms period contains another redundancy version (denoted by RV2) of the RMSI repetitions ⁇ RMSI1-RV2, RMSI2-RV2, RMSI3-RV2, RMSI4-RV2 ⁇ , wherein “n” in RMSIn denotes the RMSI index corresponding to the SS/PBCH block index “n”, and “n” in RVn denotes the redundancy version number.
  • the first 20 ms period could contain a first transmission of ⁇ SSB1, SSB2, SSB3, SSB4 ⁇ during 2 slots followed by slot-based RMSI repetitions transmitted by a beam pattern (denoted by BP1) ⁇ RMSI1-BP1, RMSI2-BP1, RMSI3-BP1, RMSI4-BP1 ⁇ during 2 slots.
  • BP1 beam pattern
  • the next 20 ms period contains another beam pattern (denoted by BP2) of the RMSI repetitions ⁇ RMSI1-BP2, RMSI2-BP2, RMSI3-BP2, RMSI4-BP2 ⁇ , wherein “n” in BPn denotes the beam pattern number.
  • both the RV patterns and beam patterns can be used to indicate how to transmit the repeated RMSI.
  • one repeated RMSI may contain a redundancy version 1 of RMSI and be transmitted by the beam pattern 1
  • another repeated RMSI may contain a redundancy version 2 of RMSI and be transmitted by the beam pattern 2 .
  • repetitive timing frequency positions of the one or more repeated RMSIs are determined by the one indicated by the SS/PBCH block in the SS burst set based on a predefined rule.
  • the second periodicity is 20 ms
  • the first periodicity is 40 ms and the RMSI CORESET and RMSI PDSCH are transmitted at x ms and y ms respectively within the beginning 20 ms of the first periodicity
  • the first repeated RMSI CORESET and/or RMSI PDSCH may be transmitted at x+20 ms and/or y+20 ms respectively, wherein x and y denotes a rational number respectively.
  • the timing frequency relative position of the one or more repeated the repeated RMSI CORESET and/or RMSI PDSCH can be same as the one indicated by the SS/PBCH block.
  • any other suitable predefined rules may be defined in other embodiments, for example, offset.
  • FIG. 7 is a flow chart depicting a method for transmitting RMSI in a wireless network according to an embodiment of the present disclosure, which may be performed at an apparatus such as the network device 110 of FIG. 1 .
  • the network device 110 may provide means for accomplishing various parts of the method 700 as well as means for accomplishing other processes in conjunction with other components.
  • the method 700 may start at block 702 where the network device 110 transmits the configured RMSI based on at least one of a second redundancy version pattern, a second beam pattern, and a scheduling window that does not overlap with that of the SS burst set, wherein the at least one of the second redundancy version pattern, the second beam pattern, and the scheduling window is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • the network device 110 transmits the configured RMSI based on the second redundancy version pattern. Assuming that the SS burst set periodicity is 20 ms and the RMSI TTI is 160 ms and each SS/PBCH block configures respective RMSIs, then there will be 8 configured RMSIs (i.e., RMSI PDSCHs and RMSI CORESETs) corresponding to each SS/PBCH block index to be transmitted in the RMSI TTI. The 8 configured RMSIs can be transmitted based on the second redundancy version pattern.
  • the 8 configured RMSIs can be transmitted based on the redundancy version pattern (denoted by RV) ⁇ RMSI1-RV1, RMSI1-RV2, RMSI1-RV3, RMSI1-RV4, RMSI1-RV1, RMSI1-RV2, RMSI1-RV3, RMSI1-RV4 ⁇ .
  • RV redundancy version pattern
  • the network device 110 transmits the configured RMSI based on the second beam pattern.
  • the above 8 configured RMSIs can be transmitted based on the beam pattern (denoted by BP) ⁇ RMSI1-BP1, RMSI1-BP2, RMSI1-BP3, RMSI1-BP4, RMSI1-BP1, RMSI1-BP2, RMSI1-BP3, RMSI1-BP4 ⁇ .
  • RMSI redundancy versions and/or beam patterns can be mapped to different SS block duration time windows. For example, assuming that the SS burst set periodicity is 20 ms while RMSI repetitions are transmitted every 40 ms. It can then be further indicated if the RMSI repetitions are transmitted using slot-based or non-slot-based scheduling (previously known as mini-slots). When “Type 1 SS/PBCH block and RMSI CORESET multiplexing pattern” is used (see FIG. 4 ) the RMSI transmissions may occur in either normal slots or in “mini-slots”.
  • the SS/PBCH block consists of 4 symbols (see FIG. 2 ), it is possible to transmit 2 SS/PBCH blocks in one slot while only one RMSI repetition can be transmitted per slot when slot-based transmission is used.
  • one solution is to transmit half of the RMSI repetitions in each sweep and to toggle between RMSI repetitions being transmitted in odd sweeps versus even sweeps in odd or even beams respectively.
  • the first sweep could then contain a first transmission of ⁇ SSB1, SSB2, SSB3, SSB4 ⁇ during 2 slots followed by slot-based RMSI repetitions containing a redundancy version 1 (denoted by RV1) for the odd beams ⁇ RMSI1-RV1, RMSI3-RV1 ⁇ during 2 slots.
  • RV1 redundancy version 1
  • the next 20 ms period would then again consists of the 4 SSBs ⁇ SSB1, SSB2, SSB3, SSB4 ⁇ transmitted during 2 slots followed by slot-based RMSI repetitions containing the redundancy version 1 for the even beams ⁇ RMSI2-RV1, RMSI4-RV1 ⁇ during 2 slots.
  • the next 40 ms period would then contain, in addition to the SSB transmissions, the redundancy version 2 of the RMSI repetitions ⁇ RMSI1-RV2, RMSI3-RV2 ⁇ and ⁇ RMSI2-RV2, RMSI4-RV2 ⁇ and so on.
  • the configured RMSI may be assigned with a non-overlapping scheduling window.
  • the RMSIs are transmitted more seldom than the SS/PBCH blocks in the RMSI TTI, then this allows for some scheduling flexibility of the RMSI on the network side.
  • the SSBs periodicity is for example 20 ms and the SSBs are all transmitted in the first 5 ms part of this time window, then a sub-set of the RMSI transmissions (e.g. odd/even or high/low RMSI index) need to be transmitted in the remaining 15 ms part of the time window.
  • a slot-based or non-slot-based scheduling is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • the content of the RMSI corresponding to a SS/PBCH block index, when transmitted in a RMSI TTI such as 160 ms, is not changed.
  • it can support RMSI soft combining from two or more transmitted RMSIs.
  • FIG. 8 is a flow chart depicting a method for receiving RMSI in a wireless network according to an embodiment of the present disclosure, which may be performed at an apparatus such as the terminal device 102 of FIG. 1 .
  • the terminal device may provide means for accomplishing various parts of the method 800 as well as means for accomplishing other processes in conjunction with other components.
  • the physical broadcast channel PBCH
  • SS synchronization signal
  • the method 800 may start at block 802 where the terminal device 102 determines whether a SS/PBCH block in the SS burst set configures the RMSI.
  • the terminal device 102 in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, receives, one or more repeated RMSI within the first periodicity.
  • the terminal device 102 may receive one or more repeated RMSI within the first periodicity by using any suitable approaches.
  • the network device 110 may receive one or more repeated RMSI within the first periodicity by using any suitable approaches based on at least one of a second periodicity, a first redundancy version pattern, a first beam pattern and a bitmap of one or more time windows within the first periodicity.
  • FIG. 9 is a flow chart depicting a method for receiving RMSI in a wireless network according to an embodiment of the present disclosure, which may be performed at an apparatus such as the terminal device 102 of FIG. 1 .
  • the terminal device may provide means for accomplishing various parts of the method 900 as well as means for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, detailed description thereof is omitted here for brevity.
  • the method 900 may start at block 902 where the terminal device 102 receives the configured RMSI based on at least one of a second redundancy version pattern, a second beam pattern, and a scheduling window that does not overlap with that of the SS burst set, wherein the at least one of the second redundancy version pattern, the second beam pattern, and the scheduling window is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • a bit in the bitmap indicates whether one of the one or more repeated RMSIs is transmitted in a corresponding time window.
  • the at least one of the second periodicity, the first redundancy version pattern, the first beam pattern, the bitmap is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • a slot-based or non-slot-based scheduling is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • repetitive timing frequency positions of the one or more repeated RMSIs are determined by the one indicated by the SS/PBCH block in the SS burst set based on a predefined rule.
  • the one of the two or more time windows within the first periodicity is used to transmit the RMSI, the one of the two or more time windows is not used to transmit the repeated RMSI.
  • the method when the repeated RMSI is transmitted, the method further comprises receiving only RMSI physical downlink shared channel (PDSCH) comprising the RMSI.
  • PDSCH physical downlink shared channel
  • the content of the RMSI corresponding to a SS/PBCH block index, when transmitted in a RMSI transmission time interval (TTI), is not changed.
  • FIG. 10 depicts a network device capable of implementing the methods for transmitting remaining minimum system information (RMSI) in a wireless network as described above, wherein a physical broadcast channel (PBCH) provides a subset of minimum system information for random access and configurations for fetching the other subset of the minimum system information in the RMSI, a number of synchronization signal (SS)/PBCH blocks constitute a SS burst set which is transmitted periodically with a first periodicity.
  • the network device 1000 comprises a processing device 1004 , a memory 1005 , and a radio modem subsystem 1001 in operative communication with the processor 1004 .
  • the radio modem subsystem 1001 comprises at least one transmitter 1002 and at least one receiver 1003 . While only one processor is illustrated in FIG. 10 , the processing device 1004 may comprises a plurality of processors or multi-core processor(s). Additionally, the processing device 1004 may also comprise cache to facilitate processing operations.
  • Computer-executable instructions can be loaded in the memory 1005 and, when executed by the processing device 1004 , cause the network device 1000 to implement the above-described methods for transmitting RMSI.
  • the computer-executable instructions can cause the network device 1000 to determine whether a SS/PBCH block in the SS burst set configures the RMSI; in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, transmit one or more repeated RMSI within the first periodicity.
  • the computer-executable instructions can further cause the network device 1000 to transmit the configured RMSI based on at least one of a second redundancy version pattern, a second beam pattern, and a scheduling window that does not overlap with that of the SS burst set, wherein the at least one of the second redundancy version pattern, the second beam pattern, and the scheduling window is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • the computer-executable instructions can further cause the network device 1000 to transmit one or more repeated RMSI within the first periodicity based on at least one of a second periodicity, a first redundancy version pattern, a first beam pattern and a bitmap of one or more time windows within the first periodicity.
  • a bit in the bitmap indicates whether one of the one or more repeated RMSIs is transmitted in a corresponding time window.
  • the at least one of the second periodicity, the first redundancy version pattern, the first beam pattern, the bitmap is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • a slot-based or non-slot-based scheduling is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • repetitive timing frequency positions of the one or more repeated RMSIs are determined by the one indicated by the SS/PBCH block in the SS burst set based on a predefined rule.
  • the one of the two or more time windows within the first periodicity is used to transmit the RMSI, the one of the two or more time windows is not used to transmit the repeated RMSI.
  • the method when the repeated RMSI is transmitted, the method further comprises transmitting only RMSI physical downlink shared channel (PDSCH) comprising the RMSI.
  • PDSCH physical downlink shared channel
  • the content of the RMSI corresponding to a SS/PBCH block index, when transmitted in a RMSI transmission time interval (TTI), is not changed.
  • FIG. 11 depicts a terminal device capable of implementing the methods for receiving RMSI in a wireless network, as described above, wherein a physical broadcast channel (PBCH) provides a subset of minimum system information for random access and configurations for fetching the other subset of the minimum system information in the RMSI, a number of synchronization signal (SS)/PBCH blocks constitute a SS burst set which is transmitted periodically with a first periodicity.
  • the terminal device 1100 comprises a processing device 1104 , a memory 1105 , and a radio modem subsystem 1101 in operative communication with the processor 1104 .
  • the radio modem subsystem 1101 comprises at least one transmitter 1102 and at least one receiver 1103 . While only one processor is illustrated in FIG. 11 , the processing device 1104 may comprises a plurality of processors or multi-core processor(s). Additionally, the processing device 1104 may also comprise cache to facilitate processing operations.
  • Computer-executable instructions can be loaded in the memory 1105 and, when executed by the processing device 1104 , cause the terminal device 1100 to implement the above-described methods for receiving RMSI.
  • the computer-executable instructions can cause the terminal device 1100 to determine whether a SS/PBCH block in the SS burst set configures the RMSI; in response to that the SS/PBCH block configures the RMSI and the first periodicity is greater than a predefined value, receive one or more repeated RMSI within the first periodicity.
  • the computer-executable instructions can further cause the terminal device 1100 to, receive one or more repeated RMSI within the first periodicity, based on at least one of a second periodicity, a first redundancy version pattern, a first beam pattern and a bitmap of one or more time windows within the first periodicity.
  • the computer-executable instructions can further cause the terminal device 1100 to receive the configured RMSI based on at least one of a second redundancy version pattern, a second beam pattern, and a scheduling window that does not overlap with that of the SS burst set, wherein the at least one of the second redundancy version pattern, the second beam pattern, and the scheduling window is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • a bit in the bitmap indicates whether one of the one or more repeated RMSIs is transmitted in a corresponding time window.
  • the at least one of the second periodicity, the first redundancy version pattern, the first beam pattern, the bitmap is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • a slot-based or non-slot-based scheduling is indicated to a terminal device in the RMSI or in a higher layer message or predefined.
  • repetitive timing frequency positions of the one or more repeated RMSIs are determined by the one indicated by the SS/PBCH block in the SS burst set based on a predefined rule.
  • the one of the two or more time windows within the first periodicity is used to transmit the RMSI, the one of the two or more time windows is not used to transmit the repeated RMSI.
  • the method when the repeated RMSI is transmitted, the method further comprises receiving only RMSI physical downlink shared channel (PDSCH) comprising the RMSI.
  • PDSCH physical downlink shared channel
  • the content of the RMSI corresponding to a SS/PBCH block index, when transmitted in a RMSI transmission time interval (TTI), is not changed.
  • FIG. 12 is a flow chart depicting a method implemented in a communication system including a host computer, a network device and a terminal device according to an embodiment of the present disclosure, which may be performed at an apparatus such as the host computer 150 of FIG. 1 .
  • the terminal device may provide means for accomplishing various parts of the method 1200 as well as means for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, detailed description thereof is omitted here for brevity.
  • the method 1200 may start at block 1202 where the host computer 150 receives user data originating from a transmission from a terminal device to a network device.
  • FIG. 13 is a flow chart depicting a method implemented in a communication system including a host computer, a network device and a terminal device according to an embodiment of the present disclosure, which may be performed at an apparatus such as the host computer 150 of FIG. 1 .
  • the terminal device may provide means for accomplishing various parts of the method 1300 as well as means for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, detailed description thereof is omitted here for brevity.
  • the method 1300 may start at block 1302 where the host computer 150 initiates a transmission carrying user data to the terminal device via the network device.
  • a computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program instructions stored therein, the computer-executable instructions being configured to, when being executed, cause a network device to operate as described above.
  • a computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program instructions stored therein, the computer-executable instructions being configured to, when being executed, cause a terminal device to operate as described above.
  • a computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program instructions stored therein, the computer-executable instructions being configured to, when being executed, cause a terminal device to operate as described above.
  • any of the components of the network device and terminal device can be implemented as hardware or software modules.
  • software modules they can be embodied on a tangible computer-readable recordable storage medium. All of the software modules (or any subset thereof) can be on the same medium, or each can be on a different medium, for example.
  • the software modules can run, for example, on a hardware processor. The method steps can then be carried out using the distinct software modules, as described above, executing on a hardware processor.
  • program means to include any sequences or human or machine cognizable steps which perform a function.
  • Such program may be rendered in virtually any programming language or environment including, for example, C/C++, Fortran, COBOL, PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML), and the like, as well as object-oriented environments such as the Common Object Request Broker Architecture (CORBA), JavaTM (including J2ME, Java Beans, etc.), Binary Runtime Environment (BREW), and the like.
  • CORBA Common Object Request Broker Architecture
  • JavaTM including J2ME, Java Beans, etc.
  • BREW Binary Runtime Environment
  • memory and “storage device” are meant to include, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the memory or storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
US16/920,305 2018-01-02 2020-07-02 Method, network device and terminal device for remaining minimum system information Active US10939360B2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/186,010 US11696217B2 (en) 2018-01-02 2021-02-26 Method, network device and terminal device for remaining minimum system information
US18/322,583 US20230308988A1 (en) 2018-01-02 2023-05-23 Method, network device and terminal device for remaining minimum system information

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
WOPCT/CN2018/070045 2018-01-02
CNPCTCN2018070045 2018-01-02
CN2018070045 2018-01-02
PCT/CN2019/070048 WO2019134636A1 (en) 2018-01-02 2019-01-02 Method, network device and terminal device for remaining minimum system information

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/070048 Continuation WO2019134636A1 (en) 2018-01-02 2019-01-02 Method, network device and terminal device for remaining minimum system information

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/186,010 Continuation US11696217B2 (en) 2018-01-02 2021-02-26 Method, network device and terminal device for remaining minimum system information

Publications (2)

Publication Number Publication Date
US20200351759A1 US20200351759A1 (en) 2020-11-05
US10939360B2 true US10939360B2 (en) 2021-03-02

Family

ID=67144345

Family Applications (3)

Application Number Title Priority Date Filing Date
US16/920,305 Active US10939360B2 (en) 2018-01-02 2020-07-02 Method, network device and terminal device for remaining minimum system information
US17/186,010 Active 2039-02-24 US11696217B2 (en) 2018-01-02 2021-02-26 Method, network device and terminal device for remaining minimum system information
US18/322,583 Abandoned US20230308988A1 (en) 2018-01-02 2023-05-23 Method, network device and terminal device for remaining minimum system information

Family Applications After (2)

Application Number Title Priority Date Filing Date
US17/186,010 Active 2039-02-24 US11696217B2 (en) 2018-01-02 2021-02-26 Method, network device and terminal device for remaining minimum system information
US18/322,583 Abandoned US20230308988A1 (en) 2018-01-02 2023-05-23 Method, network device and terminal device for remaining minimum system information

Country Status (8)

Country Link
US (3) US10939360B2 (de)
EP (1) EP3735792B1 (de)
JP (1) JP7171733B2 (de)
KR (2) KR102440875B1 (de)
CN (1) CN111543101A (de)
ES (1) ES2956333T3 (de)
PL (1) PL3735792T3 (de)
WO (1) WO2019134636A1 (de)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022011685A1 (en) * 2020-07-17 2022-01-20 Qualcomm Incorporated Nr-u for 6ghz band-rmsi pdcch repetition for lpi mode
CN119233404B (zh) * 2023-06-29 2026-03-20 华为技术有限公司 系统信息发送方法及通信装置

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017213420A1 (ko) 2016-06-07 2017-12-14 엘지전자(주) 무선 통신 시스템에서 순환 전치에 대한 정보를 획득하는 방법 및 이를 위한 장치
US20180192383A1 (en) * 2017-01-04 2018-07-05 Samsung Electronics Co., Ltd. Method and apparatus for system information delivery in advanced wireless systems
US20190306813A1 (en) * 2018-03-29 2019-10-03 Lg Electronics Inc. Method and apparatus for transmitting and receiving system information
US20200059810A1 (en) * 2017-05-02 2020-02-20 Ntt Docomo, Inc. User terminal and radio communication method
US20200178253A1 (en) * 2017-08-11 2020-06-04 Huawei Technologies Co., Ltd. Information Sending and Receiving Method and Apparatus
US20200187159A1 (en) * 2017-05-05 2020-06-11 Lg Electronics Inc. Method and apparatus for receiving a synchronization signal
US20200244530A1 (en) * 2017-11-17 2020-07-30 Telefonaktiebolaget Lm Ericsson (Publ) Compressed table-based configuration of remaining minimum system information coreset in a new radio physical broadcast channel
US20200275420A1 (en) * 2017-11-17 2020-08-27 Mediatek Singapore Pte. Ltd. Remaining minimum system information reception in 5g wireless communication system

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
MY177342A (en) * 2013-11-27 2020-09-12 Ericsson Telefon Ab L M Network node, wireless device, methods therein, for sending and detecting, respectively, synchronization signal and an associated information
US10812162B2 (en) * 2017-03-21 2020-10-20 Samsung Electronics Co., Ltd. Method and apparatus for indication of reference signals in wireless systems
CN110637488A (zh) * 2017-03-23 2019-12-31 瑞典爱立信有限公司 网络节点、无线通信设备、方法以及计算机程序
GB2563454A (en) * 2017-06-16 2018-12-19 Nec Corp Communication system
US10616877B2 (en) * 2017-11-16 2020-04-07 Huawei Technologies Co., Ltd. Configuration of the initial active bandwidth part for initial network access
JP7002651B2 (ja) * 2017-11-17 2022-01-20 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ Ｎｒにおけるページングｃｏｒｅｓｅｔマッピングに対するｓｓｂの機構
US11362878B2 (en) * 2017-11-22 2022-06-14 Qualcomm Incorporated Radio (NR) remaining minimum system information (RMSI) multiplexing and periodicity considerations
US11457472B2 (en) * 2017-12-18 2022-09-27 Samsung Electronics Co., Ltd. Method and apparatus for initial access block on stand-alone NR unlicensed spectrum

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017213420A1 (ko) 2016-06-07 2017-12-14 엘지전자(주) 무선 통신 시스템에서 순환 전치에 대한 정보를 획득하는 방법 및 이를 위한 장치
US20190268205A1 (en) 2016-06-07 2019-08-29 Lg Electronics Inc. Method for obtaining information about cyclic prefix in wireless communication system and device for same
US20180192383A1 (en) * 2017-01-04 2018-07-05 Samsung Electronics Co., Ltd. Method and apparatus for system information delivery in advanced wireless systems
US20200059810A1 (en) * 2017-05-02 2020-02-20 Ntt Docomo, Inc. User terminal and radio communication method
US20200187159A1 (en) * 2017-05-05 2020-06-11 Lg Electronics Inc. Method and apparatus for receiving a synchronization signal
US20200178253A1 (en) * 2017-08-11 2020-06-04 Huawei Technologies Co., Ltd. Information Sending and Receiving Method and Apparatus
US20200244530A1 (en) * 2017-11-17 2020-07-30 Telefonaktiebolaget Lm Ericsson (Publ) Compressed table-based configuration of remaining minimum system information coreset in a new radio physical broadcast channel
US20200275420A1 (en) * 2017-11-17 2020-08-27 Mediatek Singapore Pte. Ltd. Remaining minimum system information reception in 5g wireless communication system
US20190306813A1 (en) * 2018-03-29 2019-10-03 Lg Electronics Inc. Method and apparatus for transmitting and receiving system information

Non-Patent Citations (9)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15)," Dec. 2017, 56 pages, 3GPP TS 38.213 V2.0.0, 3GPP Organizational Partners.
"Offline summary for AI 7.1.2.2 Remaining details on Remaining Minimum System Information," Oct. 9-13, 2017, 15 pages, 3GPP TSG RAN WG1 Meeting 90bis, R1-1719198, Prague, CZ.
"Presentation of Specification/Report to TSG: TS38.213, Version 2.0.0," Dec. 18-21, 2017, 1 page, 3GPP TSG-RAN Meeting #78, Tdoc RP-172703, Lisbon, Portugal.
"RAN1 Chairman's Notes," Nov. 27-Dec. 1, 2017, 189 pages, 3GPP TSG RAN WG1 Meeting 91, Reno, NV.
"Remaining details of remaining minimum system information," Nov. 27-Dec. 1, 2017, 13 pages, 3GPP TSG RAN WG1 Meeting #91, R1-1721364, Reno, NV.
3GPP, "List of RAN1 Agreements", 3rd Generation Partnership Project, Mobile Competence Centre, F-06921 Sophia-Antipolis Cedex, vol. RAN WG1, Sep. 2017, pp. 1-195.
International Preliminary Report on Patentability, PCT App. No. PCT/CN2019/070048, dated Jul. 16, 2020, 6 pages.
International Search Report and Written Opinion for International Application No. PCT/CN2019/070048, dated Mar. 22, 2019, 10 pages.
Supplementary European Search Report and Search Opinion, EP App. No. 19735854.2, dated Nov. 11, 2020, 14 pages.

Also Published As

Publication number Publication date
CN111543101A (zh) 2020-08-14
WO2019134636A1 (en) 2019-07-11
EP3735792A1 (de) 2020-11-11
EP3735792B1 (de) 2023-08-16
KR102403157B1 (ko) 2022-05-30
KR20220076533A (ko) 2022-06-08
JP2021510032A (ja) 2021-04-08
US11696217B2 (en) 2023-07-04
EP3735792C0 (de) 2023-08-16
KR20200105503A (ko) 2020-09-07
EP3735792A4 (de) 2020-12-09
US20230308988A1 (en) 2023-09-28
KR102440875B1 (ko) 2022-09-07
US20210185594A1 (en) 2021-06-17
PL3735792T3 (pl) 2024-01-29
JP7171733B2 (ja) 2022-11-15
ES2956333T3 (es) 2023-12-19
US20200351759A1 (en) 2020-11-05

Similar Documents

Publication Publication Date Title
US11812432B2 (en) Method and apparatus for using indication information of time domain resource allocation
US11737036B2 (en) Method and apparatus for using indication information of time domain resource allocation
JP7094995B2 (ja) 情報送信方法、端末デバイス、及びネットワーク・デバイス
US12052773B2 (en) Terminal device, network device and methods therein
CA3056687A1 (en) Data transmission method, terminal device and network device
CN113273259A (zh) 数据传输方法及装置
US12120714B2 (en) Method, network device and terminal device for semi-persistent scheduling
US20180041314A1 (en) Data transmission method, feedback information transmission method, and related device
KR20210008295A (ko) 정보 결정 방법, 단말 기기 및 네트워크 기기
WO2017113077A1 (zh) 一种上行紧急业务传输方法、基站、用户设备及系统
US20230308988A1 (en) Method, network device and terminal device for remaining minimum system information
US20240292415A1 (en) Method for transmitting signals, method for receiving signals and apparatus thereof
US12133208B2 (en) Method and devices for wireless communication
US20220022260A1 (en) Terminal Device, Network Device and Methods Therein
OA20156A (en) Method, network device and terminal device for remaining minimum system information.
CN117395785A (zh) 配置方法，装置和可读存储介质

Legal Events

Date Code Title Description
AS Assignment

Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL), SWEDEN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LIN, ZHIPENG;FRENGER, PAL;GROVLEN, ASBJORN;SIGNING DATES FROM 20190107 TO 20190110;REEL/FRAME:053114/0265

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4