Communication method and apparatus

Abstract

A communication method and apparatus, which can be used for configuring an RNA for a UE in an RRC inactive state. The method comprises: a first core network element sending first area information to a first access network device; and the first access network device sending information of an RNA to a terminal device. The first area information may indicate an identifier of a cell supported by at least one access network device and / or an RAN area code supported by the at least one access network device. The RNA is determined on the basis of the first area information. In the method, there may be no communication interface between one or more access network devices of at least one access network device and the first access network device, so that an RNA configured by the first access network device for the terminal device may include an area covered by an access network device that does not have a communication interface with the first access network device, so as to configure a relatively large RNA for the terminal device to the greatest possible extent, thereby reducing a delay of the terminal device re-entering an RRC connected state.

Description

A communication method and apparatus

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510185720.8, filed on February 19, 2025, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

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

[0004] User equipment (UE) in an inactive state in Radio Resource Control (RRC) can enter the connected state in RRC through the RRC recovery process, which has a shorter latency compared to a UE in an idle state entering the connected state through the RRC establishment process. The network (or anchor base station) will configure a radio access network notification area (RNA) for the UE to support the UE in the inactive state in entering the connected state in RRC through the RRC recovery process. The anchor base station refers to the last serving radio access network (RAN) node when the UE is in the connected state.

[0005] Typically, the RNA (Registration Area) should be contained within the UE's registration area (RA), and an Xn interface connection should be established between every pair of base stations within the RNA. This allows the base station receiving the UE's RRC recovery message to successfully obtain the UE's context from the anchor base station, thereby entering the RRC connected state through the RRC recovery process. However, this limits the coverage of the RNA and also restricts the advantages of functions related to the inactive state (such as shorter network access latency). For example, if an Xn interface connection is established between every pair of base stations within the RNA, then the RNA generally does not include base stations far from the UE's anchor base station. In this case, the inactive UE cannot access the base station through the RRC recovery process.

[0006] In the future, it will be possible to allow no Xn interface connection to be established between any two base stations within the RNA configured for the UE, in order to configure a larger RNA for the UE. How to expand the RNA still needs to be addressed. Summary of the Invention

[0007] This application provides a communication method and apparatus that can be expanded to the RNA configured for the UE, thereby enabling the UE to maintain the RRC inactive state within a larger RNA, thereby reducing the latency for the UE to enter the RRC connected state and saving power consumption for establishing the RRC connection.

[0008] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0009] Firstly, a communication method is provided, which can be applied to an access network side device (hereinafter referred to as an access network device). Unless otherwise specified in this application, the access network device can be an access network equipment; or a module or unit for performing some functions of the access network equipment (e.g., the access network device is a circuit or chip / chip system in the access network equipment); or the access network device can be a logical node, logical module, or software module that implements all or part of the functions of the access network equipment. In one example, the access network device is an access network equipment or a component in the access network equipment (e.g., a module, a communication module, a circuit or chip responsible for communication functions (such as a modem chip, a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip). For example, the access network device is a central unit (CU), a distributed unit (DU), or a radio unit (RU) for implementing some functions of the access network equipment. For ease of description, the following example uses the communication method provided in the first aspect applied to a first access network device.

[0010] The method includes: receiving first area information from a first core network element, and sending RNA information to a terminal device. The first area information is used to indicate the identifier of a cell supported by at least one access network device, and / or, the RAN area code supported by at least one access network device. The RNA is determined based on the first area information, and the terminal device is in an RRC inactive state.

[0011] In this method, the first core network element can learn about the regions supported by at least one access network device and indicate these regions to the first access network device through first region information. This helps the first access network device configure appropriate RNAs for terminal devices in the RRC inactive state. Compared with the TAC list currently reported by the core network, the first region information provides more granular region indication, including the cells and RAN region codes supported by the access network device. This design allows the first access network device to select more regions to configure for the terminal device, thereby configuring a larger RNA for the terminal device. By configuring a larger RNA, the terminal device can maintain the RRC inactive state in a wider range of regions, thereby reducing the state switching latency, saving power consumption for establishing RRC connections, and improving communication efficiency when the terminal device needs to re-enter the RRC connected state.

[0012] In one design, the RNA includes a first area served by a second access network device in at least one access network device, wherein the second access network device and the first access network device cannot communicate based on a first interface, the first interface being a communication interface between access network devices.

[0013] In this design, access network devices corresponding to one or more regions of the RNA cannot communicate with the first access network device via the first interface. Unlike the design where base stations corresponding to all regions of the RNA must be able to communicate directly with anchor base stations, this design allows for a larger RNA region and more corresponding access network devices. This allows the terminal device to maintain an inactive RRC state within a larger RNA, which helps reduce the latency of the terminal device entering the connected state, saves power consumption in establishing RRC connections, and improves communication efficiency.

[0014] In one design, the first area information indicates at least one area within the registration area of ​​the terminal device.

[0015] In this design, at least one region indicated by the first region information is still within the registration region of the terminal device. When the terminal device moves the RNA, the registration region update process is not triggered, which reduces the complexity of configuring the RNA for the terminal device.

[0016] In one design, the first area information includes a first tracking area code list, which includes at least one tracking area code, and each tracking area code corresponds to the identifier of at least one cell and / or at least one RAN area code.

[0017] In this design, the tracking area code is associated with the cell identifier and / or RAN area code, thereby making it compatible with the design of the core network element feeding back the tracking area code list to the access network equipment and reducing the implementation complexity.

[0018] In one design, the first area information also includes: the identifier of at least one access network device.

[0019] This design simplifies the mapping relationship between regions and access network devices by including the identifier of at least one access network device in the first region information and clearly defining the access network device corresponding to each region. This makes it easier for the first access network device to identify the access network device corresponding to a region.

[0020] In one design, the method further includes: sending second area information, the second area information being used to indicate at least one area supported by the first access network device. In this design, the first access network device can report the supported at least one area to a first core network element, enabling the first core network element to clearly identify the area supported by the first access network device, thereby informing other access network devices of the area supported by the first access network device, which helps other access network devices configure a larger RNA for the terminal device.

[0021] In one design, the second area information includes: information about the cell of the first access network device; and / or, the RAN area code of the first access network device.

[0022] In one design, the first area information is contained within interface management messages. For example, the first area information can be carried in an NG setup response message, a RAN configuration update response, or an AMF configuration update request message. Here, NG represents the communication interface between the core network and access network devices.

[0023] In one design, the first area information is included in the core network assistance information for inactive users (RC INACTIVE). Alternatively, the first area information is included in user-related messages, which may include initial context setup request messages, UE context modification request messages, handover request messages, and path switch request acknowledge messages.

[0024] Secondly, a communication method is provided, which can be applied to a network-side device (hereinafter referred to as a network device). For details regarding the network device, please refer to the relevant description of the network device in the first aspect above. For ease of description, the following example uses the communication method provided in the second aspect applied to a second access network device.

[0025] The method includes: sending third area information, which indicates at least one area supported by the second access network device.

[0026] In this method, the second access network device can report at least one supported region to the first core network element, so that the first core network element can notify the first access network device of the region supported by the second access network device, thereby enabling the first access network device to configure the region supported by the second access network device to the terminal device, so as to configure a larger RNA for the terminal device, which can effectively utilize the relevant functions of the RRC inactive state, such as minimizing the latency of the terminal device entering the RRC connected state.

[0027] In one design, the third area information includes: cell information of the second access network device; and / or, the RAN area code of the second access network device.

[0028] The beneficial effects of the second aspect and its various designs can be referred to the aforementioned beneficial effects of the first aspect and its various designs, and will not be repeated here.

[0029] Thirdly, a communication method is provided, which can be applied to a core network device (hereinafter referred to as a core network device). Unless otherwise specified in this application, the core network device can be a core network element; or a module or unit used to perform some functions of the core network element (e.g., the core network device is a circuit or chip / chip system in the core network element); or the core network device can be a logical node, logical module, or software module that implements all or part of the functions of the core network element. In one example, the core network device is a core network element or a component in the core network element (e.g., a module, a SoC chip, or a SIP chip). For ease of description, the following example uses the communication method provided in the third aspect applied to a first core network element, such as an AMF.

[0030] The method includes: determining first area information and sending the first area information to a first access network device. The first area information is used to indicate the identifier of a cell supported by at least one access network device, and / or, the RAN area code supported by at least one access network device.

[0031] In one design, the method further includes: receiving at least one area information, wherein the area information indicates at least one area supported by an access network device, and the first area information is determined based on the at least one area information.

[0032] In one design, the first area information indicates at least one area within the registration area of ​​the terminal device.

[0033] In one design, the first area information includes a first tracking area code list, which includes at least one tracking area code, and each tracking area code corresponds to the identifier of at least one cell and / or at least one RAN area code.

[0034] In one design, the first area information also includes: the identifier of at least one access network device.

[0035] In one design, the first area information is contained in the core network auxiliary information of the inactive user, or the first area information is contained in interface management messages.

[0036] The beneficial effects of the third aspect and its various designs can be referred to the aforementioned beneficial effects of the first aspect and its various designs, and will not be repeated here.

[0037] Fourthly, a communication method is provided, which can be applied to a network management device. Unless otherwise specified in this application, the network management device can be a network management equipment; or a module or unit for performing some functions of the network management equipment (e.g., the network management device is a circuit or chip / chip system in the network management equipment); or the network management device can be a logical node, logical module, or software module that implements all or part of the functions of the network management equipment. In one example, the network management device is an operations, administration, and maintenance (OAM) device or a component (e.g., a module, SoC chip, or SIP chip) in an OAM device. For ease of description, the following example uses the communication method provided in the fourth aspect applied to an OAM device.

[0038] The method includes: determining first area information and sending the first area information to a first access network device. The first area information is used to indicate the identifier of a cell supported by at least one access network device, and / or, the RAN area code supported by at least one access network device;

[0039] In one design, the method further includes: receiving at least one area information, wherein the area information indicates at least one area supported by an access network device, and the first area information is determined based on the at least one area information.

[0040] In one design, the first area information indicates at least one area within the registration area of ​​the terminal device.

[0041] In one design, the first area information includes a first tracking area code list, which includes at least one tracking area code, and each tracking area code corresponds to the identifier of at least one cell and / or at least one RAN area code.

[0042] In one design, the first area information also includes: the identifier of at least one access network device.

[0043] The beneficial effects of the fourth aspect and its various designs can be referred to the beneficial effects of the third aspect and its various designs mentioned above, and will not be repeated here.

[0044] Fifthly, embodiments of this application provide a communication method, which can be executed by a first access network device, a second access network device, a first core network element, and a terminal device. The method includes: the first access network device sending second area information to the first core network element, the second area information indicating at least one area supported by the first access network device; the second access network device sending third area information to the first core network element, the third area information indicating at least one area supported by the second access network device; the first core network element sending first area information to the first access network device, the first area information indicating the identifier of a cell supported by at least one access network device, and / or, the RAN area code supported by at least one access network device; and the first access network device sending RNA information to the terminal device, the RNA being determined based on the first area information, wherein the terminal device is in an RRC inactive state.

[0045] For the beneficial effects of the fifth aspect and its various designs, please refer to the aforementioned first aspect and its various designs; they will not be repeated here.

[0046] Sixthly, embodiments of this application provide a communication device for performing the methods described in any of the first to fourth aspects and any of their designs. The beneficial effects can be found in the relevant descriptions of any of the first to fourth aspects, which will not be repeated here.

[0047] In one possible design, the communication device includes corresponding means, modules, or units for performing the methods of any of the first to fourth aspects. These modules, units, or means can be implemented in software, hardware, or a combination of both. For example, the communication device includes a processing module (sometimes also called a processing unit or processor) and / or input / output interfaces. Input / output interfaces include input interfaces and / or output interfaces, which can be interface circuits, output circuits, input circuits, pins, or related circuits. Optionally, the communication device also includes a transceiver module (sometimes also called a transceiver unit or transceiver). The transceiver module is capable of both transmitting and receiving functions. When the transceiver module performs the transmitting function, it can be called a transmitting module (sometimes also called a transmitting unit), and when it performs the receiving function, it can be called a receiving module (sometimes also called a receiving unit). The transmitting module and the receiving module can be the same functional module, referred to as the transceiver module, which performs both transmitting and receiving functions; or, the transmitting module and the receiving module can be different functional modules, with "transceiver module" being a collective term for these functional modules. In one possible design, the processing module includes a baseband device, and the transceiver module includes a radio frequency device. These input / output interfaces and units (modules) can perform the corresponding functions in the method examples of any of the first to fourth aspects described above, as detailed in the method examples, and will not be repeated here.

[0048] For example, when the communication device is used to implement the corresponding function in the method example of the first aspect, the transceiver module is used to receive first area information from the first core network element and send RNA information to the terminal device. The first area information is used to indicate the identifier of a cell supported by at least one access network device, and / or, the RAN area code supported by at least one access network device. Wherein, the RNA is determined based on the first area information, and the terminal device is in an RRC inactive state.

[0049] For example, when the communication device is used to implement the corresponding function in the method example of the second aspect, the transceiver module is used to send third area information, which is used to indicate at least one area supported by the second access network device.

[0050] For example, when the communication device is used to implement the corresponding function in the method examples of the third or fourth aspect, the processing module is used to determine first area information, which indicates the identifier of a cell supported by at least one access network device, and / or, the RAN area code supported by at least one access network device. The transceiver module is used to send the first area information to the first access network device.

[0051] In a seventh aspect, embodiments of this application provide a communication device including a processor configured to execute the methods described in any of the first to fourth aspects and any design thereof. This application does not limit the specific type of processor. For example, the processor may be a baseband device, a central processing unit (CPU), or other specific integrated circuits. As another example, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0052] Optionally, the communication device further includes a communication interface. Optionally, the communication device also includes a memory for storing computer programs (also referred to as code or instructions), data, etc. The processor is coupled to the memory and the communication interface. When the processor reads the computer program, data, etc., from the memory, it causes any of the first to fourth aspects and any method in any of their designs to be executed.

