A paging method and device

Abstract

This application provides a paging method and apparatus to reduce the resource overhead of the core network and the paging overhead of access network elements. The method includes: a Network Capability Open Function (NCFO) element receiving a first paging request from an Application Function (AFC) element, the first paging request carrying an identifier of a tag and an identifier of at least one access network element; the NCFO element determining a target access network element based on the identifier of the at least one access network element; and the NCFO element sending a second paging request to the target access network element, the second paging request carrying the identifier of a tag, so that the target access network element paging the tag based on the identifier of the tag carried in the second paging request.

Description

Technical Field

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

[0002] When considering tags as a new type of terminal for access to the core network, since most tags are passive, they cannot maintain a connection with the core network for a long time. If the network uses the paging method for conventional terminals to paging tags, the core network needs to store a massive amount of tag context for a long time, which will result in huge core network resource overhead. If the core network does not store the tag context, all access network elements in the global scope need to paging tags, resulting in huge paging overhead for access network elements.

[0003] Therefore, how to reduce the resource overhead of the core network and the paging overhead of the access network elements is an urgent technical problem that needs to be solved. Summary of the Invention

[0004] This application provides a paging method and apparatus to reduce the resource overhead of the core network and the paging overhead of access network elements.

[0005] Firstly, a paging method is provided, which can be applied to an access network element or a chip in an access network element. Taking the application of the method to an access network element as an example, the method includes: a network capability open function element receiving a first paging request from an application function element, the first paging request carrying an identifier of a tag and an identifier of at least one access network element; the network capability open function element determining a target access network element based on the identifier of at least one access network element; and the network capability open function element sending a second paging request to the target access network element, the second paging request carrying an identifier of a tag, so that the target access network element paging the tag based on the identifier of the tag carried in the second paging request.

