[go: up one dir, main page]

GB2589865A - Communication system - Google Patents

Communication system Download PDF

Info

Publication number
GB2589865A
GB2589865A GB1918025.6A GB201918025A GB2589865A GB 2589865 A GB2589865 A GB 2589865A GB 201918025 A GB201918025 A GB 201918025A GB 2589865 A GB2589865 A GB 2589865A
Authority
GB
United Kingdom
Prior art keywords
data
cell
pairing parameter
network
network access
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.)
Withdrawn
Application number
GB1918025.6A
Other versions
GB201918025D0 (en
Inventor
Laselva Daniela
Koziol Dawid
Yu Ling
Centenaro Marco
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to GB1918025.6A priority Critical patent/GB2589865A/en
Publication of GB201918025D0 publication Critical patent/GB201918025D0/en
Priority to PCT/EP2020/085029 priority patent/WO2021116082A1/en
Publication of GB2589865A publication Critical patent/GB2589865A/en
Withdrawn legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/08Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management

Landscapes

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

Abstract

There is provided a method for an apparatus, the method comprising: determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and using said pairing parameter to identify the at least one copy of the first data at a physical layer and/or at a medium access control layer of the apparatus

Description

COMMUNICATION SYSTEM
Field
[00011The present application relates to a method, apparatus, and computer program.
Background
[0002] A communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations/access nodes and/or other nodes by providing carriers between the various entities involved in the communications path. A communication system can be provided, for example, by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and/or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.
Summary
100031According to a first aspect, there is provided an apparatus comprising means for: determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and using said pairing parameter to control transmission of the first data in the first cell and/or the at least one copy of the first data in the second cell.
[0004] The apparatus may be a terminal accessing a network, comprising means for: receiving the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The apparatus may comprise means for: operating a first physical layer for receiving the first data; operating a second physical layer for receiving the at least one copy of the first data; and causing messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The apparatus may comprise means for: operating a first physical layer for receiving the first data; and using the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
10005] The apparatus may be a network access apparatus for facilitating access to a network, comprising means for: receiving the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
100061The pairing parameter may be a timing offset between the first time and the second time.
[0007] The apparatus may be at least part of network access apparatus, comprising means for: transmitting the pairing parameter and/or information for determining the pairing parameter to a terminal.
100081The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth pad in the cell defined by the first network access apparatus.
100091The first cell and the second cell may be provided by a same network access apparatus.
100101The first cell and the second cell may be respectively provided by different network access apparatuses.
[0011]According to a second aspect, there is provided an apparatus comprising means for: determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and using said pairing parameter to identify the at least one copy of the first data at a physical layer and/or at a medium access control layer of the apparatus.
100121The apparatus may be a terminal accessing a network, comprising means for: receiving the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The apparatus may comprise means for: operating a first physical layer for receiving the first data; operating a second physical layer for receiving the at least one copy of the first data; and causing messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The apparatus may comprise means for: operating a first physical layer for receiving the first data; and using the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
100131The apparatus may be a network access apparatus for facilitating access to a network, comprising means for: receiving the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
100141The pairing parameter may be a timing offset between the first time and the second time.
100151The apparatus may be at least pad of network access apparatus, comprising means for: transmitting the pairing parameter and/or information for determining the pairing parameter to a terminal.
100161The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus.
100171The first cell and the second cell may be provided by a same network access apparatus.
100181The first cell and the second cell may be respectively provided by different network access apparatuses.
[0019]According to a third aspect, there is provided a method for an apparatus, the method comprising: determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and using said pairing parameter to control transmission of the first data in the first cell and/or the at least one copy of the first data in the second cell.
100201When the apparatus is a terminal accessing a network, the method may comprise: receiving the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The method may comprise: operating a first physical layer for receiving the first data; operating a second physical layer for receiving the at least one copy of the first data; and causing messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The method may comprise: operating a first physical layer for receiving the first data; and using the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
100211When the apparatus is a network access apparatus for facilitating access to a network, the method may comprise: receiving the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
100221The pairing parameter may be a timing offset between the first time and the second time.
100231When the apparatus is at least part of network access apparatus, the method may comprise: transmitting the pairing parameter and/or information for determining the pairing parameter to a terminal.
100241The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus.
100251The first cell and the second cell may be provided by a same network access apparatus.
100261The first cell and the second cell may be respectively provided by different network access apparatuses.
[0027] According to a fourth aspect, there is provided a method for an apparatus, the method comprising: determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and using said pairing parameter to identify the at least one copy of the first data at a physical layer and/or at a medium access control layer of the apparatus.
[0028] When the apparatus is a terminal accessing a network, the method may comprise: receiving the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The method may comprise: operating a first physical layer for receiving the first data; operating a second physical layer for receiving the at least one copy of the first data; and causing messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The method may comprise: operating a first physical layer for receiving the first data; and using the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
[0029] When the apparatus is a network access apparatus for facilitating access to a network, the method may comprise: receiving the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
[0030] The pairing parameter may be a timing offset between the first time and the second time.
1003111Nhen the apparatus is at least part of network access apparatus, the method may comprise: transmitting the pairing parameter and/or information for determining the pairing parameter to a terminal.
100321The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus.
[00331The first cell and the second cell may be provided by a same network access apparatus.
[00341The first cell and the second cell may be respectively provided by different network access apparatuses.
[0035] According to a fifth aspect, there is provided an apparatus comprising at least one processor, and at least one memory comprising code that, when executed on the at least one processor, causes the apparatus to: determine a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and use said pairing parameter to control transmission of the first data in the first cell and/or the at least one copy of the first data in the second cell.
[0036] The apparatus may be a terminal accessing a network, and be further caused to: receive the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The apparatus may be further caused to: operate a first physical layer for receiving the first data; operate a second physical layer for receiving the at least one copy of the first data; and cause messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The apparatus may be further caused to: operate a first physical layer for receiving the first data; and use the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
[0037] The apparatus may be a network access apparatus for facilitating access to a network, and be further caused to: receive the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
100381The pairing parameter may be a timing offset between the first time and the second time.
100391The apparatus may be at least part of network access apparatus, and be further caused to: transmit the pairing parameter and/or information for determining the pairing parameter to a terminal.
100401The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus.
100411The first cell and the second cell may be provided by a same network access apparatus.
100421The first cell and the second cell may be respectively provided by different network access apparatuses.
10043] According to a sixth aspect, there is provided an apparatus comprising at least one processor, and at least one memory comprising code that, when executed on the at least one processor, causes the apparatus to: determine a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and use said pairing parameter to identify the at least one copy of the first data at a physical layer and/or at a medium access control layer of the apparatus. 100441The apparatus may be a terminal accessing a network, and be further caused to: receive the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The apparatus may be further caused to: operate a first physical layer for receiving the first data; operate a second physical layer for receiving the at least one copy of the first data; and cause messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The apparatus may be further caused to: operate a first physical layer for receiving the first data; and use the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
100451The apparatus may be a network access apparatus for facilitating access to a network, and be further caused to: receive the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
100461The pairing parameter may be a timing offset between the first time and the second time.
10047] The apparatus may be at least part of network access apparatus, and be further caused to: transmit the pairing parameter and/or information for determining the pairing parameter to a terminal.
100481The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus.
100491The first cell and the second cell may be provided by a same network access apparatus.
100501The first cell and the second cell may be respectively provided by different network access apparatuses.
[0051]According to a seventh aspect, there is provided an apparatus comprising: determining circuitry for determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and using circuitry for using said pairing parameter to control transmission of the first data in the first cell and/or the at least one copy of the first data in the second cell.
100521The apparatus may be a terminal accessing a network, comprising: receiving circuitry for receiving the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The apparatus may comprise: operating circuitry for operating a first physical layer for receiving the first data; operating circuitry for operating a second physical layer for receiving the at least one copy of the first data; and causing circuitry for causing messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The apparatus may comprise: operating circuitry for operating a first physical layer for receiving the first data; and using circuitry for using the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
100531 The apparatus may be a network access apparatus for facilitating access to a network, comprising: receiving circuitry for receiving the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
100541The pairing parameter may be a timing offset between the first time and the second time.
100551The apparatus may be at least part of network access apparatus, comprising: transmitting circuitry for transmitting the pairing parameter and/or information for determining the pairing parameter to a terminal.
100561The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus.
100571The first cell and the second cell may be provided by a same network access apparatus.
100581The first cell and the second cell may be respectively provided by different network access apparatuses.
10059] According to an eighth aspect, there is provided an apparatus comprising: determining circuitry for determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and using circuitry for using said pairing parameter to identify the at least one copy of the first data at a physical layer and/or at a medium access control layer of the apparatus. 100601 The apparatus may be a terminal accessing a network, and be further caused to: receive the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The apparatus may be further caused to: operate a first physical layer for receiving the first data; operate a second physical layer for receiving the at least one copy of the first data; and cause messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The apparatus may be further caused to: operate a first physical layer for receiving the first data; and use the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
100611The apparatus may be a network access apparatus for facilitating access to a network, and be further caused to: receive the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
100621The pairing parameter may be a timing offset between the first time and the second time.
10063] The apparatus may be at least part of network access apparatus, and be further caused to: transmit the pairing parameter and/or information for determining the pairing parameter to a terminal.
100641The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus.
100651The first cell and the second cell may be provided by a same network access apparatus.
100661The first cell and the second cell may be respectively provided by different network access apparatuses.
100671According to a seventh aspect, there is provided an apparatus comprising: determining circuitry for determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and using circuitry for using said pairing parameter to control transmission of the first data in the first cell and/or the at least one copy of the first data in the second cell.
100681The apparatus may be a terminal accessing a network, comprising: receiving circuitry for receiving the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The apparatus may comprise: operating circuitry for operating a first physical layer for receiving the first data; operating circuitry for operating a second physical layer for receiving the at least one copy of the first data; and causing circuitry for causing messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The apparatus may comprise: operating circuitry for operating a first physical layer for receiving the first data; and using circuitry for using the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
100691The apparatus may be a network access apparatus for facilitating access to a network, comprising: receiving circuitry for receiving the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
100701The pairing parameter may be a timing offset between the first time and the second time.
100711The apparatus may be at least part of network access apparatus, comprising: transmitting circuitry for transmitting the pairing parameter and/or information for determining the pairing parameter to a terminal.
100721The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus.
100731The first cell and the second cell may be provided by a same network access apparatus.
[00741The first cell and the second cell may be respectively provided by different network access apparatuses.
[0075] According to a ninth aspect, there is provided a computer program comprising program instructions for causing a computer to perform any method as described above.
100761According to a tenth aspect, there is provided a computer program product stored on a medium may cause an apparatus to perform any method as described herein.
100771According to an eleventh aspect, there is provided an electronic device that may comprise apparatus as described herein.
[0078] According to a twelfth aspect, there is provided a chipset that may comprise an apparatus as described herein.
[0079] According to a thirteenth aspect, there is provided non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: determine a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and use said pairing parameter to control transmission of the first data in the first cell and/or the at least one copy of the first data in the second cell.
[0080] The apparatus may be a terminal accessing a network, and be further caused to: receive the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The apparatus may be further caused to: operate a first physical layer for receiving the first data; operate a second physical layer for receiving the at least one copy of the first data; and cause messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The apparatus may be further caused to: operate a first physical layer for receiving the first data; and use the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
100811The apparatus may be a network access apparatus for facilitating access to a network, and be further caused to: receive the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
100821The pairing parameter may be a timing offset between the first time and the second time.
100831The apparatus may be at least part of network access apparatus, and be further caused to: transmit the pairing parameter and/or information for determining the pairing parameter to a terminal.
100841The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus.
100851The first cell and the second cell may be provided by a same network access apparatus.
100861The first cell and the second cell may be respectively provided by different network access apparatuses.
100871According to a fourteenth aspect, there is provided non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: determine a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and use said pairing parameter to identify the at least one copy of the first data at a physical layer and/or at a medium access control layer of the apparatus.
100881The apparatus may be a terminal accessing a network, and be further caused to: receive the pairing parameter and/or information for determining the pairing parameter from a network access apparatus. The apparatus may be further caused to: operate a first physical layer for receiving the first data; operate a second physical layer for receiving the at least one copy of the first data; and cause messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating decoding of the first data. The apparatus may be further caused to: operate a first physical layer for receiving the first data; and use the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
100891The apparatus may be a network access apparatus for facilitating access to a network, and be further caused to: receive the pairing parameter and/or information for determining the pairing parameter from another network access apparatus. The network access apparatus may host at least one higher protocol layer of an access point and wherein the another network access apparatus may host at least one lower protocol layer of the access point. The network access apparatus may provide a first access point and wherein the another network access apparatus may provide a second access point.
100901The pairing parameter may be a timing offset between the first time and the second time.
100911The apparatus may be at least part of network access apparatus, and be further caused to: transmit the pairing parameter and/or information for determining the pairing parameter to a terminal.
100921The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus.
100931The first cell and the second cell may be provided by a same network access apparatus.
100941The first cell and the second cell may be respectively provided by different network access apparatuses.
Description of Figures
100961 Examples will now be described, by way of example only, with reference to the accompanying Figures in which: [0097] Figure 1 shows a schematic diagram of an example communication system comprising a plurality of base stations and a plurality of communication devices; 100981 Figure 2 shows a schematic diagram of an example mobile communication device; 100991 Figure 3 shows a schematic diagram of an example network element; [00100] Figures 4 to 7 show schematic diagrams of example communication systems; 1001011 Figure 8 shows a schematic diagram of time-frequency resources that may be respectively allocated by a first and a second transmission/reception point; 1001021 Figure 9 shows a schematic diagram of an example communication system; 1001031 Figures 10 and 11 show potential pairing parameters; [00104] Figure 12 shows a potential signalling diagram; and [00105] Figures 13 and 14 show potential flow charts for operation by an apparatus, such as a radio access network apparatus and/or a terminal accessing a network through a radio access network apparatus.
Detailed description
[00106] In general, the following disclosure relates transmitting redundant copies of data for improving reliability of data transmissions. In particular, the following relates to indicating a pairing of radio resources for transmitting/receiving data and a copy of the data. This pairing indication may be used by a physical layer of the receiving entity to identify the copy of the data. The pairing indication may be used by a medium access control layer of the receiving entity to identify the copy of the data. The pairing entity may be used by both the physical layer and the medium access control layer of the receiving entity to identify the copy of the data. Once the copy of the data has been identified, operations may be performed to combine the data with its copy with the aim of improving a reliability of the reception of the transmitted data.
[00107] Further features of this are discussed below in examples.
[00108] Before explaining in detail the examples, certain general principles of a wireless communication system and mobile communication devices are briefly explained with reference to Figures 1 to 2 to assist in understanding the technology underlying the described examples.
[00109] In a wireless communication system 100, such as that shown in figure 1, mobile communication devices, user apparatus, or terminal 102, 104, 105 are provided wireless access via at least one base station or similar wireless transmitting and/or receiving node or point. A user can access the communication system by means of an appropriate communication device or terminal. A communication device of a user is often referred to as user equipment (UE) or as a user apparatus. Throughout the following, these terms will be used interchangeably. It is understood that the term "terminal" is used to cover communication devices that may access a network through an access node, and which may or may not have a user. Examples of such terminals without a user include devices that make machine-to-machine transmissions in a factory. A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users. The communication device may access a carrier provided by a station or access node, and transmit and/or receive communications on the carrier.
[00110] The communication system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and/or parameters which shall be used for the connection are also typically defined. One example of a communications system is UTRAN (3G radio). An example of attempts to solve the problems associated with the increased demands for capacity is an architecture that is known as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. The LTE standard is developed by the 3rd Generation Partnership Project (3GPP). LTE was first released in 2008 (known as LTE Release 8), and new enhancements On form of releases) has been introduced since then. LTE Release 13 and onwards is also known as LTE Advanced Pro. Another example of communications system is 5G system and New Radio (NR) radio interface, which is the latest 3GPP development.
[00111] A base station is referred to as an eNodeB (eNB) in LTE and as a gNodeB (gNB) in New Radio, and may be referred to more generally as simply a network apparatus or a network access node. Base stations are typically controlled by at least one appropriate controller apparatus, so as to enable operation thereof and management of mobile communication devices in communication with the base stations. The controller apparatus may be located in a radio access network (e.g. wireless communication system 100) or in a core network (CN) (not shown) and may be implemented as one central apparatus or its functionality may be distributed over several apparatus. The controller apparatus may be part of the base station and/or provided by a separate entity such as a Radio Network Controller. In Figure 1 control apparatus 108 and 109 are shown to control the respective macro level base stations 106 and 107. In some systems, the control apparatus may additionally or alternatively be provided in a radio network controller.
[00112] 3GPP systems may however be considered to have a so-called "flat" architecture, without the provision of RNCs; rather the (e)/(g)NB is in communication with a system architecture evolution gateway (SAE-GW) and a mobility management entity (MME), which entities may also be pooled meaning that a plurality of these nodes may serve a plurality (set) of (e)/(g)NBs. Each user apparatus is served by only one MME and/or S-OW at a time and the (e)/(g)NB keeps track of current association. SAE-GW is a "high-level" user plane core network element in LTE, which may comprise the S-OW and the P-GW (serving gateway and packet data network gateway, respectively). The functionalities of the S-GW and P-OW are separated, and they are not required to be co-located. For 50 systems, in the 5G core the above-mentioned network entities are denoted User Plane Function (UPF) and Access and Mobility Management Function (AMF). The UPF is in charge of the user plane connectivity in the core and the AMF is in charge of access-related control plane functions in the core.
[00113] In a 3GPP system, radio resource control (RRC) is defined to be a sublayer of radio interface Layer 3 that exists in the control plane only, and which provides information transfer service to the non-access stratum (an example is provided in 3GPP Technical Specification Group Services and System Aspects 21.905). RRC is a protocol layer between a user apparatus and a base station, and is in charge of, for example, paging the user apparatus when traffic comes, establishing/maintaining or release of radio links (establishing an RRC connection between user apparatus and (e)/(g)NB), user apparatus mobility, user apparatus measurement configuration and user apparatus reporting configuration, etc. RRC is also responsible for controlling the configuration of radio interface Layers 1 and 2.
1001141 In Figure 1 base stations 106 and 107 are shown as connected to a wider communications network 113 via gateway 112. A further gateway function may be provided to connect to another network.
[00115] The smaller base stations 116, 118 and 120 may also be connected to the network 113, for example by a separate gateway function and/or via the controllers of the macro level stations. The base stations 116, 118 and 120 may be pico or femto level base stations or the like. In the example, base stations 116 and 118 are connected via a gateway 111 whilst station 120 connects via the controller apparatus 108. In some examples, the smaller stations may not be provided. It is understood that this is just an example communication system, and other network structures may be defined by an operating communication protocol.
[00116] A possible mobile communication device will now be described in more detail with reference to Figure 2 showing a schematic, partially sectioned view of a communication device 200. Such a communication device is often referred to as user equipment, apparatus or terminal. An appropriate mobile communication device may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is known as a 'smart phone', a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or a tablet provided with wireless communication capabilities, or any combinations of these or the like. Other non-limiting examples include apparatuses that may be used for Industrial Internet of things applications, such as, for example, smart robotics, assembly devices, warehouse-based devices, intelligent logistics, etc. A mobile communication device may provide, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and so on. Users may thus be offered and provided numerous services via their communication devices. Non-limiting examples of these services comprise two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. Users may also be provided broadcast or multicast data. Non-limiting examples of the content comprise downloads, television and radio programs, videos, advertisements, various alerts and other information. It is understood that although a "mobile" communication device is referred to in the above and in the following, that the communication device may be stationary for extended periods of time.
[00117] The mobile device 200 may receive signals over an air or radio interface 207 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In Figure 2 transceiver apparatus is designated schematically by block 206. The transceiver apparatus 206 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.
[00118] A mobile device is typically provided with at least one data processing entity 201, at least one memory 202 and other possible components 203 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The data processing, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 204. The user may control the operation of the mobile device by means of a suitable user interface such as key pad 205, voice commands, touch sensitive screen or pad, combinations thereof or the like. A display 208, a speaker and a microphone can be also provided. Furthermore, a mobile communication device may comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto. The communication devices 102, 104, 105 may access the communication system based on various access techniques.
[00119] An example of wireless communication systems are architectures standardized by the 3rd Generation Partnership Project (3GPP). A latest 3GPP based development is often referred to as the 5th Generation (5G) New Radio (NR). Other examples of radio access system comprise those provided by base stations of systems that are based on technologies such as wireless local area network (WLAN) and/or WiMax (Worldwide Interoperability for Microwave Access). A base station can provide coverage for an entire cell or similar radio service area.
[00120] An example network equipment for the 3GPP system is shown in Figure 3. Figure 3 shows an example of a control apparatus 300 for a communication system, for example to be coupled to and/or for controlling a station of an access system, such as a radio access network node, e.g. a base station or (g) node B, or a node of a core network such as an MME or Access and Mobility Management Function (AMF). The method may be implanted in a single control apparatus or across more than one control apparatus. The control apparatus may be integrated with or external to a node or module of a core network or radio access network. In some examples, base stations comprise a separate control apparatus unit or module. In other examples, the control apparatus can be another network element such as a radio network controller or a spectrum controller. In some examples, each base station may have such a control apparatus as well as a control apparatus being provided in a radio network controller. The control apparatus 300 can be arranged to provide control on communications in the service area of the system. The control apparatus 300 comprises at least one memory 301, at least one data processing unit 302, 303 and an input/output interface 304. Via the interface the control apparatus can be coupled to a receiver and a transmitter of the base station. The receiver and/or the transmitter may be implemented as a radio front end or a remote radio head. For example, the control apparatus 300 can be configured to execute an appropriate software code to provide the control functions. Control apparatus 300 may be included in a chipset or modem apparatus. A chipset or modem apparatus which includes apparatus 300 may be included in a control node such as a gNB.
[00121] It is understood that although the example network element is shown as a single apparatus, that the functions of the network element may be split amongst several distinct apparatuses. For example, the functions of a gNB may be split up into a centralised unit (labelled as gNB-CU) and at least one distributed unit (labelled as a gNB-DU). The centralised unit may host the radio resource control (RRC) layer, the Service Data Adaptation Protocol (SDAP) layer, and the Packet Data Convergence Protocol (PDCP) Layer. The distributed unit may host the radio link control (RLC) layer, the Medium Access Control (MAC) layer, and the Physical (PHY) layer. An interface labelled as an Fl interface may connect the gNB-CU with at least one of its gNB-DUs.
[00122] 5G New Radio is a communication architecture and set of protocols defined by 3GPP (following 2G, 3G, 4G). One of the aims of 5G is to support networks that use an extremely high reliability for communication, such as industrial networks in the context of Industrial Internet of Things (loT). The "Internet of Things" refers to a system of interrelated computing devices, mechanical and digital machines, etc. that have an ability to transfer data over a network without requiring user interaction. Examples of Industrial loT use cases include the domains of factory automation, transport industry, and electric power distribution.
[00123] One way of achieving a higher reliability of communication is to introduce redundancy into the communication system. For example, multiple copies of the same data may be transmitted through distinct transmission legs (e.g. radio links) to exploit diversity, rendering at least one of these transmissions a "redundant" transmission. Sometimes, the term "redundant transmission" is used to comprise the original data transmission as well as the copy of the data transmission. In the event that at least one of these copies is received incorrectly (e.g. due to a radio failure caused by interference), it may be combined with at least one other received copy to determine what was likely transmitted.
[00124] 3GPP has considered providing redundancy at different network domains and layers of a protocol stack. For example, two redundancy mechanisms employable at the Radio Access Network (RAN) part of the network have been considered.
[00125] Redundancy may be employed at the RAN part of the network using multi-transmission-reception points (Multi-TRP) transmissions and physical layer duplication. In this case, physical transmissions of a data packet from multiple TRPs may be made to a user equipment/terminal following coordination by the RAN. This may be performed using joint transmission and reception techniques, similar to Coordinated Multipoint-based (CoMP) techniques.
1001261 This is illustrated with respect to Figure 4.
1001271 Figure 4 illustrates a 5G core network 401 providing data 402 to a radio access network 403. The radio access network 403 comprises a gNB 404 having at least two transmission points, 405a, 405b. Each transmission point 405a, 405b is shown having a respective link 406a, 406b at the physical layer to terminal 407, each of the respective links 406a, 406b having the same frequency component(s) as each other.
[00128] Redundancy may also or alternatively be employed at the RAN part of the network at a packet data convergence protocol (PDCP) layer.
[00129] The PDCP layer is a layer above the physical layer (layer 1), the medium access control (MAC) layer (layer 2), and the radio link control (RLC) layer (layer 2). The physical layer may carry information from the MAC transport channels over the air interface, and may take care of link adaption, power control, cell search and other measurement processes for a radio resource control layer (layer 3). The MAC may perform mapping between logical channels and transport channels, scheduling information reporting, error correction through Hybrid Automatic Repeat Request, and performing priority handling of scheduling. The RLC may be responsible for transfer of upper layer protocol data units (PDUs), for reordering RLC data PDUs, for detecting duplicate transmissions at the RLC layer and for performing discard operations.
[00130] PDUs are transmitted in PDU sessions. A PDU session is a logical connection between an accessing terminal and a data network through the 5G network. A PDU session is established for a UE to receive services from the data network. 3GPP Technical Specifications 23.501 and 23.502 relate to PDU sessions. In 5G Core network architecture proposals, various PDU session types are supported, such as IPv4, IPv6, Ethernet, etc. Unlike the other communication protocols in which at least one default session is always created while the terminal attaches to the network, the 5G Core network may establish a session when service is needed independently of the attachment procedure of the terminal. This means that attachment by a terminal to a network without any PDU session is possible. The proposed 5G Core network also supports a terminal establishing multiple PDU sessions to the same data network or to different data networks over a single or multiple access networks including 3GPP and non-3GPP accesses. The number of user plane functions that are used for a PDU session is not specified. At least one user plane function is used to serve a given PDU session. For a terminal with multiple PDU sessions, there is no need for a convergence point, which means that the user plane paths of different PDU sessions may be completely disjointed/independent. This implies that there is a distinct buffering node per PDU session for the terminal in the RRC-IDLE state.
[00131] To perform redundancy at the PDCP layer, packets may be duplicated at the PDCP layer, with the subsequent transmission of these identical data being uncoordinated by multiple cells.
[00132] The PDCP duplication may be performed via carrier aggregation when the transmitting cells are component carriers within the same gNB. In this case, the PDCP layer of the gNB duplicates the packet from higher layers and forwards each duplicate to distinct RLC entities that are associated with independent, respective component carriers. This is illustrated with respect to Figure 5A.
[00133] Figure 5A illustrates a 5G core network 501 providing data 502 to a radio access network 503. The radio access network 503 comprises a gNB 504 having at least two RLCs, MACs and PHYs, 505a, 505b being provided information from a single PDCP layer 506. Each of the at least two RLCs, MACs and PHYs, 505a, 505b is shown having a respective link 507a, 507b at the physical layer to terminal 508, each of the respective links 507a, 507b having different frequency component(s) to each other.
[00134] The PDCP duplication may be performed via dual connectivity when the transmitting cells belong to two distinct gNBs. In this case, the node hosting the PDCP layer is in charge of duplicating a PDCP protocol data unit and forwarding it to an assisting node. The hosting node may be a cell in the master cell group of a master gNB, and the assisting node may be a cell in the secondary group of a secondary gNB. This is illustrated with respect to Figure 5B.
[00135] Figure 5B illustrates a 5G core network 501 providing data 502 to a radio access network 503. The radio access network 503 comprises a first gNB 504a hosting a PDCP layer 505 and a second gNB 504b hosting the associated RLC layer(s). The PDCP layer 505 provides duplicates of the data to be transmitted to an RLC layer 506a of the first gNB 504a, and to an RLC layer 505b of the second gNB 504b. Physical layers of each of the first gNB and the second gNB have a respective link 507a, 507b to terminal 508, each of the respective links 507a, 507b having different frequency component(s) to each other.
1001361 Various documents have discussed PDCP duplication. For example, 3GPP Re115 covers PDCP duplication in 3GPP TS 38.323 and in 3GPP TS 38.423 / 36.423.
1001371 3GPP Re116 TR 38.825 discussed a need of enhancements of PDCP data duplication. Based on Re116 TR 38.825, a Re116 Work Item is ongoing, which has in scope an objective to specify enhancements for more efficient downlink PDCP duplication, provided that gains can be confirmed with a reasonable complexity.
[00138] Redundancy may also be introduced at higher-layers and outside the RAN. For example, 3GPP has been defining higher layer connectivity schemes, in which there may be redundant end-to-end paths between the data network and the terminal or redundant paths between the UPF and 5G RAN. Duplication of data/information may then, for example, be implemented by a frame replication and elimination entity for Reliability (FRER) according to the IEEE P802.1C standard, which uses two independent protocol data unit sessions for the redundant data to be transmitted. The hardware reliability of the receiving terminal may be addressed by introducing a second UE in the same terminal (i.e. by use of a multi-UE device). This is illustrated with respect to Figure 6.
[00139] Figure 6 shows an application/host 601 providing respective copies of the same FRER data to different 5G core networks 602a, 602b. Each of these core networks 602a, 602b forwards the data to respective gNBs 603a, 603b, which in turn forward the data to a terminal 604 using respective communication links (wherein the respective communication links may operate at different component frequencies).
[00140] Although these techniques are discussed in terms of downlink data, it is understood that they are applicable in both the downlink and uplink direction.
[00141] Higher layer duplication is discussed in a variety of documents.
[00142] For example, 3GPP technical reports such as 3GPP Rel-16 TR 23.725 contains details regarding the architecture for higher-layer multi-connectivity solutions (aka higher-layer duplication) and proposes several architectures. 3GPP Rel-16 TR 23.725 discusses requirements for time-sensitive networks and deterministic ultra-reliable low latency communications.
1001431 Various 3GPP technical documents have further related to such issues, such as R3-192107 and R3-191567. In these cases, it was concluded that a 5G core network may signal to a Master gNB which PDU sessions are paired together, thus carrying duplicated packets, using a Redundancy Sequence Number. The Master gNB may then decide a final allocation of PDU sessions to the Master gNB and the Secondary gNB. It was further proposed that coordination between a Master gNB and a Secondary gNB may be performed by each entity informing each other of which P DU sessions are paired.
[00144] Finally, Time Sensitive Communication (TSC) Assistance Information (TSCAI) is described in Section 5.27.2 of 3GPP TS 23.501. TSCAI describes the TSC traffic characteristics for use in a communication system. Knowing a traffic pattern, particularly for a time sensitive network, is useful as it allows a gNB to more efficiently schedule periodic deterministic traffic flows (e.g. via Configured Grants, dynamic grants, and/or Semi-Persistent Scheduling). TSCAI, which may be provided on establishing a Quality of Service flow is defined in this document, Table 5.27.2-1 of which is reproduced below: Table 5.27.2-1: TSC Assistance Information
Assistance Information Description
Flow Direction The direction of the TSC flow (uplink or downlink) Periodicity It refers to the time period between start of two bursts.
Burst Arrival time The arrival time of the data burst at either the ingress of the RAN (downlink flow direction) or egress interface of the UE (uplink flow direction).
[00145] With semi-persistent scheduling (SPS) allocations, a gNB can configure a user equipment/terminal to have pre-allocated periodic radio resources available for transmissions in the downlink. This may be signaled using radio resource control signaling. By pre-allocating periodic radio resources, this means that these allocations do not require dynamic control signaling (DCI) to be associated to each transmission. This is referred also to a grant-free scheme. When the periodic transmissions being made refer to periodic transmissions made by the terminal/user equipment to a gNB/access network (i.e. uplink transmissions), this is referred to as configured grant (CG) configurations. 3GPP Release-16 currently specifies a possibility to configure multiple SPSs and CGs for a UE. A CG and/or semi-persistent scheduling configuration of a cell may include an offset parameter that defines the transmission timing of the CG/semi-persistent scheduling allocations with respect to a reference timing within the given cell. Throughout the following, it is understood that that the term semi-persistent scheduling allocations also covers configured grants, as they may both be a form of resources that are assigned to a terminal/entity for transmitting/receiving on a periodic basis.
[00146] Given the variety of duplication schemes that operate at different levels/layers, it may be useful to provide some coordination between these duplication schemes to avoid wasting resources (e.g. due to too many duplicates being transmitted unnecessarily, resulting in increased interference and scheduling delays), and in turn to improve efficiency.
[00147] When data duplication is performed (e.g. at PDCP and higher-layer duplication), that duplication may only be detected by the layer/entity that performed the duplication and its reverse operations. For PDCP duplication, this means that two packets carried in different PHY transmissions are identified as duplicates when they reach the PDCP layer (and not earlier, i.e. not in lower protocol layers) because their PDCP header comprises a same sequence number. For higher-layer duplication, two packets carried in different PHY transmissions are identified as duplicates when they reach the entity that is managing the frame replication and elimination.
[00148] Consequently, the physical layer at the receiver is unaware that two distinct PHY transmissions carry duplicates of the same packet, meaning that packet duplication cannot be recognised at the physical layer whenever duplication is performed at higher layers in the protocol stack.
[00149] This is illustrated with respect to Figure 7.
[00150] Figure 7 shows a host 701 comprising a frame replication and elimination entity 702 that sends first data along path 703a to a first core network 704a, and a copy of the first data along path 703b to a second core network 704b. Each of the core networks 704a, 704b passes its received data to a respective protocol stack 705a, 705b of a respective gNB 706a, 706b. The physical layers are shown transmitting this received data to protocol stack 708 of a terminal 707. As shown therein, the transmission from gNB 706a to the terminal 707 results in the loss of a first part of the transmitted data, while the transmission from the gNB 706b to the terminal 707 results in the loss of the first part and a second part of the transmitted data. The loss of the transmitted data isn't discovered until it is received/processed by a frame replication and elimination entity 709 in the terminal.
[00151] Thus, Figure 7 illustrates a higher-layer duplication mechanism, with host 701 transmitting data to a single user equipment 707 at an end device in the downlink. Two independent PDU sessions for the same data frame are set by the host 701 frame replication and elimination entity, which duplicates each data frame and transfers the frame and its copy to the PDU sessions. As shown in Figure 7, duplicated packets are recognised by the terminal's frame replication and elimination entity 709, which may simply discard one of the duplicates of the same packet before passing the frame to the higher layers. The first packet in the frame transmitted by gNB 706a is lost, but its copy transmitted by gNB 706b is received correctly. On the other hand, the third/last packet in the frame shown is lost in each of the transmissions made by gNBs 706a, 706b. The user equipment 707 is unable to recognise that the third "lost"/corrupted packets received from the different paths represent the same data. This means that the user equipment 707 is unable to combine them to increase the probability of successfully decoding the packet.
[00152] The following will provide a brief discussion of soft combining for increasing reliability of receiving packets.
[00153] The Hybrid Automatic Repeat Request (HARQ) technique is described in 3GPP Technical Specifications, such as 3GPP TS 38.321 and 3GPP TS 36.321. It may be used in 3GPP radio systems such as LTE and 5G New Radio. Essentially, HARQ is an error-controlling technique that allows combining across multiple transmissions having the same HARQ process identifier by having each HARQ process associated with a HARQ buffer. An example combining technique is soft combining. In case of transmission failure, a HARQ process in the receiving entity stores the received MAC PDU(s) related to the failed transmission(s) in an associated HARQ buffer and combines it with any new transmission for the same TB (i.e. retransmission). The soft combining means that soft values of the data after decoding are combined rather than the signal/energy of a PHY transmissions. Basically, the marginal posterior probabilities of received bits (so called soft bits or soft bit values) are stored in a HARQ buffer in the form of log-likelihood ratios (LLR), in order to combine the information received across different retransmissions, thus increasing the probability of successful packet decoding.
1001541 As per 3GPP TS 38.321, currently a terminal's MAC entity operates with multiple HARQ processes for each carrier, up to a maximum number of HARQ processes (e.g. 16). The network conveys the HARQ information associated to a transmission over a component carrier in the downlink control information such that the terminal can buffer a packet at the right HARQ buffer in order to enable soft combining. The HARQ information for downlink link shared channel transmissions or for uplink shared channel transmissions may comprise a HARQ process number/ID, a New Data Indicator (NDI) (for example, having the value X for original data, where X=0 or 1, and X for any corresponding retransmission; this means that the NDI value is not toggled across the retransmission process), and Redundancy Version (RV, 0 for original data and incrementing RV value for retransmissions).
[00155] These HARQ soft combining operations are intra-node (intra-gNB) and intra-cell, in which case there is no ambiguity for the receiver end (e.g. UE) in terms of what transmissions to combine and when.
[00156] Now, soft combining support for PDCP duplication is discussed.
1001571 Basic mechanisms to allow soft combining with PDCP duplication may be based on creating pointers to the corresponding HARQ processes at a Master gNB and at a Secondary gNB, and on the notion of a "combining window," respectively.
1001581 Now, physical layer combining techniques are discussed.
1001591 We consider 3G soft/softer handover, joint transmission Coordinated Multipoint and Multiple transmission point transmissions.
[00160] In 3G, a user equipment may communicate simultaneously with more than one NB/cell operating at the same frequency during the handover process. The energy associated with the physical layer transmissions is combined using a RAKE receiver capability of the user equipment (a RAKE receiver is a receiver that comprises several correlators, each correlator being assigned to a respective and different multipath component). The combination utilizes synchronization of the transmissions to be combined, where such coordination is allowed by the presence of a radio network controller in the access network. Similar techniques to this 3G case may be applied to 5G cases, such as those involving multiple transmission point transmissions, joint transmission Coordinated Multipoint in LTE and multi-TRP transmissions in 5G NR. For example, non-coherent joint transmission Coordinated Multipoint is a technique of LTE/5G NR that could be considered with the aim at increasing the reliability of UltraReliable-low-latency communication. This is illustrated with respect to Figure 8.
[00161] Figure 8 shows a time frequency resource allocation map for each of a first and a second transmission point. As can be seen in the Figure, transmission point 1 (TRP 1) uses a different time-frequency resource for transmissions to a first user equipment (UE 1) than transmission point 2 (TRP 2) uses for transmissions to the first user equipment. Similarly, TRP 1 uses a different time-frequency resource for transmissions to a second user equipment (UE 2) than transmission point 2 (TRP 2) uses for transmissions to the second user equipment.
[00162] To address some of the issues discussed above, the following discloses how to enable at least one physical layer at a receiving entity to determine when it has received multiple copies of the same data, wherein the data is duplicated at a higher layer than the physical layer (e.g. PDCP layer or above). The following also discloses how to enable at least one medium access control layer at a receiving entity to determine when it has received multiple copies of the same data, wherein the data is duplicated at a higher layer than the medium access control layer (e.g. PDCP layer or above). The physical layer and the medium access control layer may work either together or separately to determine when it has received multiple copies of the same data, wherein the data is duplicated at a higher layer than the medium access control layer. Once this identification has been made, the receiving entity may then soft combine values of the received copies of the same received data for decoding purposes.
[00163] The following will discuss more specific examples of the present disclosure before considering the general principles that are applicable to multiple types of communication systems. It is consequently understood that the presently discussed examples are only examples, and that the described principles may be applied to different types of communication networks and/or in different directions transmitting. For example, for clarity reasons, the following will refer to making identifications of duplicate data at the physical/PHY layer. However, it is understood that these identifications may be made by the medium access control/MAC layer and not by the physical layer. It is also understood that these identifications may be made by the P HY and MAC layers working together.
1001641 In particular, the following examples relate to network apparatus(es) that respectively transmit to a terminal/user equipment a packet and at least one copy of the packet that was duplicated at, and/or above, a PDCP layer. The transmissions of the duplicates may be coordinated/paired, and this pairing may be indicated to the receiving terminal by marking these PHY transmissions. Paired PHY transmissions carry identical copies of a data packet (e.g. Ethernet frame, IP datagram). This enables the terminal's receiver to soft combine multiple replicas of the same data (i.e. those received paired physical layer transmissions), which may increase the decoding probability of the received data. Compared to a system that does not employ the presently described mechanism, the presently described system may thus result in a higher successful decoding probability, a reduced packet latency, an increased overall reliability, and increased duplication efficiency (since fewer transmissions per packet will be needed).
[00165] The proposed method of packet marking in the downlink may be based on the following operations, illustrated with respect to at least Figure 9.
[00166] Figure 9 illustrates a potential architecture in which the described system may be employed.
1001671 Figure 9 shows a Host 901 that provides data to a first PDU session 902a to a terminal 903. The first PDU session 902a is effected by a frame replication and elimination entity in the Host 901 providing first data to a first user plane function 904a. The first user plane function 904a passes this data to a protocol stack of a Master gNB 905a, from where it is transmitted to a first physical layer 906a of the terminal 903 using a first radio link [00168] The host 902 is also provisioned with a second PDU session 902b to a terminal 903. The second PDU session 902a is also effected by the frame replication and elimination entity in the Host 901 providing a copy of the first data to a second user plane function 904b. The second user plane function 904b passes this data to a protocol stack of a Secondary gNB 905b, from where it is transmitted to a second physical layer 906b of the terminal 903 using either the first radio link or a second radio link. The first and second radio links are different to each other. The first and second physical layers are different to each other. The first and second radio links may be respective first and second radio bearers.
1001691 Figure 9 illustrates an example use case, in which the downlink receiver is a single-UE device 903, as per Figure 7.
[00170] The frame replication and elimination entity at Host 901 may be in control of higher-layer duplication of packets for sending multiple packets comprising at least some of the same data towards terminal 903.
[00171] In a higher layer multi-connectivity scenario, the 5G network supports disjoint paths for the delivery of the duplicates by creating two independent PDU sessions (PDU session 902a and PDU session 902b). Each PDU session may be associated to a distinct gNB and/or distinct core network-based User-Plane Function (UPF). For example, each PDU session may be associated with a respective, distinct, gNB and each PDU session may be associated with the same, common UPF. In the example shown in Figure 9, PDU session 902a is associated to user plane function 904a and gNB 905a (MgNB) while PDU session 902b is associated to user plane function 904b and gNB 905b (SgNB). The MgNB may be a primary/master access point to a terminal, while the SgNB may be a secondary access point to a terminal. For example, transmissions to the terminal through the secondary access point may be performed at least partly under the control of the master access point. Thus, original data and copies are delivered to the UE by MgNB and SgNB, respectively (although it is understood that this order is not limiting). MgNB and SgNB are also informed by the core network that the PDU sessions 902a, 902b are redundant sessions used for higher-layer duplication towards the same device/terminal. Alternatively, only MgNB 905a is informed by the core network, whereas SgNB 905b may be informed by another radio access network node (e.g. by MgNB 905a) [00172] First, the network entities within a radio access network may coordinate themselves in order to agree on how to perform packet marking/pairing of physical transmissions belonging to redundant PDU sessions of the terminal (redundant PDU sessions carry copies of the same packet). In an example, the pairing is indicatable using a timing offset.
[00173] In other words, the MgNB and the SgNB may agree on pairing the transmissions of duplicates within PDU sessions 902a, 902b at the physical layer. The pairing may be implemented by means of creating semi-persistent scheduling (SPS) configurations, which are paired on the basis of a relative time offset controlling their transmission timing.
1001741 The pairing of the semi-persistent scheduling configurations used by the MgNB and SgNB may be achieved as follows.
[00175] First, both the MgNB and the SgNB determine their own semi-persistent scheduling pattern for their traffic independently for instance accounting for the TSCAI information. These may be respectively labelled SPSnAN and SPSsN.
[00176] Secondly, the MgNB may exchange signaling with the SgNB in order to pair its SP&AN to the semi-persistent scheduling pattern at the SgNB (SPSsN). Depending on the architecture of the network, the pairing between different network apparatuses may be achieved in a number of different ways. For example, this may be achieved by configuring and/or exchanging a time offset across the cells/nodes over an interface between two network entities (for example, over an X2 interface or over an Xn interface). As another example, this may be achieved by configuring and/or exchanging a time offset across a centralised unit of the gNB and a distributed unit of the gNB over an Fl interface. This may be achieved by, for example, sharing one or more parameters related to the semi-persistent scheduling configuration of SPSmN.
1001771 The SgNB may compare this signalled configuration (SPSAAN) with the configuration of its own semi-persistent scheduling configuration (SPSsN). Based on this comparison, the SgNB may derive a relative SPS time_offset to be applied between SPSNAN and SPSsN. This offset defines the relative transmission timing between SP&AN and SPSsN. In other words, the timing offset may be applied between the transmission timing of the network entities' semi-persistent scheduling allocations to the terminal. The SgNB may subsequently inform the MgNB of the determined offset in a response message. The response message may optionally comprise a semi-persistent scheduling configuration index used in SgNB. An example of the pairing/marking is illustrated in Figure 10. It is understood that the same or part of the operations described above in relation to the SgNB may be performed by the MgNB rather than SgNB.
[00178] Figure 10 shows two transmission patterns, one of which being located directly above the other transmission pattern. The upper transmission pattern represents downlink transmission patterns from the MgNB to a terminal in the time domain. The lower transmission pattern represents a downlink transmission pattern from the SgNB to the terminal. For each of these transmission patterns, data is transmitted at a time instance by the MgNB and, a set timing offset after the time instance, a copy of the data is transmitted by the SgNB, if available. If not available, no transmission will be performed.
[00179] It is understood in the above context that the phrase semi-persistent scheduling allocations refer to resource that are allocated to an apparatus for use on a periodic basis. Semi-persistent scheduling configurations may be defined using, e.g. frequency resources, physical resource blocks, a timing offset within the node determining the configuration, and a time periodicity of the allocations. The semi-persistent scheduling configuration may be determined based on information provided to the gNBs/access points from the Core Network. For example, for the New Radio case, the semi-persistent scheduling configuration may be determined based on TSC Assistance Information.
[00180] Thus the distinct semi-persistent scheduling resources allocated to a receiving apparatus may be used to transmit the data and the redundant data to the receiving data. The SPS_time_offset may control the offset between two semi-persistent scheduling allocations that are carrying copies of the same packets. The semi-persistent scheduling allocations may be associated to two different gNBs, or to two different cells within a same gNB (e.g. gNB-DUs), or to two different bandwidth parts in the same cell of a gNB. In one variant, the SPS_time_offset may control the offset between the repetitions of a single semi-persistent scheduling allocation.
[00181] It is noted that the coordination above for exchanging semi-persistent scheduling configurations may also be used to identify the redundant PDU sessions for the UE that are paired. For example, when at least one of MgNB and SgNB detect that a PDU 1 of PDU session 902a is a duplicate of a PDU 2 of PDU session 902b, respectively, they may employ the previously described pairing of the semi-persistent scheduling configurations to transmit the respective PDUs to the UE. The presence of a duplicate transmission may be performed based on, for example, TSC Assistance Information, which includes the packet arrival time at each gNB and the packet delay budget. The detection of the duplicate transmission may also be performed based on identifying redundant PDU sessions based on Redundancy Sequence Number (RSN) of the PDU sessions.
[00182] The network signaling from MgNB may also include sequence numbers used at the layer at which the data is duplicated, such that the SgNB may encapsulate the received frame from UPF 504b at the radio protocol stack with the same sequence number as in MgNB. This may be used to cause two copies of a frame received by the terminal from the multiple gNBs are completely identical. Alternatively, a pre-defined use of PDCP sequence numbers for the PDUs belonging to the redundant PDU sessions may be agreed at the two nodes.
[00183] The above assumes that no radio link control sequence numbers are used. However, if radio link control acknowledged mode is used and if the radio link control unacknowledged mode uses segmentation, then RLC sequence numbers may be used for the (segmented) packets and such information may be provided to the SgNB by the MgNB.
[00184] Once at least one radio access network entity has obtained/determined the timing offset, assistance and/or configuration information may be provided to the terminal to inform the terminal about the agreed packet marking/pairing. The MgNB may be the network entity that informs the terminal about the agreed packet marking/pairing. The terminal may use this information to detect packet duplicates already received at a physical layer. As an example, the assistance/configuration information may comprise an indication that at least two semi-persistent scheduling allocations from given cell(s) are paired (i.e. carry at least some of the same data), as well as the packet marking used within each semi-persistent scheduling allocation. The marking may be provided by an indication to the UE of a relative SPS_time offset across semi-persistent scheduling allocations. Thus the indication may be said to correspond to, or otherwise be representative of the determined timing offset.
[00185] The indication to the terminal from the network may indicate that two semi-persistent scheduling allocations from the two gNBs are paired (i.e. carry duplicates), as well as the packet marking used within each semi-persistent scheduling allocation. The indication to the terminal from the network may indicate the packet marking used within each semi-persistent scheduling allocation by providing timings of when the packets comprising at least some of the same data is transmitted according to SPSmN and SPSsN. The marking may be provided by means of an indication to the UE of the relative SPS time offset across the two paired semi-persistent scheduling allocations. The marking may be provided by means of an indication to the UE of the SPS index of SPSsN which corresponds to a certain SPSmN or vice versa. A few examples of such marking are provided below.
1001861 The first example is discussed with reference to Figure 10.
1001871 At time instance 1 of SPSmN, the master node transfers a copy of a first packet 1001a to a terminal. At time instance 1 of SPSsN, a secondary node transfers a copy of the same packet 1001b to the terminal. The time instance 1 of SPSsN may be provided to the terminal with respect to the SPSmN time allocation to be offset by SPS time_offset. In this option, the SPS_time_offset may be explicitly provided to the terminal. The time instance 1 of SPSsN may be provided to the terminal with respect to the secondary node reference time. In this option, the secondary node may consider the SPS_time offset when setting the SPSsN offset to the terminal.
1001881 The second example is discussed with reference to Figure 11. Figure 11 relates to a scenario in which multiple semi-persistent configurations are available per cell, each of which allocations comprising specific, distinct frequency allocation and scheduling periodicity. Figure 11 differs from Figure 10 in that Figure 11 shows both the original data packet and its copy being transmitted by a same MgNB while Figure 10 shows the original data packet being transmitted by a MgNB and the copy being transmitted by an SgNB.
[00189] Figure 11 shows two transmission patterns, one of which being located directly above the other transmission pattern. The upper transmission pattern represents downlink transmission patterns from the MgNB to a terminal using a first semi-persistent allocation. The lower transmission pattern represents a downlink transmission pattern from the MgNB to the terminal using a second semi-persistent allocation. For each of these transmission patterns, data is transmitted at a time instance by the MgNB on the first semi-persistent allocation and, a set timing offset after the time instance, a copy of the data is transmitted by the MgNB on the second semi-persistent allocation.
[00190] Consequently, at time instance 1 of SPSmN allocation 1, the MgNB transfers a copy of a packet. At time instance 1 (time instance 1 + SPS time_offset) of SPSmN allocation 2, the MgNB transfers a copy of the same packet.
[00191] As a third example, combinations of the first and second examples may be used.
[00192] The pairing of the semi-persistent scheduling allocations from two cells may be indicated to the terminal as part of the RRC signalling. Similarly, the new marking indication (e.g. in the form of an SPS time_offset) may be provided as an additional information element of the RRC configuration of the semi-persistent scheduling configuration. This option may be beneficial for semi-static offsets of the two semi-persistent scheduling allocations. The marking indication may be provided to the terminal using physical layer signalling. An example of such physical layer signalling in which the indication may be provided is part of downlink control information in the Physical Downlink Control Channel. This option may be beneficial for more dynamic offset configurations of the two semi-persistent scheduling allocations (e.g. when the activation/deactivation of semi-persistent scheduling is performed via the Physical Downlink Control Channel). As an example, the MgNB may provide to the terminal at least part of, and potentially all of the SPSsN configuration. If only part of the SPSsN configuration is provided, the provided part may relate to the timing and/or an index of the paired semi-persistent scheduling configuration from SN).
1001931 Finally, the terminal/user equipment may be provided with some intra-user equipment signalling at the modem level to signal soft bit values computed for the received paired physical layer transmissions (i.e. for the different semi-persistent scheduling allocations) received. These values may be exchanged across the user-plane radio protocol stacks at the user equipment that are respectively associated with the different semi-persistent scheduling allocations. For example, where a first semi-persistent scheduling allocation is associated with a master cell group and a second semi-persistent scheduling allocation is associated with a secondary cell group, the terminal may comprise separate/distinct user plane functions for each of these cell groups. Similarly, the intra-UE signalling may be used for the single-cell scenario, to exchange the soft information of different semi-persistent allocations between the user-plane radio protocol stacks associated to two cells, to two different bandwidth parts of the same cells, and for distributed gNBs belonging a same centralised gNB.
[00194] An overview of these example operations is provided with reference to Figure 12.
[00195] Figure 12 illustrates signalling between a data network 1201, a master gNB 1202, a secondary gNB 1203, a user plane function 1204 in the terminal for the master gNB 1202, and a user plane function 1205 in the terminal for the secondary gNB 1203.
[00196] At 1211, the user plane functions in the data network inform the gNBs 1202, 1203 that two or more redundant PDU sessions have been, or will be, established for the terminal. It is understood that in this example, and throughout the above and the following, that the information provided by a user plane function to inform gNBs that two or more redundant PDU sessions have been, or will be, established for the terminal, may be provided by other Core Network Functions. Example Core Network functions that may provide this information are the Session Management Function and/or the Access Management Function. At least one of the gNBs may map the redundant PDU sessions to specific radio access network configurations. For example, the mapping/pairing may be performed using a periodicity/timing offset relation that is determined based on assistance information. The mapping may be determined following communications between the gNBs (such as via an Xn interface). The resulting determined mapping may be signalled to the user equipment using, for example, radio resource control level signalling.
1001971 At 1212, the data network provides a data to the master gNB 1202, which is then transmitted to the user plane function 1204 in the terminal for the master gNB 1202. This data is not correctly decoded at the terminal.
[00198] At 1213, the data network provides the data to the secondary gNB 1203, which is then transmitted to the user plane function 1205 in the terminal for the master gNB 1203. This data is not correctly decoded at the terminal.
1001991 At 1214, the data received at the terminal at 1212 and 1213 are soft-combined and decoded at the physical layer.
[00200] In addition to regular hybrid automatic repeat request mechanisms, which operates within one cell, the proposed mechanisms enable a terminal to exploit gains of soft-combining packets duplicated at the core network and/or at the radio access network (multi-mode duplication) that are sent from different cells, different gNBs, and/or different bandwidth parts. This may result in higher reliability performance/latency reduction and improved resource efficiency compared to not using the described technique.
[00201] Moreover, the more redundant copies that are sent towards a given device, the larger the gains that may be achieved according to the presently described system, which allows to identify that distinct physical layer packets contain the same higher-layer or PDCP layer duplicated frame. To this effect, it is noted that current 5G specifications are being amended to allow up to 4 copies of PDCP layer data to be transmitted, meaning that for data duplicated at this level, up to four copies may be received by the terminal, all using different/distinct PDU sessions.
1002021 The above described techniques have been described in relation to transmitting downlink data. However, it is understood that these techniques may also be applied in the uplink. As an example, where there is a single gNB comprising two reception legs (e.g. Carrier Aggregation based PDCP duplication), the exchange of soft bits can happen locally within the single gNB. The above-described techniques may also be applied to uplink transmissions to two different gNBs (e.g. Dual Connectivity based PDCP duplication). However, depending on the implementation, tighter requirements may be applied to an interface between the two different gNBs (e.g. an Xn interface) to enable a fast exchange of soft bit across distinct nodes. The desirability of applying tighter requirements will depend on the exact implementation of the network and may be deployed by a network engineer in appropriate communication networks.
1002031 Because the described techniques may be applied in both the downlink (e.g. semi-persistent downlink allocations in New Radio) and in the uplink (e.g. configured uplink grants in New Radio), the following presents the above discussed principles in a more general form. For clarity, the term "semi persistent resource" will be used in the following to indicate a resource that it assigned for an entity for transmission and/or reception on a periodic basis. This means that every period for at least two periods, the same "semi persistent resource" is used by a same entity for transmission and/or reception.
1002041 Figure 13 is a flow chart identifying operations performed by a transmitting entity. The transmitting entity may be a network apparatus providing access to a core network (e.g. facilitating between a user equipment and a core network). The transmitting entity may be a user equipment/terminal.
1002051 At 1301, the transmitting entity determines a pairing parameter. The pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource.
1002061 Determining a pairing parameter may comprise receiving a pairing parameter from another apparatus. For example, a network access apparatus may receive the pairing parameter from another network access apparatus. As another example, a terminal may receive the pairing parameter (or information for determining the pairing parameter) from a network access apparatus.
[00207] The pairing parameter may be a timing offset, as discussed above. The pairing parameter may be an indication of an index of a paired semi persistent resource configuration. This may be useful in saving signalling overhead, compared to sending a timing offset. An indication of which of the paired resources is sending original packets and which is sending copies may also be provided. This latter indication may be useful for determining whether to combine a PDU of the configured semi persistent resource with a PDU from the paired semi persistent resource's transmission directly preceding or succeeding the transmission of the configured semi persistent resource. The indication may be implicit. For example, simply configuring a paired semi persistent resource configuration index for certain configurations may indicate that the paired resource is the resource that carries copies. Using implicit indications may be useful for saving signalling overhead, although it is noted that the present disclosure is not limited to this.
[00208] The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus. In this case, the first network apparatus and/or a terminal accessing a network through the first network apparatus may be the apparatus performing the steps of Figure 13.
1002091 The first cell and the second cell may be provided by a same network access apparatus (a "first network apparatus"). In this case, the first network apparatus and/or a terminal accessing a network through the first network apparatus may be the apparatus performing the steps of Figure 13.
[00210] The first cell and the second cell may be provided by different, and respective network access apparatuses (e.g. by, respectively, a first network apparatus and a second network apparatus). In this case, the first network apparatus, and/or the second network apparatus, and/or a terminal accessing a network through the first network apparatus may be the apparatus performing the steps of Figure 13.
1002111 At 1302, the transmitting entity uses said pairing parameter to control transmission of the first data in the first cell on the at least one first semi persistent resource and/or the at least one copy of the first data in the second cell on the at least one second semi persistent resource.
1002121 When the transmitting entity is a network access apparatus, the controlling transmission may be performed by transmitting the pairing parameter, and/or information for determining the pairing parameter, to a receiving terminal.
[00213] When the transmitting entity is a terminal, the controlling transmission may be performed by transmitting data and at least one copy of said data in accordance with the pairing parameter.
[00214] Figure 14 is a flow chart identifying operations performed by a receiving entity. The receiving entity may be a network apparatus providing access to a core network (e.g. facilitating between a user equipment and a core network). The receiving entity may be a user equipment/terminal.
1002151 At 1401, the receiving entity determines a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is transmitted in a second cell on at least one second semi persistent resource.
[00216] Determining a pairing parameter may comprise receiving a pairing parameter from another apparatus. For example, a network access apparatus may receive the pairing parameter from another network access apparatus. As another example, a terminal may receive the pairing parameter (or information for determining the pairing parameter) from a network access apparatus.
[00217] The first cell may be a first bandwidth part in a cell defined by a first network access apparatus and the second cell may be a second bandwidth part in the cell defined by the first network access apparatus. In this case, the first network apparatus and/or a terminal accessing a network through the first network apparatus may be the apparatus performing the steps of Figure 14.
1002181 The first cell and the second cell may be provided by a same network access apparatus (a "first network apparatus"). In this case, the first network apparatus and/or a terminal accessing a network through the first network apparatus may be the apparatus performing the steps of Figure 14.
[00219] The first cell and the second cell may be provided by different, and respective network access apparatuses (e.g. by, respectively, a first network apparatus and a second network apparatus). In this case, the first network apparatus, and/or the second network apparatus, and/or a terminal accessing a network through the first network apparatus may be the apparatus performing the steps of Figure 14.
[00220] At 1402, the receiving entity uses said pairing parameter to identify the at least one copy of the first data at a physical layer of the apparatus. The at least one copy of the first data may be received using the at least one second semi-persistent resource.
[00221] When the receiving entity is operated by a same device/apparatus (e.g. a network access apparatus or a terminal), the receiving entity may operate a first physical layer for receiving the first data, operate a second physical layer for receiving the at least one copy of the first data, and cause messages to be exchanged between the first and second physical layers and/or the MAC layers for facilitating decoding of the first data.
[00222] It is assumed in the above that common security keys may be applied for distinct ODU sessions belonging to different gNBs (e.g. a master cell group and a secondary cell group) that are paired (e.g. that carry duplicate packets).
1002231 It should be understood that each block of the flowchart of the Figures and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.
[00224] It is noted that whilst examples have been described in relation to one example of a standalone 5G, similar principles may be applied in relation to other examples of standalone 3G, LIE or 5G networks. It should be noted that other examples may be based on other cellular technology other than LTE, NR or on variants of both. Therefore, although certain examples were described above by way of example with reference to certain example architectures for wireless networks, technologies and standards, examples may be applied to any other suitable forms of communication systems than those illustrated and described herein.
1002251 It is also noted herein that while the above describes examples, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present claims.
[00226] It should be understood that the apparatuses may comprise or be coupled to other units or modules etc., such as radio parts or radio heads, used in or for transmission and/or reception. Although the apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.
[00227] In general, the various examples may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects of the described may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the claimed is not limited thereto. While various aspects of the claimed may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[00228] The examples of this disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and/or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out examples. The one or more computer-executable components may be at least one software code or portions of it.
[00229] Further in this regard it should be noted that any blocks of the logic flow as in the Figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a non-transitory media.
1002301 The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.
[00231] Examples of the above disclosures may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.
[00232] The foregoing description has provided by way of non-limiting examples a full and informative description of the exemplary example of this disclosure. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this disclosure will still fall within the scope of the appended claims.

