Patent Description:
Terminal devices may be classified into a single-SIM terminal and a multi-SIM terminal (for example, a dual-SIM terminal). The single-SIM terminal includes a subscriber identity module (Subscriber Identity Module, SIM), and the multi-SIM terminal includes two or more SIMs. Each SIM in the terminal device may be used as one user equipment (User Equipment, UE).

In a mobile communications system, a time division multiplexing pattern (TDM Pattern) such as a Gap allocation mechanism is generally used to resolve a problem of task scheduling when a resource conflict exists in the terminal device. Specifically, with the development of communications technologies, capabilities, tasks, and resource conflicts of terminal devices, especially multi-SIM terminals, are diversified, and therefore the terminal devices have diversified Gap needs. 3GPP DRAFT R2-<NUM> discussed about predefined rules for the NeedForGap signaling. 3GPP DRAFT S2-<NUM> discussed about a solution for scheduling gap.

However, the current Gap allocation mechanism mainly covers measurement tasks (for example, inter-frequency measurement and inter-RAT measurement), that is, it mainly resolves measurement Gap needs, but cannot resolve diversified Gap negotiation and configuration needs. Therefore, how UE requests diversified Gaps from a network device, and how the network device correspondingly allocates the diversified Gaps, that is, how to make the Gap allocation mechanism cover diversified Gap negotiation and configuration needs becomes a to-be-solved problem.

Embodiments of the present invention provide a Gap configuration method, UE and a network device as defined in the appended set of claims, to resolve a problem of how to make a Gap allocation mechanism cover diversified Gap negotiation and configuration needs.

In the embodiments of the present invention, a network device sends first enabling information to first UE, to indicate whether a first need configuration of a first Gap is enabled, that is, indicate whether a need of a Gap including at least one of N Gap types is enabled. Then, in a case that the first enabling information indicates that the first need configuration is enabled, the first UE may request a first target Gap by sending first request information to the network device, that is, request the first target Gap whose Gap type is at least one of the N Gap types. Further, the network device may send first configuration information to the first UE, to configure the first target Gap for the first UE. In this way, diversified Gap negotiation and configuration between the network device and the first UE are implemented, that is, a Gap allocation mechanism can cover diversified Gap negotiation and configuration needs. Further, through enhanced Gap negotiation, a Gap need of a multi-SIM terminal is met, to avoid service interruption of the multi-SIM terminal and more effectively use network resources, thereby avoiding a resource waste.

The following clearly and completely describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some rather than all of the embodiments of the present invention.

It should be noted that, the character "/" in this specification represents the meaning of "or", for example, A/B may represent A or B; and the term "and/or" in this specification describes only an association relationship for describing associated objects and represents that three relationships may exist.

It should be noted that, to clearly describe the technical solutions of the embodiments of this application, in the embodiments of this application, the terms "first", "second", and the like are used to distinguish same items or similar items whose functions or actions are basically the same, and a person skilled in the art may understand that the terms "first" "second", and the like do not limit a quantity and an execution order. For example, first request information and second request information are used to distinguish between different request information, and are not used to describe a specific sequence of the request information.

It should be noted that, in the embodiments of the present invention, the word "example" or "for example" is used to represent giving an example, an illustration, or a description. Any embodiment or design scheme described as an "example" in the embodiments of the present invention should not be explained as being more preferred or having more advantages than another embodiment or design scheme. Exactly, use of the term "example" or "for example" is intended to present a concept in a specific manner.

It should be noted that in the embodiments this application, "of (of)", "corresponding (corresponding, relevant)", and "corresponding (corresponding)" may be interchangeably used sometimes. It should be noted that, consistent meanings are expressed when differences are not emphasized. "A plurality of" in the embodiments of this application means two or more.

Some terms in this application document are described in the following:.

A dual-SIM terminal and a multi-SIM terminal are collectively referred to as a multi-SIM terminal. The multi-SIM terminal is a terminal device that includes two or more subscriber identity modules (Subscriber Identity Module, SIM). One SIM in the multi-SIM terminal may be used as one user equipment (User Equipment, UE).

A capability of the multi-SIM terminal may be single sending and single receiving, single sending and dual receiving, dual sending and dual receiving, and the like.

The multi-SIM terminal may camp on a plurality of networks at the same time. However, different multi-SIM terminals simultaneously camp on a plurality of networks in different implementations.

Some terminal devices may simultaneously implement data sending and data receiving in a plurality of networks, and data sending and data receiving do not affect each other.

In addition, although some terminal devices may camp on a plurality of networks at the same time, the terminal device may camp on two networks in a time division multiplexing pattern (TDM Pattern). The terminal device may camp on a network A and monitor paging (paging) of the network A in a period of time, and camp on a network B and monitor paging of the network B in another period of time. Alternatively, the terminal device may set up a connection with a network device and send/receive data in a network A in a period of time, and receive paging in a network B in another period of time. Alternatively, the terminal device may receive data in a network A in a period of time, and set up a connection with a network device or send/receive data in a network B in another period of time.

It should be noted that the terminal device may interact with different networks by using different UEs (that is, SIMs) controlled by the terminal device. For example, the terminal device may camp on the network A by using UE A controlled by the terminal device, and camp on the network B by using UE B controlled by the terminal device.

A network (for example, a network device in the network) configures a measurement Gap (Gap) for UE, so that the UE executes a new radio (New Radio, NR) measurement task.

The network sends a Gap need configuration (Need For Gap Configuration) to indicate whether the UE can report a measurement Gap need.

The UE needs to report the measurement Gap need (Need For Gap). In addition, the reported measurement Gap need includes whether a Gap is needed, a frequency band of the needed Gap, intra-frequency measurement of the needed Gap, inter-frequency measurement of the needed Gap, and Inter-RAT measurement of the needed Gap. The network allocates the measurement Gap, so that the UE executes a measurement task by using the allocated Gap.

However, a multi-SIM terminal has diversified tasks, which are specifically embodied as diversified multi-SIM tasks in the multi-SIM terminal. Tasks of the multi-SIM terminal include tasks in an idle mode and tasks in a connected mode. The tasks in the idle mode include paging, measurement, cell search, public land mobile network (Public Land Mobile Network, PLMN) search (Search), and the like. The tasks in the connected mode include a signaling process, SMS sending and receiving, a data service, and the like. In addition, terminal devices with different capabilities have diversified Gap needs when executing different tasks, that is, the terminal devices have Gap needs other than the measurement Gap need, to execute tasks other than the measurement task.

In conclusion, for multi-SIM terminals, capabilities, tasks, and resource conflicts of the terminal devices are diversified. How a terminal device requests a Gap from a network, and how the network correspondingly allocates the Gap becomes a to-be-resolved problem. In other words, a Gap allocation mechanism needs to be improved to better cover Gap negotiation and configuration needs of a multi-SIM terminal, to resolve a problem of how to configure a Gap that supports a task other than a measurement task.

