Login| Sign Up| Help| Contact|

Patent Searching and Data


Title:
APPARATUS AND METHOD FOR AVOIDING PHYSICAL CELL ID CONFLICT BETWEEN DIFFERENT OPERATORS IN AN UNLICENSED SPECTRUM
Document Type and Number:
WIPO Patent Application WO/2023/285850
Kind Code:
A1
Abstract:
An apparatus and a method of wireless communication are provided. The method by a user equipment (UE) includes determining, by the UE, a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCH) common search space set. This can solve issues in the prior art, provide a method for a UE to determine a position of a CORESET, read cell global identifier (CGI) information, and/or reduce the issue for a physical cell ID conflicting between different operators.

Inventors:
LIN HAO (FR)
Application Number:
PCT/IB2021/000489
Publication Date:
January 19, 2023
Filing Date:
July 16, 2021
Export Citation:
Click for automatic bibliography generation   Help
Assignee:
OROPE FRANCE SARL (FR)
International Classes:
H04L5/00
Domestic Patent References:
WO2021070065A12021-04-15
Other References:
ERICSSON: "Initial access signals and channels for NR-U", vol. RAN WG1, no. Athens, Greece; 20190225 - 20190301, 16 February 2019 (2019-02-16), XP051600578, Retrieved from the Internet [retrieved on 20190216]
Attorney, Agent or Firm:
FOREY, Kevin (FR)
Download PDF:
Claims:
What is claimed is:

1. A wireless communication method by a user equipment (UE), comprising: determining, by the UE, a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCH) common search space set.

2. The method of claim 1, further comprising monitoring, by the UE, the type 0 PDCCH in the CORESET.

3. The method of claim 1, further comprising being configured, by a base station, to report a cell global identifier (CGI), wherein the CGI is carried in system information, which is scheduled by a downlink control information (DCI) carried in the type 0 PDCCH.

4. The method of claim 3, wherein the DCI format comprises a DCI format 1_0.

5. The method of claim 4, wherein the DCI format 1_0 is cyclic redundancy check (CRC) scrambled by system information- radio network temporary identifier (SI-RNTI).

6. The method of claim 1, further comprising being configured, by a base station, with a frequency point information corresponding to a synchronization signal block (SSB) information.

7. The method of claim 1, further comprising detecting, by the UE, the SSB information and/or measuring, by the UE, the SSB information.

8. The method of claim 6, wherein the frequency point information corresponding to the SSB information comprises at least one of the followings: a first frequency point corresponding to a first SSB, a second frequency point corresponding to a second SSB, or a third frequency point corresponding to a third SSB.

9. The method of claim 8, wherein the first frequency point comprises a first absolute radio frequency channel number (ARFCN) and/or the second frequency point comprises a second ARFCN.

10. The method of claim 8, wherein the offset comprises a frequency interval between a first location relevant to a start location of the CORESET and a second location relevant to a start location of the second SSB.

11. The method of claim 8, wherein a transmission of the second SSB comprises a hypothetical transmission.

12. The method of claim 9, wherein the second ARFCN is provided by the base station to the UE by a radio resource control (RRC) configuration.

13. The method of claim 12, wherein the RRC configuration comprises a reportCGI RRC information element.

14. The method of claim 12, wherein a subcarrier spacing (SCS) of the first SSB, and/or the second SSB, and/or the third SSB is indicated by a base station to the UE in the RRC configuration.

15. The method of claim 8, wherein the offset is obtained from a master information block (MIB) message.

16. The method of claim 15, wherein the MIB message is carried by a physical broadcast channel (PBCH) of the first SSB.

17. The method of claim 8, wherein the offset comprises a frequency interval between a first location relevant to a start location of the CORESET and a third location relevant to a start location of the first SSB.

18. The method of claim 17, wherein the offset is provided by the base station to the UE by an RRC configuration.

19. The method of claim 18, wherein the RRC configuration comprises a reportCGI RRC information element.

20. The method of claim 8, wherein the offset comprises a frequency interval between a first location relevant to a start location of the CORESET and a second location relevant to a start location of the third SSB.

21. The method of claim 20, wherein the third frequency point corresponding to the third SSB is indicated by a base station to the UE.

22. The method of claim 8, wherein the third frequency point comprises a global synchronization channel number (GSCN).

23. The method of claim 22, wherein the GSCN is indicated by a base station in an RRC configuration.

24. The method of claim 22, wherein the GSCN is pre-defined.

25. The method of claim 24, wherein the GSCN is closest to the first frequency point.

26. The method of claim 8, wherein the first SSB and the third SSB are within a subband.

27. The method of claim 26, wherein the subband comprises a set of RB.

