Communication method and communication device
Patent Information
- Application Number
- CN202280094557.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-09-30
- Publication Date
- 2024-11-12
AI Technical Summary
The energy consumption of communication networks is gradually increasing and has become an important part of operators' operating costs. It is difficult for existing technologies to effectively reduce energy consumption.
By introducing a terminal device capability indication mechanism into the communication system, the network device determines the paging strategy based on the received information, reduces unnecessary paging message transmission, and reduces the power consumption of the terminal device.
It effectively reduces the energy consumption of the communication system, reduces false paging alarms, and improves system efficiency.
Smart Images

Figure CN118947187A_ABST
Abstract
Description
Communication method and communication device Technical Field
[0001] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art
[0002] With the development of communication technology, the energy consumption of communication networks has become increasingly high, becoming an important part of operators' operating costs. Therefore, how to reduce the energy consumption of communication networks has become a technical problem that needs to be solved urgently.
[0003] Summary of the Invention
[0004] The embodiments of the present application provide a communication method and a communication device. The following describes various aspects of the embodiments of the present application.
[0005] In a first aspect, a communication method is provided, including: a first network device receives first information, where the first information indicates whether a first terminal device supports a first capability.
[0006] In a second aspect, a communication method is provided, including: an access and mobility management function AMF network element sends first information to a first network device, wherein the first information indicates whether the first terminal device supports a first capability.
[0007] According to a third aspect, a communication method is provided, comprising: a second network device sends first information to a first network device, wherein the first information indicates whether the first terminal device supports a first capability.
[0008] In a fourth aspect, a communication method is provided, including: a first network device receives third information sent by a second network device, the third information indicating any one of the following: whether the second network device allows terminal devices that support a first capability to access, whether the second network device supports terminal devices with the first capability, whether the second network device allows terminal devices that do not support the first capability to access, and whether the second network device supports terminal devices that do not support the first capability.
[0009] In a fifth aspect, a communication method is provided, including: a second network device sends third information to a first network device, the third information indicating any one of the following: whether the second network device allows terminal devices that support a first capability to access, whether the second network device supports terminal devices with the first capability, whether the second network device allows terminal devices that do not support the first capability to access, and whether the second network device supports terminal devices that do not support the first capability.
[0010] In a sixth aspect, a communication apparatus is provided, comprising: a receiving unit configured to receive first information, wherein the first information indicates whether a first terminal device supports a first capability.
[0011] In a seventh aspect, a communication device is provided, comprising: a sending unit, configured to send first information to a first network device, wherein the first information indicates whether the first terminal device supports a first capability.
[0012] In an eighth aspect, a communication apparatus is provided, comprising: a sending unit, configured to send first information to a first network device, wherein the first information indicates whether the first terminal device supports a first capability.
[0013] In the ninth aspect, a communication device is provided, including: a receiving unit, used to: receive third information sent by a second network device, the third information indicating any one of the following: whether the second network device allows terminal devices that support a first capability to access, whether the second network device supports terminal devices with the first capability, whether the second network device allows terminal devices that do not support the first capability to access, and whether the second network device supports terminal devices that do not support the first capability.
[0014] In the tenth aspect, a communication device is provided, including: a sending unit, used to: send third information to a first network device, the third information indicating any one of the following: whether the device allows terminal devices that support a first capability to access, whether the device supports terminal devices with the first capability, whether the device allows terminal devices that do not support the first capability to access, and whether the device supports terminal devices that do not support the first capability.
[0015] In the eleventh aspect, a communication device is provided, comprising a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method described in the first aspect.
[0016] In the twelfth aspect, a communication device is provided, comprising a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method described in the second aspect.
[0017] In a thirteenth aspect, a communication device is provided, comprising a processor for calling a program from a memory so that the communication device executes the method described in the first aspect.
[0018] In a fourteenth aspect, a communication device is provided, comprising a processor for calling a program from a memory so as to execute the method described in the second aspect with the communication device.
[0019] In a fifteenth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect.
[0020] In a sixteenth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the second aspect.
[0021] In the seventeenth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in the first aspect.
[0022] In an eighteenth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in the second aspect.
[0023] In the nineteenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in the first aspect.
[0024] In the twentieth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in the second aspect.
[0025] In the twenty-first aspect, a computer program is provided, which enables a computer to execute the method described in the first aspect.
[0026] In aspect 22, a computer program is provided, which enables a computer to execute the method described in aspect 2.
[0027] In an embodiment of the present application, the first information indicates whether the first terminal device supports the first capability. The first network device receives the first information so that the first network device can determine the paging strategy based on the first information, thereby helping to reduce the power consumption of the communication system. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] FIG1 is an example diagram of a wireless communication system used in an embodiment of the present application.
[0029] FIG2 is a schematic flowchart of a communication method provided in one embodiment of the present application.
[0030] FIG3 is a schematic flowchart of a communication method provided in another embodiment of the present application.
[0031] FIG4 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.
[0032] FIG5 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.
[0033] FIG6 is a schematic structural diagram of a communication device provided in one embodiment of the present application.
[0034] FIG7 is a schematic structural diagram of a communication device provided in another embodiment of the present application.
[0035] FIG8 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.
[0036] FIG9 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.
[0037] FIG10 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.
[0038] FIG11 is a schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0039] The technical solution in this application will be described below with reference to the accompanying drawings.
[0040] FIG1 illustrates a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a user equipment (UE) 120. The network device 110 may communicate with the UE 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the UE 120 within the coverage area. The UE 120 may access a network (e.g., a wireless network) through the network device 110.
[0041] Figure 1 exemplarily shows a network device and two UEs. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include a different number of terminal devices within its coverage area, which is not limited in this embodiment of the present application. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment of the present application.
[0042] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.
[0043] The UE in the embodiments of the present application may also be referred to as a terminal device, an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The UE in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device or an in-vehicle device with wireless connection capabilities. The UE in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.
[0044] The network device in the embodiments of the present application may be a device for communicating with a UE, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a UE to a wireless network. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof.
[0045] In some embodiments, the network device can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile network device, and one or more cells can move according to the location of the mobile network device. In other examples, the helicopter or drone can be configured to act as a device for communicating with another network device. In some embodiments, the network device can refer to a CU or a DU, or the network device can include a CU and a DU, or the network device can also include an AAU.
[0046] It should be understood that network devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water; and can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the network devices and the scenarios in which they are used.
[0047] It should also be understood that all or part of the functions of the network device and UE in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).
[0048] With the increasing demand for speed, latency, high-speed mobility, and energy efficiency, coupled with the increasing diversity and complexity of future services, the 3rd Generation Partnership Project (3GPP), an international standards organization, has begun developing 5G. The main application scenarios for 5G are enhanced mobile broadband (eMBB), ultra reliable low latency communications (URLLC), and massive machine-type communications (mMTC).
[0049] Among them, eMBB aims to provide users with multimedia content, services, and data, and demand for it is growing rapidly. However, since eMBB can be deployed in different scenarios, such as indoors, in urban areas, and in rural areas, its capabilities and requirements vary significantly in each scenario, requiring detailed analysis based on the specific deployment scenario. Typical applications of URLLC include industrial automation, power automation, remote medical operations (such as surgery), and traffic safety. Typical characteristics of mMTC include high connection density, small data volumes, latency-insensitive services, low module cost, and long service life.
[0050] NR can be deployed independently. In order to reduce air interface signaling and quickly restore wireless connections and data services in the 5G network environment, a new radio resource control (RRC) state is defined, namely the RRC inactive (RRC_INACTIVE) state. This state is different from the RRC idle (RRC_IDLE) state and the RRC connected (RRC_ACTIVE) state.
[0051] RRC_IDLE: Mobility is based on UE cell reselection. Paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no UE access stratum (AS) context on the base station side. There is no RRC connection.
[0052] RRC_CONNECTED: An RRC connection exists, and a UE AS context exists between the eNodeB and the UE. The network knows the UE's location at the cell level. Mobility is controlled by the network. Unicast data can be transmitted between the UE and the eNodeB.
[0053] RRC_INACTIVE: Mobility is UE-based cell reselection. There is a connection between the core network and the access network (such as the core network-new RAN (CN-NR)). The UE AS context exists on a base station. Paging is triggered by the RAN. The RAN-based paging area is managed by the RAN. The network side knows the UE location at the RAN paging area level.
[0054] When in the RRC_INACTIVE state, the UE will automatically return to the RRC_IDLE state in the following situations:
[0055] When receiving the CN initial paging message; when initiating the RRC recovery request, starting timer T319, if the timer times out; when the integrity protection verification of message 4 (MSG4) fails; when the cell reselects to another radio access technology (radio access technology, RAT); entering the camp on any cell state.
[0056] The RRC_INACTIVE state includes the following characteristics:
[0057] The connection between the RAN and the CN is maintained; the UE and at least one base station store the AS context; the UE is reachable from the RAN side, and the relevant parameters are configured by the RAN; when the UE moves within the radio access network notification area (RAN notification area, RNA) configured by the RAN, the network side does not need to be notified, but when it moves out of the RNA, the network side needs to be notified; the UE moves within the RNA according to the cell selection reselection method.
[0058] The following is a brief introduction to the paging mechanism in the NR system. Currently, the NR system can support CN-triggered paging and RAN-triggered paging.
[0059] Among them, the paging triggered by the CN is initiated by the access and mobility management function (AMF) network element, which pages the UE in the entire registration area. That is, the AMF sends a paging message (S1 interface application protocol (S1AP) message) to the gNBs in the entire registration area, and then the gNBs send paging messages in their respective cells.
[0060] RAN-triggered paging is initiated by the UE's anchor gNB, which pages the UE within the entire RAN notification area. That is, the anchor gNB sends a RAN paging message (Xn application protocol (XnAP) message) to the gNBs within the RAN notification area. The gNBs send paging messages within their respective cells.
[0061] With the continuous development of communication technology, the energy consumption of communication networks has increased significantly, becoming a significant component of operators' operating costs. According to a report by the Global System for Mobile Communications Association (GSMA), mobile network energy costs account for approximately 23% of operators' total costs. The majority of this energy consumption comes from radio access networks, particularly active antenna units (AAUs), while data centers and fiber optic transmission only contribute to a smaller share. Communication network energy consumption primarily comes from the following two sources:
[0062] Dynamic part: such as consumption during data transmission / reception;
[0063] Static part: such as the consumption required to maintain the operation of the wireless access device even when there is no continuous data transmission / reception.
[0064] The report should not only evaluate the potential network energy consumption benefits, but also evaluate and balance the impact on network and user performance. However, the report should not have a particularly large impact on some KPIs, such as: spectrum efficiency, capacity, user perceived throughput (UE perceived throughput, UPT), latency, UE power consumption, complexity, handover performance, call drop rate, initial access performance, etc.
[0065] To reduce costs and power consumption, some communication systems introduce reduced capability (RedCap) terminal devices. RedCap terminal devices can be used in the following scenarios:
[0066] 1. Industrial wireless sensors:
[0067] Compared with URLLC, industrial wireless sensors have relatively low latency and reliability requirements. At the same time, the cost and power consumption of such devices are also lower than URLLC and eMBB.
[0068] 2. Video surveillance:
[0069] It is mainly used in video surveillance of smart cities, industrial factories, etc. For example, it can be used for data collection and processing in smart cities to more effectively monitor and control urban resources and provide more effective services to urban residents.
[0070] 3. Wearables
[0071] Including smart watches, phones, electronic health devices and some medical monitoring devices, etc. One common feature of these devices is their small size.
[0072] For RedCap terminal devices, energy saving is a very important technical indicator, especially for industrial wireless sensors and other equipment.
[0073] In Release 17 (R17) of the NR system, RedCap terminals have the following bandwidth limitations:
[0074] For frequency range 1 (FR1), the maximum supported bandwidth is 20 MHz.
[0075] For frequency range 2 (FR2), the maximum supported bandwidth is 100 MHz.
[0076] This maximum bandwidth includes the radio frequency (RF) bandwidth and the baseband (BB) bandwidth.
[0077] In Release 18 (R18) of the NR system, a further low-complexity and low-cost design was introduced for RedCap UEs supporting the FR1 frequency band. For example, the baseband bandwidth can be reduced to 5 MHz, and this 5 MHz baseband bandwidth is only for the physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH), while the RF bandwidth can remain unchanged at 20 MHz.
[0078] For RedCap terminals (such as eRedCap terminals) that only support 5MHz baseband bandwidth (i.e., cannot support baseband bandwidth exceeding 5MHz), the network may not want to limit the PDSCH transmission bandwidth in order to serve such RedCap terminals. In this case, such a network will not allow RedCap terminals that only support 5MHz baseband bandwidth to access.
[0079] Similarly, in order to cooperate with network energy saving, UEs in energy-saving networks that support certain specific network energy-saving features need to have the capabilities of these specific network energy-saving features. If the UE does not have the capabilities of these specific network energy-saving features, it cannot access the energy-saving network. For example, the network energy-saving feature may include that the network equipment in the energy-saving network does not send a synchronization signal block (SSB). The UE in the energy-saving network can be synchronized in other ways. At this time, if the UE does not have this feature, it may not be able to synchronize with the energy-saving network. Therefore, the UE that does not have this feature may not be able to access the energy-saving network. Similarly, the network energy-saving feature may also include that the network equipment does not send broadcast messages, etc., or may also include other features that can reduce network power consumption, which is not limited in the embodiments of the present application.
[0080] In the prior art, regardless of whether a paging message is received from the AMF or the anchor gNB, the base station that receives the paging message directly forwards the paging message. Therefore, for cells that do not allow RedCap terminals that only support 5MHz baseband bandwidth to access, since terminals that only support 5MHz baseband bandwidth cannot reside in the cell, sending paging messages to such terminals in the cell is redundant. This not only wastes paging resources, but also increases false alarms for other terminals, leading to increased terminal power consumption (because other terminals sharing the PO need to decode the PDSCH to determine that the paging message is not sent to them).
[0081] Similarly, for energy-saving networks, if the UE being paged does not have the network energy-saving feature, it is unnecessary for the energy-saving network to send a paging message to this UE, which will also increase paging false alarms for other UEs.
[0082] In order to solve one or more of the above technical problems, the present application proposes a communication method and a communication device.
[0083] The embodiments of the present application are described in detail below with reference to FIG. 2 to FIG. 5 .
[0084] FIG2 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 200 shown in FIG2 may include step S210, which is as follows:
[0085] S210: A first network device receives first information.
[0086] The first information may indicate whether the first terminal device supports the first capability.
[0087] The first information may be for a target frequency band, or for all frequency bands. In other words, the first information may be an indication corresponding to a certain frequency band (per band), or may be an indication regardless of frequency band.
[0088] The first capability may include at least one of the following: a RedCap terminal, a RedCap terminal having only a 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or the physical uplink shared channel PUSCH, a RedCap terminal having only a 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or the physical uplink shared channel PUSCH, a RedCap terminal having only a 5MHz baseband bandwidth capability, and a network energy-saving capability. The network energy-saving capability may refer to, but is not limited to, the network energy-saving characteristics described in the aforementioned embodiments. For example, the network energy-saving capability may include, but is not limited to: the network device not sending SSB, the network device not sending broadcast messages, etc.
[0089] It should be noted that the RedCap terminal in the embodiment of the present application may be an eRedCap terminal, wherein the eRedCap terminal may refer to (but is not limited to) a RedCap terminal with lower complexity and lower cost.
[0090] Optionally, the method 200 may further include step S220, which is as follows:
[0091] S220: The first network device determines a paging strategy according to the first information.
[0092] Optionally, the paging policy may include whether the first network device sends a paging message to the first terminal device.
[0093] In some embodiments, the first network device may determine whether to send a first paging message to the first terminal device based on the first information and whether the first network device allows access by a terminal device supporting the first capability.
[0094] Specifically, if the first terminal device supports the first capability and the first network device does not allow the terminal device supporting the first capability to access, the first network device may determine not to send the first paging message to the first terminal device.
[0095] If the first terminal device supports the first capability and the first network device allows the terminal device supporting the first capability to access, the first network device may determine to send a first paging message to the first terminal device.
[0096] For example, take the example of the first information indicating whether the first terminal device has only 5MHz baseband (BB) bandwidth capability for PDSCH and PUSCH: if the first terminal device has only 5MHz BB bandwidth capability for PDSCH and PUSCH, and the first network device does not support or allow terminal devices that only have 5MHz BB bandwidth capability for PDSCH and PUSCH to access, then the first network device determines not to send a paging message to the UE in its corresponding cell, or the paging message sent in the cell does not include the paging identifier (ID) of the first terminal device; if the first terminal device has only 5MHz BB bandwidth capability for PDSCH and PUSCH, and the first network device supports or allows terminal devices that only have 5MHz BB bandwidth capability for PDSCH and PUSCH to access, then the first network device determines to send a paging message to the first terminal device in its corresponding cell, that is, the paging message sent in the cell includes the paging ID of the first terminal device, and in implementation (such as during communication), ensure that the PDSCH bandwidth corresponding to the paging message sent to the first terminal device does not exceed 5HMz.
[0097] In some embodiments, the first network device may determine whether to send a paging message to the first terminal device based on the first information and whether the first network device allows access by a terminal device that does not support the first capability.
[0098] Specifically, if the first terminal device does not support the first capability and the first network device does not allow terminal devices that do not support the first capability to access, the first network device may determine not to send the first paging message to the first terminal device.
[0099] If the first terminal device does not support the first capability and the first network device allows access by terminal devices that do not support the first capability, the first network device may determine to send a first paging message to the first terminal device.
[0100] For example, take the example of the first information indicating whether the first terminal device supports network energy-saving capability: if the first terminal device does not support network energy-saving capability (that is, the first terminal device is a "non-network energy-saving" terminal), and the first network device does not allow terminal devices that do not support network energy-saving capability to access, then the first network device determines not to send a paging message to the first terminal device in its corresponding cell, or the paging message sent in the cell does not include the paging ID of the first terminal device; if the first terminal device does not support network energy-saving capability, and the first network device allows terminal devices that do not support network energy-saving capability to access, then the first network device determines to send a paging message to the first terminal device in its corresponding cell, that is, the paging message sent in the cell includes the paging ID of the first terminal device.
[0101] In an embodiment of the present application, by introducing terminal capability indication (such as the terminal's baseband bandwidth capability and / or non-network energy-saving capability indication) in the NG interface and Xn interface messages, the base station that does not support access of 5MHz baseband bandwidth UE and / or non-network energy-saving UE can save the sending of paging messages, thereby reducing paging false alarms of other terminal devices and avoiding an increase in terminal power consumption. Therefore, the energy consumption of the communication system can be reduced.
[0102] In S210 of the above embodiment, the first information received by the first network device may be sent by the AMF network element (introducing the terminal capability indication (such as the first information) in the NG interface message between the network device and the AMF network element as shown in FIG3 ), or may be sent by the second network device (introducing the terminal capability indication (such as the first information) in the Xn interface message between the network devices as shown in FIG4 ), which will be explained below in conjunction with FIG3 and FIG4 respectively.
[0103] FIG3 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 300 shown in FIG3 may include step S310, which is as follows:
[0104] S310, the AMF network element sends the first information to the first network device.
[0105] For example, the AMF network element may send the first information to the first network device via an initial context setup request (INITIAL CONTEXT SETUP REQUEST) message or a second paging message.
[0106] The initial context establishment request message or the second paging message may include a first information element (IE), and the first information may be carried in the first IE.
[0107] Optionally, the first IE may be a terminal radio paging information (UERadioPagingInformation) IE in the initial context establishment request message or the second paging message. Alternatively, the first IE may also be other IEs in the initial context establishment request message or the second paging message.
[0108] Alternatively, the first information may also be carried in other fields in the initial context establishment request message or the second paging message.
[0109] Optionally, before step S310, the method 300 may further include step S320, which is as follows:
[0110] S320, the third network device sends the second information to the AMF network element.
[0111] The second information may indicate whether the first terminal device supports the first capability.
[0112] The third network device may be a network device that the first terminal device previously connected to. For example, before executing method 300, the first terminal device may have disconnected from the third network device or switched to the third network device. The third network device may store the AS context of the first terminal device, which may include whether the first terminal device supports the first capability.
[0113] The third network device may send the second information to the AMF network element through a terminal radio capability information indication (UE RADIO CAPABILITY INFO INDICATION) message.
[0114] The terminal wireless capability information indication message may include a second IE, and the second information may be carried in the second IE.
[0115] Optionally, the second IE may be a terminal radio paging information (UERadioPagingInformation) IE in the terminal radio capability information indication message. Alternatively, the second IE may be other IEs in the terminal radio capability information indication message.
[0116] Alternatively, the second IE may also be carried in other fields of the terminal wireless capability information indication message.
[0117] Optionally, after S310, the method 300 may further include step S330, which is as follows:
[0118] S330: The first network device determines a paging strategy according to the first information.
[0119] The specific method for the first network device to determine the paging strategy according to the first information may refer to S220 in the aforementioned method 200.
[0120] Optionally, as shown in FIG3 , when it is determined to send the first paging message to the first terminal device, the first network device may send the first paging message to the first terminal device.
[0121] FIG4 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 400 shown in FIG4 may include step S410, which is as follows:
[0122] S410: The second network device sends first information to the first network device.
[0123] For example, the second network device may be an anchor network device (such as an anchor gNB) of the first terminal device.
[0124] For example, the second network device may send the first information to the first network device through a third paging message (RAN paging message).
[0125] The third paging message may include a first information element IE, and the first information may be carried in the first IE.
[0126] The first IE may be a terminal radio paging information (UERadioPagingInformation) IE in the third paging message. Alternatively, the first IE may also be other IEs in the third paging message.
[0127] Alternatively, the first information may also be carried in other fields in the third paging message.
[0128] Optionally, after S410, the method 400 may further include step S420, which is as follows:
[0129] S420: The first network device determines a paging strategy according to the first information.
[0130] The specific method for the first network device to determine the paging strategy according to the first information may refer to S220 in the aforementioned method 200.
[0131] Optionally, as shown in FIG4 , when it is determined to send the first paging message to the first terminal device, the first network device may send the first paging message to the first terminal device.
[0132] This application also provides a communication method, which introduces a network indication (such as the third information in FIG5 ) into an Xn interface message between network devices, so that the network device can perform mobility management on the terminal device according to the network indication.
[0133] FIG5 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 500 shown in FIG5 may include step S510, which is as follows:
[0134] S510: The second network device sends third information to the first network device.
[0135] Among them, the third information can indicate any of the following items: whether the second network device allows terminal devices that support the first capability to access, whether the second network device supports terminal devices with the first capability, whether the second network device allows terminal devices that do not support the first capability to access, and whether the second network device supports terminal devices that do not support the first capability.
[0136] The third information may be for the number of target receive RF channels (such as UE Rx branches), or the third information may be for the number of all receive RF channels. That is, the third information may be indicated based on different numbers of UE Rx branches, such as based on 1Rx branch and 2Rx branches, or the third information may not distinguish the number of receive RF channels.
[0137] The first capability may include at least one of the following: a RedCap terminal, a RedCap terminal having only a 5 MHz baseband bandwidth capability for a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH), a RedCap terminal having only a 5 MHz baseband bandwidth capability for a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH), a RedCap terminal having only a 5 MHz baseband bandwidth capability, a RedCap terminal having only a 5 MHz baseband bandwidth capability, and a network energy-saving capability. The network energy-saving capability may refer to, but is not limited to, the network energy-saving features described in the aforementioned embodiments. For example, the network energy-saving capability may include: a network device not sending SSB, a network device not sending broadcast messages, etc.
[0138] It should be noted that the RedCap terminal in the embodiment of the present application may be an eRedCap terminal, wherein the eRedCap terminal may refer to (but is not limited to) a RedCap terminal with lower complexity and lower cost.
[0139] For example, the third information may indicate any of the following: whether the second network device allows RedCap terminals to access, whether the second network device supports RedCap terminals, whether the second network device allows terminal devices or RedCap terminal devices that only have 5MHz bandwidth capability for PDSCH and PUSCH to access, and whether the second network device supports terminal devices or RedCap terminal devices that only have 5MHz bandwidth capability for PDSCH and PUSCH.
[0140] In S510, the second network device may send the third information to the first network device through at least one of the following messages:
[0141] Xn setup request (XN SETUP REQUEST) message, Xn setup response (XN SETUP RESPONSE) message, access network node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message.
[0142] Optionally, the above message may include a third IE, and the third information may be carried in the third IE.
[0143] Optionally, the third IE may be a serving cell information (Served Cell Information NR) IE. Alternatively, the third IE may be other IEs in the above message.
[0144] Optionally, the third information may be carried in a broadcast information (RedCap Broadcast Information) IE for low-capability terminals included in the serving cell information IE. Alternatively, the third information may also be carried in other IEs in the serving cell information IE.
[0145] Alternatively, the third information may also be carried in other fields in the above message.
[0146] Optionally, after S510, the method 500 may further include step S520, which is as follows:
[0147] S520: The first network device performs mobility management on the second terminal device according to the third information.
[0148] The first network device may determine a target cell for the second terminal device to move out of based on the third information. Optionally, the first network device may determine a suitable target cell for the second terminal device during handover and paging based on the third information, as shown in FIG5 . The second terminal device may support the first capability, or may not support the first capability.
[0149] For example: if the second terminal device supports the first capability and the second network device allows terminal devices supporting the first capability to access, the first network device can use the second network device as the target cell for the second terminal to move out; if the second terminal device supports the first capability and the second network device does not allow terminal devices supporting the first capability to access, the first network device determines not to use the second network device as the target cell for the second terminal to move out.
[0150] For another example: if the second terminal device does not support the first capability, and the second network device allows terminal devices that do not support the first capability to access, the first network device can use the second network device as the target cell for the second terminal to be moved out; if the second terminal device does not support the first capability, and the second network device does not allow terminal devices that do not support the first capability to access, the first network device determines not to use the second network device as the target cell for the second terminal to be moved out.
[0151] In an embodiment of the present application, by introducing network indications in the Xn interface message (such as the network's access control policy for terminals that only support 5HMz baseband bandwidth and / or non-network energy-saving terminals), the network device can determine the appropriate target cell when initiating paging or switching for such UEs. For non-connected UEs, unnecessary paging transmission can be reduced, and for connected UEs, the switching success rate can be improved, thereby reducing the energy consumption of the communication system.
[0152] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 5 . The device embodiment of the present application is described in detail below in conjunction with Figures 6 to 11 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.
[0153] FIG6 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG6 , the device 600 includes a receiving unit 610, which is specifically as follows:
[0154] The receiving unit 610 is used to receive first information, where the first information indicates whether the first terminal device supports a first capability.
[0155] Optionally, the receiving unit 610 is specifically used to: receive the first information sent by the access and mobility management function AMF network element.
[0156] Optionally, the receiving unit 610 is specifically used to: receive the first information sent by the AMF network element through an initial context establishment request message or a second paging message.
[0157] Optionally, the initial context establishment request message or the second paging message includes a first information element IE, and the first information is carried in the first IE.
[0158] Optionally, the receiving unit 610 is specifically configured to receive the first information sent by the second network device.
[0159] Optionally, the receiving unit 610 is specifically configured to: receive the first information sent by the second network device through a third paging message.
[0160] Optionally, the third paging message includes a first information element IE, and the first information is carried in the first IE.
[0161] Optionally, the first IE is a terminal wireless paging information IE.
[0162] Optionally, the first capability includes at least one of the following: low-capability RedCap terminal, low-capability RedCap terminal with only 5MHz baseband bandwidth capability for physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, low-capability RedCap terminal with only 5MHz baseband bandwidth capability for physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, low-capability RedCap terminal with only 5MHz baseband bandwidth capability, network energy saving capability.
[0163] Optionally, the first information is for a target frequency band.
[0164] Optionally, the apparatus 600 further includes a determining unit 620, configured to determine a paging strategy according to the first information.
[0165] Optionally, the determining unit 620 is specifically configured to determine whether to send a first paging message to the first terminal device according to the first information and whether the apparatus allows access by a terminal device supporting the first capability.
[0166] Optionally, the determination unit 620 is specifically used to: if the first terminal device supports the first capability and the apparatus does not allow terminal devices supporting the first capability to access, determine not to send a first paging message to the first terminal device; if the first terminal device supports the first capability and the apparatus allows terminal devices supporting the first capability to access, determine to send a first paging message to the first terminal device.
[0167] Optionally, the determining unit 620 is specifically configured to determine whether to send a first paging message to the first terminal device based on the first information and whether the apparatus allows access by a terminal device that does not support the first capability.
[0168] Optionally, the determination unit 620 is specifically used to: if the first terminal device does not support the first capability and the apparatus does not allow terminal devices that do not support the first capability to access, determine not to send a first paging message to the first terminal device; if the first terminal device does not support the first capability and the apparatus allows terminal devices that do not support the first capability to access, determine to send a first paging message to the first terminal device.
[0169] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG7 , the device 700 includes a sending unit 710, which is specifically as follows:
[0170] The sending unit 710 is used to send first information to the first network device, where the first information indicates whether the first terminal device supports the first capability.
[0171] Optionally, the sending unit 710 is specifically configured to: send the first information to the first network device through an initial context establishment request message or a second paging message.
[0172] Optionally, the initial context establishment request message or the second paging message includes a first information element IE, and the first information is carried in the first IE.
[0173] Optionally, the first IE is a terminal wireless paging information IE.
[0174] Optionally, the first capability includes at least one of the following: low-capability RedCap terminal, low-capability RedCap terminal with only 5MHz baseband bandwidth capability for physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, low-capability RedCap terminal with only 5MHz baseband bandwidth capability for physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, low-capability RedCap terminal with only 5MHz baseband bandwidth capability, network energy saving capability.
[0175] Optionally, the first information is for a target frequency band.
[0176] Optionally, the apparatus 700 further includes a receiving unit 720 configured to receive second information sent by a third network device, where the second information indicates whether the first terminal device supports the first capability.
[0177] Optionally, the receiving unit 720 is specifically configured to: receive the second information sent by the third network device through a terminal wireless capability information indication message.
[0178] Optionally, the terminal wireless capability information indication message includes a second information element IE, and the second information is carried in the second IE.
[0179] Optionally, the second IE is a terminal wireless paging information IE.
[0180] FIG8 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG8 , the device 800 includes a sending unit 810, which is specifically as follows:
[0181] The sending unit 810 is used to send first information to the first network device, where the first information indicates whether the first terminal device supports the first capability.
[0182] Optionally, the sending unit 810 is specifically configured to: send the first information to the first network device via a third paging message.
[0183] Optionally, the third paging message includes a first information element IE, and the first information is carried in the first IE.
[0184] Optionally, the first IE is a terminal wireless paging information IE.
[0185] Optionally, the first capability includes at least one of the following: low-capability RedCap terminal, low-capability RedCap terminal with only 5MHz baseband bandwidth capability for physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, low-capability RedCap terminal with only 5MHz baseband bandwidth capability for physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, low-capability RedCap terminal with only 5MHz baseband bandwidth capability, network energy saving capability.
[0186] Optionally, the first information is for a target frequency band.
[0187] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG9 , the device 900 includes a receiving unit 910, which is specifically as follows:
[0188] The receiving unit 910 is used to: receive third information sent by the second network device, where the third information indicates any one of the following: whether the second network device allows terminal devices that support the first capability to access, whether the second network device supports terminal devices with the first capability, whether the second network device allows terminal devices that do not support the first capability to access, and whether the second network device supports terminal devices that do not support the first capability.
[0189] Optionally, the receiving unit 910 is specifically configured to: receive the third information sent by the second network device through at least one of the following messages: an Xn establishment request message, an Xn establishment response message, and an access network node configuration update message.
[0190] Optionally, the message includes a third information element IE, and the third information is carried in the third IE.
[0191] Optionally, the third IE is a serving cell information IE.
[0192] Optionally, the third information is carried in a broadcast information IE for low-capability terminals included in the serving cell information IE.
[0193] Optionally, the apparatus 900 further includes a management unit 920, configured to perform mobility management on the second terminal device according to the third information.
[0194] Optionally, the management unit 920 is specifically configured to determine a suitable target cell for the second terminal device during the switching and paging process according to the third information.
[0195] Optionally, the second terminal device supports the first capability, or the second terminal device does not support the first capability.
[0196] Optionally, the first capability includes at least one of the following: low-capability RedCap terminal, low-capability RedCap terminal with only 5MHz baseband bandwidth capability for physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, low-capability RedCap terminal with only 5MHz baseband bandwidth capability for physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, low-capability RedCap terminal with only 5MHz baseband bandwidth capability, network energy saving capability.
[0197] Optionally, the third information is for the number of target receiving radio frequency channels.
[0198] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG10 , the device 1000 includes a sending unit 1010, which is specifically as follows:
[0199] The sending unit 1010 is used to send third information to the first network device, where the third information indicates any one of the following: whether the device allows terminal devices that support the first capability to access, whether the device supports terminal devices that do not support the first capability, whether the device allows terminal devices that do not support the first capability to access, and whether the device supports terminal devices that do not support the first capability.
[0200] Optionally, the sending unit 1010 is specifically configured to send the third information to the first network device via at least one of the following messages: an Xn establishment request message, an Xn establishment response message, and an access network node configuration update message.
[0201] Optionally, the message includes a third information element IE, and the third information is carried in the third IE.
[0202] Optionally, the third IE is a serving cell information IE.
[0203] Optionally, the third information is carried in a broadcast information IE for low-capability terminals included in the serving cell information IE.
[0204] Optionally, the first capability includes at least one of the following: low-capability RedCap terminal, low-capability RedCap terminal with only 5MHz baseband bandwidth capability for physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, low-capability RedCap terminal with only 5MHz baseband bandwidth capability for physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, low-capability RedCap terminal with only 5MHz baseband bandwidth capability, network energy saving capability.
[0205] Optionally, the third information is for the number of target receiving radio frequency channels.
[0206] FIG11 is a schematic diagram of the structure of an apparatus provided in one embodiment of the present application. The dotted lines in FIG11 indicate that the unit or module is optional. Apparatus 1100 may be used to implement the method described in the above method embodiment. Apparatus 1100 may be a chip or a communication device.
[0207] The device 1100 may include one or more processors 1110. The processor 1110 may support the device 1100 to implement the method described in the method embodiment above. The processor 1110 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
[0208] The apparatus 1100 may further include one or more memories 1120. The memories 1120 store programs that can be executed by the processor 1110, causing the processor 1110 to perform the methods described in the above method embodiments. The memories 1120 may be independent of the processor 1110 or integrated into the processor 1110.
[0209] The apparatus 1100 may further include a transceiver 1130. The processor 1110 may communicate with other devices or chips via the transceiver 1130. For example, the processor 1110 may transmit and receive data with other devices or chips via the transceiver 1130.
[0210] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present application, and the program enables a computer to execute the method performed by the communication device in each embodiment of the present application.
[0211] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the present application, and the program causes a computer to execute the method performed by the communication device in each embodiment of the present application.
[0212] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided in the embodiments of the present application, and the computer program enables a computer to execute the method executed by the communication device in each embodiment of the present application.
[0213] It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.
[0214] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.
[0215] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean 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 the present application.
[0216] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0217] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0218] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0219] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0220] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A communication method, characterized in that: include: The first network device receives first information, where the first information indicates whether the first terminal device supports the first capability.
2. The method according to claim 1, characterized in that The first network device receiving the first information includes: The first network device receives the first information sent by the access and mobility management function AMF network element.
3. The method according to claim 2, characterized in that The first network device receives the first information sent by the access and mobility function AMF network element, including: The first network device receives the first information sent by the AMF network element through an initial context establishment request message or a second paging message.
4. The method according to claim 3, characterized in that The initial context establishment request message or the second paging message includes a first information element IE, and the first information is carried in the first IE.
5. The method according to claim 1, wherein The first network device receives the first information, including: The first network device receives the first information sent by the second network device.
6. The method according to claim 5, characterized in that The first network device receiving the first information sent by the second network device includes: The first network device receives the first information sent by the second network device through a third paging message.
7. The method according to claim 6, characterized in that The third paging message includes a first information element IE, and the first information is carried in the first IE.
8. The method according to claim 4 or 7, characterized in that The first IE is a terminal wireless paging information IE.
9. The method according to any one of claims 1 to 8, characterized in that The first capability includes at least one of the following: Low-capability RedCap terminals, RedCap terminals with only 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability for PDSCH and / or PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability, and network energy saving capabilities.
10. The method according to any one of claims 1 to 9, characterized in that The first information is for a target frequency band.
11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: The first network device determines a paging strategy according to the first information.
12. The method according to claim 11, characterized in that The first network device determines a paging strategy according to the first information, including: The first network device determines whether to send a first paging message to the first terminal device according to the first information and whether the first network device allows the terminal device supporting the first capability to access.
13. The method according to claim 12, characterized in that The first network device determines, according to the first information and whether the first network device allows access by a terminal device supporting the first capability, whether to send a first paging message to the first terminal device, including: If the first terminal device supports the first capability and the first network device does not allow the terminal device supporting the first capability to access, the first network device determines not to send a first paging message to the first terminal device; If the first terminal device supports the first capability and the first network device allows terminal devices supporting the first capability to access, the first network device determines to send a first paging message to the first terminal device.
14. The method according to claim 11, characterized in that The first network device determines a paging strategy according to the first information, including: The first network device determines whether to send a first paging message to the first terminal device according to the first information and whether the first network device allows access by a terminal device that does not support the first capability.
15. The method according to claim 14, characterized in that The first network device determines, according to the first information and whether the first network device allows access by a terminal device that does not support the first capability, whether to send a first paging message to the first terminal device, including: If the first terminal device does not support the first capability and the first network device does not allow access by terminal devices that do not support the first capability, the first network device determines not to send a first paging message to the first terminal device; If the first terminal device does not support the first capability and the first network device allows terminal devices that do not support the first capability to access, the first network device determines to send a first paging message to the first terminal device.
16. A communication method, characterized in that: include: The access and mobility management function AMF network element sends first information to the first network device, where the first information indicates whether the first terminal device supports the first capability.
17. The method according to claim 16, characterized in that The access and mobility management function AMF network element sends first information to the first network device, including: The AMF network element sends the first information to the first network device through an initial context establishment request message or a second paging message.
18. The method according to claim 17, characterized in that The initial context establishment request message or the second paging message includes a first information element IE, and the first information is carried in the first IE.
19. The method according to claim 18, characterized in that The first IE is a terminal wireless paging information IE.
20. The method according to any one of claims 16 to 19, characterized in that The first capability includes at least one of the following: Low-capability RedCap terminals, RedCap terminals with only 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability for PDSCH and / or PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability, and network energy saving capabilities.
21. The method according to any one of claims 16 to 20, characterized in that The first information is for a target frequency band.
22. The method according to any one of claims 16 to 21, characterized in that The method further comprises: The AMF network element receives second information sent by a third network device, where the second information indicates whether the first terminal device supports the first capability.
23. The method according to claim 22, characterized in that The AMF network element receives the second information sent by the third network device, including: The AMF network element receives the second information sent by the third network device through a terminal wireless capability information indication message.
24. The method according to claim 23, wherein The terminal wireless capability information indication message includes a second information element IE, and the second information is carried in the second IE.
25. The method according to claim 24, characterized in that The second IE is a terminal wireless paging information IE.
26. A communication method, characterized in that: include: The second network device sends first information to the first network device, where the first information indicates whether the first terminal device supports the first capability.
27. The method according to claim 26, characterized in that The second network device sending the first information to the first network device includes: The second network device sends the first information to the first network device through a third paging message.
28. The method according to claim 27, characterized in that The third paging message includes a first information element IE, and the first information is carried in the first IE.
29. The method according to claim 28, characterized in that The first IE is a terminal wireless paging information IE.
30. The method according to any one of claims 26 to 29, characterized in that The first capability includes at least one of the following: Low-capability RedCap terminals, RedCap terminals with only 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability for PDSCH and / or PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability, and network energy saving capabilities.
31. The method according to any one of claims 26 to 30, characterized in that The first information is for a target frequency band.
32. A communication method, characterized in that: include: The first network device receives third information sent by the second network device, and the third information indicates any one of the following: whether the second network device allows terminal devices that support the first capability to access, whether the second network device supports terminal devices with the first capability, whether the second network device allows terminal devices that do not support the first capability to access, and whether the second network device supports terminal devices that do not support the first capability.
33. The method according to claim 32, characterized in that The first network device receiving third information sent by the second network device includes: The first network device receives the third information sent by the second network device through at least one of the following messages: Xn establishment request message, Xn establishment response message, access network node configuration update message.
34. The method according to claim 33, wherein The message includes a third information element IE, and the third information is carried in the third IE.
35. The method according to claim 34, wherein The third IE is the serving cell information IE.
36. The method according to claim 35, characterized in that The third information is carried in the broadcast information IE for low-capability terminals included in the serving cell information IE.
37. The method according to any one of claims 32 to 36, characterized in that The method further comprises: The first network device performs mobility management on the second terminal device according to the third information.
38. The method according to claim 37, wherein The first network device performs mobility management on the second terminal device according to the third information, including: The first network device determines a suitable target cell for the second terminal device during the switching and paging process based on the third information.
39. The method according to claim 37 or 38, characterized in that The second terminal device supports the first capability, or the second terminal device does not support the first capability.
40. The method according to any one of claims 32 to 39, characterized in that The first capability includes at least one of the following: Low-capability RedCap terminals, RedCap terminals with only 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability for PDSCH and / or PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability, and network energy saving capabilities.
41. The method according to any one of claims 32 to 40, characterized in that The third information is for the number of target receiving radio frequency channels.
42. A communication method, characterized in that: include: The second network device sends third information to the first network device, and the third information indicates any one of the following: whether the second network device allows terminal devices that support the first capability to access, whether the second network device supports terminal devices with the first capability, whether the second network device allows terminal devices that do not support the first capability to access, and whether the second network device supports terminal devices that do not support the first capability.
43. The method according to claim 42, characterized in that The second network device sending third information to the first network device includes: The second network device sends the third information to the first network device through at least one of the following messages: Xn establishment request message, Xn establishment response message, access network node configuration update message.
44. The method according to claim 43, wherein The message includes a third information element IE, and the third information is carried in the third IE.
45. The method according to claim 44, wherein The third IE is the serving cell information IE.
46. The method according to claim 45, characterized in that The third information is carried in the broadcast information IE for low-capability terminals included in the serving cell information IE.
47. The method according to any one of claims 42 to 46, characterized in that The first capability includes at least one of the following: Low-capability RedCap terminals, RedCap terminals with only 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability for PDSCH and / or PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability, and network energy saving capabilities.
48. The method according to any one of claims 42 to 47, characterized in that The third information is for the number of target receiving radio frequency channels.
49. A communication device, characterized in that include: A receiving unit is used to: receive first information, where the first information indicates whether the first terminal device supports the first capability.
50. The device according to claim 49, characterized in that The receiving unit is specifically used to: receive the first information sent by the access and mobility management function AMF network element.
51. The device according to claim 50, characterized in that The receiving unit is specifically used to: receive the first information sent by the AMF network element through an initial context establishment request message or a second paging message.
52. The device according to claim 51, characterized in that The initial context establishment request message or the second paging message includes a first information element IE, and the first information is carried in the first IE.
53. The device according to claim 49, characterized in that The receiving unit is specifically configured to receive the first information sent by the second network device.
54. The device according to claim 53, characterized in that The receiving unit is specifically configured to receive the first information sent by the second network device through a third paging message.
55. The device according to claim 54, characterized in that The third paging message includes a first information element IE, and the first information is carried in the first IE.
56. The device according to claim 52 or 55, characterized in that The first IE is a terminal wireless paging information IE.
57. The device according to any one of claims 49 to 56, characterized in that The first capability includes at least one of the following: Low-capability RedCap terminals, RedCap terminals with only 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability for PDSCH and / or PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability, and network energy saving capabilities.
58. The device according to any one of claims 49 to 57, characterized in that The first information is for a target frequency band.
59. The device according to any one of claims 49 to 58, characterized in that The device further includes a determining unit configured to determine a paging strategy according to the first information.
60. The device according to claim 59, characterized in that The determining unit is specifically configured to determine whether to send a first paging message to the first terminal device according to the first information and whether the apparatus allows access by a terminal device supporting the first capability.
61. The device according to claim 60, characterized in that The determining unit is specifically configured to: If the first terminal device supports the first capability and the apparatus does not allow access by the terminal device supporting the first capability, determining not to send a first paging message to the first terminal device; If the first terminal device supports the first capability and the apparatus allows access by terminal devices supporting the first capability, it is determined to send a first paging message to the first terminal device.
62. The device according to claim 59, characterized in that The determining unit is specifically configured to: Determine whether to send a first paging message to the first terminal device based on the first information and whether the apparatus allows access by a terminal device that does not support the first capability.
63. The device according to claim 62, characterized in that The determining unit is specifically configured to: If the first terminal device does not support the first capability and the apparatus does not allow access by terminal devices that do not support the first capability, determining not to send a first paging message to the first terminal device; If the first terminal device does not support the first capability and the apparatus allows access by terminal devices that do not support the first capability, it is determined to send a first paging message to the first terminal device.
64. A communication device, characterized in that include: A sending unit is used to: send first information to the first network device, where the first information indicates whether the first terminal device supports the first capability.
65. The device according to claim 64, characterized in that The sending unit is specifically configured to send the first information to the first network device through an initial context establishment request message or a second paging message.
66. The device according to claim 65, characterized in that The initial context establishment request message or the second paging message includes a first information element IE, and the first information is carried in the first IE.
67. The device according to claim 66, characterized in that The first IE is a terminal wireless paging information IE.
68. The device according to any one of claims 64 to 67, characterized in that The first capability includes at least one of the following: Low-capability RedCap terminals, RedCap terminals with only 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability for PDSCH and / or PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability, and network energy saving capabilities.
69. The device according to any one of claims 64 to 68, characterized in that The first information is for a target frequency band.
70. The device according to any one of claims 64 to 69, characterized in that The apparatus further includes a receiving unit configured to receive second information sent by a third network device, where the second information indicates whether the first terminal device supports the first capability.
71. The device according to claim 70, characterized in that The receiving unit is specifically configured to receive the second information sent by the third network device through a terminal wireless capability information indication message.
72. The device according to claim 71, characterized in that The terminal wireless capability information indication message includes a second information element IE, and the second information is carried in the second IE.
73. The method according to claim 72, characterized in that The second IE is a terminal wireless paging information IE.
74. A communication device, characterized in that include: A sending unit is used to: send first information to the first network device, where the first information indicates whether the first terminal device supports the first capability.
75. The device according to claim 74, characterized in that The sending unit is specifically configured to send the first information to the first network device through a third paging message.
76. The device according to claim 75, characterized in that The third paging message includes a first information element IE, and the first information is carried in the first IE.
77. The device according to claim 76, characterized in that The first IE is a terminal wireless paging information IE.
78. The device according to any one of claims 74 to 77, characterized in that The first capability includes at least one of the following: Low-capability RedCap terminals, RedCap terminals with only 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability for PDSCH and / or PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability, and network energy saving capabilities.
79. The device according to any one of claims 74 to 78, characterized in that The first information is for a target frequency band.
80. A communication device, characterized in that include: A receiving unit is used to: receive third information sent by a second network device, where the third information indicates any one of the following: whether the second network device allows terminal devices that support a first capability to access, whether the second network device supports terminal devices that have the first capability, whether the second network device allows terminal devices that do not support the first capability to access, and whether the second network device supports terminal devices that do not support the first capability.
81. The device according to claim 80, characterized in that The receiving unit is specifically configured to receive the third information sent by the second network device via at least one of the following messages: an Xn setup request message, an Xn setup response message, and an access network node configuration update message.
82. The device according to claim 81, characterized in that The message includes a third information element IE, and the third information is carried in the third IE.
83. The device according to claim 82, characterized in that The third IE is the serving cell information IE.
84. The device according to claim 83, characterized in that The third information is carried in the broadcast information IE for low-capability terminals included in the serving cell information IE.
85. The device according to any one of claims 80 to 84, characterized in that The apparatus further includes a management unit configured to perform mobility management on the second terminal device according to the third information.
86. The device according to claim 85, characterized in that The management unit is specifically configured to determine a suitable target cell for the second terminal device during a switching and paging process according to the third information.
87. The device according to claim 85 or 86, characterized in that The second terminal device supports the first capability, or the second terminal device does not support the first capability.
88. The device according to any one of claims 80 to 87, characterized in that The first capability includes at least one of the following: Low-capability RedCap terminals, RedCap terminals with only 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability for PDSCH and / or PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability, and network energy saving capabilities.
89. The device according to any one of claims 80 to 88, characterized in that The third information is for the number of target receiving radio frequency channels.
90. A communication device, characterized in that include: A sending unit is used to: send third information to the first network device, where the third information indicates any one of the following: whether the device allows terminal devices that support a first capability to access, whether the device supports terminal devices that do not support the first capability, whether the device allows terminal devices that do not support the first capability to access, and whether the device supports terminal devices that do not support the first capability.
91. The device according to claim 90, characterized in that The sending unit is specifically configured to send the third information to the first network device via at least one of the following messages: an Xn establishment request message, an Xn establishment response message, and an access network node configuration update message.
92. The device according to claim 91, characterized in that The message includes a third information element IE, and the third information is carried in the third IE.
93. The device according to claim 92, characterized in that The third IE is the serving cell information IE.
94. The device according to claim 93, characterized in that The third information is carried in the broadcast information IE for low-capability terminals included in the serving cell information IE.
95. The device according to any one of claims 90 to 94, characterized in that The first capability includes at least one of the following: Low-capability RedCap terminals, RedCap terminals with only 5MHz baseband bandwidth capability for the physical downlink shared channel PDSCH and / or physical uplink shared channel PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability for PDSCH and / or PUSCH, RedCap terminals with only 5MHz baseband bandwidth capability, and network energy saving capabilities.
96. The device according to any one of claims 90 to 95, characterized in that The third information is for the number of target receiving radio frequency channels.
97. A communication device, characterized in that It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 1 to 15, or 26 to 48.
98. A communication device, characterized in that It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 16 to 25.
99. A communication device, characterized in that The device comprises a processor configured to call a program from a memory so as to cause the communication device to execute the method according to any one of claims 1 to 15 or 26 to 48.
100. A communication device, characterized in that: The device comprises a processor configured to call a program from a memory so as to enable the communication device to execute the method according to any one of claims 16 to 25.
101. A chip, characterized in that: The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 15 or 26 to 48.
102. A chip, characterized in that: The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 16 to 25.
103. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 15 or 26 to 48.
104. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 16 to 25.
105. A computer program product, characterized in that A program is included, which causes a computer to execute the method according to any one of claims 1 to 15, or 26 to 48.
106. A computer program product, characterized in that A program is included, the program causing a computer to execute the method according to any one of claims 16 to 25.
107. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 15 or 26 to 48.
108. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 16 to 25.
Citation Information
Cited By
Communication method, terminal device and network device
WO2026170518A1
