CN109788563B

CN109788563B - BWP indication method, acquisition method, network side equipment and user terminal

Info

Publication number: CN109788563B
Application number: CN201711132526.5A
Authority: CN
Inventors: 沈晓冬; 潘学明; 姜蕾
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2017-11-15
Filing date: 2017-11-15
Publication date: 2021-09-10
Anticipated expiration: 2037-11-15
Also published as: CN109788563A

Abstract

The invention provides a BWP indicating method, an obtaining method, network side equipment and a user terminal, belonging to the technical field of communication. The BWP indication method is applied to a network side device and comprises the following steps: determining a first BWP allocated for a user terminal; and sending a fallback downlink control message for switching to the user terminal, where the fallback downlink control message carries an identifier of the first BWP. The technical scheme of the invention can indicate whether the UE performs BWP switching or not, and reduce the detection power consumption of the UE.

Description

BWP indication method, acquisition method, network side equipment and user terminal

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a BWP indication method, an acquisition method, a network side device, and a user terminal.

Background

A fifth generation mobile communication system (5G) New air interface (NR) system supports dynamic flexible bandwidth allocation, and divides a system bandwidth into multiple bandwidth parts (BWPs), which can be referred to as bandwidth parts, partial bandwidths, or sub-bands, and divides the system bandwidth into multiple BWPs to support a narrowband User terminal, or User Equipment (UE), and supports the UE to reduce power consumption by dynamically switching between a large bandwidth BWP and a small bandwidth BWP. BWP refers to μ at a given carrier value configuration (e.g., subcarrier spacing, cyclic prefix, etc.)_iA next set of some consecutive Physical Resource Block (PRB) resources. In NR, the maximum and minimum number of PRBs allowed by BWP are shown in table 1:

TABLE 1

Wherein,

for the minimum number of PRBs allowed for the downlink channel BWP,

the maximum number of PRBs allowed for the downlink channel BWP,

for the minimum number of PRBs allowed for the uplink channel BWP,

the maximum number of PRBs allowed for the uplink channel BWP.

The UE may be configured with one or more BWPs, activating only one BWP at a time. A Physical Downlink Shared Channel (PDSCH) or a Physical Downlink Control Channel (PDCCH) other than the activated BWP, and the UE may not receive or allow transmission.

The network side instructs the UE to perform BWP handover through Downlink Control Information (DCI). To make the channel design more flexible, the 5G system introduces the concept of UE blind detection. Specifically, the UE performs tentative detection on each PDCCH candidate (candidate) by trying various assumptions on the premise that the information such as the physical resource location where the DCI is located, the occupied resource size (i.e., the specific aggregation level), and the like is unknown until the DCI is successfully decoded.

If the DCI is missed by the UE, it may cause a disruption in communication. As shown in fig. 1, when the DCI1 triggering BWP2 is missed by the UE, the UE cannot switch to BWP2, and at this time, the terminal cannot detect the DCI2 of BWP2 without detecting the DCI1 of BWP1, thus resulting in communication interruption. Because the field length in the DCI is related to many factors such as the bandwidth and transmission mode of the BWP, the DCI lengths corresponding to different BWPs are different, and in order to avoid communication interruption caused by missing DCI detection by the UE, the UE needs to perform additional blind detection to detect all possible DCI lengths at the same time, which is very inefficient and consumes additional power consumption of the UE.

Disclosure of Invention

The technical problem to be solved by the present invention is to provide a BWP indication method, an acquisition method, a network side device and a user terminal, which can indicate whether a UE performs BWP handover or not, and reduce the detection power consumption of the UE.

To solve the above technical problem, embodiments of the present invention provide the following technical solutions:

in a first aspect, an embodiment of the present invention provides a BWP indication method, applied to a network-side device, including:

determining a first BWP allocated for a user terminal; and

and sending a fallback downlink control message for switching to the user equipment, where the fallback downlink control message carries an identifier of the first BWP.

In a second aspect, an embodiment of the present invention provides a BWP acquisition method, applied to a user terminal, including:

receiving a fallback downlink control message for switching sent by network side equipment; and

and analyzing the identifier of the first BWP allocated to the user terminal by the network side equipment from the fallback downlink control message.

In a third aspect, an embodiment of the present invention provides a network side device, including:

a processing module for determining a first BWP allocated for a user terminal; and

a sending module, configured to send a fallback downlink control message for handover to the ue, where the fallback downlink control message carries an identifier of the first BWP.

In a fourth aspect, an embodiment of the present invention provides a user terminal, including:

