Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus, capable of improving access flexibility and applicable to a communication system. The method comprises: a first communication apparatus receives a first synchronization signal and physical broadcast channel block (SSB), and on the basis of information which is carried in indication information corresponding to the first SSB and is used for determining the priority of a first frequency domain resource corresponding to the first SSB, determines whether to access the first frequency domain resource. The priority of the first frequency domain resource is the priority for the first communication apparatus to access the first frequency domain resource.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202411929968.2, filed with the State Intellectual Property Office of China on December 23, 2024, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and communication device. Background Technology

[0003] In wireless communication systems, network devices can configure Service Shields (SSBs) for terminal devices, which can then receive and access the network based on the received SSBs. However, the location of the SSBs configured in this approach is limited, and the terminal device accesses the network on the frequency domain resources corresponding to the first SSB received, resulting in a lack of flexibility in access. Summary of the Invention

[0004] This application provides a communication method and a communication device that can improve access flexibility.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a communication method is provided. This communication method includes:

[0007] The first communication device receives a first synchronization signal and a physical broadcast channel block (SSB). The indication information corresponding to the first SSB carries information for determining the priority of the first frequency domain resource corresponding to the first SSB. The priority of the first frequency domain resource is the priority for the first communication device to access the first frequency domain resource. The first communication device determines whether to access the first frequency domain resource based on the priority of the first frequency domain resource.

[0008] Based on the communication method provided in the first aspect, the first communication device can receive the first SSB and determine whether to access the first frequency domain resource according to the priority of the first frequency domain resource indicated by the indication information corresponding to the first SSB. That is, it can determine whether to access the frequency domain resource according to the priority of the frequency domain resource, thereby improving the flexibility of access.

[0009] Furthermore, when prioritizing access to higher-priority frequency domain resources, higher-priority frequency domain resources can be accessed first, avoiding the large access delay caused by accessing lower-priority resources first and then higher-priority resources, thus improving communication efficiency.

[0010] As an example, the first communication device may be a terminal device, a communication module, a circuit or chip responsible for communication functions, a chip system, or other components or parts. This communication module, circuit or chip responsible for communication functions, chip system, or other components or parts may be used in the terminal device.

[0011] In one possible implementation, the method provided by the first aspect further includes: a first communication device receiving a second SSB, wherein the indication information corresponding to the second SSB carries information indicating the priority of a second frequency domain resource corresponding to the second SSB, the priority of the second frequency domain resource being higher than the priority of the first frequency domain resource, and the priority of the second frequency domain resource being the priority for the first communication device to access the second frequency domain resource. Thus, the received SSB can be determined based on the priority of the frequency domain resource, allowing access via an SSB on a higher-priority frequency domain resource, enabling rapid communication on the higher-priority frequency domain resource, and improving communication efficiency.

[0012] In one possible implementation, the first communication device receiving the second SSB includes: if it is determined that access to the first frequency domain resource will not be possible based on its priority, the first communication device receives the second SSB. Thus, even if access is not possible based on the first SSB, the second SSB on a higher-priority frequency domain resource can be received. This avoids accessing lower-priority frequency domain resources, reducing the access complexity of the first communication device, and receiving the SSB on a higher-priority frequency domain resource improves access efficiency.

[0013] In one possible implementation, the indication information corresponding to the first SSB also includes second information, which indicates the frequency domain location of the second SSB. Thus, by using the indication information corresponding to the first SSB received first to indicate the frequency domain location of the second SSB, searching for SSBs on other frequency domain resources can be avoided, reducing access latency.

[0014] Secondly, a communication method is provided. The communication method includes: a second communication device generating a first synchronization signal and a Physical Broadcast Channel Block (SSB), wherein the indication information corresponding to the first SSB carries information for determining the priority of a first frequency domain resource corresponding to the first SSB, the priority of the first frequency domain resource being the priority for the first communication device to access the first frequency domain resource; and the second communication device transmitting the first SSB.

[0015] Based on the communication method provided in the second aspect, the second communication device can send a first SSB, so that the first communication device can determine whether to access the first frequency domain resource according to the priority of the first frequency domain resource indicated by the indication information corresponding to the first SSB. That is, it can determine whether to access the frequency domain resource according to the priority of the frequency domain resource, thereby improving the flexibility of access.

[0016] Furthermore, when the first communication device prioritizes accessing higher-priority frequency domain resources, it can prioritize accessing higher-priority frequency domain resources, avoiding the large access delay caused by first accessing lower-priority resources and then higher-priority resources, thereby improving communication efficiency.

[0017] As an example, the second communication device may be a network device, a communication module, a circuit or chip responsible for communication functions, a chip system, or other components or parts. This communication module, circuit or chip responsible for communication functions, chip system, or other components or parts may be used in a network device.

[0018] In one possible implementation, the method provided by the second aspect further includes: the second communication device sending a second SSB, wherein the indication information corresponding to the second SSB carries information indicating the priority of the second frequency domain resource corresponding to the second SSB, the priority of the second frequency domain resource is higher than the priority of the first frequency domain resource, and the priority of the second frequency domain resource is the priority of the first communication device accessing the second frequency domain resource.

[0019] In one possible implementation, the indication information corresponding to the first SSB also includes second information, which is used to indicate the frequency domain position of the second SSB.

[0020] In one possible implementation, the priority of frequency domain resources is related to their frequency domain resource type. This allows the priority of frequency domain resources to be determined based on their frequency domain resource type, prioritizing access to frequency domain resources corresponding to specific types and improving access efficiency.

[0021] In one possible implementation, the first frequency domain resource and the second frequency domain resource are either resources from the same frequency domain resource set, or they are resources from different frequency domain resource sets. Thus, the first frequency domain resource containing the first SSB and the second frequency domain resource containing the second SSB can be resources from the same frequency domain resource set, enabling the presence of multiple frequency domain resource types within the same set and allowing the first communication device to access the corresponding frequency domain resource according to priority requirements. Alternatively, the first frequency domain resource containing the first SSB and the second frequency domain resource containing the second SSB can be resources from different frequency domain resource sets, enabling the presence of frequency domain resource types in different sets and allowing the first communication device to access the corresponding frequency domain resource set according to priority requirements.

[0022] In one possible implementation, the operator corresponding to the first frequency domain resource is the first operator, and the operators corresponding to the second frequency domain resource include both the first and second operators; or, the first frequency domain resource includes both the first and second operators, and the second frequency domain resource is the first operator; wherein, the first operator is the operator corresponding to the first communication device, and the second operator is different from the first operator. In this way, different priority access requirements can be defined for operator-dedicated frequency domain resources and operator-shared frequency domain resources, enabling priority-based access and improving access efficiency.

[0023] Thirdly, a communication method is provided. The communication method includes: a first communication device determining the priority of a third frequency domain resource and the priority of a fourth frequency domain resource, wherein the priority of the third frequency domain resource is the priority for the first communication device to access the third frequency domain resource, and the priority of the fourth frequency domain resource is the priority for the first communication device to access the fourth frequency domain resource; the first communication device determining whether to access the third frequency domain resource or the fourth frequency domain resource based on the priority of the third frequency domain resource and the priority of the fourth frequency domain resource.

[0024] Based on the communication method provided in the third aspect, the first communication device can determine the access frequency domain resources based on the priority of the third frequency domain resources and the priority of the fourth frequency domain resources. That is, it can determine whether to access frequency domain resources based on the priority of the frequency domain resources, thereby improving the flexibility of access.

[0025] In one possible implementation, the priority of frequency domain resources is related to the frequency domain resource type.

[0026] In one possible implementation, the third frequency domain resource and the fourth frequency domain resource are frequency domain resources in the same set of frequency domain resources, or the third frequency domain resource and the fourth frequency domain resource are frequency domain resources in different sets of frequency domain resources.

[0027] In one possible implementation, the operator corresponding to the third frequency domain resource is the first operator, and the operator corresponding to the fourth frequency domain resource includes both the first operator and the second operator; or, the third frequency domain resource includes both the first operator and the second operator, and the fourth frequency domain resource is the first operator; wherein, the first operator is the operator corresponding to the first terminal device, and the second operator is different from the first operator.

[0028] In one possible implementation, the method provided by the third aspect further includes: the first communication device sending a random access request on the third or fourth frequency domain resource to be accessed, based on the priority of the third frequency domain resource and the priority of the fourth frequency domain resource.

[0029] Fourthly, a communication device is provided. This communication device is used to execute the communication method described in any one of the implementations of the first to third aspects.

[0030] In this application, the communication device described in the fourth aspect can be a terminal device, a communication module, a circuit with communication function, a chip, a chip system, or other components or assemblies. The communication module, the circuit with communication function, the chip, the chip system, or other components or assemblies can be applied in the terminal device. Alternatively, the communication device can be a network device (such as a radio access network (RAN) node), a communication module, a circuit with communication function, a chip, a chip system, or other components or assemblies. The communication module, the circuit with communication function, the chip, the chip system, or other components or assemblies can be applied in the network device.

[0031] It should be understood that the communication apparatus described in the fourth aspect includes modules, units, or means that implement the communication methods described in any of the first to third aspects. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units for performing the functions involved in the aforementioned communication methods.

[0032] Fifthly, a communication device is provided. The communication device includes a processor configured to execute the communication method described in any of the possible implementations of the first to third aspects.

[0033] In one possible implementation, the communication device described in the fifth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the fifth aspect and other communication devices.

[0034] In one possible implementation, the communication device described in the fifth aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs (or code instructions or program instructions) and / or data related to the communication method described in any of the first to third aspects.

[0035] In this application, the communication device described in the fifth aspect can be a terminal device, a communication module, a circuit with communication function, a chip, a chip system, or other components or assemblies. The communication module, the circuit with communication function, the chip, the chip system, or other components or assemblies can be applied in a terminal device. Alternatively, the communication device can be a network device, a communication module, a circuit with communication function, a chip, a chip system, or other components or assemblies. The communication module, the circuit with communication function, the chip, the chip system, or other components or assemblies can be applied in a network device.

[0036] A sixth aspect provides a communication device. The communication device includes a processor coupled to a memory, the processor executing a computer program stored in the memory, such that the communication device performs the communication method described in any of the possible implementations of the first to third aspects.

[0037] In one possible implementation, the communication device described in the sixth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the sixth aspect and other communication devices.

[0038] In this application, the communication device described in the sixth aspect can be a terminal device, a communication module, a circuit with communication function, a chip, a chip system, or other components or assemblies. The communication module, the circuit with communication function, the chip, the chip system, or other components or assemblies can be applied in a terminal device. Alternatively, the communication device can be a network device, a communication module, a circuit with communication function, a chip, a chip system, or other components or assemblies. The communication module, the circuit with communication function, the chip, the chip system, or other components or assemblies can be applied in a network device.

[0039] A seventh aspect provides a communication device, comprising: a processor and a memory; the memory being used to store a computer program, which, when executed by the processor, causes the communication device to perform the communication method described in any one of the first to third aspects.

[0040] In one possible implementation, the communication device described in the seventh aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the seventh aspect and other communication devices.

[0041] In this application, the communication device described in the seventh aspect can be a terminal device, a communication module, a circuit with communication function, a chip, a chip system, or other components or assemblies. The communication module, the circuit with communication function, the chip, the chip system, or other components or assemblies can be applied in a terminal device. Alternatively, the communication device can be a network device, a communication module, a circuit with communication function, a chip, a chip system, or other components or assemblies. The communication module, the circuit with communication function, the chip, the chip system, or other components or assemblies can be applied in a network device.

[0042] Eighthly, a communication device is provided, comprising: a processor; the processor being coupled to a memory and, after reading a computer program from the memory, executing a communication method according to the computer program as described in any one of the first to third aspects.

[0043] In one possible implementation, the communication device described in the eighth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the eighth aspect and other communication devices.

[0044] In this application, the communication device described in the eighth aspect can be a terminal device, a communication module, a circuit with communication function, a chip, a chip system, or other components or assemblies. The communication module, or the circuit, chip, chip system, or other components or assemblies with communication function can be applied in the terminal device. Alternatively, the communication device can be a network device (such as a radio access network (RAN) node), a communication module, a circuit, chip, chip system, or other components or assemblies with communication function. The communication module, the circuit, chip, chip system, or other components or assemblies with communication function can be applied in the network device.

[0045] Ninthly, a communication system is provided. The communication system includes one or more terminal devices and one or more network devices.

[0046] A tenth aspect provides a computer-readable storage medium comprising: a computer program or instructions; which, when executed on a computer, causes the computer to perform the communication method described in any one of the possible implementations of the first to third aspects.

[0047] Eleventhly, a computer program product is provided, comprising a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method described in any one of the possible implementations of the first to third aspects.

[0048] Furthermore, the technical effects of the fourth to eleventh aspects mentioned above can be referred to with reference to the technical effects of the communication methods described in the first to third aspects, and will not be repeated here. Attached Figure Description

[0049] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0050] Figure 2 is a schematic diagram of one implementation of resource allocation;

[0051] Figure 3 is a schematic diagram of the relationship between REG and CCE;

[0052] Figure 4 is a schematic diagram of the architecture of a communication system when operators share access network equipment;

[0053] Figure 5 is a schematic diagram of another communication system architecture when operators share access network equipment.