[0006] The above scheme allows tags to access the core network in a connectionless manner (i.e., the core network does not need to maintain the tag's context for a long time), which can improve the resource utilization of the core network. When application function network elements page tags, they can send the paging request to the target access network element (i.e., the access network element that may currently provide services to the tag) through the control plane network element, so that the target access network element can page the tag. This eliminates the need for all access network elements in the global scope to page the tag, thus saving the overall access network element overhead.

[0007] In one possible design, the identifier of at least one access network element is provided by the core network element to the application function network element.

[0008] In this way, the application function network element can obtain the identifier of at least one access network element and then initiate paging of the tag.

[0009] In one possible design, the first paging request also carries an inventory command, which is used to instruct read and / or write operations to be performed on the tag.

[0010] This reduces the complexity of the interaction process between tags and core network elements, and reduces the waiting time for tags.

[0011] In one possible design, at least one access network element includes the access network element that most recently provided services to the tag; the network capability open function element determines the target access network element based on the identifier of at least one access network element, including: the network capability open function element determines a first target access network element based on the access network element that most recently provided services to the tag; the network capability open function element sends a second paging request to the target access network element, including: the network capability open function element sends a second paging request to the first target access network element.

[0012] In this way, network capability open function network elements can improve the paging hit rate by paging tags based on the access network element that most recently provided services for the tag.

[0013] In one possible design, at least one access network element includes multiple access network elements that have historically provided services for the tag; the network capability open function element determines a target access network element based on the identifier of at least one access network element, including: the network capability open function element determines a second target access network element based on the multiple access network elements that have historically provided services for the tag; wherein, the second target access network element is a predicted access network element that is currently providing services for the tag; the network capability open function element sends a second paging request to the target access network element, including: the network capability open function element sends a second paging request to the second target access network element.

[0014] In this way, network capability open function network elements can improve the paging hit rate by paging tags based on the predicted access network elements currently providing services for tags.

[0015] In one possible design, the Network Capability Open Function (NCEF) determines a second target access network element based on multiple access network elements that have historically provided services for the tag. This includes: the NCEF sending identifiers of multiple access network elements that have historically provided services for the tag to the Network Data Analysis Function (RDF); the RDF predicting the second target access network element currently providing services for the tag based on the identifiers of the multiple access network elements that have historically provided services for the tag; and the NCEF receiving the identifier of the second target access network element from the RDF and determining the second target access network element based on the identifier.

[0016] In this way, the prediction of the second target access network element can be performed by the network data analysis function network element, which can reduce the overhead of the network capability opening function network element and improve the computational efficiency.

[0017] In one possible design, at least one access network element further includes multiple access network elements that have historically provided services for the tag; the method further includes: a network capability open function element determining that a first target access network element has failed to paging the tag; the network capability open function element determining a second target access network element based on multiple access network elements that have historically provided services for the tag; wherein the second target access network element is a predicted access network element that is currently providing services for the tag; the network capability open function element sending a third paging request to the second target access network element, the third paging request carrying the tag's identifier, so that the second target access network element paging the tag based on the tag's identifier carried in the third paging request.

[0018] In this way, by first paging the tag through the access network element that most recently provided services for the tag, and then paging the tag through the predicted access network element after the failure, the paging hit rate can be further improved.

[0019] In one possible design, before the network capability open function element receives the first paging request from the application function element, it also includes: the application function element failing to paging the tag through the user plane element.

[0020] In this way, the application function network element first pages the tag through the user plane network element. If the application function network element fails to page the tag through the user plane network element, it then pages the tag through the control plane network element, which can further improve the paging hit rate and reduce the paging time.

[0021] In one possible design, the Network Capability Open Function (NCFO) sends a second paging request to the target access network element, including: the NCFO sends a fourth paging request to the target access and mobility management (MAM) function element corresponding to the target access network element, wherein the fourth paging request carries the identifier of the tag and the identifier of the target access network element, so that the target mobility management (MAM) function element sends the second paging request to the target access network element based on the identifier of the tag and the identifier of the target access network element carried in the fourth paging request.

[0022] Secondly, a paging method is provided, which can be applied to an application function network element or a chip in the application function network element. Taking the application function network element as an example, the method includes: the application function network element obtaining the identifier of the tag and the identifier of at least one access network element that provides services to the tag; the application function network element storing the identifier of the tag and the identifier of at least one access network element; the application function network element sending a first paging request to the network capability opening function, wherein the first paging request carries the identifier of the tag and the identifier of at least one access network element.

[0023] In one possible design, the identifier of at least one access network element is provided by the core network element to the application function network element.

[0024] In one possible design, the first paging request also carries an inventory command, which is used to instruct read and / or write operations to be performed on the tag.

[0025] In one possible design, at least one access network element includes the access network element that most recently provided services for the tag.

[0026] In one possible design, at least one access network element includes multiple access network elements that have historically provided services for tags.

[0027] In one possible design, before sending the first paging request to the network capability exposure function, the application function network element sends a fifth paging request to the user plane network element. The fifth paging request carries the tag's identifier so that the user plane network element can page the tag based on the tag's identifier; and confirms that the user plane network element's paging of the tag has failed.

[0028] Thirdly, a paging method is provided, which can be applied to an access and mobility management function (AMU) network element or a chip within an AMU. Taking the application of the method to an AMU network element as an example, the method includes: the AMU acquiring the identifier of a tag and the identifier of an access network element providing services to the tag; the AMU sending the identifier of the access network element and the identifier of the tag to an application function network element, wherein the identifier of the access network element and the identifier of the tag are used by the application function network element to paging the tag.

[0029] In one possible design, the Access and Mobility Management Function (AMM) network element receives a fourth paging request from the Network Capability Open Function (LCF) network element, the fourth paging request carrying the tag identifier and the identifier of the access network element; the AMM network element sends a second paging request to the access network element based on the tag identifier carried in the fourth paging request and the identifier of the access network element, the second paging request carrying the tag identifier, so that the access network element can paging the tag based on the tag identifier carried in the second paging request.

[0030] Fourthly, a communication device is provided, comprising a module for performing the method described in the first aspect or any possible design of the first aspect.

[0031] For example, the communication device includes: a transceiver module for receiving a first paging request from an application function network element, the first paging request carrying an identifier of a tag and an identifier of at least one access network element; a processing module for determining a target access network element based on the identifier of the at least one access network element; the transceiver module is further configured to send a second paging request to the target access network element, the second paging request carrying the identifier of a tag, so that the target access network element paging the tag based on the identifier of the tag carried in the second paging request.

[0032] In one possible design, the identifier of at least one access network element is provided by the core network element to the application function network element.

[0033] In one possible design, the first paging request also carries an inventory command, which is used to instruct read and / or write operations to be performed on the tag.

[0034] In one possible design, at least one access network element includes the access network element that most recently provided services to the tag; the processing module is configured to: determine a first target access network element based on the access network element that most recently provided services to the tag; and the transceiver module is configured to: send a second paging request to the first target access network element.

[0035] In one possible design, at least one access network element includes multiple access network elements that have historically provided services to the tag; the processing module is configured to: determine a second target access network element based on the multiple access network elements that have historically provided services to the tag; wherein the second target access network element is the predicted access network element that is currently providing services to the tag; the transceiver module is configured to: send a second paging request to the second target access network element.

[0036] In one possible design, when the processing module determines the second target access network element based on multiple access network elements that have historically provided services to the tag, it specifically performs the following: sends the identifiers of multiple access network elements that have historically provided services to the tag to the network data analysis function element, which then predicts the second target access network element currently providing services to the tag based on the identifiers of these elements; and determines the second target access network element based on the identifier of the second target access network element returned by the network data analysis function element.

[0037] In one possible design, at least one access network element further includes multiple access network elements that have historically provided services for the tag; the processing module is further configured to: determine that the first target access network element has failed to paging the tag; determine a second target access network element based on the multiple access network elements that have historically provided services for the tag; wherein the second target access network element is the predicted access network element that is currently providing services for the tag; the transceiver module is further configured to: send a third paging request to the second target access network element, the third paging request carrying the tag's identifier, so that the second target access network element paging the tag according to the tag's identifier carried in the third paging request.

[0038] In one possible design, the application function network element fails to page the tag via the user plane network element before the transceiver module receives the first paging request from the application function network element.

[0039] In one possible design, when the Network Capability Open Function (NCFO) element sends a second paging request to the target access network element, it specifically sends a fourth paging request to the target access and mobility management (MAM) function element corresponding to the target access network element. The fourth paging request carries the identifier of the tag and the identifier of the target access network element, so that the target mobility management (MAM) function element sends a second paging request to the target access network element based on the identifier of the tag carried in the fourth paging request and the identifier of the target access network element.

[0040] Fifthly, a communication device is provided, comprising a module for performing the method described in the second aspect or any possible design of the second aspect.

[0041] For example, the communication device includes: a processing unit for acquiring the identifier of a tag and the identifier of at least one access network element providing services to the tag; storing the identifier of the tag and the identifier of at least one access network element; and a transceiver unit for sending a first paging request to a network capability open function, wherein the first paging request carries the identifier of the tag and the identifier of at least one access network element.

[0042] In one possible design, the identifier of at least one access network element is provided to the communication device by the core network element.

[0043] In one possible design, the first paging request also carries an inventory command, which is used to instruct read and / or write operations to be performed on the tag.

[0044] In one possible design, at least one access network element includes the access network element that most recently provided services for the tag.

[0045] In one possible design, at least one access network element includes multiple access network elements that have historically provided services for tags.

[0046] In one possible design, the transceiver module is further configured to: send a fifth paging request to the user plane network element before sending the first paging request to the network capability exposure function, the fifth paging request carrying the tag identifier, so that the user plane network element can paging the tag according to the tag identifier; the processing module is further configured to: confirm that the user plane network element has failed to paging the tag.

[0047] A sixth aspect provides a communication device comprising a module for performing the method described in the third aspect or any possible design of the third aspect.

[0048] For example, the communication device includes: a processing unit for acquiring the identifier of the tag and the identifier of the access network element providing services to the tag; and a transceiver unit for sending the identifier of the access network element and the identifier of the tag to the application function network element, wherein the identifier of the access network element and the identifier of the tag are used by the application function network element to paging the tag.

[0049] In one possible design, the transceiver unit is further configured to: receive a fourth paging request from a network capability open function network element, the fourth paging request carrying the tag identifier and the identifier of the access network element; and send a second paging request to the access network element based on the tag identifier carried in the fourth paging request and the identifier of the access network element, the second paging request carrying the tag identifier, so that the access network element paging the tag based on the tag identifier carried in the second paging request.

[0050] A seventh aspect provides a communication device, including a processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device, the processor being configured to implement the method described in the first aspect or any possible design of the first aspect, or any possible design of the second aspect, or any possible design of the third aspect, through logic circuits or executing code instructions.

[0051] Eighthly, a computer-readable storage medium is provided, wherein a computer program or instructions are stored therein, which, when executed by a communication device, implement the method described in the first aspect or any possible design of the first aspect, or in the second aspect or any possible design of the second aspect, or in the third aspect or any possible design of the third aspect.

[0052] Ninth aspect, a computer program product is provided, including instructions that, when executed on a computer, cause the method described in the first aspect or any possible design of the first aspect, or in the second aspect or any possible design of the second aspect, or in the third aspect or any possible design of the third aspect to be performed.

[0053] Tenthly, a communication system is provided, comprising:

[0054] The communication device as described in the fourth aspect or any possible design of the fourth aspect;

[0055] The communication device as described in the fifth aspect or any possible design of the fifth aspect;

[0056] The communication device as described in the sixth aspect or any possible design of the sixth aspect. Attached Figure Description

[0057] Figure 1 This is a schematic diagram of the architecture of a traditional RFID system;

[0058] Figure 2 This is a schematic diagram of the architecture of a 5G communication system;

[0059] Figure 3 A schematic diagram of the service interface for a 5G communication system;

[0060] Figure 4 A schematic diagram of a communication system provided in an embodiment of this application;

[0061] Figures 5A to 5C This is a diagram illustrating the deployment method of the reader / writer;

[0062] Figure 6 A flowchart of a paging method provided in an embodiment of this application;

[0063] Figure 7 A schematic diagram illustrating how access and mobility management function network elements provide access network element identifiers to application function network elements;

[0064] Figure 8 A schematic diagram illustrating the paging process of a target access network element for a tag;

[0065] Figure 9 A schematic diagram of the structure of a possible communication device provided for an embodiment of this application;

[0066] Figure 10 A schematic diagram of another possible communication device provided for an embodiment of this application. Detailed Implementation

[0067] The following section introduces traditional Radio Frequency Identification (RFID) systems.

[0068] See Figure 1This diagram illustrates the architecture of a traditional RFID system, including tags, readers, middleware, and backend application systems. Tags are categorized into passive tags and active tags. Passive tags do not have internal batteries and rely on the reader for power. When a tag is outside the reader's range, it is in a passive state. When the tag is within the reader's range, the reader emits an excitation signal to generate a magnetic field around it. The tag can then receive an induced current in this magnetic field and send a response signal (e.g., transmitting product information stored in its chip). Active tags, on the other hand, can be powered entirely by an internal battery, allowing them to actively transmit product information stored in their chip without requiring an excitation signal from the reader. After receiving the information from the tag, the reader forwards it to the backend application system for processing via middleware.

[0069] The Electronic Product Code (EPC) standard defines the interface protocols between various components in the RFID architecture. The tag and reader use the Ultra-High Frequency Radio Identification Protocol (EPC global Class 1 Generation 2) (Gen2 protocol); the reader and middleware use the Low-Level Reader Protocol (LLRP); and the middleware and backend application system use the Application Level Events (ALE) protocol. The EPC standard uses EPC codes to uniquely identify tags. For security reasons, tags and readers can use Secret Identifiers (SIDs) for interaction.

[0070] The following is an introduction to 5G (5th Generation Mobile Communication Technology).

[0071] See Figure 2 This is a schematic diagram of the architecture of the 3rd Generation Partnership Project (3GPP) system for 5G, which includes terminal equipment, (Radio) Access Network ((R)AN) network elements, and core network elements.

[0072] Access network elements can be base stations, evolved NodeBs (eNodeBs), Transmission Reception Points (TRPs), Next Generation NodeBs (gNBs) in 5G mobile communication systems, Next Generation NodeBs in 6th Generation (6G) mobile communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. They can also be modules or units that perform some of the functions of a base station; for example, they can be Central Units (CUs) or Distributed Units (DUs). Here, the CU performs the functions of the base station's Radio Resource Control Protocol (RRC) and Packet Data Convergence Protocol (PDCP), and can also perform the functions of the Service Data Adaptation Protocol (SDAP). The DU performs the functions of the base station's Radio Link Control (RANC) and Medium Access Control (MAC) layers, and can also perform some or all of the physical layer functions. For specific descriptions of the above protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). Access network elements can be macro base stations (such as...) Figure 1 110a in the text), can also be a micro base station or an indoor station (such as... Figure 1 110b) in the above can also be a relay node or a donor node, etc. The embodiments of this application do not limit the specific technology or equipment form used in the access network elements. For ease of description, the access network elements mentioned below will all be based on base stations.