Claims (17)

  1. Claims 1. An apparatus comprising: means for determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and means for using said pairing parameter to identify the at least one copy of the first data at a physical layer and/or at a medium access control layer of the apparatus.
  2. 2. An apparatus comprising: means for determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource: and means for using said pairing parameter to control transmission of the first data in the first cell and/or the at least one copy of the first data in the second cell.
  3. An apparatus as claimed in any preceding claim, wherein the apparatus is a terminal accessing a network, comprising means for: receiving the pairing parameter and/or information for determining the pairing parameter from a network access apparatus.
  4. 4 An apparatus as claimed in claim 3, comprising: means for operating a first physical layer for receiving the first data; means for operating a second physical layer for receiving the at least one copy of the first data; and means for causing messages to be exchanged between the first and second physical layers and/or the medium access control layers for facilitating, decoding of the first data.
  5. 5. An apparatus as claimed in claim 3, comprising: means for operating a first physical layer for receiving the first data; and means for using the pairing parameter to omit reception of the at least one copy of the first data when it is determined that the first data has been received correctly.
  6. 6. An apparatus as claimed in any of claims 1 to 2, wherein the apparatus is a network access apparatus for facilitating access to a network, comprising means for: receiving the pairing parameter and/or information for determining the pairing parameter from another network access apparatus.
  7. 7. An apparatus as claimed in claim 6, wherein the network access apparatus hosts at least one higher protocol layer of an access point and wherein the another network access apparatus hosts at least one lower protocol layer of the access point.
  8. 8. An apparatus as claimed in claim 6, wherein the network access apparatus provides a first access point and wherein the another network access apparatus provides a second access point.
  9. 9. An apparatus as claimed in any preceding claim, wherein the pairing parameter is a timing offset between the first time and the second time.
  10. 10. An apparatus as claimed in any preceding claim, wherein the apparatus is at least part of network access apparatus; comprising means for: transmitting the pairing parameter and/or information for determining the pairing parameter to a terminal.
  11. 11. An apparatus as claimed in any preceding claim, wherein the first cell is a first bandwidth part in a cell defined by a first network access apparatus and the second cell is a second bandwidth part in the cell defined by the first network access apparatus.
  12. 12. An apparatus as claimed in any of claims 1 to 10, wherein the first cell and the second cell are provided by a same network access apparatus.
  13. 13. An apparatus as claimed in any of claims 1 to 10, wherein the first cell and the second cell are respectively provided by different network access apparatuses.
  14. 14.A method for an apparatus, the method comprising: determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and using said pairing parameter to identify the at least one copy of the first data at a physical layer and/or at a medium access control layer of the apparatus.
  15. 15.A method for an apparatus, the method comprising: determining a pairing parameter, wherein the pairing parameter is representative of a time difference between a first time at which first data is intended to be transmitted in a first cell on at least one first semi persistent resource and a second time at which at least one copy of the first data is intended to be transmitted in a second cell on at least one second semi persistent resource; and using said pairing parameter to control transmission of the first data in the first cell and/or the at least one copy of the first data in the second cell.
  16. 16.A program for a computer, that, when run on a processor of an apparatus, causes the apparatus to perform the steps of claim 14,
  17. 17.A program for a computer, that, when run on a processor of an apparatus, causes the apparatus to perform the steps of claim 14.