a receiving module, configured to receive a fallback downlink control message for handover sent by a network side device; and

and the processing module is used for analyzing the identifier of the first BWP allocated to the user terminal by the network side equipment from the fallback downlink control message.

In a fifth aspect, an embodiment of the present invention provides a network side device, including: memory, a processor and a computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps of the BWP indication method as described above.

In a sixth aspect, an embodiment of the present invention provides a user terminal, including: memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the BWP acquisition method as described above.

In a seventh aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the BWP indication method or implements the steps of the BWP acquisition method.

The embodiment of the invention has the following beneficial effects:

in the above solution, the network side device indicates the BWP allocated to the ue using the fallback downlink control message, so as to indicate whether the ue performs BWP handover, and the size of the fallback downlink control message does not change with the change of the BWP, so that the blind detection burden of the ue is not increased, and the power consumption of the ue can be further saved.

Drawings

Fig. 1 is a diagram illustrating a prior art BWP handover by a DCI instructing a ue;

FIG. 2 is a flowchart illustrating a BWP indication method according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating a BWP acquisition method according to an embodiment of the present invention;

FIG. 4 is a diagram illustrating an embodiment of indicating a user equipment to perform BWP handover via a DCI of a fixed length;

fig. 5 is a block diagram of a network device according to an embodiment of the present invention;

FIG. 6 is a block diagram of a user equipment according to an embodiment of the present invention;

fig. 7 is a schematic diagram of a network device according to an embodiment of the present invention;

fig. 8 is a schematic composition diagram of a user terminal according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Embodiments of the present invention provide a BWP indication method, an acquisition method, a network side device and a user equipment, which can indicate whether a UE performs BWP handover, and reduce detection power consumption of the UE.

An embodiment of the present invention provides a BWP indication method, which is applied to a network-side device, as shown in fig. 2, and includes:

step 101: determining a first BWP allocated for a user terminal; and

step 102: and sending a fallback downlink control message for switching to the user terminal, wherein the fallback downlink control message carries an identifier of the first BWP.

In this embodiment, the network side device uses a fallback (fallback) downlink control message to indicate the BWP allocated to the ue, so as to indicate whether the ue performs BWP handover. The fallback downlink control message is different from the existing DCI and does not change with the change of the BWP, and the length can be preset, so that the blind detection burden of the user terminal is not increased, the user terminal is prevented from detecting all DCI with the possible length through blind detection, and the power consumption of the user terminal can be further saved.

Specifically, the fallback downlink control message is composed of downlink control information carrying control information and CRC.

The identifier of the first BWP may be carried by downlink control information in the fallback downlink control message, or may be carried by a CRC in the fallback downlink control message, where the identifier of the first BWP may be an index (index) or other identifier forms.

Further, the fallback downlink control message may include downlink control information of a preset payload size, where the preset payload size is independent of the bandwidth of the first BWP; or the fallback downlink control message comprises downlink control information in a preset format.

The fallback downlink control message includes downlink control information with a payload size independent of the bandwidth of the first BWP, that is, a special DCI is designed, the DCI is only used when the user equipment performs BWP handover, and the payload size is fixed and independent of the bandwidth of the BWP allocated to the user equipment, unlike the existing DCI, so that the user equipment can detect the DCI more easily without detecting all possible length DCIs through blind detection, and power consumption of the user equipment can be saved. A BWP identification field may be designed in the DCI, and the identification of the first BWP is padded in the BWP identification field. The length of the BWP id field is fixed and may be 2 bits, but may also be other lengths.

The fallback downlink control message comprises downlink control information with a preset format, namely a special DCI is designed, the DCI is only used when the user terminal performs BWP switching, and the format of the DCI is fixed unlike the existing DCI, so that the user terminal can easily detect the DCI without detecting all DCI with possible lengths through blind detection, and further, the power consumption of the user terminal can be saved. The DCI is designed with a BWP identification field, and the BWP identification field is filled with an identification of the first BWP. The length of the BWP id field is fixed and may be 2 bits, but may also be other lengths.

In a specific example, when the CRC in the fallback downlink control message carries the identifier of the first BWP, the sending the fallback downlink control message for handover to the ue includes:

scrambling RNTI information of the user terminal by using the identifier of the first BWP;

scrambling the CRC by using the scrambled RNTI information; and

and sending the fallback downlink control message comprising the scrambled CRC to a user terminal.

In another specific example, when the CRC in the fallback downlink control message carries the identifier of the first BWP, the sending the fallback downlink control message for handover to the ue includes:

