Communication method and communication apparatus

Abstract

The application provides a communication method and a communication device. The method comprises: receiving first information from a core network device, the first information comprising a correspondence between an identifier of a terminal device and a tracking identifier; receiving a paging message from the core network device, the paging message being used for paging the terminal device and carrying the tracking identifier; and determining whether to send second information to a network management device based on the first information and the paging message, the second information comprising information related to the paging. By receiving the correspondence between the identifier of the terminal device and the tracking identifier and the paging message carrying the tracking identifier, the access network device can determine whether to send the information related to the paging to the network management device, i.e. whether to track the paging message of the terminal device, thereby improving the communication performance of the terminal device.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Technology

[0002] In new radio (NR) communication systems, access network devices page terminal devices after receiving a paging request from core network devices. During the paging process, the access network device may fail to page the terminal device, potentially affecting its communication performance. Therefore, tracking the paging process of terminal devices so that network management devices are aware of the paging status is a problem that needs to be solved. Summary of the Invention

[0003] This application provides a communication method and a communication device that can track the paging process of a terminal device and improve the communication performance of the terminal device.

[0004] Firstly, a communication method is provided, which can be executed by an access network device, or by a component of the access network device (such as a chip or circuit), without limitation. For ease of description, the following explanation will take execution by an access network device as an example.

[0005] The method includes: receiving first information from a core network device, the first information including a correspondence between a terminal device identifier and a tracking identifier; receiving a paging message from the core network device, the paging message being used to page the terminal device and carrying the tracking identifier; and determining, based on the first information and the paging message, whether to send second information to a network management device, the second information including information related to the paging.

[0006] Based on the above scheme, by receiving the correspondence between the terminal device's identifier and the tracking identifier, and by carrying the tracking identifier in the paging message, the access network device can determine whether to send information related to the paging to the network management device, that is, whether to track the paging message of the terminal device, thereby improving the communication performance of the terminal device.

[0007] In some implementations of the first aspect, the first information is carried in any of the following messages: an initial context establishment request message, a switch request message, or a trace start message.

[0008] In some implementations of the first aspect, capability information is sent to the core network device, which indicates whether the access network device supports sending the second information to the network management device.

[0009] Based on the above scheme, by sending this capability information to the core network equipment, the core network equipment can determine whether to track paging messages based on the capability information, thereby improving the flexibility of tracking paging messages.

[0010] In some implementations of the first aspect, the first information is stored in the user context of the terminal device; the second information is determined to be sent to the network management device based on the first information and the paging message, and the second information is determined to be sent to the network management device based on the tracking identifier in the paging message and the user context of the terminal device.

[0011] In some implementations of the first aspect, the core network device is a mobility management entity or an access and mobility management network element.

[0012] Secondly, a communication method is provided, which can be executed by a core network device or by a component of the core network device (such as a chip or circuit). There is no limitation on this. For ease of description, the following explanation will take execution by a core network device as an example.

[0013] The method includes: sending first information to an access network device, the first information including a correspondence between the identifier of the terminal device and a tracking identifier; sending a paging message to the access network device, the paging message being used to page the terminal device, the paging message carrying the tracking identifier, the first information and the paging message being used to determine whether a network management device sends second information, the second information including information related to the paging.

[0014] Based on the above scheme, by sending the correspondence between the terminal device's identifier and the tracking identifier to the access network device, and by carrying the tracking identifier in the paging message, the access network device can determine whether to send information related to the paging to the network management device, that is, whether to track the paging message of the terminal device, thereby improving the communication performance of the terminal device.

[0015] In some implementations of the second aspect, the first information is carried in any of the following messages: initial context establishment request message, switch request message, or trace start message.

[0016] In some implementations of the second aspect, capability information from the access network device is received, which indicates whether the access network device supports sending the second information to the network management device. If the access network device supports sending the second information to the gateway device, the first information is sent to the access network device.

[0017] In some implementations of the second aspect, the core network device is a mobility management entity or an access and mobility management network element.

[0018] Thirdly, a communication device is provided, comprising a transceiver unit and a processing unit. The transceiver unit is configured to receive first information from a core network device, the first information including a correspondence between an identifier of a terminal device and a tracking identifier. The transceiver unit is also configured to receive a paging message from the core network device, the paging message being used to page the terminal device and carrying the tracking identifier. The processing unit is configured to determine, based on the first information and the paging message, whether to send second information to a network management device, the second information including information related to the paging.

[0019] In some implementations of the third aspect, the first information is carried in any of the following messages: initial context establishment request message, switch request message, or trace start message.

[0020] In some implementations of the third aspect, the transceiver unit is also used to: send capability information to the core network device, the capability information indicating whether the access network device supports sending the second information to the network management device.

[0021] In some implementations of the third aspect, the first information is stored in the user context of the terminal device; the processing unit is specifically used to determine, based on the tracking identifier in the paging message and the user context of the terminal device, to send the second information to the network management device.

[0022] In some implementations of the third aspect, the core network device is a mobility management entity or an access and mobility management network element.