[0073] Terminal devices can also be called terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the 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. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminals.

[0074] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on aircraft, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of base stations and terminals.

[0075] Core network elements may include one or more network elements (or one or more network functional entities). Examples include, but are not limited to, the following network elements:

[0076] User Plane Function (UPF) network elements are primarily responsible for forwarding and receiving user data in terminal devices. They can receive user data from the data network and transmit it to the terminal device via access network elements; UPF network elements can also receive user data from terminal devices via access network elements and forward it to the data network. The transmission resources and scheduling functions providing services to terminal devices within the UPF network element are managed and controlled by the SMF network element.

[0077] The Session Management Function (SMF) network element is primarily responsible for user plane network element selection, user plane network element redirection, Internet Protocol (IP) address allocation, bearer establishment, modification and release, and Quality of Service (QoS) control.

[0078] Access and Mobility Management Function (AMF) network elements are primarily responsible for signaling processing, such as access control, mobility management, attach and detach functions, and gateway selection. When an AMF network element provides services to a session in a terminal device, it provides control plane storage resources for that session, as well as storage for the session identifier and the SMF network element identifier associated with the session identifier.

[0079] Authentication Server Function (AUSF) network element: mainly provides authentication functions, supporting authentication for 3GPP access and non-3GPP access.

[0080] Network Slice Selection Function (NSSF) element: mainly responsible for selecting network slices for UE.

[0081] Network Exposure Function (NEF) network element: It mainly supports secure interaction between 3GPP network and third-party applications. NEF can securely expose network capabilities and events to third parties to enhance or improve the quality of application services. 3GPP network can also securely obtain relevant data from third parties to enhance network intelligent decision-making. At the same time, this network element supports recovering structured data from a unified database or storing structured data in a unified database.

[0082] Network Repository Function (NRF) element: mainly responsible for providing storage and selection functions for network function entity information for other network elements.

[0083] Policy Control Function (PCF): Primarily supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is also responsible for obtaining user subscription information related to policies.

[0084] Unified Data Management (UDM) network element: mainly responsible for managing user subscription context.