scrambling the CRC with an identification of the first BWP; and

In addition, since the fallback downlink control message cannot replace the existing common DCI, the network side device only sends the fallback control message when the user equipment performs BWP handover. The sending of the fallback downlink control message to the user terminal specifically includes:

and when the first BWP is different from a second BWP currently used by the user terminal, sending the fallback downlink control message to the user terminal.

After the user terminal completes the BWP switching, the network side equipment retransmits the common DCI. After the sending the fallback downlink control message to the user equipment, the method further includes:

and stopping sending the fallback downlink control message after receiving a BWP handover completion message sent by the user terminal.

An embodiment of the present invention provides a BWP acquisition method, which is applied to a user terminal, and as shown in fig. 3, the method includes:

step 201: receiving a fallback downlink control message for switching sent by network side equipment; and

step 202: and analyzing the identifier of the first BWP allocated to the user terminal by the network side equipment from the fallback downlink control message.

In this embodiment, the network side device uses the fallback downlink control message to indicate the BWP allocated to the ue, so as to indicate whether the ue performs BWP handover. The fallback downlink control message is different from the existing DCI and does not change with the change of the BWP, and the length can be preset, so that the blind detection burden of the ue is not increased, and the power consumption of the ue can be saved.

The identifier of the first BWP may be carried by downlink control information in the fallback downlink control message, or may be carried by CRC in the fallback downlink control message.

Further, the fallback downlink control message may preset downlink control information of a payload size, where the preset payload size is unrelated to the bandwidth of the first BWP; (ii) a Or the fallback downlink control message comprises downlink control information in a preset format.

When the identifier of the first BWP is filled in the BWP identifier field, the parsing the identifier of the first BWP allocated by the network-side device to the ue from the fallback downlink control message includes: and resolving the identification of the first BWP from the BWP identification field of the downlink control information.

Further, when the CRC of the fallback downlink control message carries the identifier of the first BWP, the parsing, from the fallback downlink control message, the identifier of the first BWP allocated by the network-side device to the ue includes:

and analyzing the CRC of the fallback downlink control message to obtain the identifier of the first BWP.

In a specific example, when the CRC in the fallback downlink control message carries an identifier of the first BWP, the parsing the CRC of the fallback downlink control message to obtain the identifier of the first BWP includes:

descrambling the CRC to obtain scrambled RNTI information;

and descrambling the scrambled RNTI information to obtain the identifier of the first BWP.

In another specific example, when the CRC in the fallback downlink control message carries the identifier of the first BWP, the parsing the CRC of the fallback downlink control message to obtain the identifier of the first BWP includes:

and descrambling the CRC to obtain the identification of the first BWP.

Further, after the analyzing the identifier of the first BWP allocated to the ue by the network-side device from the fallback downlink control message, the method further includes:

and comparing the identifier of the first BWP with the identifier of a second BWP currently used by the user terminal, and switching the user terminal to the first BWP when the identifier of the first BWP is inconsistent with the identifier of the second BWP.

In addition, since the fallback downlink control message cannot replace the existing common DCI, the network side device only sends the fallback control message when the user equipment performs BWP handover. After the user terminal switches to the first BWP, the method further comprises sending a BWP switch complete message to a network-side device. So that the network side device retransmits the normal DCI after receiving the BWP handover complete message.

The technical scheme of the invention is further described by combining the specific embodiments as follows:

detailed description of the preferred embodiment

In this embodiment, a DCI specially used for BWP handover is designed, and for a general DCI, a field length in the DCI is related to many factors such as a bandwidth and a transmission mode of the BWP, and lengths of DCIs corresponding to different BWPs are different. Unlike the general DCI, the length of the DCI of this embodiment is fixed and does not change with the change of BWP, and an additional field is introduced in the DCI to indicate the BWP index (identity), and the BWP index field is not included in the general DCI, specifically, the length of the BWP index field may be 2 bits, although the length of the BWP index field may also be other values.

Since the common DCI has other indication functions that the DCI of this embodiment cannot be replaced, the network side device cannot always send the DCI of this embodiment to the user terminal, but only sends the DCI of this embodiment to the user terminal when performing BWP handover, and after the handover is completed, the network side device needs to send the common DCI to the user terminal.

First, the network-side device determines a first BWP allocated to the ue, and when the first BWP is different from a second BWP currently used by the ue, it may determine that the ue needs to perform BWP handover, and the network-side device fills an identifier of the first BWP in a BWP index field of DCI in this embodiment, and sends the generated DCI to the ue.