[0023] Fourthly, a communication device is provided, the device including a transceiver unit, the transceiver unit being configured to: send first information to an access network device, the first information including a correspondence between an identifier of a terminal device and a tracking identifier; the transceiver unit being further configured to send a paging message to the access network device, the paging message being used to page the terminal device, the paging message carrying the tracking identifier, the first information and the paging message being used to determine whether a network management device sends second information, the second information including information related to the paging.

[0024] In some implementations of the fourth aspect, the first information is carried in any of the following messages: initial context establishment request message, switch request message, or trace start message.

[0025] In some implementations of the fourth aspect, the transceiver unit is further configured to receive capability information from the access network device, the capability information indicating whether the access network device supports sending the second information to the network management device, and the transceiver unit is specifically configured to send the first information to the access network device when the access network device supports sending the second information to the gateway device.

[0026] In some implementations of the fourth aspect, the core network device is a mobility management entity or an access and mobility management network element.

[0027] Fifthly, a communication device is provided, the device including a processor configured to implement any one of the first to second aspects and the methods in any possible implementation of the first to second aspects by executing a computer program (or computer-executable instructions) stored in a memory and / or by logic circuitry.

[0028] Optionally, the device may also include a memory, which may be deployed separately from the processor or centrally.

[0029] Optionally, the device also includes a communication interface, to which the processor is coupled. This communication interface may be a transceiver or an input / output interface.

[0030] In one implementation, the device is an access network device, or a chip configured within an access network device, or a logic module or software capable of implementing all or part of the functions of the access network device. When the device is a chip, the communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be manifested as a processing circuit or logic circuit.

[0031] In another implementation, the device is a core network device, or a chip configured within a core network device, or a logic module or software capable of implementing all or part of the functions of the core network device. When the device is a chip, the communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be manifested as a processing circuit or logic circuit.

[0032] Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0033] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be, but is not limited to, a signal received and input by a receiver, and the signal output by the output circuit can be, but is not limited to, an output to a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, used as both input and output circuits at different times. This application does not limit the specific implementation of the processor and various circuits.

[0034] In a sixth aspect, a chip system is provided, the processor being configured to execute a computer program or instructions in the memory, such that the chip system implements any one of the first to second aspects described above, and the method in any possible implementation of the first to second aspects.

[0035] A seventh aspect provides a communication system comprising: at least one of an access network device and a core network device, wherein the access network device is configured to perform the method of the first aspect and any possible implementation thereof; and the core network device is configured to perform the method of the second aspect and any possible implementation thereof.

[0036] Eighthly, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform any one of the first to second aspects described above, and the method in any possible implementation of the first to second aspects.

[0037] Ninth aspect, a computer program product is provided, the computer program product comprising a computer program (also referred to as code or instructions) that, when the computer program is run, causes a computer to perform any one of the first to second aspects described above, and the method in any possible implementation of the first to second aspects.

[0038] The beneficial effects of the third to ninth aspects mentioned above can be referred to the descriptions of the beneficial effects in the first and second aspects, and will not be repeated here. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of a network architecture applicable to this application.

[0040] Figures 2 to 3 This is a flowchart illustrating the paging process.

[0041] Figure 4 This is a schematic flowchart of a communication method 400 provided in this application.

[0042] Figure 5 This is a schematic flowchart of a communication method 500 provided in this application.

[0043] Figure 6 This is a schematic flowchart of a communication method 600 provided in this application.

[0044] Figure 7 This is a schematic block diagram of a communication device provided in an embodiment of this application.

[0045] Figure 8This is a schematic diagram of another communication device provided in an embodiment of this application.

[0046] Figure 9 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0047] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0048] The technical solution of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) communication systems or future communication systems, vehicle-to-x (V2X) systems, where V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), etc., Long Term Evolution-Vehicle (LTE-V) technology for vehicle-to-everything (V2V) communication, vehicle-to-everything (V2V) communication, machine-type communication (MTC), Internet of Things (IoT), and Long Term Evolution-Vehicle (LTE-V) technology for machine-to-machine communication. Evolution-machine (LTE-M), machine-to-machine (M2M), etc.

[0049] Figure 1 This is a schematic diagram of the network architecture applicable to the methods provided in the embodiments of this application. The network architecture may specifically include the following network elements:

[0050] 1. User Equipment (UE): This can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities, as well as various forms of terminals, mobile stations (MS), terminals, or soft terminals, etc. For example, water meters, electricity meters, sensors, etc.

[0051] For example, the user equipment in the embodiments of this application may refer to an access terminal, user unit, user station, mobile station, mobile station, relay station, remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication equipment, user agent, or user device. The user equipment may also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle equipment, wearable device, user equipment in a 5G network, or user equipment in a future evolved public land mobile network (PLMN) or a future vehicle-to-everything (V2X) network, etc., and this application does not limit it in this regard.

[0052] By way of example and not limitation, in this application embodiment, wearable devices can also be called wearable smart devices. This is a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they can also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functionality without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0053] Furthermore, in this embodiment, the user equipment can also be a user equipment within an Internet of Things (IoT) system. IoT is a crucial component of future information technology development, its main technical characteristic being the connection of objects to networks via communication technology, thereby achieving intelligent networks that enable human-machine and machine-to-machine interconnection. In this embodiment, IoT technology can achieve massive connectivity, deep coverage, and power saving for terminals through technologies such as narrowband (NB). Additionally, in this embodiment, the user equipment can also include sensors such as smart printers, train detectors, and gas station sensors, whose main functions include collecting data (in some user equipment), receiving control information and downlink data from access network devices, and transmitting uplink data to access network devices by sending electromagnetic waves.