28. The method of claim 26, wherein a value of the third frequency point corresponding to the third SSB is indicated by a base station to the UE.

29. The method of claim 26, wherein the third frequency point comprises a GSCN.

30. The method of claim 29, wherein the GSCN is within the subband.

31. The method of claim 29, wherein the GSCN is determined by a pre-defined rule within the subband.

32. The method of claim 31, wherein the GSCN is closest to an edge of the subband.

33. The method of claim 29, wherein there is only one GSCN within the subband.

34. The method of claim 33, wherein the GSCN is determined as the third frequency point for the third SSB.

35. The method of claim 8, wherein a location relevant to an SSB comprises a first common resource block (CRB) that is overlapped with a first RB of the SSB.

36. The method of claim 35, wherein the first CRB is a CRB with a smallest CRB index that is overlapped with the first RB of the SSB.

37. The method of claim 35, wherein the first RB is an RB with a smallest RB index of the SSB.

38. The method of claim 35, wherein the SSB comprises at least one of the followings: the first SSB, the second SSB, or the third SSB.

39. The method of claim 8, wherein a location relevant to the CORESET comprises a second CRB that is overlapped with a second RB of the CORESET.

40. The method of claim 39, wherein the second CRB is a CRB with a smallest CRB index that is overlapped with the second RB of the CORESET.

41. The method of claim 39, wherein the second RB of the CORESET is an RB with a smallest RB index of the CORESET.

42. The method of claim 1, wherein a value of the offset comprises a number of RBs.

43. The method of claim 8, wherein a subcarrier spacing (SCS) of the CORESET and a SCS of an SSB are same.

44. The method of claim 8, wherein the SSB comprises at least one of the followings: the first SSB, the second SSB, or the third SSB.

45. The method of claim 44, wherein the offset is expressed according to the SCS of the CORESET.

46. The method of claim 44, wherein when an SCS of the first SSB is a first value, the SCS for the CORESET is assumed by the UE to be the first value.

47. The method of claim 44, wherein when an SCS of the first SSB is the first value, the SCS for CORESET is assumed by the UE to be same as an SCS of the second SSB and/or an SCS of the third SSB.

48. The method of claim 46, wherein the first value comprises at least one of the followings: 120 kHz, 480 kHz, or 960 kHz.

49. The method of claim 1, wherein the CORESET is associated with an index zero.

50. A wireless communication method by a base station, comprising: configuring a user equipment (UE) to determine a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCEI) common search space set.

51. The method of claim 50, further comprising configuring the UE to monitor the type 0 PDCCEI in the CORESET.

52. The method of claim 50, further comprising configuring the UE to report a cell global identifier (CGI), wherein the CGI is carried in system information, which is scheduled by a downlink control information (DCI) carried in the type 0 PDCCH.

53. The method of claim 52, wherein the DCI format comprises a DCI format 1_0.

54. The method of claim 52, wherein the DCI format 1_0 is cyclic redundancy check (CRC) scrambled by system information-radio network temporary identifier (SI-RNTI).

55. The method of claim 50, further comprising configuring, to the UE, a frequency point information corresponding to a synchronization signal block (SSB) information.

56. The method of claim 50, further comprising configuring the UE to detect the SSB information and/or configuring the UE to measure the SSB information.

57. The method of claim 54, wherein the frequency point information corresponding to the SSB information comprises at least one of the followings: a first frequency point corresponding to a first SSB, a second frequency point corresponding to a second SSB, or a third frequency point corresponding to a third SSB.

58. The method of claim 57, wherein the first frequency point comprises a first absolute radio frequency channel number (ARFCN) and/or the second frequency point comprises a second ARFCN.

59. The method of claim 57, wherein the offset comprises a frequency interval between a first location relevant to a start location of the CORESET and a second location relevant to a start location of the second SSB.

60. The method of claim 57, wherein a transmission of the second SSB comprises a hypothetical transmission.

61. The method of claim 58, wherein the second ARFCN is provided by the base station to the UE by a radio resource control (RRC) configuration.

62. The method of claim 61, wherein the RRC configuration comprises a reportCGI RRC information element.

63. The method of claim 61, wherein a subcarrier spacing (SCS) of the first SSB, the second SSB, and/or the third SSB is indicated by a base station to the UE in the RRC configuration.

64. The method of claim 57, wherein the offset is obtained from a master information block (MIB) message.

65. The method of claim 64, wherein the MIB message is carried by a physical broadcast channel (PBCH) of the first SSB.

66. The method of claim 57, wherein the offset comprises a frequency interval between a first location relevant to a start location of the CORESET and a third location relevant to a start location of the first SSB.

67. The method of claim 66, wherein the offset is provided by the base station to the UE by an RRC configuration.

