Communication method and communication apparatus
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-02-06
- Publication Date
- 2026-08-13
Smart Images
Figure CN2026077577_13082026_PF_FP_ABST
Abstract
Description
Communication methods and communication devices
[0001] This application claims priority to Chinese Patent Application No. 202510144269.5, filed on February 7, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Technology
[0003] When two access network devices do not have an interface (e.g., an Xn interface or an X2 interface), they need to establish a control plane interface before they can communicate directly. Before establishing the control plane interface, the access network device needs to obtain the transport network layer (TNL) address of the other access network device to send an interface establishment request later.
[0004] For example, when access network device 1 needs to obtain the TNL address of access network device 2, access network device 1 can send a request message to access network device 2 through the core network, so that access network device 2 can send its own TNL address to access network device 1.
[0005] However, in network sharing scenarios, an access network device may support multiple different public land mobile networks (PLMNs). This means that the TNL address of access network device 2 obtained using the above method may not be applicable to all PLMNs. For example, access network device 2 might send the TNL address of PLMN2 to access network device 1, but access network device 1 does not support PLMN2. This results in a mismatch between the PLMNs to which the control plane TNLs of access network device 1 and access network device 2 belong, leading to interface establishment failure.
[0006] How to avoid interface establishment failure caused by mismatch between the PLMNs to which the control plane TNLs belong between access network devices is an urgent problem to be solved. Summary of the Invention
[0007] This application provides a communication method and a communication device to ensure that the PLMN to which the control plane TNL belongs between access network devices is matched or consistent, thereby avoiding interface establishment failure between access network devices.
[0008] Firstly, a communication method is provided, which can be executed by a first access network device or by a component of the first access network device (e.g., a chip, circuit, or chip system). For ease of understanding, the following description uses execution by the first access network device as an example.
[0009] The method includes: sending a request message, the request message being used to request obtaining the TNL address of a second access network device in a first public land mobile network (PLMN), the request message including information of the first PLMN; receiving a first TNL address of the second access network device, the first TNL address being the TNL address of the second access network device in the first PLMN; and sending an interface establishment request message based on the first TNL address, the interface establishment request message being used to request the establishment of an interface between the first access network device and the second access network device.
[0010] Through the above scheme, the first access network device obtains the TNL address of the second access network device from the specified PLMN, and if it supports the PLMN corresponding to the TNL address, it initiates an interface establishment request to the second access network device. This method can ensure that the PLMN to which the control plane TNL belongs between the access network devices is matched or consistent, thus avoiding the failure of interface establishment between the access network devices.
[0011] In some implementations, the request message may also include information about the second TNL address of the first access network device in the first PLMN.
[0012] In some implementations, the first PLMN is a PLMN supported by the first access network device.
[0013] In some implementations, receiving the first TNL address of the second access network device includes receiving a response message to the request message, wherein the response message to the request message includes information about the first TNL address of the second access network device.
[0014] In some implementations, the information of the first PLMN includes: the ID of the first PLMN.
[0015] In some implementations, the request message includes information about multiple PLMNs, which instruct the first access network device to request the TNL address of the second access network device in the multiple PLMNs, including the first PLMN.
[0016] Secondly, a communication method is provided, which can be executed by a second access network device or by a component of the second access network device (e.g., a chip, circuit, or chip system). For ease of understanding, the following description uses the execution by a first access network device as an example.
[0017] The method includes: receiving a request message, the request message being used to request the acquisition of the Transport Network Layer (TNL) address of a second access network device in a first Public Land Mobile Network (PLMN), the request message including information of the first PLMN; sending a first TNL address of the second access network device, the first TNL address being the TNL address of the second access network device in the first PLMN; and receiving an interface establishment request message, the interface establishment request message being used to request the establishment of an interface between the first access network device and the second access network device.
[0018] In some implementations, the second request message may also include information about the second TNL address of the first access network device in the first PLMN.
[0019] In some implementations, the first PLMN is a PLMN supported by the first access network device.
[0020] In some implementations, sending the information of the first TNL address of the second access network device includes sending a response message to the request message, wherein the response message to the request message includes the information of the first TNL address of the second access network device.
[0021] In some implementations, the information of the first PLMN includes: the ID of the first PLMN.
[0022] In some implementations, the request message includes information about multiple PLMNs, which instruct the first access network device to request the TNL address of the second access network device in the multiple PLMNs, including the first PLMN.
[0023] Thirdly, a communication device is provided, which has the function of implementing the method in the first aspect or any possible implementation of the first aspect, or has the function of implementing the method in the second aspect or any possible implementation of the second aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-described function.
[0024] Fourthly, a communication device is provided, comprising at least one processor configured to cause the communication device to execute the method of the first aspect or any possible implementation thereof; or to execute the method of the second aspect or any possible implementation thereof. Optionally, the at least one processor is coupled to at least one memory for storing computer programs or instructions, and the at least one processor is configured to call and run the computer program or instructions from the at least one memory, causing the communication device to execute the method of the first aspect or any possible implementation thereof; or to execute the method of the second aspect or any possible implementation thereof. Optionally, the at least one processor may be included in the communication device or may be configured outside the communication device. Optionally, the communication device further includes the at least one memory. Furthermore, the communication device may optionally include a communication interface coupled to the at least one processor, which can be used to input information and / or data to the at least one processor, or to output information and / or data from the at least one processor. As an example, the communication interface may include an input interface and / or an output interface, or an interface circuit, etc.
[0025] Fifthly, a communication device is provided, comprising a communication interface and a circuit. The communication interface is used to receive a signal to be processed and to transmit the signal to the circuit. The circuit is used to process the signal to perform a method as described in the first aspect or any possible implementation thereof; or to perform a method as described in the second aspect or any possible implementation thereof. Optionally, the communication interface is further used to output the signal processed by the circuit. As an example, the communication interface may be a transceiver, hardware circuit, bus, module, pin, or other type of communication interface. The signal includes information and / or data. Optionally, the communication device may be a chip.
[0026] A sixth aspect provides a computer-readable storage medium storing computer program code or instructions that, when executed on a computer, cause the method of the first aspect or any possible implementation thereof to be implemented; or the method of the second aspect or any possible implementation thereof to be implemented.
[0027] In a seventh aspect, a computer program product is provided, the computer program product comprising computer program code or instructions, which, when executed on a computer, cause the method in the first aspect or any possible implementation thereof to be implemented; or, as in the second aspect or any possible implementation thereof, the method to be implemented.
[0028] Eighthly, a wireless communication system is provided, including a first access network device and a second access network device. The first access network device is configured to perform the method of the first aspect or any possible implementation thereof, and the second access network device is configured to perform the method of the second aspect or any possible implementation thereof. Attached Figure Description
[0029] Figure 1 is a schematic diagram of a network architecture applicable to an embodiment of this application.
[0030] Figure 2 is a schematic diagram of the functions implemented by the central unit (CU) and the distributed unit (DU).
[0031] Figure 3 is a schematic diagram of an ORAN system applicable to an embodiment of this application.
[0032] Figure 4 is a schematic flowchart of the communication method 400 provided in this application.
[0033] Figure 5 is a schematic flowchart of the communication method 400 provided in this application.
[0034] Figure 6 is a schematic flowchart of the communication method 400 provided in this application.
[0035] Figure 7 is a schematic flowchart of the communication method 400 provided in this application.
[0036] Figure 8 is a schematic structural diagram of a communication device provided in this application.
[0037] Figure 9 is a schematic structural diagram of another communication device provided in this application.
[0038] Figure 10 is a schematic structural diagram of the chip provided in this application. Detailed Implementation
[0039] To facilitate understanding of the embodiments of this application, the following points are provided.
[0040] First, in this application, "for indicating" can include both direct and indirect indication. When describing an indication information as indicating A, it can include whether the indication information directly indicates A or indirectly indicates A, but does not necessarily mean that the indication information includes A.
[0041] The information indicated by the instruction information is called the instruction-to-be-instructed information. In the specific implementation, there are many ways to instruct the instruction-to-be-instructed information. The instruction-to-be-instructed information can be sent as a whole, or it can be divided into multiple sub-information messages and sent separately. Furthermore, the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.
[0042] Second, in this application, the words "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0043] Third, in the embodiments of this application, "under the circumstances", "when", and "if" can sometimes be used interchangeably. It should be noted that when the distinction is not emphasized, their intended meanings are consistent.
[0044] Fourth, the term "and / or" in the embodiments of this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. In addition, the character " / " in this document generally indicates that the related objects before and after it have an "or" relationship.
[0045] Fifth, the various message names or device names involved in the embodiments of this application are merely examples and do not constitute any limitation on the scope of protection of this application. For example, messages may have different names, as long as they can achieve the corresponding functions.
[0046] Sixth, the terms "message", "information", or "information element (IE)" can be used interchangeably in this article. There are no restrictions on the names of messages or information, as long as they can achieve the corresponding functions.
[0047] In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, and "send information" can include direct transmission or indirect transmission through other units or modules. "Receive information from YY" can be understood as the source of the information being YY, and "receive information" can include direct reception from YY or indirect reception from YY through other units or modules. Besides air interface transmission or reception signals implemented at the system level, such as network devices or terminal devices, "send" can also be understood as the "output" of a chip interface, and "receive" can also be understood as the "input" of a chip interface. For example, a modem or system-on-a-chip (SoC) chip or system-in-package (SIP) chip transmits or receives signals. "Send" or "receive" can also be performed through device components, for example, by using buses, traces, or interfaces to transmit or receive signals through several parts, modules, or chips of a device.
[0048] The technical solutions in this application will now be described with reference to the accompanying drawings.
[0049] The technical solutions of this application can be applied to satellite communication systems, high altitude platform station (HAPS) communication, and non-terrestrial network (NTN) systems such as unmanned aerial vehicles (UAVs), including integrated communication and navigation (ICAN) systems, GNSS, and ultra-dense low-Earth orbit satellite communication systems. Satellite communication systems can be integrated with traditional mobile communication systems. For example, the mobile communication system can be a fourth-generation (4G) communication system (e.g., Long Term Evolution (LTE) system), a worldwide interoperability for microwave access (WiMAX) communication system, a fifth-generation (5G) communication system (e.g., new radio (NR) system), and future mobile communication systems.
[0050] In communication systems, the portion operated by the operator can be referred to as a public land mobile network (PLMN), or operator network, etc. A PLMN is a network established and operated by operators to provide land mobile communication services to the public; it is primarily a public network where mobile network operators (MNOs) provide mobile broadband access services to users. The PLMN described in this application embodiment can specifically be a network conforming to the 3rd Generation Partnership Project (3GPP) standard requirements, or simply a 3GPP network. 3GPP networks typically include, but are not limited to, 5G networks, 4G networks, and other future communication systems.
[0051] Figure 1 is a schematic diagram of the communication system applicable to this application. As shown in Figure 1, the communication system 100 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal (120a-120j in Figure 1, collectively referred to as 120). RAN may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in Figure 1). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.
[0052] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, NTN (non-terrestrial network) systems, or future-oriented evolution systems. RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system, or a communication system that integrates two or more of the above systems.
[0053] The terminal 120 can also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the device form of the terminal.
[0054] RAN node 110, sometimes referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and assists terminals in achieving wireless access. Multiple RAN nodes 110 in communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.
[0055] 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 next-generation base station in a future mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU).
[0056] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes implementing some of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as the baseband unit (BBU). The CU and DU nodes separate the gNB's protocol layers; some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU. As one implementation, the CU deploys the Radio Resource Control (RRC) layer, PDCP layer, and Service Data Adaptation Protocol (SDAP) layer in the protocol stack; the DU deploys the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical Layer (PHY) in the protocol stack. Thus, the CU has the processing capabilities for RRC, PDCP, and SDAP. The DU has the processing capabilities for RLC, MAC, and PHY. It is understood that the above functional division is merely an example and does not constitute a limitation on the CU and DU. The RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH).
[0057] Core network equipment refers to the equipment in the core network (CN) that provides service support to terminals. Examples of core network equipment include: access and mobility management function (AMF) entities, session management function (SMF) entities, user plane function (UPF) entities, etc., which will not be listed here. The AMF entity is responsible for terminal access management and mobility management; the SMF entity is responsible for session management, such as user session establishment; and the UPF entity can be a user plane function entity, primarily responsible for connecting to external networks. It should be noted that in this application, entities can also be referred to as network elements or functional entities. For example, an AMF entity can also be called an AMF network element or an AMF functional entity, and similarly, an SMF entity can also be called an SMF network element or an SMF functional entity.
[0058] Figure 2 is a schematic diagram of the functions implemented by CU and DU.
[0059] As shown in Figure 2(a), the CU can implement the functions of the radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, and service data adaptation protocol (SDAP) layer in the 3rd generation partnership project (3GPP) standard. The DU can implement the functions of the radio link control (RLC) layer and medium access control (MAC) layer in the 3GPP standard, and can also complete some or all of the physical layer (PHY) functions. For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications. The RU can be used to implement the radio frequency signal transmission and reception functions.
[0060] As shown in Figure 2(b), when the CU is divided into CU-CP and CU-UP, CU-CP is used to implement the functions of the RRC layer and the control plane (PDCP-C) function of the PDCP layer. CU-UP is used to implement the functions of the SDAP layer and the user plane (PDCP-U) function of the PDCP layer.
[0061] In Figure 2, E1 is the interface between CU-CP and CU-UP, F1 is the interface between CU and DU, F1-C is the interface between CU-CP and DU, and F1-U is the interface between CU-UP and DU.
[0062] In different systems, CU (or CU-CP and CU-UP), DU, or RU can also have different names. For example, in an O-RAN system, CU can also be called an open CU (O-CU), DU can also be called an open DU (O-DU), and RU can be called an open RU (O-RU). CU-CP can also be called an open CU-CP (O-CU-CP), and CU-UP can also be called an open CU-UP (O-CU-UP). It should be understood that the O-RAN system aims to achieve an intelligent and open access network. The main feature of the O-RAN system is the separation of hardware and software, realizing the virtualization of network functions and the standardization of hardware. In addition, the O-RAN system can also introduce artificial intelligence (AI) or machine learning (ML).
[0063] For example, Figure 3 is a schematic diagram of an ORAN system, which may include one or more O-CUs, O-DUs, O-RUs, etc. Specific protocol layer functions can be found in Table 1.
[0064] Table 1. Correspondence between RAN nodes and their achievable protocol layer functions in the ORAN system.
[0065] Any of the CU (or CU-CP, CU-UP), DU, and RU units in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. In the ORAN system, any of the O-CU (or O-CU-CP, O-CU-UP), O-DU, and O-RU units in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.
[0066] It is understood that the segmentation of the protocol layer functions of the RAN nodes shown in Table 1 is only an example and does not constitute a limitation on CU, DU, and RU.
[0067] To facilitate understanding, some concepts or terms involved in this application will be explained first.
[0068] 1. Interfaces between RAN devices
[0069] Xn interface: The interface between NR RAN devices (such as base stations, CUs, CU-CPs, or CU-UPs); where Xn-c is the control plane Xn interface and Xn-u is the user plane Xn interface.
[0070] X2 Interface: The interface between LTE RAN devices; X2-c is the control plane X2 interface, and X2-u is the user plane X2 interface. In NR, the X2 interface is mainly used in E-UTRA-NR dual connectivity (EN-DC) scenarios, where the master station is an LTE RAN device that connects to the LTE core network through the X2 interface.
[0071] 2. Control plane address acquisition mechanism between RANs
[0072] If RAN node 1 (the source RAN node) knows the RAN node ID of RAN node 2 (also known as the target RAN node or candidate RAN node), but does not know the TNL address used for the stream control transmission protocol (SCTP) connection, then the RAN node can use the core network (specifically, the Access Management Function (AMF) or Mobility Management Entity (MME) to which the RAN is connected) to determine the TNL address.
[0073] Specifically, RAN Node 1 can send a request message to the core network equipment to request the TNL address of RAN Node 2. This request message carries information such as the ID of RAN Node 1, the ID of RAN Node 2, and one or more TNL addresses of RAN Node 1. The core network can then relay this request message to RAN Node 2 based on its ID. Similarly, after obtaining the ID of RAN Node 1, RAN Node 2 can also send messages to RAN Node 1 through the core network.
[0074] For ease of description, in the embodiments of this application, the interaction between RAN Node 1 and RAN Node 2 can be understood as RAN Node 1 and RAN Node 2 interacting through the core network. For example, RAN Node 1 sending a message to RAN Node 2 can be understood as RAN Node 1 sending a message to RAN Node 2 through the core network.
[0075] In one implementation, RAN Node 1 sends an interface establishment request message to RAN Node 2. After RAN Node 1 sends a request message to RAN Node 2, RAN Node 2 sends a response message to RAN Node 1. The response message carries the TNL address of RAN Node 2, so that RAN Node 1 can send an interface establishment request message based on the TNL address of RAN Node 2.
[0076] In another implementation, RAN Node 2 sends the interface establishment request message. After RAN Node 1 sends a request message to RAN Node 2, RAN Node 2 can directly send an interface establishment request message to RAN Node 1 based on the TNL address of RAN Node 1 carried in the request message.
[0077] 3. Interface Instance
[0078] An interface instance is a concrete implementation or application of an interface in a specific context, representing the actual use of an interface. Each interface instance typically corresponds to a specific interaction or session. For example, when multiple users communicate through the same interface, each session can be considered an instance of that interface.
[0079] On the same physical transmission channel, multiple logically independent control plane interfaces are distinguished by identifiers. For example, in a network sharing scenario, multiple PLMNs share the same access network equipment, and each PLMN corresponds to an independent interface instance.
[0080] Based on the background technology and the above description, in a network sharing scenario, a RAN node can have multiple different PLMNs. In the control plane address acquisition mechanism described above, the source node and the target node can only provide one or more TNL addresses for one PLMN, making it impossible to generate different TNL addresses for different PLMNs. This leads to the following problems:
[0081] If the interface establishment is initiated by RAN node 1, the TNL address sent by RAN node 2 may default to PLMN02 (the primary PLMN of RAN node 2) when RAN node 1 triggers the interface establishment. However, RAN node 1 is the node of PLMN01, which will cause the interface establishment to fail.
[0082] If the interface establishment is initiated by RAN node 2, RAN node 1 will send its own TNL address to RAN node 2. The TNL address of RAN node 1 may be generated for PLMN02, but RAN node 2 does not support PLMN02 (for example, RAN node 2's PLMN is one or more other PLMNs besides PLMN02), which will also cause the interface establishment to fail.
[0083] In view of this, this application provides a communication method that introduces PLMN interaction during the TNL address acquisition process between RANs, thereby avoiding interface establishment failure caused by PLMN mismatch between the control plane TNLs of the RANs.
[0084] For ease of understanding and explanation, the following description of the communication method of this application embodiment uses the interaction between access network devices as an example, but this should not constitute any limitation on the execution subject of the communication method of this application embodiment. For example, the method executed by the access network device can also be executed by the module of the access network device (such as a circuit, chip or chip system, etc.), or it can be implemented by a logical node, logical module or software that can implement all or part of the functions of the access network device.
[0085] Figure 4 illustrates a communication method 400 provided in this application, which includes at least some of the steps shown in Figure 4.
[0086] S410, the second access network device sends information about N TNL addresses of the second access network device to the first access network device, where N is a positive integer; correspondingly, the first access network device receives information about N TNL addresses of the second access network device.
[0087] Optionally, the information for the N TNL addresses may include the N TNL addresses themselves, or it may include the information for the N TNL addresses and the N PLMNs. The PLMN information may be the PLMN's identity (ID).
[0088] Among them, the N TNL addresses correspond to N PLMNs, and each PLMN in the N PLMNs corresponds to one TNL address in the N TNL addresses.
[0089] Among them, the N TNL addresses include the first TNL address, the N PLMNs include the first PLMN, and the first TNL address is the TNL address of the second access network device in the first PLMN.
[0090] Optionally, the second access network device sends information about N TNL addresses of the second access network device to the first access network device, including: the second access network device sending a first request message to the first access network device, the first request message being used to request to obtain the TNL addresses of the first access network device, the first request message including information about N TNL addresses of the second access network device.
[0091] Optionally, the second access network device sends information about N TNL addresses of the second access network device to the first access network device, including: a response message to the second access network device sending a second request message to the first access network device, the second request message being used to request the acquisition of the TNL addresses of the second access network device, the second request message including information about the N TNL addresses of the second access network device. It should be understood that the first access network device sends the second request message to the second access network device before the second access network device sends the response message to the first access network device.
[0092] It should be understood that when the second access network device sends information about N TNL addresses of the second access network device and N PLMNs corresponding to those N TNL addresses to the first access network device, it can be understood as the second access network device sending information about N TNL addresses of the second access network device and N PLMNs corresponding to those N TNL addresses to the first access network device through the core network (e.g., AMF or MME).
[0093] Specifically, the second access network device sends N TNL addresses of the second access network device and information about the N PLMNs corresponding to the N TNL addresses to the AMF / MME, and the AMF / MME sends information about N TNL addresses of the second access network device and information about the N PLMNs corresponding to the N TNL addresses to the first access network device.
[0094] S420, if the first access network device supports the first PLMN, the first access network device sends an interface establishment request message to the second access network device according to the first TNL address. The interface establishment request message is used to request the establishment of an interface between the first access network device and the second access network device.
[0095] Optionally, the first access network device determines a first PLMN among the N PLMNs, and the first PLMN is a PLMN supported by the first access network device.
[0096] S430, the second access network device sends an interface establishment response message to the first access network device.
[0097] Through the above scheme, the first access network device initiates an interface establishment request to the second access network device based on the TNL information corresponding to at least one PLMN supported by the second access network device. This method can ensure that the PLMNs of the control plane TNLs between access network devices are matched or consistent, thus avoiding interface establishment failure between access network devices.
[0098] The following sections will further explain method 400 using specific scenarios, specifically methods 500 and 600. It should be understood that methods 500 and 600 are, respectively, specific implementations of method 400.
[0099] Figure 5 illustrates a communication method 500 provided in this application, which includes at least some of the steps shown in Figure 5.
[0100] S510, Access Network Device 1 (i.e., an example of the first access network device) sends a second request message to Access Network Device 2 (i.e., an example of the second access network device), the second request message being used to request to obtain the TNL address of Access Network Device 2.
[0101] The second request message includes information about M PLMNs, where M is a positive integer.
[0102] Optionally, the M PLMNs are PLMNs supported by access network device 1.
[0103] Optionally, the M PLMNs represent access network device 1 requesting to obtain the TNL address of access network device 2 in the M PLMNs through the second request message. For example, if the second request message includes PLMN01 and PLMN02, it means that access network device 1 is requesting to obtain the TNL address of access network device 2 in PLMN01 and / or PLMN02.
[0104] Optionally, the second request message may also include information on the M TNL addresses of the access network device 1 corresponding to the M PLMNs. Each of the M TNL addresses corresponds one-to-one with one of the M PLMNs, and each PLMN corresponds to one of the TNL addresses among the M TNL addresses.
[0105] Specifically, the second request message sent by access network device 1 to access network device 2 includes: access network device 1 sending a second request message to core network device (AMF / MME), and the core network device sending the second request message to access network device 2.
[0106] For example, if the core network device is AMF, the second request message sent by access network device 1 to AMF is carried in the uplink access network configuration transfer message, and the second request message sent by AMF to access network device 2 is carried in the downlink access network configuration transfer message.
[0107] For example, if the core network device is an MME, the second request message sent by access network device 1 to the MME is carried in the evolved NB configuration transfer message, and the second request message sent by the MME to access network device 2 is carried in the MME RAN configuration transfer message.
[0108] Optionally, the second request message may also include the identification information of access network device 1 and the identification information of access network device 2.
[0109] The identification information of access network device 1 includes at least one of the following: the ID of access network device 1, the tracking area identity (TAI) information (selected TAI) of access network device 1, and the cell global identifier (CGI) information. The identification information of access network device 2 includes at least one of the following: the ID of access network device 2, and the TAI information (selected TAI) of access network device 2. The TAI consists of the PLMN ID and TAC, and the CGI consists of the PLMN ID and cell ID.
[0110] S520, Access Network Device 2 sends a response message (hereinafter referred to as the second response message) to Access Network Device 1 in response to the second request message. The second response message includes information on N TNL addresses of Access Network Device 2, where N is a positive integer. Correspondingly, Access Network Device 1 receives the second response message.
[0111] Optionally, the information for the N TNL addresses may include the N TNL addresses themselves, or it may include the information for the N TNL addresses and the N PLMNs. The PLMN information may be the PLMN's ID.
[0112] Among them, the N TNL addresses correspond to N PLMNs, and each PLMN in the N PLMNs corresponds to one TNL address in the N TNL addresses.
[0113] Among them, the N TNL addresses include the first TNL address, the N PLMNs include the first PLMN, and the first TNL address is the TNL address of the second access network device in the first PLMN.
[0114] Optionally, the N PLMNs are PLMNs supported by access network device 2.
[0115] Optionally, the N PLMNs are determined by access network device 2 based on the M PLMNs in the second request message. These M PLMNs are PLMN information requested by access network device 1 from access network device 2, used to request access network device 2 to obtain the TNL address of access network device 2 within these M PLMNs. In other words, these M PLMNs are the PLMNs corresponding to the TNL address of access network device 2 requested by access network device 1. For example, access network device 2 can determine the N PLMNs it supports from the M PLMNs. It should be understood that in this case, the M PLMNs include the N PLMNs.
[0116] Specifically, the access network device 2 sends a second response message to the access network device 1, including: the access network device 1 sending a second response message to the core network device (AMF / MME), and the core network device sending the second response message to the access network device 2.
[0117] For example, if the core network device is AMF, the second response message sent by access network device 2 to AMF is carried in the uplink access network configuration transfer message, and the second response message sent by AMF to access network device 1 is carried in the downlink access network configuration transfer message.
[0118] For example, if the core network device is an MME, the second response message sent by access network device 2 to the MME is carried in the evolved NB configuration transfer message, and the second response message sent by the MME to access network device 1 is carried in the MME RAN configuration transfer message.
[0119] Optionally, the second response message may also include the identification information of access network device 1 and the identification information of access network device 2.
[0120] The identification information of access network device 1 includes at least one of the following: the ID of access network device 1, the tracking area identity (TAI) information (selected TAI) of access network device 1, and the cell global identifier (CGI) information. The identification information of access network device 2 includes at least one of the following: the ID of access network device 2, and the TAI information (selected TAI) of access network device 2. The TAI consists of the PLMN ID and TAC, and the CGI consists of the PLMN ID and cell ID.
[0121] S530, when access network device 1 determines that it supports the first PLMN, it sends an interface establishment request message according to the first TNL address. The interface establishment request message is used to request the establishment of an interface between access network device 1 and access network device 2.
[0122] S540, Access Network Device 2 sends an interface establishment response message to Access Network Device 1.
[0123] Through the above scheme, access network device 1 initiates an interface establishment request to access network device 2 based on the TNL information corresponding to at least one PLMN supported by access network device 2. This method can ensure that the PLMNs of the control plane TNLs between RANs are matched or consistent, improve the success rate of SCTP connection establishment between RANs, and reduce the failure of interface establishment between RANs.
[0124] Figure 6 illustrates a communication method 600 provided in this application, which includes at least some of the steps shown in Figure 6.
[0125] S610, access network device 3 (i.e., an example of the second access network device) sends a first request message to access network device 4 (i.e., an example of the first access network device), the first request message being used to request to obtain the TNL address of access network device 4.
[0126] The first request message includes information on N TNL addresses of access network device 3, where N is a positive integer.
[0127] Optionally, the information for the N TNL addresses may include the N TNL addresses themselves, or it may include the information for the N TNL addresses and the N PLMNs. The PLMN information may be the PLMN's ID.
[0128] Among them, the N TNL addresses correspond to N PLMNs, and each PLMN in the N PLMNs corresponds to one TNL address in the N TNL addresses.
[0129] Among them, the N TNL addresses include the first TNL address, the N PLMNs include the first PLMN, and the first TNL address is the TNL address of the second access network device in the first PLMN.
[0130] Optionally, the N PLMNs are PLMNs supported by access network device 3.
[0131] Optionally, the N PLMNs represent access network device 3 requesting to obtain the TNL address of access network device 4 in the N PLMNs through the first request message. For example, if the first request message includes PLMN01 and PLMN02, it means that access network device 3 is requesting to obtain the TNL address of access network device 4 in PLMN01 and / or PLMN02.
[0132] Optionally, the first request message may also include information about the N PLMNs.
[0133] Specifically, the access network device 3 sends a first request message to the access network device 4, including: the access network device 3 sends a first request message to the core network device (AMF / MME), and the core network device sends the first request message to the access network device 4.
[0134] For example, if the core network device is AMF, the first request message sent by access network device 3 to AMF is carried in the uplink access network configuration transfer message, and the first request message sent by AMF to access network device 4 is carried in the downlink access network configuration transfer message.
[0135] For example, if the core network device is an MME, the first request message sent by the access network device 3 to the MME is carried in the evolved NB configuration transfer message, and the first request message sent by the MME to the access network device 4 is carried in the MME RAN configuration transfer message.
[0136] Optionally, the first request message may also include the identification information of access network device 3 and the identification information of access network device 4.
[0137] The identification information of access network device 3 includes at least one of the following: the ID of access network device 3, the tracking area identity (TAI) information (selected TAI) of access network device 3, and the cell global identifier (CGI) information. The identification information of access network device 4 includes at least one of the following: the ID of access network device 4, and the TAI information (selected TAI) of access network device 4. The TAI consists of the PLMN ID and TAC, and the CGI consists of the PLMN ID and cell ID.
[0138] S620, when access network device 4 determines that it supports the first PLMN, it sends an interface establishment request message according to the first TNL address. The interface establishment request message is used to request the establishment of an interface between access network device 3 and access network device 4.
[0139] S630, Access network device 3 sends an interface establishment response message to access network device 4.
[0140] Through the above scheme, the access network device 4 initiates an interface establishment request to the access network device 3 based on the TNL information corresponding to at least one PLMN supported by the access network device 3. This method can ensure that the PLMNs of the control plane TNLs between RANs are matched or consistent, improve the success rate of SCTP connection establishment between RANs, and reduce the failure of interface establishment between RANs.
[0141] The method 400 described above is proposed for scenarios where different PLMNs correspond to different TNL addresses. This application also provides another communication method 700, applicable to situations where multiple PLMNs share the same access network device (or the same interface) in a network sharing scenario. Specifically, an interface instance is associated with a PLMN ID, and different interface instances correspond to different PLMNs, or different PLMNs correspond to different interface instances. It should be understood that the TNL address in method 700 applies to multiple PLMNs.
[0142] Figure 7 illustrates a communication method 700 provided in this application, which includes at least some of the steps shown in Figure 7.
[0143] S710, the first access network device sends a first interface establishment request message to the second access network device. The first interface establishment request message is used to request the establishment of a first interface between the first access network device and the second access network device. The first interface establishment request message includes the identifier of the first interface instance of the first interface and the information of the PLMN corresponding to the first interface instance. Correspondingly, the second access network device receives the first interface establishment request message.
[0144] It should be understood that the first interface may include multiple interface instances, each corresponding to a different PLMN. The first access network device sends the identifier of the first interface instance and the PLMN information corresponding to the first interface instance to the second access network device, so that the second access network device can determine the interface establishment request for different PLMNs.
[0145] It should be understood that step S710 is performed after the first access network device obtains the TNL address of the second access network device. The specific method for obtaining the TNL address can be referred to the description of the control plane address acquisition mechanism between RANs above.
[0146] S720, the second access network device sends a response message to the first access network device to the first interface establishment request message.
[0147] Specifically, the second access network device establishes the first interface based on the identifier of the first interface instance and the information of the PLMN corresponding to the first interface instance.
[0148] The above scheme, based on the existing technology where the source RAN node and / or target RAN node only provide TNL information for a PLMN, supports different PLMNs to distinguish different PLMNs by using different interface instances when establishing inter-RAN interfaces using this TNL information, thereby improving the probability of PLMN matching or consistency between inter-RAN interface instances.
[0149] It should be understood that the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0150] It should also be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
[0151] The above is a detailed description of the communication method provided in this application. The following describes the communication device provided in this application.
[0152] In order to realize the functions of the communication device (e.g., terminal device or network device) in the embodiments of this application, the communication device can implement the corresponding functions in the form of hardware and / or software.
[0153] Figure 8 is a schematic structural diagram of a communication device provided in this application. As shown in Figure 8, the communication device 1000 includes a processing module 1001 and a communication module 1002. The communication device 1000 can be a communication device, or a device applied to a communication device and capable of realizing the corresponding functions of the communication device, such as a chip, processor, or circuit. Exemplarily, the communication device can be a terminal device or a network device, as in the method embodiment.
[0154] The communication module can also be a transceiver module, transceiver, transceiver device, or transceiver unit. The processing module can also be a processor, processing board, processing unit, or processing device. Optionally, the communication module is used to execute the sending or receiving operations of the terminal device or network device in any of the method embodiments. The device in the communication module that implements the receiving function can be considered a receiving unit, and the device in the communication module that implements the sending function can be considered a sending unit; that is, the communication module includes a receiving unit and a sending unit. The processing module is used to execute the internal implementation-related operations / processing of the terminal device or network device in any of the method embodiments. The specific operations of each module can be found in the descriptions in the method embodiments and will not be repeated here.
[0155] Alternatively, the communication module and / or processing module can be implemented as virtual modules. For example, the processing module can be implemented as a software functional unit or a virtual device, and the communication module can be implemented as a software function or a virtual device. Alternatively, the processing module or communication module can also be implemented as a physical device. For example, the communication device can be a chip, such as a system-on-chip (SoC), hardware circuitry, etc. The communication module can be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operation) and output operations (corresponding to the aforementioned sending operation); the processing module can be an integrated circuit or logic circuit, etc.
[0156] The module division in this application is illustrative and represents only one logical functional division. In actual implementation, other division methods are possible. Furthermore, the functional modules in the various examples of this application can be integrated into one module, exist as separate physical entities, or be integrated into one module. The integrated modules described above can be implemented in hardware, as software functional modules, or as a combination of hardware and software functional modules; no limitation is imposed.
[0157] Figure 9 is a schematic structural diagram of another communication device provided in this application. The communication device 1100 can be used to implement the functions of any communication device (e.g., a terminal device or a network device) in the communication system described in the foregoing examples. Optionally, the communication device 1100 can be a chip or a chip system. Optionally, in this application, the chip system can be composed of chips or may include chips and other discrete devices. The communication device 1100 may include at least one processor 1110. Optionally, the processor 1110 (or processing device) is coupled to a memory, which may be located within the communication device, or the memory may be integrated with the processor, or the memory may be located outside the communication device. For example, the communication device 1100 may also include at least one memory 1120. The memory 1120 stores computer programs / instructions or data necessary for implementing any of the above method embodiments; the processor 1110 may execute the computer programs / instructions or data stored in the memory 1120 to complete the corresponding functions of the terminal device or mobility management network element in any of the above embodiments.
[0158] Optionally, the communication device 1100 may further include a communication interface 1130, through which the communication device 1100 can interact with other devices. For example, the communication interface 1130 may be a transceiver, circuit, bus, module, pin, or other type of communication interface. When the communication device 1100 is a chip-type device or circuit, the communication interface 1130 in the device 1100 may also be an input / output circuit, capable of inputting information (or receiving information) and / or outputting information (or sending information). The processor may be an integrated circuit or logic circuit, etc., and the processor can determine the output information based on the input information.
[0159] The coupling in this application refers to indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 1110 may operate in conjunction with the memory 1120 and the communication interface 1130. This application does not limit the connection medium between the processor 1110, the memory 1120, and the communication interface 1130.
[0160] Optionally, as shown in Figure 9, the processor 1110, the memory 1120, and the communication interface 1130 are interconnected via a bus 1140. The bus 1140 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one line is used to represent the bus 1140 in Figure 9, but this does not mean that there is only one bus or one type of bus.
[0161] Figure 10 is a schematic structural diagram of the chip provided in this application. The chip 30 includes a circuit 31 and a communication interface 32. The circuit 31 can be a logic circuit, an integrated circuit, etc., and the communication interface 32 can also be called an input / output circuit, input / output interface, interface circuit, etc., which can input information (or receive information) or output information (or send information). The chip 30 can execute the methods executed by the terminal device or network device in the various embodiments of this application.
[0162] In addition, this application also provides a computer-readable storage medium storing computer instructions, which, when executed on a computer, cause operations and / or processes performed by a terminal device or network device in the various method embodiments of this application to be executed.
[0163] This application also provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are run on a computer, the operations and / or processes performed by a terminal device or network device in the various method embodiments of this application are executed.
[0164] Furthermore, this application also provides a chip including a processor. A memory for storing a computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory, so that operations and / or processes performed by a terminal device or network device in any method embodiment are executed. Further, the chip may also include a communication interface. The communication interface may be an input / output interface or an interface circuit, etc. Further, the chip may also include the memory.
[0165] This application provides a communication system, including the terminal device and network device in the above method embodiments.
[0166] The processor in this application embodiment has signal processing capabilities and can be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., capable of implementing or executing the methods, steps, and logic block diagrams disclosed in this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in this application can be directly manifested as being executed by the hardware processor, or executed by a combination of hardware and software modules within the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.
[0167] In the embodiments of this application, the memory can be volatile memory or non-volatile memory, or it can include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0168] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0169] Those skilled in the art will clearly 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.
[0170] 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.
[0171] 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.
[0172] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0173] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0174] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A communication method, characterized in that, Applied to a first access network device, the method includes: Send a request message, the request message being used to request the acquisition of the Transport Network Layer (TNL) address of the second access network device in the first Public Land Mobile Network (PLMN), the request message including information of the first PLMN; Receive the first TNL address of the second access network device, wherein the first TNL address is the TNL address of the second access network device in the first PLMN; An interface establishment request message is sent according to the first TNL address. The interface establishment request message is used to request the establishment of an interface between the first access network device and the second access network device.
2. The method according to claim 1, characterized in that, The request message also includes information about the second TNL address of the first access network device in the first PLMN.
3. The method according to claim 1 or 2, characterized in that, The first PLMN is a PLMN supported by the first access network device.
4. The method according to any one of claims 1 to 3, characterized in that, The receipt of the first TNL address of the second access network device includes: A response message to the request message is received, wherein the response message to the request message includes information about the first TNL address of the second access network device.
5. The method according to any one of claims 1 to 4, characterized in that, The information of the first PLMN includes: the ID of the first PLMN.
6. The method according to any one of claims 1 to 5, characterized in that, The request message includes information about multiple PLMNs, which instruct the first access network device to request the TNL address of the second access network device in the multiple PLMNs, including the first PLMN.
7. A communication method, characterized in that, Applied to a second access network device, the method includes: A request message is received, the request message being used to request the acquisition of the Transport Network Layer (TNL) address of the second access network device in the first Public Land Mobile Network (PLMN), the request message including information about the first PLMN; Send the first TNL address of the second access network device, wherein the first TNL address is the TNL address of the second access network device in the first PLMN; Receive an interface establishment request message, which is used to request the establishment of an interface between the first access network device and the second access network device.
8. The method according to claim 7, characterized in that, The second request message also includes information about the second TNL address of the first access network device in the first PLMN.
9. The method according to claim 7 or 8, characterized in that, The first PLMN is a PLMN supported by the first access network device.
10. The method according to any one of claims 7 to 9, characterized in that, The step of sending the information of the first TNL address of the second access network device includes: Send a response message to the request message, the response message of the request message including information about the first TNL address of the second access network device.
11. The method according to any one of claims 7 to 10, characterized in that, The information of the first PLMN includes: the ID of the first PLMN.
12. The method according to any one of claims 7 to 11, characterized in that, The request message includes information about multiple PLMNs, which instruct the first access network device to request the TNL address of the second access network device in the multiple PLMNs, including the first PLMN.
13. A communication device, characterized in that, It includes at least one processor, the at least one processor being configured to execute a computer program or instructions stored in a memory to cause the method of any one of claims 1 to 6 to be executed; or to cause the method of any one of claims 7 to 12 to be executed.
14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of claims 1 to 6; or to perform the method as described in any one of claims 7 to 12.