[0054] Figure 6 is a schematic diagram of the frequency domain resource set provided in an embodiment of this application;

[0055] Figure 7 is a schematic diagram of another frequency domain resource set provided in an embodiment of this application;

[0056] Figure 8 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0057] Figure 9 is a schematic diagram of the frequency domain resource set allocated to the second communication device;

[0058] Figure 10 is a schematic diagram of a frequency domain positional relationship between SSBs provided in an embodiment of this application;

[0059] Figure 11 is a schematic diagram of another frequency domain positional relationship between SSBs provided in an embodiment of this application;

[0060] Figure 12 is a schematic diagram of another frequency domain positional relationship between SSBs provided in an embodiment of this application;

[0061] Figure 13 is a schematic diagram of another frequency domain positional relationship between SSBs provided in an embodiment of this application;

[0062] Figure 14 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0063] Figure 15 is a schematic diagram of the communication device provided in an embodiment of this application;

[0064] Figure 16 is a schematic diagram of the structure of the communication device provided in the embodiment of this application. Detailed Implementation

[0065] The technical solutions of this application embodiment can be applied to various communication systems, such as wireless fidelity (WiFi) systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, 4th generation (4G) mobile communication systems, such as long term evolution (LTE) systems, 5th generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems, etc.

[0066] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0067] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as an "example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Rather, the use of the word "example" is intended to present the concept in a specific manner.

[0068] First, in this application, "for indicating" can include both direct and indirect indication. When describing "information" for indicating A, it can include whether the information directly indicates A or indirectly indicates A, but does not necessarily mean that the information carries A.

[0069] The information indicated by a given piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing the indication overhead to some extent. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information.

[0070] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0071] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device. This configuration information can include, for example, but not limited to, higher-layer signaling and / or physical-layer signaling. For example, higher-layer signaling can include radio resource control (RRC) signaling or medium access control (MAC) layer signaling. This configuration information can include, for example, but not limited to, one or a combination of at least two of higher-layer and physical-layer signaling. MAC layer signaling includes, for example, a medium access control-control element (MAC CE); physical (PHY) layer signaling includes, for example, downlink control information (DCI).

[0072] Second, in the embodiments shown below, the first, second, and various numerical designations are merely distinctions for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, to distinguish different indication information.

[0073] Third, "pre-defined," "pre-configured," or "pre-specified" can be achieved by pre-saving corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including terminal devices and network devices), or by pre-defining them in a protocol. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0074] Fourth, the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communications, such as LTE protocols of the 3rd generation partnership project (3GPP) (such as technical specification (TS) 36, i.e., the TS36 series of technical specifications), NR protocols (such as the TS38 series of technical specifications), and related protocols applied to future communication systems. This application does not limit this.

[0075] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0076] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0077] To facilitate understanding of the embodiments of this application, the communication system applicable to the embodiments of this application will be described in detail first using the communication system shown in FIG1 as an example. Exemplarily, FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in FIG1, the communication system includes network devices (such as access network devices) and terminal devices.

[0078] As shown in Figure 1, the communication system includes at least one access network device (such as access network device 110a and access network device 110b) and at least one terminal device (such as terminal device 120a to terminal device 120j).

[0079] Terminal devices can connect to access network devices wirelessly, and access network devices can connect to the core network (not shown in Figure 1) via wired or wireless means.

[0080] Among them, access network equipment and terminal equipment can exchange information.

[0081] The communication system may also include a core network 130. Access network devices connect to the core network 130 wirelessly or via wired means. The core network devices and access network devices in the core network 130 can be independent and different physical devices, or they can be the same physical device that integrates the logical functions of the core network devices and the logical functions of the access network devices. The communication system may also include the Internet 140.

[0082] Terminal equipment can be a terminal with transceiver capabilities. This terminal equipment can also be referred to as user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user apparatus. The terminal devices in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, and roadside units with terminal functions. The terminal device in this application can also be an onboard module, onboard unit, onboard component, onboard chip, or onboard unit, which is built into a vehicle as one or more components or units. The terminal device can also be other devices with terminal functions; for example, it can be a device that performs terminal functions in D2D communication. The embodiments of this application do not limit the device form of the terminal device. The device used to implement the function of the terminal device can be the terminal device itself; it can also be a device that supports the terminal device in implementing the function, such as a communication module, chip, chip system, other components or parts, or circuits or functional components. This device can be installed in the terminal device or used in conjunction with the terminal device. The chip system can be composed of chips or include chips and other discrete devices.Among them, the various forms of terminal devices mentioned above can also be referred to as terminal-side devices.