[0054] 2. Radio access network (RAN): Used to provide network access functionality for authorized user equipment in a specific area, and can use transmission tunnels of different quality according to the user equipment level, service requirements, etc.

[0055] The RAN manages radio resources, provides access services to user equipment, and forwards control signals and user equipment data between the user equipment and the core network. The RAN can also be understood as a base station in a traditional network.

[0056] For example, the access network device in this application embodiment can be any kind of communication device with wireless transceiver function for communicating with user equipment. This access network device includes, but is not limited to: evolved NodeB (eNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP) in a wireless fidelity (WIFI) system, and can also be a gNB in ​​a 5G, such as NR, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU).

[0057] In some deployments, a gNB may include a centralized unit (CU) and a distribution unit (DU). The gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), media access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered to be sent by the DU, or by the DU+AAU. It is understood that access network equipment can be devices including one or more of the following: CU nodes, DU nodes, and AAU nodes. In addition, the CU can be classified as an access network device in the radio access network (RAN) or as an access network device in the core network (CN), and this application does not limit this.

[0058] 3. Access and Mobility Management Function (AMF) network element: mainly used for mobility management and access management, and can be used to implement other functions of the Mobility Management Entity (MME) besides session management, such as access authorization / authentication.

[0059] 4. Session Management Function (SMF) network element: mainly used for session management, Internet Protocol (IP) address allocation and management of terminal devices, selection and management of user plane functions, policy control and charging function interface endpoints, and downlink data notification, etc.

[0060] 5. Policy control function (PCF) network element: A unified policy framework used to guide network behavior, providing policy rules for other functional network elements (such as AMF, SMF, etc.) or terminal devices in the network.

[0061] 6. User Plane Function (UPF) network element: Used for packet routing and forwarding, as well as quality of service (QoS) processing of user plane data. User data can access the data network (DN) through the UPF. In the embodiments of this application, the UPF can be used to implement the functions of the user plane network element.

[0062] 7. Application function (AF) network element: used for data routing affected by applications, accessing network open function network elements, and interacting with the policy framework for policy control, etc.

[0063] 8. Data Network (DN): A network used to provide data transmission. Examples include carrier networks, the Internet, and third-party service networks.

[0064] It should be understood that the network elements included in the communication system listed above are merely illustrative examples. The network architecture described above may also include other network elements, such as network data analytics function (NWDAF) network elements, network exposure function (NEF) network elements, etc. This application is not limited to these.

[0065] In the above network architecture, the N2 interface is the interface between the RAN and AMF network elements, used for transmitting radio parameters and non-access stratum (NAS) signaling; the N3 interface is the interface between the RAN and UPF network elements, used for transmitting user plane data; the N4 interface is the interface between the SMF and UPF network elements, used for transmitting information such as service policies, tunnel identification information for N3 connections, data buffer indication information, and downlink data notifications; and the N6 interface is the interface between the DN and UPF network elements, used for transmitting user plane data.

[0066] It should be understood that in the above network architecture, network elements can exchange information through service-oriented interfaces. For example, other network elements can exchange information with the SMF through service-oriented interfaces provided by the SMF (such as Nsmf).

[0067] It should also be understood that the network architecture applicable to the embodiments of this application is not limited thereto, and any network architecture capable of realizing the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0068] It should be noted that the names of the various network elements and interfaces in this application are merely examples. This application does not preclude the possibility of using other names for the various network elements in the future, or the merging of functions between various network elements. With the evolution of technology, any device or network element capable of implementing the functions of the aforementioned network elements is within the scope of protection of this application. Secondly, the aforementioned network elements can also be referred to as entities, devices, apparatuses, or modules, etc., and this application does not specifically limit this. Furthermore, in this application, for ease of understanding and explanation, the description of "network element" is omitted in some descriptions. For example, an SMF network element is abbreviated as SMF; in this case, "SMF" should be understood as an SMF network element. The following descriptions of the same or similar situations are omitted.

[0069] To facilitate understanding of the embodiments of this application, some basic concepts involved in this application will be briefly explained.

[0070] 1. Status of terminal equipment

[0071] The terminal device's state includes connection management connected (CM-connected) and connection management idle (CM-idle). Depending on whether radio resource control (RRC) is active or inactive, the CM-connected state can further include two possibilities:

[0072] One scenario is that both connection management and RRC are in a connected state, i.e., CM-connected with RRC_connected. In this case, the N2 connection between the AMF and RAN related to the UE, as well as the RRC connection between the RAN and the UE, are both in a connected state. In this application, this state of the UE is referred to as the connected state.

[0073] Another scenario is that Connection Management (CM) is in a connected state, but RRC is in an inactive state, i.e., CM-CONNECTED with RRC-inactive. In this case, the N2 connection between the AMF and RAN related to the UE is in a connected state, but the RRC connection between the RAN and the UE can be understood as inactive or disconnected. In this application, this state of the UE is simply referred to as the radio resource control inactive (RRC-inactive) state or the inactive state.