[0053] In one design, the memory is located outside the communication device.

[0054] In one design, the memory is located within the communication device.

[0055] In one design, the processor and memory are integrated together.

[0056] Eighthly, embodiments of this application provide a chip system including a processor and a communication interface for implementing the methods described in any of the first to fourth aspects. Optionally, the chip system further includes a memory. The memory stores a computer program (also referred to as code or instructions). The processor retrieves and executes the computer program from the memory, causing a device equipped with the chip system to perform any of the first to fourth aspects and the methods in any of their designs. The chip system may be composed of chips or may include chips and other discrete devices.

[0057] Ninthly, embodiments of this application provide a communication device including an input / output interface and logic circuitry. The input / output interface is used for inputting and / or outputting information. The input / output interface may be an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc. The logic circuitry is used to execute the methods described in any of the first to fourth aspects.

[0058] In one implementation of the ninth aspect, when the communication device is an access network device, the interface circuit can be a radio frequency processing chip in the access network device, and the processing circuit can be a baseband processing chip in the access network device.

[0059] In one implementation of the ninth aspect, when the communication device is a chip or chip system, the input circuit can be an input pin, the output circuit can be an output pin, and the logic circuit can be a transistor, gate circuit, flip-flop, or various other logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver; the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the input / output interface and the logic circuit.

[0060] The aforementioned communication device may be a first access network device in the first aspect. Alternatively, the communication device may be a device capable of supporting the first access network device in implementing the functions required by the method provided in the first aspect, for example, the communication device may be a chip or chip system in the first access network device. Alternatively, the aforementioned communication device may be a second access network device in the second aspect. Alternatively, the communication device may be a device capable of supporting the second access network device in implementing the functions required by the method provided in the second aspect, for example, the communication device may be a chip or chip system in the second access network device. Alternatively, the aforementioned communication device may be a first core network element in the third aspect. Alternatively, the communication device may be a device capable of supporting the first core network element in implementing the functions required by the method provided in the third aspect, for example, the communication device may be a chip or chip system in the first core network element. Wherein, the chip may be a baseband chip and / or a radio frequency chip, and the chip system may be composed of chips or may include chips and other discrete devices. Alternatively, the aforementioned communication device may be an OAM device in the fourth aspect. Alternatively, the communication device may be a device capable of supporting the OAM device in implementing the functions required by the method provided in the fourth aspect, for example, the communication device may be a chip or chip system in the OAM device. The chip can be a baseband chip and / or a radio frequency chip. The chip system can be composed of chips or may include chips and other discrete components.

[0061] In a tenth aspect, embodiments of this application provide a communication system comprising a first access device, a second access network device, a first core network element, and a terminal device. The first access device is used to implement the functions described in the first aspect, and the second access network device is used to implement the functions described in the second aspect; or, the first core network element is used to implement the functions described in the third aspect. Alternatively, the communication system comprises a first access device, a second access network device, an OAM device, and a terminal device, wherein the first access device is used to implement the functions described in the first aspect, and the second access network device is used to implement the functions described in the second aspect; or, the OAM device is used to implement the functions described in the third aspect.

[0062] Eleventhly, embodiments of this application provide a computer-readable storage medium for storing a computer program or instructions that, when executed, enable the methods described in any of the first to fourth aspects and any of their designs to be implemented.

[0063] In a twelfth aspect, embodiments of this application also provide a computer program product containing instructions that, when run on a computer, cause the methods described in any of the first to fourth aspects and any of their designs to be implemented.

[0064] The beneficial effects of the sixth to twelfth aspects mentioned above can be referenced with the beneficial effects of the first or third aspects and any of their designs. Attached Figure Description

[0065] Figure 1 is a schematic diagram of RA and RNA;

[0066] Figures 2A and 2B are schematic diagrams of the architecture of the two communication systems;

[0067] Figures 3 to 6 are schematic flowcharts of four embodiments provided in this application;

[0068] Figures 7 to 9 are schematic diagrams of three structures of the communication device provided in the embodiments of this application. Detailed Implementation

[0069] In the embodiments of this application, "transmission" includes "sending" and / or "receiving." "Sending" and "receiving" indicate the direction of signal transmission. For example, "sending information to XX" can be understood as the destination of the information being XX, including direct sending as well as indirect sending through other units, modules, devices, or network elements. "Receiving information from YY" can be understood as the source of the information being YY, including receiving directly from YY via the air interface as well as receiving indirectly from YY via the air interface from other units or modules. "Sending" can also be understood as the "output" of a chip interface, and "receiving" can also be understood as the "input" of a chip interface. In other words, sending and receiving can occur between devices, such as between access network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via buses, traces, or interfaces.

[0070] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A / B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and / or c means the following combinations: a exists alone, b exists alone, c exists alone, a and b exist simultaneously, a and c exist simultaneously, b and c exist simultaneously, or a, b, and c exist simultaneously, where a, b, and c can be single or multiple.

[0071] In the embodiments of this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, not to a time limit, nor to requiring the device to perform a judgment action, nor implying any other limitations. Unless otherwise specified, "if" and "if" are interchangeable, and "when" and "in the case of" are interchangeable. "When" and "if" / "if" are interchangeable. "of," "corresponding, relevant," and "corresponding" can sometimes be used interchangeably, and it should be noted that their meanings are consistent when their differences are not emphasized. In addition, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations, and are intended to present related concepts in a specific manner. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs.

[0072] In this application's embodiments, ordinal numbers such as "first" and "second" are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, "first area information" and "second area information" refer to two different areas of information, and do not indicate a difference in priority or importance between the two areas of information.

[0073] The following explanations of the terms or concepts involved in the embodiments of this application are provided to facilitate understanding of the solutions provided in the embodiments of this application.

[0074] (1) Access network equipment

[0075] Access network equipment refers to radio access network (R)AN equipment / RAN nodes. R)AN and RAN are interchangeable; for ease of description, RAN will be used as an example below. RAN can be a cellular system related to the 3rd generation partnership project (3GPP), such as a 5th generation (5G) mobile communication system / new radio (NR) mobile communication system, or a future-oriented evolution system. RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), a virtualized RAN (vRAN), or a non-terrestrial network (NTN) (e.g., a satellite communication system). RAN can also be a communication system that integrates two or more of the above systems. RAN equipment can also be called a RAN node, RAN entity, or access node, etc.