[0083] In this application embodiment, the access network device can be a device with wireless transceiver capabilities. For example, the access network device can be a device located in the access network (AN) of a communication system, which can be used to provide access services for terminal devices. In one possible scenario, the access network device can be a radio access network (RAN) device, such as a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), an integrated access and backhaul (IAB) node, an IAB parent node, or a base station in a future communication system. In future mobile communication systems, the access network device may also have other naming conventions, all of which are covered within the protection scope of this application embodiment, and this application does not impose any limitations on them. Alternatively, the access network device may also include 5G, such as a gNB in ​​an NR system, or one or a group (including multiple antenna panels) of antenna panels of a 5G base station, or it may be a network node constituting a gNB, a transmission point (TRP or transmission point (TP), or a transmission measurement function (TMF). Alternatively, the access network device can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the access network device can also be a server, wearable device, vehicle, or in-vehicle equipment, etc. For example, the access network device in V2X technology can be an RSU. All or part of the functions of the access network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network device in this application can also be a logical node, logical module, or software capable of implementing all or part of the access network device functions.

[0084] In another possible scenario, multiple access network devices collaborate to assist terminal devices in achieving wireless access, with each access network device performing a portion of the base station's functions. For example, the access network devices can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and DU can be configured separately or included in the same network element, such as a baseband unit (BBU). The RU can be included in radio frequency equipment or radio frequency units, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0085] In different systems, CU (or centralized unit control plane (CU-CP)) and centralized unit user plane (CU-UP)), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (O-RAN or ORAN) system, CU can also be called an open centralized unit (O-CU) (open CU), DU can also be called an open distributed unit (O-DU), CU-CP can also be called an open centralized unit control plane (O-CU-CP), CU-UP can also be called an open centralized unit user plane (O-CU-UP), and RU can also be called an open radio unit (O-RU). For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the CU (or CU-CP, CU-UP), DU and RU units in this application can be implemented through a software module, a hardware module, or a combination of software and hardware modules.

[0086] In this embodiment, the form of the network device (such as an access network device) is not limited. The device used to implement the function of the network device can be the network device itself; it can also be any device that supports the network device in implementing that function, such as a communication module, chip, chip system, other components or parts, or circuits or functional components. This device can be installed in the network device or used in conjunction with the network device. The chip system can be composed of chips or can include chips and other discrete devices. The network devices of the various forms described above can also be referred to as network-side devices.

[0087] It should be understood that Figure 1 is a simplified schematic diagram for ease of understanding only, and the communication system may also include other network devices and / or other terminal devices, which are not shown in Figure 1.

[0088] It should be understood that the above system application scenarios are merely examples, and this application can also be applied to other scenarios, which will not be listed here.

[0089] In wireless communication systems (such as the system shown in Figure 1), wireless communication resources may include time-frequency resources. The following explanation of time-frequency resources will use an NR system as an example. It should be understood that NR can also be replaced with 5G or 5G NR.

[0090] The technical terms and related technical solutions in this application will be described below with reference to the accompanying drawings.

[0091] 1. Parameter set (numerology).

[0092] 5G NR introduces the concept of a parameter set, which includes sub-carrier spacing (SCS) and corresponding parameters such as symbol length and cyclic prefix (CP) length. Because there is a mapping relationship between SCS and symbol length / CP length, SCS is often used instead of parameter set in some literature.

[0093] For example, the parameters involved in the parameter set are shown in Table 1.

[0094] Table 1

[0095] In Table 1, μ represents the subcarrier spacing index, or μ represents the parameter set, CP length includes the normal CP length and the extended CP length, and FR represents the frequency range (FR).

[0096] 2. Spectrum resources.

[0097] A resource element (RE) is the smallest granularity physical layer resource in 5G NR, which is one subcarrier in the frequency domain and one OFDM symbol in the time domain.

[0098] A resource block (RB) is the basic unit of channel resource allocation in the frequency domain in 5G NR. An RB can contain 12 subcarriers. Since the subcarrier spacing in 5G NR is variable, the actual bandwidth of an RB is also variable.

[0099] A resource grid (RG) is a collection of time-frequency resources. In 5G NR, it is defined as follows: For each carrier with different parameter sets, an RG is a resource set of all subcarriers in the frequency domain and all symbols within one subframe in the time domain, with the frequency domain starting at the granularity of RBs. Since different parameter sets correspond to different SCSs, and one RB consists of 12 subcarriers, the number of RBs in an RG differs depending on the parameter set for the same transmission bandwidth. An RG in the time domain is one subframe. Furthermore, uplink and downlink each define their own RGs.

[0100] Figure 2 illustrates one implementation of resource allocation. In Figure 2, a subframe in the time domain can include several OFDM symbols; an RE represents a resource with one subcarrier in the frequency domain and one OFDM symbol in the time domain; an RB contains 12 subcarriers in the frequency domain; and an RG represents a set of time-frequency resources.

[0101] A common resource block (CRB) can be understood as a collective term for all resource blocks (RBs) in 5G NR. They are numbered starting from 0, and the center frequency point of subcarrier number 0 in CRB0 is point A.

[0102] A physical resource block (PRB) refers to the RBs contained in the bandwidth part (BWP) of a UE in 5G NR. They are also numbered starting from 0 and are the basic unit of data channel scheduling.

[0103] A resource block group (RBG) refers to a combination of several resource block blocks (PRBs) within a bandwidth portion (BWP). Numbered starting from 0, it is the basic unit of data channel scheduling. An RBG can contain {2, 4, 8, 16} PRBs, the specific number depending on the number of RBs in the BWP and the configuration. The number of PRBs in an RBG can also be called the RGB size, and the number of RBs in the BWP can be called the BWP size. Configuration options can include Configuration 1 and Configuration 2. Table 3 shows the relationship between the RGB size, configuration options, and BWP size, and Table 2 shows the relationship between the RGB size and the configuration options.

[0104] Table 2

[0105] A resource element group (REG) is the basic unit of control channel resources. One REG represents 12 subcarriers (RB) in the frequency domain and one OFDM symbol in the time domain. Optionally, a REG can be replaced by a resource unit group.

[0106] The control channel element (CCE) is the basic unit for scheduling control channel resources. One CCE consists of 6 REGs in the frequency domain.

[0107] Figure 3 shows a schematic diagram of the relationship between REG and CCE.

[0108] The above defines the time-frequency resources for NR. Future networks may use the same or different definitions. For example, future networks may define multiple subcarrier spacings, not limited to the SCS in 5G. A time slot can include one or more symbols, and an RB can include one or more subcarriers, etc.

[0109] 3. Channel

[0110] The Physical Reception Link Control Channel (PRxCCH) is a physical layer control channel. Generally, standard protocols describe it from the perspective of the terminal device; it's the physical layer control channel received by the terminal device, similar in function to the PDCCH in LTE and 5G. PRxCCH may be a new physical layer control channel introduced in future communication systems. Of course, future communication systems may still use PDCCH to represent the physical downlink control channel or physical transmit link control channel of the terminal device.

[0111] The Physical Reception Link Shared Channel (PRxSCH) is a physical layer data channel. Generally, standard protocols describe it from the perspective of the terminal device; it refers to the physical layer data channel received by the terminal device, similar in function to the Physical Downlink Shared Channel (PDSCH) in LTE and 5G. PRxSCH may be a newly introduced physical layer data channel in future communication systems. However, future communication systems may still use PDSCH to represent the physical downlink data channel or physical reception link data channel of the terminal device.

[0112] The Physical Transmission Link Control Channel (PTxCCH) is a physical layer control channel. Generally, standard protocols describe it from the perspective of the terminal device; it refers to the physical layer control channel transmitted by the terminal device, similar in function to the Physical Uplink Control Channel (PUCCH) in LTE and 5G. PTxCCH may be a new physical layer control channel introduced in future communication systems. However, future communication systems may still use PUCCH to represent the physical uplink control channel or physical transmission link control channel of the terminal device.

[0113] The Physical Transmission Link Shared Channel (PTxSCH) is a physical layer data channel. Generally, standard protocols describe it from the perspective of the terminal device; it refers to the physical layer data channel transmitted by the terminal device, similar in function to the Physical Uplink Shared Channel (PUSCH) in LTE and 5G. PTxSCH may be a new physical layer data channel introduced in future communication systems. However, future communication systems may still use PUSCH to represent the physical uplink data channel or physical receive link data channel of the terminal device.

[0114] Optionally, from the perspective of the terminal device, downlink can be described as receiving; and from the perspective of the terminal device, uplink can be described as sending.

[0115] Multi-operator spectrum sharing refers to the ability of multiple operators to conduct wireless network communication on the same spectrum segment, meaning multiple operators can operate in the same frequency band and share the same spectrum. For example, operator A can communicate with terminal device 1 on spectrum resource A, and operator B can also communicate with terminal device 2 on spectrum resource A.

[0116] 4. Public Land Mobile Network (PLMN).

[0117] 4.1 A PLMN is a network established and operated by a competent authority or an authorized private telecommunications entity to provide terrestrial mobile communication services to the public.

[0118] A PLMN ID is the network identifier corresponding to a PLMN, which includes the mobile country code (MCC) and the mobile network code (MNC). An operator owns one or more PLMN IDs, and each PLMN ID is globally unique.

[0119] 4.2 Classification of PLMNs.

[0120] The location of terminal devices in a mobile network changes dynamically. To ensure that terminal devices can access mobile network services normally in different locations, the access and mobility management function (AMF) in the core network manages the access and mobility of terminal devices. During the AMF's access and mobility management process, when a terminal device registers, disconnects from the network, or re-enters the network, the same PLMN will be identified as different categories. For example, the relevant concepts of PLMN can be shown in Table 3.

[0121] Table 3

[0122] When a terminal device powers on or disconnects from the network, it will trigger a search for the PLMN. Terminal devices can search for the PLMN automatically or manually.

[0123] (1) Automatic network search refers to selecting a suitable PLMN for access based on the PLMN information recorded in the memory or SIM card, according to priority. For example, the terminal device's PLMN selection status includes one of the following three states: Trying to register with the PLMN (Trying RPLMN / PLMN), Waiting for the PLMN (Wait for PLMNs / Wait for PLMNs to appear), or Successfully registered on the PLMN (On PLMN).

[0124] When attempting to register a PLMN, the terminal device prioritizes RPLMN for registration. If the registration is successful, the terminal device will enter a state of successful registration on the PLMN. If the registration fails, the terminal device will begin selecting PLMNs according to the following priority: EPLMN, EHPLMN, HPLMN, UPLMN, OPLMN, VPLMN, and other PLMNs.

[0125] If the terminal device searches for all PLMNs but still finds no available PLMN, the terminal device enters a state of waiting for a PLMN.

[0126] Once a PLMN is successfully registered, the terminal device will periodically monitor the PLMN information. When the successfully registered PLMN becomes unavailable, the terminal device will enter a state of attempting to register a new PLMN and select a new PLMN.

[0127] Waiting for a PLMN: Currently, there are no allowed or available PLMNs, and the terminal device is waiting for a PLMN to appear. The terminal device will periodically search for available PLMNs. When an available PLMN appears, the terminal device enters the state of attempting to register a PLMN and selects a new PLMN.

[0128] During the automatic network search process, the terminal device can periodically detect the PLMN and continuously change between three states of selecting the PLMN.

[0129] (2) Manual network search refers to the terminal device providing the user with a list of available PLMNs, allowing the user to choose a PLMN to connect to. When the terminal device selects a PLMN from the list of available PLMNs, initiates registration, and the registration is successful, the terminal device can obtain normal network services.

[0130] 4.3. Multiple operators share the network.

[0131] In a communication system, there may be multiple operators, and different operators can share networks. Each operator can provide communication services to its own users, and each operator has its own core network. As shown in Figure 4, taking operators A and B as examples, operators A and B share access network equipment, and each operator A and operator B corresponds to a core network. Terminal devices (which can also be understood as users) corresponding to operator A communicate with operator A's core network through the access network equipment, and terminal devices (which can also be understood as users) corresponding to operator B communicate with operator B's core network through the access network equipment.

[0132] Different operators can share networks in the following ways: independent carrier access network (RAN) sharing and multi-operator core network (MOCN) sharing.

[0133] In a shared independent carrier access network (ICN), multiple operators each have their own complete core network, and while they share RAN equipment, they do not share radio spectrum resources. In this scenario, for the core network, it's equivalent to a single set of radio equipment being divided into multiple "virtual devices," with each core network interface connecting to these "virtual" devices. For example, consider operators A and B. As shown in Figure 5(a), assuming operators A and B share a network using an ICN sharing approach, the core network elements of operator A and operator B are independent of each other. For instance, operator A's core network elements include a Mobility Management Entity (MME)1 connected to the access network equipment, a System Architecture Evolution-Gateway (SAE-GW)1 connected to MME1, and a Home Subscriber Server (HSS)1 connected to MME1. Operator B's core network elements include an MME2 connected to the access network equipment, an SAE-GW2 connected to MME2, and an HSS2 connected to MME2. Operator A and Operator B share access network equipment, but the frequencies used by different operators for providing services on the access network equipment are different. For example, Operator A uses cell 1 to provide services, while Operator B uses cell 2. Cell 1 and cell 2 use different frequencies.

[0134] In MOCN (Multi-access Network) sharing, multiple operators share the radio access network and radio spectrum resources, but not the core network equipment, thus saving operators' investment costs. Throughout the solution, operators share radio spectrum resources. Access network equipment broadcasts information indicating multiple PLMN identifiers within the same spectrum (e.g., a cell). Terminal equipment can identify the multiple PLMN identifiers broadcast by the access network equipment and select the appropriate PLMN for access. For example, the following example combines operators A and B. As shown in Figure 5(b), assuming operators A and B share the network in MOCN mode, then the core network elements of operator A and operator B are independent of each other. For example, operator A's core network elements include MME1 connected to the access network equipment, SAE-GW1 connected to MME1, and HSS1 connected to MME1; operator B's core network elements include MME2 connected to the access network equipment, SAE-GW2 connected to MME2, and HSS2 connected to MME2. Operators A and B share access network equipment, and the frequencies used by different operators for providing services on the access network equipment are the same. For example, operator A uses cell 3 to provide services, and operator B also uses cell 3 to provide services.

[0135] It is understood that the MME1 mentioned above can also be replaced by Serving General Packet Radio Service Support Node (SGSN)1, MME2 can also be replaced by SGSN2, HSS1 can also be replaced by Home Location Register (HLR)1, and HSS2 can also be replaced by HLR2.

[0136] It is understood that the core network elements in Figure 5 above are for illustrative purposes. In different evolved versions of communication systems, the core network elements may have other possible names, and the core network may include more or fewer network elements, which will not be elaborated here.

[0137] 5. Frequency domain resource set.

[0138] A frequency domain resource set refers to a collection of one or more frequency domain resources. A frequency domain resource set can support communication of a cell on frequency domain resources in at least one frequency band. For example, a frequency domain resource set may include one or more frequency domain resources within the same frequency band, or it may include multiple carriers within multiple frequency bands. A frequency domain resource may include one or more component carriers (CCs), or a component carrier representing a portion of the frequency domain resources. In this case, a frequency domain resource set may include one or more carriers. It is understood that a frequency domain resource set can also be called a uni-carrier or a CC group, where a carrier group includes one or more frequency domain resources. Alternatively, a frequency domain resource set may have other possible names, which will not be elaborated upon here.

[0139] A frequency band can refer to a segment of frequency domain resources, which may include contiguous resources or discontinuous resources. Optionally, the frequency band in this application may be the operating band defined by the NR protocol in the prior art, or it may be a portion of the frequency domain resources within the operating band.

[0140] In a communication system, one or more frequency domain resource sets can be configured. For example, as shown in Figure 6, an access network device can be configured with three frequency domain resource sets, such as frequency domain resource set 0, frequency domain resource set 1, and frequency domain resource set 2. Frequency domain resource set 0 can include multiple frequency domain resources, frequency domain resource set 1 can include multiple frequency domain resources, and frequency domain resource set 2 can include multiple frequency domain resources. The same frequency domain resource set is configured using the same information or signaling. For example, the same frequency domain resource set can be configured using the same system information. One or more frequency domain resource sets can be configured using the same information or signaling. When configuring multiple frequency domain resource sets in a communication system...

[0141] Optionally, frequency domain resources within the same frequency domain resource set are equivalent to a single logical carrier. For example, frequency domain resources within the same set can share a single radio frequency channel, and / or the signals carried by frequency domain resources within the same set can be used together for FFT operations. Referring to frequency domain resource sets 0 to 2 in Figure 6 above, frequency domain resource set 0 is equivalent to a single logical carrier, frequency domain resource set 1 is equivalent to a single logical carrier, and frequency domain resource set 2 is equivalent to a single logical carrier. It should be understood that some frequency domain resources within the same set can also be equivalent to a single logical carrier.

[0142] Optionally, frequency domain resource sets can be divided according to the frequency band or frequency range in which the frequency domain resources are located. Taking CCs as an example, multiple CCs within frequency range 1 (FR1) constitute a frequency domain resource set, multiple CCs within frequency range 2 (FR2) constitute a frequency domain resource set, and multiple CCs within frequency range 3 (FR3) constitute a frequency domain resource set. The frequency range of FR1 is 450 MHz to 6000 MHz. FR1 can also be referred to as the 6 GHz (Sub-6 GHz) band. The frequency range of FR2 is 24250 MHz to 52600 MHz. FR2 is commonly referred to as the millimeter wave (mmWave) band. The frequency range of FR3 is 6000 MHz to 24250 MHz. FR3 is the band between FR1 and FR2, and is commonly referred to as the 24 GHz (Sub-24 GHz) band. It is understood that the frequency domain resource allocation method described here is only for illustrative purposes. In actual implementation, the same frequency domain resource set may also include CCs from different frequency ranges, or the same frequency domain resource set may include some CCs from the same frequency range. It is understood that each frequency range may include at least one frequency band.

[0143] The frequency band in this application can be FR1, FR2, or FR3. FR3 refers to the frequency band located between 6000MHz and 24250MHz. FR3 is the frequency band between FR1 and FR2, and can be referred to as the "Sub-24GHz" frequency band.

[0144] The frequency ranges FR1, FR2, and FR3 in this embodiment are for illustrative purposes only. In actual implementation, other ways of dividing the frequency range may exist, which will not be elaborated here.

[0145] For two frequency domain resources in the same frequency domain resource set, they can be co-located (i.e. used for communication between the same access network device and terminal device) or non-co-located (i.e. used for communication between different access network devices and terminal devices).

[0146] Optionally, the frequency domain resource set may include only one operator-specific frequency domain resource. For example, as shown in Figure 7(a), the frequency domain resource set includes frequency domain resources dedicated to operator A, or as shown in Figure 7(b), the frequency domain resource set includes frequency domain resources dedicated to operator B.

[0147] Optionally, the frequency domain resource set may include only frequency domain resources shared by operators. For example, as shown in Figure 7(c), the frequency domain resource set may include frequency domain resources shared by operators A and B.

[0148] Optionally, the frequency domain resource set may include operator-specific frequency domain resources and operator-shared frequency domain resources. For example, as shown in Figure 7(d), the frequency domain resource set may include operator A's dedicated frequency domain resources and frequency domain resources shared by operators A and B. As shown in Figure 7(e), the frequency domain resource set may include operator B's dedicated frequency domain resources and frequency domain resources shared by operators A and B. As shown in Figure 7(f), the frequency domain resource set may include operator A's dedicated frequency domain resources, operator B's dedicated frequency domain resources, and frequency domain resources shared by operators A and B.

[0149] Optionally, the frequency domain resource set may include frequency domain resources dedicated to different operators. For example, the frequency domain resource set may include frequency domain resources dedicated to operator A and frequency domain resources dedicated to operator B. It is understood that the quantity of each type of frequency domain resource in Figure 7 is for illustrative purposes only.

[0150] 6. Absolute Radio Frequency Channel Number (ARFCN) indication information, used to indicate ARFCN information.

[0151] The global frequency grid defines a set of radio frequency (RF) reference frequencies F. REF The RF reference frequency is used in signaling to identify the location of the RF channel, synchronization signal and physical broadcast channel block (SSB), and other information.

[0152] The global frequency grid is defined as all frequencies within the range of 0 to 100 GHz. The granularity of the global frequency grid is ΔF. Global .

[0153] For the FR1 band, the RF reference frequency is specified by the NR-ARFCN (range [0, ..., 2016666]) in the global frequency grid. The NR frequency point and the RF reference frequency F... REF The relationship shown in formula (1) is satisfied. F REF =F REF-Offs +ΔF Global (N REF -N REF-Offs (1)

[0154] Where, N REF This refers to the NR absolute radio frequency channel number (NR-ARFCN). REF-Offs For use in calculating N REF The offset used for calculating N REF F REF-Offs Indicates the use of F for calculation REF The offset.

[0155] Among them, frequency range, F REF-Offs ΔF Global N REF-Offs N REF range of N REF The correspondence between them is shown in Table 4 below.

[0156] Table 4

[0157] For the FR2 band, the RF reference frequency is specified by the NR-ARFCN (range [2016667, ..., 3279165]) in the global frequency grid. The NR frequency point and the RF reference frequency F... REF The relationship between (in MHz) satisfies the relationship shown in formula (1). The difference is that, in this case, the frequency range, F REF-Offs ΔF Global N REF-Offs N REF The correspondence between the ranges is shown in Table 5 below.

[0158] Table 5

[0159] In some examples, the ARFCN indication information may be the NR global frequency raster.

[0160] In the above parameters, FR can be measured in MHz, ΔF Global The unit can be kHz, F REF-Offs The unit can be MHz.

[0161] 7. Carrier aggregation (CA).

[0162] Carrier aggregation provides greater bandwidth to a single terminal device by aggregating multiple carrier aggregation (CCs). This allows the terminal device to enjoy bandwidth equal to the total bandwidth of all CCs, thereby increasing peak rates.

[0163] CA can be applied to 3CC aggregation scenarios. In this case, a terminal device is served by three carriers simultaneously, one of which is the primary component carrier (PCC), and the other two are secondary component carriers (SCCs). The cell where the PCC is located is called the primary cell (PCell), and the cell where the SCC is located is called the secondary cell (SCell).

[0164] Based on whether the aggregated multiple CCs belong to the same frequency band and are continuous in the frequency domain, CA can be divided into the following categories: (1) Intra-band contiguous CA, where multiple CCs belong to the same frequency band and are continuous in the frequency domain. (2) Intra-band non-contiguous CA, where multiple CCs belong to the same frequency band but are not continuous in the frequency domain. (3) Inter-band CA, where multiple CCs belong to different frequency bands. In this case, the multiple CCs are usually not continuous in the frequency domain.

[0165] In wireless communication systems, network devices can configure Service Shields (SSBs) for terminal devices, which can then receive and access the network based on the received SSBs. However, the location of the SSBs configured in this approach is limited, and the terminal device accesses the network on the frequency domain resources corresponding to the first SSB received, resulting in a lack of flexibility in access.

[0166] To address the aforementioned technical problems, embodiments of this application provide a communication method. This communication method can determine which frequency domain resources to use for access based on the priority of frequency domain resources, thereby improving access flexibility.

[0167] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0168] It should be noted that the communication method provided in this application embodiment can be applied between any two devices shown in Figure 1, such as between a terminal device and a network device. For specific implementation, please refer to the following method embodiment, which will not be repeated here.

[0169] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0170] The communication method provided in the embodiments of this application will be described in detail below with reference to Figure 8.