68. The method of claim 67, wherein the RRC configuration comprises a reportCGI RRC information element.

69. The method of claim 57, wherein the offset comprises a frequency interval between a first location relevant to a start location of the CORESET and a second location relevant to a start location of the third SSB.

70. The method of claim 69, wherein the third frequency point corresponding to the third SSB is indicated by a base station to the UE.

71. The method of claim 57, wherein the third frequency point comprises a global synchronization channel number (GSCN).

72. The method of claim 71, wherein the GSCN is indicated by a base station in an RRC configuration.

73. The method of claim 71, wherein the GSCN is pre-defined.

74. The method of claim 73, wherein the GSCN is closest to the first frequency point.

75. The method of claim 54, wherein the first SSB and the third SSB are within a subband.

76. The method of claim 75, wherein the subband comprises a set of RB.

77. The method of claim 75, wherein a value of the third frequency point corresponding to the third SSB is indicated by a base station to the UE.

78. The method of claim 75, wherein the third frequency point comprises a GSCN.

79. The method of claim 79, wherein the GSCN is within the subband.

80. The method of claim 79, wherein the GSCN is determined by a pre-defined rule within the subband.

81. The method of claim 80, wherein the GSCN is closest to an edge of the subband.

82. The method of claim 78, wherein there is only one GSCN within the subband.

83. The method of claim 82, wherein the GSCN is determined as the third frequency point for the third SSB.

84. The method of claim 57, wherein a location relevant to an SSB comprises a first common resource block (CRB) that is overlapped with a first RB of the SSB.

85. The method of claim 84, wherein the first CRB is a CRB with a smallest CRB index that is overlapped with the first RB of the SSB.

86. The method of claim 84, wherein the first RB is an RB with a smallest RB index of the SSB.

87. The method of claim 84, wherein the SSB comprises at least one of the followings: the first SSB, the second SSB, or the third SSB.

88. The method of claim 57, wherein a location relevant to the CORESET comprises a second CRB that is overlapped with a second RB of the CORESET.

89. The method of claim 88, wherein the second CRB is a CRB with a smallest CRB index that is overlapped with the second RB of the CORESET.

90. The method of claim 88, wherein the second RB of the CORESET is an RB with a smallest RB index of the CORESET.

91. The method of claim 52, wherein a value of the offset comprises a number of RBs.

92. The method of claim 57, wherein a subcarrier spacing (SCS) of the CORESET and a SCS of an SSB are same.

93. The method of claim 57, wherein the SSB comprises at least one of the followings: the first SSB, the second SSB, or the third SSB.

94. The method of claim 93, wherein the offset is expressed according to the SCS of the CORESET.

95. The method of claim 93, wherein when an SCS of the first SSB is a first value, the SCS for the CORESET is assumed by the UE to be the first value.

96. The method of claim 93, wherein when an SCS of the first SSB is the first value, the SCS for CORESET is assumed by the UE to be same as an SCS of the second SSB and/or an SCS of the third SSB.

97. The method of claim 95, wherein the first value comprises at least one of the followings: 120kEIz, 480kEIz, or 960kEIz.

98. The method of claim 50, wherein the CORESET is associated with an index zero.

99. A user equipment (UE), comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the processor is configured to perform the method of any one of claims 1 to 49.

100. A base station, comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the processor is configured to perform the method of any one of claims 50 to 98.

101. A non-transitory machine -readable storage medium having stored thereon instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 98.

102. A chip, comprising: a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the method of any one of claims 1 to 98.

103. A computer readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to execute the method of any one of claims 1 to 98.

104. A computer program product, comprising a computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 98.

105. A computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 98.

Description:
APPARATUS AND METHOD OF WIRELESS COMMUNICATION

BACKGROUND OF DISCLOSURE

1. Field of the Disclosure

[0001] The present disclosure relates to the field of communication systems, and more particularly, to an apparatus and a method of wireless communication, which can provide a good communication performance and/or high reliability.

2. Description of the Related Art

[0002] In an unlicensed band, an unlicensed spectrum is a shared spectrum. Communication equipment in different communication systems can use the unlicensed spectrum as long as the unlicensed meets regulatory requirements set by countries or regions on a spectrum. There is no need to apply for a proprietary spectrum authorization from a government. [0003] In order to allow various communication systems that use the unlicensed spectrum for wireless communication to coexist friendly in the spectrum, some countries or regions specify regulatory requirements that must be met to use the unlicensed spectrum. For example, a communication device follows a listen before talk (LBT) or channel access procedure, that is, the communication device needs to perform a channel sensing before transmitting a signal on a channel. When an LBT outcome illustrates that the channel is idle, the communication device can perform signal transmission; otherwise, the communication device cannot perform signal transmission. In order to ensure fairness, once a communication device successfully occupies the channel, a transmission duration cannot exceed a maximum channel occupancy time (MCOT). LBT mechanism is also called a channel access procedure. In new radio (NR) Release 16, there are different types of channel access procedures, e.g., type 1, type 2A, type 2B and type 2C channel access procedures as described in TS 37.213.

