Method and apparatus for synchronization of bandwidth parts

Abstract

The embodiment of the application discloses a kind of synchronization methods of BWP and its device, it can be applied to communication technology field, the method is executed by terminal device, comprising: determining two and two or more bandwidth parts BWP of uplink access process are configured;Determine to execute first uplink access process, then activate the first BWP corresponding to first uplink access process, wherein first uplink access process is two and two or more uplink access process in any one of process.The embodiment of the application can be activated corresponding BWP according to the uplink access process of terminal equipment confirmed by execution.By this way, it can make network equipment and terminal equipment for the understanding of BWP frequency domain resource used by terminal equipment remain consistent, to avoid signal transmission loss.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for synchronizing bandwidth. Background Technology

[0002] Terminal devices operate in different bandwidth parts (BWP) during different uplink access processes. In related technologies, the network device and the terminal device may have inconsistent understandings of the BWP frequency domain resources currently being used by the terminal device, which may lead to signal loss. Summary of the Invention

[0003] This application provides a method and apparatus for synchronizing bandwidth, which can be applied to fields such as communication technology.

[0004] In a first aspect, embodiments of this application provide a BWP synchronization method, executed by a terminal device, the method comprising:

[0005] Identify the bandwidth portion (BWP) configured for two or more uplink access procedures;

[0006] If the execution of the first uplink access procedure is determined, the first BWP corresponding to the first uplink access procedure is activated, wherein the first uplink access procedure is any one of the two or more uplink access procedures.

[0007] By implementing this application, the terminal device can confirm the activation of the corresponding BWP based on the uplink access procedure performed. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss.

[0008] In one implementation, the method further includes: deactivating the BWP that was active before the first uplink access procedure was executed.

[0009] In one implementation, the method further includes: determining that a switch from the first uplink access procedure to the second uplink access procedure is made, then activating the second BWP corresponding to the second uplink access procedure, and / or deactivating the first BWP.

[0010] In one implementation, the method further includes: receiving a deactivation instruction sent by the network device, wherein the deactivation instruction is used to instruct the terminal device to deactivate the currently activated BWP, the currently activated BWP being the BWP configured in the uplink access procedure currently performed by the terminal device; and activating a third BWP configured by the network device or agreed upon by the protocol.

[0011] In one implementation, the method further includes: listening to a handover trigger event, and if the handover trigger event is detected, determining to switch from the first uplink access procedure to the second uplink access procedure.

[0012] In one implementation, the handover triggering event includes at least one of the following: receiving handover indication information sent by a network device, wherein the handover indication information is used to instruct the terminal device to switch from the first uplink access procedure to the second uplink access procedure; monitoring that the measurement result of the first uplink access procedure no longer meets the measurement threshold value for selecting the first uplink access procedure; monitoring that the number of uplink transmission failures in the first uplink access procedure reaches a threshold value.

[0013] In one implementation, the first BWP and the second BWP overlap.

[0014] In one implementation, different uplink access procedures are configured with different BWPs.

[0015] In one implementation, the configured BWP is the BWP used when the terminal device is in an idle state or a deactivated state.

[0016] In one implementation, the uplink access procedure includes any one of the following: Small Data Transmission (SDT) procedure; Random Access (RACH) SDT procedure; Configuration Authorization (CG) SDT procedure; or Non-SDT uplink access procedure.

[0017] In one implementation, the BWP includes at least one of uplink BWP indication information and downlink BWP indication information.

[0018] In one implementation, the BWP indication information includes at least one of a BWP identifier and a BWP type indication.

[0019] In one implementation, the method further includes: receiving a BWP configured by the network device for each uplink access procedure.

[0020] In one implementation, the method further includes: determining the initial state of the BWP configured for each uplink access procedure based on protocol conventions; or receiving status indication information sent by the network device, the status indication information being used to indicate the initial state of the configured BWP.

[0021] In one implementation, the initial state of the BWP is one of an active state, a deactivated state, and a dormant state.

[0022] In one implementation, the method further includes: determining whether the terminal device is in an idle state or a deactivated state, and determining the currently active BWP as the BWP currently residing on the terminal device.

[0023] In one implementation, the method further includes: determining whether the terminal device is in an idle state or a deactivated state, and performing cell measurement on the cell where the terminal device is camped on a designated BWP, wherein the designated BWP includes one of an initial BWP, a currently active BWP, and a protocol-defined BWP.

[0024] Secondly, embodiments of this application provide another method for synchronizing a BWP, executed by a network device, the method comprising:

[0025] Configure a BWP for two or more uplink access procedures of a terminal device, wherein the uplink access procedures are executed by the terminal device on their respective configured BWPs.

[0026] By implementing this application, the terminal device can confirm the activation of the corresponding BWP based on the uplink access procedure performed. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss.

[0027] In one implementation, the method further includes: sending a deactivation instruction to the terminal device, wherein the deactivation instruction is used to instruct the terminal device to deactivate the currently activated BWP, and the currently activated BWP is the BWP configured in the uplink access procedure currently performed by the terminal device.

[0028] In one implementation, the method further includes: configuring a third BWP to the terminal device, wherein the third BWP is used to be activated by the terminal device.

[0029] In one implementation, the method further includes: sending handover indication information to the terminal device, wherein the handover indication information is used to instruct the terminal device to switch from a first uplink access procedure to a second uplink access procedure.

[0030] In one implementation, the first BWP and the second BWP overlap.

[0031] In one implementation, different uplink access procedures are configured with different BWPs.

[0032] In one implementation, the configured BWP is the BWP used when the terminal device is in an idle state or a deactivated state.

[0033] In one implementation, the uplink access procedure includes any one of the following: Small Data Transmission (SDT) procedure; Random Access (RACH) SDT procedure; Configuration Authorization (CG) SDT procedure; or Non-SDT uplink access procedure.

[0034] In one implementation, the BWP includes at least one of uplink BWP indication information and downlink BWP indication information.

[0035] In one implementation, the BWP indication information includes at least one of a BWP identifier and a BWP type indication.