[0171] For example, Figure 8 is a schematic flowchart of a communication method provided in an embodiment of this application. This communication method can be applied to communication between a first communication device (the terminal device shown in Figure 1) and a second communication device (the access network device shown in Figure 1). For ease of understanding, the following embodiments will use the first communication device as the first terminal device and the second communication device as the access network device as examples.

[0172] As shown in Figure 8, the communication method includes:

[0173] S801, the second communication device generates a first synchronization signal and a physical broadcast channel block (SSB).

[0174] The indication information corresponding to the first SSB carries information for determining the priority of the first frequency domain resource corresponding to the first SSB. The priority of the first frequency domain resource is the priority of the first communication device accessing the first frequency domain resource.

[0175] In some examples, the first SSB can be a carrier-dedicated SSB, or the first SSB can be carried on carrier-dedicated frequency domain resources.

[0176] In some examples, the first SSB can be an operator-shared SSB, or in other words, the first SSB is carried on operator-shared frequency domain resources.

[0177] The indication information corresponding to the first SSB can be information in the first SSB, such as the master information block (MIB), or other information indicated by the information in the first SSB, such as the system information block (SIB).

[0178] Optionally, the indication information corresponding to the first SSB carries information for determining the priority of the first frequency domain resource corresponding to the first SSB, which can be described as: the indication information corresponding to the first SSB includes information for determining the priority of the first frequency domain resource corresponding to the first SSB, or the indication information corresponding to the first SSB includes information on the priority of the first frequency domain resource corresponding to the first SSB.

[0179] In this embodiment of the application, the frequency domain resource corresponding to an SSB refers to the frequency domain resource where the SSB is located, or in other words, the frequency domain resource carrying the SSB. The first frequency domain resource corresponding to the first SSB refers to the frequency domain resource where the first SSB is located, or in other words, the frequency domain resource carrying the first SSB.

[0180] The priority of frequency domain resources is the priority of terminal devices accessing frequency domain resources.

[0181] In one possible implementation, the priority of frequency domain resources is related to their frequency domain resource type. For example, the priority of the first frequency domain resource is related to the priority of its frequency domain resource type. The frequency domain resource type can be classified according to different rules, which will be discussed later and will not be repeated here.

[0182] In some examples, frequency domain resources of different types have different priorities.

[0183] Optionally, the priority of frequency domain resource types is related to the characteristics of the terminal device. These characteristics can also be the characteristics of the user using the terminal device. For example, for a terminal device corresponding to a high-priority user, such as a paid premium member (VIP), the priority of the operator-dedicated frequency domain resource corresponding to the terminal device is higher than the priority of the operator-shared frequency domain resource corresponding to the terminal device. For a low-priority user, such as a regular user, the priority of the operator-shared frequency domain resource corresponding to the terminal device is higher than the priority of the operator-dedicated frequency domain resource corresponding to the terminal device.

[0184] Optionally, the priority of frequency domain resource types is related to the needs of the terminal device. The needs of the terminal device can also be the needs of the users using the terminal device.

[0185] For example, in scenarios where the number of terminal devices is less than or equal to a first threshold and / or the service demand is less than or equal to a second threshold, the priority of operator-shared frequency domain resources is higher than the priority of operator-dedicated frequency domain resources. In scenarios where the number of terminal devices exceeds the first threshold and the service demand exceeds the second threshold, the priority of operator-dedicated frequency domain resources is higher than the priority of operator-shared frequency domain resources.

[0186] Optionally, the priority of the frequency domain resource type corresponding to the frequency domain resource can be determined based on the priority of the SSB carried by the frequency domain resource, or based on the connection priority of the frequency domain resource, or based on the priority of the PLMN corresponding to the frequency domain resource.

[0187] Optionally, the priority of frequency domain resource types can be described as: the priority of the SSB carried by the frequency domain resource, the access priority of the frequency domain resource, or the priority of the PLMN corresponding to the frequency domain resource.

[0188] Optionally, the priority of the PLMN can also be described as: the priority of the PLMN identifier.

[0189] In some examples, the priority of frequency domain resources is related to the type of frequency domain resource and the signal strength of the SSB received on the frequency domain resource.

[0190] Optionally, each frequency domain resource type corresponds to a priority coefficient, which can also be understood as the priority coefficient of the SSB received on that frequency domain resource. For example, the priority coefficient corresponding to a frequency domain resource type can be any of the following: 1, 0, 8, 0.7, or 0.5. As an example, the priority of a frequency domain resource is the product of the priority coefficient corresponding to the frequency domain resource type and the signal strength of the SSB received on the frequency domain resource.

[0191] S802, the second communication device sends the first SSB. Correspondingly, the first communication device receives the first SSB.

[0192] The first SSB may include at least one of the following: a synchronization signal and a broadcast channel.

[0193] When the first communication device receives the first SSB, it can obtain the priority of the first frequency domain resource from the first SSB, thereby executing S803.

[0194] S803, the first communication device determines whether to access the first frequency domain resource based on the priority of the first frequency domain resource.

[0195] Optionally, accessing a frequency domain resource means selecting a cell corresponding to that frequency domain resource, or in other words, camping on that frequency domain resource. Accessing a first frequency domain resource means selecting a cell corresponding to that first frequency domain resource, or camping on that first frequency domain resource.

[0196] Optionally, accessing a frequency domain resource can refer to performing downlink synchronization based on the SSB of that frequency domain resource and sending a random access request on that frequency domain resource, or sending a random access request on the access resource corresponding to the SSB of the frequency domain resource. For example, accessing a first frequency domain resource may include performing synchronization based on a first SSB and sending a random access request in the access resource corresponding to that first SSB.

[0197] The random access request may include at least one of the following: PRACH, preamble, message 1 (Msg1), or message A (Msg A), etc. The second communication device may determine the frequency domain resource to be accessed by the first communication device based on the priority of the transmitted frequency domain resource, and the frequency domain resource to be accessed by the first terminal device is the highest priority frequency domain resource among the frequency domain resources that the first terminal device can access.

[0198] Optionally, the second communication device receives random access requests on the access resources corresponding to the SSBs on high-priority frequency domain resources.

[0199] Optionally, the second communication device transmits a random access response message on high-priority frequency domain resources. Correspondingly, the first communication device receives the random access response message on high-priority frequency domain resources.

[0200] As an example, the second communication device can determine whether the first communication device should access the first frequency domain resource based on the priority of the transmitted frequency domain resource, which will not be elaborated further. If it is determined that the first communication device should access the first frequency domain resource, a random access request is received on the first frequency domain resource.

[0201] Optionally, the second communication device can also send a random access response message on the first frequency domain resources. Correspondingly, the first communication device can receive a random access response message on the first frequency domain resources.

[0202] In this embodiment of the application, the first communication device stores different priorities in advance. For example, the first communication device stores the size relationship between different priorities, such as priority 1 > priority 2 > priority 3.

[0203] The first communication device can determine whether the priority of the first frequency domain resource is a preset priority, such as the highest priority. If the priority of the first frequency domain resource is the preset priority, such as the highest priority, then the device accesses the first frequency domain resource. For example, if the operator-specific frequency domain resource corresponding to the first communication device is the highest priority frequency domain resource, and the first frequency domain resource is also an operator-specific frequency domain resource corresponding to the first communication device, then the device accesses the first frequency domain resource. In this way, accessing the operator-specific frequency domain resource reduces interference from other operators' terminal devices to the first communication device, thereby improving communication performance.

[0204] For example, if the frequency domain resources shared by the operators, including the operator corresponding to the first communication device, are the highest priority frequency domain resources, and the first frequency domain resource is a frequency domain resource shared by operators and the operator corresponding to the first frequency domain resource includes the operator corresponding to the first communication device, then access can be made on the first frequency domain resource. In this way, access can be made on the frequency domain resources shared by operators, so that multiple operators can share the same frequency domain resources for access, thereby improving the spectrum efficiency of the network and realizing network energy saving.

[0205] Based on the communication method provided in Figure 8, the first communication device can receive the first SSB and determine whether to access the first frequency domain resource according to the priority of the first frequency domain resource indicated by the indication information corresponding to the first SSB. That is, it can determine whether to access the frequency domain resource according to the priority of the frequency domain resource, thus improving the flexibility of access.

[0206] Furthermore, when prioritizing access to higher-priority frequency domain resources, higher-priority frequency domain resources can be accessed first, avoiding the large access delay caused by accessing lower-priority resources first and then higher-priority resources, thus improving communication efficiency.

[0207] In one possible implementation, the method shown in Figure 8 also includes S804.

[0208] S804, the second communication device sends a second SSB. Correspondingly, the first communication device receives the second SSB.

[0209] Optionally, the indication information corresponding to the second SSB carries information indicating the priority of the second frequency domain resource corresponding to the second SSB. The priority of the second frequency domain resource is higher than the priority of the first frequency domain resource. The priority of the second frequency domain resource is the priority of the first communication device accessing the second frequency domain resource.

[0210] In this way, the receiving SSB can be determined according to the priority of frequency domain resources, so that access can be made through the SSB on the high-priority frequency domain resources, and communication can be carried out quickly on the high-priority frequency domain resources, thus improving communication efficiency.

[0211] The information regarding the second SSB, its corresponding indication information, and the priority of the second frequency domain resource can be found in the relevant introductions to the first SSB, its corresponding indication information, and the priority of the first frequency domain resource, and will not be repeated here.

[0212] The second SSB is different from the first SSB.

[0213] Optionally, the first communication device receiving the second SSB includes: receiving the second SSB if it is determined, based on the priority of the first frequency domain resource, that the device will not access the first frequency domain resource.

[0214] In this way, if access cannot be made based on the first SSB, the second SSB on a higher-priority frequency domain resource can be received. This avoids accessing lower-priority frequency domain resources, reduces the access complexity of the first communication device, and improves access efficiency by receiving SSBs on higher-priority frequency domain resources.

[0215] In some examples, if the priority of the first frequency domain resource is not a preset priority, such as the highest priority, the first communication device may execute the following S804. For example, if the operator-dedicated frequency domain resource corresponding to the first communication device is the highest priority frequency domain resource, and the first frequency domain resource is an operator-shared frequency domain resource, then the following S804 is executed.

[0216] Optionally, when the method provided in FIG8 includes S804, the first frequency domain resource and the second frequency domain resource are frequency domain resources in the same set of frequency domain resources, or the first frequency domain resource and the second frequency domain resource are frequency domain resources in different sets of frequency domain resources.

[0217] Thus, the first frequency domain resources where the first SSB is located and the second frequency domain resources where the second SSB is located can be frequency domain resources from the same set of frequency domain resources. This allows for the presence of multiple frequency domain resource types within the same set, enabling the first communication device to access the corresponding frequency domain resources according to priority requirements. Conversely, the first frequency domain resources where the first SSB is located and the second frequency domain resources where the second SSB is located can be frequency domain resources from different sets of frequency domain resources. This allows for the presence of frequency domain resources of different types within different sets, enabling the first communication device to access the corresponding set of frequency domain resources according to priority requirements.

[0218] The set of frequency domain resources containing the first frequency domain resource and the set of frequency domain resources containing the second frequency domain resource can be configured by the second communication device. It is understood that the set of frequency domain resources configured by the second communication device can be one or more sets of frequency domain resources. One or more sets of frequency domain resources can also be agreed upon by a protocol.