[0004] In unlicensed spectrum, different operators can deploy their networks in the same band. When different operators select a same physical cell identifier (PCI) for their SSB transmissions at a same frequency point, there will occur PCI conflicting. To resolve this issue, the network may request its UE to read a cell global identifier (CGI) information and report the CGI information to the network, so that the network will be able to identify if the PCI is conflicting with other operators. To this end, it requires the UE to read system information from a neighbor cell based on the measured SSB at a given frequency point. Since the system information is scheduled by a type 0 physical downlink control channel (PDCCH) in a control resource set (CORESET) (also known as CORESET#0), therefore, there is a need for an apparatus and a method of wireless communication, which can solve issues in the prior art, provide a method for a UE to determine a position of a CORESET, read cell global identifier (CGI) information, and/or reduce the issue for a physical cell ID conflicting between different operators.

SUMMARY

[0005] An object of the present disclosure is to propose an apparatus (such as a user equipment (UE) and/or a base station) and a method of wireless communication, which can solve issues in the prior art, provide a method for a UE to determine a position of a CORESET, read cell global identifier (CGI) information, and/or reduce the issue for a physical cell ID conflicting between different operators.

[0006] In a first aspect of the present disclosure, a method of wireless communication by a user equipment (UE) comprises determining, by the UE, a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCH) common search space set.

[0007] In a second aspect of the present disclosure, a method of wireless communication by a base station comprises configuring a user equipment (UE) to determine a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCH) common search space set. [0008] In a third aspect of the present disclosure, a user equipment comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to determine a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCH) common search space set.

[0009] In a fourth aspect of the present disclosure, a base station comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to configure a user equipment (UE) to determine a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCH) common search space set.

[0010] In a fifth aspect of the present disclosure, a non-transitory machine-readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method.

[0011] In a sixth aspect of the present disclosure, a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method.

[0012] In a seventh aspect of the present disclosure, a computer readable storage medium, in which a computer program is stored, causes a computer to execute the above method.

[0013] In an eighth aspect of the present disclosure, a computer program product includes a computer program, and the computer program causes a computer to execute the above method.

[0014] In a ninth aspect of the present disclosure, a computer program causes a computer to execute the above method.

BRIEF DESCRIPTION OF DRAWINGS

[0015] In order to illustrate the embodiments of the present disclosure or related art more clearly, the following figures will be described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person having ordinary skill in this field can obtain other figures according to these figures without paying the premise.

[0016] FIG. 1 is a block diagram of one or more user equipments (UEs) and a base station (e.g., gNB) of communication in a communication network system according to an embodiment of the present disclosure.

[0017] FIG. 2 is a schematic diagram illustrating an example user plane protocol stack according to an embodiment of the present disclosure.

[0018] FIG. 3 is a schematic diagram illustrating an example control plane protocol stack according to an embodiment of the present disclosure.

[0019] FIG. 4 is a flowchart illustrating a method of wireless communication performed by a user equipment (UE) according to an embodiment of the present disclosure.

[0020] FIG. 5 is a flowchart illustrating a method of wireless communication performed by a base station according to an embodiment of the present disclosure.

[0021] FIG. 6 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure.

[0022] FIG. 7 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure.

[0023] FIG. 8 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure.

[0024] FIG. 9 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure. [0025] FIG. 10 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure.

[0026] FIG. 11 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure.

[0027] FIG. 12 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure.

[0028] FIG. 13 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure.

[0029] FIG. 14 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

[0030] Embodiments of the present disclosure are described in detail with the technical matters, structural features, achieved objects, and effects with reference to the accompanying drawings as follows. Specifically, the terminologies in the embodiments of the present disclosure are merely for describing the purpose of the certain embodiment, but not to limit the disclosure.

[0031] FIG. 1 illustrates that, in some embodiments, one or more user equipments (UEs) 10 and abase station (e.g., gNB) 20 for transmission adjustment in a communication network system 30 according to an embodiment of the present disclosure are provided. The communication network system 30 includes the one or more UEs 10 and the base station 20. The one or more UEs 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and the transceiver 13. The base station 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and the transceiver 23. The processor 11 or 21 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of radio interface protocol may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively coupled with the processor 11 or 21 and stores a variety of information to operate the processor 11 or 21. The transceiver 13 or 23 is operatively coupled with the processor 11 or 21, and the transceiver 13 or 23 transmits and or receives a radio signal.

