Wireless communication methods, systems and network open functional network elements, passive Internet of Things terminals
By enhancing the functionality of NEF network elements and selecting appropriate core network elements to execute AIoT services, the problem of the core network's inability to effectively support AIoT services has been solved, enabling flexible and efficient execution of AIoT services.
Patent Information
- Application Number
- CN202510622231.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-14
- Publication Date
- 2026-11-17
AI Technical Summary
The core network is currently unable to effectively support the execution of passive Internet of Things (AIoT) services and lacks flexible and efficient support for AIoT terminals.
By enhancing the functionality of Network Open Function (NEF) network elements, they can receive AIoT service requests and select appropriate core network elements from the core network to execute AIoT services, including selecting the first core network element and forwarding the service request and receiving the service result.
It enables the core network to provide flexible and efficient support for AIoT services, improves the processing efficiency and flexibility of AIoT services, and adapts to the needs of AIoT terminals of different types and states.
Smart Images

Figure CN123123835A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a wireless communication method, system and network open functional network element, and passive Internet of Things terminal. Background Technology
[0002] Passive IoT (AIoT) is an IoT technology that relies on external wireless signals for communication. Its key feature is that passive IoT terminals (hereinafter referred to as "AIoT terminals") do not require an external power source or built-in battery; instead, they obtain energy from the environment through energy harvesting technology for communication. Passive IoT services (hereinafter referred to as "AIoT services") refer to various application services based on AIoT technology, widely used in fields such as logistics and transportation, warehousing and inventory management, and environmental monitoring. Summary of the Invention
[0003] According to some embodiments of this disclosure, a wireless communication method is provided, executed by a Network Open Function (NEF) network element, comprising: receiving a service request to execute a passive Internet of Things (AIoT) service; selecting a first core network element; forwarding the service request to the first core network element; and receiving a first service result of executing the AIoT service returned by the first core network element.
[0004] According to some other embodiments of this disclosure, a wireless communication method is provided, executed by an AIoT terminal, comprising: executing an AIoT service through a wireless-side read / write device, wherein the wireless-side read / write device is selected by an AIoT wireless access network node based on a received service request for executing the AIoT service, wherein the service request is forwarded by a NEF network element to the AIoT wireless access network node via a first core network element, and the first core network element is selected by the NEF element; and sending a first service result of the AIoT service to the first core network element through the wireless-side read / write device, so that the first core network element returns the first service result to the NEF network element.
[0005] According to some embodiments of this disclosure, a network open function element is provided, including: a first receiving module configured to receive a service request for executing an AIoT service; a selection module configured to select a first core network element; a sending module configured to forward the service request to the first core network element; and a second receiving module configured to receive a first service result of executing the AIoT service returned by the first core network element.
[0006] According to further embodiments of this disclosure, a passive Internet of Things (IoT) terminal is provided, comprising: an execution module configured to execute a passive IoT AIoT service via a wireless side read / write device, wherein the wireless side read / write device is selected by an AIoT wireless access network node based on a received service request for executing the AIoT service, the service request being forwarded from a NEF network element to the AIoT wireless access network node via a first core network element, the first core network element being selected by the NEF network element; and a transmission module configured to send a first service result of the AIoT service to the first core network element via the wireless side read / write device, so that the first core network element returns the first service result to the NEF network element.
[0007] According to some embodiments of this disclosure, a wireless communication system is provided, including: a NEF network element configured to perform the wireless communication method for AIoT in any of the above embodiments; and an AIoT terminal configured to perform the wireless communication method in any of the above embodiments.
[0008] According to some embodiments of the present disclosure, an electronic device is provided, including: a memory; and a processor coupled to the memory, the processor being configured to execute the wireless communication method of any of the above embodiments based on instructions stored in the memory device.
[0009] According to some embodiments of the present disclosure, a computer-readable storage medium is provided that stores computer instructions thereon, which, when executed by a processor, implement the wireless communication method in any of the above embodiments.
[0010] According to further embodiments of this disclosure, a computer program product is also provided, including instructions that, when executed by a processor, cause the processor to perform a wireless communication method according to any of the foregoing embodiments. Attached Figure Description
[0011] The accompanying drawings, which form part of this specification, illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure.
[0012] This disclosure will become clearer with reference to the accompanying drawings and the following detailed description, wherein:
[0013] Figure 1 A flowchart illustrating a wireless communication method according to some embodiments of the present disclosure is shown;
[0014] Figure 2 A signaling diagram of a wireless communication method according to some embodiments of the present disclosure is shown;
[0015] Figure 3 A network architecture diagram of a wireless communication system according to some embodiments of the present disclosure is shown;
[0016] Figure 4 A schematic diagram illustrating a wireless communication method according to some embodiments of the present disclosure is shown;
[0017] Figure 5 A flowchart illustrating a wireless communication method according to other embodiments of the present disclosure is shown;
[0018] Figure 6 A block diagram of network open function network elements according to some embodiments of the present disclosure is shown;
[0019] Figure 7 A block diagram of an AIoT terminal according to some embodiments of the present disclosure is shown;
[0020] Figure 8 A block diagram of an electronic device according to some embodiments of the present disclosure is shown;
[0021] Figure 9 Block diagrams of electronic devices according to other embodiments of the present disclosure are shown;
[0022] Figure 10 A block diagram of a wireless communication system according to some embodiments of the present disclosure is shown. Detailed Implementation
[0023] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.
[0024] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.
[0025] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.
[0026] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.
[0027] In all examples shown and discussed herein, any specific values should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.
[0028] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.
[0029] The inventors of this disclosure have discovered through research that the smooth operation of AIoT services relies heavily on the support of the core network. However, the core network is currently unable to support the execution of AIoT services.
[0030] In view of this, this disclosure proposes a wireless communication method for AIoT, which enhances the functionality of the Network Exposure Function (NEF) network elements in the core network, enabling the NEF network elements to receive service requests for executing AIoT services and select core network elements from the core network to support the execution of the AIoT service, thereby enabling the core network to support the smooth execution of AIoT services.
[0031] Figure 1 A flowchart illustrating a wireless communication method for AIoT according to some embodiments of this disclosure is shown. Figure 1 As shown, the wireless communication method for AIoT is executed by a NEF network element and includes at least one of steps 110 to 140.
[0032] NEF (Network Element) is a core network element of the AIoT network, used to present the capabilities of one or more other core network elements in the AIoT network to other network elements, such as application function (AF) network elements.
[0033] In step 110, a service request to execute AIoT services is received.
[0034] In some embodiments, service requests for executing AIoT services may originate from application function (AF) network elements.
[0035] In some embodiments, the service request may carry at least one of the identification information or location information of the AIoT terminal targeted by the AIoT service.
[0036] For example, the identification information of an AIoT terminal may include the AIoT terminal's ID.
[0037] For example, the location information of an AIoT terminal may include at least one of the following: location information or target area information. Location information identifies the location of the AIoT terminal, such as a location determined based on the Global Positioning System (GPS). Target area information can identify the area where the AIoT terminal is located, such as the cell to which the AIoT terminal belongs.
[0038] In some embodiments, an AIoT terminal is an IoT device with extremely low energy storage, extremely low power consumption, and no SIM card. Furthermore, AIoT terminals are categorized into weak terminals and strong terminals based on whether they have an amplifier. Weak terminals only support backscatter communication, while strong terminals can generate signals themselves or support backscatter communication.
[0039] In some embodiments, AIoT services may include one or more services such as warehouse inventory management, data collection, and device control. A service request to execute an AIoT service instructs the core network to execute a specified AIoT service for a designated terminal.
[0040] For example, an AIoT service could be a warehouse inventory management service, where a service request could instruct one or more AIoT terminals (e.g., goods with Radio Frequency Identification (RFID) tags) within a certain area to report their identification, status, and location. Alternatively, an AIoT service could be a data collection service, where a service request could instruct one or more AIoT terminals within a certain area to monitor and periodically report measurement results of specified parameters (e.g., ambient temperature, humidity). Finally, an AIoT service could be a device control service, where a service request could instruct the writing of control information to one or more AIoT terminals within a certain area, enabling these terminals to control themselves or other devices according to the written control information. In step 120, a first core network element is selected.
[0041] The first core network element is a network element in the core network that enables the execution of AIoT services corresponding to service requests. In some embodiments, the first core network element forwards service requests corresponding to AIoT services to the AIoT terminals corresponding to the AIoT services, so that the AIoT services can be executed by the AIoT terminals. More specifically, the first core network element can forward the service request to the AIoT-Radio Access Network (AIoT-RAN) corresponding to the AIoT terminal, so that the AIoT-RAN can further execute the AIoT services for the AIoT terminals. In some embodiments, the first core network element can be responsible for the management and execution of AIoT services, and provide AIoT terminals with access and service management functions.
[0042] In some embodiments, the first core network element may be an Ambient IoT Function (AIoTF) element.
[0043] In some embodiments, the core network may include a plurality of first core network elements capable of executing AIoT services. An NEF element may select one of these first core network elements to execute the AIoT service corresponding to the current service request.
[0044] In some embodiments, NEF network elements can select the first core network element independently based on service requests or according to instructions from other network elements. The following sections will further explain the method by which NEF network elements select the first core network element using some embodiments.
[0045] In step 130, the service request for executing AIoT services is forwarded to the first core network element.
[0046] In some embodiments, after receiving a service request to perform an AIoT service, the first core network element can coordinate with nodes in the passive IoT radio access network (AIoT-RAN) to perform the AIoT service on the AIoT terminal requested by the AIoT service and obtain the first service result of performing the AIoT service.
[0047] In step 140, the first service result of executing the AIoT service is received from the first core network element.
[0048] In some embodiments, the first business result may include information on whether all business operations were successfully executed.
[0049] In some embodiments, if the first service result indicates that all AIoT services were successfully executed, the first service result may further include successful execution result information. For example, when the AIoT service involves reading or writing to a specific AIoT terminal, the first service result may record information about the AIoT terminals that were successfully read or successfully written to.
[0050] In some embodiments, if the first service result indicates that the AIoT service portion of the execution has failed, the first service result may further include successful execution result information, failed execution result information, and the reason for the failure. For example, the number of AIoT terminals targeted by the AIoT service may be multiple. The first service result may record the ID of the AIoT terminal whose information was successfully read, the information of the AIoT terminal whose information was successfully read, the ID of the AIoT terminal whose information was not successfully read, and the reason for the failure to read the information. For example, the reason may be that no response was received from the AIoT terminal (e.g., the AIoT terminal may be offline due to malfunction or other reasons).
[0051] In some embodiments, if the first service result is that all AIoT services fail to execute, the first service result may further include information about the execution failure and the reason for the failure. For example, the first service result may record the ID of the AIoT terminal whose information was not successfully read and the reason for the failure to read the information.
[0052] In some embodiments, the NEF network element may choose whether to send the first service result based on the received first service result.
[0053] For example, if the first service result is that all AIoT services are successfully executed, the NEF network element can send the first service result (e.g., to the AF network element).
[0054] If the first service result indicates that the AIoT service has at least partially failed, the NEF network element can choose not to send the first service result temporarily and perform other operations based on the first service result. This will be explained further below.
[0055] In other words, NEF network elements can selectively provide the first service result of the first core network element executing AIoT services.
[0056] In the above embodiments, the NEF network element in the core network can select a first core network element from the core network to support the execution of the AIoT service based on the received service request for executing the AIoT service, then forward the service request to the selected first core network element, and receive the first service result of executing the AIoT service returned by the first core network element.
[0057] In this approach, the NEF network elements in the core network are capable of receiving and processing service requests for AIoT services, as well as selecting a suitable first core network element to complete the requested AIoT service. By enhancing the processing capabilities of the NEF network elements related to AIoT services, the core network can provide flexible and efficient support for the smooth execution of AIoT services.
[0058] The following examples illustrate the implementation of step 120, namely, the NEF network element selecting the first core network element.
[0059] In some embodiments, service requests for executing AIoT services can be sent by the AF network element. The NEF network element can select the first core network element based on whether the service request sent by the AF network element carries indication information related to the AIoT service.
[0060] In this way, external service providers of AIoT services can selectively provide instructions through AF network elements as needed, so that NEF network elements can flexibly select appropriate first core network elements to support the execution of the requested AIoT services, thereby enabling AIoT services to be executed flexibly and efficiently.
[0061] In some embodiments, indication information related to AIoT services can be carried in existing fields in the service request.
[0062] In some embodiments, new fields may be added to the business request to carry indication information related to the AIoT business.
[0063] In some embodiments, the indication information related to the AIoT service in the service request may include either indication information related to the service type of the AIoT service or indication information related to the AIoT terminal targeted by the AIoT service.
[0064] In some embodiments, the indication information related to the AIoT service may include indication information related to the service type of the AIoT service. For example, the indication information may be used to indicate that the service type of the AIoT service is any one of a new service, a continuous service, or a non-continuous service (also referred to as an "existing service"), wherein both continuous and non-continuous services are considered non-new services.
[0065] A completely new service refers to an AIoT service involved in a service request that has not been requested to be executed before and / or has not been executed on the AIoT terminal targeted by the service request. In some cases, the service type of the AIoT service can be directly indicated as a completely new service in the service request. In other cases, the service type of the AIoT service can be indirectly indicated by existing or newly added fields in the service request. For example, when a completely new service is one in which no AIoT service has been executed on the AIoT terminal targeted by the service request, it means that the AIoT terminal targeted by the AIoT service has not been registered in the core network. In this case, the service type of the AIoT service can be indirectly indicated as a completely new service by indicating that the AIoT terminal has not been registered in the core network in the service request.
[0066] It's important to clarify that AIoT terminal registration in the core network refers to the AIoT terminal submitting relevant information for identity authentication (such as the AIoT terminal's enterprise information, identification information, device capability information, and supported service types) to the core network through a series of processes. The terminal then completes the relevant policy and service configurations within the core network to obtain access permissions and services. Through registration, the AIoT terminal's relevant information can be stored in relevant network elements of the core network (such as Unified Data Repository (UDR) elements). For example, the AIoT terminal can submit relevant identity authentication information to the core network through AF (Automatic Data Repository) elements.
[0067] Continuous service refers to a short time interval between the current AIoT service request and the previous AIoT service request, meaning the AIoT service is requested and executed consecutively within a short period. In some cases, the service type can be directly indicated as continuous service in the service request. In other cases, the service type can be indirectly indicated through existing or newly added fields in the service request. For example, including the same AIoT service and the same AIoT terminal in two or more consecutive service requests, and ensuring the time interval between the service requests does not exceed a certain threshold, indicates that the requested AIoT service is a continuous service. As another example, in some cases, continuous service means that the AIoT terminal targeted by the AIoT service has been registered in the core network and its movement range has not exceeded a specified range. Therefore, in this case, indicating that the AIoT terminal is already registered in the core network and that its movement range has not exceeded the specified range in the service request can indirectly indicate that the AIoT service is a continuous service.
[0068] Discontinuous service refers to an AIoT service request that occurs at a relatively long interval between the current request and the previous request. In some cases, the service type can be directly indicated as discontinuous in the service request. In other cases, the service type can be indirectly indicated through existing or newly added fields in the service request. For example, in some cases, discontinuous service means that the AIoT terminal targeted by the service has already registered with the core network and its movement range exceeds a specified range. Therefore, in this case, indicating that the AIoT terminal is already registered with the core network and that its movement range exceeds the specified range in the service request can indirectly indicate that the AIoT service type is discontinuous.
[0069] Taking AIoT services as warehouse inventory services as an example, assuming that one or more AIoT terminals signed by the AF network element are deployed in the same warehouse, and the mobility of these one or more AIoT terminals is low (for example, the movement range of these one or more AIoT terminals does not exceed the range of the warehouse), then the AF network element can carry indication information indicating that the service type of the AIoT service is a continuous service in each service request initiated for the inventory service of these one or more AIoT terminals.
[0070] Taking AIoT services as an example of warehouse inventory management, if one or more new AIoT terminals that have signed a new contract with the AF network element are newly added to the warehouse, the AF network element can include indication information in the business request for the inventory management of these one or more newly contracted AIoT terminals to indicate that the business type of the AIoT service is a brand new service.
[0071] It should be noted that the signing of an agreement between an AF network element and an AIoT terminal refers to the AIoT terminal submitting relevant information (such as the AIoT terminal's enterprise information, identification information, device capability information, and supported service types) to the core network through the AF network element for registration.
[0072] In this way, the AF network element can provide clear indication information indicating the type of AIoT service. The NEF network element can flexibly select the appropriate first core network element to execute the AIoT service based on its service type, thereby improving the flexibility of AIoT service processing.
[0073] In some embodiments, the indication information related to the AIoT service may include indication information related to the AIoT terminal targeted by the AIoT service. For example, the indication information may be used to indicate the status of the AIoT terminal targeted by the AIoT service. For example, the status of the AIoT terminal may include the following three statuses: the AIoT terminal has not registered with the core network, the AIoT terminal has registered with the core network and its movement range has not exceeded the specified range, and the AIoT terminal has registered with the core network and its movement range has exceeded the specified range.
[0074] In this way, the AF network element can provide clear indication information indicating the status of the AIoT terminal requested by the AIoT service. The NEF network element can flexibly select the appropriate first core network element to execute the AIoT service based on the status of the requested AIoT terminal, thereby improving the flexibility of AIoT service processing.
[0075] The following examples illustrate how NEF network elements select the first core network element when the service request carries indication information related to AIoT services.
[0076] In some embodiments, when the service request sent by the AF network element carries indication information related to AIoT services, the NEF network element can select the first core network element based on the indication information.
[0077] Specifically, NEF network elements can determine the identity of the first core network element based on the indication information related to AIoT services carried in the service request. Then, based on the determined identity of the first core network element, it can choose to select that first core network element through either the second or third core network element. The second and third core network elements are different.
[0078] In some embodiments, the second core network element can be an Ambient IoT Data Management (ADM) network element. For example, the ADM network element can be responsible for managing the subscription information and / or service information of AIoT terminals. For example, the subscription information of AIoT terminals may include one or more of the following: the enterprise information of the AIoT terminal subscribed to by the AF network element, the ID of the AIoT terminal, and the device capability information. The service information of AIoT terminals may include the service types supported by the AIoT terminal.
[0079] In some embodiments, the third core network element can be a Network Repository Function (NRF) element. For example, an NRF element can be responsible for storing the network element information of each first core network element in the core network. For example, the network element information of each first core network element in the core network may include one or more of the following: the identification information of each first core network element, its deployment location, its service range, and the service types of AIoT services it can support.
[0080] The following examples illustrate how NEF network elements select the first core network element through the second core network element.
[0081] In some embodiments, the NEF network element determines the identity of the first core network element based on the indication information related to the AIoT service carried in the service request, and selects the first core network element through the second core network element.
[0082] For example, the first network element identity can be the first core network element (also known as the "Last known AIoTF" network element) most recently associated with the AIoT terminal targeted by the requested AIoT service. For example, the most recently associated first core network element can be the AIoTF network element that most recently associated with the AIoT terminal and supported the AIoT terminal in executing AIoT services.
[0083] In some embodiments, when a NEF network element responds to indication information related to the AIoT service carried in a service request, indicating that the AIoT service type is a continuous service, it can determine the identity of the first core network element. In this case, the NEF network element will select the first core network element through a second core network element (e.g., an ADM network element).
[0084] In some embodiments, if the NEF network element responds to the indication information related to the AIoT service carried in the service request, indicating that the AIoT terminal targeted by the AIoT service has been registered in the core network and that the movement range of the AIoT terminal has not exceeded the specified range, it can determine the identity of the first core network element as the first network element identity. In this case, the NEF network element will select the first core network element through a second core network element (e.g., an ADM network element).
[0085] In other words, the AF network element can choose to provide either the service type of the AIoT service or the status information of the AIoT terminal targeted by the AIoT service in the service request, so that the NEF network element can know the identity of the first core network element as the first network element identity. Then, based on the first network element identity, the NEF network element selects the first core network element through the second core network element.
[0086] As some exemplary implementations, the service request received by the NEF network element to execute AIoT services may carry the identification information of the AIoT terminal targeted by the AIoT service.
[0087] The NEF network element can provide this identification information to the second core network element to request the second core network element to query the network element information of the first core network element. The NEF network element can receive the network element information of the first core network element returned by the second core network element based on the identification information.
[0088] In some embodiments, the network element information of the first core network element returned by the second core network element may include the identification information of the first core network element. For example, the identification information of the first core network element may include the ID of the first core network element.
[0089] In some embodiments, the second core network element can retrieve the network element information of the first core network element from the fourth core network element based on the identification information of the AIoT terminal. For example, the second core network element is an ADM network element, and the fourth core network element is a UDR network element.
[0090] For example, the UDR network element can be responsible for storing the identification information of the AIoT terminal targeted by the AIoT service, as well as the identification information of the first core network element most recently associated with the AIoT terminal. The ADM network element can obtain the network element information of the first core network element from the UDR network element by providing the identification information of the AIoT terminal to the UDR network element.
[0091] In this way, the NEF network element can query the network element information of the first core network element through the second core network element based on the identification information of the AIoT terminal, so as to complete the selection of the first core network element, thereby enabling AIoT services to be executed flexibly and efficiently.
[0092] The following examples illustrate how NEF network elements select the first core network element through the third core network element.
[0093] In some embodiments, the NEF network element determines the identity of the first core network element as the second network element identity based on the indication information related to the AIoT service carried in the service request, and selects the first core network element through the third core network element. The second network element identity is different from the first network element identity.
[0094] For example, the second network element identity can be a first core network element that is not most recently associated with the AIoT terminal targeted by the requested AIoT service. That is, the second network element identity can be a "non-Last known AIoTF" network element, which will also be referred to as a "Related AIoTF" network element below.
[0095] In some embodiments, in response to indications carried in a service request that the AIoT service type is a new service or a discontinuous service, the NEF network element can determine the identity of the first core network element as the second network element. In this case, the NEF network element will select the first core network element through a third core network element (e.g., an NRF network element).
[0096] In some embodiments, if a NEF network element responds to indication information related to the AIoT service carried in a service request, indicating that the AIoT terminal targeted by the AIoT service has not been registered in the core network, it can determine that the identity of the first core network element is that of the second network element. In this case, the NEF network element will select the first core network element through a third core network element (such as an NRF network element).
[0097] In some embodiments, if a NEF network element responds to indication information related to the AIoT service carried in a service request, indicating that the AIoT terminal targeted by the AIoT service has been registered in the core network and that the movement range of the AIoT terminal exceeds a specified range, it can determine the identity of the first core network element as the identity of the second network element. In this case, the NEF network element will select the first core network element through a third core network element (e.g., an NRF network element).
[0098] In other words, the AF network element can choose to provide either the service type of the AIoT service or the status information of the AIoT terminal targeted by the AIoT service in the service request, so that the NEF network element can know that the identity of the first core network element is the identity of the second network element. Then, based on the identity of the second network element, the NEF network element selects the first core network element through the third core network element.
[0099] As some exemplary implementations, the service requests received by the NEF network element to execute AIoT services may carry the location information of the AIoT terminal targeted by the AIoT service.
[0100] The NEF network element can provide this location information to the third core network element in order to request the third core network element to query the network element information of the first core network element. The NEF network element can receive the network element information of the first core network element determined based on the location information returned by the third core network element.
[0101] In some embodiments, the network element information of the first core network element returned by the third core network element may include the identification information of the first core network element. For example, the identification information of the first core network element may include the ID of the first core network element.
[0102] In some embodiments, the third core network element queries the local first core network element that can support the requested AIoT service based on the location information. For example, the third core network element is an NRF network element. The NRF network element can perform a network element query based on the location information and the network element information of each first core network element stored locally, and return the network element information of the first core network element that meets the service conditions (e.g., the service range covers the location of the AIoT terminal and the service type that can support the AIoT service) to the NRF network element.
[0103] In some embodiments, if multiple first core network elements queried by the third core network element based on the location information all meet the service conditions, the third core network element can select to return the network element information of one of the first core network elements to the NEF network element based on the strength of the service capabilities of each first core network element. For example, the closer the deployment location of the first core network element is to the location of the AIoT terminal, and the stronger the signal of the first core network element, the stronger the service capability of the first core network element. For example, the third core network element is an NRF network element. The NRF network element can choose to return the network element information of the first core network element with the strongest service capability to the NEF network element.
[0104] In this way, the NEF network element can query the network element information of the first core network element through the third core network element based on the location information of the AIoT terminal, thereby selecting the first core network element and enabling the AIoT service to be executed flexibly and efficiently. The following examples illustrate how the NEF network element selects the first core network element when the service request does not carry indication information that can be used to determine the identity of the first core network element.
[0105] In some embodiments, if the service request sent by the AF network element does not carry the indication information, the NEF network element may select the first core network element according to the local policy pre-configured based on the subscription information of the AIoT service.
[0106] For example, operators can pre-configure local policies in the NEF network element to select the first core network element to execute the AIoT service based on the subscription information of the AIoT service. For example, operators can flexibly configure this local policy based on information such as the deployment location and service range of multiple first core network elements in the core network, as well as the deployment location of the terminals targeted by the AIoT service.
[0107] In this way, external service providers for AIoT services can sign up for AIoT services with operators on demand. Operators pre-configure corresponding local policies in the NEF network elements based on the AIoT service contract information. Thus, without needing to provide instructions through the AF network elements, the NEF network elements can independently select the first core network element to execute the requested AIoT service, reducing unnecessary network element queries and retrieval processes, thereby improving the processing efficiency of AIoT services.
[0108] In some embodiments, the pre-configured local policy may include either a first correspondence between the AF network element and the first core network element or a second correspondence between the AIoT terminal and the first core network element.
[0109] In some embodiments, an AF network element can subscribe to multiple AIoT terminals. If the multiple AIoT terminals subscribed to by the AF network element are all deployed in the same area, and the mobility of these multiple AIoT terminals is low (for example, in a warehouse inventory scenario, the multiple AIoT terminals subscribed to by the AF network element are all deployed in the same warehouse and the movement range of each AIoT terminal does not exceed the range of the warehouse), then the pre-configured local policy may include a first correspondence between the AF network element and the first core network element.
[0110] It is understandable that, considering that multiple AIoT terminals subscribed to by an AF network element are deployed in the same area and these AIoT terminals have low mobility, the first core network element supporting the AIoT service requested by the AF network element usually remains unchanged. Therefore, for any service request from the AF network element, the requested AIoT service can be consistently executed by the same first core network element, meaning that the first correspondence between the AF network element and the first core network element can be pre-configured.
[0111] In this way, regardless of what kind of AIoT service the service request from the AF network element is for, as long as the service request received by the NEF network element is sent by the AF network element, the NEF network element can choose to have the requested AIoT service executed by the same first core network element corresponding to the AF network element. This reduces unnecessary network element query and retrieval processes and improves the processing efficiency of AIoT services.
[0112] In some embodiments, an AF network element can subscribe to multiple AIoT terminals. If the multiple AIoT terminals subscribed to by the AF network element are deployed in multiple different areas, and the mobility of these multiple AIoT terminals is low (e.g., in a warehouse inventory scenario, the multiple AIoT terminals subscribed to by the AF network element are deployed in multiple different warehouses, and the movement range of each AIoT terminal does not exceed the range of its respective warehouse), then the pre-configured local policy may include a second correspondence between the AIoT terminals and the first core network element. For example, one or more AIoT terminals in the same area may correspond to the same first core network element.
[0113] It is understandable that, considering the multiple AIoT terminals contracted by the AF network element are deployed in different areas, configuring a first correspondence between the AF network element and the first core network element might prevent the configured first core network element from supporting the execution of AIoT services in some areas. In this case, since the mobility of each AIoT terminal is low, the first core network element supporting AIoT services for each AIoT terminal usually remains unchanged. Therefore, as long as the requested AIoT service targets one or more specific AIoT terminals in the same area, the requested AIoT service can be consistently executed by the same first core network element, meaning a second correspondence between the AIoT terminal and the first core network element can be pre-configured.
[0114] In this way, regardless of what kind of AIoT service the service request from the AF network element is for, as long as the requested AIoT service is for one or more specific AIoT terminals, the NEF network element can choose to have the same first core network element corresponding to these one or more specific AIoT terminals execute the requested AIoT service. This reduces unnecessary network element query and retrieval processes and improves the processing efficiency of AIoT services.
[0115] In some embodiments, the first correspondence and / or the second correspondence may take different forms.
[0116] In some embodiments, the first correspondence can be the correspondence between the ID of the AF network element and the ID of the first core network element.
[0117] In some embodiments, the first correspondence may be the correspondence between the ID of the AF network element and the selection operation of the NEF network element. The selection operation may include the operation of selecting the first core network element through the second core network element or the operation of selecting the first core network element through the third core network element.
[0118] For example, if the ID of a certain AF network element corresponds to the operation of selecting the first core network element through the second core network element, then as long as the received service request is sent by that AF network element, the NEF network element will select the first core network element through the second core network element.
[0119] For example, if the ID of a certain AF network element corresponds to the operation of selecting the first core network element through the third core network element, then as long as the received service request is sent by that AF network element, the NEF network element will select the first core network element through the third core network element.
[0120] In some embodiments, the second correspondence may be the correspondence between the ID of the AIoT terminal and the ID of the first core network element.
[0121] In some embodiments, the second correspondence may be the correspondence between the ID of the AIoT terminal and the selection operation of the NEF network element. The selection operation may include the operation of selecting the first core network element through the second core network element or the operation of selecting the first core network element through the third core network element.
[0122] For example, if the ID of a certain AIoT terminal corresponds to the operation of the NEF network element in selecting the first core network element through the second core network element, then as long as the AIoT terminal targeted by the received service request is that AIoT terminal, the NEF network element will select the first core network element through the second core network element.
[0123] For example, if the ID of a certain AIoT terminal corresponds to the operation of the NEF network element in selecting the first core network element through the third core network element, then as long as the AIoT terminal targeted by the received service request is that AIoT terminal, the NEF network element will select the first core network element through the third core network element.
[0124] The following examples further illustrate the operations that a NEF network element can perform after receiving the first service result returned by the first core network element.
[0125] In some embodiments, the NEF network element can determine whether to reselect another first core network element for executing AIoT services based on the first service result. In some further embodiments, the network element identity of the reselected other first core network element may be different from that of the previously selected first core network element. For example, the previously selected first core network element may be a "Last known AIoTF" network element, while the reselected other first core network element may be a "Related AIoTF" network element. Accordingly, the core network element relied upon in the two selections will also change. For example, the "Last known AIoTF" network element was determined through a second core network element in the previous selection, while the "Related AIoTF" network element was determined through a third core network element in the reselection. The same applies when the two selections are reversed. In some further embodiments, the network element identity of the reselected other first core network element may be the same as that of the previously selected first core network element.
[0126] In this way, NEF network elements can choose whether to reselect another first core network element to continue executing the AIoT service based on the execution status of the first core network element, thereby improving the reliability of AIoT service execution.
[0127] In some embodiments, in response to a first service outcome where the AIoT service fails to execute at least partially, the NEF network element reselects another first core network element to execute the AIoT service via a third core network element. For example, the third core network element is an NRF network element.
[0128] Here, the method of selecting other first core network elements through the third core network element is similar to the method of selecting first core network elements through the third core network element. The relevant implementation can be referred to the description in the relevant embodiments above, and will not be repeated here.
[0129] Thus, by introducing a reselection mechanism for the first core network element, the NEF network element can select a reliable first core network element to complete the requested AIoT service, thereby enabling the AIoT service to be executed efficiently and reliably.
[0130] In some embodiments, after reselecting other first core network elements, the NEF network element can forward the service request for executing AIoT services to other first core network elements and receive the second service result of the AIoT services returned by other first core network elements.
[0131] In some embodiments, the second business result may include information on whether all business operations were successfully executed.
[0132] In some embodiments, if the second service result indicates that all AIoT services were successfully executed, the second service result may further include successful execution result information. For example, the second service result may record information about AIoT terminals that were successfully read or successfully written.
[0133] In some embodiments, if the second service result indicates that the AIoT service portion of the execution has failed, the second service result may further include information indicating successful execution, information indicating failed execution, and the reason for the failure. For example, if the AIoT service targets multiple AIoT terminals, the second service result may record the ID of the AIoT terminal whose information was successfully read, the information of the successfully read AIoT terminal, the ID of the AIoT terminal whose information was not successfully read, and the reason for the unsuccessful reading. For example, the reason may be that no response was received from the AIoT terminal (e.g., the AIoT terminal may be offline due to malfunction or other reasons).
[0134] In some embodiments, if the second service result is that all AIoT services fail to execute, the second service result may further include information about the execution failure and the reason for the failure. For example, the second service result may record the IDs of the AIoT terminals whose information was not successfully read and the reasons for the failure to read the information.
[0135] In some embodiments, the NEF network element responds to a second service result indicating that all AIoT services have been successfully executed by sending both the first and second service results. For example, the NEF network element can send the first and second service results to the AF network element. For details regarding the first service result, please refer to the descriptions in the preceding embodiments; they will not be repeated here.
[0136] In this way, NEF network elements can provide the service results of the selected first core network element executing the AIoT service when all AIoT services are successfully executed. That is, NEF network elements can summarize and provide all service results at once, thereby reducing the number of information transmissions and processing time, and improving the processing efficiency of AIoT services.
[0137] In some embodiments, in response to the second service result that the AIoT service has at least partially failed to execute, the NEF network element continues to reselect another first core network element to execute the AIoT service through the third core network element.
[0138] It should be understood that the method by which a NEF network element selects the first core network element each time can be implemented in a similar manner to the methods described in the relevant embodiments above, and will not be repeated here.
[0139] In other words, as long as the requested AIoT service is not fully executed, the NEF network element can initiate a reselection mechanism to select a different first core network element to continue executing the AIoT service, thereby enabling the AIoT service to be executed efficiently and reliably.
[0140] In some embodiments, in response to the first service result indicating that all AIoT services have been successfully executed, the NEF network element determines not to reselect any other first core network element and sends the first service result. For example, the NEF network element can send the first service result to the AF network element.
[0141] In this way, AIoT services can be completed by selecting the first core network element once, reducing unnecessary query and retrieval processes and improving the processing efficiency of AIoT services.
[0142] Figure 2 Signaling diagrams for wireless communication methods for AIoT according to some embodiments of this disclosure are shown. For example, Figure 2 The diagram schematically shows that the first core network element is the first AIoTF network element, the other first core network elements are the second AIoTF network elements, the second core network elements are the ADM network elements, the third core network element is the NRF network element, and the fourth core network element is the UDR network element.
[0143] like Figure 2 As shown, in event 1, the AF network element sends a service request to the NEF network element to execute AIoT services.
[0144] In some embodiments, the AF network element may choose whether to include indication information related to the AIoT service in the service request.
[0145] In some embodiments, the service request may carry the identification information and location information of the AIoT terminal to which the AIoT service is targeted.
[0146] In Event 2, the NEF network element selected the first AIoTF network element.
[0147] In some embodiments, when the service request carries indication information related to the AIoT service, the NEF network element can select the first AIoTF network element through the ADM network element or the NRF network element.
[0148] In some embodiments, if the service request does not carry indication information related to AIoT services, the NEF network element may select the first AIoT network element according to a pre-configured local policy.
[0149] In Event 3, the NEF network element determines the identity of the AIoTF network element as the first network element based on the instruction information, and selects the first AIoTF network element through the ADM network element.
[0150] In some embodiments, the first network element identity can be the AIoTF network element most recently associated with the AIoT terminal targeted by the requested AIoT service. That is, the first AIoTF network element is the "Last known AIoTF" network element.
[0151] In some embodiments, the NEF network element requests the ADM network element to query the network element information of the first AIoTF network element based on the identification information of the AIoT terminal. For example, the NEF network element provides the identification information of the AIoT terminal to the ADM network element to request the ADM network element to query the network element information of the first AIoTF network element.
[0152] In some embodiments, the ADM network element can obtain the network element information of the first AIoTF network element from the UDR network element by providing the identification information of the AIoT terminal to the UDR network element.
[0153] In Event 4, the ADM network element returns the network element information of the first AIoTF network element it queried to the NEF network element.
[0154] In some embodiments, the network element information of the first AIoTF network element returned by the ADM network element may include the ID of the first AIoTF network element. For example, the ADM network element returns the ID of the "Last known AIoTF" obtained from the query to the NEF network element.
[0155] In Event 5, the NEF network element sends a service request for executing AIoT services from the AF network element to the selected first AIoTF network element. For example, the NEF network element sends the service request for executing AIoT services to the "Last known AIoTF" network element based on the ID of the "Last known AIoTF" network element.
[0156] In event 6, the first AIoTF network element returned a response to the NEF network element.
[0157] For example, the first AIoTF network element can return a response to the NEF network element to inform the NEF network element that it has received the service request to execute the AIoT service.
[0158] In Event 7, the first AIoTF network element, in collaboration with the nodes in the AIoT-RAN, executes the AIoT service for the AIoT terminal requesting the AIoT service and obtains the first service result of executing the AIoT service.
[0159] In some embodiments, the first AIoTF network element can forward a service request for executing an AIoT service to the AIoT-RAN node. The AIoT-RAN node selects a suitable radio-side read / write device based on the received service request, and interacts with the AIoT terminal requesting the AIoT service through the radio-side read / write device to execute the AIoT service.
[0160] For example, the wireless side read / write device may include at least one of a base station read / write device (BSReader) or a user equipment read / write device (UEReader).
[0161] In Event 8, the first AIoTF network element notifies the NEF network element of the result of executing the AIoT service. That is, the first AIoTF network element returns the first service result of executing the AIoT service to the NEF network element.
[0162] In Event 9, the NEF network element responded that the first service result was that the AIoT service had failed to be executed at least partially, and determined to reselect a second AIoTF network element to execute the AIoT service.
[0163] In some embodiments, the second AIoTF network element is a “Related AIoTF” network element.
[0164] In Event 10, the NEF network element provides the location information of the AIoT terminal to the NRF network element in order to request the NRF network element to query the network element information of the second AIoTF network element.
[0165] In Event 11, the NRF network element determines the network element information of the second AIoTF network element based on the location information of the AIoT terminal, and returns the network element information of the second AIoTF network element to the NEF network element.
[0166] In some embodiments, the network element information of the second AIoTF network element returned by the NRF network element may include the ID of the second AIoTF network element. For example, the NRF network element returns the ID of the "Related AIoTF" network element obtained from the query to the NEF network element.
[0167] In Event 12, the NEF network element sends the service request for executing AIoT services from the AF network element to the reselected second AIoTF network element.
[0168] For example, the NEF network element sends the service request for executing AIoT services to the "Related AIoTF" network element based on the ID of the "Related AIoTF" network element.
[0169] In event 13, the second AIoTF network element returned a response to the NEF network element.
[0170] For example, the second AIoTF network element can return a response to the NEF network element to inform the NEF network element that it has received the service request to execute the AIoT service.
[0171] In Event 14, the second AIoTF network element, in coordination with the nodes in the AIoT-RAN, executes the AIoT service for the AIoT terminal requesting the AIoT service and obtains the second service result of the execution of the AIoT service.
[0172] In Event 15, the second AIoTF network element notifies the NEF network element of the result of executing the AIoT service. That is, the second AIoTF network element returns the second service result of executing the AIoT service to the NEF network element.
[0173] In Event 16, the NEF network element responded that the second service result was that all AIoT services were successfully executed, and then summarized the results of the second service and the first service. That is, it summarized the results of the two executions of the AIoT service.
[0174] In Event 17, the NEF network element sent the aggregated second service results and first service results to the AF network element.
[0175] It should be understood that after Event 15, if the NEF network element responds to the second service result that the AIoT service has failed to execute at least partially, it will refer to the relevant procedures in Events 9 to 15 to continue to reselect the AIoT network element until the AIoT service is fully executed.
[0176] It should also be understood that the preceding text Figure 1The steps and descriptions in the illustrated embodiments are also applicable to... Figure 2 The wireless communication method shown can be described in the previous embodiments, and will not be repeated here.
[0177] In the above embodiments, on the one hand, the AF network element has the ability to provide indication information, enabling the NEF network element to select the first core network element according to the indication information. On the other hand, local policies can be pre-configured in the NEF network element, enabling the NEF network element to select the first core network element according to the local policies. Thus, the NEF network element can select the first core network element more flexibly to support the efficient and flexible operation of AIoT services.
[0178] The following is combined Figure 3 and Figure 4 The wireless communication method for AIoT proposed in this disclosure is further described.
[0179] Figure 3 A network architecture diagram of a wireless communication system for AIoT according to some embodiments of the present disclosure is shown.
[0180] like Figure 3 As shown, the wireless communication system 300 may include NEF network elements, a first core network element, a second core network element, a third core network element, and a fourth core network element. For example, Figure 3 The diagram schematically shows that the first core network element is an AIoTF network element, the second core network element is an ADM network element, the third core network element is an NRF network element, and the fourth core network element is a UDR network element.
[0181] In some embodiments, the AIoTF network element can provide AIoT terminals with access and service management functions, and is responsible for the management and execution of AIoT services. For example, the AIoTF network element can communicate with other network elements in the core network through the Naiotf interface. For example, the AIoTF network element can receive service requests forwarded by the NEF network element through the Naiotf interface.
[0182] In some embodiments, the ADM network element can be responsible for managing the subscription information and service information of AIoT terminals. In some embodiments, the ADM network element can communicate with other network elements in the core network through the Nadm interface. For example, the ADM network element can communicate with the NEF network element and the UDR network element through the Nadm interface to assist the NEF network element in selecting the AIoT network element.
[0183] In some embodiments, the NRF network element can be responsible for storing the network element information of each first core network element in the core network.
[0184] In some embodiments, the UDR network element may be responsible for storing the identification information of the AIoT terminal targeted by the AIoT service, as well as the identification information of the first core network element (i.e., the "Last known AIoTF" network element) most recently associated with the AIoT terminal.
[0185] In some embodiments, the wireless communication system 300 may further include an AF (Active Front-End) network element. For example, the AF network element, acting as the initiator of an AIoT service, can request the execution of an AIoT service from the core network through the NEF (Non-Active Front-End) network element. The AF network element can provide the identification information and location information of the AIoT terminal targeted by the AIoT service.
[0186] In some embodiments, the AF network element may selectively include indication information related to the AIoT service in the service request sent to the NEF network element to indicate the identity of the AIoTF network element.
[0187] In some embodiments, the wireless communication system 300 may further include an AIoT-RAN node and an AIoT terminal. For example, the AIoT-RAN node selects a suitable wireless-side read / write device based on the service request sent by the AIoTF network element, and interacts with the AIoT terminal requesting the AIoT service through the wireless-side read / write device to execute the AIoT service. For example, the wireless-side read / write device may include at least one of a base station read / write device (BS Reader) or a user equipment read / write device (UE Reader).
[0188] based on Figure 3 The wireless communication system 300 shown can perform Figure 4 The wireless communication method for AIoT is shown.
[0189] Figure 4 Schematic diagrams are shown illustrating wireless communication methods for AIoT according to some embodiments of the present disclosure. For example, Figure 4 The diagram schematically shows that the first core network element is the first AIoTF network element, and the other first core network elements are the second AIoTF network elements.
[0190] like Figure 4 As shown, in event 0, the AF network element initiates a service request to execute an AIoT service. For example, the AF network element may selectively include indication information related to the AIoT service in the service request to indicate the identity of the first AIoT AF network element.
[0191] In Event 1, the NEF network element responded to the service request by including the indication information, and determined the identity of the first AIoTF network element based on this indication information. For example, the first network element identity is "Last known AIoTF" network element.
[0192] In Event 2, the NEF network element queries the network element information of the first AIoTF network element through the ADM network element.
[0193] For example, the NEF network element provides the identification information of the AIoT terminal to the ADM network element. Based on this identification information, the ADM network element requests the UDR network element to query the network element information of the first AIoTF network element. The ADM network element then returns the network element information of the first AIoTF network element obtained through the UDR network element query to the NEF network element.
[0194] In Event 3, the NEF network element forwards a service request to the first AIoTF network element, requesting the first AIoTF network element to execute the AIoT service.
[0195] In Event 4, the first AIoTF network element, in collaboration with the AIoT-RAN node, executes the AIoT service for the AIoT terminal requesting the AIoT service and obtains the first service result of executing the AIoT service.
[0196] For example, the AIoT-RAN node selects a suitable base station reader (BSReader) or user equipment reader (UEReader) based on the service request sent by the AIoTF network element, and interacts with the AIoT terminal requesting the AIoT service through the base station reader (BSReader) or user equipment reader (UEReader) to execute the AIoT service.
[0197] For example, the first business outcome is that the AIoT business has failed at least partially.
[0198] In Event 5, the NEF network element, responding to the first service result indicating that the AIoT service had at least partially failed, queries the network element information of the second AIoTF network element through the NRF network element. For example, the second AIoTF network element is the "Related AIoTF" network element.
[0199] For example, the NEF network element provides the location information of the AIoT terminal to the NRF network element. The NRF network element then queries the network element information of the second AIoTF network element based on this location information and returns the retrieved network element information of the second AIoTF network element to the NEF network element.
[0200] In Event 6, the NEF network element forwarded a service request to the second AIoTF network element, requesting the second AIoTF network element to execute the AIoT service.
[0201] In Event 7, the second AIoTF network element, in collaboration with the AIoT-RAN node, executes the AIoT service for the AIoT terminal requesting the AIoT service and obtains the second service result of executing the AIoT service (i.e., obtains the data returned by the AIoT-RAN node).
[0202] For example, the second business result is that the entire AIoT business was successfully executed.
[0203] although Figure 4 Although not shown, it is understood that the NEF network element, in response to the second service result indicating that the AIoT service has been successfully executed, can return the second service result and the first service result to the AF network element.
[0204] It is also understandable that the preceding text Figure 1 and Figure 2 The steps and descriptions in the illustrated embodiments are also applicable to... Figure 4 The wireless communication method shown can be described in the previous embodiments, and will not be repeated here.
[0205] Figure 5 A flowchart illustrating a wireless communication method for AIoT according to other embodiments of this disclosure is shown. Figure 5 As shown, the wireless communication method for AIoT is executed by an AIoT terminal and includes at least one of steps 510 to 520.
[0206] In step 510, AIoT services are executed via the wireless side read / write device.
[0207] Here, the wireless read / write device is selected by the nodes in the AIoT-RAN based on the received service request for executing AIoT services. This service request is forwarded by the NEF network element to the transmitting AIoT-RAN node via the first core network element, which is selected by the NEF network element.
[0208] In step 520, the first service result of the AIoT service is sent to the first core network element through the wireless side read / write device, so that the first core network element can return the first service result to the NEF network element.
[0209] For details regarding wireless side-reading devices, AIoT-RAN nodes, and the collaboration between AIoT-RAN nodes and wireless side-reading devices in performing AIoT services, please refer to the preceding text. Figures 1 to 4 The descriptions in the relevant embodiments shown will not be repeated here.
[0210] In the above embodiments, the NEF network element in the core network has the ability to receive and process service requests for executing AIoT services, and to select a suitable first core network element from the core network to complete the requested AIoT service. Thus, the core network can provide flexible and efficient support for the smooth execution of AIoT services. In this way, the AIoT terminal executes AIoT services through the first core network element selected by the NEF network element, effectively improving the efficiency of AIoT service processing.
[0211] In some embodiments, the service request to execute an AIoT service originates from an AF network element, and this service request carries indication information related to the AIoT service. The first core network element is selected by the NEF network element based on this indication information.
[0212] In some embodiments, the first core network element is determined by the NEF network element based on the instruction information, and then selected by the second core network element.
[0213] In some embodiments, the first network element is the first core network element most recently associated with the AIoT terminal targeted by the AIoT service, and the second core network element is the ADM network element.
[0214] In some embodiments, the indication information indicates that the service type of the AIoT service is a continuous service. The NEF network element determines the identity of the first core network element as the first network element identity based on the indication information.
[0215] In some embodiments, the indication information indicates that the AIoT terminal targeted by the AIoT service has been registered in the core network and that the movement range of the AIoT terminal has not exceeded a specified range. The NEF network element determines the identity of the first core network element as the first network element identity based on the indication information.
[0216] In some embodiments, the service request for executing an AIoT service carries identification information of the AIoT terminal to which the AIoT service is targeted.
[0217] The first core network element is selected by the NEF network element by performing the following steps: the NEF network element provides the identification information to the second core network element to request the second core network element to query the network element information of the first core network element; the NEF network element receives the network element information of the first core network element obtained by querying the identification information from the second core network element.
[0218] In some embodiments, the first core network element is determined by the NEF network element to be the second network element based on the instruction information, and then selected by the third core network element.
[0219] In some embodiments, the second network element is a first core network element that is not most recently associated with the AIoT terminal targeted by the AIoT service, and the third core network element is an NRF network element.
[0220] In some embodiments, the indication information indicates that the AIoT service is a new service or a discontinuous service. The NEF network element determines the identity of the first core network element as the second network element based on the indication information.
[0221] In some embodiments, the indication information indicates that the AIoT terminal targeted by the AIoT service has not been registered in the core network. The NEF network element determines the identity of the first core network element as the identity of the second network element based on the indication information.
[0222] In some embodiments, the indication information indicates that the AIoT terminal targeted by the AIoT service has been registered in the core network and that the mobile range of the AIoT terminal exceeds a specified range. The NEF network element determines the identity of the first core network element as the identity of the second network element based on the indication information.
[0223] In some embodiments, the service request for executing an AIoT service carries the location information of the AIoT terminal targeted by the AIoT service.
[0224] The first core network element is selected by the NEF network element by performing the following steps: the NEF network element provides location information to the third core network element to request the third core network element to query the network element information of the first core network element; the NEF network element receives the network element information of the first core network element determined based on the location information returned by the third core network element.
[0225] In some embodiments, the service request to execute an AIoT service originates from an AF network element, and this service request does not carry any indication information related to the AIoT service. The first core network element is selected by the NEF network element based on a local policy pre-configured according to the subscription information of the AIoT service.
[0226] In some embodiments, the first service result is sent by the NEF network element in response to the first service result indicating that all AIoT services have been successfully executed. For example, the first service result is sent by the NEF network element to the AF network element in response to the first service result indicating that all AIoT services have been successfully executed.
[0227] In some embodiments, the AIoT terminal executes AIoT services again via other wireless-side read / write devices. Here, the other wireless-side read / write devices are selected by the AIoT-RAN node based on the received service request to execute the AIoT service. This service request is sent by the NEF network element through other first core network elements, which are reselected by the NEF network element based on the result of the first service.
[0228] In some embodiments, the other first core network element is reselected by the NEF network element in response to at least a partial failure of the first service result.
[0229] In some embodiments, the wireless side-reading device may be the same as or different from other wireless side-reading devices.
[0230] In some embodiments, the other first core network element is reselected by the NEF network element in response to the first service result being that the AIoT service has at least partially failed to execute.
[0231] In some embodiments, the AIoT terminal sends the second service result of the AIoT service to other first core network elements through other wireless side read / write devices, so that the other first core network elements can return the second service result to the NEF network element.
[0232] In some embodiments, the first service result and the second service result are sent by the NEF network element in response to the second service result indicating that all AIoT services have been successfully executed. For example, the first service result and the second service result are sent by the NEF network element to the AF network element in response to the second service result indicating that all AIoT services have been successfully executed.
[0233] It should be understood that the relevant steps in the wireless communication method performed by the NEF network elements on the core network side are also applicable to the wireless communication method performed by the AIoT terminal on the terminal side. For relevant explanations, please refer to the preceding text. Figures 1 to 4 The descriptions in the relevant embodiments will not be repeated here.
[0234] Figure 6 A block diagram of a NEF network element according to some embodiments of the present disclosure is shown.
[0235] like Figure 6 As shown, the NEF network element 600 may include one or more modules selected from the first receiving module 601, the selection module 602, the transmitting module 603, and the second receiving module 604.
[0236] The first receiving module 601 can be configured to receive service requests for executing passive Internet of Things (AIoT) services.
[0237] The selection module 602 can be configured to select the first core network element.
[0238] The sending module 603 can be configured to forward service requests to the first core network element.
[0239] The second receiving module 604 can be configured to receive the first service result of executing AIoT services returned by the first core network element.
[0240] In some embodiments, the NEF network element 600 can also be used to perform the aforementioned... Figures 1 to 4 Other operations in the illustrated embodiments.
[0241] In some embodiments, the NEF network element 600 may further include the execution of the aforementioned... Figures 1 to 4 Other modules of other operations in the illustrated embodiments.
[0242] Figure 7 A block diagram of an AIoT terminal according to some embodiments of the present disclosure is shown.
[0243] like Figure 7 As shown, the AIoT terminal 700 includes at least one of the execution module 701 and the transmission module 702.
[0244] The execution module 701 can be configured to execute passive IoT (AIoT) services via a wireless-side read / write device. Here, the wireless-side read / write device is selected by the AIoT wireless access network node based on a received service request to execute the AIoT service. This service request is forwarded to the AIoT wireless access network node by the Network Open Function (NEF) element via a first core network element, which is selected by the NEF element.
[0245] The sending module 702 can be configured to send the first service result of the AIoT service to the first core network element through the wireless side read / write device, so that the first core network element can return the first service result to the NEF network element.
[0246] In some embodiments, the AIoT terminal 700 can also be used to perform the aforementioned... Figure 5 Other operations in the illustrated embodiments.
[0247] In some embodiments, the AIoT terminal 700 may further include the execution of the foregoing description. Figure 5 Other modules of other operations in the illustrated embodiments.
[0248] Figure 8 A block diagram of an electronic device according to some embodiments of the present disclosure is shown.
[0249] like Figure 8 As shown, the electronic device 800 of this embodiment includes a memory 801 and a processor 802 coupled to the memory 801. The processor 802 is configured to execute the method in any embodiment of this disclosure based on instructions stored in the memory 801.
[0250] The memory 801 may include, for example, system memory, fixed non-volatile storage media, etc. The system memory may store, for example, an operating system, application programs, a boot loader, a database, and other programs.
[0251] In some embodiments, the electronic device 800 can function as a NEF network element performing the operations of any of the above embodiments. In other embodiments, the electronic device 800 can function as an AIoT terminal performing the operations of any of the above embodiments.
[0252] Figure 9 Block diagrams of electronic devices according to other embodiments of the present disclosure are shown.
[0253] like Figure 9 As shown, the electronic device 900 of this embodiment includes a memory 901 and a processor 902 coupled to the memory 901. The processor 902 is configured to execute the method in any of the foregoing embodiments based on instructions stored in the memory 901.
[0254] The memory 901 may include, for example, system memory, fixed non-volatile storage media, etc. The system memory stores, for example, the operating system, application programs, boot loader, and other programs.
[0255] The electronic device 900 may also include an input / output interface 903, a network interface 904, and a storage interface 905. These interfaces 903, 904, and 905, as well as the memory 901 and processor 902, can be connected, for example, via a bus 906. The input / output interface 903 provides a connection interface for input / output devices such as monitors, mice, keyboards, touchscreens, microphones, and speakers. The network interface 904 provides a connection interface for various networked devices. The storage interface 905 provides a connection interface for external storage devices such as SD cards and USB flash drives.
[0256] In some embodiments, the electronic device 900 can function as a NEF network element performing the operations of any of the above embodiments. In other embodiments, the electronic device 900 can function as an AIoT terminal performing the operations of any of the above embodiments.
[0257] Figure 10 A block diagram of a wireless communication system according to some embodiments of the present disclosure is shown.
[0258] like Figure 10 As shown, the wireless communication system 1000 includes a NEF network element 1001 and an AIoT terminal 1002. For example, the NEF network element 1001 can be a NEF network element 600 / 800 / 900. For example, the AIoT terminal 1002 can be an AIoT terminal 700 / 800 / 900.
[0259] In some embodiments, the wireless communication system 1000 may further include a first core network element 1003. The first core network element 1003 may be configured to receive a service request for executing AIoT services sent by the NEF network element 1001, and return a first service result of executing the AIoT services to the NEF network element 1001.
[0260] In some embodiments, the wireless communication system 1000 may also include other network elements and devices as described in the relevant embodiments above, which will not be detailed here.
[0261] This disclosure also provides a computer-readable storage medium including computer program instructions that, when executed by a processor, implement the wireless communication method of any of the above embodiments.
[0262] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the wireless communication method of any of the above embodiments.
[0263] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0264] This concludes the detailed description of the wireless communication technology solution for AIoT according to this disclosure. To avoid obscuring the concept of this disclosure, some details known in the art have not been described. Those skilled in the art can fully understand how to implement the technical solutions disclosed herein based on the above description.
[0265] The methods and systems of this disclosure may be implemented in many ways. For example, they may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order of steps for the methods is for illustrative purposes only, and the steps of the methods of this disclosure are not limited to the specific order described above unless otherwise specifically stated. Furthermore, in some embodiments, this disclosure may also be implemented as a program recorded on a recording medium, the program including machine-readable instructions for implementing the methods according to this disclosure. Thus, this disclosure also covers recording media storing programs for performing the methods according to this disclosure.
[0266] While specific embodiments of this disclosure have been described in detail by way of example, those skilled in the art should understand that the examples are for illustrative purposes only and not intended to limit the scope of this disclosure. Those skilled in the art should understand that modifications can be made to the above embodiments without departing from the scope and spirit of this disclosure. The scope of this disclosure is defined by the appended claims.
Claims
1. A wireless communication method, executed by a Network Open Function (NEF) element, comprising: Receive business requests for executing passive Internet of Things (AIoT) services; Select the first core network element; Forward the service request to the first core network element; Receive the first service result of executing the AIoT service returned by the first core network element.
2. The wireless communication method according to claim 1, wherein, The service request originates from the application function (AF) network element, and carries indication information related to the AIoT service. The selection of the first core network element includes: Select the first core network element according to the instruction information.
3. The wireless communication method according to claim 2, wherein, The step of selecting the first core network element according to the indication information includes: The identity of the first core network element is determined as the first network element identity based on the indicated information; and The first core network element is selected by the second core network element.
4. The wireless communication method according to claim 3, wherein, The first network element is the first core network element most recently associated with the AIoT terminal targeted by the AIoT service, and the second core network element is the passive IoT data management function (ADM) network element.
5. The wireless communication method according to claim 4, wherein, The indication information indicates that the service type of the AIoT service is a continuous service.
6. The wireless communication method according to claim 4, wherein, The indication information indicates that the AIoT terminal targeted by the AIoT service has been registered in the core network and that the movement range of the AIoT terminal has not exceeded the specified range.
7. The wireless communication method according to claim 4, wherein, The service request carries the identification information of the AIoT terminal to which the AIoT service is targeted. The step of selecting the first core network element through the second core network element includes: The identification information is provided to the second core network element to request the second core network element to query the network element information of the first core network element; Receive network element information of the first core network element returned by the second core network element, which is obtained by querying the identification information.
8. The wireless communication method according to claim 2, wherein, The step of selecting the first core network element according to the indication information includes: Based on the indicated information, the identity of the first core network element is determined to be the identity of the second network element; and The first core network element is selected by the third core network element.
9. The wireless communication method according to claim 8, wherein, The second network element is a first core network element that is not most recently associated with the AIoT terminal targeted by the AIoT service, and the third core network element is a network warehousing function (NRF) network element.
10. The wireless communication method according to claim 9, wherein, The indication information indicates whether the AIoT service is a new service or a non-continuous service.
11. The wireless communication method according to claim 9, wherein, The indication information indicates that the AIoT terminal targeted by the AIoT service has not been registered on the core network.
12. The wireless communication method according to claim 9, wherein, The indication information indicates that the AIoT terminal targeted by the AIoT service has been registered in the core network and that the mobile range of the AIoT terminal exceeds the specified range.
13. The wireless communication method according to claim 9, wherein, The service request carries the location information of the AIoT terminal. The step of selecting the first core network element through the third core network element includes: The location information is provided to the third core network element to request the third core network element to query the network element information of the first core network element; Receive network element information of the first core network element, determined based on the location information, returned by the third core network element.
14. The wireless communication method according to claim 1, wherein, The service request originates from the AF network element, and the service request does not carry any indication information related to the AIoT service. The selection of the first core network element includes: The first core network element is selected based on a local policy pre-configured according to the subscription information of the AIoT service.
15. The wireless communication method according to any one of claims 1-14, further comprising: Based on the results of the first service, determine whether to reselect another first core network element for executing the AIoT service.
16. The wireless communication method according to claim 15, wherein, The step of determining whether to reselect other first core network elements for executing the AIoT service based on the first service result includes: In response to the first service result indicating that the AIoT service has at least partially failed to execute, the other first core network elements are reselected through the third core network element.
17. The wireless communication method according to claim 16, further comprising: After reselecting the other first core network element, the service request is forwarded to the other first core network element; Receive the second service result of the AIoT service returned by the other first core network elements; In response to the second service result indicating that all AIoT services have been successfully executed, the first service result and the second service result are sent.
18. The wireless communication method according to claim 15, wherein, The step of determining whether to reselect other first core network elements for executing the AIoT service based on the first service result includes: In response to the first service result indicating that all AIoT services have been successfully executed, it is determined not to reselect the other first core network elements, and the first service result is sent back.
19. A wireless communication method, performed by a passive Internet of Things (AIoT) terminal, comprising: AIoT services are executed through a wireless side read / write device. The wireless side read / write device is selected by the AIoT wireless access network node based on the received service request to execute the AIoT service. The service request is forwarded to the AIoT wireless access network node by the Network Open Function (NEF) network element via the first core network element. The first core network element is selected by the NEF network element. The wireless side read / write device sends the first service result of the AIoT service to the first core network element, so that the first core network element returns the first service result to the NEF network element.
20. A network open function element, comprising: The first receiving module is configured to receive service requests for executing passive Internet of Things (AIoT) services. The selection module is configured to select the first core network element. The sending module is configured to forward the service request to the first core network element; The second receiving module is configured to receive the first service result of executing the AIoT service returned by the first core network element.
21. A passive Internet of Things (IoT) terminal, comprising: The execution module is configured to execute passive IoT AIoT services through a wireless side read / write device. The wireless side read / write device is selected by the AIoT wireless access network node according to the received service request to execute the AIoT service. The service request is forwarded from the NEF network element to the AIoT wireless access network node via a first core network element. The first core network element is selected by the NEF network element. The sending module is configured to send the first service result of the AIoT service to the first core network element through the wireless side read / write device, so that the first core network element returns the first service result to the NEF network element.
22. An electronic device, comprising: Memory; and A processor coupled to the memory, the processor being configured to execute the wireless communication method of any one of claims 1-18, or the wireless communication method of claim 19, based on instructions stored in the memory.
23. A wireless communication system, comprising: The Network Open Function (NEF) network element is configured to perform the wireless communication method described in any one of 1-18; as well as A passive Internet of Things (AIoT) terminal is configured to perform the wireless communication method of claim 19.
24. The wireless communication system according to claim 23, further comprising: The first core network element is configured to receive a service request for executing AIoT services sent by the NEF network element, and return the first service result of executing the AIoT services to the NEF network element.
25. A computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the wireless communication method of any one of claims 1-18, or the wireless communication method of claim 19.
26. A computer program product comprising instructions that, when executed by a processor, cause the processor to perform the wireless communication method of any one of claims 1-18, or to perform the wireless communication method of claim 19.