[0036] In one implementation, the method further includes: sending status indication information to the terminal device, the status indication information being used to indicate the initial state of the configured BWP.

[0037] Thirdly, embodiments of this application provide a communication device that implements some or all of the functions of the terminal device described in the first aspect above. For example, the communication device may have the functions of some or all of the embodiments in this application, or it may have the functions of any one embodiment in this application implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0038] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module supports communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.

[0039] As an example, the processing module can be a processor, the transceiver module can be a transceiver or a communication interface, and the storage module can be a memory.

[0040] Fourthly, embodiments of this application provide another communication device that implements some or all of the functions of the network device in the method example described in the second aspect above. For example, the communication device may have the functions of some or all of the embodiments in this application, or it may have the functions of any one embodiment in this application implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0041] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is coupled to the transceiver module and the processing module, and stores the necessary computer programs and data of the communication device.

[0042] As an example, the processing module can be a processor, the transceiver module can be a transceiver or a communication interface, and the storage module can be a memory.

[0043] Fifthly, embodiments of this application provide a communication device including a processor, which executes the method described in the first aspect when it calls a computer program in memory.

[0044] In a sixth aspect, embodiments of this application provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second aspect above.

[0045] In a seventh aspect, embodiments of this application provide a communication device, which includes a processor and a memory, wherein the memory stores a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the first aspect above.

[0046] Eighthly, embodiments of this application provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the second aspect above.

[0047] Ninthly, embodiments of this application provide a communication device, the device including a processor and an interface circuit, the interface circuit being used to receive code instructions and transmit them to the processor, the processor being used to execute the code instructions to cause the device to perform the method described in the first aspect above.

[0048] In a tenth aspect, embodiments of this application provide a communication device including a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, which is used to execute the code instructions to cause the device to perform the method described in the second aspect above.

[0049] Eleventhly, embodiments of this application provide a synchronization system for a BWP, the system including the communication device described in the third aspect and the communication device described in the fourth aspect, or the system including the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system including the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system including the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0050] In a twelfth aspect, embodiments of the present invention provide a computer-readable storage medium for storing instructions for use by the aforementioned terminal device, which, when executed, cause the terminal device to perform the method described in the first aspect.

[0051] In a thirteenth aspect, embodiments of the present invention provide a readable storage medium for storing instructions for use by the network device described above, which, when executed, cause the network device to perform the method described in the second aspect above.

[0052] In a fourteenth aspect, this application also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0053] In a fifteenth aspect, this application also provides a computer program product including a computer program, which, when run on a computer, causes the computer to perform the method described in the second aspect above.

[0054] In a sixteenth aspect, this application provides a chip system including at least one processor and an interface for supporting a terminal device in implementing the functions involved in the first aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the terminal device. The chip system may be composed of chips or may include chips and other discrete devices.

[0055] In a seventeenth aspect, this application provides a chip system including at least one processor and an interface for supporting a network device in implementing the functions involved in the second aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the network device. The chip system may be composed of chips or may include chips and other discrete devices.

[0056] In an eighteenth aspect, this application provides a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0057] In a nineteenth aspect, this application provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above. Attached Figure Description

[0058] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

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

[0060] Figure 2 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application;

[0061] Figure 3 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application;

[0062] Figure 4 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application;

[0063] Figure 5 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application;

[0064] Figure 6 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application;

[0065] Figure 7 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application;

[0066] Figure 8 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application;

[0067] Figure 9 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application;

[0068] Figure 10 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0069] Figure 11 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0070] Figure 12 This is a schematic diagram of the structure of a chip according to an embodiment of this application. Detailed Implementation

[0071] To facilitate understanding, the terminology used in this application will be introduced first.

[0072] 1. Bandwidth Part (BWP)

[0073] When a terminal device is sending or receiving data, the network device will specify the frequency range in which the terminal device operates, also known as the BWP.

[0074] To better understand the BWP synchronization method disclosed in this application, the communication system to which this application is applicable is first described below.

[0075] Please see Figure 1 , Figure 1 This application provides a schematic diagram of the architecture of a communication system according to an embodiment. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this application. In actual applications, it may include two or more network devices and two or more terminal devices. Figure 1 The communication system shown is exemplified by a network device 101 and a terminal device 102.

[0076] It should be noted that the technical solutions of this application embodiment can be applied to various communication systems. For example, long term evolution (LTE) systems, 5th generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems, etc.

[0077] The network device 101 in this embodiment is a network-side entity used for transmitting or receiving signals. For example, the network device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. This application does not limit the specific technology or device form used in the network device. The network device provided in this embodiment can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0078] In this application embodiment, the terminal device 102 is a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal device.

[0079] It is understood that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does 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 system 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.

[0080] The synchronization method and apparatus for BWP provided in this application will be described in detail below with reference to the accompanying drawings.

[0081] Please see Figure 2 , Figure 2 This is a flowchart illustrating a method for determining the synchronization of a BWP according to an embodiment of this application. Figure 2 As shown, this method is executed by the terminal device and may include, but is not limited to, the following steps:

[0082] S201, determine the bandwidth portion (BWP) configured for two or more uplink access procedures.

[0083] Optionally, the uplink access procedure includes the following: Small Data Transmission (SDT) procedure; Random Access Channel (RACH) SDT procedure; Configure Grant (CG) SDT procedure; and non-SDT uplink access procedure. In this application, two or more uplink access procedures are any two or more combinations of the above-mentioned uplink access procedures.

[0084] As one possible implementation, BWP can be based on two or more uplink access procedures agreed upon in the protocol.

[0085] As another possible implementation, the network device can configure two or more uplink access procedure BWPs. Optionally, the network device sends configuration information to the terminal device, which carries two or more uplink access procedure BWPs. Optionally, the network device can configure two or more uplink access procedure BWPs separately using different configuration information.

[0086] Taking the configuration of the BWP for the CG SDT procedure as an example, the network device configures the CG resource for the CG SDT procedure of cell 1 to the terminal device through a Radio Resource Control Release (RRCRelease) message, and configures BWP1 for the CG resource. Accordingly, the terminal device can determine the CG resource of the CG SDT procedure and the corresponding BWP1 from the RRCRelease message, that is, configure BWP1 for the CG SDT procedure.

