EP3651514A1 - Procédé et dispositif de transmission d'informations - Google Patents

Procédé et dispositif de transmission d'informations Download PDF

Info

Publication number
EP3651514A1
EP3651514A1 EP17918870.1A EP17918870A EP3651514A1 EP 3651514 A1 EP3651514 A1 EP 3651514A1 EP 17918870 A EP17918870 A EP 17918870A EP 3651514 A1 EP3651514 A1 EP 3651514A1
Authority
EP
European Patent Office
Prior art keywords
scheduling request
terminal device
network device
configuration information
different
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.)
Granted
Application number
EP17918870.1A
Other languages
German (de)
English (en)
Other versions
EP3651514A4 (fr
EP3651514B1 (fr
Inventor
Zhihu LUO
Xiaolei TIE
Zhe Jin
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP3651514A1 publication Critical patent/EP3651514A1/fr
Publication of EP3651514A4 publication Critical patent/EP3651514A4/fr
Application granted granted Critical
Publication of EP3651514B1 publication Critical patent/EP3651514B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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 signaling, 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/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • 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—Signaling for the administration of the divided path
    • 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/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/0012—Hopping in multicarrier systems

Definitions

  • This application relates to communications technologies, and in particular, to an information transmission method and a device.
  • the internet of things is the "Internet on which things are connected”.
  • a mobile communications standardization organization 3GPP 3rd Generation Partnership Project, 3rd generation partnership project proposes a narrowband internet of things (Narrowband Internet of Things, NB-IOT) at the RAN#69 meeting.
  • 3GPP 3rd Generation Partnership Project, 3rd generation partnership project
  • FIG. 1 is a flowchart of initiating random access by a terminal device in the prior art.
  • the terminal device sends a random access preamble to a base station, and the base station returns a random access response to the terminal device.
  • the terminal device sends a radio resource control (Radio Resource Control, RRC) connection request to the base station after receiving the random access response.
  • RRC Radio Resource Control
  • the base station establishes an RRC connection to the terminal device, and the terminal device feeds back hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ)-acknowledgment (Acknowledgement, ACK) information to the base station.
  • Hybrid Automatic Repeat reQuest Hybrid Automatic Repeat reQuest, HARQ
  • Acknowledgement ACK
  • the terminal device After the RRC connection is established, each time before receiving downlink data sent by the base station or sending data to the base station, the terminal device needs to listen to a narrowband physical downlink control channel (Narrowband Physical Downlink Control CHannel, NPDCCH) to obtain scheduling information related to scheduling of the downlink data or the uplink data.
  • NPDCCH narrowband Physical Downlink Control CHannel
  • Embodiments of this application provide an information transmission method and a device.
  • An implementation process is simple, and a delay and power consumption are greatly reduced.
  • an embodiment of this application provides an information transmission method, and the method includes:
  • an embodiment of this application provides an information transmission method, and the method includes:
  • an embodiment of this application provides a terminal device, and the terminal device includes:
  • an embodiment of this application provides a network device, and the network device includes:
  • the terminal device obtains the resource configuration information used to indicate the resource used by the terminal device to send the scheduling request, and sends the scheduling request to the network device on the resource indicated by the resource configuration information.
  • the network device determines, based on the scheduling request, the amount of uplink data that is requested to be sent by the network device, and configures a resource suitable for the amount of uplink data for the terminal device. Because the preset correspondence exists between a sequence carried in the scheduling request and an amount of uplink data that is requested to be sent by the terminal device to the network device, the amount of uplink data that is requested to be sent by the terminal may be determined based on the sequence carried in the scheduling request. In this way, a step of reporting a buffer status report (Buffer Status Report, BSR) can be reduced. A process is simple, and a delay and power consumption are greatly reduced.
  • Buffer Status Report Buffer Status Report
  • the scheduling request includes a plurality of symbol groups in time domain, and each symbol group includes a cyclic prefix and at least one symbol.
  • the scheduling request is transmitted in a single-carrier frequency-hopping manner.
  • the scheduling request is transmitted in a single-carrier frequency-hopping manner. This may avoid mutual interference with a narrowband physical random access channel (Narrowband Physical Random Access Channel, NPRACH) preamble (preamble) signal.
  • NPRACH narrowband Physical Random Access Channel
  • the scheduling request is transmitted in a single-carrier frequency-hopping manner, so that a configuration manner of a resource used to send the scheduling request is more flexible.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are the same.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are the same.
  • Different sequences are carried on different symbol groups to indicate different amounts of uplink data. In this way, a step of separately reporting a BSR can be avoided. A process is simple, and a delay and power consumption are greatly reduced.
  • the scheduling request is transmitted in a single-carrier manner, all symbol groups in a repeated sending period of the scheduling request are located at a same subcarrier location, and a sending period of the scheduling request includes at least one repeated sending period.
  • different sequences are carried by using a symbol as a granularity to form different scheduling requests, and the scheduling requests are transmitted in a single-carrier manner.
  • a plurality of symbol groups in a repeated sending period of the scheduling request are located at a same subcarrier location. Therefore, a longer sequence can be formed, a code resource is richer, and a granularity of the amount of uplink data is finer.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are different.
  • sequences carried on different symbol groups of scheduling request are different, and sequences carried on different symbols in a same symbol group are also different, so that a more refined scheduling request may be formed, so as to indicate more types of amounts of uplink data. Therefore, a resource allocated by the network device to the terminal device for sending uplink data is more accurate, and proper utilization of the resource is ensured.
  • the method before the sending, by the terminal device, the scheduling request to a network device on the resource indicated by the resource configuration information, the method further includes: performing timing advance TA adjustment.
  • the terminal device performs the timing advance adjustment before sending the scheduling request.
  • the timing advance adjustment is to ensure orthogonality of uplink transmission, so that times at which signals that are of different terminal devices and that arrive in a same subframe arrive at the network device is the same or a time difference between times at which signals arrive at the network device falls within a range of a cyclic prefix, to avoid intra-cell interference.
  • the resource indicated by the resource configuration information includes all frequency domain resources used to transmit a narrowband physical random access channel NPRACH; or the resource indicated by the resource configuration information includes a subset of all frequency domain resources used to transmit a narrowband physical random access channel NPRACH; or the resource indicated by the resource configuration information includes a frequency domain resource, other than a frequency domain resource used for contention-based random access in frequency domain resources used to transmit an NPRACH; or the resource indicated by the resource configuration information includes a subset of a frequency domain resource, other than a frequency domain resource used for contention-based random access in frequency domain resources used to transmit an NPRACH; or the resource indicated by the resource configuration information includes a frequency-hopping resource, other than resource whose quantity is an integer multiple of a quantity of resources in an NPRACH frequency-hopping range in all frequency domain resources used to transmit an NPRACH.
  • the obtaining, by a terminal device, resource configuration information includes:
  • the network device may deliver the resource configuration information each time the terminal device needs to send a scheduling request, or the network device may periodically send the resource configuration information to the terminal device.
  • the network device configures the resource configuration information for the terminal device when the terminal device is initialized.
  • the terminal device stores the resource configuration information in a local cache, and obtains the resource configuration information from the local cache when the terminal device needs to send a scheduling request.
  • a manner of obtaining the resource configuration information is relatively flexible, so that reliability of obtaining the resource configuration information by the terminal device is ensured.
  • the resource configuration information is sent by the network device to the terminal device; or the resource configuration information is configured by the network device for the terminal device when the terminal device is initialized.
  • the network device may deliver the resource configuration information each time the terminal device needs to send a scheduling request, or the network device configures the resource configuration information for the terminal device when the terminal device is initialized.
  • the terminal device stores the resource configuration information in a local cache, and obtains the resource configuration information form the local cache when the terminal device needs to send a scheduling request.
  • a manner of obtaining the resource configuration information is relatively flexible, so that reliability of obtaining the resource configuration information by the terminal device is ensured.
  • the obtaining module is specifically configured to:
  • the obtaining module may receive the resource configuration information sent by the network device each time the terminal device needs to send a scheduling request, or the obtaining module may periodically receive the resource configuration information sent by the network device.
  • the network device configures the resource configuration information for the terminal device when the terminal device is initialized.
  • the terminal device stores the resource configuration information in a local cache, and obtains the resource configuration information from the local cache when the terminal device needs to send a scheduling request.
  • a manner of obtaining the resource configuration information by the obtaining module is relatively flexible, so that reliability of obtaining the resource configuration information by the terminal device is ensured.
  • a configuration manner of a resource used to send a scheduling request is flexible. In this way, a frequency domain resource can be properly used, and mutual interference between NPRACH transmission signals can be avoided.
  • a fifth aspect of this application provides a terminal device, including at least one processing component (or chip) configured to perform the method in the first aspect or all implementations of the first aspect.
  • a sixth aspect of this application provides a network device, including at least one processing component (or chip) configured to perform the method in the second aspect or all implementations of the second aspect.
  • a seventh aspect of this application provides a readable storage medium, and the readable storage medium stores an executable instruction.
  • the terminal device executes the executable instruction, the terminal device performs the information transmission method provided in the first aspect or all implementations of the first aspect.
  • An eighth aspect of this application provides a readable storage medium, and the readable storage medium stores an executable instruction.
  • the network device executes the executable instruction, the network device performs the information transmission method provided in the second aspect or all implementations of the second aspect.
  • a ninth aspect of this application provides a program product.
  • the program product includes an executable instruction, and the executable instruction is stored in a readable storage medium.
  • At least one processor of a terminal device may read the executable instruction from the readable storage medium, and the at least one processor executes the executable instruction to enable the terminal device to perform the information transmission method provided in the first aspect or all implementations of the first aspect.
  • a tenth aspect of this application provides a program product.
  • the program product includes an executable instruction, and the executable instruction is stored in a readable storage medium.
  • At least one processor of a network device may read the executable instruction from the readable storage medium, and the at least one processor executes the executable instruction to enable the network device to perform the information transmission method provided in the second aspect or all implementations of the second aspect.
  • An eleventh aspect of this application provides a network system, and the network system includes the terminal device and the network device in the foregoing aspects.
  • An information transmission method provided in the embodiments of this application is mainly applied to a wireless communications system such as a long term evolution (Long Term Evolution, LTE) system, a long term evolution-advanced LTE-A (LTE Advanced) system, or NB-IOT.
  • a wireless communications system such as a long term evolution (Long Term Evolution, LTE) system, a long term evolution-advanced LTE-A (LTE Advanced) system, or NB-IOT.
  • the information transmission method may also be applied to another communications system, for example, a mobile communications systems such as a new radio (New Radio, NR) system, a global system for mobile communications (Global System of Mobile communication, GSM) system, a code division multiple access (Code Division Multiple Access, CDMA) system, a wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, a general packet radio service (General Packet Radio Service, GPRS), a long term evolution (Long Term Evolution, LTE) system, a long term evolution-advanced (Advanced long term evolution, LTE-A) system, a universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), an evolved long term evolution (evolved Long Term Evolution, eLTE) system, or 5G.
  • a mobile communications systems such as a new radio (New Radio, NR) system, a global system for mobile communications (Global System of Mobile communication, GSM) system, a code division multiple access (Code Division Multiple
  • FIG. 2 is a schematic diagram of an application scenario of an information transmission method according to an embodiment of this application.
  • a network device and a terminal device 1 to a terminal device 6 form a communications system.
  • a base station sends information to one or more terminal devices in the terminal device 1 to the terminal device 6.
  • a terminal device 4 to the terminal device 6 also form a communications system.
  • a terminal device 5 may send information to the terminal device 4, the terminal device 6, or both the terminal device 4 and the terminal device 6.
  • the network device may be a common base station (for example, a Node B or an eNB), a new radio controller (New Radio controller, NR controller), a gNode B (gNB) in a 5G system, a centralized network element (Centralized Unit), a new radio base station, a remote radio unit, a micro base station, a relay (relay), a distributed network element (Distributed Unit), a reception point (Transmission Reception Point, TRP), a transmission point (Transmission Point, TP), or any other radio access device.
  • a common base station for example, a Node B or an eNB
  • a new radio controller New Radio controller, NR controller
  • gNode B gNB
  • 5G system a centralized network element
  • a new radio base station for example, a new radio base station, a remote radio unit, a micro base station, a relay (relay), a distributed network element (Distributed Unit), a reception point (Transmission Reception Point,
  • the terminal device is also referred to as user equipment (User Equipment, UE), and is a device that provides a user with voice and/or data connectivity, for example, a handheld device or a vehicle-mounted device that has a wireless connection function.
  • UE user equipment
  • Common terminals include a mobile phone, a tablet, a notebook computer, a palmtop computer, a mobile Internet device (mobile internet device, MID), and a wearable device, such as a smartwatch, a smart band, or a pedometer.
  • FIG. 3 is a flowchart of an information transmission method according to an embodiment of this application.
  • an application scenario of the method includes a terminal device and a network device. The method includes the following steps.
  • Step 101 The terminal device obtains resource configuration information.
  • the resource configuration information is used to indicate a resource used by the terminal device to send the scheduling request.
  • the resource configuration information may include a subcarrier index, a carrier index, a quantity of repetition times, a period, a starting subframe location, and the like; or the resource configuration information may include an index jointly indicated by configuration parameters such as a subcarrier index, a carrier index, a quantity of repetition times, a period, and a starting subframe location.
  • the resource indicated by the resource configuration information includes all frequency domain resources used to transmit a narrowband physical random access channel (Narrowband Physical Random Access Channel, NPRACH); or includes a subset of all frequency domain resources used to transmit an NPRACH; or includes a frequency domain resource other than a frequency domain resource used for contention-based random access in frequency domain resources used to transmit an NPRACH; or includes a subset of a frequency domain resource other than a frequency domain resource used for contention-based random access in frequency domain resources used to transmit an NPRACH; or includes a frequency-hopping resource other than resources whose quantity is an integer multiple of a quantity of resources in an NPRACH frequency-hopping range in all frequency domain resources used to transmit an NPRACH.
  • NPRACH narrowband Physical Random Access Channel
  • that the terminal device obtains resource configuration information may include: The terminal device receives the resource configuration information sent by the network device; or the terminal device obtains the resource configuration information from a local cache.
  • the resource configuration information is configured by the network device when the terminal device is initiated.
  • the network device may deliver the resource configuration information each time the terminal device needs to send the scheduling request.
  • the network device may periodically send the resource configuration information to the terminal device.
  • the network device configures the resource configuration information when the terminal device is initialized.
  • the terminal device stores the resource configuration information in the local cache, and obtains the resource configuration information from the local cache when the terminal device needs to send the scheduling request.
  • a manner of obtaining the resource configuration information is relatively flexible.
  • that the terminal device is initialized means that the terminal device is powered on, the terminal device establishes an RRC connection, the terminal device re-establishes an RRC connection, the terminal device performs RRC reconfiguration, or the like.
  • the network device may deliver the resource configuration information each time the terminal device needs to send the scheduling request, or the network device may periodically send the resource configuration information to the terminal device.
  • the network device configures the resource configuration information when the terminal device is initialized.
  • the terminal device stores the resource configuration information in the local cache, and obtains the resource configuration information from the local cache when the terminal device needs to send the scheduling request.
  • a manner of obtaining the resource configuration information is relatively flexible, so that reliability of obtaining the resource configuration information by the terminal device is ensured.
  • Step 102 The terminal device sends the scheduling request to the network device on the resource indicated by the resource configuration information, where a preset correspondence exists between a sequence carried in the scheduling request and an amount of uplink data that is requested to be sent by the terminal device to the network device.
  • the preset correspondence between a sequence carried in the scheduling request and an amount of uplink data that is requested to be sent by the terminal device to the network device may be pre-established.
  • one sequence may correspond to one fixed amount of uplink data, or one sequence may correspond to one group of amounts of uplink data, or one sequence may correspond to one range of an amount of uplink data.
  • a person skilled in the art may set, based on an actual situation, the preset correspondence between a sequence carried in the scheduling request and an amount of uplink data that is requested to be sent by the terminal device to the network device. This is not limited in this application.
  • the sequence carried in the scheduling request is determined based on the correspondence between a sequence carried in the scheduling request and an amount of uplink data that is requested to be sent by the terminal device to the network device, and the scheduling request is sent on a resource allocated by the network device.
  • the terminal device performs timing advance adjustment before sending the scheduling request.
  • the timing advance adjustment is to ensure orthogonality of uplink transmission, so that times at which signals that are of different terminal devices and that arrive in a same subframe arrive at the network device is the same or a time difference between times at which signals arrive at the network device falls within a range of a cyclic prefix, to avoid intra-cell interference.
  • a process of timing advance adjustment herein is the same as that in the prior art.
  • the terminal device determines a timing advance based on a timing advance command sent by the network device, and uses the timing advance when sending uplink data.
  • Step 103 The network device receives the scheduling request that is sent by the terminal device on the resource indicated by the resource configuration information.
  • Step 104 The network device determines, based on the scheduling request, the amount of uplink data that is requested to be sent by the network device.
  • the network device detects, on an allocated resource, whether a scheduling request is reported; obtains, based on a sequence carried in a detected scheduling request, information about an amount that is of uplink data and that needs to be reported by the terminal device; and sends scheduling information to the terminal device.
  • the scheduling information is used to indicate a resource used by the terminal device to send uplink data.
  • the terminal device After receiving the scheduling information sent by the network device, the terminal device sends uplink data to the network device at a resource location indicated by the scheduling information.
  • the resource configuration information, the resource indicated by the resource configuration information, and the scheduling request in step 103 and step 104 are the same as the resource configuration information, the resource indicated the resource configuration information, and the scheduling request in step 101 and step 102. Details are not described herein again.
  • the terminal device obtains the resource configuration information used to indicate the resource used by the terminal device to send the scheduling request, and sends the scheduling request to the network device on the resource indicated by the resource configuration information.
  • the network device determines, based on the scheduling request, the amount of uplink data that is requested to be sent by the network device, and configures a resource suitable for the amount of uplink data for the terminal device. Because the preset correspondence exists between the sequence carried in the scheduling request and the amount of uplink data that is requested to be sent by the terminal device to the network device, the amount of uplink data that is requested to be sent by the terminal may be determined based on the sequence carried in the scheduling request. In this way, a step of reporting a BSR (Buffer Status Report, buffer status report) can be reduced. A process is simple, and a delay and power consumption are greatly reduced.
  • BSR Buffer Status Report, buffer status report
  • the scheduling request includes a plurality of symbol groups in time domain, and each symbol group includes a cyclic prefix and a plurality of symbols.
  • different scheduling requests are formed by using a symbol as a granularity in time domain, setting different quantity of symbols, and adding different sequences to different symbols, so as to indicate different amounts of uplink data.
  • This method is simple and has stronger scalability.
  • FIG. 4 is a schematic diagram of a signal format of a scheduling request according to an embodiment of this application.
  • FIG. 5 is a schematic diagram of a symbol group format according to an embodiment of this application.
  • the signal format of the scheduling request may use a design of an NPRACH preamble (preamble), or may use another format different from a signal format of the NPRACH preamble. This is not limited in this application.
  • one scheduling request includes four symbol groups, and each symbol group includes a cyclic prefix and a plurality of symbols.
  • the scheduling request is transmitted in a single-carrier frequency-hopping manner.
  • a frequency domain location for transmitting the scheduling request may be limited to 12 subcarriers, and a frequency-hopping range of frequency domain is 12 subcarriers.
  • #0 to #11 indicate 12 subcarriers.
  • One carrier bandwidth is 180 kHz
  • one scheduling request occupies one subcarrier
  • symbol groups of the scheduling request in each repetition period in the figure are represented by gray-filled rectangles and numbers, and are denoted as a first symbol group, a second symbol group, a third symbol group, and a fourth symbol group in a time sequence, which are respectively represented by using numbers 1, 2, 3, and 4 in the figure.
  • the scheduling request has two types of frequency-hopping intervals in one repetition period: 3.75 kHz and 22.5 kHz.
  • the frequency-hopping interval is an integer multiple of a subcarrier bandwidth, and a minimum frequency-hopping interval and the subcarrier bandwidth are the same.
  • a frequency-hopping interval between the first symbol group and the second symbol group is 3.75 kHz
  • a frequency-hopping interval between the third symbol group and the fourth symbol group is 3.75 kHz.
  • a frequency-hopping interval between the second symbol group and the third symbol group is 22.5 kHz.
  • Pseudo random frequency-hopping is used between two time-continuous repetition periods.
  • a frequency-hopping interval between the two repetition periods is determined based on a pseudo random sequence, and an initialization seed of the pseudo random sequence is a cell identity or a function of a cell identity.
  • the scheduling request is transmitted in a single-carrier frequency-hopping manner. This may avoid mutual interference between narrowband physical random access channel (Narrowband Physical Random Access Channel, NPRACH) preamble (preamble) signals.
  • NPRACH narrowband Physical Random Access Channel
  • the scheduling request is transmitted in a single-carrier frequency-hopping manner, so that a configuration manner of a resource used to send the scheduling request is more flexible.
  • a person skilled in the art may set, based on an actual requirement, a frequency domain location for transmitting the scheduling request.
  • the frequency domain location is not limited to 12 subcarriers.
  • FIG. 4 is merely an example for description, and is not intended to constitute any limitation on the solutions of this application.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are the same.
  • the signal format of the scheduling request may reuse the design of the NPRACH preamble, to be specific, the scheduling request also uses a single-carrier frequency-hopping manner, and a frequency-hopping pattern is the same as an NPRACH preamble manner.
  • a subcarrier bandwidth, a quantity of symbol groups, a length of a cyclic prefix and a length of a symbol that are in a symbol group, and a quantity of symbols are the same as those of the NPRACH preamble.
  • a difference lies in that a sequence carried on each symbol of the NPRACH preamble is 1, and sequences carried on symbols in different symbol groups are 1.
  • sequences carried on different symbol groups of the scheduling request are different, sequences carried on different symbols in a same symbol group are the same, and different sequences carried on different symbol groups are used to indicate different amounts of uplink data.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are the same. Different sequences are carried on different symbol groups to indicate different amounts of uplink data. In this way, a step of separately reporting a BSR can be avoided. A process is simple, and a delay and power consumption are greatly reduced.
  • FIG. 6 is a schematic diagram of a signal format of a scheduling request according to an embodiment of this application. As shown in FIG. 6 , sequences carried on different symbol groups of the scheduling request are different. Sequences carried in the scheduling request are ⁇ a, b, c, d ⁇ , and a, b, c, and d are respectively carried on different symbol groups. Sequences carried on symbols in each symbol group are the same, and different sequences correspond to different amounts of uplink data.
  • a sequence carried in the scheduling request may be a Walsh sequence, which may also be referred to as Walsh code.
  • a Walsh sequence with a length of 4 may be selected.
  • Table 1 shows a correspondence between a sequence carried in the scheduling request and an uplink quantity. As shown in Table 1, there are four Walsh sequences with a length of 4, and a maximum of four Walsh sequences may be used to carry information about a 2-bit amount of uplink data.
  • BSR_0, BSR_1, BSR_2, and BSR_3 respectively represent four types of different amounts of uplink data.
  • BSR_0 is X0 bytes
  • BSR_1 is X1 bytes
  • BSR_2 is X2 bytes
  • BSR_3 is X3 bytes
  • BSR_0, BSR_1, BSR_2, and BSR_3 respectively represent different ranges of an amount of uplink data.
  • Some Walsh sequences may be selected to carry information about a 1-bit amount of uplink data.
  • Table 2 and Table 3 respectively represent another correspondence between a sequence carried in the scheduling request and an uplink quantity.
  • BSR_I and BSR_II respectively represent two different types of amounts of uplink data, for example, BSR_I is Z0 bytes, and BSR_II is Z1 bytes; and Z0 ⁇ Z1.
  • BSR_I and BSR_II respectively represent different ranges of the amount of uplink data, for example, W00 bytes ⁇ BSR_I ⁇ W01 bytes, and W10 bytes ⁇ BSR_II ⁇ W11 bytes; and W00 ⁇ W01 ⁇ W10 ⁇ W11. Specially, there may be no upper limit W11.
  • Table 2 a b c d BSR_I 1 1 1 1 BSR_II 1 -1 1 -1
  • Table 3 a b c d BSR_I 1 1 1 1 1 BSR_II 1 -1 -1 1
  • the scheduling request has two formats that respectively correspond to two cyclic prefix (Cyclic Prefix, CP) CP lengths.
  • Table 4 shows the two formats of the scheduling request.
  • TCP is a length of a cyclic prefix
  • TSEQ is total duration of five symbols in each symbol group.
  • FIG. 4 is merely an example.
  • Table 4 Scheduling request format TCP ( ⁇ s) TSEQ ( ⁇ s) Maximum cell radius (km) 0 66.7 5 x 266.67 10 1 266.67 5 x 266.67 40
  • a quantity of symbol groups in one repetition period is 4, and a case in which more symbol groups are supported in subsequent evolution is not excluded. Therefore, the quantity of symbol groups is not limited in this application.
  • a sequence carried on each symbol group of the scheduling request may be a Walsh sequence with a length of 8, and may carry information about a maximum of a 3-bit amount of uplink data.
  • the signal format of the scheduling request reuses a design of an NPRACH preamble, and is naturally compatible with an NPRACH, so that resource configuration of the scheduling request is more flexible.
  • a symbol of the NPRACH preamble is filled with a grid, and a symbol of the scheduling request is not filled.
  • different sequences are carried by using a symbol group as a granularity to indicate different amounts of uplink data, so as to avoid generating inter-subcarrier interference to the NPRACH.
  • FIG. 8 is a schematic diagram of another signal format of a scheduling request according to an embodiment of this application.
  • the scheduling request is transmitted in a single-carrier manner, a plurality of symbol groups in a repeated sending period of the scheduling request are located at a same subcarrier location, and a sending period of the scheduling request includes a plurality of repeated sending periods.
  • the sending period of the scheduling request includes the plurality of repeated sending periods.
  • the sending period of the scheduling request may be determined based on a parameter period in the resource configuration information, and a quantity of the repeated sending periods in the sending period may be determined based on a quantity of repetition times in the resource configuration information.
  • a plurality of symbol groups in the repeated sending period of the scheduling request are located at a same subcarrier location, and the plurality of symbol groups of the scheduling request may be located at a same subcarrier location or may be located at different subcarrier locations in different repeated sending periods. For example, in a scenario, one sending period is divided into a repeated sending period a, a repeated sending period b, and a repeated sending period c.
  • Subcarrier locations corresponding to different symbol groups in each repeated sending period are the same, and symbol groups between the repeated sending period a, the repeated sending period b, and the repeated sending period c may be located at a same subcarrier location or may be located at different subcarrier locations.
  • a change of subcarrier locations of symbol groups in different repetition periods of the scheduling request is determined based on a pseudo random sequence.
  • the pseudo random sequence may be an m sequence, an M sequence, a gold sequence, or the like.
  • a pseudo random sequence seed is a cell identifier or a function of a cell identifier.
  • different sequences are carried by using a symbol as a granularity to form different scheduling requests, and the scheduling requests are transmitted in a single-carrier manner.
  • a plurality of symbol groups in a repeated sending period of the scheduling request are located at a same subcarrier location. Therefore, a longer sequence can be formed, a code resource is richer, and a granularity of an amount of uplink data is finer.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are different.
  • the signal format of the scheduling request reuses a design of an NPRACH preamble, but a frequency-hopping design is removed.
  • a single-carrier manner is used.
  • a subcarrier bandwidth, a quantity of symbol groups, a length of the CP and a length of a symbol in a symbol group, and a quantity of symbols that are of the scheduling request are the same as those of the NPRACH preamble.
  • a sequence carried on each symbol of the NPRACH preamble is 1, and sequences carried on symbols in different symbol groups are 1.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are also different, so that a more refined scheduling request may be formed, to indicate a plurality of types of amounts of uplink data. Therefore, a resource allocated by a network device to a terminal device for sending uplink data is more accurate, and proper utilization of the resource is ensured.
  • all frequency domain resources allocated for transmitting the NPRACH preamble may be used to transmit the scheduling request; or the scheduling request may be transmitted on a resource, other than resources whose quantity is an integer multiple of resources in an NPRACH frequency-hopping range in all frequency domain resources allocated for transmitting an NPRACH preamble.
  • a symbol of the NPRACH preamble is filled with a grid, and a symbol of the scheduling request is not filled.
  • a frequency domain resource allocated for transmitting the NPRACH preamble is 24 subcarriers, and a frequency-hopping range of an NPRACH is 12 subcarriers.
  • a subcarrier 0 to a subcarrier 11 are used to transmit the NPRACH preamble, and a subcarrier 12 to a subcarrier 23 may be used to transmit the scheduling request.
  • a sequence carried in the scheduling request may be an m sequence, an M sequence, a ZC sequence, a Walsh sequence, or the like.
  • a ZC sequence with a length of 20 may be selected.
  • ZC sequences with different root factors, or ZC sequences with same root factors but different cyclic shifts, or ZC sequences with different root factors and different cyclic shifts separately represent different information about an amount of uplink data.
  • different sequences are carried on different symbols to indicate different amounts of uplink data, so that a delay and power consumption can be further reduced.
  • different sequences are carried by using a symbol as a granularity to form different scheduling requests. Therefore, a longer sequence can be used, a code resource is richer, and a granularity of an amount of uplink data can be finer.
  • FIG. 9 is a block diagram of a terminal device according to an embodiment of this application.
  • the terminal device may be configured to perform the technical solutions on a terminal device side in any one of the foregoing method embodiments.
  • the terminal device includes an obtaining module 11 and a sending module 12.
  • the obtaining module 11 is configured to obtain the resource configuration information, and the resource configuration information is used to indicate a resource used by the terminal device to send the scheduling request.
  • the sending module 12 is configured to send the scheduling request to a network device on the resource indicated by the resource configuration information obtained by the obtaining module 11, and a preset correspondence exists between a sequence carried in the scheduling request and an amount of uplink data that is requested to be sent by the terminal device to the network device.
  • the scheduling request includes a plurality of symbol groups in time domain, and each symbol group includes a cyclic prefix and at least one symbol.
  • the scheduling request is transmitted in a single-carrier frequency-hopping manner.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are the same.
  • the scheduling request is transmitted in a single-carrier manner, a plurality of symbol groups in a repeated sending period of the scheduling request are located at a same subcarrier location, and a sending period of the scheduling request includes a plurality of repeated sending periods.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are different.
  • the obtaining module 11 is specifically configured to receive the resource configuration information sent by the network device, or obtain the resource configuration information from a local cache.
  • the resource configuration information is configured by the network device for the terminal device when the terminal device is initialized.
  • FIG. 10 is a block diagram of a network device according to an embodiment of this application.
  • the network device may be configured to perform the technical solutions on a network device side in any one of the foregoing method embodiments.
  • the network device includes a receiving module 21 and a determining module 22.
  • the receiving module 21 is configured to receive, on a resource indicated by the resource configuration information, the scheduling request sent by the terminal device.
  • the resource configuration information is used to indicate the resource used by the terminal device to send the scheduling request, and a preset correspondence exists between a sequence carried in the scheduling request and an amount of uplink data that is requested to be sent by the terminal device to the network device.
  • the determining module 22 is configured to determine, based on the scheduling request received by the receiving module 21, the amount of uplink data that is requested to be sent by the network device.
  • the scheduling request includes a plurality of symbol groups in time domain, and each symbol group includes a cyclic prefix and a plurality of symbols.
  • the scheduling request is transmitted in a single-carrier frequency-hopping manner.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are the same.
  • the scheduling request is transmitted in a single-carrier manner, a plurality of symbol groups in a repeated sending period of the scheduling request are located at a same subcarrier location, and a sending period of the scheduling request includes at least one repeated sending period.
  • sequences carried on different symbol groups of the scheduling request are different, and sequences carried on different symbols in a same symbol group are different.
  • the resource configuration information is sent by the network device to the terminal device.
  • the resource configuration information is obtained by the terminal device from a local cache, and the resource configuration information is configured by the network device for the terminal device when the terminal device is initialized.
  • FIG. 11 is a block diagram of a terminal device according to an embodiment of this application.
  • the terminal device includes a processor 31 and a memory 32.
  • the memory 32 is configured to store an instruction
  • the processor 31 is configured to execute the instruction stored in the memory 32.
  • the terminal device is configured to perform the method on a terminal device side in any one of the foregoing embodiments.
  • an embodiment of this application further provides a network device.
  • a structural block diagram of the network device is the same as a structure in FIG. 11 .
  • the network device includes a processor 31 and a memory 32.
  • the memory 32 is configured to store an instruction
  • the processor 31 is configured to execute the instruction stored in the memory 32.
  • the network device is configured to perform the method on a network device side in any one of the foregoing embodiments.
  • This application further provides a readable storage medium, and the readable storage medium stores an instruction.
  • the terminal device executes the instruction, the terminal device performs the information transmission method provided in any one of the foregoing method embodiments.
  • This application further provides a readable storage medium, and the readable storage medium stores an instruction.
  • the network device executes the instruction, the network device performs the information transmission method provided in any one of the foregoing method embodiments.
  • the program product includes an instruction, and the instruction is stored in a readable storage medium.
  • At least one processor of a terminal device may read the instruction from the readable storage medium, and execute the instruction, to enable the terminal device to perform the information transmission method provided in any one of the method embodiments.
  • the program product includes an instruction, and the instruction is stored in a readable storage medium.
  • At least one processor of a network device may read the instruction from the readable storage medium, and execute the instruction, to enable the network device to perform the information transmission method provided in any one of the foregoing method embodiments.
  • This application further provides a network system, and the network system includes the terminal device and the network device in any one of the foregoing embodiments.
  • a processor may be a central processing unit (English: Central Processing Unit, CPU for short), or may be another general purpose processor, a digital signal processor (English: Digital Signal Processor, DSP for short), an application-specific integrated circuit (English: Application Specific Integrated Circuit, ASIC for short), or the like.
  • the general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the methods disclosed with reference to this application may be directly performed by a hardware processor, or may be performed by a combination of hardware and a software module in the processor.
  • the memory includes: a read-only memory (English: read-only memory, ROM for short), a RAM, a flash memory, a hard disk, a solid-state drive, a magnetic tape (English: magnetic tape), a floppy disk (English: floppy disk), an optical disc (English: optical disc), and any combination thereof.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
EP17918870.1A 2017-07-27 2017-07-27 Procédé et dispositif de transmission d'informations Active EP3651514B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/094783 WO2019019125A1 (fr) 2017-07-27 2017-07-27 Procédé et dispositif de transmission d'informations

Publications (3)

Publication Number Publication Date
EP3651514A1 true EP3651514A1 (fr) 2020-05-13
EP3651514A4 EP3651514A4 (fr) 2020-07-15
EP3651514B1 EP3651514B1 (fr) 2021-06-02

Family

ID=65039308

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17918870.1A Active EP3651514B1 (fr) 2017-07-27 2017-07-27 Procédé et dispositif de transmission d'informations

Country Status (4)

Country Link
US (1) US20200163111A1 (fr)
EP (1) EP3651514B1 (fr)
CN (1) CN110622597B (fr)
WO (1) WO2019019125A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6980899B2 (ja) * 2017-08-09 2021-12-15 エルジー エレクトロニクス インコーポレイティドLg Electronics Inc. ランダム接続過程を行う方法及びそのための装置
CN112333675B (zh) * 2020-11-25 2022-09-13 紫光展锐(重庆)科技有限公司 一种数据计数的方法及相关装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101123793B (zh) * 2006-08-09 2011-01-05 大唐移动通信设备有限公司 一种发送连续多个协议数据单元的方法及用户设备
CN101132628A (zh) * 2006-08-21 2008-02-27 北京三星通信技术研究有限公司 用于语音业务的调度请求传输方法及设备
CN101753181B (zh) * 2008-12-12 2015-04-29 电信科学技术研究院 一种数据传输方法、系统及装置
CN102685895B (zh) * 2011-03-11 2015-02-04 华为技术有限公司 一种上行数据的调度方法、系统及装置
CN106572543B (zh) * 2012-02-15 2020-10-23 华为技术有限公司 随机接入方法、基站及用户设备
WO2013166670A1 (fr) * 2012-05-09 2013-11-14 华为技术有限公司 Procédé et dispositif pour configurer les ressources d'un canal montant
US11582724B2 (en) * 2013-04-30 2023-02-14 Ntt Docomo, Inc. User equipment, base station, communication access method, and communication method
CN105451355B (zh) * 2014-08-18 2019-06-18 上海诺基亚贝尔股份有限公司 用于向自身服务的用户设备传输数据的方法、基站和系统
KR101999810B1 (ko) * 2014-08-25 2019-07-12 엘지전자 주식회사 무선 통신 시스템에서 스케줄링 요청 방법 및 이를 위한 장치
CN106954272A (zh) * 2016-01-07 2017-07-14 中兴通讯股份有限公司 一种资源调度方法、装置及系统
CN108811145A (zh) * 2017-05-04 2018-11-13 株式会社Ntt都科摩 发送和接收上行数据的方法、用户设备和基站

Also Published As

Publication number Publication date
WO2019019125A1 (fr) 2019-01-31
EP3651514A4 (fr) 2020-07-15
CN110622597B (zh) 2022-02-15
EP3651514B1 (fr) 2021-06-02
CN110622597A (zh) 2019-12-27
US20200163111A1 (en) 2020-05-21

Similar Documents

Publication Publication Date Title
US11388710B2 (en) Uplink information sending method and apparatus, downlink information sending method and apparatus, downlink information receiving method and apparatus and system scheduling method and apparatus
JP7306501B2 (ja) 基地局、基地局における方法、及び無線端末
CN111148263B (zh) 发送数据的方法及其装置
WO2013137699A1 (fr) Procédé et appareil de transmission en liaison montante
CN111133718A (zh) 在支持feNB-IOT操作的TDD中的上行链路传输
EP3364700B1 (fr) Procédé de transmission de données, dispositif de réseau et dispositif de terminal
US20200022090A1 (en) Communication Method, Terminal, And Network Device
EP4017177B1 (fr) Procédé et appareil de multiplexage de ressources
CN109600833B (zh) 一种确定传输资源的方法及设备
CN111586861A (zh) 一种随机接入方法、设备及系统
US20200163111A1 (en) Information transmission method and device
CN110971362B (zh) 一种发现参考信号发送方法及装置
EP3764711A1 (fr) Procédé et appareil d'attribution de ressources
WO2019157639A1 (fr) Procédé et appareil de transmission d'informations de harq, et support de stockage informatique
CN113728556B (zh) 一种通信方法及设备
EP4258796A1 (fr) Procédé de transmission d'informations, dispositif de terminal, dispositif de réseau et support de stockage d'ordinateur
US12022517B2 (en) Non-scheduling resource based data sending method and apparatus thereof
CN109565758B (zh) 通信方法和装置

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200203

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

A4 Supplementary search report drawn up and despatched

Effective date: 20200612

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 72/12 20090101ALI20200606BHEP

Ipc: H04L 5/00 20060101ALI20200606BHEP

Ipc: H04W 72/04 20090101AFI20200606BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20201223

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1399656

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210615

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602017039892

Country of ref document: DE

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210902

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20210602

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1399656

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210602

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210903

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210902

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211004

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602017039892

Country of ref document: DE

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210731

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210731

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220201

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210731

26N No opposition filed

Effective date: 20220303

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210727

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210802

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210727

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20170727

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230608

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210602