[0032] The processor 11 or 21 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and or data processing device. The memory 12 or 22 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and/or other storage device. The transceiver 13 or 23 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the memory 12 or 22 and executed by the processor 11 or 21. The memory 12 or 22 can be implemented within the processor 11 or 21 or external to the processor 11 or 21 in which case those can be communicatively coupled to the processor 11 or 21 via various means as is known in the art.

[0033] FIG. 2 illustrates an example user plane protocol stack according to an embodiment of the present disclosure. FIG. 2 illustrates that, in some embodiments, in the user plane protocol stack, where service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), radio link control (RLC), and media access control (MAC) sublayers and physical (PHY) layer may be terminated in a UE 10 and a base station 20 (such as gNB) on a network side. In an example, a PHY layer provides transport services to higher layers (e.g., MAC, RRC, etc.). In an example, services and functions of a MAC sublayer may comprise mapping between logical channels and transport channels, multiplexing/demultiplexing of MAC service data units (SDUs) belonging to one or different logical channels into/from transport blocks (TBs) delivered to/from the PHY layer, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ) (e.g. one HARQ entity per carrier in case of carrier aggregation (CA)), priority handling between UEs by means of dynamic scheduling, priority handling between logical channels of one UE by means of logical channel prioritization, and/or padding. A MAC entity may support one or multiple numerologies and or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and/or transmission timing a logical channel may use. In an example, an RLC sublayer may supports transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM) transmission modes. The RLC configuration may be per logical channel with no dependency on numerologies and/or transmission time interval (TTI) durations. In an example, automatic repeat request (ARQ) may operate on any of the numerologies and/or TTI durations the logical channel is configured with. In an example, services and functions of the PDCP layer for the user plane may comprise sequence numbering, header compression, and decompression, transfer of user data, reordering and duplicate detection, PDCP PDU routing (e.g., in case of split bearers), retransmission of PDCP SDUs, ciphering, deciphering and integrity protection, PDCP SDU discard, PDCP re-establishment and data recovery for RLC AM, and or duplication of PDCP PDUs. In an example, services and functions of SDAP may comprise mapping between a QoS flow and a data radio bearer. In an example, services and functions of SDAP may comprise mapping quality of service Indicator (QFI) in downlink (DL) and uplink (UL) packets. In an example, a protocol entity of SDAP may be configured for an individual PDU session.

[0034] FIG. 3 illustrates an example control plane protocol stack according to an embodiment of the present disclosure. FIG. 2 illustrates that, in some embodiments, in the control plane protocol stack where PDCP, RLC, and MAC sublayers and PHY layer may be terminated in a UE 10 and a base station 20 (such as gNB) on a network side and perform service and functions described above. In an example, RRC used to control a radio resource between the UE and a base station (such as a gNB). In an example, RRC may be terminated in a UE and the gNB on a network side. In an example, services and functions of RRC may comprise broadcast of system information related to AS and NAS, paging initiated by 5GC or RAN, establishment, maintenance and release of an RRC connection between the UE and RAN, security functions including key management, establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs), mobility functions, QoS management functions, UE measurement reporting and control of the reporting, detection of and recovery from radio link failure, and or NAS message transfer to/from NAS from/to a UE. In an example, NAS control protocol may be terminated in the UE and AMF on a network side and may perform functions such as authentication, mobility management between a UE and an AMF for 3GPP access and non-3GPP access, and session management between a UE and a SMF for 3GPP access and non-3GPP access.

[0035] In some embodiments, the processor 11 is configured to determine a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCH) common search space set. This can solve issues in the prior art, provide a method for a UE to determine a position of a CORESET, read cell global identifier (CGI) information, and/or reduce the issue for a physical cell ID conflicting between different operators.

[0036] In some embodiments, the processor 21 is configured to configure the user equipment (UE) 10 to determine a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCH) common search space set. This can solve issues in the prior art, provide a method for a UE to determine a position of a CORESET, read cell global identifier (CGI) information, and or reduce the issue for a physical cell ID conflicting between different operators.

[0037] FIG. 4 illustrates a method 200 of wireless communication by a user equipment (UE) according to an embodiment of the present disclosure. In some embodiments, the method 200 includes: a block 202, determining, by the UE, a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCH) common search space set. This can solve issues in the prior art, provide a method for a UE to determine a position of a CORESET, read cell global identifier (CGI) information, and/or reduce the issue for a physical cell ID conflicting between different operators.