[0076] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a satellite (or satellite base station), or a high-altitude platform station (HAPS), or base station equipment mounted on a satellite / HAPS, or a base station in a future mobile communication system. The satellite can include at least one of the following: a geostationary Earth orbit (GEO) satellite or a non-geostationary Earth orbit (NGEO) satellite. A non-geostationary Earth orbit satellite can include at least one of the following: a medium Earth orbit (MEO) satellite or a low Earth orbit (LEO) satellite. There are no limitations here. RAN nodes can also be macro base stations, micro base stations, indoor stations, relay nodes, donor / host nodes, or wireless controllers. RAN nodes can also be servers, wearable devices, vehicles, or vehicle-mounted equipment. For example, in vehicle-to-everything (V2X) technology, the RAN node can be a roadside unit (RSU). The AP (Access Point) can serve as the central hub of this communication system, and can be a base station, router, gateway, repeater, communication server, switch, or bridge, etc., equipped with a Wi-Fi chip. RAN nodes can also be gateway stations (or ground stations, earth stations, signaling stations, gateways, or gateway stations). Notably, gNBs (gampions on network nodes) and next-generation radio access networks (NG-RAN) are interchangeable.

[0077] In another possible scenario, the RAN node can be a module or unit that performs some of the functions of the base station; or multiple RAN nodes can cooperate to assist terminal equipment in achieving wireless access, with different RAN nodes performing some of the functions of the base station. For example, the RAN node can be a CU, DU, or RU. The function of the CU can be implemented by a single entity or by different entities. For example, the function of the CU can be further divided, that is, the control plane and the user plane can be separated and implemented by different entities, namely the control plane CU entity (i.e., CU-control plane (CP) entity) and the user plane CU entity (i.e., CU-user plane (UP) entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the function of the RAN node. The CU and DU can be set up separately or included in the same network element, such as in the baseband unit (BBU). Any of the units among the CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented by software modules, hardware modules, or a combination of software modules and hardware modules.

[0078] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples.

[0079] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement. For example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and higher protocol layers (such as the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer). The CU connects to network nodes such as the core network through interfaces, which can be E2 interfaces. Optionally, the CU can have some core network functions. The CU (e.g., the PDCP layer and higher) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower layers) through interfaces. For example, the DU can be configured to implement the functions of protocol layers below the PDCP layer (e.g., RLC, MAC, and / or the Physical (PHY) layer). For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications or the technical specifications of other applicable communication protocols.

[0080] The above division of CU and DU processing functions according to the protocol layer is merely an example; other division methods are also possible, and this application does not impose any restrictions.

[0081] For example, in one design, the CU or DU can be further divided into processing functions with protocol layers. In one design, some functions of the RLC layer and the protocol layer functions above the RLC layer are located in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer are located in the DU. In another possible design, the DU and RU cooperate to implement the PHY layer functions, or it can be described as moving some of the PHY layer functions of the DU to the RU. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways depending on the design. For example, the DU is configured to implement baseband functions, and the RU is configured to implement mid-RF functions. As another example, the DU is configured to implement higher-level functions in the PHY layer, and the RU is configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions.

[0082] When the RAN is O-RAN, it can also have artificial intelligence (AI) capabilities. For example, O-RAN includes an intelligent controller. The intelligent controller can be a non-real-time RAN intelligent controller (RIC / non-RT RIC / NRT RIC) or a near-real-time RAN intelligent controller (RIC / near-RT RIC / nRT RIC). A non-real-time RIC can be used to implement non-real-time intelligent management of RAN functions, enabling workflows including model training and model updates, and guiding applications / functions in the nRT RIC based on policies. A near-real-time RIC can be used to implement near-real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, near-real-time control and optimization of O-RAN modules and resources are achieved.

[0083] (2) Terminal equipment

[0084] Terminal equipment refers to any device capable of communicating with a base station. It is also known as a terminal, terminal device, user equipment (UE), user terminal, mobile station, or mobile terminal. Examples of terminal equipment include: mobile phones, computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, stations (STA), robotic arms, cameras, robots, vehicles, drones, smart home devices, relays, and customer premises equipment (CPE). STAs can include Wi-Fi-enabled mobile phones, tablets, smart TVs, smart wearable devices, vehicle communication devices, routers, switches, and so on.

[0085] Furthermore, in this embodiment, the terminal device can also be a terminal device in an Internet of Things (IoT) system, such as a water meter or electricity meter. When the terminal device is applied to V2X, it can also be called a V2X device. All the terminal devices described above, if located on a vehicle (e.g., placed / installed inside the vehicle), can be considered in-vehicle terminal devices. In-vehicle terminal devices can be built into a vehicle's in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit as one or more components or units. The vehicle can implement the methods of this application through the built-in in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit. In-vehicle terminal devices can be vehicle equipment, in-vehicle modules, vehicles, in-vehicle units (on-board units, OBUs), remote sensing units (RSUs), in-vehicle infotainment systems (or in-vehicle transmission units) (telematics boxes, T-boxes), chips, or system-on-chips (SoCs), etc. These chips or SoCs can be installed in the vehicle, OBU, RSU, or T-box.

[0086] (3) Core Network

[0087] In this application, the core network may include equipment that processes and forwards user signaling and data. This includes, for example, AMF (Active Network Function) elements, Session Management Function (SMF) elements, and user plane gateways. The user plane gateway can be a server with functions such as mobility management, routing, and forwarding of user plane data, typically located on the network side, such as a User Plane Function (UPF) element. The core network may also include other network elements, which are not listed here.

[0088] In this application, the communication device used to implement the functions of the core network equipment can be referred to as a core network device. This core network device can be a core network element, a core network device, or a device capable of supporting the core network device or network element to implement the function, such as a chip system. This device can be installed in the core network device. In the technical solutions provided in the embodiments of this application, the core network device is used as an example to describe the technical solutions provided in the embodiments of this application. Additionally, a network element can also be referred to as an entity or functional entity. For example, an AMF network element can also be referred to as an AMF entity or an AMF functional entity. Optionally, the device name mentioned in the embodiments of this application can omit "network element". For example, AMF network element and AMF represent the same meaning. Furthermore, a network element / functional entity can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network element or functional entity can be implemented by one device, or by multiple devices, or can be different functional modules within one device. The embodiments of this application do not specifically limit this. In actual deployment, the above-mentioned network elements can be co-located.

[0089] (4) RRC status.

[0090] Terminal devices have three RRC states: RRC connected, RRC idle, and RRC inactive.

[0091] RRC Connection State: The terminal device has established an RRC connection with the network and can transmit data. RRC connection state can also be simply referred to as connection state. In this article, "connection state" and "RRC connection state" are the same concept and the two terms can be used interchangeably.

[0092] RRC Idle State: The terminal device has not established an RRC connection with the network and cannot transmit data with network devices, but it can receive broadcast information from the cell, such as system information and paging messages. Furthermore, the base station does not store the context of this terminal device. If the terminal device needs to transition from the RRC Idle State to the RRC Connected State, it needs to initiate an RRC connection establishment process. The RRC Idle State can also be simply referred to as the Idle State. In this article, "Idle State" and "RRC Idle State" are the same concept, and the two terms can be used interchangeably.

[0093] RRC Inactive State: The terminal device previously entered the RRC connected state at the anchor base station, and then the anchor base station released the RRC connection, but it preserved the terminal device's context. If the terminal device needs to re-enter the RRC connected state from the RRC inactive state, it needs to initiate an RRC connection recovery process (or RRC connection re-establishment process) at the currently camped base station. Because the terminal device may be in a mobile state, the base station currently camped by the terminal device and the anchor base station may be the same base station or different base stations. Compared to the RRC establishment process, the RRC recovery process has shorter latency and lower signaling overhead. However, the base station needs to preserve the terminal device's context, which consumes base station storage overhead. The RRC inactive state can also be called the RRC inactive state, or simply inactive or inactive state. In this article, "deactivated state," "inactive state," "deactivated state," "inactive state," "RRC inactive state," or "RRC deactivated state" are all the same concept and these terms are interchangeable.

[0094] (5) RA and RNA

[0095] A Tracking Area (RA) is a geographical area in a mobile communication network, consisting of one or more Tracking Areas (TAs). Each TA corresponds to a Tracking Area Identity (TAI), which is used to manage the mobility and location updates of terminal devices.

[0096] An RNA (Radio Area) is a specific geographic region used for UE mobility management. Generally, an RNA can be a smaller area than the RA (Radio Area). An RNA can cover one or more cells, or one or more RAN (Radio Area) regions. As shown in Figure 1, an RNA can include multiple cells, and each RNA corresponds to an RNA identifier (ID).

[0097] For UEs in the RRC inactive state, paging can be performed within the RNA range. The RNA is managed by the base station, which can locate the UE by paging it via the RNA (RAN paging). This process is called radio access network level terminal tracking.

[0098] (6) Inactive UE RNA configuration

[0099] When a UE detects its own paging message while inactive, it initiates an RRC recovery procedure to the network side. The UE in the inactive state can have its RNA configured by the last serving RAN node from when it was in the connected state.

[0100] When configuring the RNA for a UE, the base station can provide the UE with any of the following configurations via an RRC Release message: a cell list and a RAN area list. The cell list provides the UE with the identifiers (IDs) of one or more cells constituting the RNA; for example, the cell list includes one or more cell IDs. The RAN area list indicates one or more RAN areas. For example, the RAN area list includes one or more RAN area IDs, where one RAN area ID indicates one RAN area. A RAN area is a subset of a Tracking Area Code (TA) or equal to one TA, and can be characterized by either a Tracking Area Code (TAC) or a RAN area code.

[0101] The terms and concepts involved in the embodiments of this application have been introduced above. The technical features related to the embodiments of this application are described below.

[0102] Typically, the RNA should be contained within the UE's RA, and there should be Xn connectivity (or an established Xn connection) between any two base stations within the RNA. This is to ensure that the base station receiving the UE's RRC recovery message can successfully obtain the UE's context from the anchor base station, thereby improving the success rate of the UE's RRC recovery process. Here, the Xn interface can be considered a general term for the communication interface between base stations. If there is no Xn connectivity between the base station receiving the UE's RRC recovery message and the anchor base station, the base station receiving the UE's RRC recovery message will not be able to successfully obtain the UE's context from the anchor base station, and the UE's RRC recovery connection will fail.