[0087] It should be noted that terminal devices in idle or deactivated states operate on the initial BWP configured by the network device, such as performing connection establishment or connection recovery processes; for terminal devices in active states, the network device can configure two or more BWPs for each uplink access process.

[0088] Optionally, each uplink access procedure is configured with a BWP, and different uplink access procedures can be configured with different BWPs.

[0089] Optionally, the BWP includes at least one of uplink BWP indication information and downlink BWP indication information, and the BWP indication information includes at least one of BWP identifier and BWP type indication.

[0090] Optionally, when configuring a BWP for a terminal device, the network device can agree on the initial state of the BWP through a protocol, for example, determining the initial state of the BWP configured for each uplink access procedure based on the protocol agreement.

[0091] Optionally, when configuring a BWP for a terminal device, the network device can indicate the initial state of the BWP, for example, by sending status indication information to the terminal device. This status indication information indicates the initial state of the configured BWP. The initial state of the BWP can be one of three: active, deactivated, or dormant.

[0092] S202, if it is determined that the first uplink access procedure will be executed, then the first BWP corresponding to the first uplink access procedure will be activated, wherein the first uplink access procedure is any one of two or more uplink access procedures.

[0093] In this embodiment of the application, the uplink access process executed by the terminal device is referred to as the first uplink access process.

[0094] In some implementations, if the first uplink access procedure performed by the terminal device is confirmed to be an SDT procedure, then the first BWP corresponding to the SDT procedure is activated.

[0095] In some implementations, if the first uplink access procedure executed by the terminal device is confirmed to be the RACH SDT procedure, then the first BWP corresponding to the RACH SDT procedure is activated.

[0096] In some implementations, if the first uplink access procedure executed by the terminal device is confirmed to be the CG SDT procedure, then the first BWP corresponding to the CGSDT procedure is activated.

[0097] In some implementations, if it is confirmed that the first uplink access procedure executed by the terminal device is a non-SDT uplink access procedure, then the first BWP corresponding to the non-SDT uplink access procedure is activated.

[0098] For example, the network device configures BWP-1 for the CG resource in the CG SDT procedure of cell 1. The terminal device is currently camped in cell 1, and the BWP camped on the terminal device is the initial BWP; that is, the BWP currently activated by the terminal is the initial BWP. In response to the terminal triggering the SDT procedure in cell 1 and executing the CG SDT procedure, since BWP-1 is not the currently activated BWP, the terminal device will activate BWP-1.

[0099] In some implementations, it is determined whether the terminal device is in an idle state or a deactivated state, and cell measurements are performed on the cell where the terminal device is camped on a designated BWP. The designated BWP includes one of the initial BWP, the currently active BWP, and the protocol-defined BWP.

[0100] In this embodiment, to ensure consistent understanding between the network device and the terminal device regarding the BWP frequency domain resources currently used by the terminal device, two or more BWPs configured for uplink access procedures are determined for the terminal device. Any one of these uplink access procedures can serve as the first uplink access procedure. When the terminal device executes the first uplink access procedure, the first BWP corresponding to that procedure is activated. By implementing this embodiment, the terminal device can confirm the activation of the corresponding BWP based on the executed uplink access procedure. This approach ensures consistent understanding between the network device and the terminal device regarding the BWP frequency domain resources used by the terminal device, thereby preventing signal transmission loss.

[0101] The BWP synchronization method provided in this application embodiment further includes the following steps:

[0102] Optionally, in this embodiment, after determining that the terminal device has executed the first uplink access procedure, it is also necessary to deactivate the BWPs that were active before executing the first uplink access procedure. For example, if the first uplink access procedure is an SDT procedure, and the terminal device is in a RACH SDT procedure before executing the SDT procedure, after executing the SDT procedure, it is necessary to collect the first BWPs corresponding to the SDT procedure and further deactivate the BWPs corresponding to the RACH SDT procedure. This application can avoid the situation where two active BWPs exist simultaneously, thus avoiding the waste of frequency domain resources and the problem of easy signal loss during transmission.

[0103] Please see Figure 3 , Figure 3 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application. Figure 3 As shown, this method is executed by the terminal device and may include, but is not limited to, the following steps:

[0104] S301, determine the bandwidth portion (BWP) configured for two or more uplink access procedures.

[0105] S302, if it is determined that the first uplink access procedure will be executed, then the first BWP corresponding to the first uplink access procedure will be activated, wherein the first uplink access procedure is any one of two or more uplink access procedures.

[0106] The details of steps S301 and S302 can be found in the descriptions of the above embodiments, and will not be repeated here.

[0107] S303, Receive deactivation instruction sent by network device, wherein the deactivation instruction is used to instruct terminal device to deactivate the currently activated first BWP.

[0108] In some implementations, when it is necessary to deactivate the currently active BWP of a terminal device, the network device sends a deactivation instruction to the terminal device. The deactivation instruction is used to instruct the terminal device to deactivate the currently active BWP.

[0109] In this embodiment, the currently active BWP is the BWP configured during the uplink access process executed by the current terminal device.

[0110] S304, activates the third BWP configured or agreed upon by the network device.

[0111] After deactivating the first BWP, the terminal device needs to activate the third BWP in order to continue communicating with the network device. Optionally, the third BWP can be configured according to a protocol, for example, the third BWP can be the initial BWP. Optionally, the third BWP can also be configured by the network device to the terminal device. For example, the network device configures the third BWP to be the initial BWP to the terminal device. In this application, when the third BWP is the initial BWP, the terminal device can activate the initial BWP.

[0112] In some implementations, during the CG SDT process on BWP-1, if the terminal device receives a deactivation instruction from the network device, it will deactivate the currently active BWP-1. If the third BWP configured by the network device or agreed upon by the protocol is the initial BWP, the terminal device can activate the initial BWP.