After receiving the DCI, the user terminal judges whether the received DCI is common DCI or special DCI, and if the received DCI is common DCI, the user terminal does not need to perform BWP switching; if the received DCI is the special DCI, the user terminal judges whether the BWP switching is needed according to the BWP index field in the DCI. The user terminal compares the identifier of the first BWP in the BWP index field with the identifier of the second BWP currently used by the user terminal, and when the identifier of the first BWP is inconsistent with the identifier of the second BWP, the user terminal switches to the first BWP. After the switching is completed, the user terminal sends a BWP switching completion message to the network side equipment, and after the network side equipment receives the BWP switching completion message, the network side equipment stops sending the special DCI and changes to send the common DCI.

As shown in fig. 4, before the user terminal switches from BWP1 to BWP2, the user terminal simultaneously detects x-bit normal DCI1 and z-bit DCI3, where the length of DCI1 is related to the bandwidth of BWP1, transmission mode, etc., and the length of DCI3 is fixed. When performing BWP handover, the network side device (e.g. base station) sends DCI3 until the network side device receives a BWP handover complete message of the user terminal. After the user terminal completes the BWP handover, the user terminal simultaneously detects y-bit normal DCI2 and z-bit DCI3, where the length of DCI2 is related to the bandwidth of BWP2, transmission mode, and other factors.

In this embodiment, when the user terminal needs to perform BWP handover, a special DCI is used for indication, and the DCI payload (payload) size of the DCI does not change with the change of BWP, so that the DCI blind detection burden of the user terminal is not increased. However, the DCI payload size of the general DCI may change with the change of the BWP, so that the ue needs to perform additional blind detection during the BWP handover to avoid the problem of communication interruption between the network side device and the ue caused by the fact that the ue does not detect the DCI during the handover.

Detailed description of the invention

In this embodiment, an additional field BWP identification field is introduced in some types of DCI formats (formats) (e.g. similar to LTE DCI format 1A) to indicate the BWP index, and for general DCI, there is no BWP index field; the length of the BWP identification field is fixed, and may specifically be 2 bits, or may of course be other values.

After receiving the DCI, the ue determines whether the received DCI is normal DCI or special DCI, and may determine whether the received DCI is normal DCI or special DCI according to whether the BWP index field exists in the DCI. If the received DCI is the common DCI, the user terminal does not need to perform BWP switching; and if a special DCI format of a certain type is received, judging whether the BWP switching is required according to a BWP index field in the DCI format. The user terminal compares the identifier of the first BWP in the BWP index field with the identifier of the second BWP currently used by the user terminal, and when the identifier of the first BWP is inconsistent with the identifier of the second BWP, the user terminal switches to the first BWP.

After the handover is completed, the ue may send a BWP handover complete message to the network-side device, and after the network-side device receives the BWP handover complete message, the network-side device may send a general DCI, or may continue to send the DCI carrying the BWP index field.

Detailed description of the preferred embodiment

In this embodiment, BWP index is used to scramble RNTI, and scrambled RNTI is used to scramble CRC, and the scrambled CRC is sent to the ue along with DCI, that is, different CRCs are used to activate or/reactivate or/deactivate BWP.

Herein, RNTI (Radio Network temporary Identity) is an identifier of the UE in the signal information between the UE and the UTRAN. This identity is an identity at the access stratum layer. There are a number of different RNTIs in LTE, for example:

-SI-RNTI: for parsing system messages

-P-RNTI: for resolving paging channels

-RA-RNTI: used for marking resource blocks used by user terminals for sending random access signals, and then randomly accessing the msg3

-C-RNTI: the method is used for the UE to identify own service;

TPC-PUCCH-RNTI: for resolving PUCCH (Physical Uplink Control CHannel) Uplink power Control information;

TPC-PUSCH-RNTI: the system is used for analyzing PUSCH (Physical Uplink Shared Channel) Uplink power control information;

SPS C-RNTI: the usage is the same as the C-RNTI, which is only used when semi-persistent scheduling is used.

The UE needs to determine whether the received data includes data corresponding to the UE by using the RNTI to descramble without stopping descrambling. The RNTI is a 16-bits sequence carried by scrambling on the CRC of the PDCCH. The UE can descramble the CRC by using different RNTIs in different states, obtain the content on the PDCCH and finally identify the information belonging to the UE on the PDSCH.

The assignment of RNTI is specifically explained in 3GPP TS36.321, as shown in table 2:

TABLE 2

The P-RNTI and the SI-RNTI are fixed values, and the UE searches the two RNTIs in a public search space of the PDCCH; for other RNTIs, the UE may search in a special search space.