[0103] To ensure that the RNA is included within the UE's RA and that there is Xn connectivity between any two base stations within the RNA, the UE's serving base station, when determining (or generating) the RNA, can refer to the UE's RA information (or a list of tracking areas) indicated in the core network assistance information for RRC inactive state, and configure the UE to be within the RA. The core network assistance information for RRC inactive state includes a TAI list for RRC inactive state. The TAI includes the public land mobile network (PLMN) ID and the TAC ID.

[0104] The serving base station determines which area (RA) the UE is currently in based on the TAI list, and excludes areas outside that RA when configuring the RNA for the UE. As mentioned above, every pair of base stations within the RNA configured by the serving base station for the UE has Xn connectivity. However, within an operator's entire network, it's impossible to guarantee that all base stations establish Xn interfaces. This is partly because data transmission between distant base stations may be minimal or nonexistent, and establishing Xn interfaces would waste unnecessary base station resources. Furthermore, operators generally do not establish Xn interfaces for base stations at geographical boundaries based on network management strategies. Therefore, if every pair of base stations within the RNA configured for the UE has Xn connectivity, it obviously limits the RNA's coverage and the advantages of inactive related functions (e.g., shorter network access latency). For example, if every pair of base stations within the RNA configured for the UE has Xn connectivity, then that RNA generally does not include base stations far from the UE's serving base station. Thus, an inactive UE cannot access a base station far from its serving base station through the RRC recovery process.

[0105] In the future, it may be possible to configure a larger RNA for the UE without Xn connectivity or without establishing Xn connections between any two base stations within the RNA configured for the UE (e.g., there may be no Xn interface between the anchor base station and the serving base station (or the base station currently serving the UE)). However, how to expand the RNA remains to be solved.

[0106] In view of this, the following solution is provided according to the embodiments of this application. In this solution, one or more base stations can report the supported areas to a first core network element, thereby enabling the first core network element to know the areas supported by at least one base station and indicate these areas to the serving base station, so that the serving base station can know the areas supported by at least one base station. In this process, one or more of the at least one base station may not have a communication interface with the serving base station, so that the RNA configured by the serving base station for the UE can cover the area covered by these base stations without communication interfaces, thereby achieving a larger range of RNA configuration. This allows the terminal device to remain in the RRC inactive state in a larger RNA, thereby reducing the state switching latency when the terminal device needs to re-enter the RRC connected state, saving the power consumption of establishing the RRC connection, and improving communication efficiency.

[0107] The technical solutions provided in the embodiments of this application can be applied to various communication systems, such as long-term evolution (LTE) communication systems, 5G mobile communication systems / NR communication systems, or future mobile communication systems, or other similar communication systems. Other similar communication systems may include V2X systems, IoT systems, wireless local area networks (WLANs), NTN (e.g., satellite communication systems), or systems integrating NTN with terrestrial networks (TN), etc. The NTN system can be an NTN system integrated with 4G, 5G, and any future generation of communication systems, such as NR NTN, IoT NTN, etc. The NTN communication system can be, for example, a satellite communication system, and may also include drones, HAPS, and other airborne access network equipment; this application does not limit this.

[0108] Please refer to Figure 2A, which illustrates a communication system applicable to an embodiment of this application. Figure 2A includes a terminal device, access network device 1, access network device 2, and core network (CN) equipment. Both access network device 1 and access network device 2 can communicate with the core network equipment. The terminal device can communicate with access network device 1 or access network device 2 via a wireless air interface. For example, the communication system shown in Figure 2A can be a 5G NR communication system, where the first interface can be an Xn interface, and access network device 1 and access network device 2 can communicate with the core network equipment via an NG interface, where the wireless air interface can be a Uu interface. Where access network device 1 and access network device 2 cannot communicate via the first interface, this is indicated by an "×" in Figure 2A. The inability for two access network devices to communicate via the first interface includes the absence of a first interface between the two access network devices, or the failure or unavailability of the first interface between the two access network devices.

[0109] Figure 2A shows an example where access network device 1 and access network device 2 are connected to the same core network device. In possible scenarios, access network device 1 and access network device 2 may be connected to different core network devices, or access network device 1 and access network device 2 may be connected to different core network devices.

[0110] For example, please refer to Figure 2B, which shows a communication system according to an embodiment of this application. The system shown in Figure 2B includes a terminal device, access network device 1, access network device 2, core network device 1, and core network device 2. As shown in Figure 2B, access network device 1 can communicate with core network device 1, and access network device 2 can communicate with core network device 2. Core network device 1 and core network device 2 can communicate with each other. The terminal device can communicate with access network device 1 or access network device 2 through a wireless air interface. In Figure 2B, access network device 1 and access network device 2 cannot communicate with each other through the first interface.

[0111] For the terminal device in Figure 2A or Figure 2B, the terminal device can move between the cells provided by the two access network devices. When moving to one of the access network devices (e.g., camping on a cell provided by that access network device), the terminal device can communicate with that access network device. Alternatively, the terminal device may only move between different cells provided by one access network device; or the terminal device may move between cells provided by more access network devices, thus allowing for the presence of more access network devices. Figure 2A or Figure 2B illustrates the presence of two access network devices. The method provided in this application embodiment can be executed by access network devices and core network devices. Figure 2A or Figure 2B is merely illustrative; the number of devices may be fewer or more.

[0112] The solutions provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0113] For ease of description, the following description uses the example of the communication method provided in this application being executed by a first communication device, a second communication device, and a third communication device. Optionally, the communication method provided in this application may also be executed by a third communication device.

[0114] In this context, the first and second communication devices can be access network devices, and the third communication device can be a core network device. For a single communication device (e.g., the first, second, or third communication device), the steps performed by that device can be implemented by the communication device itself, by a device including the communication device, by a component within the communication device (e.g., a processing unit / processor), or by a logic module or software that performs some or all of the functions of the communication device. For example, if the first communication device is a RAN device, the steps performed by the first communication device can be implemented by the RAN device, or by a CU, DU, or SU that performs some of the functions of the RAN device. Similarly, if the third communication device is a core network device, the steps performed by the third communication device can be implemented by a module that performs some of the functions of the core network device (e.g., a CPU chip). For ease of description, the following examples will use the first communication device as a first access network device, the second communication device as a second access network device, and the third communication device as a first core network element. The first access network device can be access network device 1 in Figure 2A or 2B, the second access network device can be access network device 2 in Figure 2A or 2B, and the first core network element can be the core network device in Figure 2A, or core network device 1 or core network device 2 in Figure 2B. For example, the first core network element can be AMF.

[0115] Furthermore, the processing performed by a single execution entity can also be divided into multiple execution entities, which can be logically and / or physically separated.

[0116] In this application embodiment, "regional information" refers to one or more regions. Here, "region" can include one or more cells, or it can be used to represent a group of physically close or geographically adjacent cells that collectively cover a large geographical area. The terminal device may move randomly within this large geographical area, possibly moving from one cell to another. In this application embodiment, the region served by the access network device, the cell of the access network device, the cell broadcast by the access network device, the cell provided by the access network device, and the cell covered by the access network device are all the same concept and can be substituted for each other.

[0117] The solution provided in this application is described below with reference to specific embodiments.

[0118] Example 1:

[0119] Please refer to Figure 3, which is a flowchart illustrating the communication method provided in Embodiment 1 of this application. Figure 3 illustrates the interaction between a first access network device, a second access network device, and a first core network element. The first access network device is either the serving base station of the terminal device, or the last serving base station of the terminal device, or any base station connected to the first core network element. The first core network element includes an AMF (Advanced Management Function).

[0120] S301. The first core network element sends the first area information to the first access network device.

[0121] The first area information can be used to indicate the cell / area supported by at least one access network device. Alternatively, the first area information can be used to indicate the identifier of the cell supported by at least one access network device, and / or the RAN area code supported by at least one access network device. It should be understood that the at least one access network device does not include the first access network device.

[0122] Before the first core network element executes S301, one or more access network devices may report their supported areas to the first core network element. The first core network element, upon obtaining the supported areas from these access network devices, can determine the first area information based on these areas. For ease of description, the following example illustrates how the first and second access network devices report their supported cells to the first core network element before S301 is executed. Alternatively, S31 and S32 may also be executed before S301. The execution order of S31 and S32 is not restricted. For example, S31 may be executed before S32, after S32, or simultaneously.

[0123] Optionally, steps S31 and S32 are not mandatory and are illustrated by dashed lines in Figure 3. For example, the area supported by each of at least one access network device can be notified to the first core network element by the core network management device, without needing to execute S31 and S32. Optionally, the core network management device can be OAM.

[0124] S31. The first access network device sends the second area information to the first core network element.

[0125] Accordingly, the first core network element receives second area information. The second area information may indicate at least one area supported by the first access network device, or the second area information may indicate at least one area, the at least one area including the cell served by the first access network device.

[0126] This application does not limit the content of the second area information, as long as the second area information can indicate at least one area supported by the first access network device. Examples are given below.