To resolve the foregoing problem, the embodiments of the present invention provide a Gap configuration method, UE, and a network device. A network device sends first enabling information to a first UE, to indicate whether a first need configuration of a first Gap is enabled, that is, indicate whether a need of a Gap including at least one of N Gap types is enabled. Then, in a case that the first enabling information indicates that the first need configuration is enabled, the first UE may request a first target Gap by sending first request information to the network device, that is, request the first target Gap whose Gap type is at least one of the N Gap types. Further, the network device may send first configuration information to the first UE, to configure the first target Gap for the first UE. In this way, diversified Gap negotiation and configuration between the network device and the first UE are implemented, that is, a Gap allocation mechanism can cover diversified Gap negotiation and configuration needs. Further, through enhanced Gap negotiation, a Gap need of a multi-SIM terminal is met, to avoid service interruption of the multi-SIM terminal and more effectively use network resources, thereby avoiding a resource waste.

It should be noted that the Gap configuration method, the UE, and the network device provided in the embodiments of the present invention may be applied to a scenario in which diversified Gap negotiation and configuration is performed between a single-SIM terminal or a multi-SIM terminal and a network device.

In the embodiments of the present invention, the UE may be a SIM installed in the terminal device, or may be a plurality of devices associated with the terminal device. For example, the terminal device and the plurality of UEs may be a plurality of devices in the same Internet of Things, and the terminal device may be used as a control device of the plurality of UEs.

Optionally, in the Gap configuration method provided in the embodiments of the present invention, an execution body on a UE side may be UE, a central processing unit (Central Processing Unit, CPU) of the UE, or a control module configured to perform the Gap configuration method in the UE.

Similarly, in the Gap configuration method provided in the embodiments of the present invention, an execution body on a network device side may be a network device, or a CPU of the network device, or a control module configured to perform the Gap configuration method in the network device.

The technical solutions in the embodiments of the present invention may be applied to various communications systems, for example, a <NUM> Long Term Evolution (Long Term Evolution, LTE) communications system, a <NUM> communications system, a future evolved system, or a plurality of communications fusion systems. There may be a plurality of application scenarios, such as a machine-to-machine (Machine to Machine, M2M) scenario, a D2M scenario, a macro/micro communication scenario, an enhanced mobile broadband (enhance Mobile Broadband, eMBB) scenario, an ultra-reliable and low latency communication (ultra-Reliable & Low Latency Communication, uRLLC) scenario, and a massive machine type communication (Massive Machine Type Communication, mMTC) scenario. These scenarios include but are not limited to communication between terminal devices, communication between network devices, communication between a network device and a terminal device, and the like. For example, the embodiments of the present invention may be applied to communication between a network device in a <NUM> communications system and one or more UEs.

<FIG> is a possible schematic structural diagram of a communications system according to an embodiment of the present invention. As shown in <FIG>, the communications system includes at least one network device <NUM> (only one network device is shown in <FIG>), one or more UEs <NUM> connected to each network device <NUM>, and one or more UEs <NUM> connected to each network device <NUM>. Each UE <NUM> may be a single-SIM terminal, and each UE <NUM> is a multi-SIM terminal.

In addition, <FIG> is another possible schematic structural diagram of a communications system according to an embodiment of the present invention. As shown in <FIG>, the communications system includes at least one network device <NUM> (only one network device is shown in <FIG>), one or more UEs <NUM> connected to each network device <NUM>, and a terminal device <NUM> for connecting and controlling one or more UEs <NUM>.

The network device <NUM> may be a base station, a core network device, a transmission and reception point (Transmission and Reception Point, TRP), a relay station, an access point, or the like. The network device <NUM> may be a base transceiver station (Base Transceiver Station, BTS) in a global system for mobile communication (Global System for Mobile communication, GSM) or a code division multiple access (Code Division Multiple Access, CDMA) network, or may be an NB (NodeB) in wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA), or may be an eNB or an eNodeB (evolved NodeB) in LTE. Alternatively, the network device <NUM> may be a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN) scenario. Alternatively, the network device <NUM> may be a network device in a <NUM> communications system or a network device in a future evolved network. However, use of the words does not constitute a limitation on the present invention.

The UE <NUM>, the UE <NUM>, the UE <NUM>, and the terminal devices may be wireless terminal devices or may be wired terminal devices. The wireless terminal device may be a device that provides voice and/or other service data connectivity for a user, a handheld device with a wireless communication function, a computing device, another processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a future <NUM> network, or a terminal device in a future evolved PLMN network. The wireless terminal device may communicate with one or more core networks by using a radio access network (Radio Access Network, RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or referred to as a "cellular" phone) and a computer with a mobile terminal device. For example, the wireless terminal device may be a portable, pocket-sized, handheld, built-in or vehicle-mounted mobile apparatus. The wireless terminal device may exchange voice and/or data with a radio access network, and may be a device such as a personal communication service (Personal Communication Service, PCS) phone, a cordless phone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, or a personal digital assistant (Personal Digital Assistant, PDA). The wireless terminal device may be alternatively a mobile device, user equipment (User Equipment, UE), a UE terminal device, an access terminal device, a wireless communication device, a terminal device unite, a terminal device station, a mobile station (Mobile Station), a mobile console (Mobile), a remote station (Remote Station), a distant station, a remote terminal device (Remote Terminal), a subscriber unit (Subscriber Unit), a subscriber station (Subscriber Station), a user agent (User Agent), a terminal device apparatus, or the like. For example, in the embodiments of this application, the UE <NUM>, the UE <NUM>, the UE <NUM>, and the terminal device are mobile phones <FIG> and <FIG>.

<FIG> is a schematic flowchart of a Gap configuration method according to an embodiment of the present invention. An example in which first UE interacts with a network device to perform the Gap configuration method is used for description. As shown in <FIG>, the Gap configuration method may include the following steps.

Step <NUM>: A network device sends first enabling information to first UE.

Correspondingly, the first UE may receive the first enabling information from the network device.

The first enabling information is used to indicate whether a first need configuration of a first Gap is enabled, the first Gap is a Gap including at least one of N Gap types, and N is a positive integer.

It can be understood that the first enabling information may be Need For Gap Configuration for the first Gap.

Optionally, the first UE is one UE in a single-SIM terminal or a multi-SIM terminal.