In this embodiment, first, a network side device determines a first BWP allocated to a user terminal, and when the first BWP is different from a second BWP currently used by the user terminal, it may determine that the user terminal needs to perform BWP handover, where the network side device scrambles an RNTI of the user terminal by using an identifier of the first BWP and carries information of the scrambled RNTI in a transmission process of DCI, where the information of the RNTI is carried by scrambling a Check bit CRC (Cyclic Redundancy Check) of the DCI. The RNTI may be any RNTI in table 2. In a specific example, the C-RNTI is scrambled by the BWP-index as shown in Table 3 below:

TABLE 3

	C-RNTI＝003D
		BWP-index＝0	003D
BWP-index＝1	003E
		BWP-index＝2	003F
BWP-index＝3	0040

And the user terminal descrambles the CRC after receiving the DCI to obtain scrambled RNTI, descrambles the scrambled RNTI to obtain an identifier of a first BWP, compares the analyzed identifier of the first BWP with an identifier of a second BWP currently used by the user terminal, and switches to the first BWP when the identifier of the first BWP is inconsistent with the identifier of the second BWP.

After the handover is completed, the ue may send a BWP handover complete message to the network-side device, and after the network-side device receives the BWP handover complete message, the network-side device may send a normal CRC, or may continue to send a scrambled CRC.

Detailed description of the invention

In this embodiment, BWP index is used to scramble CRC, and the scrambled CRC is sent to the ue along with DCI, and different CRCs are used to activate or/reactivate or/deactivate BWP.

CRC is one of the most commonly used error checking codes in the field of data communication, and is characterized in that the lengths of the information field and the check field can be arbitrarily selected. CRC is a data transmission error detection function that performs polynomial calculations on data and attaches the resulting result to the back of a frame, and the receiving device also performs similar algorithms to ensure the correctness and integrity of the data transmission.

The basic principle of the cyclic redundancy check code is as follows: splicing the check code of R bits after the information code of K bits, wherein the whole coding length is N bits,thus, this code is also called the (N, K) code. For a given (N, K) code, it can be shown that there is a polynomial g (x) with the highest power N-K-R. According to G (x), a check code of K bits of information can be generated, and G (x) is called a generator polynomial of the CRC code. The specific generation process of the check code comprises the following steps: assuming that the information to be transmitted is represented by the polynomial c (x), c (x) is left-shifted by R bits (which may be represented as c (x) 2^R) So that the right side of C (x) will be free of R bits, which is the position of the check code. By C (x) 2^RThe remainder of the division by the generator polynomial g (x) is the check code.

Any code consisting of a binary string can be one-to-one mapped to a polynomial with coefficients of only '0' and '1'. For example: the polynomial corresponding to the code 1010111 is x⁶+x⁴+x²+ x +1, and the polynomial is x⁵+x³+x²+ x +1 corresponds to code 101111.

The CRC checks commonly used for the control channel and the data channel are different in LTE, and four types of CRC24A, CRC24B, CRCl6, and CRC8 are commonly used. The generator polynomial is as follows:

CRC-24A：g(x)＝x²⁴+x²³+x¹⁸+x¹⁷+x¹⁴+x¹¹+x¹⁰+x⁷+x⁶+x⁵+x⁴+x³+x+1；

CRC-24B:g(x)＝x²⁴+x²³+x⁶+x⁵+x+1；

CRC-16:g(x)＝x¹⁶+x¹²+x⁵+1；

CRC-8:g(x)＝x⁸+x⁷+x⁴+x³+x+1；

the CRC24A and CRC24B with a length of 24 are mainly used for transmission of shared channel data, the CRC16 with a length of 16 is mainly used for transmission of downlink Control channel and broadcast channel data, and the CRC8 with a length of 8 is mainly used for transmission of CQI (Control quality information), as shown in fig. 4.

The application scenarios of CRC24A and CRC24B differ mainly as follows: first, 24bits CRC is added to a transport block TB (length a) according to a generator polynomial of CRC-24A, and then the length of the transport block after CRC check is added is B ═ L + a. After the TB block data is added with the check code 24, if the length exceeds Z6144, the TB block data must be segmented and divided into a plurality of code blocks, and CRC processing is performed again on the code blocks by using the generator polynomial CRC-24B, and CRC addition is performed on each segment.

TABLE 4

Check polynomial	Channel used
		CRC-24A	PDSCH/PUSCH/PMCH/PCH
CRC-24B	PDSCH/PUSCH/PMCH/PCH
		CRC-16	PBCH