[0127] In Example 1, the second area information may include information about the cells of the first access network device, or the second area information may include information about the cells supported / served by the first access network device. The cell information of the first access network device includes the cell ID of the first access network device. For example, the second area information includes one or more cell ID lists, wherein a cell ID list includes one or more cell IDs (e.g., cell ID#1, cell ID#2, etc.), which include the IDs of cells supported by the first access network device.

[0128] In Example 2, the second area information may include the RAN area code of the first access network device. For example, the second area information may include one or more RAN Area Code lists, wherein a RAN Area Code list includes one or more RAN area codes (e.g., RAN area code#x, RAN area code#y, etc.).

[0129] In Example 3, the second area information may include cell information of the first access network device and the RAN area code of the first access network device. For example, the second area information may include one or more cell ID lists and one or more RAN Area Code lists, as detailed in Examples 1 and 2, which will not be repeated here. Another example is that the second area information may include one or more cell ID lists, where each cell ID list includes one or more cell IDs and one or more RAN area codes.

[0130] The second area information in Examples 1 to 3 above may also include a TAC list, which includes one or more TAC IDs (e.g., TAC#1, TAC#2, etc.), with one TAC ID associated with one cell ID list; or one TAC ID associated with one RAN Area Code list; or one TAC ID associated with one cell ID list and one RAN Area Code list. Alternatively, the second area information in Examples 1 to 3 above may also include a tracking area identity (TAI) list, where the TAI includes a TAC ID and a public land mobile network (PLMN) ID, with one TAI list associated with one cell ID list; or one TAI list associated with one RAN Area Code list; or one TAI list associated with one cell ID list and one RAN Area Code list.

[0131] For example, the information in the second region can be implemented in two ways, as shown in Table 1 and Table 2.

[0132] Table 1

[0133] Optionally, the second area information includes updated area information. Updated area information refers to information updated compared to the area information most recently sent by the first access network device to the first core network element, or the area indicated by the updated area information is updated compared to the area indicated by the first access network device most recently to the first core network element. For example, the updated area includes newly added areas, modified areas, or deleted areas. For example, the second area information includes newly added RAN area codes, modified RAN area codes, or deleted RAN area codes. Accordingly, the areas supported by the first access network device in this instance are the sum of the areas indicated by the area information most recently sent by the first access network device to the first core network element and the areas indicated by the updated area information. For example, if the area indicated by the area information most recently sent by the first access network device to the first core network element is Area 1, Area 2, and Area 3, and the second area information includes information about a newly added Area 4, then the areas supported by the first access network device are Area 1, Area 2, Area 3, and Area 4. Continuing this example, if the second area information includes information about a deleted Area 1, then the areas supported by the first access network device are Area 2 and Area 3.

[0134] The second area information can be carried in interface management messages between the base station and the core network. These interface management messages include one or more of the following: "NG setup request" message, "RAN configuration update request" message, and "uplink RAN ​​configuration transfer" message. This application does not limit the timing of the first access network device sending the second area information to the first core network element. For example, the first access network device can send the second area information to the first core network element when establishing an NG interface with it. Accordingly, the second area information can be carried in an "NG SETUP REQUEST" message. As another example, when the first access network device needs to notify the first core network element of its configuration update, it can send the second area information to the first core network element. Accordingly, the second area information can be carried in a "RAN configuration update request" message.

[0135] Optionally, the first core network element receiving the second area information can send a response message for the second area information to the first access network device. For example, if the second area information is carried in an NG setup request message, the first core network element receiving the NG setup request can send an "NG setup response" message to the first access network device.

[0136] Similar to the first access network device, one or more other access network devices in the network also indicate to the first core network element the at least one area they support. Taking the second access network device as an example, the second access network device can execute S302.

[0137] S32. The second access network device sends the third area information to the first core network element.

[0138] Accordingly, the first core network element receives third area information. This third area information indicates at least one area supported by the second access network device. For example, the third area information may include cell information of the first access network device; or, the third area information may include the RAN area code of the first access network device; or, the third area information may include both cell information and the RAN area code of the first access network device. The specific implementation of the third area information is the same as that of the second area information, and can be referred to the aforementioned description of the second area information, which will not be repeated here. Similar to the second area information, the third area information can also be carried in interface management messages between the base station and the core network.

[0139] For a first core network element, it can receive at least one area information, wherein one of the area information indicates at least one area supported by an access network device. Based on the obtained at least one area information, the first core network element can determine / generate first area information and send the first area information to the first access network device to help the first access network device configure RNA for the terminal device.

[0140] The first area information can indicate at least one area supported by at least one access network device. Similar to the second or third area information, the first area information can be used to indicate (or include) the identifiers of cells supported by at least one access network device, and / or, the RAN area codes supported by at least one access network device. Compared to the TAC list reported to the first access network device, the first area information provides a more granular area indication, including the cells and RAN area codes supported by the access network device. This allows the first access network device to select more areas to configure for the terminal device, thereby configuring a larger RNA for the terminal device. By configuring a larger RNA, the terminal device can maintain an RRC inactive state over a wider area, thereby reducing state switching latency, saving power consumption in establishing RRC connections, and improving communication efficiency when the terminal device needs to re-enter the RRC connected state.

[0141] Optionally, the first area information may further include the identifier of at least one access network device, so that the first access network device knows which area(s) is provided by which access network device. Optionally, the area indicated by the first area information does not include areas supported by the first access network device.

[0142] As an example, the first region information may include a first TAC list or a first TAI list. The first TAC list includes a list of TACs supported by at least one access network device. Similarly, the first TAI list includes a list of TAIs supported by at least one access network device. A TAC list includes one or more tracking area codes, and each tracking area code corresponds to / is associated with the identifier of at least one cell and / or at least one RAN area code. Alternatively, the first region information may include a first TAC list or a first TAI list, which includes at least one TAC, and each TAC is associated with at least one cell ID and / or at least one RAN area code. Optionally, a TAC may also be associated with the ID of at least one access network device. For example, the first region information can be implemented in three ways, as shown in Tables 3 to 5. The first access network device can determine the regions supported by each access network device based on the first region information. Associating the tracking area code with the cell identifier and / or RAN area code can be compatible with the design of the core network element feeding back the tracking area code list to the access network device, reducing implementation complexity.

[0143] Table 3

[0144] Table 4

[0145] Table 5

[0146] Optionally, at least one region indicated by the first region information may be within the registered region of the terminal device. Alternatively, at least one region indicated by the first region information may not include regions other than the registered region of the terminal device. In this way, when the terminal device moves within the RNA, the registration region update process will not be triggered, reducing the complexity of configuring the RNA for the UE.

[0147] Optionally, similar to how the second area information includes updated area information, the first area information may also include updated area information. For example, the first area information may include one or more of the following: information on newly added areas, information on deleted areas, and information on modified areas. Please refer to the relevant description in S31 above for details, which will not be repeated here.

[0148] The first area information can also be carried in interface management messages, such as NG setup response messages, RAN configuration update response messages, AMF configuration update request messages, or downlink RAN ​​configuration transfer messages.

[0149] Alternatively, the first region information can be carried within user-associated messages. User-associated messages may include initial context setup request messages, handover request messages, path switch request acknowledge messages, UE context modification request messages, or core network assistance information for inactive users. When the first region information is included in user-associated messages, it is included within the core network assistance information for inactive users. Alternatively, when the first region information is included in user-associated messages, it can be sent to the first access network device as part of a "core network assistance information for RRC INACTIVE" element. The first access network device, upon receiving the first region information, can also send a response message containing the first region information to the first core network element. For example, if the first region information is carried within an initial context setup request message, the first access network device, upon receiving this message, can send an initial context setup response message to the first core network element.

[0150] S302, The first access network device sends RNA information to the terminal device.

[0151] When the first access network device decides to release the terminal device to the RRC inactive state, or when the first access network device decides to transition the terminal device from the RRC connected state to the RRC inactive state, the first access network device may send RNA information to the terminal device. This RNA information may be carried within an RRC release message. Alternatively, the first access network device may send first area information to the terminal device via an RRC release message.

[0152] The RNA can be determined based on the first region information, or the first access network device can generate RNA information based on the first region information. For example, the RNA includes one or more regions in at least one region indicated by the first region information. For example, the first access network device can detect whether there is an Xn interface between itself and the access network device (e.g., the second access network device) corresponding to a certain region (e.g., the first region) in the at least one region indicated by the first region information. Optionally, the first access network device determines whether there is an Xn interface between itself and the first access network device based on the identifier (e.g., the identifier of the second access network device) of the access network device corresponding to a certain region (e.g., the first region). If the first access network device does not record the identifier of the second access network device, then there is no Xn interface between the second access network device and the first access network device. Thus, the first access network device can know the regions of the second access network device that cannot communicate with the first access network device through the first interface based on the first region information, or the first access network device can know more regions based on the first region information, so that the first access network device can select more regions (e.g., one or more regions supported by the second access network device) to configure for the terminal device, thereby configuring a larger RNA for the terminal device.

[0153] Of course, the RNA configured by the first access network device for the terminal device may include the area supported by access network devices that have an Xn interface with the first access network device, or the area supported by access network devices that cannot communicate with the first access network device through the first interface. For example, the first access network device obtains the TAI of access network device A and the TAI of access network device B. Based on the TAI of access network device A and the TAI of access network device B, and the RA indicated by the core network, it can determine that the area served by access network device A and the area served by access network device B are located in the same RA. When access network device A and access network device B do not have an Xn interface with the serving base station, the RNA configured by the serving base station for the UE may include the area served by access network device A and / or access network device B. As another example, the RNA configured by the first access network device for the terminal device may include the area served by access network devices whose communication interface with the first access network device is faulty. For example, if the Xn interface between the second access network device and the first access network device is faulty, the RNA configured by the first access network device for the terminal device may include the area served by the second access network device (e.g., the first area).

[0154] In this embodiment, each access network device can report its supported regions to the first core network element. The first core network element then sends at least one region supported by the access network device to the first access network device, enabling the first access network device to configure the RNA for the terminal device based on the region supported by the at least one access network device. The at least one access network device may include access network devices that cannot communicate with the first access network device through the first interface. Correspondingly, the access network devices corresponding to one or more regions included in the RNA may not have a communication interface with the first access network device. Compared to the requirement that all base stations corresponding to all regions in the RNA must have an Xn interface with the last serving base station, the first region information indicates at least more regions and corresponds to more access network devices. This allows the first access network device to select more regions to configure for the terminal device, thereby configuring a larger RNA for the terminal device. By configuring a larger RNA, the terminal device can maintain an RRC inactive state over a wider area, thus reducing the state switching latency, saving power consumption in establishing RRC connections, and improving communication efficiency when the terminal device needs to re-enter the RRC connected state. Furthermore, at least one region indicated by the first region information sent by the first core network element to the first access network device is within the registered region of the terminal device. When the terminal device moves within the RNA, the registration region update process will not be triggered, which can reduce the complexity of configuring the RNA for the terminal device.

[0155] Example 2:

[0156] The difference between Embodiment 2 and Embodiment 1 is that the second access network device can notify the first core network element of the supported areas, and the first core network element then notifies the first access network device of the areas supported by the second access network device. Similarly, other access network devices can also notify the first core network element of their supported areas, and the first core network element then notifies the first access network device of the areas supported by other access network devices. Thus, the first access network device can obtain areas supported by at least one access network device. In Embodiment 2, the first core network element acts as a relay device between access network devices, used to forward information about the areas supported by the access network devices. Likewise, the first access network device can notify the first core network element of its supported areas, and the first core network element then notifies the second access network device of the areas supported by the first access network device.

[0157] Please refer to Figure 4, which is a flowchart illustrating the communication method provided in Embodiment 2 of this application. Figure 4 uses the interaction between the first access network device, the second access network device, and the first core network element as an example. The descriptions of the first access network device and the first core network element in Embodiment 1 are provided and will not be repeated here.

[0158] S401. The second access network device sends third area information to the first core network element.

[0159] S402, The first core network element sends the third area information and the ID of the second access network device to the first access network device.

[0160] For details regarding S401, please refer to the relevant description in S32; it will not be repeated here. For example, the third area information in S401 can be carried in an NG establishment request message, and the third area information and the ID of the second access network device in S402 can be carried in an NG establishment response message. As another example, the third area information in S401 can be carried in an uplink RAN ​​configuration transmission message, and the third area information and the ID of the second access network device in S402 can be carried in a downlink RAN ​​configuration transmission message.

[0161] Optionally, similar to how the second area information includes updated area information, the third area information may also include updated area information, as detailed in the relevant description in S31 above, which will not be repeated here.

[0162] Optionally, in addition to sending the third area information to the first core network element, the second access network device also sends its own ID to the first core network element. Upon receiving the third area information, the first core network element can send the third area information and the second access network device's ID to the first access network device. In this way, the first access network device can determine at least one area supported by the second access network device.

[0163] Optionally, in addition to sending the third area information to the first core network element, the second access network device may also send area information of other access network devices adjacent to the second access network device to the first core network element. The third area information may include updated area information, such as information about newly added areas, modified areas, or deleted areas.

[0164] It should be understood that other access network devices besides the first and second access network devices will also report the supported regions to the first core network element. In Figure 4, "other access network devices" refers to access network devices other than the first and second access network devices. The first core network element can indicate the regions supported by other access network devices to the first access network device, thereby allowing the first access network device to know at least one region supported by at least one access network device, or allowing the first access network device to determine first region information.

[0165] Similarly, the first access network device can also send the second area information to the first core network element, which will then forward the second area information to other access network devices (such as the second access network device). S403 and S404 in Figure 4 are examples of this.

[0166] S403. The first access network device sends the second area information to the first core network element.

[0167] S404. The first core network element sends the second area information and the ID of the first access network device to the second access network device.

[0168] For details regarding S403, please refer to the relevant description in S31. Furthermore, for S403 and S404, please refer to the relevant descriptions in S401 and S402; they will not be repeated here. For example, the second area information in S403 can be carried in an NG establishment request message, and the second area information and the ID of the first access network device in S404 can be carried in an NG establishment response message. As another example, the second area information in S403 can be carried in an uplink RAN ​​configuration transmission message, and the second area information and the ID of the first access network device in S404 can be carried in a downlink RAN ​​configuration transmission message.

[0169] It should be noted that the execution order of S401 and S403 is not restricted, and correspondingly, the execution order of S402 and S404 is not restricted. Optionally, the third area information and the ID of the second access network device sent by the first core network element to the first access network device can be carried in the response message of the second area information. For example, the second area information is carried in an NG establishment request message, and the third area information and the ID of the second access network device are carried in an NG establishment response message. Another example is that the second area information is carried in an uplink RAN ​​configuration transmission message, and the third area information and the ID of the second access network device are carried in a downlink RAN ​​configuration transmission message. Similarly, the second area information and the ID of the first access network device sent by the first core network element to the second access network device can be carried in the response message of the third area information. For example, the third area information is carried in an NG establishment request message, and the second area information and the ID of the first access network device are carried in an NG establishment response message. Another example is that the third area information is carried in an uplink RAN ​​configuration transmission message, and the second area information and the ID of the first access network device are carried in a downlink RAN ​​configuration transmission message.

[0170] S405, The first access network device sends RNA information to the terminal device.

[0171] For details on the execution of S405, please refer to the relevant description in S302, which will not be repeated here.

[0172] Example 3:

[0173] The difference between Embodiment 3 and Embodiment 1 is that the first access network device and the second access network device are connected to different core network elements. Taking the example of the first core network device connected to a first core network element and the second access network device connected to a second core network element, the first and second core network elements can act as relay devices between access network devices, enabling the first access network device to know at least one area supported by the second access network device, and vice versa.

[0174] Please refer to Figure 5, which is a flowchart illustrating the communication method provided in Embodiment 3 of this application. Figure 5 uses the interaction between the first access network device, the second access network device, the first core network element, and the second core network element as an example. The descriptions of the first access network device and the first core network element in Embodiment 1 are provided and will not be repeated here.

[0175] S501, The first access network device sends the second area information of the first access network device, the ID and TAI of the second access network device to the first core network element.

[0176] Accordingly, the first core network element receives the second area information, the ID and TAI of the second access network device. Optionally, the first access network device may also send its ID to the first core network element, or the first access network device may also send its ID and TAI to the first core network element. It should be understood that the first core network element knows the TAI and ID of the first access network device in advance.

[0177] Optionally, the first access network device may also send area information of other access network devices adjacent to the first core network element to the first core network element, so that the first core network element knows more areas supported by the access network devices.

[0178] S502, the first core network element sends the second area information, the ID and TAI of the second access network device, and the ID and TAI of the first access network device to the second core network element.

[0179] The first core network element can address the second core network element based on the TAI corresponding to the ID of the second access network device, and then send the second area information, the ID and TAI of the second access network device, and the ID and TAI of the first access network device to the second core network element.

[0180] S503, the second core network element sends the second area information to the second access network device.

[0181] The second core network element receives the second area information, the ID and TAI of the first access network device, and sends the second area information to the first access network device. It can also send the ID and TAI of the first access network device to the second access network device.

[0182] Through S501 to S503, the second access network device can obtain the second area information of the first access network device. Similarly, through S504 to S506, the first access network device can obtain the third area information of the second access network device.

[0183] S504. The second access network device sends the third area information of the second access network device, the ID and TAI of the first access network device to the second core network element.

[0184] Accordingly, the second core network element receives the third area information, the ID and TAI of the first access network device. Optionally, the second access network device may also send its ID to the second core network element, or the second access network device may also send its ID and TAI to the second core network element. It should be understood that the second core network element knows the ID and TAI of the second access network device in advance.

[0185] S505, the second core network element sends the third area information, the ID and TAI of the first access network device, and the ID and TAI of the second access network device to the first core network element.

[0186] The first core network element can address the first core network element based on the second area information corresponding to the ID of the first access network device, and then send the third area information, the ID and TAI of the first access network device, and the ID and TAI of the second access network device to the first core network element.

[0187] S506. The first core network element sends third area information to the first access network device.

[0188] The first core network element receives third area information, the ID and TAI of the first access network device, and the ID and TAI of the second access network device. It can send the third area information to the first access network device based on the first access network device's ID. It can also send the ID and TAI of the second access network device to the first access network device.

[0189] Through S504 to S506, the first access network device can obtain the third area information of the second access network device. Similarly, the first access network device can obtain at least one area supported by at least one access network device, or the first access network device can determine the first area information.

[0190] S507, The first access network device sends RNA information to the terminal device.

[0191] The first access network device can determine the RNA based on the first area information, and then send the RNA information to the terminal device. For details on the execution of S507, please refer to the relevant description in S302; it will not be repeated here.

[0192] Example 4:

[0193] The difference between Embodiment 4 and Embodiment 1 is that the first area information sent by the first core network element to the first access network device can be applied to the RNA configuration of multiple terminal devices. For multiple terminal devices, the first core network element only needs to send the first area information once, saving signaling overhead.

[0194] Please refer to Figure 6, which is a flowchart illustrating the communication method provided in an embodiment of this application. Figure 6 illustrates the interaction between a first access network device, a second access network device, and a first core network element. The first access network device is either the serving base station of the terminal device or the last serving base station of the terminal device. The first core network element includes an AMF (Advanced Management Function).

[0195] S601. The first access network device sends the second area information to the first core network element.

[0196] For details regarding S601, please refer to the relevant description in S31; it will not be repeated here.

[0197] S602, The second access network device sends third area information to the first core network element.

[0198] For details regarding S602, please refer to the relevant description in S32; it will not be repeated here. It should be understood that other access network devices besides the first and second access network devices will also report their supported regions to the first core network element. In Figure 6, "other access network devices" refers to access network devices other than the first and second access network devices.

[0199] S603, The first core network element sends the first area information to the first access network device.

[0200] The first area information may indicate an area supported by at least one access network device, or the first area information may indicate at least one area that is supported by at least one access network device. In Embodiment 2, the at least one access network device may include at least one access network device adjacent to the first access network device. Optionally, the first area information may also include an identifier of the at least one access network device, so that the first access network device knows which area(s) is provided by which access network device. To distinguish it from Embodiment 1, Figure 6 uses the example of the first area information indicating at least one area.

[0201] In possible implementations, the first area information may include a first TAC list or a first TAI list, which includes at least one tracking area code, and one tracking area code corresponds to the identifier of at least one cell and / or at least one RAN area code. Alternatively, the first area information may include a first TAC list or a first TAI list, which includes at least one cell ID and / or at least one RAN area code. Optionally, the first TAC list or the first TAI list may also include the ID of at least one access network device. Alternatively, the first area information may include a first TAI list, which includes at least one TAC, one TAC associated with one access network device ID list, and one access network device ID list associated with at least one access network device ID, at least one cell ID, and at least one RAN area code. For example, the first area information has the two implementations shown in Tables 6 and 7.

[0202] Table 6

[0203] Table 7

[0204] Optionally, similar to how the second area information includes updated area information, the first area information may also include updated area information. For example, the first area information may include one or more of the following: information on newly added areas, information on deleted areas, and information on modified areas. Please refer to the relevant description in S31 above for details, which will not be repeated here.

[0205] The first area information can also be carried in interface management messages, or it can be carried in user-related messages. Please refer to the relevant description in Implementation Example 1 for details, which will not be repeated here.

[0206] S604. The first access network device sends RNA information to the terminal device.

[0207] For details on the execution of S604, please refer to the relevant description in S302, which will not be repeated here.

[0208] In this embodiment, each access network device can report its supported regions to the first core network element. The first core network element then sends at least one region supported by the access network device to the first access network device. The first access network device then configures the RNA for the terminal device based on this supported region. Thus, there may be no communication interface between the access network device corresponding to one or more regions included in the RNA and the first access network device. This allows the terminal device to remain inactive within a larger RNA, effectively utilizing its inactive state functions and minimizing latency when entering the connected state. Furthermore, it enables the RAN paging forwarded by the core network to locate the target access network device, thereby improving the paging success rate.

[0209] Example 5:

[0210] Unlike Embodiments 1 to 4, in Embodiment 5, the network management device sends the first area information to the first access network device. This network management device is, for example, an OAM device. The OAM device can be a device that deploys OAM functionality. The network management device in Embodiment 5 can implement the functions of the first core network element in Embodiments 1 and 4, as detailed in the relevant descriptions in Embodiments 1 and 4, which will not be repeated here.

[0211] In the embodiments provided above, the methods provided by the embodiments of this application are described using access network devices (e.g., a first access network device and a second access network device), a first core network element, and a terminal device as examples. In this application, each embodiment can be implemented independently or in combination based on certain inherent connections; in each embodiment, different implementation methods can be implemented in combination or independently. To achieve the functions in the methods provided by the embodiments of this application above, the steps executed by the access network device can be implemented by the access network device itself, or by a functional entity including the access network device, or by different functional entities constituting the access network device. The steps executed by the first core network element can be implemented by the first core network element itself, or by different functional entities constituting the first core network element, or by a functional entity including the first core network element. To achieve the functions in the methods provided by the embodiments of this application above, the access network device and the first core network element can include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. Whether a certain function is executed in the form of hardware structures, software modules, or hardware structures plus software modules depends on the specific application and design constraints of the technical solution.

[0212] Based on the same inventive concept as the method embodiments, this application provides a communication device. The communication device used to implement the above method in the embodiments of this application is described below with reference to the accompanying drawings. The content above can be used in subsequent embodiments, and repeated content will not be repeated.

[0213] Figure 7 is a schematic block diagram of the communication device 700 provided in an embodiment of this application. The communication device 700 can correspondingly implement the functions or steps implemented by the access network device or the first core network element in the various method embodiments described above. For example, the communication device 700 can be an access network device; or, the communication device 700 can be a chip (system) in the access network device; or, the communication device 700 can be a software module of the access network device. Alternatively, the communication device 700 can be a first core network element; or, the communication device 700 can be a chip (system) in the first core network element; or, the communication device 700 can be a software module of the first core network element.

[0214] The communication device 700 may include a processing module 710 and a transceiver module 720. Optionally, it may also include a storage module, which can be used to store instructions (code or program) and / or data. The storage module may be, for example, a memory. The processing module 710 and the transceiver module 720 may be coupled to the storage module. For example, the processing module 710 can read instructions (code or program) and / or data from the storage module to implement a corresponding method. When the communication device 700 is a chip in a first core network element or access network device, the storage module may be an internal storage module within the chip, such as a register or cache. For example, the storage module may also be an external storage module within the first core network element or access network device, such as a read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, such as random access memory (RAM). The above-mentioned units may be set independently or partially or completely integrated.

[0215] Processing module 710 may be a processor or controller, such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing unit (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. Transceiver module 720 is a transceiver, interface circuit, bus, pin, or other possible communication interface for receiving signals from other devices. For example, when the device is implemented as a chip, transceiver module 720 is an interface circuit for the chip to receive signals from other chips or devices, or an interface circuit for the chip to send signals to other chips or devices.

[0216] In one implementation, the communication device 700 can correspondingly implement the behavior and functions of the first access network device in the above method embodiments. The communication device 700 can be an access network device, a component (e.g., a chip or circuit) within the access network device, a part of a chip or chipset in the access network device used to execute the relevant method functions, or a software module in the access network device capable of implementing the above communication method; there are no limitations. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0217] For example, the transceiver module 720 is used to receive first area information from a first core network element and send RNA information to the terminal device. The first area information is used to indicate the identifier of a cell supported by at least one access network device, and / or, the RAN area code supported by at least one access network device. Based on the first area information, the RNA determines that the terminal device is in an RRC inactive state.

[0218] As an optional implementation, RNA includes a first area served by a second access network device in at least one access network device, wherein the second access network device and the communication device 700 cannot communicate based on a first interface, the first interface being a communication interface between access network devices.

[0219] As an optional implementation, the first area information indicates at least one area within the registration area of ​​the terminal device.

[0220] As an optional implementation, the first area information includes a first tracking area code list, which includes at least one tracking area code, and each tracking area code corresponds to the identifier of at least one cell and / or at least one RAN area code.

[0221] As an optional implementation, the first area information also includes the identifier of at least one access network device.

[0222] As an optional implementation, the transceiver module 720 is also used to send second area information, which is used to indicate at least one area supported by the communication device 700.

[0223] As an optional implementation, the second area information includes information about the cell of the communication device 700; and / or, the RAN area code of the communication device 700.

[0224] As an optional implementation, the first region information is contained in the interface management class message, or the first region information is contained in the core network auxiliary information of the inactive user.

[0225] In one implementation, the communication device 700 can correspondingly implement the behavior and functions of the second access network device in the above method embodiments. The communication device 700 can be an access network device, a component (e.g., a chip or circuit) within the access network device, a part of a chip or chipset in the access network device used to execute the relevant method functions, or a software module in the access network device capable of implementing the above communication method; there are no limitations. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0226] For example, the processing module 710 is used to send third area information, which indicates at least one area supported by the communication device 700.

[0227] As an optional implementation, the third area information includes: information about the cell of the communication device 700; and / or, the RAN area code of the communication device 700.

[0228] In one implementation, the communication device 700 can correspondingly implement the behavior and functions of the first core network element in the above method embodiments. The communication device 700 can be a core network element, a component (e.g., a chip or circuit) within a core network element, a part of a chip or chipset within a core network element used to execute related method functions, or a software module in the first core network element capable of implementing the above communication method; there are no limitations. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0229] For example, processing module 710 is used to determine first area information, which indicates the identifier of a cell supported by at least one access network device, and / or the RAN area code supported by at least one access network device. Transceiver module 720 is used to send the first area information to the first access network device.

[0230] As an optional implementation, the transceiver module 720 is also configured to receive at least one area information, wherein the area information indicates at least one area supported by an access network device, and the first area information is determined based on the at least one area information.

[0231] As an optional implementation, the first area information indicates at least one area within the registration area of ​​the terminal device.

[0232] As an optional implementation, the first area information includes a first tracking area code list, which includes at least one tracking area code, and each tracking area code corresponds to the identifier of at least one cell and / or at least one RAN area code.

[0233] As an optional implementation, the first area information also includes: the identifier of at least one access network device.

[0234] As an optional implementation, the first region information can be contained in the core network auxiliary information of the inactive user, or the first region information can be contained in interface management messages.

[0235] When the communication device 700 is a chip-based device or circuit, the transceiver module can be an input / output circuit and / or a communication interface; the processing module is an integrated processor, microprocessor, or integrated circuit.

[0236] Figure 8 is a schematic block diagram of a communication device 800 provided in an embodiment of this application. This communication device 800 can be used to implement the functions of the first access network device, the second access network device, the first core network element, or the OAM in the above embodiments. For example, the communication device 800 can be an access network device, a core network element, or the OAM, or it can be a chip (system) within an access network device, a core network element, or the OAM. In this embodiment, the chip system can be composed of chips or may include chips and other discrete devices. Specific functions can be found in the descriptions in the above method embodiments.

[0237] The communication device 800 includes one or more processors 801, used to implement or support the communication device 800 in implementing the functions of the first access network device, the second access network device, the first core network element, or OAM in the methods provided in the embodiments of this application. See the detailed description in the method examples for details, which will not be repeated here. The processor 801 can also be called a processing unit or processing module, and can implement certain control functions. The processor 801 can be a general-purpose processor or a dedicated processor, etc. For example, it includes: a baseband processor, a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and / or a neural network processor, etc. The baseband processor can be used to process communication protocols and communication data. The central processing unit can be used to control the communication device 800 (e.g., a network device or a terminal device), execute software programs, and / or process data. Different processors can be independent devices or integrated into one or more processors, for example, integrated on one or more application-specific integrated circuits.

[0238] In one design, processor 801 may include program 803 (sometimes referred to as code or instructions) that can be executed on processor 801 to cause communication device 800 to perform the methods described in the embodiments below. In yet another possible design, communication device 800 includes circuitry (not shown in FIG8) for implementing the functions of the first access network device, second access network device, first core network element, or OAM in the above embodiments.

[0239] In one design, the communication device 800 may include one or more memories 802 storing a program 804 (sometimes referred to as code or instructions), which can be run on the processor 801 to cause the communication device 800 to perform the methods described in the above method embodiments.

[0240] In one design, the processor 801 and / or memory 802 may include an AI module 807 and an AI module 808, which are used to implement AI-related functions. The AI ​​modules can be implemented through software, hardware, or a combination of both. For example, the AI ​​module may include a RIC module. For example, the AI ​​module may be a near real-time RIC or a non-real-time RIC.

[0241] In one possible design, the processor 801 and / or memory 802 may also store data. The processor and memory may be configured separately or integrated together.

[0242] In one possible design, when the communication device 800 is a first access network device or a second access network device, the communication device 800 may further include a transceiver and / or an antenna. The processor 801, sometimes referred to as a processing unit, controls the communication device 800. The transceiver, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or simply a transceiver, is used to implement the transmission and reception functions of the communication device 800 via the antenna.

[0243] In one possible design, the communication device 800 may further include one or more of the following components: a wireless communication module, an audio module, an external memory interface, internal memory, a universal serial bus (USB) interface, a power management module, an antenna, a speaker, a microphone, an input / output module, a sensor module, a motor, a camera, or a display screen, etc. It is understood that in some embodiments, the communication device 800 may include more or fewer components, or some components may be integrated, or some components may be separated. These components may be implemented in hardware, software, or a combination of software and hardware.

[0244] Please refer to Figure 9. This application embodiment also provides another communication device 900, including an input / output interface 910 and a logic circuit 920. The input / output interface 910 is used to receive code instructions and transmit them to the logic circuit 920. The logic circuit 920 is used to run the code instructions to execute the method executed by the terminal device or network device in any of the above embodiments. Please refer to the above method embodiments, which will not be repeated here.

[0245] When the communication device 900 is used to execute the method performed by the first access network device, the input / output interface 910 is used to receive first area information from the first core network element and send RNA information to the terminal device. The first area information is used to indicate the identifier of at least one cell supported by the access network device, and / or, the RAN area code supported by at least one access network device. Based on the first area information, the RNA determines that the terminal device is in an RRC inactive state.

[0246] When the communication device 900 performs the method executed by the second access network device, the logic circuit 920 is used to send third area information, which indicates at least one area supported by the second access network device.

[0247] When the communication device 900 is used to execute the method performed by the first core network element, the logic circuit 920 is used to determine first area information, which indicates the identifier of a cell supported by at least one access network device, and / or the RAN area code supported by at least one access network device. The input / output interface 910 is used to send the first area information to the first access network device.

[0248] The communication device in the above embodiments can be an access network device, a core network element, or an OAM (Operational Access Module). It can also be a circuit, a chip applied in the access network device, core network element, or OAM, or other combined devices or components having the aforementioned access network device, core network element, or OAM. When the communication device is an access network device, the transceiver module can be a transceiver, which may include an antenna and radio frequency circuits, etc., and the processing module can be a processor, such as a CPU. When the communication device is a chip system, it can be an FPGA, a dedicated ASIC, a SoC (System-on-a-Chip), a CPU, a network processor (NP), a DSP, a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. The processing module can be the processor of the chip system. The transceiver module or communication interface can be the input / output interface or interface circuit of the chip system. For example, the interface circuit can be a code / data read / write interface circuit. The interface circuit can be used to receive code instructions (the code instructions are stored in memory and can be read directly from memory or through other devices) and transmit them to the processor; the processor can then execute the code instructions to perform the methods described in the above method embodiments. Alternatively, the interface circuit can also be a signal transmission interface circuit between a communication processor and a transceiver.

[0249] This application also provides a communication system, which includes at least two access network devices, a first core network element, and a terminal device. The at least two access network devices include a first access network device and a second access network device. The first access network device is an access network device used to implement the functions related to the above-mentioned communication method. The first core network element is a core network device used to implement the functions related to the above-mentioned communication method.

[0250] This application also provides a computer-readable storage medium including instructions that, when run on a computer, cause the method executed by the first access network device, the second access network device, the first core network element, or the OAM in the above-described communication method to be executed.

[0251] This application also provides a computer program product, including computer program code, which, when executed, causes the method executed by the first access network device, the second access network device, the first core network element, or the OAM in the above-described communication method to be executed.

[0252] This application provides a chip system including a processor and potentially a memory, for implementing the functions of the first access network device, the second access network device, the first core network element, or OAM in the aforementioned communication method. The chip system can be composed of chips or may include chips and other discrete components.

[0253] To achieve the functions of the communication devices shown in Figures 7-9, this application embodiment also provides a chip, including a processor, for supporting the communication device in implementing the functions involved in the first access network device, the second access network device, the first core network element, or OAM in the above method embodiments. In one possible design, the chip is connected to a memory or the chip includes a memory for storing necessary computer programs, instructions, and data for the communication device.

[0254] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0255] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0256] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0257] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0258] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0259] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the essential contributing part of the technical solution of this application, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, external hard drives, ROM, RAM, magnetic disks, or optical disks.