[0038] FIG. 5 illustrates a method 300 of wireless communication by a base station according to an embodiment of the present disclosure. In some embodiments, the method 300 includes: a block 302, configuring a user equipment (UE) to determine a position of a control resource set (CORESET) from an offset, where the CORESET is associated with a type 0 physical downlink control channel (PDCCH) common search space set. This can solve issues in the prior art, provide a method for a UE to determine a position of a CORESET, read cell global identifier (CGI) information, and/or reduce the issue for a physical cell ID conflicting between different operators.

[0039] In some embodiments, the method further comprises monitoring, by the UE, the type 0 PDCCH in the CORESET. In some embodiments, the method further comprises being configured, by a base station, to report a cell global identifier (CGI), wherein the CGI is carried in system information, which is scheduled by a downlink control information (DCI) format carried in the type 0 PDCCH. In some embodiments, the DCI format comprises a DCI format 1_0. In some embodiments, the DCI format 1_0 is cyclic redundancy check (CRC) scrambled by system information-radio network temporary identifier (SI-RNTI). In some embodiments, the method further comprises being configured, by a base station, with a frequency point information corresponding to a synchronization signal block (SSB) information. In some embodiments, the method further comprises detecting, by the UE, the SSB information and/or measuring, by the UE, the SSB information. In some embodiments, the frequency point information corresponding to the SSB information comprises at least one of the followings: a first frequency point corresponding to a first SSB, a second frequency point corresponding to a second SSB, or a third frequency point corresponding to a third SSB. In some embodiments, the first frequency point comprises a first absolute radio frequency channel number (ARFCN) and/or the second frequency point comprises a second ARFCN. [0040] In some embodiments, the offset comprises a frequency interval between a first location relevant to a start location of the CORESET and a second location relevant to a start location of the second SSB. In some embodiments, a transmission of the second SSB comprises a hypothetical transmission. In some embodiments, the second ARFCN is provided by the base station to the UE by a radio resource control (RRC) configuration. In some embodiments, the RRC configuration comprises a reportCGI RRC information element. In some embodiments, a subcarrier spacing (SCS) of the first SSB, the second SSB, and or the third SSB is indicated by a base station to the UE in the RRC configuration. In some embodiments, the offset is obtained from a master information block (MIB) message. In some embodiments, the MIB message is carried by a physical broadcast channel (PBCH) of the first SSB. In some embodiments, the offset comprises a frequency interval between a first location relevant to a start location of the CORESET and a third location relevant to a start location of the first SSB. In some embodiments, the offset is provided by the base station to the UE by an RRC configuration.

[0041] In some embodiments, the RRC configuration comprises a reportCGI RRC information element. In some embodiments, the offset comprises a frequency interval between a first location relevant to a start location of the CORESET and a second location relevant to a start location of the third SSB. In some embodiments, the third frequency point corresponding to the third SSB is indicated by a base station to the UE. In some embodiments, the third frequency point comprises a global synchronization channel number (GSCN). In some embodiments, the GSCN is indicated by a base station in an RRC configuration. In some embodiments, the GSCN is pre-defined. In some embodiments, the GSCN is closest to the first frequency point. In some embodiments, the first SSB and the third SSB are within a subband. In some embodiments, the subband comprises a set of RB. In some embodiments, a value of the third frequency point corresponding to the third SSB is indicated by a base station to the UE. In some embodiments, the third frequency point comprises a GSCN.

[0042] In some embodiments, the GSCN is within the subband. In some embodiments, the GSCN is determined by a pre-defined rule within the subband. In some embodiments, the GSCN is closest to an edge of the subband. In some embodiments, there is only one GSCN within the subband. In some embodiments, the GSCN is determined as the third frequency point for the third SSB. In some embodiments, a location relevant to an SSB comprises a first common resource block (CRB) that is overlapped with a first RB of the SSB. In some embodiments, the first CRB is a CRB with a smallest CRB index that is overlapped with the first RB of the SSB. In some embodiments, the first RB is an RB with a smallest RB index of the SSB. In some embodiments, the SSB comprises at least one of the followings: the first SSB, the second SSB, or the third SSB. In some embodiments, a location relevant to a CORESET comprises a second CRB that is overlapped with a second RB of the CORESET. In some embodiments, the second CRB is a CRB with a smallest CRB index that is overlapped with the second RB of the CORESET.

[0043] In some embodiments, the second RB of the CORESET is an RB with a smallest RB index of the CORESET. In some embodiments, a value of the offset comprises a number of RBs. In some embodiments, a subcarrier spacing (SCS) of the CORESET and a SCS of an SSB are same. In some embodiments, the SSB comprises at least one of the followings: the first SSB, the second SSB, or the third SSB. In some embodiments, the offset is expressed according to the SCS of the CORESET. In some embodiments, when an SCS of the first SSB is a first value, the SCS for the CORESET is assumed by the UE to be the first value. In some embodiments, when an SCS of the first SSB is the first value, the SCS for CORESET is assumed by the UE to be same as an SCS of the second SSB and/or an SCS of the third SSB. In some embodiments, the first value comprises at least one of the followings: 120kHz, 480kHz, or 960kHz. In some embodiments, the CORESET is associated with an index zero.