[0113] In some implementations, during the random access process of the terminal device in initial BWP-2, if the terminal device receives a deactivation instruction from the network device, it will deactivate the currently active initial BWP-2 and activate initial BWP-1 according to the protocol. If the third BWP configured by the network device or agreed upon by the protocol is the initial BWP, the terminal device can activate the initial BWP.

[0114] By implementing the embodiments of this application, the terminal device can confirm the activation of the corresponding BWP based on the executed uplink access procedure. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss.

[0115] Please see Figure 4 , Figure 4 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application. Figure 4 As shown, this method is executed by the terminal device and may include, but is not limited to, the following steps:

[0116] S401, determine the bandwidth portion (BWP) configured for two or more uplink access procedures.

[0117] S402, if it is determined that the first uplink access procedure will be executed, then the first BWP corresponding to the first uplink access procedure will be activated, wherein the first uplink access procedure is any one of two or more uplink access procedures.

[0118] The details of steps S401 and S402 can be found in the descriptions of the above embodiments, and will not be repeated here.

[0119] S403, if it is determined that the terminal device has switched from the first uplink access procedure to the second uplink access procedure, then the second BWP corresponding to the second uplink access procedure is activated, and / or the first BWP is deactivated.

[0120] In some implementations, when the services applied by the terminal device change, the uplink access process changes, and the terminal device switches from the first uplink access process to the second uplink access process.

[0121] It should be noted that the BWP corresponding to the first uplink access procedure is called the first BWP, and the BWP of the second uplink access procedure is called the second BWP.

[0122] In some implementations, when the first uplink access procedure switches to the second uplink access procedure, the second BWP corresponding to the second uplink access procedure is activated.

[0123] In some implementations, when the first uplink access procedure switches to the second uplink access procedure, the first BWP is deactivated.

[0124] In some implementations, when the first uplink access procedure switches to the second uplink access procedure, the second BWP corresponding to the second uplink access procedure is activated, and the first BWP is deactivated.

[0125] Optionally, the first BWP and the second BWP overlap. Optionally, the first BWP includes the second BWP; for example, if the frequency range of the second BWP is 2.4GHz-2.5GHz, then the frequency range of the first BWP is 2.43GHz-2.48GHz.

[0126] By implementing the embodiments of this application, the terminal device can confirm the activation of the corresponding BWP based on the executed uplink access procedure. When the services applied by the terminal device change, the BWP can also be adjusted synchronously after switching the uplink access procedure. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss.

[0127] Please see Figure 5 , Figure 5 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application. Figure 5 As shown, this method is executed by the terminal device and may include, but is not limited to, the following steps:

[0128] S501, determine the bandwidth portion (BWP) configured for two or more uplink access procedures.

[0129] S502, if it is determined that the first uplink access procedure will be executed, then the first BWP corresponding to the first uplink access procedure will be activated, wherein the first uplink access procedure is any one of two or more uplink access procedures.

[0130] The details of steps S501 and S502 can be found in the descriptions of the above embodiments, and will not be repeated here.

[0131] S503 listens for the handover trigger event. If the handover trigger event is detected, it determines to switch from the first uplink access procedure to the second uplink access procedure.

[0132] In some implementations, a handover trigger event is determined to have been detected when the terminal device receives a handover indication message sent by the network device; wherein the handover indication message is used to instruct the terminal device to switch from the first uplink access procedure to the second uplink access procedure. Optionally, a Radio Resource Control (RRC) message can be used as the handover indication message; alternatively, a Media Access Control (MAC) control element (CE) or DCI can also be used as the handover indication message.

[0133] In some implementations, a handover trigger event is detected when the measurement results of the first uplink access procedure no longer meet the measurement threshold for selecting the first uplink access procedure.

[0134] In some implementations, a handover trigger event is determined to have been detected when the number of uplink transmission failures during the first uplink access process reaches a threshold.

[0135] After detecting the handover trigger event, the terminal device further determines whether to switch from the first uplink access procedure to the second uplink access procedure.

[0136] S504, activate the second BWP corresponding to the second uplink access procedure, and / or deactivate the first BWP.

[0137] The details of step S504 can be found in the description of the above embodiments, and will not be repeated here.

[0138] By implementing the embodiments of this application, the terminal device can confirm the activation of the corresponding BWP based on the executed uplink access procedure. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss.

[0139] Please see Figure 6 , Figure 6This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application. Figure 6 As shown, this method is executed by the terminal device and may include, but is not limited to, the following steps:

[0140] S601, determine the bandwidth portion (BWP) configured for two or more uplink access procedures.

[0141] S602, if it is determined that the first uplink access procedure will be executed, then the first BWP corresponding to the first uplink access procedure will be activated, wherein the first uplink access procedure is any one of two or more uplink access procedures.

[0142] The details of steps S601 and S602 can be found in the descriptions of the above embodiments, and will not be repeated here.

[0143] S603, determine to switch from the first uplink access procedure to the second uplink access procedure, activate the second BWP corresponding to the second uplink access procedure, and deactivate the first BWP.

[0144] S604, Receive a deactivation instruction sent by the network device, wherein the deactivation instruction is used to instruct the terminal device to deactivate the currently active BWP, and the currently active BWP is the BWP configured in the uplink access procedure performed by the current terminal device.

[0145] S605 activates the third BWP configured or agreed upon by the network device.

[0146] The details of steps S603, S604, and S605 can be found in the descriptions of the above embodiments, and will not be repeated here.

[0147] By implementing the embodiments of this application, the terminal device can confirm the activation of the corresponding BWP based on the executed uplink access procedure. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss.

[0148] Please see Figure 7 , Figure 7 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application. Figure 7 As shown, this method is executed by a network device and may include, but is not limited to, the following steps:

[0149] S701 configures a BWP for two or more uplink access procedures of a terminal device, wherein the uplink access procedures are executed by the terminal device on their respective configured BWPs.

[0150] Optionally, the uplink access procedure includes the following: SDT procedure; RACH SDT procedure; CG SDT procedure; and non-SDT uplink access procedure. In this application, two or more uplink access procedures are any two or more combinations of the above-mentioned uplink access procedures.