[0260] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, The method is applied to a first access network device or a chip of the first access network device, and the method includes: Receive first area information from a first core network element, wherein the first area information is used to indicate the identifier of a cell supported by at least one access network device, and / or, the radio access network (RAN) area code supported by at least one access network device; The terminal device is sent information about the Radio Access Network Notification Area (RNA), which is determined based on the first area information. The terminal device is in a Radio Resource Control (RRC) inactive state.

2. The method as described in claim 1, characterized in that, The RNA includes a first area served by the second access network device in the at least one access network device. The second access network device and the first access network device cannot communicate based on a first interface, which is a communication interface between access network devices.

3. The method as described in claim 2, characterized in that, The first area information indicates at least one area within the registration area of ​​the terminal device.

4. The method as described in claim 1, characterized in that, The first area information includes a first tracking area code list, which includes at least one tracking area code, and each tracking area code corresponds to the identifier of at least one cell and / or at least one RAN area code.

5. The method according to any one of claims 1-4, characterized in that, The first area information also includes: The identifier of the at least one access network device.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Send second area information, which is used to indicate at least one area supported by the first access network device.

7. The method as described in claim 6, characterized in that, The second area information includes: Information about the cell of the first access network device; and / or, the RAN area code of the first access network device.

8. The method according to any one of claims 1-7, characterized in that, The information for the first region is contained in the interface management class message.