CRC-8	Control signalling, e.g. CQI

In order to ensure the reliability of transmission in the transmission process of DCI, CRC bits are added to the transmitted information for checking and correcting errors. Additional information, such as information of BWP index, may be carried by further scrambling the CRC bits.

In this embodiment, first, the network-side device determines a first BWP allocated to the ue, and when the first BWP is different from a second BWP currently used by the ue, it may determine that the ue needs to perform BWP handover, and the network-side device scrambles a CRC appended to the downlink control information by using an identifier of the first BWP, and sends the CRC to the ue along with the DCI.

And the user terminal descrambles the CRC part after receiving the DCI to obtain an identifier of the first BWP, compares the analyzed identifier of the first BWP with an identifier of a second BWP currently used by the user terminal, and switches to the first BWP when the identifier of the first BWP is inconsistent with the identifier of the second BWP.

An embodiment of the present invention further provides a network side device, as shown in fig. 5, including:

a processing module 31, configured to determine a first BWP allocated to the user terminal; and

a sending module 32, configured to send a fallback downlink control message for handover to the ue, where the fallback downlink control message carries an identifier of the first BWP.

Further, the fallback downlink control message is composed of downlink control information carrying control information and corresponding CRC thereof.

Further, the fallback downlink control message includes downlink control information of a preset load size, where the preset load size is unrelated to the bandwidth of the first BWP; or

The fallback downlink control message comprises downlink control information in a preset format.

Further, the downlink control information includes a BWP identification field, and the BWP identification field is filled with the identifier of the first BWP.

Further, the CRC carries an identifier of the first BWP.

Further, the sending module is specifically configured to scramble RNTI information of the user terminal by using the identifier of the first BWP, scramble the CRC by using the scrambled RNTI information, and send the fallback downlink control message including the scrambled CRC to the user terminal.

Further, the sending module is specifically configured to scramble the CRC by using the identifier of the first BWP, and send the fallback downlink control message including the scrambled CRC to the user terminal.

Further, the sending module is specifically configured to send the fallback downlink control message to the ue when the first BWP is different from a second BWP currently used by the ue.

Further, the sending module is further configured to stop sending the fallback downlink control message after receiving a BWP handover complete message sent by the user equipment.

An embodiment of the present invention further provides a user terminal, including:

a receiving module 41, configured to receive a fallback downlink control message for handover sent by a network side device; and

a processing module 42, configured to parse, from the fallback downlink control message, an identifier of the first BWP allocated by the network-side device for the ue.

Further, the downlink control information includes a BWP identification field,

the processing module is specifically configured to parse an identifier of the first BWP from the BWP identifier field of the downlink control information.

Further, the CRC of the fallback downlink control message carries the identifier of the first BWP,

the processing module is specifically configured to parse the CRC of the fallback downlink control message to obtain an identifier of the first BWP.

Further, the processing module is specifically configured to descramble the CRC to obtain scrambled RNTI information, and descramble the scrambled RNTI information to obtain the identifier of the first BWP.

Further, the processing module is specifically configured to descramble the CRC to obtain an identifier of the first BWP.

Further, the user terminal further includes:

and the switching control module is used for comparing the identifier of the first BWP with the identifier of a second BWP currently used by the user terminal, and switching the user terminal to the first BWP when the identifier of the first BWP is inconsistent with the identifier of the second BWP.

Further, the user terminal further includes:

a sending module, configured to send a BWP handover complete message to a network-side device after the user terminal is handed over to the first BWP.

An embodiment of the present invention further provides a network side device, including: memory, a processor and a computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps of the BWP indication method as described above.

Referring to fig. 7, fig. 7 is a structural diagram of a network-side device according to an embodiment of the present invention, which can implement details of the BWP indication method in the foregoing embodiments and achieve the same effects. As shown in fig. 7, the network side device 500 includes: a processor 501, a transceiver 502, a memory 503, a user interface 504, and a bus interface, wherein:

in this embodiment of the present invention, the network side device 500 further includes: a computer program stored on the memory 503 and executable on the processor 501, the computer program realizing the following steps when executed by the processor 501: determining a first BWP allocated for a user terminal; and sending a fallback downlink control message for switching to the user terminal, where the fallback downlink control message carries an identifier of the first BWP.

In fig. 5, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 501 and various circuits of memory represented by memory 503 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 502 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user devices, the user interface 504 may also be an interface capable of interfacing with a desired device externally, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 501 is responsible for managing the bus architecture and general processing, and the memory 503 may store data used by the processor 501 in performing operations.