[0151] As one possible implementation, the network device can configure two or more uplink access procedure BWPs. Optionally, the network device sends configuration information to the terminal device, which carries two or more uplink access procedure BWPs. Optionally, the network device can configure two or more uplink access procedure BWPs separately using different configuration information.

[0152] Taking the configuration of the BWP for the CG SDT procedure as an example, the network device configures the CG resource for the CG SDT procedure of cell 1 to the terminal device via the RRCRelease message, and configures BWP1 for this CG resource. It should be noted that the network device can also configure the BWP for the traditional random access procedure of cell 1 as the initial BWP to the terminal device via system information. Accordingly, the terminal device can determine the CG resource of the CG SDT procedure and the corresponding BWP1 from the RRCRelease message, that is, configure BWP1 for this CG SDT procedure.

[0153] It should be noted that terminal devices in idle or deactivated states operate on the initial BWP configured by the network device, such as performing connection establishment or connection recovery processes; for terminal devices in active states, the network device can configure two or more BWPs for each uplink access process.

[0154] Optionally, each uplink access procedure is configured with a BWP, and different uplink access procedures can be configured with different BWPs.

[0155] Optionally, the BWP includes at least one of uplink BWP indication information and downlink BWP indication information, and the BWP indication information includes at least one of BWP identifier and BWP type indication.

[0156] Optionally, when configuring a BWP for a terminal device, the network device can agree on the initial state of the BWP through a protocol, for example, determining the initial state of the BWP configured for each uplink access procedure based on the protocol agreement.

[0157] Optionally, when configuring a BWP for a terminal device, the network device can indicate the initial state of the BWP, for example, by sending a status indication message to the terminal device. The status indication message is used to indicate the initial state of the configured BWP.

[0158] Optionally, the initial state of the BWP is one of the following: active state, deactivated state, and dormant state.

[0159] In this embodiment, a Broadband Virtualization Program (BWP) is configured for two or more uplink access procedures of a terminal device, wherein the uplink access procedures are executed by the terminal device on their respective configured BWPs. By implementing this embodiment, the terminal device can confirm the activation of the corresponding BWP based on the executed uplink access procedure. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss.

[0160] Please see Figure 8 , Figure 8 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application. Figure 8 As shown, this method is executed by a network device and may include, but is not limited to, the following steps:

[0161] S801 configures a BWP for two or more uplink access procedures of a terminal device, wherein the uplink access procedures are executed by the terminal device on their respective configured BWPs.

[0162] The details of step S801 can be found in the description of the above embodiments, and will not be repeated here.

[0163] S802, send a deactivation instruction to the terminal device, wherein the deactivation instruction is used to instruct the terminal device to deactivate the currently activated BWP, and the currently activated BWP is the BWP configured in the uplink access procedure performed by the current terminal device.

[0164] In some implementations, when it is necessary to deactivate the currently active BWP of a terminal device, the network device sends a deactivation instruction to the terminal device. The deactivation instruction is used to instruct the terminal device to deactivate the currently active BWP.

[0165] In this embodiment, the currently active BWP is the BWP configured during the uplink access process executed by the current terminal device.

[0166] S803, configure a third BWP to the terminal device, wherein the third BWP is used to be activated by the terminal device.

[0167] After deactivating the current BWP, the terminal device needs to activate a third BWP in order to continue communicating with the network device. Optionally, the third BWP can be configured according to a protocol, for example, the third BWP can be the initial BWP. Optionally, the third BWP can be configured by the network device to the terminal device. For example, the network device configures the third BWP to be the initial BWP to the terminal device. In this application, when the third BWP is the initial BWP, the terminal device can activate the initial BWP.

[0168] In some implementations, during the CG SDT process on BWP-1, if the terminal device receives a deactivation instruction from the network device, it will deactivate the currently active BWP-1. If the third BWP configured by the network device or agreed upon by the protocol is the initial BWP, the terminal device can activate the initial BWP.

[0169] In some implementations, during the random access process of the terminal device in initial BWP-2, if the terminal device receives a deactivation instruction from the network device, it will deactivate the currently active initial BWP-2 and activate initial BWP-1 according to the protocol. If the third BWP configured by the network device or agreed upon by the protocol is the initial BWP, the terminal device can activate the initial BWP.

[0170] By implementing the embodiments of this application, the terminal device can confirm the activation of the corresponding BWP based on the executed uplink access procedure. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss. This application avoids the situation where two BWPs are active simultaneously, preventing the waste of frequency domain resources and the problem of easy signal transmission loss.

[0171] Please see Figure 9 , Figure 9 This is a flowchart illustrating a BWP synchronization method provided in an embodiment of this application. Figure 9 As shown, this method is executed by a network device and may include, but is not limited to, the following steps:

[0172] S901 configures a BWP for two or more uplink access procedures of a terminal device, wherein the uplink access procedures are executed by the terminal device on their respective configured BWPs.

[0173] The details of step S901 can be found in the description of the above embodiments, and will not be repeated here.

[0174] S902, a handover instruction message is sent to the terminal device, wherein the handover instruction message is used to instruct the terminal device to switch from the first uplink access procedure to the second uplink access procedure.

[0175] In some implementations, when the services used by the terminal device change, the uplink access process changes, and the network device sends a handover instruction to the terminal device to instruct the terminal device to switch from the first uplink access process to the second uplink access process.

[0176] Optionally, an RRC message can be used as a handover indication message; alternatively, a MAC CE or DCI message can also be used as a handover indication message.

[0177] By implementing the embodiments of this application, the terminal device can confirm the activation of the corresponding BWP based on the executed uplink access procedure. When the services applied by the terminal device change, the BWP can also be adjusted synchronously after switching the uplink access procedure. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss.

[0178] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspectives of a network device and a first terminal device, respectively. To implement the functions of the methods provided in the embodiments of this application, the network device and the first terminal device may include hardware structures and software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions may be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0179] Please see Figure 10 This is a schematic diagram of the structure of a communication device 100 provided in an embodiment of this application. Figure 10 The communication device 100 shown may include a transceiver module 1001 and a processing module 1002. The transceiver module 1001 may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module 1001 can implement the sending function and / or the receiving function.