[0085] Application Function (AF) network elements: These mainly support interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0086] Among them, UE, (R)AN, and UPF are generally referred to as user layer network function entities. User data traffic can be transmitted through the Protocol Data Unit (PDU) session established between the UE and the Data Network (DN), and the transmission will pass through the (R)AN and UPF network elements; while the other parts are referred to as control layer network function entities, which are mainly responsible for authentication and authorization, registration management, session management, mobility management, and policy control, thereby realizing reliable and stable transmission of user layer traffic.

[0087] It should be understood that Figure 2 The document illustrates the interaction relationships between various network functional entities and their corresponding interfaces. For example, the UE and AMF can interact through the N1 interface. The interactions between other network functional entities are similar and will not be elaborated further. Some interfaces can be implemented using service-oriented interfaces, such as... Figure 3 As shown, NSSF provides the Nnssf interface to the outside world, NEF provides the Nnef interface to the outside world, and other network elements are similar and will not be described in detail.

[0088] This application considers tags as a new type of terminal, accessing the cellular network via the air interface (e.g., accessing...). Figure 3 (As shown in the network diagram), the access network element reads / writes the tag under the control of the core network element.

[0089] For example, see Figure 4 This is a schematic diagram of a communication system provided in an embodiment of this application. It includes tags, access network elements, and core network elements. Multiple readers corresponding to the tags are deployed on the access network elements. Middleware and backend application systems are connected to the core network elements and communicate with the readers through the core network elements. For details regarding access network elements and core network elements, please refer to the preceding text. Figure 2 The relevant information will not be repeated here.

[0090] It should be understood that Figure 4 Taking the deployment of backend application systems outside the core network as an example, such as when the backend application system is provided by a third party (i.e., a third party other than the operator and the user), the AF (Active Application Server) in the core network can serve as the interface for the backend application system to access the core network. However, in practical applications, backend application systems can also be deployed within the core network. For example, if the backend application system is provided by the network operator, the network operator can directly deploy the backend application system to the AF in the core network. It should be understood that... Figure 4 This is just one example; other variations are possible in actual applications.

[0091] As an alternative implementation, the reader can be deployed independently within a micro base station, specifically as follows: Figure 5A As shown;

[0092] As another alternative implementation, the reader can be deployed in a generic access node (NodeX node), specifically as follows: Figure 5B As shown, in this scenario, NodeX nodes can interact with tags in a D2D manner.

[0093] As an alternative implementation, the reader's functionality can also be separated; for example, the reader's transmit and receive functions can be deployed separately on different physical devices. Figure 5C As shown, the NodeX node deploys a transmitting module to perform the reader's transmitting function, while the macro base station deploys a receiving module to perform the reader's receiving function. Because the NodeX node is closer to the tag than the macro base station, the NodeX node can send an excitation signal to enable the tag to obtain more energy to send a response signal, which can then reach the macro base station. Therefore, the macro base station can directly receive the response signal sent by the tag.

[0094] exist Figure 4 In the communication system shown, the tag and middleware can exchange signaling (such as authentication, read, or write commands) or data (such as user data) through the core network, and then the middleware interacts with the backend application system. Alternatively, the tag and the backend application system can directly exchange signaling (such as authentication, read, or write commands) or data (such as user data) through the core network.

[0095] In cellular networks, the conventional way for a UE to access the core network is connection-oriented. That is, the core network stores the UE's context (such as UE identifier, recently accessed area information, etc.). When the core network needs to page a UE, it can send a paging request for the target UE to the radio access device (RAN) in the nearest access area based on the stored context. Then, the RAN will further page the target UE.

[0096] As described above, tags are divided into active tags and passive tags. Active tags, because they have their own power supply, can be considered a type of UE similar to NB-IoT, and their paging method can follow the paging procedure of a conventional UE (or the paging procedure optimized for NB-IoT). For passive tags, this application embodiment considers the following two methods to connect passive tags to the core network:

[0097] Method 1: The core network view tag is a special UE, still connection-oriented, that is, the core network saves the tag context, and the paging method is similar to the paging method of a regular UE.

[0098] This method is limited by the unique nature of passive tags obtaining energy, relying on excitation signals to obtain energy. Therefore, it is difficult to maintain a connection with the core network for a long time, and the massive tag context stored by the core network for a long time will occupy the core network's resources.

[0099] Method 2: The core network video tag is a special UE, which is connectionless. It only maintains the tag's temporary context for a short period of time when the tag is accessed, and provides the tag with a temporary control plane or user plane transmission channel. The tag's temporary context is released when the tag's data transmission is completed or the timer expires.

[0100] This method is suitable for scenarios where a large number of tags access the core network in a very short time. However, since the core network does not store the context of the tags, it is not possible to use the conventional UE paging mechanism to paging the tags. When it is necessary to inventory specific tags, the core network needs to initiate paging for all access network elements in the global scope (i.e., all access network elements send excitation signals, and the tags initiate responses after acquiring energy), which increases the paging overhead of the access network elements.

[0101] In view of this, embodiments of this application also provide a paging scheme that can improve the resource utilization of the core network while reducing the paging overhead of global access network elements for tags. The scheme is described in detail below.

[0102] See Figure 6 This is a flowchart of a paging method provided in an embodiment of this application. The following describes the application of this method... Figure 4 Taking the communication system shown as an example, the method includes:

[0103] S101, the application function network element sends a first paging request to the network capability open function network element, the first paging request carrying the identifier of the tag and the identifier of at least one access network element; correspondingly, the network capability open function network element receives the paging request.

[0104] The tag identifier carried in the first paging request is used to indicate the tag being paging.

[0105] As an optional implementation, before sending the first paging request to the network capability exposure function (CAVF) network element, the application function network element needs to first acquire and save the tag identifier and the identifier of at least one access network element. Only then can it generate and send the first paging request.

[0106] As an optional implementation, the identifier of at least one access network element can be provided to the application function network element by the core network element. The core network element can be any core network element capable of obtaining the identifier of at least one access network element, including but not limited to access and mobility management function network elements, session management function network elements, and user plane function network elements.

[0107] As an optional implementation, at least one access network element includes an identifier of at least one access network element that has provided services to the tag. The core network element provides the identifier of at least one access network element to the application function network element during the process of at least one access network element providing services to the tag.