[0219] Optionally, one or more frequency domain resource sets may include a frequency domain resource set that includes frequency domain resources dedicated to operator A and frequency domain resources dedicated to operator B; or, the frequency domain resource set may include frequency domain resources shared by multiple operators, including operator A and operator B. In this case, operator A or operator B is the operator corresponding to the first communication device, or in other words, the operator providing communication services to the first communication device.

[0220] Optionally, one or more frequency domain resource sets may include multiple frequency domain resource sets. In some examples, as shown in Figure 9(a), the multiple frequency domain resource sets include frequency domain resource set 0 to frequency domain resource set 1, wherein frequency domain resource set 0 includes frequency domain resources shared by operator A and operator B, and frequency domain resource set 1 includes frequency domain resources dedicated to operator A. In some examples, as shown in Figure 9(b), the multiple frequency domain resource sets include frequency domain resource set 0 to frequency domain resource set 1, wherein frequency domain resource set 0 includes frequency domain resources shared by operator A and operator B, and frequency domain resource set 1 includes frequency domain resources dedicated to operator B. In some examples, as shown in Figure 9(c), the multiple frequency domain resource sets include frequency domain resource set 0 to frequency domain resource set 1, wherein frequency domain resource set 0 includes frequency domain resources dedicated to operator A, and frequency domain resource set 1 includes frequency domain resources dedicated to operator B. In some examples, as shown in Figure 9(d), multiple frequency domain resource sets include frequency domain resource set 0 to frequency domain resource set 2, wherein frequency domain resource set 0 includes frequency domain resources dedicated to operator A, frequency domain resource set 1 includes frequency domain resources dedicated to operator B, and frequency domain resource set 2 includes frequency domain resources shared by operator A and operator B.

[0221] Using operators A and B as examples, assuming the first communication device corresponds to operator A, the first frequency domain resource is a frequency domain resource dedicated to operator A, and the second frequency domain resource is a frequency domain resource shared by operators A and B, then, if at least one frequency domain resource set in the frequency domain resource set configured for the second communication device includes a frequency domain resource shared by operators A and B, then the first and second frequency domain resources reside in the same frequency domain resource set. If at least two frequency domain resource sets in the frequency domain resource set configured for the second communication device include a frequency domain resource shared by operators A and B, then the first and second frequency domain resources can be frequency domain resources from different frequency domain resource sets. Alternatively, if the frequency domain resource set configured for the second communication device includes a frequency domain resource shared by operators A and B in the first frequency domain resource set and a frequency domain resource dedicated to operator A in the second frequency domain resource set, then the first and second frequency domain resources can be frequency domain resources from different frequency domain resource sets.

[0222] In one possible implementation, the operator corresponding to the first frequency domain resource is the first operator, and the operator corresponding to the second frequency domain resource includes both the first operator and the second operator; or, the first frequency domain resource includes both the first operator and the second operator, and the second frequency domain resource is the first operator; wherein, the first operator is the operator corresponding to the first communication device, and the second operator is different from the first operator.

[0223] In this way, different priorities can be defined for access requirements of operator-dedicated frequency domain resources and operator-shared frequency domain resources, enabling priority-based access and improving access efficiency.

[0224] Optionally, when the method provided in Figure 8 includes S804, the indication information corresponding to the first SSB further includes second information, which is used to indicate the frequency domain location of the second SSB. Thus, by indicating the frequency domain location of the second SSB through the previously received indication information corresponding to the first SSB, searching for SSBs on other frequency domain resources can be avoided, reducing access latency.

[0225] The indication information corresponding to the SSB can be the system information corresponding to the SSB, such as MIB or SIB (e.g., SIB1).

[0226] In some examples, the frequency domain location of a shared SSB can be indicated in a dedicated SSB.

[0227] For example, if the first SSB is a dedicated SSB for the operator, and the second SSB is a shared SSB for the operator, then the frequency domain location of the shared SSB is indicated by the dedicated SSB. It can be understood that the frequency domain resources corresponding to the shared SSB have a higher priority than those corresponding to the dedicated SSB.

[0228] The following example illustrates the positional relationship between the first SSB and the second SSB indicated by the second information.

[0229] Example 1: The first SSB and the second SSB are in the same frequency domain resource set.

[0230] For example, in a scenario where the SSBs in the frequency domain resource set include operator-dedicated SSBs and operator-shared SSBs, the frequency domain location of the operator-shared SSB is indicated in the system information corresponding to the operator-dedicated SSB. Thus, when the first communication device searches for an operator-dedicated SSB, and the operator-shared SSB or operator-shared frequency domain resource of the first communication device has a higher priority, the first communication device can determine the frequency domain resource location of the operator-shared SSB based on the frequency domain location of the operator-shared SSB, such as the second information mentioned above. This avoids searching for SSBs on operator-shared frequency domain resources, reduces access latency, and enables fast SSB reception.

[0231] Optionally, the frequency domain location of the operator-shared SSB indicated by the second information may be an absolute frequency domain resource location.

[0232] For example, the frequency domain location of a shared SSB can be indicated by at least one of the following: frequency domain range indication (e.g., FR1, FR2, etc.), frequency band (e.g., frequency band identifier), carrier component (e.g., carrier component identifier), or ARFCN. In some examples, ARFCN can be indicated by the NR global frequency raster.

[0233] Optionally, when indicating the frequency domain location of a shared SSB, the operator information corresponding to that SSB can be indicated, such as the PLMN information corresponding to that SSB, or public PLMN information (also known as virtual PLMN information). PLMN information is used to indicate the PLMN identifier. Public PLMN information is used to indicate the public PLMN (PLMNC) identifier. In this case, the public PLMN identifier corresponds to multiple operators. The PLMN identifier is used to represent the PLMN; indicating the PLMN identifier can also be understood as indicating the PLMN.

[0234] Optionally, the PLMN identifier can also be described as: PLMN information, or PLMN identifier information, etc.

[0235] Optionally, the frequency domain location of the operator-shared SSB indicated by the second information can be a relative frequency domain resource location.

[0236] For example, the frequency domain location of a shared SSB can be an offset between the frequency domain resources of the shared SSB and the frequency domain location of the dedicated SSB. The second information can indicate the offset between the frequency domain resources of the shared SSB and the frequency domain location of the dedicated SSB, and may include at least one of the following: the offset bandwidth, the offset number of RBGs, or the offset number of RBs, etc.

[0237] Optionally, the offset between the frequency domain position of the operator-shared SSB and the frequency domain position of the operator-dedicated SSB can be the offset of the center position of the operator-shared SSB relative to the operator-dedicated SSB or the currently found SSB, or the offset of the minimum frequency domain subcarrier position relative to the operator-dedicated SSB or the currently found SSB, or the offset of the maximum frequency domain subcarrier position relative to the operator-dedicated SSB or the currently found SSB, etc.

[0238] For example, as shown in Figure 10 below, if the frequency domain resource set includes an SSB dedicated to operator A, an SSB dedicated to operator B, and an SSB shared by operators A and B, and the first SSB is an SSB dedicated to operator A, the system information corresponding to the SSB dedicated to operator A can indicate offset 0, where offset 0 is the offset between the frequency domain position of the SSB dedicated to operator A and the frequency domain position of the SSB shared by operators A and B.

[0239] For example, the second piece of information includes offset0 and PLMNC. Among them, PLMNC is a PLMN identifier shared by operator A and operator B.

[0240] If the first SSB is a dedicated SSB for operator B, the system information corresponding to the dedicated SSB for operator B can indicate offset 1, where offset 1 is the offset between the frequency domain position of the dedicated SSB for operator B and the frequency domain position of the SSB shared by operator A and operator B.

[0241] For example, the second piece of information includes indications of offset1 and PLMNC. Among them, PLMNC is a PLMN identifier shared by operator A and operator B.

[0242] Example 2: The first SSB and the second SSB are in different frequency domain resource sets.

[0243] The following explanation combines the SSBs in frequency domain resource set 0, which include SSBs shared by operators; the SSBs in frequency domain resource set 1, which include SSBs dedicated to operator A; and the SSBs in frequency domain resource set 2, which include SSBs dedicated to operator B.

[0244] In scenarios where the system information corresponding to a carrier-dedicated SSB includes the frequency domain location of a carrier-shared SSB, when the first communication device searches for a carrier-dedicated SSB, and the priority of the carrier-shared SSB or carrier-shared frequency domain resource corresponding to the first communication device is high, the first communication device can determine the frequency domain location of the carrier-shared SSB based on the frequency domain location of the carrier-dedicated SSB. This avoids searching for SSBs on carrier-shared frequency domain resources, reduces access latency, and enables fast SSB reception.

[0245] Optionally, the frequency domain location of the operator-shared SSB indicated by the second information can be an absolute frequency domain resource location.

[0246] For example, the frequency domain location of an operator-shared SSB can be indicated by at least one of the following information: frequency domain resource set (e.g., frequency domain resource set identifier), frequency domain range (e.g., FR1, FR2, etc.), frequency band (e.g., band identifier), carrier component (e.g., carrier component identifier), or ARFCN.

[0247] Optionally, when indicating the frequency domain location of an SSB shared by operators, the operator information corresponding to the SSB can be indicated, such as the PLMN information corresponding to the SSB, or the public PLMN information (also known as virtual PLMN information).

[0248] Optionally, the frequency domain location of the operator-shared SSB indicated by the second information can be a relative frequency domain resource location.

[0249] For example, the frequency domain location of a shared SSB can be an offset relative to the frequency domain location of a dedicated SSB.

[0250] For example, the frequency domain location of a shared SSB can be the offset between the frequency domain resources of the shared SSB and the frequency domain location of the dedicated SSB. The second information can indicate the offset between the frequency domain resources of the shared SSB and the frequency domain location of the dedicated SSB, and may include at least one of the following: the offset bandwidth, the number of offset RBGs, the number of offset RBs, etc.

[0251] Optionally, the operator-shared SSB can be the offset of the center position of the operator-shared SSB relative to the operator-dedicated SSB or the currently found SSB, or the offset of the minimum frequency domain subcarrier position relative to the operator-dedicated SSB or the currently found SSB, or the offset of the maximum frequency domain subcarrier position relative to the operator-dedicated SSB or the currently found SSB, etc.

[0252] For example, as shown in Figure 11 below, if frequency domain resource set 0 includes an SSB shared by operators A and B, frequency domain resource set 1 includes an SSB dedicated to operator A, and frequency domain resource set 2 includes an SSB dedicated to operator B, and if the first SSB is an SSB dedicated to operator A, the system information corresponding to the SSB dedicated to operator A can indicate offset 0, where offset 0 is the offset between the frequency domain position of the SSB dedicated to operator A and the frequency domain position of the SSB shared by operators A and B.

[0253] For example, the second piece of information includes offset0 and PLMNC. Among them, PLMNC is a PLMN identifier shared by operator A and operator B.

[0254] If the first SSB is a dedicated SSB for operator B, the system information corresponding to the dedicated SSB for operator B can indicate offset 1, where offset 1 is the offset between the frequency domain position of the dedicated SSB for operator B and the frequency domain position of the SSB shared by operator A and operator B.

[0255] For example, the second piece of information includes offset1 and PLMNC. Among them, PLMNC is a PLMN identifier shared by operator A and operator B.

[0256] In some examples, the frequency domain location of a shared SSB can be indicated within a dedicated SSB. For instance, if the first SSB is a carrier-shared SSB and the second SSB is a carrier-dedicated SSB, the frequency domain location of the carrier-dedicated SSB is indicated through the carrier-shared SSB. It is understood that in this case, the frequency domain resources corresponding to the carrier-dedicated SSB have a higher priority than those corresponding to the carrier-shared SSB.

[0257] Example 3: The first SSB and the second SSB are in the same frequency domain resource set. For instance, in a scenario where the SSBs in the frequency domain resource set include operator-dedicated SSBs and operator-shared SSBs, the frequency domain location of the operator-dedicated SSB is indicated in the system information corresponding to the operator-shared SSB. Thus, when the first communication device searches for an operator-shared SSB, and the operator-dedicated SSB or operator-dedicated frequency domain resource of the first communication device has a higher priority, the first communication device can determine the frequency domain location of the operator-dedicated SSB based on its frequency domain location, avoiding searching for SSBs on operator-dedicated frequency domain resources, reducing access latency, and achieving fast SSB reception.

[0258] Optionally, the frequency domain location of the operator-specific SSB indicated by the second information can be an absolute frequency domain resource location.

[0259] For example, the frequency domain location of a carrier-specific SSB can be indicated by at least one of the following: frequency domain range indication (e.g., FR1, FR2, etc.), frequency band (e.g., frequency band identifier), carrier component (e.g., carrier component identifier), or ARFCN. In some examples, the ARFCN can be indicated by the NR global frequency grid.

[0260] Optionally, when indicating the frequency domain location of a carrier-specific SSB, the carrier information corresponding to that SSB, such as PLMN information, can be indicated.

[0261] Optionally, the frequency domain location of the operator-specific SSB indicated by the second information can be a relative frequency domain resource location.

[0262] For example, the frequency domain location of a carrier-dedicated SSB can be an offset between the frequency domain resources of the carrier-dedicated SSB and the frequency domain location of the carrier-shared SSB.