[0044] In some examples, a network such as a base station may request a UE to report a cell global ID (CGI). The CGI is carried in system information, which is scheduled by a DCI carried in a type 0 PDCCH. Therefore, in order to read the CGI in the system information, the UE needs to detect the type 0 PDCCH in a dedicated CORESET (such as a CORESET 0). In this disclosure, some embodiments present a method for the UE to determine a position of the CORESET 0, where the CORESET 0, is a control resource set associated with the type 0 PDCCH common search space set. The UE monitors the type 0 PDCCH in the CORESET 0. In some examples, the network provides the UE with a frequency point (e.g., a first ARFCN) at which the UE detects a first SSB and performs measurement. Moreover, the network may configure the UE to report the CGI, then the UE needs to determine the position in frequency domain of the CORESET 0 in order to further detect the type 0 PDCCH in the CORESET 0.

[0045] FIG. 6 illustrates an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure. As illustrated in FIG. 6, the network provides the UE with a frequency point (e.g., ARFCN) of an SSB 1. The UE determines a location of the CORESET 0 from an offset, where the offset represents a frequency interval between a first location relevant to a start location of the COREST 0 and a second location relevant to a start location of an SSB 2. In some examples, a second frequency point (e.g., a second ARFCN) is a frequency point for the SSB 2. In some examples, an SSB 2 transmission is a hypothetical transmission, e.g., the SSB 2 is not actually transmitted. In some examples, the second ARFCN is provided by the network to the UE by an RRC configuration. In some examples, the RRC configuration comprises at least reportCGI RRC information element. In some examples, the network indicates a subcarrier spacing of the SSB 1 and/or the SSB 2 to the UE in the RRC configuration. In some examples, the offset is obtained from a MIB message. In some examples, the MIB message is carried by a PBCH of the SSB 1.

[0046] FIG. 7 illustrates an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure. In some examples, as illustrated in FIG. 7, the UE determines a location of the CORESET 0 from an offset, where the offset represents a frequency interval between a first location relevant to a start location of the CORESET 0 and a third location relevant to a start location of an SSB 1. Optionally, the offset is indicated by a network in an RRC configuration, e.g., in reportCGI RRC information element (IE).

[0047] FIG. 8 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure. In some examples, as illustrated in FIG. 8, the UE determines a location of a CORESET 0 from an offset, where the offset represents a frequency interval between a first location relevant to a start location of the CORESET 0 and a second location relevant to a start location of a third SSB, where a frequency point corresponding to the third SSB is indicated by the network. In some examples, the frequency point is a GSCN. In some examples, the network indicates the GSCN in an RRC configuration.

[0048] FIG. 9 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure. In some examples, as illustrated in FIG. 9, the UE determines a location of a CORESET 0 from an offset, where the offset represents a frequency interval between a first location relevant to a start location of the CORESET 0 and a second location relevant to a start location of a third SSB, where a frequency point corresponding to the third SSB is indicated by the network. In some examples, the frequency point is a GSCN. In some examples, the network indicates the GSCN in an RRC configuration. In some examples, as illustrated in FIG. 9, the GSCN is pre-defined, for example, the UE assumes a GSCN which is closest to the first frequency point (e.g., ARFCN 1).

[0049] FIG. 10, FIG. 11, and FIG. 12 are each a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure. In some examples, as illustrated in FIG. 10, a first SSB (SSB 1) and a third SSB (SSB 3) are within a subband. A network indicates a value of a GSCN corresponding to the third SSB to the UE, where the GSCN is within the subband. Optionally, the GSCN is determined by a pre-defined rule within the subband, e.g., the GSCN closest to the edge of the subband. In some examples, as illustrated in FIG. 11 , there is only one GSCN within the subband, and the GSCN is determined as the frequency point for SSB 3. In some examples, a value of the offset is a number of RBs as illustrated in FIG. 12. In some examples, the offset is indicated by the network in the RRC configuration, e.g., inreportCGI RRC IE as illustrated in FIG. 12.

