Communication method, and device, chip, storage medium and program product
By acquiring indication information, terminal devices can accurately determine the connection requirements of wireless access technology types, solving the problems of high energy consumption and complex switching of user terminal devices under different network coverage, and achieving efficient network switching and improved communication performance.
Patent Information
- Application Number
- PCT/CN2024/105331
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-07-12
- Publication Date
- 2026-01-15
AI Technical Summary
In existing technologies, user terminal devices need to switch networks in a connected state when covered by networks of different wireless access technologies, resulting in high energy consumption and complex switching, which affects communication performance.
By acquiring indication information, terminal devices can accurately determine the type of wireless access technology that requires establishing a connection, avoiding frequent invalid handovers or continuous monitoring of signals from other RAT types, thereby reducing energy consumption and optimizing the network handover process.
Reduce unnecessary handovers, improve communication reliability and response speed, ensure that terminal devices are always connected to the most suitable RAT type, improve data transmission rate and service quality, and simplify the network handover process.
Smart Images

Figure CN2024105331_15012026_PF_FP_ABST
Abstract
Description
Communication methods, devices, chips, storage media and software products Technical Field
[0001] This application relates to the field of communication technology, specifically to a communication method, device, chip, storage medium, and program product. Background Technology
[0002] In existing technologies, user equipment (UE) accesses two base stations using two different Radio Access Technology (RAT) types via Dual Connectivity (DC) technology, and this can only be done when the UE is in connected mode. Therefore, under network coverage conditions of different RAT types, network handover must be performed while the UE is in connected mode. This results in higher UE power consumption and more complex network handover, thus affecting communication performance.
[0003] Summary of the Invention
[0004] This application provides a communication method, device, chip, storage medium, and program product that can reduce the power consumption of terminal devices, simplify the network switching process, and thus improve communication performance.
[0005] In a first aspect, embodiments of this application provide a communication method applied to a terminal device, the method comprising:
[0006] Obtain indication information; wherein, the indication information is used to indicate relevant information about the wireless access technology (RAT) type that has connection requirements with the terminal device.
[0007] Secondly, embodiments of this application provide a communication method applied to a first network device, the method comprising:
[0008] Send indication information to the terminal device; wherein the indication information is used to indicate relevant information about the wireless access technology (RAT) type that has a connection requirement with the terminal device.
[0009] Thirdly, embodiments of this application provide a communication device, the device comprising:
[0010] The first communication unit is configured to acquire indication information; wherein the indication information is used to indicate information related to the Radio Access Technology (RAT) type that has a connection requirement with the terminal device.
[0011] Fourthly, embodiments of this application provide a communication device, the device comprising:
[0012] The second communication unit is configured to send indication information to the terminal device; wherein the indication information is used to indicate relevant information about the wireless access technology (RAT) type that has a connection requirement with the terminal device.
[0013] Fifthly, embodiments of this application provide a communication device, the communication device comprising:
[0014] Memory is used to store executable instructions for a computer;
[0015] A processor, connected to the memory, is configured to implement the method of the first aspect or the method of the second aspect by executing the computer-executable instructions.
[0016] Sixthly, embodiments of this application provide a chip, the chip comprising:
[0017] A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method described in the first aspect, or the method described in the second aspect.
[0018] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by at least one processor, implements the method described in the first aspect, or implements the method described in the second aspect.
[0019] Eighthly, embodiments of this application provide a computer program product including computer program instructions that, when executed by a processor, implement the method described in the first aspect, or, when executed by a processor, implement the method described in the second aspect.
[0020] This application provides a communication method, terminal, network device, chip, storage medium, and product. On the terminal side, the method includes: acquiring indication information; wherein the indication information is used to indicate information related to the Radio Access Technology (RAT) type that requires connection with the terminal device. The indication information helps the terminal device accurately determine whether there is a RAT type requiring connection establishment, avoiding frequent invalid handovers or continuous listening to signals from other RAT types, thereby reducing the terminal device's power consumption. The indication information provides clear guidance, making the network handover process smoother and more efficient. After knowing the RAT type requiring connection establishment, the terminal device can quickly respond and perform a handover operation, reducing handover latency and improving service continuity and stability. By reducing unnecessary handovers and optimizing handover timing, the indication information helps improve communication reliability and response speed. Ensuring that the terminal device always connects to the most suitable RAT type can improve data transmission rate and service quality, thereby improving communication performance. Attached Figure Description
[0021] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.
[0022] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.
[0023] Figure 1 is a schematic diagram of an optional application scenario provided by an embodiment of this application;
[0024] Figure 2A is a schematic diagram of an optional LTE dual connectivity scenario provided by an embodiment of this application;
[0025] Figure 2B is a schematic diagram of an optional LTE-NR dual connectivity scenario provided by an embodiment of this application;
[0026] Figure 3 is a flowchart illustrating an optional communication method provided in an embodiment of this application;
[0027] Figure 4 is a schematic flowchart of an optional communication method provided in an embodiment of this application;
[0028] Figure 5 is a flowchart illustrating an optional communication method provided in an embodiment of this application.
[0029] Figure 6 is a schematic flowchart of an optional communication method provided in an embodiment of this application;
[0030] Figure 7 is a flowchart illustrating an optional communication method provided in an embodiment of this application;
[0031] Figure 8 is a flowchart illustrating an optional communication method provided in an embodiment of this application;
[0032] Figure 9 is a flowchart illustrating an optional communication method provided in an embodiment of this application;
[0033] Figure 10 is an interactive schematic diagram of an optional communication method provided in an embodiment of this application;
[0034] Figure 11 is a schematic diagram of an optional communication method provided in an embodiment of this application.
[0035] Figure 12 is a schematic diagram of an optional communication method provided in an embodiment of this application.
[0036] Figure 13 is a schematic diagram of an optional communication method provided in an embodiment of this application.
[0037] Figure 14 is a schematic diagram of an optional communication method provided in an embodiment of this application.
[0038] Figure 15 is a schematic diagram of an optional communication method provided in an embodiment of this application.
[0039] Figure 16 is a schematic diagram of an optional communication method provided in an embodiment of this application.
[0040] Figure 17 is a schematic diagram of the structural composition of an optional communication device provided in an embodiment of this application;
[0041] Figure 18 is a schematic diagram of the structure of an optional communication device provided in an embodiment of this application;
[0042] Figure 19 is a schematic diagram of the structural composition of an optional communication device provided in an embodiment of this application;
[0043] Figure 20 is a schematic diagram of the structural composition of an optional chip provided in an embodiment of this application;
[0044] Figure 21 is a schematic diagram of the structural composition of an optional communication system provided in an embodiment of this application. Detailed Implementation
[0045] In order to gain a more detailed understanding of the features and technical content of the embodiments of this application, the implementation of the embodiments of this application will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference and illustration only and are not intended to limit the embodiments of this application.
[0046] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.
[0047] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.
[0048] It should also be noted that the terms "first, second, and third" used in the embodiments of this application are only used to distinguish similar objects and do not represent a specific order of objects. It is understood that "first, second, and third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.
[0049] Figure 1 is a schematic diagram of an optional application scenario provided by an embodiment of this application.
[0050] As shown in Figure 1, the communication system 100 may include a terminal device 110 (also called a terminal) and a network device (NW) 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.
[0051] It should be understood that the embodiments of this application are only illustrated by way of example with communication system 100, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication systems, etc.
[0052] In the communication system 100 shown in Figure 1, the network device 120 can be an access network device that communicates with the terminal device 110. The access network device can provide communication coverage for a specific geographical area and can communicate with the terminal device 110 located within that coverage area.
[0053] In some embodiments, the network device may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, a Next Generation Radio Access Network (NG RAN) device, a base station (gNB) in an NR system, or a radio controller in a Cloud Radio Access Network (CRAN). Alternatively, the network device may be a macro base station, a micro base station (also known as a small station), a satellite, a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a Home Evolved Node B (or Home Node B, HNB), a Baseband Unit (BBU), an Access Point (AP), a Wireless Relay Node, a Wireless Backhaul Node, a Transmission Point (TP), or a Transmission and Reception Point (TRP) in a Wireless Fidelity (WiFi) system. This network equipment can also be used as a relay station, access point, vehicle-mounted equipment, wearable devices, hub, switch, bridge, router, or network equipment in the future evolved Public Land Mobile Network (PLMN).
[0054] In some embodiments, terminal device 110 may be any terminal device, including but not limited to terminal devices that are connected to network device 120 or other terminal devices via wired or wireless connection.
[0055] In some embodiments, terminal device 110 may refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal may be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, IoT device, satellite handheld terminal, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, or terminal device in a future evolved network, etc.
[0056] In some embodiments, the terminal device 110 can be used for device-to-device (D2D) communication.
[0057] Figure 1 illustrates an exemplary network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices, and each network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.
[0058] It should be noted that Figure 1 is merely an example illustrating the system to which this application applies. Of course, the method shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably in this application.
[0059] It should be noted that Figure 1 is merely an example illustrating the system to which this application applies. Of course, the method shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably in this application. The term "and / or" in this application is simply a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that the "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of an association relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is an association relationship between A and B. It should also be understood that the term "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an association between them, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to what is defined in a protocol. It should also be understood that in the embodiments of this application, the term "protocol" can refer to standard protocols in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems, and this application does not limit this.
[0060] It should be understood that the term "and / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Furthermore, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship.
[0061] It should also be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.
[0062] It should also be understood that the term "correspondence" mentioned in the embodiments of this application may indicate a direct or indirect correspondence between the two, or an association between the two, or a relationship of instruction and being instructed, configuration and being configured, etc.
[0063] It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as LTE protocol, NR protocol, and related protocols applied to future communication systems, and this application does not limit it.
[0064] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.
[0065] Related Technology 1:
[0066] Currently, with people's pursuit of speed, latency, high-speed mobility, and energy efficiency, as well as the diversity and complexity of services in future life, the 3GPP international standards organization has begun to develop 5G. The main application scenarios of 5G are: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC).
[0067] eMBB, still focused on providing users with multimedia content, services, and data, is experiencing rapid demand growth. However, because eMBB can be deployed in various scenarios, such as indoors, urban areas, and rural areas, its capabilities and requirements vary significantly. Therefore, generalizations are not possible; a detailed analysis based on the specific deployment scenario is essential. Typical applications of URLLC include industrial automation, power automation, remote medical operations (surgery), and traffic safety assurance. Typical characteristics of mMTC include high connection density, small data volume, latency-insensitive services, low module cost, and long module lifespan.
[0068] NR (New Radio, referring to the new radio technology in 5G wireless communication) can also be deployed independently. In a 5G network environment, to reduce air interface signaling (referring to reducing signaling overhead transmitted through the air interface (i.e., wireless channel) in wireless communication. Signaling overhead includes resource consumption such as the transmission, processing, and storage of signaling messages. Reducing air interface signaling can improve network efficiency and performance) and to quickly restore wireless connectivity and data services, a new Radio Resource Control State (RRC), namely the RRC_INACTIVE state, is defined. This state is different from the RRC_IDLE (idle state) and RRC_ACTIVE (connected state) states.
[0069] The RRC connected state (RRC_CONNECTED) is suitable for applications requiring real-time communication. In this state, the device maintains a connection with the network and can initiate or receive data transmissions at any time. The IDLE state (RRC_IDLE) is suitable for applications that do not require real-time communication. The INACTIVE state (RRC_INACTIVE) falls between the two, maintaining a connection while reducing power consumption and latency, making it suitable for low-power and low-latency applications.
[0070] Specifically, RRC_IDLE: Mobility is based on User Equipment (UE) cell selection and reselection; paging is initiated by the Core Network (CN), and the paging area is configured by the CN. There is no UE AS context on the base station side, and no RRC connection exists. RRC_CONNECTED: An RRC connection exists; the base station and UE have a UE AS context. The network side knows the UE's location at the cell level. Mobility is network-controlled; unicast data can be transmitted between the UE and the base station. RRC_INACTIVE: Mobility is based on UE cell selection and reselection; a CN-NR connection exists; the UE AS context exists on a specific base station; paging is triggered by the Radio Access Network (RAN); the RAN-based paging area is managed by the RAN; the network side knows the UE's location at the RAN-based paging area level.
[0071] Related Technology 2:
[0072] Paging mechanisms in NR (New Radio) systems primarily have three application scenarios: paging initiated by the core network, paging initiated by the gNB (gNodeB, next-generation base station), and system message update notifications initiated by the gNB. Core network-initiated paging and mobility management at the NAS (Non-Access Stratum, primarily responsible for handling basic functions related to mobile terminal (UE) control and management) layer in RRC_IDLE state are complementary processes; the paging range is the tracking area (TA) currently registered by the UE. The defined tracking area represents a trade-off between paging load and location update frequency. This is because a larger tracking area results in fewer location updates, but a greater system paging load. Core network-initiated paging is typically only for UEs in RRC_IDLE state. UEs in RRC_INACTIVE state will receive gNB-initiated paging. This is because in RRC_INACTIVE state, NR introduces a concept similar to the tracking area, namely the RAN Notification Area (RNA). A UE in the RRC_INACTIVE state only needs to inform the network of a new RNA through the notification area update procedure (RNA Update) when moving across RNAs. When new downlink data or signaling (such as NAS signaling) needs to be sent to the UE, a paging procedure is triggered by the gNB. This paging procedure is initiated by the anchor gNB of the UE in the RRC_INACTIVE state, i.e., the gNB that made the UE enter the INACTIVE state through the RRC Release (RRC release) message. Since a cell under an RNA may cover multiple gNBs, paging initiated by the gNB also needs to be forwarded through the Xn interface (the Xn interface is the internal radio access network interface used in 5G networks to connect different base stations (gNBs or ng-eNBs)).
[0073] These two paging mechanisms are not entirely independent. The core network can provide auxiliary information to the gNB to determine the RNA size. Furthermore, paging initiated by the core network is a fallback scheme for paging initiated by the gNB. If the gNB does not receive a paging response from the UE after initiating a paging, it assumes that the UE and the network have lost synchronization at the RNA level, and therefore notifies the core network. The core network will then trigger a paging process within the TA (Timing Advance) range. If the UE receives a paging message from the core network while in RRC_INACTIVE state, it will first enter the RRC_IDLE state before responding to the paging message. Paging messages triggered by the core network and gNB can be distinguished by the UE identifier contained in the paging message. Paging messages containing I-RNTI (Temporary Radio Network Identifier in INACTIVE state) are gNB-triggered, while those containing NG-5G-S-TMSI (5G System Temporary Mobile Registration Number) are core network-triggered.
[0074] Terminals in the RRC_IDLE and RRC_INACTIVE states will only listen to POs associated with themselves. UEs in the RRC_CONNECTED state, however, may not necessarily associate POs with their own identifier, in order to minimize conflicts with other dedicated downlink data.
[0075] Before introducing the specific paging mechanism, it is necessary to introduce two basic concepts: paging frame (PF) and paging occasion (PO). (PO refers to the subframe number of the PDCCH (Physical Downlink Control Channel) on the paging radio frame that the terminal needs to listen for when its paging occasion arrives within each paging cycle. Specifically, PO is the subframe number of the PDCCH on the paging radio frame that the terminal needs to listen for. Within a DRX cycle, the terminal listens for one or more POs to receive the corresponding paging message. These POs can include multiple time slots (e.g., subframes or OFDM symbols), and the terminal listens for the PDCCH on these POs to determine whether the network has sent a paging message to it.) In the LTE system, the definitions of PF and PO are simple: PF is a radio frame containing a PO within a DRX cycle (the time interval between wake-up and listening for the UE in Discontinuous Reception (DRX) mode), and PO is a subframe within the PF that can send a paging message. In NR, if the PDCCH (Physical Downlink Control Channel) monitoring occasion (PMO) is defined by the paging search space in SIB1 (System Information Block 1, a system information block used to broadcast critical network and configuration information to UE or mobile equipment), then the definition of PF can remain consistent with LTE, while the definition of PO needs to be changed to include radio slots containing multiple PMOs. The number of PMOs is equal to the number of SSBs (Synchronization Signal Blocks) actually transmitted in the SSB BURST set (a set of multiple SSBs within a certain period) in this cell. When the PMO is defined by search space 0 in MIB (Master Information Block), the definition of PO can follow the new definition, but PF actually points to the reference radio frame of PO. This reference radio frame actually contains the SSB BURST. The relationship between this reference radio frame and the radio frame (and its radio slot and OFDM symbol) of the associated PO is fixed, so the UE can accurately locate the PO based on the reference radio frame. The protocol defines a formula for determining the PF, which applies to the two cases mentioned above: (SFN+PF_offset)mod T=(T div N)*(UE_ID mod N) (1)
[0076] In formula (1), SFN represents the frame number of the radio frame in which the PF is located, PF_offset represents the radio frame offset, T represents the paging period, N represents the number of PFs in the paging period, and UE_ID represents the UE identifier, which is equal to 5G-S-TMSI mod 1024.
[0077] Related Technology 2:
[0078] Regarding 4G-5G dual connectivity in the access network, Figure 2A is a schematic diagram of an optional LTE dual connectivity scenario provided by an embodiment of this application, and Figure 2B is a schematic diagram of an optional LTE-NR dual connectivity scenario provided by an embodiment of this application. As shown in Figures 2A and 2B, for early 5G deployment, in the LTE-NR dual connectivity mode, the LTE eNB (4G base station) is the master station and the gNB (5G base station) is the slave station. However, traditional LTE dual connectivity is difficult to meet this deployment mode. The main reason is that since 5G NR has a larger bandwidth, it requires the 4G base station that supports the separation of MCG (Master Cell Group controlled by MeNB, i.e., master node bearer) to have stronger processing and buffering capabilities.
[0079] Therefore, in order to avoid the bottleneck of 4G base station processing capacity, minimize the upgrade of the original 4G base stations, and reduce the cost of equipment development and network construction as much as possible, LTE-NR dual connectivity takes a different approach. It stipulates that the data can also be carried separately by the SCG (Secondary Cell Group, which refers to the secondary cell group in which the terminal device is located during random access (RACH)). That is, the downlink data stream can be transmitted directly from the 5G slave station to the mobile phone, or it can be transmitted from the 5G slave station to the 4G master station and then to the mobile phone.
[0080] In related technologies, a UE (single SIM card) can access two base stations with different RATs via DC technology, and this can only be done in connected mode (RRC_CONNECTED). However, in 6G systems, if connected-free (RRC_IDLE, RRC_INACTIVE) UEs are allowed to register simultaneously in both 5G and 6G systems, a solution needs to be found for successfully receiving paging messages from network nodes in different systems, since 5G and 6G base stations (systems) may carry / associate different types of services.
[0081] Based on this, this application provides a communication method. The main idea of this method is that a terminal device obtains indication information. The terminal device is at least camped in a cell of a first network device, which is associated with a first Radio Access Technology (RAT) type. The indication information indicates relevant information about a second RAT type. The first RAT type is different from the second RAT type, and the terminal device is at least in a disconnected state with the second network device associated with the second RAT type. The indication information helps the terminal device accurately determine when to switch to the second RAT type, avoiding frequent invalid handovers or continuous listening to signals from other RAT types, thereby reducing the terminal device's power consumption. The indication information provides clear guidance, making the network handover process smoother and more efficient. After knowing when and how to switch to the second RAT type, the terminal device can quickly respond and execute the handover operation, reducing handover latency and improving service continuity and stability. By reducing unnecessary handovers and optimizing handover timing, the indication information helps improve communication reliability and response speed. Ensuring that the terminal device always connects to the most suitable RAT type can improve data transmission rate and service quality, thereby improving communication performance and user experience.
[0082] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.
[0083] Figure 3 is a flowchart illustrating an optional communication method provided in an embodiment of this application, applied to a terminal device. As shown in Figure 3, the method may include S101:
[0084] S101. Obtain indication information; wherein, the indication information is used to indicate relevant information about the wireless access technology (RAT) type that has connection requirements with the terminal device.
[0085] In some embodiments of this application, a communication method is provided, applied to a first network device, the method comprising:
[0086] Send indication information to the terminal device; wherein the indication information is used to indicate relevant information about the RAT type of wireless access technology that has connection requirements with the terminal device.
[0087] In this application embodiment, the RAT type that has a connection requirement with the terminal device can be understood as: the network associated with the RAT searching for or finding the terminal device, and / or, downlink data or Mobile Terminated (MT) data arriving.
[0088] Specifically, on the one hand, when a RAT-type network searches for a terminal device to establish or re-establish a connection, a paging process is triggered. For example, when the network has new service requirements, it needs to find a terminal device to establish the necessary connection. On the other hand, when a RAT-type network has downlink data to send to a terminal device, it means that there is a connection requirement between the RAT-type network and the terminal device. For example, when a terminal device receives downlink data packets, it needs to establish a connection to receive these data. Furthermore, when MT data (such as telephone calls, SMS messages, etc.) arrives at a terminal device, it means that the RAT-type network needs to establish a connection with the terminal device to transmit these data.
[0089] It is understandable that by providing instructions, terminal devices can efficiently establish connections with networks of different RAT types, ensuring the timely transmission and processing of data and services.
[0090] In some embodiments of this application, the terminal device is at least camped in the cell of a first network device, the first network device is associated with a first RAT type, the second network device is associated with a second RAT type, the first RAT type and the second RAT type are different, and the terminal device is at least associated with the second network device of the second RAT type in a non-connected state.
[0091] For example, the first RAT type can be described as RAT1, and the second RAT type can be described as RAT2.
[0092] In this embodiment of the application, the terminal device obtains instruction information.
[0093] In this embodiment of the application, the instruction information may be sent from the first network device to the terminal device, or it may be sent from the core network to the terminal device through the first network device.
[0094] In this embodiment of the application, the indication information is used to indicate relevant information about the second RAT type, which is different from the first RAT type. That is, the first RAT type and the second RAT type are different wireless access technologies. For example, the first RAT type is NR (5G), while the second RAT type is sixth-generation mobile communication technology (6G).
[0095] In the embodiments of this application, the first network device is associated with a first radio access technology (RAT) type, which can be understood as: the first network device uses a first radio access technology (RAT), for example, a 5G base station (first network device) uses NR (New Radio, first RAT type). Alternatively, the first network device supports a specific radio access technology (RAT), for example, a base station supports LTE or NR. The association of the second network device with a second RAT type is similar.
[0096] In some embodiments of this application, the terminal device and the first network device are in a connected state, an idle state, or an inactive state.
[0097] In the embodiments of this application, the idle state (IDLE) and the inactive state (INACTIVE) are also referred to as the disconnected state.
[0098] In this embodiment, the terminal device is in a disconnected state with the second network device associated with the second RAT type. That is, the terminal device does not have an active connection with the second network device of the second RAT type and is in an IDLE or INACTIVE state. It should be noted that the disconnected state means that the terminal device does not maintain an active data transmission connection with the second network device, but only maintains basic network attachment and location updates.
[0099] It should be understood that indication information helps terminal devices accurately determine whether there is a need to establish a connection with the second RAT type (RAT2) (or whether downlink data associated with RAT2 has arrived), avoiding frequent invalid handovers or continuous listening to signals from other RAT types, thereby reducing the power consumption of terminal devices. Indication information provides clear guidance, making the network handover process smoother and more efficient. Knowing when and how to switch to the second RAT type, terminal devices can quickly respond and execute the handover operation, reducing handover latency and improving service continuity and stability. By reducing unnecessary handovers and optimizing handover timing, indication information helps improve communication reliability and response speed. Ensuring that terminal devices always connect to the most suitable RAT type can improve data transmission rates and service quality, thereby improving communication performance and user experience. Obtaining accurate indication information can have significant benefits in reducing terminal device power consumption, simplifying the network handover process, and improving communication performance. These advantages not only help optimize the management and operation of existing networks but also improve the overall user experience and satisfaction.
[0100] In this embodiment of the application, the instruction information includes: first instruction information, second instruction information, and third instruction information. The following explains these three types of instruction information:
[0101] 1) The first indication information includes the RAT type corresponding to the Radio Resource Control (RRC) connection.
[0102] In this embodiment of the application, the first indication information is used to inform the terminal device whether there is a need to establish a connection with the second RAT type RAT2 or whether downlink data associated with RAT2 has arrived, for example, the second RAT type is 6G.
[0103] In some embodiments of this application, the communication method further includes: receiving first paging information; the first paging information carries first indication information.
[0104] In this embodiment of the application, the first network device sends a first paging message to the terminal device.
[0105] Accordingly, the terminal device receives the first paging information sent by the first network device.
[0106] In this embodiment of the application, the first paging information carries first indication information for indicating the RAT type corresponding to the RRC connection.
[0107] In some embodiments of this application, the first instruction information includes one or more of the following:
[0108] RAT type identifier;
[0109] The identifier for the terminal device varies depending on the RAT type.
[0110] Public Land Mobile Network (PLMN) information.
[0111] In this application embodiment, the indication method of the first indication information includes three methods: RAT type identifier, terminal device identifier, and PLMN information.
[0112] For example, regarding the RAT type identifier, this field indicates the type of radio access technology used, such as 5G, 6G, etc. This allows the terminal device to know the specific RAT type corresponding to the current connection or message, enabling appropriate adjustments and configurations. Regarding the terminal device identifier, the terminal device may have different identifiers under different RAT types. This field can indicate the unique identifier of the terminal device under the current RAT, allowing the terminal device to identify the radio access technology type based on the user identifier. Regarding PLMN information, this field contains PLMN identification information. PLMN information indicates specific information about the network operator; different RATs correspond to different PLMN information, allowing the terminal device to identify the radio access technology type based on the user identifier, enabling the terminal device to identify and connect to the correct operator's network.
[0113] In this embodiment, the RAT type identifier is also called the explicit indication method, which clearly indicates in the paging message whether the RAT type used by the associated service is the first RAT type RAT1 (e.g., 5G) or the second RAT type RAT1 (e.g., 6G). This applies to new base stations (6G base stations) and new user equipment (6G user equipment). Another implementation is that if the associated RAT is the same as the currently camped RAT1, it is not necessary to indicate the RAT type in the paging message. Only when the RAT associated in the paging message is different from the current RAT1 is it necessary to explicitly indicate the associated RAT type in the paging message.
[0114] For example, Scenario 1: RAT indicates 5G, current RAT1: 5G, associated RAT: 5G, indication status: no indication required or indication required, because the associated RAT is the same as the current RAT1. Scenario 2: RAT indicates 6G, current RAT1: 5G, associated RAT: 6G, indication status: indication required, because the associated RAT is different from the current RAT1.
[0115] Understandably, when the associated RAT is the same as the current RAT1, there is no need to indicate the RAT type, reducing signaling overhead. When the associated RAT is different from the current RAT1, the associated RAT type is explicitly indicated to ensure that the terminal equipment can process it correctly. This is applicable to new 6G base stations and 6G user equipment, ensuring future network compatibility and scalability. In this way, the network can flexibly manage service requirements of different RAT types while ensuring signaling efficiency and system flexibility.
[0116] In this embodiment, the terminal device identifier and PLMN information are also referred to as implicit indication. Implicit indication distinguishes 5G and 6G paging messages using the UE ID (terminal device identifier) or PLMN. This method allows the terminal device to determine the associated service type based on different identification information. Specifically, by using the UE ID, different UE IDs are used for 5G and 6G services; or, the terminal device can distinguish the RAT type related to the service associated with the paging message (first paging information) based on the different address spaces of the UE ID. By using the PLMN, different PLMN information is indicated in the paging message to distinguish 5G and 6G services; or, based on different PLMN identifiers, the terminal device can determine the associated service type.
[0117] For example, Scenario 1: Distinguishing by UE ID: 5G service UE ID: 100000-199999, 6G service UE ID: 200000-299999, received paging message UE ID: 150000, judgment result: Based on the UE ID range, the terminal device determines that the service associated with this paging message is 5G. Scenario 2: Distinguishing by PLMN: 5G service PLMN: PLMN ID = 00101, 6G service PLMN: PLMN ID = 00202, received paging message PLMN ID: 00101, judgment result: Based on the PLMN ID, the terminal device determines that the service associated with this paging message is 5G.
[0118] Understandably, terminal devices can seamlessly distinguish between 5G and 6G services through implicit information, without the need for additional explicit indication. This differentiation via UE ID or PLMN reduces signaling overhead and improves paging message processing efficiency. It is applicable to various network and service scenarios, ensuring the flexibility and scalability of future networks. Through this implicit indication method, networks and terminal devices can efficiently process and differentiate between 5G and 6G services, ensuring communication reliability and efficiency.
[0119] In some embodiments of this application, the first paging information includes two types: CN paging and RAN paging.
[0120] In the embodiments of this application, CN Paging and RAN Paging are sent by the core network and the radio access network (base station), respectively, to notify the terminal device (UE) that there is data or event from the core network or the access network that needs to be processed.
[0121] Specifically, CN Paging (core network paging) originates from nodes in the core network, such as the MME (Mobility Management Entity) or other core network controllers, and is used to notify the UE that there is data transmission or time-sensitive events from the core network that need to be processed, such as incoming calls or SMS messages. RAN Paging (radio access network paging) originates from the RRC entity of the radio access network (base station) and is used to notify the UE that there is data or events from the access network or core network that need to be processed, such as location updates or system information changes. CN Paging is primarily sent by the core network and involves core network-level control and data transmission; it is typically used to handle important core network services and communication management. RAN Paging is sent by the base station and involves access network-level control and data transmission; it is used to optimize radio resource management and quality of service, as well as to notify the UE of specific events and service requests between the UE and the base station.
[0122] It should be understood that the two types of paging information work together in mobile communication systems to ensure that terminal devices can respond promptly to various services and events from the core network and access network, thus guaranteeing smooth and efficient communication.
[0123] In this embodiment, when the CN sends a paging message, it needs to inform the RAN (Radio Access Network) of the RAT type associated with the paging message. This indication can be explicit, i.e., directly specifying the relevant RAT type, or indicating a different RAT type from the current RAT (RAT1) when necessary. If RAN paging is generated by another RAT (i.e., different from the current RAT1), the CN needs to assist RAT1 in sending the paging message and needs to explicitly inform the RAT type of the service associated with the paging message. In this case, the CN acts as a coordinator, ensuring that the UE can correctly handle service requests from different RATs.
[0124] 2) The second indication information is used to indicate the RAT type associated with the current PDU session.
[0125] In this embodiment of the application, the second indication information is used to indicate the RAT type associated with the current PDU (Protocol Data Unit) session.
[0126] In the embodiments of this application, the RAT type associated with the current PDU session is explicitly indicated, such as 5G NR, 6G NR, LTE, etc. Specifically, a unique PDU session identifier is included to distinguish different PDU sessions.
[0127] 3) The third indication information is used to indicate the connection method between the terminal device and the second RAT type.
[0128] In this embodiment, the third indication information is used to indicate the connection method between the terminal device and the second RAT type. The connection method includes: dual-stack connection and handover connection. Dual-stack connection refers to the terminal device maintaining a connection with two RAT types simultaneously, typically a primary RAT and a secondary RAT. This method can provide higher throughput and better service continuity. Handover connection refers to the terminal device switching from one RAT type to another, disconnecting the connection with the original RAT and maintaining a connection only with the new RAT. This method is used when resources are scarce or when better coverage and signal quality are required.
[0129] For example, Scenario 1: Dual-protocol stack connection, in which the terminal device connects to both 5G and 6G networks simultaneously. Scenario 2: Connection switching, in which the terminal device switches from a 5G network to a 6G network.
[0130] Understandably, by indicating the connection method, the network can better allocate and utilize resources in a multi-RAT environment. Dual-stack connections and connection switching can provide better service continuity in different scenarios. Terminal devices and networks can dynamically select the optimal connection method based on current needs and conditions. Through third-party indication information, terminal devices and networks can efficiently manage connection methods in a multi-RAT environment, ensuring users receive the best connection experience.
[0131] Understandably, on the one hand, the instruction information helps terminal devices and the network decide when and how to switch to the second RAT type. This avoids unnecessary switching or delays, improving user experience and network efficiency. On the other hand, clear instruction information can speed up the switch to the second RAT type, thereby reducing connection or service interruption time and improving service continuity and stability. Furthermore, accurate instruction information can help the network optimize resource allocation and management, ensuring that terminal devices receive the best connection and service quality when needed. Finally, with effective instructions, end users can obtain the services they need more quickly, regardless of whether they are from the first or second RAT type network, thus improving the overall user experience and satisfaction. In summary, the role of instruction information is to optimize network resource management, improve service efficiency, and ensure a fast and seamless switch when terminal devices switch to different RAT types, thereby achieving a better user experience and network performance.
[0132] The following describes the process of network switching for terminal devices based on different types of instruction information (three types of information: first instruction information, second instruction information, and third instruction information).
[0133] Category 1, the instruction information is the first instruction information.
[0134] In this embodiment of the application, when the indication information is the first indication information, there are two cases:
[0135] Scenario 1:
[0136] In this embodiment of the application, the terminal device is in an unconnected state (IDLE / INACTIVE state) with both the first network device and the second network device.
[0137] In this embodiment of the application, as shown in FIG4, the communication method includes S201 to S204:
[0138] S201, The first network device sends the first paging information to the terminal device.
[0139] In some embodiments of this application, the terminal device receives first paging information sent by the first network device. The first paging information carries the RAT type used to indicate the RRC connection.
[0140] In this embodiment of the application, when the terminal device is camped in the cell of the first network device, it listens for paging information and receives the first paging information sent by the first network device.
[0141] S202, The terminal device performs cell reselection.
[0142] In this application embodiment, cell reselection can be described as cell(RAT)Reselection.
[0143] S203. The terminal device sends a first RRC connection request to the second network device.
[0144] S204. The second network device sends the first RRC connection information to the terminal device.
[0145] In some embodiments of this application, when the terminal device is camped on the cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type, cell reselection is triggered, and a first RRC connection request (RRC Setup REQ) or a first RRC recovery request (RRC Resume REQ) is sent to the second network device; wherein, the cell of the second network device is the cell to be reselected.
[0146] In this embodiment, the terminal device receives a first indication message indicating that a connection request or recovery request needs to be made on the second RAT type. Based on the first indication message, the terminal device initiates a cell reselection process to switch to an appropriate cell conforming to the second RAT type. Once the terminal device successfully selects a target cell of the second RAT type, it sends an RRC Setup REQ or RRC Resume REQ to the second network device. These requests are used to establish a new RRC connection or restore a previously interrupted RRC connection, ensuring that the terminal device can communicate and operate normally under the second RAT type. Through these steps, the terminal device can effectively switch between the first and second RAT types according to network requirements and the first indication message, ensuring smooth connection and communication between different network devices.
[0147] In some embodiments of this application, the terminal device receives first RRC connection information (RRC Setup) or first RRC recovery information (RRC Resume) sent by the second network device; the terminal device establishes an RRC connection with the second network device based on the first RRC connection information.
[0148] In this embodiment, after the terminal device sends an RRC Setup REQ or RRC Resume REQ to the second network device, the second network device, upon receiving these requests, will reply with the corresponding RRC Setup or RRC Resume. Accordingly, upon receiving the RRC Setup or RRC Resume from the second network device, the terminal device will perform relevant configuration and parameter settings according to the network protocol requirements based on the received information. The terminal device completes the RRC connection establishment process with the second network device based on the first RRC connection information. This includes the exchange and confirmation of various configuration messages to ensure the reliability and stability of the connection. Through these steps, the terminal device can successfully establish an RRC connection on the second network device, achieving a smooth transition from the first network device to the second network device and ensuring continuous communication services. This process helps improve network switching efficiency, reduce terminal device power consumption, simplify network management, and improve overall communication performance.
[0149] In some embodiments of this application, cell reselection is carried out in the following four ways:
[0150] Method 1: Adjust the priority of cells and / or frequencies associated with the first RAT type and use the R criterion for cell reselection.
[0151] In this embodiment of the application, the cell of the first RAT type is the currently serving cell.
[0152] For example, a terminal device receives a paging message associated with another RAT (e.g., RAT2) within the current RAT1 cell. The terminal device lowers the frequency priority of the cell associated with the current RAT1 to the lowest level, and then performs cell reselection according to the R criterion to select a cell that meets the R criterion and is associated with the RAT associated with the paging message. The R criterion typically includes signal strength thresholds (such as RSRP, RSRQ), quality of service metrics (such as SINR), and cell congestion status.
[0153] Understandably, by lowering the priority of the cell / frequency associated with the current RAT1 to the lowest level, it ensures that the terminal device prioritizes the cell of the RAT type associated with the paging message, improving network handover efficiency. Cell selection based on the R criterion can select the cell with the best signal strength and quality, improving user experience. The optimized cell reselection process reduces unnecessary handovers and signal searches, thereby reducing the power consumption of the terminal device. The network can dynamically adjust priorities according to service needs, flexibly adapting to different communication scenarios and requirements. Through the above steps and explanations, it can be ensured that when the terminal device receives paging messages associated with other RATs, it can prioritize the best cell for handover or connection, thereby improving overall communication performance and user experience.
[0154] Method 2: Adjust the priority of cells and / or frequencies associated with the second RAT type and use the R criterion for cell reselection.
[0155] In this embodiment, a terminal device receives a paging message associated with another RAT (e.g., RAT2) within the current RAT1 cell. The terminal device increases the priority of the cell or frequency of the RAT (e.g., RAT2) associated with the paging message, making its priority higher than that of the current RAT1 cell or frequency. The terminal device evaluates all available cells based on the adjusted priority and R criteria. R criteria typically include signal strength (e.g., RSRP, RSRQ), quality of service (e.g., SINR), cell load, etc. The terminal device selects a cell that meets the criteria and has a higher priority based on the priority and R criteria; or, it prioritizes the cell of the RAT (e.g., RAT2) associated with the paging message with a higher priority. The terminal device initiates an RRC Setup Request or RRC Resume Request on the selected cell. The Cause value in this connection request indicates that this connection is in response to a paging message associated with another RAT.
[0156] Understandably, adjusting priorities allows terminal devices to connect to cells with better signal quality and service, optimizing network resource utilization. By selecting cells that meet the R criterion and have higher priority, terminal devices can obtain better signal and service quality. Reasonable priority adjustment and execution of the R criterion calculation avoid unnecessary cell handovers and reduce terminal device power consumption. The optimized cell reselection process improves connection stability and communication performance of terminal devices, enhancing user experience.
[0157] Method 3: Perform cell reselection based on all neighboring cells associated with the second RAT type.
[0158] In this embodiment, a terminal device receives a paging message in the current RAT1 cell, indicating a service associated with another RAT (RAT2). The terminal device does not perform frequency priority adjustment and immediately triggers cell reselection upon receiving the paging message associated with RAT2. The terminal device only considers neighboring cells of RAT2 associated with the paging message. These neighboring cells are evaluated using signal quality metrics (e.g., RSRP, RSRQ, SINR). Among the evaluated neighboring cells associated with RAT2, the cell with the strongest signal quality is selected for reselection. The terminal device initiates an RRC connection establishment request or an RRC recovery request on the selected cell. The Cause value in the connection request indicates that this connection is in response to a paging message associated with another RAT.
[0159] Understandably, triggering cell reselection directly without adjusting frequency priority simplifies the process. By selecting the cell with the strongest signal quality, it ensures the terminal device receives optimal signal and service quality. Immediate cell reselection improves the terminal device's response speed to paging messages. Performing cell reselection only when necessary avoids frequent network handovers and reduces the terminal device's power consumption. In summary, when receiving paging messages associated with other RATs, the terminal device can quickly and effectively perform cell reselection, ensuring connection to the cell with the best signal quality, thereby improving overall communication performance.
[0160] Method 4: Cell reselection is performed using the R criterion based on one or more preset parameter configurations; wherein, one or more parameter configurations are configured by the first network device; one or more parameter configurations correspond to different RAT types.
[0161] In this embodiment, a terminal device receives a paging message in the current RAT1 cell, indicating a service associated with another RAT (RAT2). After receiving the paging message associated with RAT2, the terminal device triggers cell reselection based on preset parameter configurations corresponding to RAT2. The network device (e.g., the base station of RAT1) configures one or more parameters separately for cell reselection triggered by the paging message. It should be noted that not only does the network device configure different parameter configurations based on the terminal device's state (via dedicated RRC information), but the network can also configure multiple sets of parameter configurations in the System Information Block (SIB), with the UE deciding which set to use based on the paging received. These parameters may include, but are not limited to: Priority: the priority of cells or frequencies in different RATs; Thresholds: such as threshold values for RSRP (Reference Signal Received Power) or RSRQ (Reference Signal Received Quality). After receiving the paging message, the terminal device performs cell reselection based on the parameters separately configured by the network for this situation. These configurations ensure that the terminal device selects the best cell under appropriate conditions.
[0162] In this embodiment, the network device (first network device RAT1) pre-configures one or more parameters for cell reselection of different RATs according to specific needs. These configuration parameters are stored in the network device and are ready to be sent to the terminal device when needed. Additionally, the network device can dynamically adjust the cell reselection parameter configuration based on real-time network conditions and service requirements. Alternatively, the network can configure multiple sets of parameter configurations in the SIB, and the UE decides which set to use based on the paging information it receives, ensuring that the terminal device always uses the most suitable parameters for cell reselection.
[0163] Understandably, on the one hand, by configuring separate parameters for cell reselection triggered by receiving paging messages, the network can guide terminal devices to perform cell reselection more flexibly and accurately. Terminal devices can use the most appropriate parameters for cell reselection based on real-time network conditions and specific paging requirements, thus selecting the best cell. On the other hand, separate priority and threshold configurations ensure that terminal devices find the best cell with as few handovers as possible, thereby reducing energy consumption. Terminal devices use optimized parameters for cell reselection under specific circumstances, avoiding unnecessary frequent reselections. On the other hand, preset separate configurations simplify the decision-making process of terminal devices, enabling them to respond to paging messages and complete cell reselection more quickly. After receiving a paging message, terminal devices can quickly perform cell reselection based on separately configured parameters, reducing the complexity that may be encountered during handover. On the other hand, through optimized cell reselection parameters, terminal devices can select the cell with the best signal quality, thereby improving overall communication performance. The optimized cell reselection process ensures that terminal devices can respond to service needs in a timely manner, improving user experience.
[0164] It should be noted that the above four cell reselection methods can be combined arbitrarily, and this application embodiment does not impose any limitations on this.
[0165] In some embodiments of this application, the communication method further includes:
[0166] When the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the first RAT type, a second RRC connection request is sent to the first network device so that the terminal device can establish an RRC connection with the first network device.
[0167] In this embodiment, the terminal device is currently camped in the cell of the first network device, and receives first indication information from the first network device. This information contains RAT type identical to the current first RAT type, indicating that the terminal device should continue using the current RAT for communication. Based on the content of the first indication information, the terminal device decides to continue communicating with the current network device and therefore sends a second RRC connection request. This request can be an RRC Setup Request or an RRC Resume Request, depending on the current state of the terminal device (e.g., whether an RRC connection needs to be re-established). After receiving the second RRC connection request from the terminal device, the first network device processes the request and establishes an RRC connection with the terminal device. Once the RRC connection is established, the terminal device can effectively communicate with the network device, including data transmission and control signaling.
[0168] In some embodiments of this application, the communication method further includes:
[0169] In a cell where the terminal device is camped on at least the first network device and the second network device, according to the first method, it is determined that the first paging information is being listened to in the cell of the first network device or the second network device.
[0170] In this embodiment, the terminal device is currently camped in at least the cells of the first network device and the second network device, and is able to receive signals from both network devices. The terminal device determines which network device's cell to listen for the first paging information according to one or more predefined methods.
[0171] In some embodiments of this application, the first approach includes one or more of the following:
[0172] Predefined configuration methods;
[0173] Implementation based on terminal devices;
[0174] Determined based on the monitoring cycles of at least two neighboring cells;
[0175] Network configuration.
[0176] In this embodiment, a predefined configuration method is used, where the terminal device listens in specific cells according to a pre-configured network policy. This configuration method can be set by the network operator according to different application scenarios and requirements. In this method, the network device pre-defines the terminal device's listening policy. For example, the network operator can set rules to allow the terminal device to prioritize listening in cells with better signal strength.
[0177] In this embodiment, the implementation of the terminal device and its internal implementation will also affect its monitoring selection. Different devices may employ different strategies to select the cell to monitor based on differences in hardware and software design. Different terminal devices may have different monitoring strategies in their design. For example, some high-performance terminal devices may monitor the signals of multiple cells simultaneously, while some low-power devices may select the cell with the strongest signal to monitor in order to save energy.
[0178] In this embodiment, the terminal device determines which cell to monitor based on the monitoring periods of at least two neighboring cells. For example, the terminal device can select a cell with a shorter monitoring period to improve response speed and connection reliability. Specifically, the terminal device can select the cell to monitor based on the monitoring periods of neighboring cells. For example, if the monitoring periods of two neighboring cells are different, the terminal device can select the cell with the shorter monitoring period to improve connection reliability and response speed.
[0179] In this embodiment of the application, the network device can dynamically configure the listening policy of the terminal device. For example, the network device can instruct the terminal device to listen in a specific cell based on the current network load and service requirements. Specifically, the network device can dynamically adjust the listening policy of the terminal device according to the actual situation. For example, the network device can instruct the terminal device to switch to a less loaded cell for listening based on the current network load, in order to balance the network load.
[0180] Understandably, through predefined configuration methods and dynamic network configuration, terminal devices can listen in the most suitable cell, thereby improving listening efficiency and connection reliability. Dynamic configuration of network devices allows for optimization of the terminal device's listening strategy based on actual conditions, thus optimizing network resource utilization and improving overall network performance. By selecting appropriate cells for listening, terminal devices can reduce connection interruptions caused by signal instability, thereby improving connection stability and user experience. Through the first method, terminal devices can listen in the most suitable cell, thereby improving listening efficiency, reducing energy consumption, optimizing network resource utilization, and enhancing connection stability.
[0181] Scenario 2:
[0182] In this embodiment of the application, the terminal device is in an unconnected state (IDLE / INACTIVE state) with both the first network device and the second network device.
[0183] In this embodiment of the application, as shown in FIG5, the communication method includes S301 to S306:
[0184] S301, The first network device sends the first paging information to the terminal device.
[0185] In this embodiment of the application, the description of the first paging information can be referred to the description of S101 above, and will not be repeated here.
[0186] In some embodiments of this application, the terminal device receives first paging information sent by the first network device. The first paging information carries the RAT type used to indicate the RRC connection.
[0187] In this embodiment of the application, when the terminal device is camped in the cell of the first network device, it listens for paging information and receives the first paging information sent by the first network device.
[0188] S302, The terminal device sends a third RRC connection request to the first network device.
[0189] In some embodiments of this application, when the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type, the terminal device sends a third RRC connection request to the first network device.
[0190] Accordingly, the first network device receives the third RRC connection request sent by the terminal device.
[0191] In this embodiment of the application, the third RRC connection request can be described as an RRC Setup REQ.
[0192] S303, The first network device sends a first handover request to the second network device.
[0193] In this embodiment of the application, the first handover request can be described as a HO REQ (HandOver Request).
[0194] S304. The second network device sends the first handover information to the first network device.
[0195] In this embodiment of the application, the first switching information can be described as HO RES (HandOver Response).
[0196] S305. The first network device sends the second RRC connection information to the terminal device.
[0197] Accordingly, the terminal device obtains the second RRC connection information sent by the first network device. The second RRC connection information includes: handover configuration information related to the second network device.
[0198] In the embodiments of this application, the second RRC connection information can be described as RRC Setup.
[0199] S306. The terminal device sends the first RRC reconfiguration completion information to the second network device.
[0200] In this embodiment of the application, the first RRC reconfiguration completion information can be described as RRC Reconfig Complete.
[0201] In this embodiment, a first network device (RAT1) sends a paging message to a terminal device residing in its cell, notifying the terminal device of an event or data from the core network or RAN that needs processing. Upon receiving the paging message, the terminal device sends a third RRC setup request to the first network device, requesting the establishment of an RRC connection to handle the paging event. After receiving the RRC setup request from the terminal device, the first network device, based on the terminal device's measurement report and service requirements, sends a handover request (HO REQ) to the second network device (RAT2), requesting the handover of the terminal device to the second network. Upon receiving the handover request from the first network device, the second network device evaluates the request and sends a handover response (HO RES) to the first network device, confirming the handover request and providing necessary handover parameters. Upon receiving the handover response from the second network device, the first network device sends a second RRC setup message to the terminal device, instructing the terminal device to perform a handover operation and providing handover parameters and target cell information. Based on the instructions of the first network device, the terminal device sends an RRC reconfiguration complete message to the second network device, confirming the handover operation and establishing an RRC connection.
[0202] Understandably, a well-designed handover and connection control process ensures that terminal devices can respond quickly to network changes, improving communication efficiency. Optimizing paging and handover processes reduces unnecessary network scanning and connection attempts, lowering terminal device power consumption. Dynamically adjusting and optimizing handover between RATs improves network resource utilization and user experience.
[0203] In some embodiments of this application, the third RRC connection request includes: a cause value, which includes information indicating the RAT type associated with the first paging information, and a measurement report, which includes measurement results from one or more neighboring cells of a second RAT type.
[0204] In this embodiment, the cause value indicates the reason why the terminal device requests an RRC connection. It includes information indicating the RAT type associated with the first paging information, which helps the network device understand the specific background and requirements of the connection request. The measurement report is the result of the terminal device's measurement of the signal strength and quality of neighboring cells. This report includes measurement results of one or more neighboring cells of a second RAT type, providing a reference for the network device's handover decision. Specifically, the cause value indicates the reason why the terminal device requests a connection, including the associated RAT type (e.g., 5G, 4G, etc.). This is to let the network device know the current RAT environment of the terminal device and process it according to the specific RAT type. The measurement report includes the signal strength and quality of neighboring cells of the second RAT type (e.g., 5G, 6G) measured by the terminal device. These measurement results are used to evaluate the situation of candidate cells in order to make a handover decision. For example, the measurement results include: the signal strength of each neighboring cell, the signal quality of each neighboring cell, and the cell identifier.
[0205] Understandably, the reason value includes RAT type information, enabling network devices to more accurately identify and process connection requests. The measurement report provides detailed measurement results from neighboring cells, giving network devices sufficient information to make more reliable handover decisions. By including specific RAT type information and measurement reports in the third RRC connection request, network devices can more accurately assess the rationale for handover requests, reduce unnecessary connection attempts, and improve communication efficiency.
[0206] Scenario 3:
[0207] In this embodiment of the application, the terminal device is in an unconnected state (IDLE / INACTIVE state) with both the first network device and the second network device.
[0208] In this embodiment of the application, as shown in FIG6, the communication method includes S401 to S408:
[0209] S401. The first network device sends the first paging information to the terminal device.
[0210] In this embodiment of the application, the description of the first paging information can be referred to the description of S101 above, and will not be repeated here.
[0211] In some embodiments of this application, the terminal device receives first paging information sent by the first network device. The first paging information carries the RAT type used to indicate the RRC connection.
[0212] In this embodiment of the application, when the terminal device is camped in the cell of the first network device, it listens for paging information and receives the first paging information sent by the first network device.
[0213] S402, The terminal device sends a third RRC connection request to the first network device.
[0214] In some embodiments of this application, when the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type, the terminal device sends a third RRC connection request to the first network device.
[0215] Accordingly, the first network device receives the third RRC connection request sent by the terminal device.
[0216] In this embodiment of the application, the third RRC connection request can be described as an RRC Setup REQ.
[0217] S403, The first network device sends the third RRC connection information to the terminal device.
[0218] Accordingly, the terminal device receives the third RRC connection information sent by the first network device.
[0219] In this embodiment of the application, the third RRC connection information can be described as RRC Setup.
[0220] S404. The terminal device sends the first RRC connection completion information to the first network device.
[0221] Accordingly, the first network device receives the first RRC connection completion information sent by the terminal device.
[0222] In this embodiment of the application, the first RRC connection completion information can be described as RRC Setup Complete.
[0223] In some embodiments of this application, in response to the third RRC connection information sent by the first network device in response to the third RRC connection request, a first RRC connection completion information is sent to the first network device; wherein, the first RRC connection completion information includes: information indicating the RAT type associated with the first paging information and a measurement report.
[0224] In this embodiment, the first RRC connection completion information includes at least two types of information. One type is information indicating the RAT type associated with the first paging information. This information is used to inform the first network device of the RAT type associated with the first paging information (e.g., 4G, 5G, etc.), which is crucial for the first network device to correctly identify and process the background information of the connection when processing the connection completion information. The other type is a measurement report, which is the measurement result of the terminal device on the signal strength and quality of neighboring cells. This includes the measurement results of one or more neighboring cells of the second RAT type (e.g., signal strength, signal quality, cell identifier, etc.), which is provided to the first network device for further handover decisions and resource optimization.
[0225] Specifically, after receiving the first paging information, the terminal device executes the corresponding RRC connection establishment process. After the RRC connection is established, the terminal device generates first RRC connection completion information, which includes information indicating the RAT type associated with the first paging information and a measurement report. The first network device receives the first RRC connection completion information sent by the terminal device and, based on the RAT type information and measurement report in the first RRC connection completion information, makes network optimization and handover decisions.
[0226] S405, The first network device sends a first handover request to the second network device.
[0227] Accordingly, the second network device receives the first handover request sent by the first network device.
[0228] In this embodiment of the application, the first switching request can be described as a HO REQ.
[0229] S406, The second network device sends the first handover information to the first network device.
[0230] Accordingly, the first network device receives the first handover information sent by the second network device.
[0231] In this embodiment of the application, the first switching information can be described as HO RES.
[0232] S407. The first network device sends a first handover command to the terminal device.
[0233] Accordingly, the terminal device receives the first handover instruction sent by the first network device.
[0234] In this embodiment of the application, the first switching instruction can be described as a HO Command.
[0235] S408. The terminal device sends the first RRC reconfiguration completion information to the second network device.
[0236] Accordingly, the second network device receives the first RRC reconfiguration completion information sent by the terminal device.
[0237] In this embodiment of the application, the first RRC reconfiguration completion information can be described as RRC Reconfig Complete.
[0238] In this embodiment, a first network device sends a first paging message (carrying first indication information indicating the RAT type of the RRC connection) to a terminal device via a paging channel to notify the terminal device that data or events from the network need to be processed. After receiving the first paging message, the terminal device sends a third RRC connection request to the first network device, indicating a desire to establish an RRC connection to process the paging event. Upon receiving the third RRC connection request, the first network device sends third RRC connection information to the terminal device to establish the RRC connection. After receiving the third RRC connection information, the terminal device completes the RRC connection and sends first RRC connection completion information to the first network device. This information includes an indication of the RAT type associated with the first paging message and a measurement report. Based on the content of the first RRC connection completion information, the first network device determines that a handover operation is required (by determining the second network device based on the measurement report and RAT type) and sends a first handover request (HO REQ) to the second network device, requesting a handover to the second network device. Upon receiving the first handover request, the second network device processes the request and sends first handover information (HO RES) to the first network device, confirming the handover operation. After receiving the handover confirmation information from the second network device, the first network device sends a first handover command to the terminal device, instructing the terminal device to perform the handover operation. The terminal device completes the handover operation according to the first handover command and sends a first RRC reconfiguration completion message to the second network device, confirming the completion of the RRC connection reconfiguration.
[0239] Understandably, the above process ensures that terminal devices can quickly switch to the target network (RAT2), improving the efficiency of network resource utilization. Furthermore, it reduces latency and interruptions during the handover process, guaranteeing continuity and connection stability for users while on the move, thus improving user experience. Additionally, it reduces the complex operations required by terminal devices during handover, thereby lowering power consumption and increasing battery life.
[0240] Scenario 4:
[0241] In this embodiment of the application, the terminal device is in a connected state with the first network device and the second network device is in a disconnected state (IDLE / INACTIVE state).
[0242] In this embodiment of the application, as shown in FIG7, the communication method includes S501 to S505:
[0243] S501. The first network device sends RRC dedicated information to the terminal device, wherein the RRC dedicated information carries first indication information.
[0244] Accordingly, the terminal device receives the RRC-specific information sent by the first network device.
[0245] In this embodiment of the application, RRC-specific information can be described as Paging via dedicated RRC.
[0246] In this embodiment of the application, the first network device sends RRC-specific information to the terminal device. This information is transmitted through a dedicated RRC channel to ensure the security and integrity of the information.
[0247] Understandably, RRC-specific information is transmitted through a dedicated channel, ensuring the reliability and security of information transmission and reducing the risk of information loss or mistransmission.
[0248] S502, The terminal device determines whether to establish a connection with the network associated with the second RAT type.
[0249] In this application embodiment, determining whether to establish a connection with a network associated with the second RAT type can be described as: Maintain or Switch or Simultanously Tx / Rx at both sides.
[0250] In some embodiments of this application, when the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type, it is determined whether the terminal device should establish a connection with the network associated with the second RAT type based on the terminal capabilities and / or current service requirements.
[0251] In this embodiment of the application, S502 includes the following two levels:
[0252] Level 1: Does the UE support dual stack connections? This capability determines whether the UE performs a handover HO, connects to both sides (dual stack connection), or remains under the current RAT connection.
[0253] In this application embodiment, whether the terminal device supports dual protocol stack connection is a key factor that determines whether the terminal device switches, uses dual protocol stack connection, or remains under the current RAT connection in the above scenario.
[0254] In this embodiment, if the terminal device supports dual-protocol stack connectivity, it means that it can maintain connections to two different RAT types (e.g., 5G and 6G) simultaneously. This capability allows the terminal device to maintain connections with two different network devices simultaneously when needed, thereby achieving more flexible and stable network switching and connection maintenance.
[0255] For example, if it is determined that the terminal device uses a dual-protocol stack connection, the terminal device can choose to maintain connections with both the first and second network devices simultaneously, without completely severing its connection with one network. This approach improves the reliability and continuity of communication.
[0256] In this embodiment, if the terminal device does not support dual-protocol stack connections, when switching to another RAT type, the current connection needs to be disconnected first, and then a new connection needs to be established. For example, after receiving a switching instruction, the terminal device will disconnect the current RAT connection and establish a connection with the target RAT according to a pre-set switching procedure. During this process, the terminal device needs to re-establish the RRC connection.
[0257] In some cases, based on current service requirements and network policies, terminal devices may choose to remain under the current RAT connection without switching or switching to a dual-protocol stack connection. For example, if the network performance and coverage of the current RAT meet the service requirements, the terminal device may choose to continue to remain under the current RAT connection.
[0258] Understandably, terminal devices can flexibly choose whether to switch, use dual-protocol stack connections, or retain the current connection based on current business needs and network environment, thereby improving the efficiency of network resource utilization and user experience.
[0259] In the case of dual protocol stack connection in Level 1, the UE's transmit and receive capabilities are limited, which means that the UE can only transmit and receive on one side in the time domain. Therefore, it is necessary to indicate to the network which side to transmit and receive during which time period.
[0260] In this embodiment of the application, the terminal device may send the handover time and / or handover period to the first network device.
[0261] In this embodiment, the handover time includes: handover start time and / or handover end time. The handover start time indicates when the handover process begins, allowing network devices to coordinate resources and timing. The handover end time indicates when the handover process is expected to complete, ensuring a sufficient handover time window.
[0262] In this embodiment, the handover period includes: handover period length and / or handover start position. The handover period length indicates the total time required for the entire handover process, facilitating the rational allocation of network resources and the smooth execution of the handover operation. The handover start position indicates the starting point of the handover period, ensuring that the handover process occurs within the predetermined time and location.
[0263] Understandably, clearly defined time slot allocations allow terminal devices to efficiently utilize their limited transmission and reception capabilities, while dynamically adjusting these allocations can optimize overall network performance and improve service quality. In this way, terminal devices and the network can effectively collaborate to ensure efficient and stable communication even when transmission and reception capabilities are limited.
[0264] In this embodiment, the terminal device first evaluates its hardware and software capabilities, including whether it supports multiple RAT connections and single Tx / Rx (can only operate under one network at a time). That is, it determines whether the terminal device can connect to multiple networks simultaneously or can only operate under one network. Further, the terminal device evaluates whether it needs to establish a network connection associated with the second RAT type based on factors such as the currently running service type, service priority, and network congestion. Based on service needs and priorities (e.g., urgent tasks, important data transmission), it determines whether it needs to switch to or simultaneously connect to the network of the second RAT type.
[0265] For example, if the terminal device only supports a single Tx / Rx and the current network service has a higher priority, the terminal device may choose to continue operating under the current RAT type. If the terminal device supports multiple RAT connections and the service of the second RAT type has a higher priority, the terminal device may choose to establish a connection with the network associated with the second RAT type.
[0266] In some embodiments of this application, determining whether a terminal device establishes a connection with a network associated with a second RAT type is made based on terminal capabilities and / or current service requirements, including one or more of the following:
[0267] If the terminal capability supports a single RAT connection, and the priority of the second RAT type is lower than that of the first RAT type, then it is determined that the terminal device maintains the connection with the network associated with the first RAT type.
[0268] If the terminal capability supports a single RAT connection, and the priority of the second RAT type is higher than that of the first RAT type, then the terminal device is determined to establish a connection with the network associated with the second RAT type.
[0269] When the UE capability supports multiple RAT connections, it is determined that the terminal device establishes a connection with the network associated with the second RAT type, or the terminal device establishes a connection with the network associated with both the first and second network devices simultaneously.
[0270] For example, in scenario 1: Multiple RAT support, if the terminal device supports simultaneous connection to both 4G and 5G networks, when high-priority services require it (such as HD video calls), the terminal device can choose to connect to both networks simultaneously to ensure service continuity and high quality. Scenario 2: Single RAT support, if the terminal device supports a single RAT connection, and the current 4G network service has a higher priority, the terminal device may choose to continue operating on the 4G network without switching to the 5G network to ensure the stability of the current service.
[0271] Understandably, dynamically adjusting connection strategies based on terminal capabilities and business needs can effectively utilize network resources, reduce unnecessary connections and handovers, and optimize network performance. Selecting connections based on service priority ensures that high-priority services are processed first, improving user experience and service quality. Intelligent selection based on terminal capabilities and current needs avoids frequent network handovers and connection recovery, saving terminal device power and extending battery life.
[0272] S503. If it is determined that the terminal device has established a connection with the network associated with the second RAT type, the terminal device sends a first handover instruction to the first network device.
[0273] Accordingly, the first network device receives the first handover instruction sent by the terminal device.
[0274] In some embodiments of this application, the first handover indication includes: connection mode and / or network measurement information associated with the second RAT type. Connection mode includes: dual-stack connection and / or switched connection.
[0275] In this application embodiment, the first switching indication can be described as a Switch Indication.
[0276] Dual-stack connectivity refers to the ability of a terminal device to connect to two different RAT types simultaneously (e.g., 4G and 5G). Switching connectivity refers to the ability of a terminal device to switch from one RAT type to another (e.g., from 4G to 5G) to achieve a single-connectivity mode.
[0277] For layer 2 in S502, in some embodiments of this application, when the terminal device establishes a connection with the network associated with the first network device and the second network device at the same time, the transmitter and / or receiver are switched between the networks associated with the first network device and the second network device in a time-division multiplexing (TDM) manner. The switching of the transmitter and / or receiver in a TDM manner is related to the user's capabilities and / or service characteristics.
[0278] In this embodiment of the application, the relevant information of the second network device includes: the cell identifier of the second network device (including cell ID, frequency band, frequency and other information), and / or the identifier of the second network device (including base station ID or other unique identifier).
[0279] In this embodiment, the handover time includes: handover start time and / or handover end time. The handover start time indicates when the handover process begins, allowing network devices to coordinate resources and timing. The handover end time indicates when the handover process is expected to complete, ensuring a sufficient handover time window.
[0280] In this embodiment, the handover period includes: handover period length and / or handover start position. The handover period length indicates the total time required for the entire handover process, facilitating the rational allocation of network resources and the smooth execution of the handover operation. The handover start position indicates the starting point of the handover period, ensuring that the handover process occurs within the predetermined time and location.
[0281] Understandably, by providing advance notice of handover times and cycles, network devices can better coordinate resources, avoid resource conflicts and waste, and improve the overall network resource utilization. Furthermore, accurate and timely handover instructions reduce latency and interruptions during the handover process, improving user communication experience and service continuity.
[0282] S504, The first network device sends a second handover request to the second network device.
[0283] Accordingly, the second network device receives the second handover request sent by the first network device.
[0284] In this embodiment of the application, the second switching request can be described as a HO REQ.
[0285] S505, the second network device sends a second handover message to the first network device.
[0286] Accordingly, the first network device receives the second handover information sent by the second network device.
[0287] In this embodiment of the application, the second switching information can be described as HO RES.
[0288] S506, The first network device sends a second handover command to the terminal device.
[0289] Accordingly, the terminal device receives the second handover command sent by the first network device.
[0290] In this embodiment of the application, the second switching instruction can be described as a HO Command.
[0291] In this embodiment of the application, the second handover instruction includes handover configuration information related to the second network device.
[0292] In some embodiments of this application, the terminal device responds to a second handover command by switching from the first network device to the second network device, or by establishing a connection with both the first and second network devices simultaneously.
[0293] S507. The terminal device sends an RRC connection request to the second network device.
[0294] Accordingly, the second network device receives the RRC connection request sent by the terminal device.
[0295] In this embodiment of the application, the RRC connection request can be described as an RRC Setup REQ.
[0296] S508, the second network device sends RRC connection information to the terminal device.
[0297] Accordingly, the terminal device receives the RRC connection information sent by the second network device.
[0298] In this embodiment of the application, RRC connection information can be described as RRC Setup.
[0299] In some embodiments of this application, when a terminal device establishes connections with the networks associated with both the first and second network devices simultaneously, a connection switch is performed between the networks associated with the first and second network devices respectively.
[0300] In this embodiment of the application, the terminal device switches between the networks associated with the first network device and the second network device based on information such as current service requirements, network conditions, or terminal device status.
[0301] In some embodiments of this application, when it is determined that the terminal device has established a connection with a network associated with the second RAT type, a connection is established with the second network device, and the connection with the second network device is either cut off or not switched.
[0302] In this embodiment, a first network device sends RRC information containing specific information (first indication information) to a terminal device. This information (first indication information) indicates the RAT type associated with the terminal device's RRC connection, such as switching to a network of a different RAT type. Based on the received first indication information, the terminal device determines whether it needs to establish a connection with a network of a second RAT type (e.g., 5G or 6G). If it determines that the terminal device needs to establish a connection with a network associated with a second RAT type, the terminal device sends a handover indication to the current first network device, informing it that it needs to switch to a network of the second RAT type. After receiving the handover indication from the terminal device, the first network device sends a handover request to the second network device, requesting the second network device to prepare to receive the terminal device. The second network device confirms that it can receive the handover request and sends handover information to the first network device, including the resources and configuration required for the handover. Based on the feedback from the second network device, the first network device sends a handover command to the terminal device, instructing it to begin the handover operation. The terminal device executes the handover operation and sends an RRC connection request to the second network device, beginning the establishment of an RRC connection with the second network device. After receiving the connection request from the terminal device, the second network device sends RRC connection information to the terminal device, completing the RRC connection establishment process.
[0303] Understandably, the above steps ensure that terminal devices can efficiently switch networks according to business needs and network conditions, thereby improving communication performance and user experience.
[0304] Category 2, the instruction information is the second instruction information.
[0305] In this embodiment of the application, the terminal device is in an unconnected state (IDLE / INACTIVE state) with both the first network device and the second network device.
[0306] In this embodiment of the application, as shown in FIG8, the communication method includes S601 to S604:
[0307] S601, The first network device sends a second paging message to the terminal device.
[0308] In this embodiment of the application, the second paging information does not need to indicate the RAT type associated with the RRC connection.
[0309] S602. The terminal device establishes an RRC connection with the first network device.
[0310] S603, the core network sends the second instruction information to the terminal device through the first network device.
[0311] In some embodiments of this application, the second indication information is used to indicate the RAT type associated with the current PDU session.
[0312] Accordingly, the terminal device receives the second instruction information through the first network device.
[0313] S604. The terminal device determines the connection method with the second network device.
[0314] In this embodiment of the application, the method of determining the connection with the second network device can be described as a determine switch / dual connection.
[0315] S605, The terminal device sends a second handover instruction to the first network device.
[0316] Accordingly, the first network device receives the second handover instruction sent by the terminal device.
[0317] S606, The first network device sends a second handover request to the second network device.
[0318] Accordingly, the second network device receives the second handover request sent by the first network device.
[0319] S607, The second network device sends a second handover message to the first network device.
[0320] Accordingly, the first network device receives the second handover information sent by the second network device.
[0321] S608, The first network device sends a second handover command to the terminal device.
[0322] Accordingly, the terminal device receives the second handover command sent by the first network device.
[0323] S609. The terminal device sends the first RRC reconfiguration completion information to the second network device.
[0324] Accordingly, the second network device receives the first RRC reconfiguration completion information sent by the terminal device.
[0325] S610, The terminal device establishes an RRC connection with the second network device.
[0326] In this embodiment, the second paging information is used to notify the terminal device that there is new data or event that needs to be processed. Based on the instruction of the second paging information, the terminal device establishes an RRC connection with the first network device to facilitate further communication and control signaling interaction. The core network sends a second indication message to the terminal device through the first network device, indicating the RAT type associated with the current PDU session, so that the terminal device understands the specific radio access technology to be used. Further, based on the second indication message and its own capabilities, the terminal device decides whether to establish a dual-stack connection with the second network device or to completely switch to the second network device. Further, the terminal device informs the first network device of its switching requirements and related information, including connection method or measurement reports. Based on the terminal device's switching indication, the first network device sends a switching request to the second network device, requesting the second network device to prepare for the terminal device's switching. The second network device sends a second switching instruction to the terminal device, and the first network device, based on the feedback from the second network device, sends a switching instruction to the terminal device, instructing it to begin the switching operation. The terminal device executes the switching operation and sends an RRC reconfiguration completion message to the second network device, notifying it that the switching is complete. The terminal device re-establishes an RRC connection with the second network device, completes the handover process, and begins communication in the new network.
[0327] Understandably, the above switching process not only ensures that terminal devices can select the optimal connection method according to business needs and network conditions, but also improves network resource utilization and user experience.
[0328] Category 3, the instruction information is the third instruction information.
[0329] In this embodiment of the application, the terminal device is in an unconnected state (IDLE / INACTIVE state) with both the first network device and the second network device.
[0330] In this embodiment of the application, as shown in FIG9, the communication method includes S701 to S712:
[0331] S701, The first network device sends a second paging message to the terminal device.
[0332] Accordingly, the terminal device receives the second paging information sent by the first network device.
[0333] S702. The terminal device establishes an RRC connection with the first network device.
[0334] S703, the core network sends the fourth instruction information to the first network device.
[0335] In some embodiments of this application, the fourth indication information is used to indicate the RAT type associated with the current PDU session.
[0336] Accordingly, the first network device receives the fourth instruction information issued by the core network.
[0337] S704. The first network device determines the connection method between the terminal device and the second network device.
[0338] S705, The first network device sends a third instruction message to the terminal device.
[0339] In some embodiments of this application, the third indication information is used to indicate the connection method between the terminal device and the second RAT type.
[0340] In some embodiments of this application, the third indication information is related to the current service connection status.
[0341] Accordingly, the terminal device receives the third instruction information sent by the first network device.
[0342] S706, The terminal device sends a measurement report to the first network device.
[0343] Accordingly, the first network device receives the measurement report sent by the terminal device.
[0344] S707, The first network device sends a second handover request to the second network device.
[0345] Accordingly, the second network device receives the second handover request sent by the first network device.
[0346] S708, the second network device sends a second handover message to the first network device.
[0347] Accordingly, the first network device receives the second handover information sent by the second network device.
[0348] S709, The first network device sends a second handover command to the terminal device.
[0349] Accordingly, the terminal device receives the second handover command sent by the first network device.
[0350] S710, the terminal device sends the first RRC reconfiguration completion information to the second network device.
[0351] Accordingly, the second network device receives the first RRC reconfiguration completion information sent by the terminal device.
[0352] S711. The terminal device establishes an RRC connection with the second network device.
[0353] In this embodiment, the first network device sends a second paging message to the terminal device. After receiving the second paging message, the terminal device establishes an RRC connection with the first network device. The core network sends a fourth indication message to the first network device, informing it of the RAT type associated with the current PDU session. Based on the fourth indication message and network configuration, the first network device determines how the terminal should connect to the second network device. The first network device transmits the determined connection method to the terminal device via a third indication message. Based on the third indication message, the terminal device sends a report to the first network device including current network and neighboring cell measurement results. The first network device confirms the handover request and sends handover information to the first network device, including the resources and configurations learned during the handover. Based on the feedback from the second network device, the first network device sends a handover command to the terminal device, instructing it to begin the handover operation. The terminal device executes the handover operation and sends an RRC reconfiguration completion message to the second network device, completing the handover process. The terminal device establishes a new RRC connection with the second network device, completing the handover from the first network device to the second network device.
[0354] Understandably, the above process ensures that terminal devices can efficiently switch networks according to business needs and network configuration, maintaining the continuity and stability of communication.
[0355] This application provides a communication method. The main idea of this method is that a terminal device obtains indication information. The terminal device is at least camped in a cell of a first network device, which is associated with a first Radio Access Technology (RAT) type. The indication information indicates information related to a second RAT type, where the first RAT type differs from the second RAT type. The terminal device is at least in a disconnected state with the second network device associated with the second RAT type. The indication information helps the terminal device accurately determine when to switch to the second RAT type, avoiding frequent invalid handovers or continuous monitoring of other RAT types, thereby reducing the terminal device's power consumption. The indication information provides clear guidance, making the network handover process smoother and more efficient. Knowing when and how to switch to the second RAT type, the terminal device can quickly respond and execute the handover operation, reducing handover latency and improving service continuity and stability. By reducing unnecessary handovers and optimizing handover timing, the indication information helps improve communication reliability and response speed. Ensuring that the terminal device always connects to the most suitable RAT type can improve data transmission rate and service quality, thereby improving communication performance and user experience.
[0356] The communication method provided in this application will be explained in some specific embodiments below.
[0357] In this embodiment of the application, the terminal device UE is in IDLE / INACTIVE state (equivalent to a disconnected state) in both networks (Network1 and Network2). After receiving the paging message (equivalent to the first paging information) sent by the first network device, the UE determines which network to access from based on the paging message.
[0358] In this embodiment of the application, as shown in FIG10, the communication method further includes S1001 to S1004:
[0359] S1001, The first network device sends paging information to the terminal device.
[0360] In this embodiment, the first network device is associated with a first RAT type (RAT1), and the second network device is associated with a second RAT type (RAT2). In other words, the network type of the first network device is the first RAT type, and the network type of the second network device is the second RAT type.
[0361] In this embodiment of the application, the paging information in S1001 is equivalent to the first paging information mentioned above.
[0362] In this embodiment, the first paging information can explicitly or implicitly indicate that the associated service is a 5G and / or 6G service. Specifically, it explicitly indicates that the RAT of the associated service is 5G and / or 6G (applicable to new (6G) base stations and new (6G) users). In this case, the RAT indication can also be optional. For example, if the RAT is the same as the current RAT1, no indication is needed; it is only indicated when the RAT associated with the paging is different from RAT1. Implicit methods include distinguishing 5G and 6G paging through the UE ID. For example, if the UE's 5G-related services and 6G-related services use different UE IDs, the UE can distinguish the RAT associated with the paging based on the different address spaces of the UE IDs; or it can distinguish 5G and 6G by indicating the PLMN.
[0363] In this application embodiment, the first paging information includes two types: CN paging (sent from the core network to the UE to notify the UE that there is data or time from the core network that needs to be processed) or RAN paging (sent from the radio access network (base station) to notify the UE that there is data or event from the RAN or core network that needs to be processed within a specific area).
[0364] If it is CN paging, then CN instructs the RAN to send the paging message to the RAT associated with it (or only if the RAT associated with the paging is different from RAT1). If it is RAN paging, and the RAN paging is generated by another RAT, then CN assists RAT1 in sending the paging message and needs to inform the RAT of the service associated with the paging message.
[0365] It is understandable that the UE can receive all paging messages regardless of which RAT it is camped on, and can identify which RAT the service associated with the paging message comes from, thereby determining which RAT to access from.
[0366] S1002, The terminal device performs cell reselection.
[0367] In this application embodiment, cell reselection can be described as cell(RAT) reselection.
[0368] S1003, The terminal device sends an RRC connection request to the second network device.
[0369] In this embodiment of the application, the RRC connection request can be described as an RRC Setup REQ.
[0370] Specifically, the UE responds to the received paging message. If the paging message is associated with the currently camped RAT1, the UE initiates an RRC (Radio Resource Control) connection establishment request (RRC setup / RRC resume) on RAT1. If the paging message is associated with another RAT, the UE triggers cell (RAT) reselection and initiates an RRC connection establishment request (RRC setup / RRC resume) on the reselected cell.
[0371] In this application embodiment, the cell reselection method includes the following:
[0372] Method 1: The terminal device increases the priority of the cell (frequency) of the RAT associated with the paging message (higher than the priority of the current RAT1 cell or frequency), and then performs cell reselection according to the R criterion to select the cell that meets the R criterion and is associated with the RAT associated with the paging message.
[0373] Method 2: The terminal device lowers the priority of the current serving cell to the lowest level, and then performs cell reselection according to the R criterion to select a cell that meets the R criterion and is associated with the RAT associated with the paging message;
[0374] Method 3: The terminal device does not adjust the frequency priority. Upon receiving a paging message, it triggers cell reselection. During reselection, it only considers cells associated with the RAT associated with the paging message and selects the cell with the strongest signal quality among these cells.
[0375] Method 4: The network configures separate parameters (priority, threshold configuration) for cell reselection triggered by receiving a paging message. In this case, the UE uses the separate configuration to perform cell reselection.
[0376] In this embodiment, if the paging message is associated with other RATs, another implementation (without triggering cell reselection) is that the UE can simultaneously camp on multiple RATs' cells, i.e., 5G cells and 6G cells. If RAT1 receives a paging message from RAT2, the UE directly accesses and responds on RAT2's cell. In this case, whether the UE listens for the paging message on RAT1's cell or RAT2's cell depends on: the protocol definition (e.g., default priority to listen on 6G networks); the UE implementation; the paging period (longer / shorter); or the network configuration (e.g., configuring which RAT has higher priority).
[0377] S1004. The second network device sends RRC connection information to the terminal device.
[0378] Understandably, when a UE receives a paging message, it triggers cell reselection based on the paging message and directly responds to the paging message in cell x of the corresponding RAT, which is faster and simpler.
[0379] In this embodiment, the UE is in IDLE / INACTIVE state in both networks. After receiving the paging message, the UE directly accesses the current network (the network then transfers the accessed UE to the corresponding RAT).
[0380] Implementation Method 1:
[0381] In this embodiment of the application, as shown in FIG11, the communication method further includes S2001 to S2006:
[0382] S2001, The first network device sends a paging message to the terminal device.
[0383] In this embodiment of the application, the paging information in S2001 is equivalent to the first paging information mentioned above.
[0384] It is understandable that the UE can receive all paging messages regardless of which RAT it is camped on, and can identify which RAT the service associated with the paging message comes from, thereby determining the cause value accessed in the current RAT.
[0385] S2002, The terminal device sends an RRC connection establishment request to the first network device.
[0386] In this embodiment of the application, the RRC connection establishment request can be described as RRC Setup REQ.
[0387] In this embodiment of the application, the UE responds to the received paging message and initiates a connection establishment request in the current RAT1. The connection establishment request message needs to carry: Cause value (equivalent to the reason value mentioned above) and measurement report.
[0388] For the cause value, if the paging message is associated with the currently residing RAT1, the cause value in the RRC connection establishment request (RRC setup / RRC resume) is filled with the existing normal cause value; if the paging message is associated with other RATs, the cause value in the RRC connection establishment request (RRC setup / RRC resume) indicates that the connection is a paging connection in response to the service associated with other RATs, such as indicating 5G-Access or 6G-Access.
[0389] The measurement report is carried when accessing other RATs and reports the cells associated with those other RATs and the measurement results. The measurement report may only include cells with values greater than a first threshold. The first threshold is either a cell reselection threshold or a threshold configured separately by the network and associated with the measurement report (a broadcast system message).
[0390] It is understandable that when a UE receives a paging message, it directly establishes a connection in the current cell and determines the signaling content of the RRC connection establishment request based on the paging message.
[0391] S2003, The first network device sends a handover request to the second network device.
[0392] In this embodiment of the application, the switching request can be described as a HO REQ.
[0393] S2004, The second network device sends a handover message to the first network device.
[0394] In this embodiment of the application, the switching information can be described as HO RES.
[0395] In this embodiment, after receiving a connection establishment request, the RAT1 network determines the target RAT2 network based on the cause value and measurement report in the request, and sends a handover request (HO REQ) to the RAT2 network. The handover request indicates that the handover is due to paging. Furthermore, the RAT2 network responds to the RAT1 request.
[0396] It is understandable that since the UE accesses the RAT1 network only to access the RAT2 network as soon as possible, there is no need to go through the complete access procedure. The reason for access and the candidate target cell can be directly indicated in SRB0, and the RAT1 network will directly switch the UE to the RAT2 network based on this information.
[0397] S2005. The first network device sends RRC connection information to the terminal device.
[0398] In this embodiment of the application, RRC connection information can be described as RRC Setup.
[0399] In this embodiment of the application, the RAT1 network sends RRC setup information to the UE, which carries handover configuration information (sent in S2004) generated by the RAT2 network (refer to the current ReconfigwithSync configuration).
[0400] Understandably, merging the HO and RRC setup steps eliminates unnecessary procedures and reduces latency and signaling overhead.
[0401] S2006. The terminal device sends an RRC connection completion message to the second network device.
[0402] In this embodiment of the application, the RRC connection completion information can be described as RRC Reconfig Complete.
[0403] In this embodiment of the application, the UE completes the handover process and establishes a connection in the target network.
[0404] In this embodiment of the application, relevant information is carried in the RRC setup to let the network know that the connection is established in response to the paging message associated with other RATs (cause value indicates that the access request is for the service associated with other RATs).
[0405] Implementation Method Two:
[0406] In this embodiment of the application, as shown in FIG12, the communication method further includes S3001 to S3008:
[0407] S3001, The first network device sends a paging message to the terminal device.
[0408] In the embodiments of this application, the description of S3001 is the same as that of S1001, and will not be repeated here.
[0409] S3002, The terminal device sends an RRC connection establishment request to the first network device.
[0410] In this embodiment of the application, the RRC connection establishment request can be described as RRC Setup REQ.
[0411] S3003, The first network device sends RRC connection information to the terminal device.
[0412] In this embodiment of the application, RRC connection information can be described as RRC Setup.
[0413] In this embodiment of the application, the UE responds to the received paging message and initiates a connection establishment request in the current RAT1. The network responds to the request by sending an RRC setup command to the UE.
[0414] S3004. The terminal device sends an RRC connection completion message to the first network device.
[0415] In this embodiment of the application, the RRC connection completion information can be described as RRC Sutep Complete.
[0416] In this embodiment, the UE sends an RRC connection establishment request completion message. This message must carry: an indication that the connection is a paging connection in response to services associated with other RATs, such as 5G-Access or 6G-Access, and a measurement report. The measurement report is carried when accessing other RATs, reporting the cells associated with those RATs and the measurement results. This measurement report may only include cells with values greater than a first threshold, where the first threshold is a cell reselection threshold or a network-configured threshold associated with the measurement report (a broadcast system message).
[0417] It is understandable that when a UE receives a paging message, it directly establishes a connection in the current cell and determines that access in the current RAT requires further switching to the target RAT.
[0418] S3005, The first network device sends a handover request to the second network device.
[0419] In this embodiment of the application, the switching request can be described as a HO REQ.
[0420] S3006, The second network device sends a handover message to the first network device.
[0421] In this embodiment of the application, the switching information can be described as HO RES.
[0422] Understandably, the UE still completed the entire connection establishment process in RAT1, and the final completion information indicated that the connection establishment was for the purpose of connecting to other RATs.
[0423] S3007. The first network device sends a handover command to the terminal device.
[0424] In this embodiment, the handover command can be described as a HO Command. The RAT1 network sends HO command information to the UE.
[0425] S3008. The terminal device sends an RRC connection reconfiguration completion message to the second network device.
[0426] In this embodiment, the RRC connection reconfiguration completion information can be described as RRC Reconfig Complete. The UE completes the handover procedure and establishes a connection on the target network.
[0427] In this embodiment of the application, the RRC setupcomplete carries relevant information to let the network know that the connection is established in response to paging messages associated with other RATs.
[0428] It should be noted that, for Embodiment 2, the network can choose to bar (discard or disconnect) a UE that accesses the cell to access another RAT. The barring method can be to indicate in the MIB or SIB1 that the access method is not supported, or to set the priority of the access method to a relatively low level, thus preventing the UE from accessing the network for this reason when the network is congested. After a UE is barred, cell reselection can be triggered according to the current mechanism, allowing the UE to select a cell for the corresponding RAT, referring to Embodiment 1.
[0429] In this embodiment, the UE is in IDLE / INACTIVE state in both networks. The UE does not need to distinguish which network the paging message (equivalent to the second paging information mentioned above) comes from. The UE responds to the paging message in the current network. After the UE enters the connected state, it can choose to switch to other networks or connect via dual protocol stack.
[0430] Implementation Method 1:
[0431] For implementation method one, the UE decides whether to switch or use a dual protocol stack connection.
[0432] In this embodiment of the application, as shown in FIG13, the communication method further includes S4001 to S4010:
[0433] S4001, The first network device sends a paging message to the terminal device.
[0434] In this embodiment of the application, the paging information in S4001 is equivalent to the second paging information mentioned above.
[0435] In this embodiment, S4001 uses the existing paging mechanism and does not require indicating 5G / 6G related information.
[0436] S4002. The terminal device establishes an RRC connection with the first network device.
[0437] In this embodiment of the application, the UE responds to the received paging message and establishes a connection in the current RAT1.
[0438] S4003, the core network sends instruction information to the terminal equipment.
[0439] In this embodiment, the indication information in S4003 is equivalent to the second indication information mentioned above. The second indication information can be described as the indication of 5G / 6G.
[0440] In this embodiment of the application, the CN sends a NAS message to the UE through RAT1 to indicate that the current PDU session is associated with RAT2.
[0441] S4004. The terminal device determines whether to use a dual-protocol stack connection or a switching connection.
[0442] In this application embodiment, S4004 can be described as a determine switch / dual connection.
[0443] In this embodiment of the application, the UE determines whether to establish a dual protocol stack connection with RAT2 or perform HO (handover) to RAT2 based on the CN instruction and in combination with the current connection / service status of RAT1 (whether there is / will be a service associated with RAT1).
[0444] Specifically, if there is a dual protocol stack connection, a connection establishment request is initiated in RAT2, and the cause value uses MT access; if switching to RAT2, a handover request indication is sent to the RAT1 network along with a measurement report (reporting the cells associated with other RATs and the measurement results, which may only include cells greater than a first threshold, where the first threshold is a cell reselection threshold or a threshold configured separately by the network and associated with the measurement report).
[0445] S4005, The terminal device sends a handover instruction to the first network device.
[0446] In this embodiment of the application, the switching indication can be described as a switch indication.
[0447] S4006, The first network device sends a handover request to the second network device.
[0448] In this embodiment of the application, the switching request can be described as a HO REQ.
[0449] S4007. The second network device sends a handover message to the first network device.
[0450] In this embodiment of the application, the switching information can be described as HO RES.
[0451] S4008, The first network device sends a handover command to the terminal device.
[0452] In this application embodiment, the switching instruction can be described as a HO Command.
[0453] S4009. The terminal device sends an RRC connection reconfiguration completion message to the second network device.
[0454] In this embodiment of the application, the RRC connection reconfiguration completion information can be described as RRC Reconfig Complete.
[0455] S4010, The terminal device is connected to the second network device RRC.
[0456] Implementation Method Two:
[0457] In the second implementation method, the first network device NW decides whether to switch or use a dual protocol stack connection.
[0458] In this embodiment of the application, as shown in FIG14, the communication method further includes S5001 to S5012:
[0459] S5001, The first network device sends paging information to the terminal device.
[0460] In this embodiment of the application, the paging information in S5001 is equivalent to the second paging information mentioned above.
[0461] In this embodiment of the application, the existing paging mechanism does not require the second paging information to indicate 5G / 6G related information.
[0462] S5002, The terminal device establishes RRC connection information with the first network device.
[0463] S5003, the core network sends instruction information to the terminal equipment.
[0464] In this embodiment of the application, the instruction information in S5003 is equivalent to the fourth instruction information mentioned above.
[0465] In this embodiment of the application, the fourth indication information can be described as an indication of 5G / 6G.
[0466] S5004. The first network device determines whether to use a dual-protocol stack connection or switch connections.
[0467] In this application embodiment, determining whether to use a dual protocol stack connection or a switching connection can be described as a determine switch / dual connection.
[0468] In this embodiment, RAT1 determines, based on the CN instruction and in conjunction with the current connection / service status of RAT1 (whether there is / will be a service associated with RAT1), whether to control the UE to establish a dual protocol stack connection with RAT2 or to execute HO to RAT2; or the CN directly decides whether to switch or establish a dual protocol stack connection and directly instructs the RAN node.
[0469] Specifically, if a dual-protocol stack connection is established, a dual-protocol stack connection indication is sent to the UE, and a connection establishment request is initiated on RAT2, using MT access as the cause value. If switching to RAT2, a handover indication is sent from RAT1.
[0470] S5005, The first network device sends a connection switching instruction to the terminal device.
[0471] In this embodiment of the application, the connection switching indication is equivalent to the third indication information mentioned above.
[0472] In this embodiment of the application, if a dual protocol stack connection indication is received, a connection establishment request is initiated on RAT2, and the cause value uses MT access; if a handover indication is received, a measurement report is sent, and the handover is switched to RAT2 according to the handover command.
[0473] S5006, The terminal device sends a measurement report to the first network device.
[0474] In this embodiment of the application, the measurement report can be described as a measurement report.
[0475] S5007, The first network device sends a handover request to the second network device.
[0476] In this embodiment of the application, the switching request can be described as a HO REQ.
[0477] S5008, the second network device sends a handover message to the first network device.
[0478] In this embodiment of the application, the switching information can be described as HO RES.
[0479] S5009, The first network device sends a handover command to the terminal device.
[0480] In this application embodiment, the switching instruction can be described as a HO Command.
[0481] S5010: The terminal device sends an RRC connection reconfiguration completion message to the second network device.
[0482] In this embodiment of the application, the RRC connection reconfiguration completion information can be described as RRC Reconfig Complete.
[0483] S5011, The first network device sends a dual protocol stack connection instruction to the terminal device.
[0484] In this embodiment of the application, the connection switching indication is equivalent to the third indication information mentioned above.
[0485] S5012, Terminal equipment and second network equipment RRC connection
[0486] In this embodiment of the application, as shown in FIG15, the communication method further includes S6001 to S6005:
[0487] S6001, The first network device sends RRC dedicated information to the terminal device.
[0488] In this embodiment of the application, if the UE is in connected state in RAT1 and in IDLE / INACTIVE state in RAT2, and a service associated with RAT2 triggers a paging message, the CN instructs RAT1 to send the paging message to the UE through a dedicated message.
[0489] It should be understood that when a UE is in connected state under one network (RAT), it does not need to listen to paging messages from another network. Receiving dedicated messages is more power-efficient for the UE.
[0490] S6002, The terminal device determines whether to establish a connection with the network associated with the second RAT type.
[0491] In this embodiment, the UE determines whether to stay in the current network, switch to the target network, or connect to both networks simultaneously, based on the received paging message, the current service status under the network, and the UE's capabilities.
[0492] Specifically, if the UE's capability is to support only a single Tx / Rx (only one network can operate at a time), and the priority of the target network's services (indicated by paging information, such as paging cause, or indicated by service priority level) is lower than or equal to the current network's service priority, then the UE remains in the current network. If the UE's capability is to support only a single Tx / Rx (only one network can operate at a time), and the priority of the target network's services (indicated by paging information, such as paging cause, or indicated by service priority level) is higher than or equal to the current network's service priority, then the UE switches to the target network and indicates to the current network the switchover time and / or switchover period (e.g., start position + time length). If the UE's capability is to support multiple Tx / Rx (only one network can operate at a time), then the UE can access two networks simultaneously (or choose to access only one network, referring to the first two cases).
[0493] S6003, The terminal device sends a handover instruction to the first network device.
[0494] S6004. The terminal device sends an RRC connection request to the second network device.
[0495] S6005, The terminal device is connected to the second network device RRC.
[0496] In this embodiment of the application, as shown in FIG16, the communication method further includes S5001 to S5012:
[0497] S7001, The first network device sends paging information to the terminal device.
[0498] In this embodiment, if the UE is in connected state on RAT1 and in IDLE / INACTIVE state on RAT2, and a service associated with RAT2 triggers a paging message, RAT1 sends the paging message to the UE through normal paging broadcast. The specific content of the paging message is described in Embodiments 1 and 2.
[0499] S7002, The terminal device determines whether to establish a connection with the network associated with the second RAT type.
[0500] S7003, The terminal device sends a handover instruction to the first network device.
[0501] S7004. The terminal device sends an RRC connection request to the second network device.
[0502] S7005, The terminal device is connected to the second network device RRC.
[0503] In this application embodiment, a paging monitoring and response mechanism is provided in a 6G scenario where 5G / 6G base stations and corresponding services coexist.
[0504] This application addresses the problem of ensuring that a UE can receive paging messages generated by any RAT (associated with different services) under different network coverage conditions (different RATs), and how to respond to these paging messages. It allows the UE to listen for paging messages from only one network (energy-saving and simpler for the UE) and discusses different mechanisms for the UE to respond to paging messages.
[0505] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application. Moreover, without conflict, the various embodiments and / or the technical features in the various embodiments described in this application can be arbitrarily combined with related technologies, and the resulting technical solutions should also fall within the protection scope of this application.
[0506] It should also be understood that in the various method embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. Furthermore, in the embodiments of this application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data. "Downlink" indicates that the transmission direction of signals or data is a first direction from the site to the user equipment in the cell; "uplink" indicates that the transmission direction of signals or data is a second direction from the user equipment in the cell to the site; and "sidelink" indicates that the transmission direction of signals or data is a third direction from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. Additionally, in the embodiments of this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0507] Figure 17 is a schematic diagram of the structure of an optional communication device according to an embodiment of this application, applied to a terminal device. As shown in Figure 17, the communication device 10 includes a first communication unit 11; wherein,
[0508] The first communication unit 11 is configured to acquire indication information; wherein the indication information is used to indicate information related to the wireless access technology (RAT) type that has a connection requirement with the terminal device.
[0509] In some embodiments, the indication information includes first indication information; the first indication information includes the RAT type corresponding to the Radio Resource Control (RRC) connection.
[0510] In some embodiments, the first communication unit 11 is further configured to receive first paging information; the first paging information carries the first indication information.
[0511] In some embodiments, the first indication information includes one or more of the following: RAT type identifier; identifier of the terminal device, wherein the identifier of the terminal device is different under different RAT types; Public Land Mobile Network (PLMN) information.
[0512] In some embodiments, the terminal device is at least camped in a cell of a first network device, the first network device being associated with a first RAT type, the second network device being associated with a second RAT type, the first RAT type being different from the second RAT type, and the second network device associated with the terminal device at least with the second RAT type being in a disconnected state.
[0513] In some embodiments, the first communication unit 11 is further configured to trigger cell reselection and send a first RRC connection request or a first RRC recovery request to the second network device when the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type; wherein the cell of the second network device is a reselection cell.
[0514] In some embodiments, the first communication unit 11 is further configured to receive first RRC connection information or first RRC recovery information sent by the second network device; and to establish an RRC connection with the second network device according to the first RRC connection information.
[0515] In some embodiments, the cell reselection method includes one or more of the following: adjusting the priority of cells and / or frequencies associated with the first RAT type and performing cell reselection using the R criterion; adjusting the priority of cells and / or frequencies associated with the second RAT type and performing cell reselection using the R criterion; performing cell reselection based on all neighboring cells associated with the second RAT type; and performing cell reselection using the R criterion according to one or more preset parameter configurations; wherein the one or more parameter configurations are configured by the first network device; and the one or more parameter configurations correspond to different RAT types.
[0516] In some embodiments, the first communication unit 11 is further configured to send a second RRC connection request to the first network device when the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the first RAT type, so as to enable the terminal device to establish an RRC connection with the first network device.
[0517] In some embodiments, the first communication unit 11 is further configured to, according to a first method, determine to listen to the first paging information in the cell of the first network device or the second network device where the terminal device is camped at least in the cell of the first network device and the second network device.
[0518] In some embodiments, the first method includes one or more of the following: a predefined configuration method; an implementation based on the terminal device; determination based on the listening period of the at least two neighboring cells; and network configuration.
[0519] In some embodiments, the first communication unit 11 is further configured to send a third RRC connection request to the first network device when the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type.
[0520] In some embodiments, the third RRC connection request includes: a cause value, the cause value including information indicating the RAT type associated with the first paging information, and a measurement report, the measurement report including measurement results of one or more neighboring cells of the second RAT type.
[0521] In some embodiments, the first communication unit 11 is further configured to acquire second RRC connection information sent by the first network device, and establish an RRC connection with the second network device according to the second RRC connection information; wherein the second RRC connection information includes: handover configuration information related to the second network device.
[0522] In some embodiments, the first communication unit 11 is further configured to send first RRC connection completion information to the first network device in response to the third RRC connection information sent by the first network device in response to the third RRC connection request; wherein the first RRC connection completion information includes: information indicating the RAT type associated with the first paging information and a measurement report.
[0523] In some embodiments, the first communication unit 11 is further configured to receive a first handover instruction sent by the first network device to enable the terminal device to establish an RRC connection with the second network device; the first handover instruction includes handover configuration information related to the second network device.
[0524] In some embodiments, the first communication unit 11 is further configured to receive RRC dedicated information sent by the first network device; the RRC dedicated information carries the first indication information.
[0525] In some embodiments, the first communication unit 11 is further configured to determine, based on terminal capabilities and / or current service requirements, whether the terminal device establishes a connection with a network associated with the second RAT type, when the terminal device is camped in a cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type.
[0526] In some embodiments, the first communication unit 11 is further configured to: when the terminal capability supports a single RAT connection, if the priority of the second RAT type is lower than the priority of the first RAT type, determine that the terminal device maintains a connection with the network associated with the first RAT type; when the terminal capability supports a single RAT connection, if the priority of the second RAT type is higher than the priority of the first RAT type, determine that the terminal device establishes a connection with the network associated with the second RAT type; when the UE capability supports multiple RAT connections, determine that the terminal device establishes a connection with the network associated with the second RAT type, or, the terminal device simultaneously establishes connections with the networks associated with the first network device and the second network device.
[0527] In some embodiments, the first communication unit 11 is further configured to send a first handover instruction to the first network device when it is determined that the terminal device has established a connection with a network associated with the second RAT type; the first handover instruction includes: connection mode and / or network measurement information associated with the second RAT type. In response to the first handover instruction, the terminal device switches to the second network device, or simultaneously establishes a connection with both the first and second network devices.
[0528] In some embodiments, the first communication unit 11 is further configured to, upon determining that the terminal device has established a connection with a network associated with the second RAT type, trigger the establishment of a connection with the second network device and disconnect or not disconnect the connection with the first network device.
[0529] In some embodiments, the first communication unit 11 is further configured to, when the terminal device establishes a connection with the networks associated with the first network device and the second network device simultaneously, switch the transmitter and / or receiver between the networks associated with the first network device and the second network device in a time-division multiplexing (TDM) manner, wherein the switching of the transmitter and / or receiver in a TDM manner is related to the user's capability and / or service characteristics.
[0530] In some embodiments, the first communication unit 11 is further configured to send a second handover instruction to the first network device; the second handover instruction includes: relevant information of the second network device, and / or, handover time, and / or, handover period.
[0531] In some embodiments, the indication information includes second indication information, which is used to indicate the RAT type associated with the current PDU session.
[0532] In some embodiments, the second indication information is forwarded by the first network device from the core network.
[0533] In some embodiments, the first communication unit 11 is further configured to, when the terminal device is camped in the cell of the first network device and the terminal device establishes an RRC connection with the first network device, if the second indication information indicates that the RAT type associated with the current PDU session includes a second RAT type, determine the connection method between the terminal device and the second network device based on the current service connection status.
[0534] In some embodiments, the indication information is third indication information, which is used to indicate the connection method between the terminal device and the second RAT type.
[0535] In some embodiments, the first communication unit 11 is further configured to acquire the third indication information sent by the first network device; the third indication information is related to the current service connection status.
[0536] In some embodiments, the connection method includes: dual protocol stack connection, and / or, switching connection.
[0537] In some embodiments, the first communication unit 11 is further configured to trigger cell reselection and send a fourth RRC connection request to the second network device of the reselected cell when the connection mode is the dual protocol stack connection, so that the terminal device establishes an RRC connection with the second network device.
[0538] In some embodiments, the first communication unit 11 is further configured to send a measurement report to the first network device when the connection mode is the dual protocol stack connection or the switching connection, the measurement report being used by the terminal device to establish an RRC connection with the second network device.
[0539] In some embodiments, the first communication unit 11 is further configured to, when the terminal device is camped in the cell of the first network device, acquire second paging information sent by the first network device; and, in response to the second paging information, establish an RRC connection with the first network device.
[0540] In some embodiments, the first communication unit 11 is further configured to receive a second handover instruction sent by the first network device, the first handover instruction including handover configuration information related to the second network device; and in response to the second handover request, to switch from the first network device to the second network device, or to establish a connection with both the first network device and the second network device simultaneously.
[0541] In some embodiments, the terminal device and the first network device are in a connected state, an idle state, or an inactive state.
[0542] Those skilled in the art should understand that the description of the communication device in the embodiments of this application can be understood with reference to the description of the communication method in the embodiments of this application.
[0543] Figure 18 is a schematic diagram of the structure of an optional communication device according to an embodiment of this application, applied to a first network device. As shown in Figure 18, the communication device 20 includes a second communication unit 21; wherein,
[0544] The second communication unit 21 is configured to send indication information to the terminal device; wherein the indication information is used to indicate relevant information about the wireless access technology (RAT) type that has connection requirements with the terminal device.
[0545] In some embodiments, the indication information is first indication information, which includes the RAT type corresponding to the Radio Resource Control (RRC) connection.
[0546] In some embodiments, the second communication unit 21 is further configured to send a first paging message to the terminal device; the first paging message carries the first indication information.
[0547] In some embodiments, the second communication unit 21 is further configured such that the first indication information includes one or more of the following: RAT type identifier; identifier of the terminal device, wherein the identifier of the terminal device is different under different RAT types; Public Land Mobile Network (PLMN) information.
[0548] In some embodiments, the terminal device is at least camped in a cell of a first network device, the first network device being associated with a first RAT type, the second network device being associated with a second RAT type, the first RAT type being different from the second RAT type, and the second network device associated with the terminal device at least with the second RAT type being in a disconnected state.
[0549] In some embodiments, the second communication unit 21 is further configured to receive a third RRC connection request sent by the terminal device when the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type.
[0550] In some embodiments, the third RRC connection request includes: a cause value, the cause value including information indicating the RAT type associated with the first paging information, and a measurement report, the measurement report including measurement results of one or more neighboring cells of the second RAT type.
[0551] In some embodiments, the second communication unit 21 is further configured to send second RRC connection information to the terminal device so that the terminal device establishes an RRC connection with the second network device; wherein the second RRC connection information includes: handover configuration information related to the second network device.
[0552] In some embodiments, the second communication unit 21 is further configured to determine the second network device based on the cause value and the measurement report.
[0553] In some embodiments, the second communication unit 21 is further configured to receive first RRC connection completion information sent by the terminal device; wherein the first RRC connection completion information includes: information indicating the RAT type associated with the first paging information and a measurement report.
[0554] In some embodiments, the second communication unit 21 is further configured to send a first handover instruction to the terminal device to enable the terminal device to establish an RRC connection with the second network device; the first handover instruction includes handover configuration information related to the second network device.
[0555] In some embodiments, the second communication unit 21 is further configured to send RRC dedicated information to the first network device; the RRC dedicated information carries the first indication information.
[0556] In some embodiments, the second communication unit 21 is further configured to receive a first handover instruction sent by the terminal device when the terminal device is camped in a cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type, and the terminal device determines that a connection has been established with the network associated with the second RAT type; the first handover instruction includes: connection method and / or network measurement information associated with the second RAT type.
[0557] In some embodiments, the second communication unit 21 is further configured to receive a second handover instruction sent by the terminal device if the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type, and the terminal device simultaneously establishes a connection with the networks associated with the first network device and the second network device; the second handover instruction includes: relevant information of the second network device, and / or, handover time, and / or, handover period.
[0558] In some embodiments, the indication information includes second indication information, which is used to indicate the RAT type associated with the current PDU session.
[0559] In some embodiments, the second instruction information is issued by the core network.
[0560] In some embodiments, the indication information includes third indication information, which is used to indicate the connection method between the terminal device and the second RAT type; the third indication information is related to the current service connection status.
[0561] In some embodiments, the second communication unit 21 is further configured to receive a fourth indication information sent by the core network; the fourth indication information is used to indicate the RAT type associated with the current PDU session; and a third indication information is determined based on the fourth indication information and the current service connection status.
[0562] In some embodiments, the connection method includes: dual protocol stack connection, and / or, switching connection.
[0563] In some embodiments, the second communication unit 21 is further configured to receive a measurement report sent by the terminal device when the connection mode is the dual protocol stack connection or the switching connection, the measurement report being used by the terminal device to establish an RRC connection with the second network device.
[0564] In some embodiments, the second communication unit 21 is further configured to send a second paging message to the terminal device when the terminal device is camped in the cell of the first network device.
[0565] In some embodiments, the second communication unit 21 is further configured to send a second handover instruction to the terminal device, the first handover instruction including handover configuration information related to the second network device, so that the terminal device responds to the second handover request to switch from the first network device to the second network device, or to establish a connection with both the first network device and the second network device simultaneously.
[0566] In some embodiments, the terminal device and the first network device are in a connected state, an idle state, or an inactive state.
[0567] Those skilled in the art should understand that the description of the communication device in the embodiments of this application can be understood with reference to the description of the communication method in the embodiments of this application.
[0568] Figure 19 is a schematic diagram of the structural composition of an optional communication device provided in an embodiment of this application. The communication device 30 can be a terminal device or a first network device. The communication device 30 shown in Figure 19 includes a processor 31, which can call and run computer programs from memory to implement the methods in the embodiments of this application.
[0569] Optionally, as shown in FIG19, the communication device 30 may further include a memory 32. The processor 31 can retrieve and run computer programs from the memory 32 to implement the methods described in the embodiments of this application.
[0570] The memory 32 can be a separate device independent of the processor 31, or it can be integrated into the processor 31.
[0571] Optionally, as shown in FIG19, the communication device 30 may further include a transceiver 33, and the processor 31 may control the transceiver 33 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.
[0572] Transceiver 33, also known as communication interface, is used for receiving and sending signals during the process of sending and receiving information with other external network elements.
[0573] The transceiver 33 may include a transmitter and a receiver. The transceiver 33 may further include an antenna, and the number of antennas may be one or more.
[0574] Optionally, the communication device 30 may specifically be the first device (mobile terminal / terminal device) in the embodiments of this application, and the communication device 30 may implement the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0575] Optionally, the communication device 30 may specifically be the second device (network device) in the embodiments of this application, and the communication device 30 may implement the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0576] Figure 20 is a schematic diagram of the structure of an optional chip provided in an embodiment of this application. The chip 40 shown in Figure 20 includes a processor 41, which can call and run computer programs from memory to implement the methods in the embodiments of this application.
[0577] Optionally, as shown in FIG20, chip 40 may further include memory 42. Processor 41 can retrieve and run computer programs from memory 42 to implement the methods in the embodiments of this application.
[0578] The memory 42 can be a separate device independent of the processor 41, or it can be integrated into the processor 41.
[0579] Optionally, the chip 40 may also include a transceiver (also known as a communication interface) for receiving and sending signals during the exchange of information with a device or chip.
[0580] Optionally, as shown in FIG20, the transceiver may include an input interface 43. The processor 41 can control this input interface to communicate with other devices or chips; specifically, it can receive information or data sent by other devices or chips.
[0581] Optionally, as shown in Figure 20, the transceiver may include an output interface 44. The processor 41 can control this output interface to communicate with other devices or chips; specifically, it can send information or data to other devices or chips.
[0582] Optionally, the chip can be applied to the first device (mobile terminal / terminal device) in the embodiments of this application, and the chip can implement the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0583] Optionally, the chip can be applied to the second device (network device) in the embodiments of this application, and the chip can implement the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0584] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.
[0585] This application also provides a computer storage medium storing one or more programs, which can be executed by one or more processors to implement the methods in this application.
[0586] Figure 21 is a schematic diagram of the structural composition of an optional communication system provided in an embodiment of this application. As shown in Figure 21, the communication system 50 includes a terminal device 51 and a first network device 52.
[0587] The terminal device 51 can be used to implement the corresponding functions implemented by the first network device in the above method, and the second device 52 can be used to implement the corresponding functions implemented by the second device in the above method. For the sake of brevity, these will not be elaborated here.
[0588] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.
[0589] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0590] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.
[0591] This application also provides a computer-readable storage medium for storing computer programs.
[0592] Optionally, the computer-readable storage medium can be applied to the first device (mobile terminal / terminal device) in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0593] Optionally, the computer-readable storage medium can be applied to the second device (network device) in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0594] This application also provides a computer program product, including computer program instructions.
[0595] Optionally, the computer program product can be applied to the first device (mobile terminal / terminal device) in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.
[0596] Optionally, the computer program product can be applied to the second device (network device) in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.
[0597] This application also provides a computer program.
[0598] Optionally, the computer program can be applied to the first device (mobile terminal / terminal device) in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0599] Optionally, the computer program can be applied to the second device (network device) in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.
[0600] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0601] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0602] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0603] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0604] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0605] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to related technologies, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0606] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of protection of the embodiments of this application.
Claims
1. A communication method applied to a terminal device, the method comprising: Obtain indication information; wherein, the indication information is used to indicate relevant information about the wireless access technology (RAT) type that has connection requirements with the terminal device.
2. The method according to claim 1, wherein, The indication information includes first indication information; the first indication information includes the RAT type corresponding to the Radio Resource Control (RRC) connection.
3. The method according to claim 2, wherein, The method further includes: Receive the first paging information; the first paging information carries the first indication information.
4. The method according to claim 2 or 3, wherein, The first indication information includes one or more of the following: RAT type identifier; The identifier of the terminal device varies depending on the RAT type. Public Land Mobile Network (PLMN) information.
5. The method according to any one of claims 1 to 4, wherein, The terminal device is at least camped in the cell of the first network device, the first network device is associated with a first RAT type, the second network device is associated with a second RAT type, the first RAT type and the second RAT type are different, and the terminal device is at least associated with the second network device of the second RAT type in a non-connected state.
6. The method according to claim 5, wherein, The method further includes: When the terminal device is camped in the cell of the first network device, and the RAT type indicated by the first indication information includes the second RAT type, cell reselection is triggered, and a first RRC connection request or a first RRC recovery request is sent to the second network device; wherein, the cell of the second network device is the cell to be reselected.
7. The method according to claim 6, wherein, The method further includes: Receive the first RRC connection information or the first RRC recovery information sent by the second network device; Based on the first RRC connection information, an RRC connection is established with the second network device.
8. The method according to claim 6 or 7, wherein, The cell reselection methods include one or more of the following: The priority of cells and / or frequencies associated with the first RAT type is adjusted, and cell reselection is performed using the R criterion; The priority of cells and / or frequencies associated with the second RAT type is adjusted, and cell reselection is performed using the R criterion; Cell reselection is performed based on all neighboring cells associated with the second RAT type; Cell reselection is performed using the R criterion based on one or more preset parameter configurations; wherein, the one or more parameter configurations are configured by the first network device; and the one or more parameter configurations correspond to different RAT types.
9. The method according to claim 5, wherein, The method further includes: When the terminal device is camped in the cell of the first network device and the first indication information indicates that the RAT type includes the first RAT type, a second RRC connection request is sent to the first network device to enable the terminal device to establish an RRC connection with the first network device.
10. The method according to any one of claims 5 to 9, wherein, The method further includes: When the terminal device is camped in at least the cell of the first network device and the second network device, according to the first method, it is determined to listen to the first paging information in the cell of the first network device or the second network device.
11. The method according to claim 10, wherein, The first method includes one or more of the following: Predefined configuration methods; Implementation based on the terminal device; Determined based on the monitoring periods of the at least two neighboring cells; Network configuration.
12. The method according to claim 5, wherein, The method further includes: When the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type, a third RRC connection request is sent to the first network device.
13. The method according to claim 12, wherein, The third RRC connection request includes: A cause value, which includes information indicating the RAT type associated with the first paging message. The measurement report includes measurement results from one or more neighboring cells of the second RAT type.
14. The method according to claim 12 or 13, wherein, The method further includes: Obtain the second RRC connection information sent by the first network device, and based on the second RRC connection information, connect it with the first... Two network devices establish an RRC connection; wherein, the second RRC connection information includes: handover configuration information related to the second network device.
15. The method according to claim 12, wherein, The method further includes: In response to the third RRC connection information sent by the first network device in response to the third RRC connection request, a first RRC connection completion information is sent to the first network device; wherein, the first RRC connection completion information includes: information indicating the RAT type associated with the first paging information and a measurement report.
16. The method according to claim 15, wherein, The method further includes: The terminal device receives a first handover instruction sent by the first network device to establish an RRC connection with the second network device; the first handover instruction includes handover configuration information related to the second network device.
17. The method according to claim 5, wherein, The method further includes: Receive RRC dedicated information sent by the first network device; the RRC dedicated information carries the first indication information.
18. The method according to claim 17, wherein, The method further includes: When the terminal device is camped in the cell of the first network device, and the RAT type indicated by the first indication information includes the second RAT type, it is determined whether the terminal device should establish a connection with the network associated with the second RAT type based on the terminal capabilities and / or current service requirements.
19. The method according to claim 18, wherein, The step of determining whether the terminal device establishes a connection with the network associated with the second RAT type based on terminal capabilities and / or current service requirements includes one or more of the following: If the terminal capability supports a single RAT connection, and the priority of the second RAT type is lower than that of the first RAT type, then it is determined that the terminal device maintains a connection with the network associated with the first RAT type. If the terminal capability supports a single RAT connection, and the priority of the second RAT type is higher than the priority of the first RAT type, then it is determined that the terminal device establishes a connection with the network associated with the second RAT type. When the UE capability supports multiple RAT connections, it is determined that the terminal device establishes a connection with the network associated with the second RAT type, or the terminal device establishes a connection with the networks associated with both the first network device and the second network device simultaneously.
20. The method according to claim 18, wherein, The method further includes: If it is determined that the terminal device has established a connection with the network associated with the second RAT type, a first handover instruction is sent to the first network device; the first handover instruction includes: connection method and / or network measurement information associated with the second RAT type. In response to the first switching command, the device switches from the first network device to the second network device, or establishes a connection with both the first network device and the second network device simultaneously.
21. The method according to claim 18, wherein, The method further includes: If it is determined that the terminal device has established a connection with the network associated with the second RAT type, the connection with the second network device is triggered, and the connection with the first network device may or may not be disconnected.
22. The method according to claim 18, wherein, The method further includes: When the terminal device establishes connections with the networks associated with both the first network device and the second network device, the transmitter and / or receiver are switched between the networks associated with the first network device and the second network device in a time-division multiplexing (TDM) manner. The switching of the transmitter and / or receiver in a TDM manner is related to the user's capabilities and / or service characteristics.
23. The method according to claim 22, wherein, The method further includes: Send a second handover instruction to the first network device; the second handover instruction includes: relevant information of the second network device, and / or, handover time, and / or, handover cycle.
24. The method according to claim 5, wherein, The indication information includes second indication information, which is used to indicate the RAT type associated with the current PDU session.
25. The method according to claim 24, wherein, The second indication information is forwarded by the first network device from the core network.
26. The method according to claim 24 or 25, wherein, The method further includes: When the terminal device is camped in the cell of the first network device and the terminal device establishes an RRC connection with the first network device, if the second indication information indicates that the RAT type associated with the current PDU session includes the second RAT type, then the connection method between the terminal device and the second network device is determined according to the current service connection status.
27. The method according to claim 5, wherein, The indication information includes third indication information, which is used to indicate the connection method between the terminal device and the second RAT type.
28. The method according to claim 27, wherein, The acquisition of indication information includes: Obtain the third indication information sent by the first network device; the third indication information is related to the current service connection status.
29. The method according to any one of claims 20, 26, and 27, wherein, The connection methods include: dual protocol stack connection, and / or, switching connection.
30. The method according to claim 29, wherein, The method further includes: When the connection method is the dual protocol stack connection, cell reselection is triggered, and a fourth RRC connection request is sent to the second network device of the reselected cell so that the terminal device can establish an RRC connection with the second network device.
31. The method according to claim 30, wherein, The method further includes: When the connection method is the dual protocol stack connection or the switching connection, a measurement report is sent to the first network device. The measurement report is used by the terminal device to establish an RRC connection with the second network device.
32. The method according to any one of claims 23 to 31, wherein the method further comprises: When the terminal device is camped in the cell of the first network device, it obtains the second paging information sent by the first network device; In response to the second paging message, an RRC connection is established with the first network device.
33. The method according to any one of claims 15 to 32, wherein, The method further includes: Receive a second handover instruction sent by the first network device, the second handover instruction including handover configuration information related to the second network device; In response to the second handover command, the device switches from the first network device to the second network device, or establishes a connection with both the first network device and the second network device simultaneously.
34. The method according to any one of claims 1 to 33, wherein, The terminal device is connected to the first network device, is idle, or is inactive.
35. A communication method applied to a first network device, the method comprising: Send indication information to the terminal device; wherein the indication information is used to indicate relevant information about the wireless access technology (RAT) type that has a connection requirement with the terminal device.
36. The method according to claim 35, wherein, The indication information includes first indication information, which includes the RAT type corresponding to the Radio Resource Control (RRC) connection.
37. The method of claim 36, wherein, The method further includes: Send a first paging message to the terminal device; the first paging message carries the first indication information.
38. The method according to claim 36 or 37, wherein, The first indication information includes one or more of the following: RAT type identifier; The identifier of the terminal device varies depending on the RAT type. Public Land Mobile Network (PLMN) information.
39. The method according to any one of claims 35 to 38, wherein, The terminal device is at least camped in the cell of the first network device, the first network device is associated with a first RAT type, the second network device is associated with a second RAT type, the first RAT type and the second RAT type are different, and the terminal device is at least associated with the second network device of the second RAT type in a non-connected state.
40. The method according to claim 39, wherein, The method further includes: When the terminal device is camped in the cell of the first network device and the RAT type indicated by the first indication information includes the second RAT type, a third RRC connection request sent by the terminal device is received.
41. The method according to claim 40, wherein, The third RRC connection request includes: A cause value, which includes information indicating the RAT type associated with the first paging message. The measurement report includes measurement results from one or more neighboring cells of the second RAT type.
42. The method according to claim 40 or 41, wherein, The method further includes: Send second RRC connection information to the terminal device to enable the terminal device to establish an RRC connection with the second network device; wherein, the second RRC connection information includes: handover configuration information related to the second network device.
43. The method according to claim 40, wherein, The method further includes: The terminal device receives a first RRC connection completion message; wherein the first RRC connection completion message includes: information indicating the RAT type associated with the first paging message and a measurement report.
44. The method according to claim 43, wherein, The method further includes: A first handover instruction is sent to the terminal device to enable the terminal device to establish an RRC connection with the second network device; the first handover instruction includes handover configuration information related to the second network device.
45. The method according to any one of claims 40 to 44, wherein, The method further includes: The second network device is determined based on the cause value and the measurement report.
46. The method according to claim 39, wherein, The method further includes: Send RRC-specific information to the terminal device; the RRC-specific information carries the first indication information.
47. The method according to claim 46, wherein, The method further includes: When the terminal device is camped in the cell of the first network device, and the RAT type indicated by the first indication information includes the second RAT type, if the terminal device determines that a connection has been established with the network associated with the second RAT type, the terminal device receives a first handover indication sent by the terminal device; the first handover indication includes: connection method and / or network measurement information associated with the second RAT type.
48. The method according to claim 46, wherein, When the terminal device is camped in the cell of the first network device, and the RAT type indicated by the first indication information includes the second RAT type, if the terminal device establishes a connection with the networks associated with both the first network device and the second network device, then the terminal device receives a second handover indication sent by the terminal device; the second handover indication includes: relevant information of the second network device, and / or, handover time, and / or, handover cycle.
49. The method according to claim 39, wherein, in, The indication information includes second indication information, which is used to indicate the RAT type associated with the current PDU session.
50. The method according to claim 49, wherein, The second instruction information is issued by the core network.
51. The method according to claim 39, wherein, The indication information includes third indication information, which is used to indicate the connection method between the terminal device and the second RAT type; the third indication information is related to the current service connection status.
52. The method according to claim 51, wherein, The method further includes: Receive the fourth indication information sent by the core network; the fourth indication information is used to indicate the RAT type associated with the current PDU session; Based on the fourth instruction information and the current service connection status, the third instruction information is determined.
53. The method according to claim 51 or 52, wherein, The connection methods include: dual protocol stack connection, and / or, switching connection.
54. The method according to claim 53, wherein, The method further includes: When the connection method is the dual protocol stack connection or the switching connection, a measurement report sent by the terminal device is received. The measurement report is used by the terminal device to establish an RRC connection with the second network device.
55. The method according to any one of claims 49 to 54, wherein, The method further includes: When the terminal device is camped in the cell of the first network device, a second paging message is sent to the terminal device.
56. The method according to any one of claims 43 to 55, wherein, The method further includes: A second handover instruction is sent to the terminal device. The first handover instruction includes handover configuration information related to the second network device, so that the terminal device responds to the second handover request and switches from the first network device to the second network device, or establishes a connection with both the first network device and the second network device simultaneously.
57. The method according to any one of claims 35 to 56, wherein, The terminal device is connected to the first network device, is idle, or is inactive.
58. A communication device, the device comprising: The first communication unit is configured to acquire indication information; wherein the indication information is used to indicate information related to the Radio Access Technology (RAT) type that has a connection requirement with the terminal device.
59. A communication device, the device comprising: The second communication unit is configured to send indication information to the terminal device; wherein the indication information is used to indicate relevant information about the wireless access technology (RAT) type that has a connection requirement with the terminal device.
60. A communication device, the communication device comprising: Memory, used to store computer programs; A processor, connected to the memory, is configured to retrieve and run the computer program from the memory to implement the method of any one of claims 1 to 33, or to implement the method of any one of claims 34 to 55; A transceiver is used to receive and send information when exchanging information with other external devices.
61. A chip, the chip comprising: Memory, used to store computer programs; A processor, connected to the memory, is configured to retrieve and run a computer program from the memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 34, or to perform the method as described in any one of claims 35 to 57; A transceiver is used to receive and send information during the exchange of information with a device or chip.
62. A computer-readable storage medium storing a computer program that, when executed by at least one processor, implements the method as claimed in any one of claims 1 to 34, or implements the method as claimed in any one of claims 35 to 57.
63. A computer program product comprising a computer program or instructions which, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 34; or implement the steps of the method as claimed in any one of claims 35 to 57.
64. A computer program comprising computer program instructions that, when executed by a processor, implement the method as claimed in any one of claims 1 to 34, or implement the method as claimed in any one of claims 35 to 57.
Citation Information
Patent Citations
User mode indication method and service management method and device
CN101272521A
System and method for communicating radio access technology characteristics
CN113424647A
Method for accessing inter-rat cell and related device
US20190159075A1
UE-Controlled Selection Between Inter-RAT Handover and Inter-RAT Dual Connectivity
US20220240145A1
Information transmission method and apparatus
US20230300722A1