[0263] The second information may indicate the offset between the frequency domain location of the operator-dedicated SSB and the frequency domain location of the operator-shared SSB, and may include at least one of the following: the offset bandwidth, the offset number of RBGs, or the offset number of RBs, etc.

[0264] Optionally, the offset between the frequency domain position of the operator-dedicated SSB and the frequency domain position of the operator-shared SSB can be the offset between the frequency domain position of the operator-dedicated SSB and the center position of the frequency domain resources of the operator-shared SSB, the offset between the frequency domain position of the operator-dedicated SSB and the minimum frequency domain subcarrier position of the frequency domain resources of the operator-shared SSB, or the offset between the frequency domain position of the operator-dedicated SSB and the maximum frequency domain subcarrier position of the frequency domain resources of the operator-shared SSB, etc.

[0265] For example, as shown in Figure 12 below, if the frequency domain resource set includes an SSB dedicated to operator A, an SSB dedicated to operator B, and an SSB shared by operators A and B, and if the first SSB is an SSB shared by operators A and B, and the second SSB is an SSB dedicated to operator A, the system information corresponding to the operator-shared SSB can indicate offset 3, where offset 3 is the offset between the frequency domain position of the SSB shared by operators A and B and the frequency domain position of the SSB dedicated to operator A.

[0266] For example, the second piece of information includes offset3 and PLMNA. Among them, PLMNA is the PLMN identifier corresponding to operator A.

[0267] If the first SSB is a shared SSB between operator A and operator B, and the second SSB is a dedicated SSB for operator B, the system information corresponding to the operator-shared SSB can indicate offset 4, where offset 4 is the offset between the frequency domain position of the SSB shared by operator A and operator B and the frequency domain position of the dedicated SSB for operator B.

[0268] For example, the second piece of information includes offset4 and PLMNB. Among them, PLMNB is the PLMN identifier corresponding to operator B.

[0269] Example 4: The first SSB and the second SSB are in different frequency domain resource sets.

[0270] The following explanation combines the SSBs in frequency domain resource set 0, which include SSBs shared by operators; the SSBs in frequency domain resource set 1, which include SSBs dedicated to operator A; and the SSBs in frequency domain resource set 2, which include SSBs dedicated to operator B.

[0271] In scenarios where the system information corresponding to the operator-shared SSB includes the frequency domain resource location of the operator-dedicated SSB, when the first communication device searches for the operator-shared SSB, and the operator-dedicated SSB or operator-dedicated frequency domain resource corresponding to the first communication device has a higher priority, the first communication device can determine the frequency domain location of the operator-dedicated SSB based on the frequency domain location of the operator-dedicated SSB, avoiding searching for the SSB on the operator-dedicated frequency domain resource, reducing access latency, and achieving fast SSB reception.

[0272] Optionally, the frequency domain location of the operator-specific SSB indicated by the second information can be an absolute frequency domain resource location.

[0273] For example, the frequency domain location of a carrier-specific SSB can be indicated by at least one of the following information: frequency domain resource set (e.g., frequency domain resource set identifier), frequency domain range (e.g., FR1, FR2, etc.), frequency band (e.g., band identifier), carrier component (e.g., carrier component identifier), or ARFCN.

[0274] Optionally, when indicating the frequency domain location of a carrier-specific SSB, the carrier information corresponding to the SSB can be indicated, such as the PLMN information corresponding to the SSB.

[0275] Optionally, the second piece of information refers to the frequency domain location of the operator-specific SSB, which can be a relative frequency domain resource location.

[0276] For example, the frequency domain location of a carrier-dedicated SSB can be an offset relative to the frequency domain location of a carrier-shared SSB.

[0277] For example, the second information may indicate that the frequency domain location of the operator-dedicated SSB may be offset relative to the frequency domain location of the operator-shared SSB, and may include at least one of the following: the offset bandwidth, the offset number of RBGs, or the offset number of RBs, etc.

[0278] Optionally, the frequency domain position of the operator-dedicated SSB can be an offset relative to the frequency domain position of the operator-shared SSB. This offset can be the offset of the center position of the operator-dedicated SSB relative to the frequency domain position of the operator-shared SSB, the offset of the minimum frequency domain subcarrier position of the operator-dedicated SSB relative to the frequency domain position of the operator-shared SSB, or the offset of the maximum frequency domain subcarrier position of the operator-dedicated SSB relative to the frequency domain position of the operator-shared SSB, etc.

[0279] For example, as shown in Figure 13 below, frequency domain resource set 0 includes SSBs shared by operators A and B, frequency domain resource set 1 includes SSBs dedicated to operator A, and frequency domain resource set 2 includes SSBs dedicated to operator B.

[0280] If the first SSB is a shared SSB between operator A and operator B, and the second SSB is a dedicated SSB for operator A, the system information corresponding to the shared SSB between operator A and operator B can indicate offset 3, where offset 3 is the offset between the frequency domain position of the shared SSB between operator A and operator B and the frequency domain position of the dedicated SSB for operator A.

[0281] For example, the second piece of information includes offset3 and PLMNA. Among them, PLMNA is the PLMN identifier corresponding to operator A.

[0282] If the first SSB is a shared SSB between operator A and operator B, and the second SSB is a dedicated SSB for operator B, the system information corresponding to the shared SSB between operator A and operator B can indicate offset 4, where offset 4 is the offset between the frequency domain position of the shared SSB between operator A and operator B and the frequency domain position of the dedicated SSB for operator B.

[0283] For example, the second piece of information includes offset4 and PLMNB. Among them, PLMNB is the PLMN identifier corresponding to operator B.

[0284] Optionally, if the method provided in FIG8 includes S804, the method provided in FIG8 may also include S805.

[0285] S805, the first communication device determines whether to access the second frequency domain resource based on the priority of the second frequency domain resource.

[0286] For details on the implementation of S805, please refer to the relevant introduction of S803, which will not be elaborated here.

[0287] Optionally, before S804, the method provided in Figure 8 may also include S806.

[0288] S806, the second communication device generates the second SSB.

[0289] In the method shown in Figure 8, S804 can also be understood as a repeated execution of S802, and S805 can be understood as a repeated execution of S803. The difference is that the second SSB in S804 and S805 is equivalent to the first SSB in S802 and S803, and the second frequency domain resource in S804 and S805 is equivalent to the first frequency domain resource in S802 and S803. In this embodiment, the steps S801 to S803 can be repeated until the priority of the frequency domain resource corresponding to the SSB is detected to be a preset priority. Each time S801 to S803 is repeated, the SSB used is different from the SSB used in the previously executed steps.

[0290] As mentioned earlier, "frequency domain resource types can be classified according to different rules." The following examples illustrate frequency domain resource types using different classification rules.

[0291] Optionally, the frequency domain resource type is related to the operator corresponding to the frequency domain resource and / or whether it is an anchor frequency domain resource. The following examples illustrate this.

[0292] In one possible implementation, operator-shared frequency domain resources refer to frequency domain resources corresponding to at least two operators, i.e., frequency domain resources that can be shared by at least two operators. For example, if a frequency domain resource corresponds to operator A and operator B, then that frequency domain resource is an operator-shared frequency domain resource. Similarly, if a frequency domain resource corresponds to operator A, operator B, and operator C, then that frequency domain resource is an operator-shared frequency domain resource. It can be understood that if a frequency domain resource is an operator-shared frequency domain resource, then at least two operators corresponding to that frequency domain resource can provide communication services to terminal devices on that frequency domain resource, and that frequency domain resource can also be referred to as an operator-shared frequency domain resource corresponding to that frequency domain resource.

[0293] In one possible implementation, the anchor frequency domain resource is a frequency domain resource that carries information for access control, such as a frequency domain resource carrying at least one of the following: information for camping, paging messages, low-power wake-up signals, or uplink wake-up signals. The anchor frequency domain resource can also be understood as a frequency domain resource used for access control, or as a frequency domain resource used to meet the coverage performance requirements of the terminal device.

[0294] Optionally, the anchor frequency domain resource may include frequency domain resources used to carry uplink signals (i.e., uplink frequency domain resources) and / or frequency domain resources used to carry downlink signals (i.e., downlink frequency domain resources). Here, an anchor frequency domain resource that is an uplink frequency domain resource can also be called an uplink anchor frequency domain resource, and an anchor frequency domain resource that is a downlink frequency domain resource can also be called a downlink anchor frequency domain resource. As an example, when the anchor frequency domain resource is a frequency division multiplexing (FDM) frequency domain resource, i.e., when uplink and downlink use a frequency division method, the anchor frequency domain resource may include uplink anchor frequency domain resources and / or downlink anchor frequency domain resources. It is understood that in time division multiplexing (TDM), i.e., when uplink and downlink use a time division method, the anchor frequency domain resource may also include uplink anchor frequency domain resources. The functionality of both uplink and downlink anchor frequency domain resources can be implemented through resources at different frequency positions on the anchor frequency domain resource.

[0295] In contrast to frequency domain resources corresponding to at least two operators, frequency domain resources corresponding to one operator are operator-dedicated frequency domain resources, meaning they are dedicated to a single operator. If a frequency domain resource is operator-dedicated, then only the operator corresponding to that resource can provide communication services to terminal devices on that resource. In this case, the frequency domain resource can also be referred to as operator-dedicated. It can be understood that the distinction between operator-dedicated frequency domain resources and operator-shared frequency domain resources is relative to whether the number of operators corresponding to the resource is one or at least two.

[0296] In contrast to the frequency domain resources used to carry access control information, the frequency domain resources used to carry service data are called capacity frequency domain resources.

[0297] Optionally, the capacity frequency domain resource may include frequency domain resources used to carry uplink signals (i.e., uplink frequency domain resources) and / or frequency domain resources used to carry downlink signals (i.e., downlink frequency domain resources). The capacity frequency domain resource of the uplink frequency domain resource can also be referred to as the uplink capacity frequency domain resource, and the capacity frequency domain resource of the downlink frequency domain resource can also be referred to as the downlink capacity frequency domain resource. As an example, when the capacity frequency domain resource is an FDM frequency domain resource, the capacity frequency domain resource may include frequency domain resources used for uplink transmission and / or frequency domain resources used for downlink transmission. It is understood that in TDM, the frequency domain resources used for uplink transmission and the frequency domain resources used for downlink transmission on the capacity frequency domain resource may be resources at different time domain locations on the same frequency domain resource.

[0298] In some scenarios, anchor frequency domain resources can also be called coverage frequency domain resources. In other scenarios, anchor frequency domain resources can also be called anchor carriers (CC) or coverage carriers (CC), and capacity frequency domain resources can also be called capacity carriers (CC).

[0299] In one possible implementation, the frequency domain resource type includes at least one of the following: operator-shared frequency domain resources, operator-dedicated frequency domain resources, anchor frequency domain resources, capacity frequency domain resources, operator-shared frequency domain resources that are also anchor frequency domain resources, operator-shared frequency domain resources that are also capacity frequency domain resources, operator-dedicated frequency domain resources that are also anchor frequency domain resources, and operator-dedicated frequency domain resources that are also capacity frequency domain resources.

[0300] In one possible implementation, frequency domain resource types can be divided according to rule 1.

[0301] Optionally, Rule 1 satisfies the following: the frequency domain resource type is related to whether it is a shared frequency domain resource of the operator; in other words, the frequency domain resource type is related to whether it is a dedicated frequency domain resource of the operator. In this embodiment, the frequency domain resource type is related to whether it is a shared frequency domain resource of the operator, or the frequency domain resource type is related to whether it is a dedicated frequency domain resource of the operator; this can also be understood as the frequency domain resource type being related to the operator corresponding to the operator. For a frequency domain resource, it is either a shared frequency domain resource of the operator or a dedicated frequency domain resource of the operator. In other words, if a frequency domain resource is not a shared frequency domain resource of the operator, then it is a dedicated frequency domain resource of the operator.

[0302] Optionally, frequency domain resource types can be categorized based on whether they are operator-shared or operator-dedicated. Alternatively, they can be categorized based on whether the frequency domain resource corresponds to one or at least two operators. In this case, frequency domain resource types include operator-shared frequency domain resources and operator-dedicated frequency domain resources. Taking operators A, B, and C as an example, the correspondence between frequency domain resource types and operators is shown in Table 6 below.

[0303] Table 6

[0304] Rule 1 can also be understood as classifying frequency domain resource types according to the PLMN identifier corresponding to the frequency domain resource. The PLMN identifier corresponding to the frequency domain resource can refer to an actual PLMN identifier or a virtual PLMN identifier, such as at least one PLMN identifier from Table 4. An actual PLMN identifier can be used to identify an operator, i.e., it corresponds to one PLMN identifier. A virtual PLMN identifier can be used to identify a set of operators including at least one operator, i.e., it corresponds to an operator in the operator set. A PLMN identifier corresponds to one or more operators. Taking operators A and B as examples, assume the relationship between PLMN identifiers and operators is as shown in Table 7 below.

[0305] Table 7

[0306] Therefore, based on Table 7 above, the correspondence between frequency domain resource types and PLMN identifiers is shown in Table 8.

[0307] Table 8

[0308] In one possible implementation, frequency domain resource types can be divided according to rule 2.