Optionally, the fallback downlink control message is composed of downlink control information carrying control information and a corresponding CRC thereof.

Optionally, the fallback downlink control message includes downlink control information of a preset load size, where the preset load size is unrelated to the bandwidth of the first BWP; or

Optionally, the downlink control information includes a BWP identification field, and the BWP identification field is filled with an identifier of the first BWP.

Optionally, the CRC carries an identifier of the first BWP.

Optionally, the computer program may further implement the following steps when executed by the processor 501: scrambling RNTI information of the user terminal by using the identifier of the first BWP; scrambling the CRC by using the scrambled RNTI information; and sending the fallback downlink control message comprising the scrambled CRC to a user terminal.

Optionally, the computer program may further implement the following steps when executed by the processor 501: scrambling the CRC with an identification of the first BWP; and sending the fallback downlink control message comprising the scrambled CRC to a user terminal.

Optionally, the computer program may further implement the following steps when executed by the processor 501: and when the first BWP is different from a second BWP currently used by the user terminal, sending the fallback downlink control message to the user terminal.

Optionally, the computer program may further implement the following steps when executed by the processor 501: and stopping sending the fallback downlink control message after receiving a BWP handover completion message sent by the user terminal.

An embodiment of the present invention further provides a user terminal, including: memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the BWP acquisition method as described above.

Referring to fig. 8, fig. 8 is a structural diagram of a user terminal applied in an embodiment of the present invention, which can implement details of the BWP acquisition method in the above embodiments and achieve the same effects. As shown in fig. 8, the user terminal 600 includes: processor 604, antenna 601, radio frequency device 602, baseband device 603, memory 605, network interface 606, and bus interface, wherein:

in this embodiment of the present invention, the user terminal 600 further includes: a computer program stored on the memory 605 and executable on the processor 604, the computer program when executed by the processor 604 performing the steps of: receiving a fallback downlink control message for switching sent by network side equipment; and analyzing the identifier of the first BWP allocated to the user terminal by the network side equipment from the fallback downlink control message.

In FIG. 8, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented in particular by processor 604, and various circuits, represented by memory 605, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The network interface 606 may also be an interface capable of interfacing externally to a desired device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 604 is responsible for managing the bus architecture and general processing, and the memory 605 may store data used by the processor 604 in performing operations.

Optionally, the downlink control information includes a BWP identification field, and when executed by the processor 604, the computer program further can implement the following steps: and resolving the identification of the first BWP from the BWP identification field of the downlink control information.

Optionally, the CRC of the fallback downlink control message carries an identifier of the first BWP, and when executed by the processor 604, the computer program may further implement the following steps: and analyzing the CRC of the fallback downlink control message to obtain the identifier of the first BWP.

Optionally, the computer program when executed by the processor 604 may further implement the steps of: descrambling the CRC to obtain scrambled RNTI information; and descrambling the scrambled RNTI information to obtain the identifier of the first BWP.

Optionally, the computer program when executed by the processor 604 may further implement the steps of: and descrambling the CRC to obtain the identification of the first BWP.

Optionally, after parsing the identifier of the first BWP allocated by the network-side device to the ue from the fallback downlink control message, the computer program when executed by the processor 604 may further implement the following steps: and comparing the identifier of the first BWP with the identifier of a second BWP currently used by the user terminal, and switching the user terminal to the first BWP when the identifier of the first BWP is inconsistent with the identifier of the second BWP.

Optionally, after switching to the first BWP, the computer program when executed by the processor 604 may further implement the following steps: and sending a BWP switching completion message to the network side equipment.

An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the BWP indication method or implements the steps of the BWP acquisition method as described above.

It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units configured to perform the functions described herein, or a combination thereof.

For a software implementation, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.

It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.

While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims.

Claims

1. A BWP indication method is applied to a network side device, and is characterized by comprising the following steps:

determining a first bandwidth portion BWP allocated for the user terminal; and

sending a fallback downlink control message for switching to the user terminal, where the fallback downlink control message carries an identifier of the first BWP;

the rollback downlink control message consists of downlink control information carrying control information and Cyclic Redundancy Check (CRC);

the fallback downlink control message comprises downlink control information with a preset load size, wherein the preset load size is irrelevant to the bandwidth of the first BWP; or

2. The BWP indication method of claim 1,

the downlink control information comprises a BWP identification field, and the BWP identification field is filled with the identifier of the first BWP.

3. The BWP indication method according to claim 1, wherein said CRC carries an identifier of said first BWP.