[0108] Taking the first access and mobility management function (AMAC) network element as an example, the AMAC network element can obtain the tag's identifier and the identifier of the first access network element providing services to the tag, and send the identifier of the first access network element and the tag's identifier to the application function network element. Accordingly, the aforementioned at least one access network element includes the first access network element.

[0109] For example, see Figure 7 A schematic diagram illustrating how access and mobility management function network elements provide access network element identifiers to application function network elements, including:

[0110] S201. The tag acquires the excitation signal of the access network element and completes the interaction with the underlying layer (such as the access layer, AS) of the radio access network element.

[0111] S202, a security process is completed between the tag and the core network elements, which includes the core network's authentication and authorization of the tag.

[0112] In practical implementation, the security process between the tag and the core network element is completed through the radio access network element. This application does not limit the communication protocol between the tag and the core network. For example, the access network element can establish a Non-Access Stratum (NAS) layer connection for the tag to enable interaction between the tag and the core network. Specifically, the access network element can add a Unified Access Gateway Function (Uni-AGF) module to establish a control plane for the tag, supporting interaction between the tag and the core network, enabling the core network to be aware of the tag (because the tag does not have a NAS layer, it cannot directly interact with the 5GC at the NAS layer like a regular UE); or, for example, the access network element can directly interact with the core network through N2 messages (interface messages between the access network element and the access and mobility management function elements).

[0113] In one possible implementation, the core network's authentication of the tag is a two-way authentication, which includes both core network authentication of the tag and tag authentication of the core network.

[0114] In one possible implementation, two-way authentication between the tag and the core network can be achieved based on the cellular network's authentication framework. For example, the core network can perform two-way tag authentication through authentication network elements, such as Authentication Server Function (AUSF) network elements, Unified Data Management (UDM) network elements, etc., which are not limited in this application. Alternatively, two-way tag authentication can be achieved through network slicing and independent non-public network authentication and authorization functions (NSSAAF). In another possible implementation, the tag may not have an operator attribute. Here, a method similar to the private network external authentication in 3GPP Release 17 is adopted, where authentication and authorization can be performed by a third-party network element.

[0115] In one possible implementation, the tag can interact with core network elements to complete the exchange of security parameters such as authorization and authentication based on hash, symmetric key, and asymmetric key.

[0116] S203A, the core network establishes a control plane (CP) forwarding channel;

[0117] Specifically, the core network stores the tag's general subscription / configuration information. Based on the tag's uploaded identifier (such as a protected security identifier (SID), a temporary SID, or other identifiers that can uniquely identify the tag), it establishes the tag's context and builds a control plane forwarding channel for the tag. The specific forwarding path can be: tag → access network element → access and mobility management function element → network capability opening function element → application function element (it should be understood that this is only an example, and the core network elements passed through are not limited to access and mobility management function elements and network capability opening function elements; in reality, they can also be other core network elements).

[0118] S203B, the core network establishes a user plane (UP) forwarding channel;

[0119] Compared to S203A, after the tag completes the security process, the core network establishes a user plane forwarding channel for the tag. For example, the specific forwarding path can be: tag → access network element → user plane function element → application function element.

[0120] It should be understood that in specific implementation, the core network may establish only a control plane forwarding channel for the label, or only a user plane forwarding channel for the label, or both control plane forwarding channels and user plane forwarding channels for the label simultaneously; this application does not impose any restrictions. In other words, in the above S203A and S203B, only one step may be executed, or both steps may be executed.

[0121] Following S203A and / or S203B, the connection between the tag and the core network is established. Based on this connection, core network elements and access network elements can provide data transmission services to the tag. For example, the core network and application function network elements / application servers can exchange data through control plane forwarding channels or user plane forwarding channels. During the process of the access network elements providing services to the tag, the core network maintains the connection between the tag and the core network; that is, the core network maintains the tag's temporary context. When the access network elements finish providing services to the tag (e.g., data transmission between the core network and the tag is completed or the connection between the tag and the core network times out), the core network disconnects the connection between the tag and the core network; that is, the core network releases the tag's temporary context.

[0122] S204. During the process of an access network element providing services to a tag, the access and mobility management function network element obtains the identifier of the access network element providing services to the tag.

[0123] S205. The access and mobility management function network element reports the identifier of the access network element to the application function network element.

[0124] In one possible implementation, the identifier of an access network element can be a globally unique identifier, meaning that the identifier of an access network element uniquely identifies that access network element.

[0125] In one possible implementation, the access and mobility management function (AMU) network element, network capability open function (CMO) network element, or other core network element can anonymize the access network element identifier obtained by the AMU network element before sending it to the application function network element. For example, if the access network element identifier is an operator-defined identifier, it can be anonymized to avoid directly providing internal operator identifier information to third parties, thereby reducing security risks. Anonymization can be achieved by first pseudonyming, encrypting, suppressing, or masking the identifier to obtain an indirect identifier; then, the indirect identifier can be generalized or randomized to obtain an anonymized identifier. It should be understood that the above are merely examples, and this application does not limit the specific steps of the anonymization process.

[0126] In one possible implementation, the core network element provides the identifier of the access network element to the application function network element based on the addressing information of the application function network element. The addressing information of the application function network element can be obtained from general subscription information or configuration information, or from the routing field in the identifier, and can further be obtained through the Domain Name System (DNS) to obtain the precise address of the application function network element (such as the IP address of the application function network element).

[0127] According to S201 to S205, it can be seen that the access and mobility management function network element can provide the access network element identifier to the application function network element.

[0128] It should be understood that S201 to S205 above can occur when the tag first accesses the core network (i.e., establishes a connection with the core network for the first time), or when the tag disconnects from the core network and reconnects to the core network. This application does not impose any restrictions.

[0129] It should be noted that S201 to S205 above exemplify how a core network element provides the access network element identifier for the tag to the application function network element during a single connection process. As mentioned earlier, the tag can establish multiple connections with the core network. Therefore, during each connection process, the core network element can provide the application function network element with the identifier of the access network element providing access services to the tag. Furthermore, after the tag reconnects to the core network, the access network element and access and mobility management function network element that again provides services to the tag can be the same as or different from the access network element and access and mobility management function network element that previously provided services to the tag; this application does not impose any restrictions. The application function network element can obtain the identifiers of multiple different access network elements that successively provided services to the tag.

[0130] S102. The network capability opening function network element determines the target access network element based on the identifier of at least one access network element.

[0131] Among them, the target access network element is the access network element that can currently provide services for the tag, and the network capability opening function element can try to page the tag through the target access network element.