[0050] FIG. 13 is a schematic diagram illustrating an example of for a UE to determine a position of a CORESET according to an embodiment of the present disclosure. In some examples, as illustrated in FIG. 13, a location relevant to an SSB comprises a first CRB (common RB) that is overlapped with a first RB of the SSB, where the first CRB is a CRB with the smallest CRB index that is overlapped with the first RB of the SSB. The first RB is an RB with the smallest RB index of the SSB. In this example, the SSB comprises at least one of the followings: the first SSB, the second SSB, or the third SSB. In some examples, a location relevant to a CORESET comprises a second CRB that is overlapped with a second RB of the CORESET, where the second CRB is a CRB with the smallest CRB index that is overlapped with the second RB of the CORESET. The second RB of the CORESET is an RB with the smallest RB index of the CORESET. In some examples, the value of the offset is a number of RBs. In some examples, a subcarrier spacing (SCS) of CORESET 0 and an SCS of the SSB are same, where the SSB comprises at least one of the followings: the first SSB, the second SSB or the third SSB. In some examples, the offset is expressed according to the SCS of the CORESET 0. In some examples, when the SCS of the first SSB is 120 KHz, the SCS for CORESET 0 is assumed by the UE to be 120 KHz. In some examples, when the SCS of the first SSB is 480 KHz, the SCS for CORESET 0 is assumed by the UE to be 480 KHz. In some examples, when the SCS of the first SSB is 960 KHz, the SCS for CORESET 0 is assumed by the UE to be 960 KHz. Optionally, when the SCS of the first SSB is 120 KHz, 480 KHz, or 960 KHz, the SCS for CORESET 0 is assumed by the UE to be same as the SCS of the second SSB and/or the third SSB.

[0051] Commercial interests for some embodiments are as follows. 1. Solving issues in the prior art. 2. Providing a method for a UE to determine a position of a CORESET. 3. Reading cell global identifier (CGI) information. 4. Reducing the issue for a physical cell ID conflicting between different operators. 5. Some embodiments of the present disclosure are used by 5G-NR chipset vendors, V2X communication system development vendors, automakers including cars, trains, trucks, buses, bicycles, moto-bikes, helmets, and etc., drones (unmanned aerial vehicles), smartphone makers, communication devices for public safety use, AR/VR device maker for example gaming, conference/seminar, education purposes. Some embodiments of the present disclosure are a combination of “techniques/processes” that can be adopted in 3GPP specification to create an end product. Some embodiments of the present disclosure could be adopted in the 5G NR licensed and non-licensed or shared spectrum communications. Some embodiments of the present disclosure propose technical mechanisms.

[0052] FIG. 14 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and/or software. FIG. 14 illustrates the system 700 including a radio frequency (RF) circuitry 710, a baseband circuitry 720, an application circuitry 730, a memory/storage 740, a display 750, a camera 760, a sensor 770, and an input/output (I/O) interface 780, coupled with each other at least as illustrated. The application circuitry 730 may include a circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and dedicated processors, such as graphics processors, application processors. The processors may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system.

[0053] The baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi core processors. The processors may include a baseband processor. The baseband circuitry may handle various radio control functions that enables communication with one or more radio networks via the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi -mode baseband circuitry.

[0054] In various embodiments, the baseband circuitry 720 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency. The RF circuitry 710 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In various embodiments, the RF circuitry 710 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

[0055] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitry, the baseband circuitry, and/or the application circuitry. As used herein, “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, the application circuitry, and/or the memory/storage may be implemented together on a system on a chip (SOC). The memory/storage 740 may be used to load and store data and/or instructions, for example, for system. The memory/storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM)), and/or non-volatile memory, such as flash memory. [0056] In various embodiments, the I/O interface 780 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface. In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite. [0057] In various embodiments, the display 750 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, an AR/VR glasses, etc. In various embodiments, system may have more or less components, and/or different architectures. Where appropriate, methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

[0058] A person having ordinary skill in the art understands that each of the units, algorithm, and steps described and disclosed in the embodiments of the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the condition of application and design requirement for a technical plan. A person having ordinary skill in the art can use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he/she can refer to the working processes of the system, device, and unit in the above-mentioned embodiment since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed. [0059] It is understood that the disclosed system, device, and method in the embodiments of the present disclosure can be realized with other ways. The above-mentioned embodiments are exemplary only. The division of the units is merely based on logical functions while other divisions exist in realization. It is possible that a plurality of units or components are combined or integrated in another system. It is also possible that some characteristics are omitted or skipped. On the other hand, the displayed or discussed mutual coupling, direct coupling, or communicative coupling operate through some ports, devices, or units whether indirectly or communicatively by ways of electrical, mechanical, or other kinds of forms. The units as separating components for explanation are or are not physically separated. The units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments. Moreover, each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units.

[0060] If the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product. Or, one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other kinds of media capable of storing program codes. [0061] While the present disclosure has been described in connection with what is considered the most practical and preferred embodiments, it is understood that the present disclosure is not limited to the disclosed embodiments but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.