Optionally, the first Gap includes at least one of the following: a Gap for a terminal device; a Gap for the first UE; a Gap for second UE; a first time Gap corresponding to data receiving and sending; a capability-based Gap; a configuration-based Gap; a multiple-input multiple-output (Multiple-Input Multiple-Output, MIMO) Gap; a carrier aggregation (Carrier aggregation, CA) Gap; a second time Gap corresponding to uplink (Uplink, UL) data sending; a third time Gap corresponding to downlink (Downlink, DL) data sending; a Gap corresponding to a master cell group (Master Cell group, MCG) of the first UE; and a Gap corresponding to a secondary cell group ((Secondary Cell group, SCG) of the first UE, where the second UE and the first UE are UE controlled by a same terminal device.

In a case that the second UE and the first UE are controlled by a same terminal device, the first UE and the second UE are different SIMs in the terminal device. Alternatively the first UE and the second UE may be two independent devices (for example, mobile phones) that are simultaneously controlled by the terminal device.

It should be noted that, in this embodiment of the present invention, Gap types may be classified in the following two manners: a manner <NUM> and a manner <NUM>.

Manner <NUM>: Gap types are classified according to devices corresponding to Gaps.

The Gap types classified in the manner <NUM> may include: a Gap for UE, a terminal Gap (Device Gap), a Gap for another UE (Other Gap), and a multi-SIM Gap (multi-SIM Gap).

The Gap for the UE may be the Gap for the first UE, the device Gap may be the Gap for the terminal device, the Gap for the another UE is the Gap for the second UE, and the multi-SIM Gap is implemented by the Gap for the first UE and the Gap for the second UE.

It can be understood that Gap corresponding to MCG of the first UE and the Gap corresponding to the SCG of the first UE may be subdivision of the Gap for the first UE.

Manner <NUM>: Gap types are classified according to tasks corresponding to Gaps.

The Gap types classified in the manner <NUM> may include: a first time Gap corresponding to data receiving and sending; a capability-based Gap; a configuration-based Gap; a MIMO Gap; a CA Gap; a second time Gap; and a third time Gap.

Optionally, the Gap corresponding to the MCG includes at least one of the following: the first time Gap, the capability-based Gap, the configuration-based Gap, the MIMO Gap, the CA Gap, the second time Gap, and the third time Gap; and the Gap corresponding to the SCG includes at least one of the following: the first time Gap, the capability-based Gap, the configuration-based Gap, the MIMO Gap, the CA Gap, the second time Gap, and the third time Gap.

Optionally, one of the N Gap types corresponds to at least one task, and all or a part of the at least one task is different from a measurement task. That is, a Gap of one of the N Gap types may correspond to a task that is different from a measurement task. It indicates that the first Gap that is allocated to the UE by the network device can not only correspond to a measurement task, but also correspond to a task that is different from the measurement task. Apparently, the first Gap provided in this embodiment of the present invention is different from a conventional measurement Gap of a current corresponding measurement task.

Optionally, a task (denoted as a task <NUM>) corresponding to the Gap for the terminal device includes: executing, inside the Gap, tasks of a plurality of UEs controlled by the terminal device.

Tasks of the terminal device may include a multi-UE task and another task. The multi-UE task may be a task of the first UE and a task of the second UE. The another task may be a task of the second UE.

For example, the tasks of the plurality of UEs controlled by the terminal device are states of the plurality of UEs in the terminal device and a task process that is being executed. UE states include an idle (Idle) state, an inactive (Inactive) state, a connected (Connected) state, and the like. UE tasks include tasks in an idle mode and tasks in a connected mode. The tasks in the idle mode may be paging, measurement, cell search, PLMN search, or the like. The tasks in the connected mode may be a signaling process, SMS sending and receiving, a data service, or the like.

Optionally, a task (denoted as a task <NUM>) corresponding to the Gap for the first UE includes: executing a task of the first UE inside the Gap, for example, a task of sending and receiving data in a network A by the first UE.

Optionally, a task (denoted as a task <NUM>) corresponding to the Gap for the second UE includes: executing a task of the second UE inside the Gap.

Optionally, a task corresponding to the first time Gap includes: stopping service data receiving and sending inside the Gap. Therefore, resources originally used for service data receiving and sending may be released inside the Gap, to support task scheduling of the terminal device or the first UE.

Optionally, a task (denoted as a task <NUM>) corresponding to the capability-based Gap includes: using a first capability outside the Gap, and using a second capability inside the Gap, where the first capability is greater than the second capability. Therefore, resources occupied by capabilities used by the first UE may be reduced inside the Gap, to support task scheduling of the terminal device or the first UE.

Optionally, a task (denoted as a task <NUM>) corresponding to the configuration-based Gap includes: using a first configuration outside the Gap, and using a second configuration inside the Gap, where the first configuration is greater than the second configuration. Therefore, resources occupied by configurations used by the first UE may be reduced inside the Gap, to support task scheduling of the terminal device or the first UE.

Optionally, a task (denoted as a task <NUM>) corresponding to the MIMO Gap includes: reducing a quantity of MIMO layers inside the Gap. For example, the quantity of MIMO layers is reduced from <NUM> to <NUM> inside the Gap. Therefore, resources occupied by MIMO may be reduced inside the Gap, to support task scheduling of the terminal device or the first UE.

Optionally, a task (denoted as a task <NUM>) corresponding to the CA Gap includes: reducing a CA quantity inside the Gap. Therefore, resources occupied by a CA process may be reduced inside the Gap, to support task scheduling of the terminal device or the first UE.

Optionally, a task (denoted as a task <NUM>) corresponding to the second time Gap includes: stopping uplink data sending inside the Gap. Therefore, resources originally used for uplink data sending may be released inside the Gap, to support task scheduling of the terminal device or the first UE.

Optionally, a task (denoted as a task <NUM>) corresponding to the third time Gap includes: stopping downlink data receiving inside the Gap. Therefore, resources originally used for downlink data receiving may be released inside the Gap, to support task scheduling of the terminal device or the first UE.

It should be noted that a task corresponding to the first Gap may be any combination of the foregoing tasks <NUM> to <NUM>, that is, an and/or relationship between every two tasks in the tasks <NUM> to <NUM>.

Optionally, the first enabling information and second enabling information are carried in a same information element (information element, IE) in a same message, or the first enabling information and second enabling information are carried in different IEs in a same message, or the first enabling information and second enabling information are carried in different messages, where the second enabling information is received from the network device, the second enabling information is used to indicate whether a second need configuration of a second Gap is enabled, and the second Gap corresponds to a measurement task.

Specifically, the second Gap is only a Gap corresponding to a measurement task in the related art.

Optionally, the network device may send second enabling information to the first UE. Correspondingly, the first UE may receive the second enabling information from the network device.

For example, a message carrying the first enabling information and/or the second enabling information may be a radio resource control resume (RRC Resume) message, a radio resource control reconfiguration (RRC Reconfiguration) message, or the like.

Optionally, in a case that the first enabling information and second enabling information are separately carried in two messages, the network device may simultaneously or separately send the two messages to the first UE.

Optionally, if the first enabling information and the second enabling information are carried in different IEs, the first Gap and the second Gap are separately enabled. The first Gap and the second Gap may be separately enabled by using a same message or different messages.

Optionally, if the first enabling information and the second enabling information are carried in a same IE, the first Gap and the second Gap are separately enabled or the first Gap and the second Gap are simultaneously enabled. The first Gap and the second Gap may be simultaneously enabled by using a same message or different messages.

Step <NUM>: The first UE sends first request information to the network device in a case that the first enabling information indicates that the first need configuration is enabled.

The first request information is used to request a first target Gap, and a Gap type of the first target Gap is at least one of the N Gap types.

Correspondingly, the network device may receive the first request information from the first UE.

For example, the Gap type of the first target Gap is the Gap for the second UE, that is, the Gap for the another UE.

Optionally, the first request information is carried in a target message, where the target message is any one of the following: a radio resource control resume complete (RRC Resume Complete) message, a radio resource reconfiguration complete (RRC Reconfiguration Complete) message, and a user equipment assistance information (UE Assistance Information) message.

Optionally, in a case that the first request information and the second request information are carried in a same message, the message may be RRC Resume Complete, RRC Reconfiguration Complete, or the like.

In a case that the first request information and the second request information are carried in different messages, the first request information may be UE Assistance Information, another message that supports a Gap request, or the like.

Optionally, in a case that the first configuration information and second configuration information are separately carried in two messages, the network device may simultaneously or separately send the two messages to the first UE.

Optionally, the first request information and third request information are carried in different IEs in a same message, or the first request information and third request information are carried in a same IE in a same message, or the first request information and third request information are carried in different messages, where the third request information is used to request a second Gap from the network device, and the second Gap corresponds to a measurement task.

Optionally, the first UE may send third request information to the network device. Correspondingly, the network device may receive the third request information from the first UE.

Optionally, in a case that the first request information and the third request information are separately carried in two messages, the first UE may simultaneously or separately send the two messages to the network device.

Optionally, the first request information includes at least one of the following: first indication information used to indicate whether the first UE needs a Gap, second indication information used to indicate a Gap type of a Gap requested by the first UE, third indication information used to indicate a task corresponding to the Gap requested by the first UE, and Gap time information of the Gap requested by the first UE.

It can be understood that the first indication information in the first request message indicates that the first UE needs a Gap, to be specific, the first UE needs the first target Gap. Specifically, the first indication information "Gap" indicates that the first UE needs a Gap, and the first indication information "No Gap" indicates that the first UE does not need a Gap. The second indication information indicates the Gap type of the first target Gap requested by the first UE. The third indication information indicates a task corresponding to the first target Gap, and a Gap request purpose (Gap Purpose).

Optionally, the Gap time information includes at least one of the following: a start moment of a Gap, Gap duration, and Gap cycle information.

The Gap cycle information is used to indicate that the requested Gap is a one-time Gap or a periodic Gap, a quantity of periodic Gap cycles, a time interval of different cycles, and the like.

Optionally, the task corresponding to the requested Gap (for example, the first target Gap) includes at least one of the following: a task of a terminal device, a task of the first UE, a task of second UE, an idle-state task, a signaling process, and another service. The second UE and the first UE are UE controlled by a same terminal device.

Step <NUM>: The network device sends first configuration information to the first UE according to the first request information.

Correspondingly, the first UE may receive the first configuration information from the network device.

The first configuration information is used to configure the first target Gap.

Optionally, the first configuration information includes at least one of the following: Gap time information of the first Gap and resource configuration information. The resource configuration information is used to indicate a resource configuration of the first UE inside the first Gap, and the resource configuration information is determined based on the first request information.

For example, the resource configuration information is used to instruct the first UE to reduce a part or all of resource configurations in original configurations.

For example, when a Gap type of a Gap requested by the first request information is the Gap for the terminal device, the resource configuration information is used to instruct the first UE to reduce a part or all of resource configurations in the original configurations.

Optionally, the first configuration information and second configuration information are carried in different IEs in a same message, or the first configuration information and second configuration information are carried in a same IE in a same message, or the first configuration information and second configuration information are carried in different messages, where the second configuration information is received from the network device, and the second configuration information is used to configure a second Gap.

Optionally, the network device may send second configuration information to the first UE. Correspondingly, the first UE may receive the second configuration information from the network device.

For example, a message carrying the first configuration information and/or the second configuration information may be a radio resource control resume (RRC Resume) message, a radio resource control reconfiguration (RRC Reconfiguration) message, or the like.

Further, optionally, with reference to <FIG>, as shown in <FIG>, after step <NUM> the Gap method provided in this embodiment of the present invention further includes step <NUM>.

Step <NUM>: The first UE sends second request information to the network device in a case that the first request information changes.

The case that the first request information changes includes at least one of the following: a task corresponding to the first target Gap changes, a configuration of a second Gap changes, and a radio resource control RRC configuration changes.

For example, that the radio resource control RRC configuration changes is that an RRC Reconfiguration message changes.

Optionally, if the configuration of the second Gap changes so that the second Gap meets resource scheduling of a task in the first UE or a terminal device that controls the first UE, the first UE changes to not requiring the first Gap.

Specifically, the second request information is used to request a second target Gap, a Gap type of the second target Gap is at least one of the N Gap types, and the second Gap corresponds to a measurement task. That is, after requesting the first target Gap, the first UE requests the second target Gap of the Gap type in the N Gap types again.

It can be understood that the first target Gap is the same as or different from the second target Gap.

Correspondingly, the network device may receive a second request message from the first UE, where the second request information is a change of the first request information; and
the second request information is used to request a second target Gap, and a Gap type of the second target Gap is at least one of the N Gap types.

It should be noted that, in this embodiment of the present invention, Gap request messages may be classified into a first-type Gap request message used to request diversified Gaps and a second-type Gap request message used to request a measurement Gap. Both a message in which the first request information is located and a message in which the second request information is located are first-type Gap request messages, and a message in which the third request information is located is a second-type Gap request message.

It can be understood that with reference to <FIG>, as shown in <FIG>, the Gap method provided in this embodiment of the present invention further includes step <NUM> and step <NUM>. For example, after step <NUM>, the method further includes step <NUM> and step <NUM>.

Step <NUM>: In a case that the first UE is handed over from a first serving cell to a target serving cell, the network device sends the first request information to the target serving cell by using the first serving cell.

For example, the network device sends the first request information to a base station in which the target serving cell is located by using a base station in which the first serving cell is located.

Step <NUM>: The network device sends the first configuration information to the first UE by using the target serving cell.

In this way, in a case that the first UE is handed over from the first serving cell to the target serving cell, the network device sends the first request information to the target serving cell by using the first serving cell, so that the target serving cell can quickly and conveniently learn the first request information of the first UE, and the first UE does not need to specifically exchange the first request information with the target serving cell.

Optionally, the Gap method provided in this embodiment of the present invention may further include step <NUM>. For example, after step <NUM>, the method further includes step <NUM>.

Step <NUM>: The network device sends third enabling information to the first UE.

Correspondingly, the first UE may receive the third enabling information from the network device.

The third enabling information is used to indicate at least one of the following: whether the first need configuration is enabled, and whether a second need configuration of a second Gap is enabled; and the second Gap corresponds to a measurement task.

It can be understood that the network device may trigger, at any time, enabling information for changing a Gap need for the first UE. For example, in the case of a shortage of resources of the network device, the Gap need for the first UE is disabled.

Optionally, after step <NUM>, the Gap configuration method (specifically, a first Gap negotiation process) provided in this embodiment of the present invention further includes the following scenarios <NUM> to <NUM>:
Scenario <NUM>: A network sets up or releases a second Gap configuration for a plurality of times. For example, the network device may initiate enabling information (for example, third enabling information) for a plurality of times.

Scenario <NUM>: The UE changes a first Gap request. The UE may change content of a Gap request, including that a second Gap is not needed.

Scenario <NUM>: Repeat a negotiation process, including a plurality of times of repetition of the foregoing steps <NUM> to <NUM>.

Scenario <NUM>: The UE in the connected mode may jointly negotiate a first Gap and a second Gap, or independently negotiate a first Gap and a second Gap.

The jointly negotiating the first Gap and the second Gap may include: simultaneously sending information related to the first Gap (for example, enabling information) and information related to the second Gap (for example, enabling information), and carrying the information related to the first Gap and the information related to the second Gap by using a same message or a same information element.

Scenario <NUM>: When the second Gap meets needs of tasks of a plurality of UEs controlled by the terminal device, the UE does not need to initiate the first Gap negotiation.

In this embodiment of the present invention, the Gap configuration method is described below by using examples <NUM> to <NUM>.

First Gap negotiation in a connected (connected) state is described. As shown in <FIG> is a schematic flowchart of a Gap configuration method according to an embodiment of the present invention.

Step <NUM>: UE (for example, first UE) is in a connected state, and receives a downlink message RRC Reconfiguration from a network (denoted as an NW, for example, a network device).

The RRC Reconfiguration message indicates setup or release of a first Gap configuration (Setup/Release NeedForGaps2ConfigNR).

Setup of the first Gap configuration means that a first need configuration of the first Gap is changed from not enabling to enabling, and releasing of the first Gap configuration means that the first need configuration of the first Gap is changed from enabling to not enabling.

Optionally, the first Gap negotiation may be configured as independent IE NeedForGapsConfigNR.

Alternatively, the first Gap and the second Gap are configured in same IE NeedForGapsConfigNR to be separately enabled.

Alternatively, the first Gap and the second Gap are configured in same IE NeedForGapsConfigNR to be simultaneously enabled, that is, being simultaneously set up or released.

The first Gap is a Gap (that is, diversified Gap) including at least one of N Gap types, and the second Gap is a measurement Gap corresponding to a measurement task.

Step <NUM>: The UE sends RRC Reconfiguration Complete.

If the network sets up the first Gap negotiation, the RRC Reconfiguration Complete includes a first Gap request message. The first Gap request message includes Gap information of task needs (for example, NeedForGapsIofo2NR) of a plurality of UEs (for example, the plurality of UEs including the first UE) controlled by a terminal device.

Specifically, the first Gap request message may be the foregoing target message that carries the first request information.

Step <NUM>: The UE sends a UE Assistance Information message when tasks of a plurality of UEs controlled by the terminal device changes.

The UE sends the UE Assistance Information message to initiate the first Gap negotiation (for example, NeedForGapsIofo2NR).

Optionally, the change in the tasks of the plurality of UEs controlled by the terminal device includes but is not limited to:.

Step <NUM>: The UE receives a downlink message RRC Reconfiguration from the network.

The RRC Reconfiguration message includes first Gap configuration information used for Setup/Release NeedForGaps2ConfigNR.

Specifically, in a UE handover process, an original serving cell transmits the first Gap configuration to a handed-over target serving cell. For example, the first Gap request message in step <NUM> is transmitted to the target serving cell by using the original serving cell, so that the RRC Reconfiguration message sent by the target serving cell to the UE includes the first Gap configuration information.

Step <NUM>: The UE sends an RRC Reconfiguration Complete message.

The UE may optionally include the first Gap request message, to negotiate the first Gap (for example, NeedForGapsIofo2NR) again.

The foregoing step <NUM> and step <NUM> may be repeatedly performed.

Optionally, after step <NUM> in the example <NUM>, step <NUM> may be further included.

Step <NUM>: The UE receives a downlink message RRC Reconfiguration.

The RRC Reconfiguration message includes the first Gap configuration information, and the network device may release or set up the first Gap negotiation at any time.

First Gap negotiation when UE enters a connected state from an RRC inactive state is described. As shown in <FIG> is a schematic flowchart of a Gap configuration method according to an embodiment of the present invention.

Step <NUM>: UE (for example, first UE) is in an inactive (that is, inactive) state, and receives a downlink message RRC Resume from a network (that is, an NW).

The RRC Resume message indicates setup or release of the first Gap negotiation (Setup/Release NeedForGaps2ConfigNR).

Optionally, second Gap negotiation may be configured as independent IE NeedForGapsConfigNR.

Alternatively, the second Gap and the first Gap are configured in same IE NeedForGapsConfigNR to be separately enabled.

Alternatively, the second Gap and the first Gap are configured in same IE NeedForGapsConfigNR to be simultaneously enabled, that is, being simultaneously set up or released.

Step <NUM>: If the network sets up the first Gap negotiation, the UE sends RRC Resume Complete.

The RRC Resume Complete includes a first Gap request message, and the first Gap request message includes Gap information of task needs of a plurality of UEs controlled by a terminal device. Specifically, the first Gap request message may be the foregoing target message that carries the first request information.

The RRC Reconfiguration message includes first Gap configuration information.

The UE may optionally include the first Gap request message, to negotiate the first Gap.

The RRC Reconfiguration message includes the first Gap configuration information, and the first Gap negotiation may be released or set up at any time.

UE and a network (for example, a network device) jointly negotiate a first Gap and a second Gap. As shown in <FIG> is a schematic flowchart of a Gap configuration method according to an embodiment of the present invention.

Step <NUM>: UE is in a connected state and receives a downlink message RRC Reconfiguration from a network.

The RRC Reconfiguration message indicates setup or release of first Gap negotiation (Setup/Release NeedForGapsConfigNR).

Optionally, the second Gap and the first Gap are configured in same IE NeedForGapsConfigNR to be separately enabled.

Alternatively, the first Gap negotiation may be configured as independent IE NeedForGaps2ConfigNR.

If the network sets up the first Gap negotiation and/or second Gap negotiation, the RRC Reconfiguration Complete includes a first Gap and/or second Gap request message.

Step <NUM>: The UE initiates the first Gap negotiation and sends a UE Assistance Information message when tasks of a plurality of UEs controlled by a terminal device changes.

The RRC Reconfiguration message includes first Gap and/or second Gap configuration information.

The UE may optionally include the first Gap and/or second Gap request message, to perform Gap negotiation again.

The RRC Reconfiguration message includes the first Gap and/or second Gap configuration information, and the first Gap and/or second Gap negotiation may be released or set up at any time.

UE initiates first Gap request messages (that is, the foregoing target message) for requesting a plurality of Gap types, including but is not limited to:.

In this embodiment of the present invention, a network device sends first enabling information to first UE, to indicate whether a first need configuration of a first Gap is enabled, that is, indicate whether a need of a Gap including at least one of N Gap types is enabled. Then, in a case that the first enabling information indicates that the first need configuration is enabled, the first UE may request a first target Gap by sending first request information to the network device, that is, request the first target Gap whose Gap type is at least one of the N Gap types. Further, the network device may send first configuration information to the first UE, to configure the first target Gap for the first UE. In this way, diversified Gap negotiation and configuration between the network device and the first UE are implemented, that is, a Gap allocation mechanism can cover diversified Gap negotiation and configuration needs. Further, through enhanced Gap negotiation, a Gap need of a multi-SIM terminal is met, to avoid service interruption of the multi-SIM terminal and more effectively use network resources, thereby avoiding a resource waste.

<FIG> is a possible schematic structural diagram of UE according to an embodiment of the present invention. As shown in <FIG>, UE <NUM> is a first UE and includes: a receiving module <NUM>, configured to receive first enabling information from a network device, where the first enabling information is used to indicate whether a first need configuration of a first Gap is enabled, and the first Gap is a Gap including N Gap types; and a sending module <NUM>, configured to send first request information to the network device in a case that the first enabling information received by the receiving module <NUM> indicates that the first need configuration is enabled, where the first request information is used to request a first target Gap, and a Gap type of the first target Gap is at least one of the N Gap types, where the receiving module <NUM> is further configured to receive first configuration information from the network device, where the first configuration information is used to configure the first target Gap.

Optionally, the first Gap includes at least one of the following: a Gap for a terminal device; a Gap for the first UE; a Gap for second UE; a first time Gap corresponding to data receiving and sending; a capability-based Gap; a configuration-based Gap; a multiple-input multiple-output MIMO Gap; a carrier aggregation CA Gap; a second time Gap corresponding to uplink data sending; a third time Gap corresponding to downlink data sending; a Gap corresponding to a master cell group MCG of the first UE; and a Gap corresponding to a secondary cell group SCG of the first UE, where the second UE and the first UE are UE controlled by a same terminal device.

Optionally, one of the N Gap types corresponds to at least one task, and all or a part of the at least one task is different from a measurement task.

Optionally, a task corresponding to the Gap for the terminal device includes: executing, inside the Gap, tasks of a plurality of UEs controlled by the terminal device; and/or a task corresponding to the Gap for the first UE includes: executing a task of the first UE inside the Gap; and/or a task corresponding to the Gap for the second UE includes: executing a task of the second UE inside the Gap; and/or a task corresponding to the first time Gap includes: stopping service data receiving and sending inside the Gap; and/or a task corresponding to the capability-based Gap includes: using a first capability outside the Gap, and using a second capability inside the Gap, where the first capability is greater than the second capability; and/or a task corresponding to the configuration-based Gap includes: using a first configuration outside the Gap, and using a second configuration inside the Gap, where the first configuration is greater than the second configuration; and/or a task corresponding to the MIMO Gap includes: reducing a quantity of MIMO layers inside the Gap; and/or a task corresponding to the CA Gap includes: reducing a CA quantity inside the Gap; and/or a task corresponding to the second time Gap includes: stopping uplink data sending inside the Gap; and/or a task corresponding to the third time Gap includes: stopping downlink data receiving inside the Gap.

Optionally, the first enabling information and second enabling information are carried in a same information element IE in a same message, or the first enabling information and second enabling information are carried in different IEs in a same message, or the first enabling information and second enabling information are carried in different messages, where the second enabling information is received from the network device, the second enabling information is used to indicate whether a second need configuration of a second Gap is enabled, and the second Gap corresponds to a measurement task.

Optionally, if the first enabling information and the second enabling information are carried in different IEs, the first Gap and the second Gap are separately enabled; or if the first enabling information and the second enabling information are carried in a same IE, the first Gap and the second Gap are separately enabled or the first Gap and the second Gap are simultaneously enabled.

Optionally, the sending module <NUM> is further configured to: after sending the first request information to the network device, send second request information to the network device in a case that the first request information changes, where the case that the first request information changes includes at least one of the following: a task corresponding to the first target Gap changes, a configuration of a second Gap changes, and a radio resource control RRC configuration changes; and the second request information is used to request a second target Gap, a Gap type of the second target Gap is at least one of the N Gap types, and the second Gap corresponds to a measurement task.

Optionally, the task corresponding to the requested Gap includes at least one of the following: a task of a terminal device, a task of the first UE, a task of second UE, an idle-state task, a signaling process, and another service, where the second UE and the first UE are UE controlled by a same terminal device.

Optionally, the receiving module <NUM> is further configured to receive third enabling information from the network device after receiving the first enabling information from the network device, where the third enabling information is used to indicate at least one of the following: whether the first need configuration is enabled, and whether a second need configuration of a second Gap is enabled; and the second Gap corresponds to a measurement task.

Optionally, the first configuration information includes at least one of the following: Gap time information of the first Gap and resource configuration information, where the resource configuration information is used to indicate a resource configuration of the first UE inside the first Gap, and the resource configuration information is determined based on the first request information.

The UE <NUM> provided in this embodiment of the present invention can implement the processes of the foregoing method embodiment. To avoid repetition, details are not described herein again.

According to the UE provided in this embodiment of the present invention, the first UE may receive the first enabling information from the network device, to learn whether the first need configuration of the first Gap is enabled, that is, indicate whether a need of the Gap including the at least one of the N Gap types is enabled. Then, in a case that the first enabling information indicates that the first need configuration is enabled, the first UE may request a first target Gap by sending first request information to the network device, that is, request the first target Gap whose Gap type is at least one of the N Gap types. Further, the first UE receives the first configuration information from the network device, to configure the first target Gap. In this way, diversified Gap negotiation and configuration between the network device and the first UE are implemented, that is, a Gap allocation mechanism can cover diversified Gap negotiation and configuration needs. Further, through enhanced Gap negotiation, a Gap need of a multi-SIM terminal is met, to avoid service interruption of the multi-SIM terminal and more effectively use network resources, thereby avoiding a resource waste.

<FIG> is a possible schematic structural diagram of a network device according to an embodiment of the present invention. As shown in <FIG>, a network device <NUM> includes: a sending module <NUM>, configured to send first enabling information to first user equipment UE, where the first enabling information is used to indicate whether a first need configuration of a first Gap is enabled, and the first Gap is a Gap including at least one of N Gap types; and a receiving module <NUM>, configured to receive first request information from the first UE in a case that the first enabling information sent by the sending module <NUM> indicates that the first need configuration is enabled, where the first request information is used to request a first target Gap, and a Gap type of the first target Gap is at least one of the N Gap types, where the sending module <NUM> is further configured to send first configuration information to the first UE according to the first request information received by the receiving module <NUM>, where the first configuration information is used to configure the first target Gap.

Optionally, the receiving module <NUM> is further configured to receive a second request message from the first UE, where the second request information is a change of the first request information; and the second request information is used to request a second target Gap, and a Gap type of the second target Gap is at least one of the N Gap types.

Optionally, the sending module <NUM> is further configured to send third enabling information to the first UE after sending the first enabling information to the first UE, where the third enabling information is used to indicate at least one of the following: whether the first need configuration is enabled, and whether a second need configuration of a second Gap is enabled; and the second Gap corresponds to a measurement task.

Optionally, the first configuration information and second configuration information are carried in different IEs in a same message, or the first configuration information and second configuration information are carried in a same IE in a same message, or the first configuration information and second configuration information are carried in different messages, where the second configuration information is received from the network device, the second configuration information is used to configure a second Gap, and the second Gap corresponds to a measurement task.

Optionally, the sending module <NUM> is further configured to: after sending the first configuration information to the first UE, in a case that the first UE is handed over from a first serving cell to a target serving cell, send the first request information to the target serving cell by using the first serving cell; and send the first configuration information to the first UE by using the target serving cell.

The network device <NUM> provided in this embodiment of the present invention can implement the processes of the foregoing method embodiment. To avoid repetition, details are not described herein again.

According to the network device provided in this embodiment of the present invention, first enabling information is sent to first UE, to indicate whether a first need configuration of a first Gap is enabled, that is, indicate whether a need of a Gap including at least one of N Gap types is enabled. Then, in a case that the first enabling information indicates that the first need configuration is enabled, the first UE may request a first target Gap by sending first request information to the network device, that is, request the first target Gap whose Gap type is at least one of the N Gap types. Further, the network device may send first configuration information to the first UE, to configure the first target Gap for the first UE. In this way, diversified Gap negotiation and configuration between the network device and the first UE are implemented, that is, a Gap allocation mechanism can cover diversified Gap negotiation and configuration needs. Further, through enhanced Gap negotiation, a Gap need of a multi-SIM terminal is met, to avoid service interruption of the multi-SIM terminal and more effectively use network resources, thereby avoiding a resource waste.

<FIG> is a schematic structural diagram of hardware of a terminal device according to the embodiments of the present invention. UE <NUM> includes but is not limited to components such as a radio frequency unit <NUM>, a network module <NUM>, an audio output unit <NUM>, an input unit <NUM>, a sensor <NUM>, a display unit <NUM>, a user input unit <NUM>, an interface unit <NUM>, a memory <NUM>, a processor <NUM>, and a power supply <NUM>. A person skilled in the art may understand that the structure of the UE <NUM> shown in <FIG> constitutes no limitation on the terminal device, and the UE <NUM> may include more or fewer components than those shown in the figure, or combine some components, or have a different component arrangement. In this embodiment of the present invention, the UE <NUM> includes but is not limited to a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle terminal, a wearable device, a pedometer, and the like.

Optionally, the foregoing UE <NUM> may be implemented by the UE <NUM>. For example, the receiving module <NUM> in the UE <NUM> may be implemented by the interface unit <NUM> in the UE <NUM>, and the sending module <NUM> in the UE <NUM> may be implemented by the radio frequency unit <NUM> in the UE <NUM>.

The interface unit <NUM> is configured to receive first enabling information from a network device, where the first enabling information is used to indicate whether a first need configuration of a first Gap is enabled, and the first Gap is a Gap including at least one of N Gap types; the radio frequency unit <NUM> is configured to send first request information to the network device in a case that the first enabling information received by the interface unit <NUM> indicates that the first need configuration is enabled, where the first request information is used to request a first target Gap, and a Gap type of the first target Gap is at least one of the N Gap types; and the interface unit <NUM> is further configured to receive first configuration information from the network device, where the first configuration information is used to configure the first target Gap.

It should be understood that, in this embodiment of the present invention, the radio frequency unit <NUM> may be configured to receive and send information or a signal in a call process. Specifically, after receiving downlink data from a base station, the radio frequency unit <NUM> sends the downlink data to the processor <NUM> for processing. In addition, the radio frequency unit <NUM> sends uplink data to the base station. Usually, the radio frequency unit <NUM> includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit <NUM> may communicate with a network and another device through a wireless communication system.

The UE <NUM> provides wireless broadband Internet access for the user by using the network module <NUM>, for example, helping the user to send and receive an e-mail, brows a web page, and access streaming media.

The audio output unit <NUM> may convert audio data received by the radio frequency unit <NUM> or the network module <NUM> or stored in the memory <NUM> into an audio signal and output the audio signal as a sound. In addition, the audio output unit <NUM> may further provide an audio output (for example, a call signal received voice, or a message received voice) related to a specific function implemented by the UE <NUM>. The audio output unit <NUM> includes a speaker, a buzzer, a telephone receiver, and the like.

The input unit <NUM> is configured to receive an audio signal or a video signal. The input unit <NUM> may include a graphics processing unit (Graphics Processing Unit, GPU) <NUM> and a microphone <NUM>, and the graphics processing unit <NUM> processes image data of a still picture or video obtained by an image capture apparatus (such as a camera) in a video capture mode or an image capture mode. A processed image frame may be displayed on the display unit <NUM>. The image frame processed by the graphics processing unit <NUM> may be stored in the memory <NUM> (or another storage medium) or sent by using the radio frequency unit <NUM> or the network module <NUM>. The microphone <NUM> may receive a sound and can process such sound into audio data. Processed audio data may be converted, in a call mode, into a format that can be sent to a mobile communication base station by using the radio frequency unit <NUM> for output.

The UE <NUM> further includes at least one type of sensor <NUM>, such as a light sensor, a motion sensor, and another sensor. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor may adjust luminance of the display panel <NUM> based on brightness of ambient light. The proximity sensor may turn off the display panel <NUM> and/or backlight when the UE <NUM> moves to an ear. As a type of the motion sensor, an accelerometer sensor may detect an acceleration value in each direction (generally, three axes), and detect a value and a direction of gravity when the accelerometer sensor is static, and may be used in an application for recognizing a posture of the terminal device (such as screen switching between landscape and portrait modes, a related game, or magnetometer posture calibration), a function related to vibration recognition (such as a pedometer or a knock), and the like. The sensor <NUM> may further include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and the like.

The display unit <NUM> is configured to display information entered by a user or information provided for a user. The display unit <NUM> may include a display panel <NUM>.

The user input unit <NUM> may be configured to receive input digit or character information, and generate a key signal input related to a user setting and function control of the UE <NUM>. Specifically, the user input unit <NUM> includes a touch panel <NUM> and another input device <NUM>. The touch panel <NUM> is also referred to as a touchscreen, and may collect a touch operation performed by a user on or near the touch panel <NUM> (such as an operation performed by a user on the touch panel <NUM> or near the touch panel <NUM> by using any proper object or accessory, such as a finger or a stylus). The touch panel <NUM> may include two parts: a touch detection apparatus and a touch controller. The touch detection apparatus detects a touch position of the user, detects a signal brought by the touch operation, and sends the signal to the touch controller. The touch controller receives touch information from the touch detection apparatus, converts the touch information into touch point coordinates, and sends the touch point coordinates to the processor <NUM>, and can receive and execute a command sent by the processor <NUM>. In addition, the touch panel <NUM> may be of a resistive type, a capacitive type, an infrared type, a surface acoustic wave type, or the like. The user input unit <NUM> may include another input device <NUM> in addition to the touch panel <NUM>. Specifically, the another input device <NUM> may include but is not limited to a physical keyboard, a functional button (such as a volume control button or a power on/off button), a trackball, a mouse, and a joystick.

Further, the touch panel <NUM> may cover the display panel <NUM>. When detecting the touch operation on or near the touch panel <NUM>, the touch panel <NUM> transmits the touch operation to the processor <NUM> to determine a type of a touch event, and then the processor <NUM> provides corresponding visual output on the display panel <NUM> based on the type of the touch event. In <FIG>, although the touch panel <NUM> and the display panel <NUM> are used as two independent parts to implement input and output functions of the UE <NUM>, in some embodiments, the touch panel <NUM> and the display panel <NUM> may be integrated to implement the input and output functions of the UE <NUM>. This is not specifically limited herein.

The interface unit <NUM> is an interface for connecting an external apparatus with the UE <NUM>. For example, the external apparatus may include a wired or wireless headphone port, an external power supply (or a battery charger) port, a wired or wireless data port, a storage card port, a port used to connect to an apparatus having an identity module, an audio input/output (I/O) port, a video I/O port, a headset port, and the like. The interface unit <NUM> may be configured to receive input (for example, data information and power) from an external apparatus and transmit the received input to one or more elements in the UE <NUM> or may be configured to transmit data between the UE <NUM> and an external apparatus.

The memory <NUM> may be configured to store a software program and various data. The memory <NUM> may mainly include a program storage area and a data storage area. The program storage area may store an operating system, an application required by at least one function (such as a sound play function or an image play function), and the like. The data storage area may store data (such as audio data or an address book) created based on use of the mobile phone, and the like. In addition, the memory <NUM> may include a high-speed random access memory, and may further include a nonvolatile memory, for example, at least one magnetic disk storage component, a flash memory component, or another volatile solid-state storage component.

The processor <NUM> is a control center of the UE <NUM>, and connects all parts of the entire UE <NUM> by using various interfaces and lines. By running or executing a software program and/or a module stored in the memory <NUM> and invoking data stored in the memory <NUM>, the processor <NUM> performs various functions and/or data processing of the UE <NUM>, to perform overall monitoring on the UE <NUM>. The processor <NUM> may include one or more processing units. Optionally, an application processor and a modem processor may be integrated into the processor <NUM>. The application processor mainly processes an operating system, a user screen, an application, and the like. The modem processor mainly processes wireless communications. It can be understood that, alternatively, the modem processor may not be integrated into the processor <NUM>.

The UE <NUM> may further include the power supply <NUM> (such as a battery) that supplies power to each component. Optionally, the power supply <NUM> may be logically connected to the processor <NUM> by using a power management system, so as to implement functions such as charging, discharging, and power consumption management by using the power management system.

In addition, the UE <NUM> includes some function modules not shown, and details are not described herein.

<FIG> is a schematic structural diagram of hardware of a network device according to an embodiment of the present invention. A network device <NUM> includes a processor <NUM>, a transceiver <NUM>, a memory <NUM>, a user interface <NUM>, and a bus interface.

The transceiver <NUM> is configured to send first enabling information to first user equipment UE, where the first enabling information is used to indicate whether a first need configuration of a first Gap is enabled, and the first Gap is a Gap including at least one of N Gap types; receive first request information from the first UE in a case that the first enabling information indicates that the first need configuration is enabled, where the first request information is used to request a first target Gap, and a Gap type of the first target Gap is at least one of the N Gap types; and send first configuration information to the first UE according to the first request information, where the first configuration information is used to configure the first target Gap.

In this embodiment of the present invention, in <FIG>, a bus architecture may include any quantity of interconnected buses and bridges, and specifically links various circuits of one or more processors represented by the processor <NUM> and a memory represented by the memory <NUM>. The bus architecture may further link various other circuits such as a peripheral device, a voltage regulator, and a power management circuit. These are well known in the art, and therefore are not further described in this specification. A bus interface provides an interface. The transceiver <NUM> may be a plurality of components. To be specific, the transceiver <NUM> includes a transmitter and a receiver, and provides a unit configured to communicate with various other apparatuses on a transmission medium. For different user equipment, a user interface <NUM> may be an interface that can externally or internally connect to a needed device, and the connected device includes but is not limited to a keypad, a display, a loudspeaker, a microphone, and a joystick. The processor <NUM> is responsible for bus architecture management and general processing. The memory <NUM> may store data used by the processor <NUM> when the processor <NUM> performs an operation.

In addition, the network device <NUM> further includes some function modules not shown, and details are not described herein.

Optionally, an embodiment of the present invention further provides UE, including a processor, a memory, and a computer program that is stored in the memory and that can run on the processor. When the computer program is executed by the processor, the processes of the Gap configuration method in the foregoing embodiment are implemented and a same technical effect can be achieved. To avoid repetition, details are not described herein again.

Optionally, an embodiment of the present invention further provides a network device, including a processor, a memory, and a computer program that is stored in the memory and that can run on the processor. When the computer program is executed by the processor, the processes of the Gap configuration method in the foregoing embodiment are implemented and a same technical effect can be achieved. To avoid repetition, details are not described herein again.

An embodiment of the present invention not cover by the claims further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processes of the Gap configuration method in the foregoing embodiment are implemented and a same technical effect can be achieved. To avoid repetition, details are not described herein again. The computer-readable storage medium includes a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk, an optical disc, and the like.

It should be noted that, in this specification, the terms "include", "comprise", or their any other variant is intended to cover a non-exclusive inclusion, so that a process, a method, an article, or an apparatus that includes a list of elements not only includes those elements but also includes other elements which are not expressly listed, or further includes elements inherent to such process, method, article, or apparatus. An element limited by "includes a. " does not, without more constraints, preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

Based on the descriptions of the foregoing implementations, a person skilled in the art may clearly understand that the method in the foregoing embodiment may be implemented by software in addition to a necessary universal hardware platform or by hardware only. In most circumstances, the former is a preferred implementation. Based on such an understanding, the technical solutions of the present invention essentially or the part contributing to the prior art may be implemented in a form of a software product. The computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal device (which may be mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the methods described in the embodiments of the present invention.

Claim 1:
A gap configuration method comprising:
receiving, by a first user equipment, UE, first enabling information from a network device,
wherein the first enabling information is used to indicate whether a first need configuration of a first gap is enabled, the first gap comprise one or more gaps comprising at least one of N gap types, and N is a positive integer, the first gap comprises a gap for a second UE, the first UE and the second UE are different UEs in a same terminal device, and the first UE and the second UE correspond to different subscriber identity modules, SIMs;
sending (<NUM>), by the first UE, first request information to the network device in a case that the first enabling information indicates that the first need configuration is enabled, wherein the first request information is used to request a first target gap, and a gap type of the first target gap is at least one of the N gap types; and
receiving, by the first UE, first configuration information from the network device, wherein the first configuration information is used to configure the first target gap.