GB1918025.6A 2019-12-09 2019-12-09 Communication system Withdrawn GB2589865A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
GB1918025.6A GB2589865A (en) 2019-12-09 2019-12-09 Communication system
PCT/EP2020/085029 WO2021116082A1 (en) 2019-12-09 2020-12-08 Communication system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB1918025.6A GB2589865A (en) 2019-12-09 2019-12-09 Communication system

Publications (2)

Publication Number Publication Date
GB201918025D0 GB201918025D0 (en) 2020-01-22
GB2589865A true GB2589865A (en) 2021-06-16

Family

ID=69172153

Family Applications (1)

Application Number Title Priority Date Filing Date
GB1918025.6A Withdrawn GB2589865A (en) 2019-12-09 2019-12-09 Communication system

Country Status (2)

Country Link
GB (1) GB2589865A (en)
WO (1) WO2021116082A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11375523B2 (en) * 2019-09-18 2022-06-28 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Resource configuration method and access network device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180302886A1 (en) * 2017-04-14 2018-10-18 Asustek Computer Inc. Method and apparatus of requesting semi-persistent scheduling resource for transmission of data duplication in a wireless communication system
US20190116597A1 (en) * 2017-10-17 2019-04-18 Institute For Information Industry Mobile device and uplink data transmission method thereof
EP3500033A1 (en) * 2016-08-12 2019-06-19 LG Electronics Inc. -1- Method and apparatus for transmitting sps help information in wireless communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3500033A1 (en) * 2016-08-12 2019-06-19 LG Electronics Inc. -1- Method and apparatus for transmitting sps help information in wireless communication system
US20180302886A1 (en) * 2017-04-14 2018-10-18 Asustek Computer Inc. Method and apparatus of requesting semi-persistent scheduling resource for transmission of data duplication in a wireless communication system
US20190116597A1 (en) * 2017-10-17 2019-04-18 Institute For Information Industry Mobile device and uplink data transmission method thereof

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "New QoS parameter Time Offset", vol. SA WG2, no. Santa Cruz-Tenerife, Spain; 20190225 - 20190301, 19 February 2019 (2019-02-19), XP051610310, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG2%5FArch/TSGS2%5F131%5FTenerife/Docs/S2%2D1901710%2Ezip> [retrieved on 20190219] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11375523B2 (en) * 2019-09-18 2022-06-28 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Resource configuration method and access network device
US11950277B2 (en) 2019-09-18 2024-04-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Resource configuration method and access network device