[0180] The communication device 100 may be a terminal device (such as the first terminal device in the aforementioned method embodiments), a device within a terminal device, or a device that can be used in conjunction with a terminal device. Alternatively, the communication device 100 may be a network device, a device within a network device, or a device that can be used in conjunction with a network device.

[0181] The communication device 100 is a terminal device (such as the first terminal device in the aforementioned method embodiment), including:

[0182] The processing module 1002 is used to determine the bandwidth portion (BWP) configured for two or more uplink access procedures; if it is determined that the first uplink access procedure is to be executed, the first BWP corresponding to the first uplink access procedure is activated, wherein the first uplink access procedure is any one of the two or more uplink access procedures.

[0183] By implementing the embodiments of this application, the terminal device can confirm the activation of the corresponding BWP based on the executed uplink access procedure. When the services applied by the terminal device change, the BWP can also be adjusted synchronously after switching the uplink access procedure. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss.

[0184] The processing module 1002 is also used to: deactivate the BWP that was in an active state before the execution of the first uplink access procedure.

[0185] The processing module 1002 is further configured to: determine that the switch from the first uplink access procedure to the second uplink access procedure, then activate the second BWP corresponding to the second uplink access procedure, and / or deactivate the first BWP.

[0186] The communication device 100 also includes:

[0187] The transceiver module 1001 is used to receive a deactivation instruction sent by the network device, wherein the deactivation instruction is used to instruct the terminal device to deactivate the currently activated BWP, and the currently activated BWP is the BWP configured in the uplink access procedure executed by the current terminal device.

[0188] The processing module 1002 is also used to activate the third BWP configured or agreed upon by the network device.

[0189] The processing module 1002 is also used to: listen for the handover trigger event, and if the handover trigger event is detected, determine to switch from the first uplink access process to the second uplink access process.

[0190] In one possible implementation, the handover trigger event includes at least one of the following: receiving handover indication information sent by a network device, wherein the handover indication information is used to instruct the terminal device to switch from a first uplink access procedure to a second uplink access procedure; monitoring that the measurement result of the first uplink access procedure no longer meets the measurement threshold value for selecting the first uplink access procedure; monitoring that the number of uplink transmission failures in the first uplink access procedure reaches a threshold value.

[0191] In one possible implementation, the first BWP and the second BWP overlap.

[0192] In one possible implementation, different uplink access procedures are configured with different BWPs.

[0193] In one possible implementation, the configured BWP is the BWP used when the terminal device is in an idle or deactivated state.

[0194] In one possible implementation, the uplink access procedure includes any of the following: Small Data Transmission (SDT) procedure; Random Access (RACH) SDT procedure; Configuration Authorization (CG) SDT procedure; or Non-SDT uplink access procedure.

[0195] In one possible implementation, the BWP includes at least one of uplink BWP indication information and downlink BWP indication information.

[0196] In one possible implementation, the BWP indication information includes at least one of a BWP identifier and a BWP type indication.

[0197] The transceiver module 1001 is also used to receive the BWP configured for each uplink access procedure of the network device.

[0198] The transceiver module 1001 is also used to: determine the initial state of the BWP configured for each uplink access procedure based on the protocol agreement; or receive status indication information sent by the network device, the status indication information being used to indicate the initial state of the configured BWP.

[0199] In one possible implementation, the initial state of BWP is one of the following: active state, deactivated state, and dormant state.

[0200] The processing module 1002 is also used to: determine whether the terminal device is in an idle state or a deactivated state, and determine the currently active BWP as the BWP currently residing on the terminal device.

[0201] The processing module 1002 is further configured to: determine whether the terminal device is in an idle state or a deactivated state, and perform cell measurement on the cell where the terminal device is camped on a specified BWP, wherein the specified BWP includes one of the initial BWP, the currently active BWP, and the protocol-defined BWP.

[0202] Communication device 100 is a network device, including:

[0203] The processing module 1001 is used to configure BWP for two or more uplink access procedures of the terminal device, wherein the uplink access procedures are executed by the terminal device on their respective configured BWPs.

[0204] By implementing the embodiments of this application, the terminal device can confirm the activation of the corresponding BWP based on the executed uplink access procedure. When the services applied by the terminal device change, the BWP can also be adjusted synchronously after switching the uplink access procedure. In this way, the network device and the terminal device can maintain a consistent understanding of the BWP frequency domain resources used by the terminal device, thereby avoiding signal transmission loss.

[0205] The communication device 100 also includes:

[0206] The transceiver module 1001 is further configured to: send a deactivation instruction to the terminal device, wherein the deactivation instruction is used to instruct the terminal device to deactivate the currently activated BWP, and the currently activated BWP is the BWP configured in the uplink access procedure executed by the current terminal device.

[0207] The processing module 1002 is used to configure a third BWP to the terminal device, wherein the third BWP is used to be activated by the terminal device.

[0208] The transceiver module 1001 is also used to: send handover indication information to the terminal device, wherein the handover indication information is used to instruct the terminal device to switch from the first uplink access procedure to the second uplink access procedure.

[0209] In one possible implementation, the first BWP and the second BWP overlap.

[0210] In one possible implementation, different uplink access procedures are configured with different BWPs.

[0211] In one possible implementation, the configured BWP is the BWP used when the terminal device is in an idle or deactivated state.

[0212] In one possible implementation, the uplink access procedure includes any of the following: Small Data Transmission (SDT) procedure; Random Access (RACH) SDT procedure; Configuration Authorization (CG) SDT procedure; or Non-SDT uplink access procedure.

[0213] In one possible implementation, the BWP includes at least one of uplink BWP indication information and downlink BWP indication information.

[0214] In one possible implementation, the BWP indication information includes at least one of a BWP identifier and a BWP type indication.

[0215] The transceiver module 1001 is also used to: send status indication information to the terminal device, the status indication information being used to indicate the initial status of the configured BWP.