[0074] The CM-idle state refers to the state where the N2 connection between the AMF and RAN related to the UE is disconnected, and the RRC connection between the RAN and the UE is also disconnected. In this application, this state of the UE is referred to as the idle state.

[0075] 2. Paging

[0076] In cellular networks, paging enables the network to locate the UE (User Equipment) and send data or control signaling to it. Paging can be initiated by the core network (CN) or the RAN (Radio Area Network). The RAN can be understood as the base station in the cellular network.

[0077] In this context, paging initiated by the CN (Network Core Network) can be used by the core network to locate UEs in an idle state. Idle UEs typically have no connection to either the RAN (Radio Network Area Network) or the core network. When the core network receives data from a UE, it needs to locate the UE in the network and send the data back to it. Paging initiated by the RAN (Radio Network Area Network) can be used by the RAN to locate UEs in an inactive state. Inactive UEs typically still have a connection to the core network, but no connection to the RAN. When the RAN receives data from a UE, it needs to locate the UE and send the data back to it.

[0078] Figure 2 The diagram shown is a schematic flowchart of a paging process initiated by the CN. Figure 2 As shown, the process includes the following steps.

[0079] S201, UE releases RRC connection.

[0080] This means the UE enters the idle state.

[0081] S202, RAN 1 sends list information to AMF.

[0082] When a UE releases its RRC connection and enters an idle state, the RAN can provide the AMF with a list of information associated with that UE, including a list of recommended cells and a list of recommended RAN nodes.

[0083] S203, AMF sends paging messages to RAN 1 and RAN 2.

[0084] When the CN needs to initiate paging, the AMF can prioritize sending the UE's paging message in the recommended cell and recommended RAN node. For example, in Figure 2 In this context, the recommended RAN nodes include RAN 1 and RAN 2.

[0085] For example, when the AMF pages a UE, a certain strategy can be configured, such as first paged the UE in a small area, and if the paged fails, then paged the UE in a larger area, in order to reduce the overhead of sending paged messages.

[0086] S204, RAN 1 and RAN 2 paging UE.

[0087] Specifically, RAN 1 and RAN 2 page the UE based on the paging message from the AMF.

[0088] Figure 3 The diagram shown is a schematic flowchart of a paging process initiated by the RAN. Figure 3 As shown, the process includes the following steps.

[0089] S301, UE suspends RRC connection.

[0090] That is, the UE enters the inactive state.

[0091] S302, RAN 1 sends a paging message to RAN 2.

[0092] For a UE in an inactive state, the UE's last serving gNB will configure a RAN-based notification area (RNA) for the UE. The RNA contains several cells or RAN nodes. When the UE leaves this RNA, the UE will actively enter the connected state, obtain the updated RNA, and then re-enter the inactive state.

[0093] For example, Figure 3 In this context, the UE's last serving base station is RAN 1, and the RAN within the RNA includes RAN 1 and RAN 2. When RAN 1 pages an inactive UE, it can send a paging message to RAN 2 within the RNA via the Xn interface to locate the UE.

[0094] S303, RAN 1 and RAN 2 paging UE.

[0095] Specifically, RAN 1 and RAN 2 page the UE based on the paging message from RAN 1.

[0096] As can be seen from the paging process described above, during the paging of a terminal device, signaling may be exchanged between the UE and the access network equipment, between the access network equipment and the 5G core network (5th generation core, 5GC), and between the access network equipment itself. Tracking this signaling helps the network management equipment understand the paging status of the terminal device. For example, the access network equipment may fail to paging the terminal device; by tracking the signaling, the reason for the paging failure can be determined. In existing solutions, because the paging message sent from the core network to the base station does not carry the user identification information from the access network, the paging message cannot be tracked at the base station, making it impossible to quickly delineate (core network side or access network side) the cause of the paging failure, which may affect the communication performance of the terminal device.

[0097] In view of this, this application proposes a communication method that, by tracking the paging messages of the terminal device on the access network side, can promptly obtain the paging status of the terminal device and improve the communication performance of the terminal device.

[0098] Figure 4 This is a schematic diagram of a communication method 400 provided in this application. Method 400 may include the following steps.

[0099] S410, the core network device sends the first information to the access network device. Accordingly, the access network device receives the first information.

[0100] The first piece of information includes the correspondence between the terminal device's identifier and the trace ID. The terminal device's identifier is used to identify the terminal device and can be used by the access network device to obtain (address) the user context of the terminal device; the trace ID can be used to identify a signaling tracing task.

[0101] In this application, the terminal device can be a terminal device in an idle state or an inactive state. The terminal device can refer to a single terminal device or multiple terminal devices, that is, multiple terminal devices served by the access network device.

[0102] The core network equipment can be an access management function network element in the core network, or a module (such as a chip) used to implement access management functions; there is no limitation. For example, the core network equipment is a mobility management entity (MME) or an AMF.

[0103] Correspondingly, the access network device can be an eNB or a gNB.

[0104] The core network equipment and access network equipment mentioned above are merely examples. This application does not impose specific limitations on the core network equipment and access network equipment. For example, the core network equipment and access network equipment may also be core network equipment used for access management in future communication systems, and access network equipment used for accessing the network.