[0132] In one possible implementation, at least one access network element includes the access network element that most recently (i.e., the one that previously provided services to the tag. Correspondingly, the Network Capability Open Function (NCFO) element can determine the target access network element based on the access network element that most recently provided services to the tag; that is, the target access network element is the access network element that most recently provided services to the tag. For ease of distinction, the target access network element determined based on the access network element that most recently provided services to the tag is referred to here as the first target access network element.

[0133] In one possible implementation, at least one access network element includes multiple access network elements that have historically provided services for the tag. Correspondingly, the Network Capability Open Function (NCFO) element can determine a target access network element based on these multiple historically serving access network elements. The target access network element is the predicted current access network element providing services for the tag. For ease of distinction, the target access network element determined based on these multiple historically serving access network elements is referred to here as the second target access network element.

[0134] Optionally, multiple access network elements that have historically provided services for the tag may or may not include the access network element that most recently provided services for the tag.

[0135] Optionally, the identifiers of multiple access network elements that have historically provided services to the tag can be in the form of a list, for example, carried in the first paging request. The list contains the identifiers of multiple access network elements that have historically provided services to the tag. Furthermore, the list may also include information such as the time information of each access network element providing services to the tag and the location information of the tag.

[0136] In one alternative approach, the prediction of the second target access network element can be performed by the Network Capability Open Function (NCF) element, that is, the NCF element predicts the second target access network element currently providing services to the tag based on the identifiers of multiple access network elements that have historically provided services to the tag.

[0137] In another alternative approach, the prediction of the second target access network element can also be performed by other network elements besides the Network Capability Open Function (NCEF) element. For example, the NCEF element can send multiple identifiers of access network elements that have historically provided services for the tag to the Network Data Analysis Function (RDF) element. The RDF element then predicts the second target access network element currently providing services for the tag based on these identifiers and sends the prediction result (e.g., the identifier of the second target access network element) to the NCEF element. The NCEF element receives the prediction result and determines the second target access network element based on it.

[0138] In one possible implementation, at least one access network element includes the aforementioned first target access network element (the access network element that most recently provided services for the tag) and the second target access network element (i.e., the predicted target access network element).

[0139] Of course, the above methods are only examples and not limitations. There may be other specific implementation methods for at least one access network element, the target access network element, and the paging process, and this application does not impose any restrictions.

[0140] S103, The network capability opening function network element sends a second paging request to the target access network element, the second paging request carrying the identifier of the tag; correspondingly, the target access network element receives the second paging request.

[0141] Based on the various possible implementations of the target access network element in S102 above, the network capability opening function network element sends a second paging request to the target access network element, including but not limited to the following implementations:

[0142] Method 1: The network capability open function network element sends a second paging request to the first target access network element (i.e., the access network element that last provided services for the tag). The second paging request carries the tag's identifier, so that the first target access network element can paging the tag according to the tag's identifier carried in the second paging request.

[0143] Method 1, which uses the access network element that last provided services to the tag to paging the tag, can improve the paging hit rate.

[0144] Method 2: The network capability open function network element sends a second paging request to the second target access network element (i.e., the access network element that currently provides services for the tag based on historical data prediction). The second paging request carries the tag's identifier so that the second target access network element can paging the tag according to the tag's identifier carried in the second paging request.

[0145] Method 2, which uses predictions of the current access network element providing services to the tag for paging, can improve the paging hit rate.

[0146] Method 3: The Network Capability Opening Function (NCEF) network element can first send a second paging request to the first target access network element. The second paging request carries the tag's identifier, enabling the first target access network element to paging the tag based on the tag's identifier carried in the second paging request. If the first target access network element fails to paging the tag (for example, the NCEF network element receives a paging response from the first target access network element indicating paging failure), then the NCEF network element sends a third paging request to the second target access network element. The third paging request carries the tag's identifier, enabling the second target access network element to paging the tag based on the tag's identifier carried in the third paging request.

[0147] Method 3 first paging the tag through the access network element that most recently provided services for the tag, and if that fails, then paging the tag through the predicted access network element, which can further improve the paging hit rate.

[0148] Method 4: The network capability open function (CVC) element can first send a second paging request to the second target access network element, carrying the tag's identifier, so that the second target access network element can paging the tag based on the tag's identifier carried in the second paging request. If the second target access network element fails to paging the tag (for example, the CVC element receives a paging response from the second target access network element indicating paging failure), then the CVC element sends a third paging request to the first target access network element, carrying the tag's identifier, so that the first target access network element can paging the tag based on the tag's identifier carried in the third paging request.

[0149] Method 4 first attempts to paging the tag through the predicted access network element. If that fails, it then attempts to paging the tag through the access network element that most recently provided service for the tag. This can further improve the paging hit rate.

[0150] Method 5: The network capability open function network element sends a second paging request to the first target access network element and a third paging request to the second target access network element (the order of sending the second paging request and the third paging request is not important). Both the second paging request and the third paging request carry the tag identifier so that both the first target access network element and the second target access network element can paging the tag.

[0151] Method 5 simultaneously paging tags using both the predicted access network element and the access network element that most recently provided services for the tag can improve the paging hit rate while reducing the time required for paging.

[0152] Of course, the above methods are just examples and not limitations. There are other specific implementation methods, and this application does not impose any restrictions.

[0153] In one possible implementation, the Network Capability Open Function (NCEF) network element sends the second paging request to the target access network element through the target access and mobility management (MAM) network element corresponding to the target access network element. The target MAM network element can forward the request between the NCEF network element and the target access network element using either transparent or non-transparent transmission methods; this application does not impose any restrictions. For example, the target MAM network element may directly receive the second paging request from the NCEF network element and then send the second paging request to the target access network element (transparent transmission method); or, the target MAM network element may receive a fourth paging request from the NCEF network element, which may carry the identifier of a tag and the identifier of the target access network element. The target MAM network element then sends the second paging request to the target access network element based on the identifier of the target access network element carried in the fourth paging request (non-transparent transmission method).

[0154] S104. The target access network element identifies the paging tag based on the tag carried in the second paging request.

[0155] For example, see Figure 8 The paging process for a tag by a target access network element may include:

[0156] S301. After receiving the second paging request, the target access network element activates the excitation signal;

[0157] S302. The tag acquires the excitation signal of the target radio access network element and completes the interaction with the underlying layer (such as the AS layer) of the target access network element.

[0158] S303. The target access network element sends a paging response to the application function network element. The paging response is used to indicate that the paging tag was successfully sent. This step is optional. Figure 8 S303 is marked with a dashed line as an optional step;

[0159] S304. The security process is completed between the tag and the core network element. The specific implementation method of this step can be referred to S202 above, and will not be repeated here.

[0160] S305. The core network establishes control plane and / or user plane forwarding channels for the labels. The specific implementation of this step can be found in S203A and S203B above, and will not be repeated here.

[0161] According to S101 to S104 above, the tag can access the core network in a connectionless manner (i.e., the core network does not need to maintain the tag's context for a long time), which can improve the resource utilization of the core network. When the application function network element paging the tag, it can send the paging request to the target access network element (i.e., the access network element that may currently provide services to the tag) through the control plane network element, so that the target access network element can paging the tag. This eliminates the need for all access network elements in the global scope to paging the tag, thus saving the overall access network element overhead.

[0162] As an optional implementation, each paging request in this document (e.g., the first paging request, the second paging request, the third paging request, or the fourth paging request, etc.) may also carry an inventory command, which is used to instruct the operation to be performed on the tag. For example, the inventory command is used to instruct the tag to perform read and / or write operations. Of course, this is just an example; in actual applications, the inventory command includes, but is not limited to, instructing the tag to perform read and / or write operations. After receiving the second paging request and activating the excitation signal, the target access network element sends the inventory command to the tag. This method, by additionally carrying the inventory command in the paging request, can reduce the complexity of the interaction process between the tag and the core network element and reduce the tag's waiting time.

[0163] As an optional implementation, after receiving the inventory command, the tag triggers a security process between itself and the core network element. After completing the security process (i.e., after the tag and the core network element have successfully completed two-way authentication and authorization), it then responds to the inventory command. This can improve the security of tag data.

[0164] As an optional implementation, the application function network element can first page the tag through the user plane network element. If the application function network element fails to page the tag through the user plane network element, it then pages the tag through the control plane network element. Therefore, before the network capability open function network element receives the first paging request from the application function network element, the process can also include: the application function network element failing to page the tag through the user plane network element. In a specific implementation, the application function network element first sends a fifth paging request through the established user plane forwarding channel. The fifth paging request carries the tag's identifier. If the application function network element receives a response from the user plane function network element or the access network element (on the established user plane forwarding channel) indicating a paging failure, the application function network element determines that the user plane network element has failed to page the tag, and then pages the tag through the control plane network element, for example, by sending the first paging request to the network capability open function network element. Optionally, the fifth paging request carries an inventory command. This can further improve the paging hit rate and reduce the paging time.

[0165] It should be understood that the above-described implementation methods can be implemented individually or in combination.

[0166] It is understood that, in order to achieve the functions in the above embodiments, the base station and terminal include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0167] Figure 9 and Figure 10 The diagram illustrates the possible communication devices provided in the embodiments of this application. These communication devices can be used to implement the function of any network element in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0168] like Figure 9 As shown, the communication device 900 includes a processing module 910 and a transceiver module 920. The communication device 900 is used to implement the above-mentioned... Figure 6 or Figure 7 or Figure 8 The method embodiments shown illustrate the function of any network element.