[0216] Please see Figure 11 , Figure 11This is a schematic diagram of another communication device 110 provided in an embodiment of this application. The communication device 110 can be a network device, a terminal device (such as the first terminal device in the foregoing method embodiments), a chip, chip system, or processor that supports the network device in implementing the above methods, or a chip, chip system, or processor that supports the terminal device in implementing the above methods. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0217] The communication device 110 may include one or more processors 1101. The processor 1101 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0218] Optionally, the communication device 110 may further include one or more memories 1102, which may store a computer program 1104. The processor 1101 executes the computer program 1104 to cause the communication device 110 to perform the method described in the above method embodiments. Optionally, the memory 1102 may also store data. The communication device 110 and the memory 1102 may be provided separately or integrated together.

[0219] Optionally, the communication device 110 may also include a transceiver 1105 and an antenna 1106. The transceiver 1105 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1105 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0220] Optionally, the communication device 110 may further include one or more interface circuits 1107. The interface circuits 1107 are used to receive code instructions and transmit them to the processor 1101. The processor 1101 executes the code instructions to cause the communication device 110 to perform the methods described in the above method embodiments.

[0221] Communication device 110 is a terminal device (such as the first terminal device in the aforementioned method embodiment): processor 1101 is used to execute Figure 2 Steps S201 and S202 in the process; execute Figure 3 Steps S301, S302, and S304 in the process; Figure 4 Steps S401, S402, and S403 in the process; Figure 5Steps S501, S502, S503, and S504 in the above steps; or Figure 6 Steps S601, S602, S603, and S605 are described in the text. Transceiver 1105 is used to execute... Figure 3 Step S303 in the process; Figure 6 Step S604 in the process.

[0222] Communication device 110 is a network device: transceiver 1105 is used to perform execution Figure 8 Step S802 in the process; Figure 9 Step S902 in the process. Processor 1101 is used to execute Figure 7 Step S701 in the process; Figure 8 Steps S801 and S803 in the process; Figure 9 Step S901 in the process.

[0223] In one implementation, the processor 1101 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0224] In one implementation, processor 1101 may store computer program 1103, which runs on processor 1101 and causes communication device 110 to perform the methods described in the above method embodiments. Computer program 1103 may be embedded in processor 1101, in which case processor 1101 may be implemented in hardware.

[0225] In one implementation, the communication device 110 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0226] The communication device described in the above embodiments may be a network device or a terminal device (such as the first terminal device in the foregoing method embodiments), but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may vary. Figure 11 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0227] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0228] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0229] (3) ASIC, such as modem;

[0230] (4) Modules that can be embedded in other devices;

[0231] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0232] (6) Others, etc.

[0233] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 12 The diagram shows the structure of the chip. Figure 12 The chip shown includes a processor 1201 and an interface 1202. There can be one or more processors 1201, and multiple interfaces 1202.

[0234] For cases where the chip is used to implement the functions of the terminal device in the embodiments of this application (such as the first terminal device in the aforementioned method embodiments):

[0235] Interface 1202 is used for execution Figure 3 Step S303 in the process; Figure 6 Step S604 in the process.

[0236] For cases where the chip is used to implement the functions of the network device in the embodiments of this application:

[0237] Interface 1202 is used to perform execution. Figure 8 Step S802 in the process; Figure 9 Step S902 in the process.

[0238] Optionally, the chip also includes a memory 1203 for storing necessary computer programs and data.

[0239] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0240] This application also provides a BWP synchronization system, which includes the aforementioned Figure 10 In the embodiments, the communication device serves as a terminal device (such as the first terminal device in the aforementioned method embodiments) and the communication device serves as a network device; alternatively, the system includes the aforementioned... Figure 11 The embodiments include a communication device as a terminal device (such as the first terminal device in the aforementioned method embodiments) and a communication device as a network device.

[0241] This application also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0242] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0243] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and 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 program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0244] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., involved in this application are merely for the convenience of description and are not intended to limit the scope of the embodiments of this application, nor do they indicate the order of sequence.

[0245] At least one in this application can also be described as one or more, and multiple can be two, three, four or more, and this application does not impose any limitation. In the embodiments of this application, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order or size among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0246] The correspondences shown in the tables of this application can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this application is not limited to these values. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this application may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headings of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0247] The term "predefined" in this application can be understood as definition, pre-defined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0248] 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.

[0249] 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.

[0250] 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 synchronization method for the bandwidth portion, characterized in that, Performed by a user equipment, the method includes: Identify the bandwidth portion (BWP) configured for two or more uplink access procedures; If it is determined that the first uplink access procedure will be executed, then the first BWP corresponding to the first uplink access procedure will be activated, wherein the first uplink access procedure is any one of the two or more uplink access procedures; If it is determined that the switch from the first uplink access procedure to the second uplink access procedure is initiated, the second BWP corresponding to the second uplink access procedure is activated, and / or the first BWP is deactivated; wherein the second BWP corresponding to the second uplink access procedure is different from the first BWP corresponding to the first uplink access procedure; the uplink access procedure includes at least one of the following: Small Data Transmission Deployment (SDT) procedure, Random Access Deployment (RACH) Deployment Deployment (RACH) procedure, and Configuration Authorization Deployment (CG) Deployment (CG) procedure.

2. The method according to claim 1, characterized in that, The method further includes: Deactivate the BWP that was active before executing the first uplink access procedure.

3. The method according to claim 1, characterized in that, The method further includes: The user equipment receives a deactivation instruction sent by a network device. The deactivation instruction is used to instruct the user equipment to deactivate the currently active BWP, which is the BWP configured in the uplink access procedure currently being performed by the user equipment. Activate the third BWP configured or agreed upon by the network device.

4. The method according to claim 1, characterized in that, The method further includes: The system listens for handover trigger events, and upon detecting such events, determines whether to switch from the first uplink access procedure to the second uplink access procedure; wherein the handover trigger event includes at least one of the following: Receive handover indication information sent by a network device, wherein the handover indication information is used to instruct the user equipment to switch from the first uplink access procedure to the second uplink access procedure; The monitoring detected that the measurement results of the first uplink access process no longer meet the measurement threshold value for selecting the first uplink access process; The monitoring showed that the number of uplink transmission failures in the first uplink access process reached the threshold value.