9. The method according to any one of claims 1-8, characterized in that, The first area information includes the core network auxiliary information of inactive users.

10. A communication method, characterized in that, The method is applied to a second access network device or a chip of a second access network device, and the method includes: Send third area information, which is used to indicate at least one area supported by the second access network device.

11. The method as described in claim 10, characterized in that, The third region information includes: The cell information of the second access network device; and / or, the Radio Access Network (RAN) area code of the second access network device.

12. A communication method, characterized in that, The method is applied to a first core network element or a chip of a first core network element, and the method includes: Determine first area information, which is used to indicate the identifier of a cell supported by at least one access network device, and / or the Radio Access Network (RAN) area code supported by at least one access network device; Send the first area information to the first access network device.

13. The method as described in claim 12, characterized in that, The method further includes: Receive at least one area information, wherein one of the area information indicates at least one area supported by an access network device, and the first area information is determined based on the at least one area information.

14. The method as described in claim 12 or 13, characterized in that, The first area information indicates at least one area within the registration area of ​​the terminal device.

15. The method according to any one of claims 12-14, characterized in that, The first area information includes a first tracking area code list, which includes at least one tracking area code, and each tracking area code corresponds to the identifier of at least one cell and / or at least one RAN area code.

16. The method as described in claim 15, characterized in that, The first area information also includes: The identifier of the at least one access network device.