[0169] When the communication device 900 is used to implement Figure 6 In the method embodiment shown, the access network element functions as follows: transceiver module 920 is used to receive a first paging request from an application function network element, the first paging request carrying the identifier of a tag and the identifier of at least one access network element; processing module 910 is used to receive the first paging request from an application function network element, the first paging request carrying the identifier of a tag and the identifier of at least one access network element; transceiver module 920 is also used to send a second paging request to a target access network element, the second paging request carrying the identifier of a tag, so that the target access network element paging the tag according to the identifier of the tag carried in the second paging request.

[0170] When the communication device 900 is used to implement Figure 6 When applying the function of the functional network element in the method embodiment shown: the processing module 910 is used by the transceiver module 920 to store the tag identifier and the identifier of at least one access network element; the transceiver module 920 is used to send a first paging request to the network capability opening function, the first paging request carrying the tag identifier and the identifier of at least one access network element.

[0171] When the communication device 900 is used to implement Figure 6 In the method embodiment shown, when accessing and using the mobility management function network element: the processing module 910 is used to obtain the tag identifier and the identifier of the access network element providing services to the tag; the transceiver module 920 is used to send the access network element identifier and the tag identifier to the application function network element, and the access network element identifier and the tag identifier are used by the application function network element to paging the tag.

[0172] For a more detailed description of the aforementioned processing module 910 and transceiver module 920, please refer to [link / reference needed]. Figure 6 The relevant descriptions in the method embodiments shown are directly obtained and will not be repeated here.

[0173] like Figure 10 As shown, the communication device 1000 includes a processor 1010 and an interface circuit 1020. The processor 1010 and the interface circuit 1020 are coupled to each other. It is understood that the interface circuit 1020 can be a transceiver or an input / output interface. Optionally, the communication device 1000 may also include a memory 1030 for storing instructions executed by the processor 1010, or storing input data required by the processor 1010 to execute instructions, or storing data generated after the processor 1010 executes instructions.

[0174] When the communication device 1000 is used to implement Figure 6 In the method shown, the processor 1010 is used to implement the functions of the processing module 910, and the interface circuit 1020 is used to implement the functions of the transceiver module 920.

[0175] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0176] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. Of course, the processor and storage medium can also exist as discrete components in the base station or terminal.

[0177] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0178] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0179] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0180] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A paging method, characterized in that, include: The network capability open function network element receives a first paging request from the application function network element, wherein the first paging request carries the identifier of the tag and the identifier of at least one access network element. The network capability opening function network element determines the target access network element based on the identifier of the at least one access network element; The network capability open function network element sends a second paging request to the target access network element, the second paging request carrying the identifier of the tag, so that the target access network element can paging the tag according to the identifier of the tag carried in the second paging request; Wherein, the at least one access network element includes the access network element that most recently provided services to the tag; The network capability opening function network element determines the target access network element based on the identifier of the at least one access network element, including: The network capability opening function network element determines the first target access network element based on the access network element that most recently provided services to the tag; The network capability open function network element sends a second paging request to the target access network element, including: The network capability opening function network element sends the second paging request to the first target access network element.

2. The method as described in claim 1, characterized in that, The identifier of the at least one access network element is provided to the application function network element by the core network element.

3. The method as described in claim 1, characterized in that, The first paging request also carries an inventory command, which is used to instruct read and / or write operations to be performed on the tag.