[0309] Optionally, Rule 2 satisfies the following: frequency domain resource types are classified according to the operators corresponding to the frequency domain resources. This can also be understood as classifying frequency domain resource types based on whether the operators corresponding to the frequency domain resources are the same. In this case, frequency domain resources belonging to the same operator have the same frequency domain resource type, and frequency domain resources belonging to different operators have different frequency domain resource types. In some examples, for operator-shared frequency domain resources, at least one of the corresponding operators is different, and the frequency domain resource types of shared frequency domain resources belong to different operators. In some examples, operator-specific frequency domain resources belonging to the same operator have the same frequency domain resource type, and operator-specific frequency domain resources belonging to different operators have different frequency domain resource types. Taking operators A, B, and C as an example, the frequency domain resource types can include frequency domain resource type 0 to frequency domain resource type 6. The correspondence between each frequency domain resource type and the corresponding operator is shown in Table 9 below.

[0310] Table 9

[0311] Based on Table 9 above, frequency domain resource types 0 to 2 are frequency domain resources dedicated to operators, while frequency domain resource types 3 to 6 are frequency domain resources shared by operators. Specifically, frequency domain resource type 0 is dedicated to operator A, frequency domain resource type 1 is dedicated to operator B, frequency domain resource type 3 is dedicated to operator C, frequency domain resource type 4 is shared by operators A and B, frequency domain resource type 5 is shared by operators A and C, frequency domain resource type 6 is shared by operators A, B, and C.

[0312] It is understood that the frequency domain resource types listed in Table 9 above are for illustrative purposes only. In actual implementation, operators may use fewer or more. For example, there may be two operators, such as operator A and operator B. In this case, the frequency domain resource types may include frequency domain resource type 2, frequency domain resource type 3, and frequency domain resource type 5 as shown in Table 9 above. When there are three or more operators, the implementation of the frequency domain resource types is similar to that when there are three operators, and will not be elaborated further.

[0313] In one possible implementation, frequency domain resource types can be divided according to rule 3.

[0314] Optionally, rule 3 satisfies the following: the type of frequency domain resource is related to whether it is an anchor frequency domain resource, which can also be understood as the type of frequency domain resource being related to whether it is a capacity frequency domain resource. For a frequency domain resource, it is either an anchor frequency domain resource or a capacity frequency domain resource. In other words, if a frequency domain resource is not an anchor frequency domain resource, it is a capacity frequency domain resource.

[0315] Optionally, frequency domain resource types can be categorized based on whether they are anchor frequency domain resources, or in other words, based on whether they are capacity frequency domain resources. In this case, frequency domain resource types include anchor frequency domain resources and capacity frequency domain resources. Furthermore, frequency domain resource types can include two types, such as frequency domain resource types 7 to 8. The relationship between each frequency domain resource type and whether it is an anchor frequency domain resource is shown in Table 10 below.

[0316] Table 10

[0317] Optionally, frequency domain resource types are categorized based on whether they are anchor frequency domain resources and whether they are uplink frequency domain resources. Whether a resource is an anchor frequency domain resource can also be described as whether it is a capacity frequency domain resource, and whether it is an uplink frequency domain resource can also be described as whether it is a downlink frequency domain resource. In this case, frequency domain resource types can include four types, such as frequency domain resource type 9 to frequency domain resource type 12. The relationship between each frequency domain resource type and whether it is an anchor frequency domain resource and whether it is an uplink frequency domain resource is shown in Table 11 below.

[0318] Table 11

[0319] Based on Table 11 above, frequency domain resource type 9 is uplink anchor frequency domain resource, frequency domain resource type 10 is downlink anchor frequency domain resource, frequency domain resource type 11 is uplink capacity frequency domain resource, and frequency domain resource 1 is downlink capacity frequency domain resource.

[0320] In one possible implementation, the frequency domain resource type is related to whether it is a shared frequency domain resource for operators and whether it is an anchor frequency domain resource.

[0321] In one possible implementation, frequency domain resource types can be divided according to rule 4.

[0322] Optionally, Rule 4 refers to the relationship between frequency domain resource type and whether it is a shared frequency domain resource of the operator and whether it is an anchor frequency domain resource. In this case, the frequency domain resource type can include four types, such as frequency domain resource type 13 to frequency domain resource type 16. The relationship between each frequency domain resource type and whether it is a shared frequency domain resource of the operator and whether it is an anchor frequency domain resource is shown in Table 12 below.

[0323] Table 12

[0324] In one possible implementation, frequency domain resource types can be divided according to rule 5.

[0325] Optionally, Rule 5 means that frequency domain resource types can be classified by combining any one of Rules 1 and 2, as well as any one of Rules 3 and 4. In this case, the methods for classifying frequency domain resource types include Rules 5.0 to Rule 5.3, where the classification criteria corresponding to each of Rules 5.0 to Rule 5.3 are shown in Table 13 below.

[0326] Table 13

[0327] Specifically, under the classification according to Rule 5.0, the correspondence between frequency domain resource types and whether they are operator-shared frequency domain resources and anchor frequency domain resources is shown in Table 13. Under the classification according to Rule 5.1, the correspondence between frequency domain resource types and whether they are operator-shared frequency domain resources, anchor frequency domain resources, and uplink frequency domain resources is shown in Table 14.

[0328] Table 14

[0329] The following examples, including Operator A and Operator B, illustrate the correspondence between frequency domain resource types and whether they are corresponding operators and whether they are anchor frequency domain resources when classifying frequency domain resource types according to Rule 5.2. Table 15 is shown below.

[0330] Table 15

[0331] It is understandable that, when there are three or more operators and the frequency domain resource type is divided according to rule 5.2, the correspondence between the frequency domain resource type and whether it is the corresponding operator and whether it is the anchor frequency domain resource is similar to that in Table 15, and will not be repeated here.

[0332] The following examples, including Operator A and Operator B, illustrate the correspondence between frequency domain resource types and whether they are corresponding operators, whether they are anchor frequency domain resources, and whether they are uplink frequency domain resources when classifying frequency domain resource types according to Rule 5.3. Table 16 is shown below.

[0333] Table 16

[0334] It is understandable that when there are 3 or more operators and the frequency domain resource type is divided according to rule 5.3, the correspondence between the frequency domain resource type and whether it is the corresponding operator and whether it is the anchor frequency domain resource is similar to that in Table 16, and will not be repeated here.

[0335] In one possible implementation, frequency domain resource types can be divided according to rule 6.

[0336] Rule 6 refers to classifying frequency domain resources according to the frequency band in which they reside. In some examples, each frequency domain resource can be classified into one frequency domain resource type.

[0337] Furthermore, the frequency domain resource types involved in the embodiments of this application are for illustrative purposes only. In actual implementation, frequency domain resource types can also be obtained through other division methods, such as division according to the frequency range of frequency domain resources, which will not be elaborated here.

[0338] In one possible implementation, the method shown in Figure 8 may also include S807.

[0339] S807, the second communication device sends the third information. Correspondingly, the first communication device receives the third information.

[0340] The third piece of information is used to indicate one or more frequency domain resource sets.

[0341] Optionally, the third information can be carried in a broadcast message, such as in the SI. In one example, the second information is carried in SIB1. It is understood that carrying the third information in SIB1 is for illustrative purposes. In actual implementation, the second information can also be carried in other system information blocks within the system information, or the third information can also be carried in other possible messages outside of the system information, which will not be elaborated further.

[0342] Optionally, the third information may carry a dedicated message for the first communication device.

[0343] Optionally, the third information can be carried in higher-level signaling, such as RRC signaling or MAC CE signaling.

[0344] Optionally, step S806 may be performed after or before S802 and / or S804, and this application does not limit this to any particular step.

[0345] Optionally, step S806 may be performed after or before S803 and / or S805, and this application does not limit this to any particular step.

[0346] In other embodiments, the first communication device may first obtain the priorities of different frequency domain resources, and then determine which frequency domain resource to access based on the priorities of the different frequency domain resources. In this case, the communication method is shown in Figure 14 below.

[0347] S1401, the first communication device determines the priority of the third frequency domain resource and the priority of the fourth frequency domain resource.

[0348] Among them, the priority of the third frequency domain resource is the priority of the first communication device accessing the third frequency domain resource, and the priority of the fourth frequency domain resource is the priority of the first communication device accessing the fourth frequency domain resource.

[0349] In one possible implementation, the priority of frequency domain resources is related to the frequency domain resource type.

[0350] In this way, the priority of frequency domain resources can be determined according to the type of frequency domain resources, and priority can be given to accessing frequency domain resources corresponding to specific types of frequency domain resources, which can improve access efficiency.

[0351] The implementation of the third frequency domain resource and its priority can be referred to the relevant introduction of the first frequency domain resource and its priority in the method provided in Figure 8 above. The implementation of the fourth frequency domain resource and its priority can be referred to the relevant introduction of the second frequency domain resource and its priority in the method provided in Figure 8 above, and will not be elaborated further.

[0352] In one possible implementation, the third frequency domain resource and the fourth frequency domain resource are frequency domain resources in the same set of frequency domain resources, or the third frequency domain resource and the fourth frequency domain resource are frequency domain resources in different sets of frequency domain resources.

[0353] The relationship between the frequency domain resources of the third and fourth frequency domains can be referenced from the relationship between the frequency domain resources of the first and second frequency domains, and will not be elaborated further.

[0354] In one possible implementation, the operator corresponding to the third frequency domain resource is the first operator, and the operators corresponding to the third frequency domain resource include the first operator and the second operator; or, the third frequency domain resource includes the first operator and the second operator, and the third frequency domain resource is the first operator; wherein, the first operator is the operator corresponding to the first terminal device, and the second operator is different from the first operator.

[0355] In this embodiment of the application, the priority of the third frequency domain resource and the priority of the fourth frequency domain resource can be configured by the second communication device or agreed upon by the protocol.

[0356] S1402, the first communication device determines whether to access the third frequency domain resource or the fourth frequency domain resource based on the priority of the third frequency domain resource and the priority of the fourth frequency domain resource.

[0357] The first communication device can determine the frequency domain resource to access based on the priority of the third frequency domain resource and the priority of the fourth frequency domain resource, where the priority is higher. For example, if the priority of the third frequency domain resource is higher than that of the fourth frequency domain resource, the first communication device accesses the third frequency domain resource. If the priority of the fourth frequency domain resource is higher than that of the third frequency domain resource, the first communication device accesses the fourth frequency domain resource.

[0358] For information on how the first communication device can access the third or fourth frequency domain resources, please refer to the relevant introduction in Figure 8 regarding the first communication device accessing the first frequency domain resources.

[0359] Optionally, the operation of accessing frequency domain resources may include at least one of the following: receiving SSB on high-priority frequency domain resources, receiving system information on high-priority frequency domain resources, or sending a random access request to the access resource corresponding to the SSB on high-priority frequency domain resources.

[0360] The random access request may include at least one of the following: PRACH, preamble, message 1 (Msg1), or message A (Msg A), etc.

[0361] Optionally, the method provided in FIG14 may further include: the second communication device transmitting SSB on high-priority frequency domain resources.

[0362] Optionally, the method provided in FIG14 may further include: the first communication device sending a random access request on the frequency domain resources to be accessed.

[0363] In some examples, the second communication device receives random access requests on the access resources corresponding to the SSBs on high-priority frequency domain resources.

[0364] In some examples, the method provided in Figure 14 may further include: the second communication device determining the priority of the frequency domain resource to which the random access request is received. For example, the second communication device may determine the priority of the frequency domain resource to which the random access request is received as the highest priority frequency domain resource among those accessible by the first communication device.

[0365] Thus, the frequency domain resources used by the first communication device for access are obtained.

[0366] In this embodiment of the application, the method provided in FIG14 may further include: the second communication device communicating with the first communication device on the frequency domain resources on which the random access request is received.

[0367] Thus, when the first communication device sends a random access request on the highest priority frequency domain resource, communication is carried out on the highest priority frequency domain resource, thereby improving communication efficiency.

[0368] Optionally, the second communication device transmits a random access response message on high-priority frequency domain resources. Correspondingly, the first communication device receives the random access response message on high-priority frequency domain resources.

[0369] It is understood that the first communication device can also determine the priorities of other frequency domain resources besides the priorities of the third and fourth frequency domain resources. The implementation of the priorities of other frequency domain resources can refer to the implementation of the priorities of the first or second frequency domain resources. In this case, in S1402, the first communication device can determine the frequency domain resource to be accessed from the priorities of all frequency domain resources determined by the first communication device. The accessed frequency domain resource can be a frequency domain resource whose priority meets a preset condition among all frequency domain resources for which the first communication device has determined priorities, such as the frequency domain resource with the highest priority.

[0370] In one possible implementation, where the priority of the third frequency domain resources and the priority of the fourth frequency domain resources are configured by the second communication device, the method provided in FIG14 may further include S1403.

[0371] S1403, the second communication device sends the fourth information. Correspondingly, the first communication device receives the fourth information.

[0372] The fourth piece of information is used to determine the priority of the third frequency domain resource and the priority of the fourth frequency domain resource.

[0373] In cases where the first communication device can also determine the priorities of other frequency domain resources besides the priorities of the third and fourth frequency domain resources, the fourth information is also used to indicate the priorities of other frequency domain resources besides the priorities of the third and fourth frequency domain resources.