17. The method according to any one of claims 12-16, characterized in that, The first area information includes the core network auxiliary information of inactive users.

18. The method according to any one of claims 12-16, characterized in that, The information for the first region is contained in the interface management class message.

19. A communication device, characterized in that, include: The transceiver module is used to receive first area information from a first core network element and send radio access network notification area (RNA) information to the terminal device; wherein, the first area information is used to indicate the identifier of a cell supported by at least one access network device, and / or, the radio access network (RAN) area code supported by at least one access network device; the RNA is determined according to the first area information, and the terminal device is in a radio resource control (RRC) inactive state; A processing module is used to determine information about the RNA.

20. The apparatus as claimed in claim 19, characterized in that, The RNA includes a first area served by a second access network device among the at least one access network device, wherein the second access network device and the communication device cannot communicate based on a first interface, the first interface being a communication interface between access network devices.

21. The apparatus of claim 20, wherein, The first area information indicates at least one area within the registration area of ​​the terminal device.

22. The apparatus of claim 19, wherein, The first area information includes a first tracking area code list, which includes at least one tracking area code, and each tracking area code corresponds to the identifier of at least one cell and / or at least one RAN area code.

23. The apparatus of any one of claims 19-22, wherein, The first area information also includes: The identifier of the at least one access network device.

24. The apparatus of any one of claims 19-23, wherein, The transceiver module is also used for: Send second area information, which indicates at least one area supported by the communication device.

25. The apparatus of claim 24, wherein, The second area information includes: The cell information of the communication device; and / or the RAN area code of the first access network device.

26. The apparatus of any one of claims 19-25, wherein, The information for the first region is contained in the interface management class message.

27. The apparatus of any one of claims 19-26, wherein, The first area information includes the core network auxiliary information of inactive users.

28. A communications device, characterized by include: A processing module is configured to determine third region information, the third region information being used to indicate at least one region supported by the communication device; The transceiver module is used to send the information from the third region.

29. The apparatus as claimed in claim 28, characterized in that, The third region information includes: Information about the cell of the communication device; and / or, the Radio Access Network (RAN) area code of the communication device.

30. A communications device, characterized by include: The processing module is configured to determine first area information, wherein the first area information is used to indicate the identifier of a cell supported by at least one access network device, and / or the Radio Access Network (RAN) area code supported by at least one access network device; The transceiver module is used to send the first area information to the first access network device.

31. The apparatus of claim 30, wherein, The method further includes: Receive at least one area information, wherein one of the area information indicates at least one area supported by an access network device, and the first area information is determined based on the at least one area information.

32. The apparatus of claim 30 or 31, wherein, The first area information indicates at least one area within the registration area of ​​the terminal device.

33. The apparatus of any one of claims 30-32, wherein, The first area information includes a first tracking area code list, which includes at least one tracking area code, and each tracking area code corresponds to the identifier of at least one cell and / or at least one RAN area code.

34. The apparatus of claim 33, wherein, The first area information also includes: The identifier of the at least one access network device.

35. The apparatus of any one of claims 30-34, wherein, The first area information includes the core network auxiliary information of inactive users.

36. The apparatus of any one of claims 30-34, wherein, The information for the first region is contained in the interface management class message.

37. A communication system, characterized by The communication system includes at least two access network devices, a first core network element, and terminal devices, wherein the at least two access network devices include a first access network device and a second access network device. Wherein, the first core network element is used to send first area information to the first access network device, the first area information being used to indicate the identifier of the cell supported by at least one access network device, and / or the Radio Access Network (RAN) area code supported by at least one access network device; The first access network device is used to send information about the Radio Access Network Notification Area (RNA) to the terminal device. The RNA is determined based on the first area information, and the terminal device is in a Radio Resource Control (RRC) inactive state.

38. A communications device, characterized by The communication device includes at least one processor configured to execute a computer program or perform a method as described in any one of claims 1-9, or as described in any one of claims 10-11, or as described in any one of claims 12-18.

39. A chip or chip system, characterized by The chip or chip system includes: At least one processor and an interface, the at least one processor being configured to call and execute instructions from the interface, wherein when the at least one processor executes the instructions, the method as claimed in any one of claims 1-9 is executed, or the method as claimed in any one of claims 10-11 is executed, or the method as claimed in any one of claims 12-18 is executed.

40. A computer-readable storage medium, comprising: The computer-readable storage medium is used to store a computer program or instructions that, when executed on a computer, cause the method as described in any one of claims 1-9 to be performed, or the method as described in any one of claims 10-11 to be performed, or the method as described in any one of claims 12-18 to be performed.

41. A computer program product, characterised in that, The computer program product includes one or more computer programs or instructions that, when read and executed by a computer, cause the method as described in any one of claims 1-9 to be implemented, or cause the method as described in any one of claims 10-11 to be implemented, or cause the method as described in any one of claims 12-18 to be implemented.

Images