[0105] For example, a core network device may send the first information to each of at least one access network device it serves. The first information may include a mapping between the identifier of at least one terminal device and at least one tracking identifier. For instance, the first information may include one or more tracking identifiers, each of which may correspond to the identifier of one or more terminal devices. Alternatively, the same or different tracking identifiers may be assigned to multiple terminal devices served by the access network device.

[0106] As an example, the identifier of the terminal device includes at least one of the following: a user-specific identifier, an E-UTRAN cell global identifier (ECGI), or a unique identifier of the terminal device on the eNB-side S1 interface (eNB UE S1 application protocol identifier, eNB UE S1AP ID). This trace identifier can be an evolved universal terrestrial radio access network (E-UTRAN) trace ID.

[0107] As another example, the terminal device identifier includes at least one of the following: a unique identifier for the terminal device on the gNB-side NG interface (gNB UE NG application protocol identifier, gNB UE NGAP ID) and a user-specific identifier (refer to the description in the previous example). This trace identifier can be a next-generation radio access network (NG-RAN) Trace ID.

[0108] That is, for different network standards, the user context and signaling tracing identifiers used to address terminal devices can be different, and there is no restriction on this.

[0109] For example, the core network device sends the first information to the access network device through any of the following procedures: initial context setup procedure, handover procedure, and trace start procedure. For instance, the first information is carried in any of the following messages sent by the core network device in the above procedures: initial UE context setup request message, handover request message, and trace start message.

[0110] It should be understood that this application does not limit the specific message carrying the first information. For example, the first information may also be carried by a message specifically designed to carry the first information.

[0111] For example, when it is determined that a signaling tracing task needs to be created on the access network device, the core network device receives a paging message from the serving gateway or other network elements (such as a session management network element), and the core network device sends the first information to the access network device. That is, the tracing identifier serves as the identifier for the signaling tracing task.

[0112] Optionally, after receiving the first information, the access network device saves the correspondence between the identifier and the tracking identifier of each terminal device. For example, the access network device saves this correspondence in the context of the terminal device.

[0113] In step S420, the core network device sends a paging message to the access network device. The access network device then receives the paging message.

[0114] Among them, the paging message is used to page the terminal equipment, and the paging message carries the tracking identifier corresponding to the identifier of the terminal equipment.

[0115] For example, when downlink data arrives at a terminal device, a voice call occurs, or a system message changes, the core network device sends this paging message to the access network device. If it is determined that a paging message for a terminal device needs to be tracked, the core network device can add a tracking identifier corresponding to that terminal device to the paging message.

[0116] The paging message may also carry other information for paging the terminal device, such as the terminal device's specific identification, for details please refer to existing relevant descriptions.

[0117] S430, the access network device determines to send the second information to the network management device based on the first information and the paging message.

[0118] For example, the access device can determine whether to send the second information to the network management device based on the tracking identifier included in the paging message and the context of the terminal device.

[0119] Specifically, after receiving a paging message from a terminal device, the access network device can query the context of the terminal device based on the terminal device's identifier to determine whether the context includes a correspondence between the terminal device's identifier and the tracking identifier. If such a correspondence exists, the second information is sent to the gateway device; otherwise, it is not necessary to send it.

[0120] The second information can be understood as information related to paging. This second information can be used to monitor the paging process, reflect the paging result, and indicate the cause of the paging result. The access network device sending this second information to the network management device can be understood as the access device providing feedback on the tracking results of the paging signaling. For example, the second information may include an indication that the access network device received the paging message, an indication that the paging message was sent, and the paging result, such as paging failure or success.

[0121] This application does not limit the specific content of the second information, which may also be other information that reflects the paging process or result.

[0122] For example, the access network device can provide feedback on the second information in real time, or provide feedback on the second information according to predetermined conditions, without limiting the specific method by which the access network device sends the second information.

[0123] Optionally, the method further includes:

[0124] S401, the access network device sends capability information to the core network device. Correspondingly, the core network device receives this capability information.

[0125] This capability information can indicate whether the access network device supports paging signaling tracing, or whether the access network device supports sending paging-related information to the network management device, or whether the access network device supports querying the context of the terminal device based on the tracing identifier in the paging message.

[0126] Optionally, if the access network device supports paging signaling tracing, the core network device sends the first information to the access network device.

[0127] This step can be performed before S410 or S420, and there is no limitation on the timing of the access network device sending capability information.

[0128] Based on the above scheme, by sending the correspondence between the terminal device's identifier and the tracking identifier to the access network device, and by including the tracking identifier in the paging message when paging the terminal device, the access network device can report information related to the paging terminal device based on the tracking identifier. This allows the access network device to track the terminal device's paging message, promptly identify the cause of paging failure, and thus improve the communication performance of the terminal device.

[0129] Figure 5 and Figure 6 These are schematic flowcharts illustrating communication methods 500 and 600 provided in this application. Method 500 is illustrated using an MME as the core network device and an eNB as the access network device; method 600 is illustrated using an AMF as the core network device and a gNB as the access network device. Methods 500 and 600 can be considered as specific implementations of method 400.

[0130] The method 500 may include the following steps.

[0131] S501 establishes a connection between the eNB and the MME.