[0374] The communication method provided by the embodiments of this application has been described in detail above with reference to Figures 8-14. The communication apparatus used to perform the communication method provided by the embodiments of this application is described in detail below with reference to Figures 15 and 16.

[0375] For example, FIG15 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in FIG15, the communication device 1500 includes a processing module 1501 and a transceiver module 1502. For ease of explanation, FIG15 only shows the main components of the communication device.

[0376] In some embodiments, the communication device 1500 may be adapted to the communication system shown in FIG1 to perform the functions of the first communication device in the communication method shown in FIG8.

[0377] The transceiver module 1502 is used to receive a first synchronization signal and a physical broadcast channel block (SSB). The indication information corresponding to the first SSB carries information for determining the priority of the first frequency domain resource corresponding to the first SSB. The priority of the first frequency domain resource is the priority of the first communication device accessing the first frequency domain resource.

[0378] The processing module 1501 is used to determine whether to access the first frequency domain resource based on the priority of the first frequency domain resource.

[0379] The transceiver module 1502 is also used to receive a second SSB. The indication information corresponding to the second SSB carries information indicating the priority of the second frequency domain resource corresponding to the second SSB. The priority of the second frequency domain resource is higher than the priority of the first frequency domain resource. The priority of the second frequency domain resource is the priority of the first communication device accessing the second frequency domain resource.

[0380] The transceiver module 1502 is also used to receive the second SSB when it is determined, based on the priority of the first frequency domain resource, that the first frequency domain resource will not be accessed.

[0381] Optionally, the transceiver module 1502 may include a receiving module and a transmitting module (not shown in FIG15). The transceiver module is used to implement the transmitting and receiving functions of the communication device 1500.

[0382] Optionally, the communication device 1500 may further include a storage module (not shown in FIG15) that stores programs or instructions. When the processing module 1501 executes the program or instructions, the communication device 1500 can perform the functions of the first communication device in any of the communication methods shown in FIG8.

[0383] It should be understood that the communication device 1500 may be a terminal device, a communication module, a circuit or chip responsible for communication functions, a chip system, or other components or assemblies. This communication module, circuit or chip responsible for communication functions, chip system, or other components or assemblies can be applied in a terminal device. This application does not limit this.

[0384] Furthermore, the technical effects of the communication device 1500 can be referenced from the technical effects of the communication method shown in any of Figure 8, and will not be repeated here.

[0385] In other embodiments, the communication device 1500 may be adapted to the communication system shown in FIG1 to perform the functions of the second communication device in the communication method shown in FIG8.

[0386] The processing module 1501 is used to generate a first synchronization signal and a physical broadcast channel block (SSB). The indication information corresponding to the first SSB carries information for determining the priority of the first frequency domain resource corresponding to the first SSB. The priority of the first frequency domain resource is the priority of the first communication device accessing the first frequency domain resource.

[0387] The transceiver module 1502 is used to send the first SSB.

[0388] The transceiver module 1502 is also used to send a second SSB. The indication information corresponding to the second SSB carries information indicating the priority of the second frequency domain resource corresponding to the second SSB. The priority of the second frequency domain resource is higher than the priority of the first frequency domain resource. The priority of the second frequency domain resource is the priority of the first communication device accessing the second frequency domain resource.

[0389] Optionally, the communication device 1500 may further include a storage module (not shown in FIG. 15) that stores programs or instructions. When the processing module 1501 executes the program or instructions, the communication device 1500 can perform the functions of the second communication device in the communication method shown in FIG. 8.

[0390] It should be understood that the processing module 1501 involved in the communication device 1500 can be implemented by a processor or processor-related circuit components, and can be a processor or processing unit; the transceiver module 1502 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver unit.

[0391] It should be noted that the communication device 1500 can be a network device, a communication module, a circuit or chip responsible for communication functions, a chip system, or other components or assemblies. This communication module, circuit or chip responsible for communication functions, chip system, or other components or assemblies can be used in network devices.

[0392] Furthermore, the technical effects of the communication device 1500 can be referred to in the technical effects of the communication methods shown in any of Figure 8, and will not be elaborated here.

[0393] In other embodiments, the communication device 1500 may be adapted to the communication system shown in FIG1 to perform the functions of the first communication device in the communication method shown in FIG14.

[0394] The processing module 1501 is used to determine the priority of the third frequency domain resources and the priority of the fourth frequency domain resources.

[0395] Among them, the priority of the third frequency domain resource is the priority of the first communication device accessing the third frequency domain resource, and the priority of the fourth frequency domain resource is the priority of the first communication device accessing the fourth frequency domain resource.

[0396] The processing module 1501 is also used to determine whether to access the third frequency domain resource or the fourth frequency domain resource based on the priority of the third frequency domain resource and the priority of the fourth frequency domain resource.

[0397] The transceiver module 1502 is used to determine whether to send a random access request on the accessed frequency domain resources.

[0398] Optionally, the transceiver module 1502 may include a receiving module and a transmitting module (not shown in FIG15). The transceiver module is used to implement the transmitting and receiving functions of the communication device 1500.

[0399] Optionally, the communication device 1500 may further include a storage module (not shown in FIG. 15) that stores programs or instructions. When the processing module 1501 executes the program or instructions, the communication device 1500 can perform the functions of the first communication device in any of the communication methods shown in FIG. 14.

[0400] It should be understood that the communication device 1500 may be a terminal device, a communication module, a circuit or chip responsible for communication functions, a chip system, or other components or assemblies. This communication module, circuit or chip responsible for communication functions, chip system, or other components or assemblies can be applied in a terminal device. This application does not limit this.

[0401] Furthermore, the technical effects of the communication device 1500 can be referred to the technical effects of the communication method shown in any of Figure 14, and will not be repeated here.

[0402] For example, Figure 16 is a second schematic diagram of the structure of a communication device provided in an embodiment of this application. This communication device can be a terminal device or a network device, or it can be a chip (system) or other component or assembly that can be disposed in a terminal device or network device. As shown in Figure 16, the communication device 1600 may include a processor 1601. Optionally, the communication device 1600 may also include a memory 1602 and / or a transceiver 1603. The processor 1601 is coupled to the memory 1602 and the transceiver 1603, for example, they can be connected via a communication bus.

[0403] The following section, with reference to Figure 16, provides a detailed description of each component of the communication device 1600:

[0404] The processor 1601 is the control center of the communication device 1600. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1601 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0405] Optionally, the processor 1601 can perform various functions of the communication device 1600 by running or executing software programs stored in the memory 1602 and calling data stored in the memory 1602.

[0406] In a specific implementation, as one example, processor 1601 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG16.

[0407] In a specific implementation, as one embodiment, the communication device 1600 may also include multiple processors, such as processors 1601 and 1604 shown in FIG. 16. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, a processor may refer to one or more devices, circuits, and / or processing cores used for processing data (e.g., computer program instructions).

[0408] The memory 1602 is used to store the software program that executes the solution of this application, and is controlled by the processor 1601 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0409] Optionally, the memory 1602 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1602 may be integrated with the processor 1601 or may exist independently and be coupled to the processor 1601 through the interface circuit of the communication device 1600 (not shown in FIG. 16). This embodiment of the application does not specifically limit this.

[0410] Transceiver 1603 is used for communication with other communication devices. For example, if communication device 1600 is a terminal device, transceiver 1603 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1600 is a network device, transceiver 1603 can be used to communicate with a terminal device or with another network device.

[0411] Optionally, transceiver 1603 may include a receiver and a transmitter (not shown separately in Figure 16). The receiver is used to implement the receiving function, and the transmitter is used to implement the transmitting function.

[0412] Optionally, the transceiver 1603 can be integrated with the processor 1601 or exist independently and be coupled to the processor 1601 through the interface circuit of the communication device 1600 (not shown in FIG16). This application embodiment does not specifically limit this.

[0413] It should be noted that the structure of the communication device 1600 shown in Figure 16 does not constitute a limitation on the communication device. The actual communication device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0414] Furthermore, the technical effects of the communication device 1600 can be referred to the technical effects of the communication method described in the above method embodiments, and will not be repeated here.

[0415] This application provides a communication system. The communication system includes one or more terminal devices and one or more network devices.

[0416] It should be understood that the processor in the embodiments of this application can be a CPU, but it can also be other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0417] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), EEPROM, or flash memory. Volatile memory can be RAM, which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0418] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0419] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0420] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0421] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0422] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0423] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0424] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0425] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0426] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0427] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0428] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to a first communication device, the method includes: The device receives a first synchronization signal and a physical broadcast channel block (SSB), wherein the indication information corresponding to the first SSB carries information for determining the priority of the first frequency domain resource corresponding to the first SSB, and the priority of the first frequency domain resource is the priority of the first communication device accessing the first frequency domain resource. Whether to access the first frequency domain resource is determined based on its priority.

2. The method according to claim 1, characterized in that, The method further includes: The first communication device receives a second SSB, and the indication information corresponding to the second SSB carries information indicating the priority of the second frequency domain resource corresponding to the second SSB. The priority of the second frequency domain resource is higher than the priority of the first frequency domain resource. The priority of the second frequency domain resource is the priority of the first communication device accessing the second frequency domain resource.

3. The method according to claim 2, characterized in that, The receiving of the second SSB includes: If it is determined, based on the priority of the first frequency domain resource, that the first frequency domain resource will not be accessed, the second SSB is received.

4. The method according to any one of claims 1-3, characterized in that, The indication information corresponding to the first SSB also includes second information, which is used to indicate the frequency domain position of the second SSB.

5. A communication method, characterized in that, Applied to a second communication device, the method includes: A first synchronization signal and a physical broadcast channel block (SSB) are generated, wherein the indication information corresponding to the first SSB carries information for determining the priority of the first frequency domain resource corresponding to the first SSB, and the priority of the first frequency domain resource is the priority of the first communication device accessing the first frequency domain resource. Send the first SSB.

6. The method according to claim 5, characterized in that, The method further includes: A second SSB is sent, and the indication information corresponding to the second SSB carries information indicating the priority of the second frequency domain resource corresponding to the second SSB. The priority of the second frequency domain resource is higher than the priority of the first frequency domain resource, and the priority of the second frequency domain resource is the priority of the first communication device accessing the second frequency domain resource.

7. The method according to claim 5 or 6, characterized in that, The indication information corresponding to the first SSB also includes second information, which is used to indicate the frequency domain position of the second SSB.

8. The method according to any one of claims 1-7, characterized in that, The priority of frequency domain resources is related to the type of frequency domain resources.

9. The method according to any one of claims 2, 3, or 6, characterized in that, The first frequency domain resource and the second frequency domain resource are frequency domain resources in the same set of frequency domain resources, or the first frequency domain resource and the second frequency domain resource are frequency domain resources in different sets of frequency domain resources.

10. The method according to any one of claims 2, 3, or 6, characterized in that, The operator corresponding to the first frequency domain resource is the first operator, and the operator corresponding to the second frequency domain resource includes the first operator and the second operator; or, the first frequency domain resource includes the first operator and the second operator, and the second frequency domain resource is the first operator; wherein, the first operator is the operator corresponding to the first communication device, and the second operator is different from the first operator.

11. A communication method, characterized in that, Applied to a first communication device, the method includes: The priorities of the third frequency domain resources and the fourth frequency domain resources are determined, wherein the priority of the third frequency domain resources is the priority of the first communication device accessing the third frequency domain resources, and the priority of the fourth frequency domain resources is the priority of the first communication device accessing the fourth frequency domain resources. Access to the third frequency domain resource or the fourth frequency domain resource is determined based on the priority of the third frequency domain resource and the priority of the fourth frequency domain resource.

12. The method according to claim 11, characterized in that, The priority of frequency domain resources is related to the type of frequency domain resources.

13. The method according to claim 11 or 12, characterized in that, The third frequency domain resource and the fourth frequency domain resource are frequency domain resources in the same frequency domain resource set, or the third frequency domain resource and the fourth frequency domain resource are frequency domain resources in different frequency domain resource sets.

14. The method according to any one of claims 11-13, characterized in that, The operator corresponding to the third frequency domain resource is the first operator, and the operator corresponding to the fourth frequency domain resource includes the first operator and the second operator; or, the third frequency domain resource includes the first operator and the second operator, and the fourth frequency domain resource is the first operator; wherein, the first operator is the operator corresponding to the first terminal device, and the second operator is different from the first operator.

15. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1-14.

16. A communication device, characterized in that, include: Processor and interface circuits; among which, The interface circuit is used to receive code instructions and transmit them to the processor; The processor is used to run the code instructions to perform the method as described in any one of claims 1-14.

17. A communication device, characterized in that, The communication device includes a processor and a transceiver, the transceiver being used for information exchange between the communication device and other communication devices, and the processor executing code instructions to perform the method as described in any one of claims 1-14.

18. A communication device, characterized in that, include: A processor for performing the method as described in any one of claims 1-14.

19. The communication device according to any one of claims 16-18, characterized in that, The communication device further includes a memory for storing code instructions relating to the method as described in any one of claims 1-14.

20. The communication device according to any one of claims 15-19, characterized in that, The communication device is a chip.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-14.

22. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-14.

Images