5. The method according to claim 1, characterized in that, The first BWP and the second BWP overlap.

6. The method according to any one of claims 1-5, characterized in that, Different uplink access procedures are configured with different BWPs.

7. The method according to claim 6, characterized in that, The configured BWP is the BWP used when the user equipment is in an idle state or a deactivated state.

8. The method according to any one of claims 1-5, characterized in that, The BWP includes at least one of uplink BWP indication information and downlink BWP indication information.

9. The method according to claim 8, characterized in that, The BWP indication information includes at least one of BWP identifier and BWP type indication.

10. The method according to claim 1, characterized in that, The method further includes: The receiving network device configures the BWP for each of the aforementioned uplink access procedures.

11. The method according to claim 10, characterized in that, The method further includes: The initial state of the BWP configured for each uplink access procedure is determined based on the protocol agreement; or The system receives status indication information sent by the network device, the status indication information being used to indicate the initial state of the configured BWP.

12. The method according to claim 11, characterized in that, The initial state of the BWP is one of the following: active state, deactivated state, and dormant state.

13. The method according to claim 1, characterized in that, The method further includes: Determine whether the user equipment is in an idle state or a deactivated state, and identify the currently active BWP as the BWP currently residing in the user equipment.

14. The method according to claim 1, characterized in that, The method further includes: The user equipment is determined to be in an idle state or a deactivated state. Cell measurements are performed on the cell where the user equipment is camped on a designated BWP, wherein the designated BWP includes one of the initial BWP, the currently active BWP, and the protocol-defined BWP.

15. A method for synchronizing a bandwidth portion (BWP), characterized in that, Performed by a network device, the method includes: Configure a BWP for two or more uplink access procedures of a user equipment, wherein the uplink access procedures are executed by the user equipment on their respective configured BWPs, so that when the user equipment determines to switch from a first uplink access procedure to a second uplink access procedure, it activates the second BWP corresponding to the second uplink access procedure and / or deactivates the first BWP corresponding to the first uplink access procedure; wherein the second BWP corresponding to the second uplink access procedure is different from the first BWP corresponding to the first uplink access procedure; the uplink access procedure includes at least one of the following: Small Data Transmission (SDT) procedure, Random Access (RACH) SDT procedure, and Configuration Authorization (CG) SDT procedure.

16. The method according to claim 15, characterized in that, The method further includes: Send a deactivation instruction to the user equipment, wherein the deactivation instruction is used to instruct the user equipment to deactivate the currently active BWP, and the currently active BWP is the BWP configured for the uplink access procedure currently being performed by the user equipment.

17. The method according to claim 16, characterized in that, The method further includes: Configure a third BWP on the user equipment, wherein the third BWP is used to be activated by the user equipment.

18. The method according to claim 15, characterized in that, The method further includes: Send handover indication information to the user equipment, wherein the handover indication information is used to instruct the user equipment to switch from the first uplink access procedure to the second uplink access procedure.

19. The method according to claim 15, characterized in that, The first BWP and the second BWP overlap.

20. The method according to claim 15, characterized in that, Different uplink access procedures are configured with different BWPs.

21. The method according to claim 15, characterized in that, The configured BWP is the BWP used when the user equipment is in an idle state or a deactivated state.

22. The method according to any one of claims 15-21, characterized in that, The BWP includes at least one of uplink BWP indication information and downlink BWP indication information.

23. The method according to claim 22, characterized in that, The BWP indication information includes at least one of BWP identifier and BWP type indication.

24. The method according to claim 15, characterized in that, The method further includes: A status indication message is sent to the user equipment, the status indication message being used to indicate the initial state of the configured BWP.

25. A communication device, characterized in that, The device includes: The processing module is configured to determine the bandwidth portion (BWP) configured for two or more uplink access procedures; if it determines that the first uplink access procedure is to be executed, the first BWP corresponding to the first uplink access procedure is activated, wherein the first uplink access procedure is any one of the two or more uplink access procedures; The processing module is also used for: If it is determined that the switch from the first uplink access procedure to the second uplink access procedure is initiated, the second BWP corresponding to the second uplink access procedure is activated, and / or the first BWP is deactivated; wherein the second BWP corresponding to the second uplink access procedure is different from the first BWP corresponding to the first uplink access procedure; the uplink access procedure includes at least one of the following: Small Data Transmission Deployment (SDT) procedure, Random Access Deployment (RACH) Deployment Deployment (RACH) procedure, and Configuration Authorization Deployment (CG) Deployment (CG) procedure.

26. A communication device, characterized in that, The device includes: A processing module is configured to configure a Base Video Controller (BWP) for two or more uplink access procedures of a user equipment (UE), wherein the uplink access procedures are executed by the UE on their respective configured BWPs, so that when the UE determines to switch from a first uplink access procedure to a second uplink access procedure, it activates the second BWP corresponding to the second uplink access procedure and / or deactivates the first BWP corresponding to the first uplink access procedure; wherein the second BWP corresponding to the second uplink access procedure is different from the first BWP corresponding to the first uplink access procedure; the uplink access procedure includes at least one of the following: Small Data Transmission (SDT) procedure, Random Access RACH (RACH) SDT procedure, and Configuration Authorization (CG) SDT procedure.

27. A communication device, characterized in that, The device includes a processor and a memory, the memory storing computer instructions, the processor executing the computer instructions stored in the memory to cause the device to perform the method as described in any one of claims 1-14.

28. A communication device, characterized in that, The device includes a processor and a memory, the memory storing computer instructions, the processor executing the computer instructions stored in the memory to cause the device to perform the method as described in any one of claims 15-24.

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

30. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method as described in any one of claims 15-24.

31. A computer-readable storage medium storing instructions that, when executed, cause the method as described in any one of claims 1-14 to be implemented.

32. A computer-readable storage medium storing instructions that, when executed, cause the method of any one of claims 15-24 to be implemented.

Images