[0132] For example, eNB1 establishes an S1 interface connection with the MME; eNB2 establishes an S1 interface connection with the MME. The access network devices served by the MME include eNB1 and eNB2.

[0133] S502, the eNB sends capability information to the MME.

[0134] For example, eNB1 and eNB2 send information to the MME about whether they support paging signaling tracing capabilities, which can be found in the description in S401.

[0135] For example, after receiving the capability information, if the MME determines that eNB1 and eNB2 support paging signaling tracing, it will record the capability information of eNB1 and eNB2.

[0136] S503, MME creates tracking tasks for eNB1 and eNB2.

[0137] S504, the MME sends the correspondence between the E-UTRAN Trace ID (an example of a trace identifier) ​​and the eNB UES1AP ID (an example of a terminal device identifier) ​​to eNB1 and eNB2 respectively.

[0138] Taking the transmission from MME to eNB1 as an example, this correspondence can include the correspondence between multiple UE eNB UE S1AP IDs and one or more E-UTRAN Trace IDs. That is, there is a one-to-one correspondence between E-UTRAN Trace IDs and eNB UE S1AP IDs, and the E-UTRAN Trace IDs corresponding to different eNB UE S1AP IDs can be the same or different.

[0139] S505, eNB1 and eNB2 save the mapping between E-UTRAN Trace ID and eNB UE S1AP ID to the UE's user context.

[0140] S506, the Serving Gateway (SGW) sends a paging message to the MME.

[0141] For example, the SGW sends this paging message to the MME when downlink data arrives at the UE, a voice call is made, or a system message changes.

[0142] S507, MME sends paging messages to eNB1 and eNB2 respectively.

[0143] For example, the MME sends this paging message to an eNB that supports paging signaling tracing. eNBs that support paging signaling tracing include eNB1 and eNB2.

[0144] The paging message carries the E-UTRAN Trace ID.

[0145] S508, eNB1 traverses the UE's context to determine if there is an E-UTRAN Trace ID in the UE's context.

[0146] If applicable, report the relevant paging information. For example, report the relevant paging information to the network management device.

[0147] The method 600 may include the following steps.

[0148] S601 establishes a connection between gNB and AMF.

[0149] For example, gNB1 establishes an N2 interface connection with AMF; gNB2 establishes an N2 interface connection with AMF. The access network devices served by AMF include gNB1 and gNB2.

[0150] S602, gNB sends capability information to AMF.

[0151] For example, gNB1 and gNB2 send information to the AMF about whether they support paging signaling tracing capabilities, which can be found in the description in S401.

[0152] For example, after receiving the capability information, if the AMF determines that gNB1 and gNB2 support paging signaling tracing, it will record the capability information of gNB1 and gNB2.

[0153] S603, AMF creates tracking tasks for gNB1 and gNB2.

[0154] S604, AMF sends the correspondence between NG-RAN Trace ID (an example of a trace identifier) ​​and gNB UENGAP ID (an example of a terminal device identifier) ​​to gNB1 and gNB2 respectively.

[0155] Taking AMF sending data to gNB1 as an example, this correspondence can include the correspondence between multiple UE gNB UE NGAP IDs and one or more NG-RAN Trace IDs. That is, there is a one-to-one correspondence between NG-RAN Trace IDs and gNB UE NGAP IDs, and the NG-RAN Trace IDs corresponding to different gNB UE NGAP IDs can be the same or different.

[0156] S605, gNB1 and gNB2 save the mapping between NG-RAN Trace ID and gNB UE NGAP ID to the UE's user context.

[0157] S606, SMF sends a paging message to AMF.

[0158] For example, the SMF sends the paging message to the AMF when downlink data arrives at the UE, a voice call is made, or a system message changes.

[0159] S607, AMF sends paging messages to gNB1 and gNB2 respectively.

[0160] For example, the AMF sends this paging message to a gNB that supports paging signaling tracing. gNBs that support paging signaling tracing include gNB1 and gNB2.

[0161] The paging message carries the NG-RAN Trace ID.

[0162] S608, gNB1 traverses the context of the serving UE to determine whether there is an NG-RAN Trace ID in the UE's context.

[0163] If applicable, report the relevant paging information. For example, report the relevant paging information to the network management device.

[0164] 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.

[0165] 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.

[0166] It should also be understood that in some of the above embodiments, the examples are mainly based on devices in existing network architectures (such as core network devices and access network devices). It should be understood that the specific form of the devices is not limited in the embodiments of this application. For example, any devices that can achieve the same function in the future are applicable to the embodiments of this application.

[0167] It is understood that the methods and operations implemented by devices (such as core network devices and access network devices) in the above-described method embodiments can also be implemented by components of the devices (such as chips or circuits).

[0168] The above, combined with Figures 1 to 6 The communication method provided in the embodiments of this application is described in detail below. Figures 7 to 9 The communication device provided in the embodiments of this application is described in detail.

[0169] Figure 7 A schematic diagram of a communication device 700 provided in an embodiment of this application is shown.

[0170] The device 700 includes an interface unit 710, which can be used to implement corresponding communication functions. The interface unit 710 can also be called a communication interface, a communication unit, or a transceiver unit.

[0171] Optionally, the device 700 may further include a processing unit 720, which can be used for data processing.