Also Published As

Publication number Publication date
WO2021116082A1 (en) 2021-06-17
GB201918025D0 (en) 2020-01-22

Similar Documents

Publication Publication Date Title
CN113271180B (en) Feedback method of hybrid automatic repeat request (HARQ) bitmap information and related equipment
US12047915B2 (en) Control channel structure design to support V2X traffic
JP2022033808A (en) Triggering group acknowledgment/negative and gack/channel state information
US12245181B2 (en) Multi-transmit-receive point transmission for ultra reliable low latency communication
US11711167B2 (en) Apparatus, method and computer program
CN110214432B (en) Method and node for activation or deactivation of a carrier in a communication network
CN110121848A (en) Method and device in cordless communication network
AU2017418048B2 (en) Communication apparatus, method and computer program
US20140105224A1 (en) Retransmissions in a Communication System Using Almost Blank Subframes
CN109152069A (en) The method and apparatus of transmission control information
WO2018199643A1 (en) Method and apparatus for determining uplink transmission timing in wireless communication system
WO2017220855A1 (en) Method and apparatus for performing packet duplication in a multi-connectivity scenario
CN113287274A (en) Manage group replication
CN113597007A (en) Transmission resource selection method, network equipment and user equipment
CN115398838A (en) HARQ-ACK delay to support 14 HARQ processes in enhanced machine type communication
US12273208B2 (en) HARQ feedback technique for communication systems
WO2021116082A1 (en) Communication system
WO2020151811A1 (en) Communication apparatus, method and computer program
US11968683B2 (en) Apparatus, method and computer program
WO2023000177A1 (en) Method, device and computer readable medium for communication
US12507255B2 (en) Method and device in nodes used for wireless communication
US20230276460A1 (en) Method and device in nodes used for wireless communication
WO2021008672A1 (en) Apparatus, method and computer program for reliable transmission of commands
CN119384817A (en) Signal receiving method, signal sending method and device
WO2020098915A1 (en) Control channel combining for telecommunication systems

Legal Events

Date Code Title Description
WAP Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1)