4. The method as described in claim 2, characterized in that, The first paging request also carries an inventory command, which is used to instruct read and / or write operations to be performed on the tag.

5. The method according to any one of claims 1-4, characterized in that, The at least one access network element further includes multiple access network elements that have historically provided services for the tag; the method further includes: The network capability opening function network element determines that the first target access network element failed to page the tag; The network capability open function network element determines a second target access network element based on the multiple access network elements that have historically provided services to the tag; wherein, the second target access network element is the predicted access network element that is currently providing services to the tag; The network capability open function network element sends a third paging request to the second target access network element. The third paging request carries the identifier of the tag, so that the second target access network element can page the tag according to the identifier of the tag carried in the third paging request.

6. The method according to any one of claims 1-4, characterized in that, Before the network capability open function network element receives the first paging request from the application function network element, the method further includes: The application function network element failed to page the tag through the user plane network element.

7. The method as described in claim 5, characterized in that, Before the network capability open function network element receives the first paging request from the application function network element, the method further includes: The application function network element failed to page the tag through the user plane network element.

8. The method according to any one of claims 1-4 and 7, characterized in that, The network capability open function network element sends a second paging request to the target access network element, including: The network capability open function network element sends a fourth paging request to the target access and mobility management function network element corresponding to the target access network element. The fourth paging request carries the identifier of the tag and the identifier of the target access network element, so that the target mobility management function network element sends a second paging request to the target access network element based on the identifier of the tag and the identifier of the target access network element carried in the fourth paging request.

9. The method as described in claim 5, characterized in that, The network capability open function network element sends a second paging request to the target access network element, including: The network capability open function network element sends a fourth paging request to the target access and mobility management function network element corresponding to the target access network element. The fourth paging request carries the identifier of the tag and the identifier of the target access network element, so that the target mobility management function network element sends a second paging request to the target access network element based on the identifier of the tag and the identifier of the target access network element carried in the fourth paging request.

10. The method as described in claim 6, characterized in that, The network capability open function network element sends a second paging request to the target access network element, including: The network capability open function network element sends a fourth paging request to the target access and mobility management function network element corresponding to the target access network element. The fourth paging request carries the identifier of the tag and the identifier of the target access network element, so that the target mobility management function network element sends a second paging request to the target access network element based on the identifier of the tag and the identifier of the target access network element carried in the fourth paging request.

11. A paging method, characterized in that, include: The application function network element obtains the identifier of the tag and the identifier of at least one access network element that provides services to the tag; The application function network element stores the identifier of the tag and the identifier of the at least one access network element; The application function network element sends a first paging request to the network capability opening function, and the first paging request carries the identifier of the tag and the identifier of the at least one access network element; The at least one access network element includes the access network element that most recently provided services to the tag.

12. The method as described in claim 11, characterized in that, The identifier of the at least one access network element is provided to the application function network element by the core network element.

13. The method as described in claim 11, characterized in that, The first paging request also carries an inventory command, which is used to instruct read and / or write operations to be performed on the tag.

14. The method as described in claim 12, characterized in that, The first paging request also carries an inventory command, which is used to instruct read and / or write operations to be performed on the tag.

15. The method according to any one of claims 11-14, characterized in that, The at least one access network element includes multiple access network elements that have historically provided services for the tag.

16. The method according to any one of claims 11-14, characterized in that, Also includes: Before sending the first paging request to the network capability opening function, the application function network element sends a fifth paging request to the user plane network element. The fifth paging request carries the identifier of the tag so that the user plane network element can paging the tag according to the identifier of the tag. It has been confirmed that the user plane network element failed to page the tag.

17. The method as described in claim 15, characterized in that, Also includes: Before sending the first paging request to the network capability opening function, the application function network element sends a fifth paging request to the user plane network element. The fifth paging request carries the identifier of the tag so that the user plane network element can paging the tag according to the identifier of the tag. It has been confirmed that the user plane network element failed to page the tag.

18. A paging method, characterized in that, include: The access and mobility management function network element obtains the identifier of the tag and the identifier of the access network element providing services to the tag; The access and mobility management function network element sends the identifier of the access network element and the identifier of the tag to the application function network element. The identifier of the access network element and the identifier of the tag are used by the application function network element to page the tag.

19. The method as described in claim 18, characterized in that, Also includes: The access and mobility management function network element receives a fourth paging request from the network capability open function network element, the fourth paging request carrying the identifier of the tag and the identifier of the access network element; The access and mobility management function network element sends a second paging request to the access network element based on the identifier of the tag carried in the fourth paging request and the identifier of the access network element. The second paging request carries the identifier of the tag, so that the access network element can paging the tag based on the identifier of the tag carried in the second paging request.

20. A communication device, characterized in that, include: The transceiver module is used to receive a first paging request from an application function network element, wherein the first paging request carries the identifier of a tag and the identifier of at least one access network element. The processing module is used to determine the target access network element based on the identifier of the at least one access network element; The transceiver module is further configured to send a second paging request to the target access network element, the second paging request carrying the identifier of the tag, so that the target access network element can paging the tag according to the identifier of the tag carried in the second paging request; Wherein, the at least one access network element includes the access network element that most recently provided services to the tag; Processing module, used for: The first target access network element is determined based on the access network element that most recently provided services to the tag; The transceiver module is used for: Send the second paging request to the first target access network element.

21. A communication device, characterized in that, include: The processing unit is used to obtain the identifier of the tag and the identifier of at least one access network element that provides services to the tag; Store the identifier of the tag and the identifier of the at least one access network element; The transceiver unit is used to send a first paging request to the network capability exposure function, wherein the first paging request carries the identifier of the tag and the identifier of the at least one access network element; The at least one access network element includes the access network element that most recently provided services to the tag.

22. A communication device, characterized in that, include: The processing unit is used to obtain the identifier of the tag and the identifier of the access network element that provides services to the tag; The transceiver unit is used to send the identifier of the access network element and the identifier of the tag to the application function network element. The identifier of the access network element and the identifier of the tag are used by the application function network element to page the tag. The identifier of the access network element belongs to the identifier of at least one access network element, and the at least one access network element includes the access network element that most recently provided services to the tag.

23. A communication device, characterized in that, The device includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor is used to implement the method as described in any one of claims 1-10, 11-17, or 18-19 through logic circuits or execution code instructions.

24. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1-10, 11-17, or 18-19.

Images