[0172] Optionally, the device 700 further includes a storage unit, which can be used to store instructions and / or data. The processing unit 720 can read the instructions and / or data in the storage unit so that the device can perform the actions of different devices in the foregoing method embodiments.

[0173] In one possible design, the device 700 can be the core network device in the foregoing embodiments, or it can be a component of the core network device (such as a chip). The device 700 can implement the steps or processes performed by the core network device corresponding to those described in the above method embodiments. Specifically, the interface unit 710 can be used to perform transmit / receive related operations of the core network device in the above method embodiments; the processing unit 720 can be used to perform processing related operations of the core network device in the above method embodiments.

[0174] In another possible design, the device 700 can be the access network device in the foregoing embodiments, or it can be a component of the access network device (such as a chip). The device 700 can implement the steps or processes corresponding to those performed by the access network device in the above method embodiments. Specifically, the interface unit 710 can be used to perform transmit / receive related operations of the access network device in the above method embodiments; the processing unit 720 can be used to perform processing related operations of the access network device in the above method embodiments.

[0175] Figure 8 This is a schematic block diagram of a communication device 800 provided in an embodiment of this application.

[0176] The device 800 includes a processor 810 coupled to a memory 820. Optionally, it also includes a memory 820. The memory 820 is used to store computer programs or instructions and / or data, and the processor 810 is used to execute the computer programs or instructions stored in the memory 820, or to read the data stored in the memory 820, to perform the methods in the above-described method embodiments.

[0177] Optionally, there may be one or more processors 810.

[0178] Optionally, the memory 820 may be one or more.

[0179] Alternatively, the memory 820 can be integrated with the processor 810, or it can be set separately.

[0180] Optionally, such as Figure 8 As shown, the device 800 also includes a communication interface 830, which is used for receiving and / or transmitting signals. For example, the processor 810 is used to control the communication interface 830 to receive and / or transmit signals.

[0181] For example, the communication interface 830 may be a transceiver, circuit, bus, module, or other type of communication interface. The communication interface 830 may also be referred to as an interface.

[0182] As one option, the device 800 is used to implement the operations performed by the core network equipment in the various method embodiments described above.

[0183] For example, processor 810 is used to execute computer programs or instructions stored in memory 820 to implement the relevant operations of the core network device in the various method embodiments described above.

[0184] As an alternative, the device 800 is used to implement the operations performed by the access network device in the various method embodiments described above.

[0185] For example, processor 810 is used to execute computer programs or instructions stored in memory 820 to implement the relevant operations of the access network device in the various method embodiments described above.

[0186] In implementation, each step of the above method can be completed by the integrated logic circuitry in the processor 810 or by software instructions. The method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or 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 820, and the processor 810 reads information from memory 820 and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0187] It should be understood that in the embodiments of this application, the processor may be one or more integrated circuits used to execute relevant programs to perform the method embodiments of this application.

[0188] A processor (e.g., processor 810) may include one or more processors and be implemented as a combination of computing devices. The processor may include one or more of the following: microprocessor, microcontroller, digital signal processor (DSP), digital signal processing device (DSPD), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), programmable logic device (PLD), gating logic, transistor logic, discrete hardware circuitry, processing circuitry, or other suitable hardware, firmware, and / or combinations of hardware and software, for performing the various functions described in this disclosure. The processor may be a general-purpose processor or a special-purpose processor. For example, processor 810 may be a baseband processor or a central processing unit (CPU). A baseband processor may be used to process communication protocols and communication data. A CPU may be used to enable the device to execute software programs and process data within the software programs. Furthermore, a portion of the processor may include non-volatile random access memory. For example, the processor may also store information about the device type.

[0189] The term "program" in this application is used broadly to refer to software. Non-limiting examples of software include: program code, program, subroutine, instructions, instruction sets, code, code segments, software modules, application programs, or software application programs, etc. Programs can run in a processor and / or computer to cause devices to perform the various functions and / or processes described in this application.

[0190] The memory (e.g., memory 820) may store data required by the processor (e.g., processor 810) when executing software. The memory may be implemented using any suitable storage technology. For example, the memory may be any available storage medium that the processor and / or computer can access. Non-limiting examples of storage media include: random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact disc-ROM (CD-ROM), 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), removable media, optical disc storage, magnetic disk storage media, magnetic storage devices, flash memory, registers, state memory, remotely mounted memory, local or remote memory components, or any other medium capable of carrying or storing software, data, or information and accessible by a processor / computer. It should be noted that the memory described in this article is intended to include, but is not limited to, these and any other suitable types of memory.

[0191] Memory (e.g., memory 820) and processor (e.g., processor 810) can be configured separately or integrated together. Optionally, when memory and processor are integrated, the memory can be a cache. Memory can be used to connect to the processor, enabling the processor to read information from memory, store information in memory, and / or write information to memory. Memory can be integrated into the processor. Memory and processor can be disposed in an integrated circuit (e.g., the integrated circuit can be disposed in the UE or other network node).

[0192] Figure 9 This is a schematic block diagram of a chip system 900 provided in an embodiment of this application. The chip system 900 (or may also be referred to as a processing system) includes logic circuitry 910 and an input / output interface 920.