4. The BWP indication method of claim 3, wherein the sending the fallback downlink control message for handover to the user equipment comprises:

scrambling the Radio Network Temporary Identifier (RNTI) information of the user terminal by using the identifier of the first BWP;

scrambling the CRC by using the scrambled RNTI information;

5. The BWP indication method of claim 3, wherein the sending the fallback downlink control message for handover to the user equipment comprises:

scrambling the CRC with an identification of the first BWP;

6. The BWP indication method according to claim 1, wherein the sending of the fallback downlink control message to the ue is specifically:

7. The BWP indication method of claim 6, wherein after the sending the fallback downlink control message to the user equipment, the method further comprises:

8. A BWP acquisition method is applied to a user terminal, and is characterized by comprising the following steps:

analyzing the identifier of the first bandwidth part BWP allocated to the user terminal by the network side equipment from the fallback downlink control message;

9. The BWP obtaining method according to claim 8, wherein the downlink control information includes a BWP identification field, and the parsing the identification of the first BWP allocated by the network-side device to the ue from the fallback downlink control message comprises:

and resolving the identification of the first BWP from the BWP identification field of the downlink control information.

10. The BWP obtaining method according to claim 8, wherein the CRC of the fallback downlink control message carries an identifier of the first BWP, and the parsing the identifier of the first BWP allocated by the network-side device to the ue from the fallback downlink control message includes:

11. The BWP acquisition method according to claim 10, wherein the parsing the CRC of the fallback downlink control message to obtain the identifier of the first BWP comprises:

descrambling the CRC to obtain scrambled radio network temporary identifier RNTI information;

12. The BWP acquisition method according to claim 10, wherein the parsing the CRC of the fallback downlink control message to obtain the identifier of the first BWP comprises:

and descrambling the CRC to obtain the identification of the first BWP.

13. The BWP obtaining method according to claim 8, wherein after parsing out the identifier of the first BWP allocated by the network-side device for the ue from the fallback downlink control message, the method further comprises:

14. The BWP acquisition method of claim 13, wherein after the user terminal switches to the first BWP, the method further comprises:

and sending a BWP switching completion message to the network side equipment.

15. A network-side device, comprising:

a processing module for determining a bandwidth portion allocated for a user terminal, a first BWP; and

a sending module, configured to send a fallback downlink control message for handover to the ue, where the fallback downlink control message carries an identifier of the first BWP;

16. The network-side device of claim 15,

17. The network-side device of claim 15, wherein the CRC carries an identifier of the first BWP.

18. The network-side device of claim 17,

the sending module is specifically configured to scramble radio network temporary identity RNTI information of the user terminal by using the identifier of the first BWP, scramble the CRC by using the scrambled RNTI information, and send the fallback downlink control message including the scrambled CRC to the user terminal.

19. The network-side device of claim 17,

the sending module is specifically configured to scramble the CRC with the identifier of the first BWP, and send the fallback downlink control message including the scrambled CRC to the user terminal.

20. The network-side device of claim 15,

the sending module is specifically configured to send the fallback downlink control message to the ue when the first BWP is different from a second BWP currently used by the ue.

21. The network-side device of claim 20,

the sending module is further configured to stop sending the fallback downlink control message after receiving a BWP handover completion message sent by the user terminal.

22. A user terminal, comprising:

a processing module, configured to parse, from the fallback downlink control message, an identifier of a first bandwidth portion BWP allocated by the network side device for the ue, where the fallback downlink control message is composed of downlink control information carrying control information and a Cyclic Redundancy Check (CRC);

23. The UE of claim 22, wherein the downlink control information comprises a BWP identification field,

24. The UE of claim 22, wherein a CRC of the fallback downlink control message carries an identifier of the first BWP,

25. The user terminal of claim 24,

the processing module is specifically configured to descramble the CRC to obtain scrambled radio network temporary identity RNTI information, and descramble the scrambled RNTI information to obtain the identity of the first BWP.

26. The user terminal of claim 24,

the processing module is specifically configured to descramble the CRC to obtain an identifier of the first BWP.

27. The user terminal according to claim 22, further comprising:

28. The user terminal of claim 27, further comprising:

29. A network-side device, comprising: memory, processor and computer program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the BWP indication method according to any of the claims 1 to 7.

30. A user terminal, comprising: memory, processor and computer program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the BWP acquisition method according to any one of claims 8 to 14.

31. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, carries out the steps of the BWP indication method according to one of the claims 1 to 7 or the steps of the BWP acquisition method according to one of the claims 8 to 14.