[0193] The logic circuit 910 can be a processing circuit in the chip system 900, used to implement the methods and functions of the various embodiments of this application. Optionally, the logic circuit 910 can be coupled to a memory unit to call instructions in the memory unit, enabling the chip system 900 to implement the methods and functions of the various embodiments of this application. The input / output interface 920 can be an input / output circuit in the chip system 900, outputting the information processed by the chip system 900, or inputting data or signaling information to be processed into the chip system 900 for processing.

[0194] As one approach, the chip system 900 is used to implement the operations performed by the core network equipment in the various method embodiments described above.

[0195] For example, logic circuit 910 is used to implement processing-related operations performed by the core network device in the above method embodiments; input / output interface 920 is used to implement sending and / or receiving-related operations performed by the core network device in the above method embodiments.

[0196] As an alternative, the chip system 900 is used to implement the operations performed by the access network device in the various method embodiments described above.

[0197] For example, logic circuit 910 is used to implement processing-related operations performed by the access network device in the above method embodiments; input / output interface 920 is used to implement sending and / or receiving-related operations performed by the access network device in the above method embodiments.

[0198] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by communication devices (such as core network devices and access network devices) in the above-described method embodiments.

[0199] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods described above as being performed by a communication device (such as a core network device or an access network device).

[0200] This application also provides a communication system, which includes at least one of the core network device and access network device in the above embodiments.

[0201] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0202] In the above embodiments, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0203] In the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the term "example" is intended to present the concept in a specific manner.

[0204] It should be understood that the term "embodiment" used throughout this specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0205] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. All node and message names in this application are merely names set for the convenience of description, and the names in the actual network may be different. It should not be understood that this application limits the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in this application is regarded as the method or equivalent substitution of this application and is within the protection scope of this application.

[0206] It should also be understood that in this application, “when…”, “if” and “if” all refer to the network element making a corresponding processing under certain objective circumstances, and are not time-limited, nor do they require the network element to make a judgment when it is implemented, nor do they mean that there are other limitations.

[0207] It should be noted that in the embodiments of this application, "pre-setting" and "pre-configuration" can be implemented by pre-saving the corresponding code, table or other means that can be used to indicate relevant information in the device (e.g., terminal device). This application does not limit the specific implementation method, such as the preset rules and preset constants in the embodiments of this application.

[0208] In addition, the terms “system” and “network” are often used interchangeably in this article.

[0209] In this document, the terms "at least one of..." or "at least one of..." refer to all or any combination of the listed items. For example, "at least one of A, B, and C" can represent six possibilities: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, and A, B, and C exist simultaneously. "At least one" in this document means one or more. "More than one" means two or more.

[0210] It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0211] Furthermore, the terms "of," "corresponding (relevant)," "corresponding," and "associate" are sometimes used interchangeably. It should be noted that their intended meanings are consistent unless otherwise emphasized. The terms "including," "containing," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0212] 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.

[0213] 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.

[0214] 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.

[0215] 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.

[0216] 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.

[0217] 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, ROM, RAM, magnetic disks, or optical disks.

[0218] 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 access network equipment, including: Receive first information from the core network equipment, the first information including the correspondence between the terminal device's identifier and the tracking identifier; Receive a paging message from the core network device, the paging message being used to page the terminal device, the paging message carrying the tracking identifier; Based on the first information and the paging message, it is determined whether to send second information to the network management device, the second information including information related to the paging.

2. The method according to claim 1, characterized in that, The first information is carried in any of the following messages: The initial context setup request message, the toggle request message, and the startup message are traced.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The access network device sends capability information to the core network device, the capability information indicating whether the access network device supports sending the second information to the network management device.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first information is stored in the user context of the terminal device; The step of determining to send the second information to the network management device based on the first information and the paging message includes: Based on the tracking identifier in the paging message and the user context of the terminal device, the second information is determined to be sent to the network management device.

5. The method according to any one of claims 1 to 4, characterized in that, The core network equipment is a mobility management entity or an access and mobility management network element.

6. A communication method, characterized in that, Applied to core network equipment, including: Send first information to the access network device, the first information including the correspondence between the terminal device's identifier and the tracking identifier; A paging message is sent to the access network device. The paging message is used to page the terminal device. The paging message carries the tracking identifier. The first information and the paging message are used to determine whether the network management device sends second information. The second information includes information related to the paging.

7. The method according to claim 6, characterized in that, The first information is carried in any of the following messages: The initial context setup request message, the toggle request message, and the startup message are traced.

8. The method according to claim 6 or 7, characterized in that, The method further includes: Receive capability information from the access network device, the capability information indicating whether the access network device supports sending the second information to the network management device; Sending the first information to the access network device includes: If the access network device supports sending the second information to the network management device, the first information is sent to the access network device.

9. The method according to any one of claims 6 to 8, characterized in that, The core network equipment is a mobility management entity or an access and mobility management network element.

10. A communication device, characterized in that, The apparatus includes a unit or module for performing the method as described in any one of claims 1 to 9.

11. A communication device, characterized in that, include: A processor, the processor being configured to cause the apparatus to perform the method as described in any one of claims 1 to 9 by executing a computer program stored in a memory and / or by means of logic circuitry.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 9.

13. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1 to 9.

Images