Service control method, terminal device, and network device

Abstract

The present application relates to a service control method, a terminal device, and a network device. The method comprises: a terminal device executes a first service on the basis of identification information corresponding to the first service, wherein the identification information is determined on the basis of feature information of the first service and authorization information of the terminal device, and the authorization information comprises the feature information of the first service allowed to be executed by the terminal device and the identification information corresponding to the first service. The present application can improve the effect of AIoT service operations.

Description

Business control methods, terminal equipment and network equipment Technical Field

[0001] This application relates to the field of communications, and more specifically, to service control methods, terminal equipment, and network equipment. Background Technology

[0002] In existing technologies, Ambient Power-enabled Internet of Things (AIoT) devices can access 5G networks. AIoT devices access 5G networks in various ways, such as direct connection and non-direct connection. In the non-direct connection method, AIoT devices access the network through an intermediate node, which can include User Equipment (UE). How to achieve differentiated control of Ambient IoT readers in the non-direct connection method to improve the efficiency of AIoT service operations is a technical problem that needs to be solved.

[0003] Summary of the Invention

[0004] This application provides a service control method, a terminal device, and a network device.

[0005] This application provides a business control method, including:

[0006] The terminal device executes the first service based on the identification information corresponding to the first service; wherein,

[0007] The identification information is determined based on the feature information of the first service and the authorization information of the terminal device. The authorization information includes the feature information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

[0008] This application provides a business control method, including:

[0009] The first network element determines the terminal device that performs the first service based on the feature information of the first service and the authorization information of the terminal device; the authorization information includes the feature information of the first service that the terminal device is allowed to perform.

[0010] The first network element sends a message to instruct the terminal device to perform the first service.

[0011] This application provides a business control method, including:

[0012] The second network element sends a management terminal device policy command message. The management terminal device policy command message carries the authorization information of the terminal device. The authorization information includes the characteristic information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

[0013] This application provides a terminal device, including:

[0014] The first processing module is used to execute the first service based on the identification information corresponding to the first service; wherein,

[0015] The identification information is determined based on the feature information of the first service and the authorization information of the terminal device. The authorization information includes the feature information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

[0016] This application provides a first network element, including:

[0017] The second processing module is used to determine the terminal device that performs the first service based on the feature information of the first service and the authorization information of the terminal device; the authorization information includes the feature information of the first service that the terminal device is allowed to perform.

[0018] The second transceiver module is used to send messages that instruct the terminal device to perform the first service.

[0019] This application provides a second network element, including:

[0020] The third transceiver module is used to send management terminal device policy command messages. The management terminal device policy command messages carry the authorization information of the terminal device. The authorization information includes the feature information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

[0021] This application provides a terminal device, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to enable the terminal device to perform the aforementioned service control method.

[0022] This application provides a network device, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to enable the network device to perform the aforementioned service control method.

[0023] This application provides a chip for implementing the above-described business control method.

[0024] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the aforementioned business control method.

[0025] This application provides a computer-readable storage medium for storing a computer program, which, when run by a device, causes the device to perform the aforementioned business control method.

[0026] This application provides a computer program product, including computer program instructions, which cause a computer to execute the above-described business control method.

[0027] This application provides a computer program that, when run on a computer, causes the computer to execute the above-described business control method.

[0028] In this embodiment of the application, when a terminal device (UE) performs AIoT service operations, it can perform them based on corresponding identification information. That is, different identification information is used for different AIoT service operations, thereby making AIoT service operations more efficient. Attached Figure Description

[0029] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application.

[0030] Figure 2A is a schematic diagram of the 5G network architecture.

[0031] Figure 2B is a schematic diagram of the basic principle of Ambient IoT communication.

[0032] Figure 3A is a schematic diagram of an Ambient IoT device connecting to a 5G network via a direct connection method.

[0033] Figure 3B is a schematic diagram of an Ambient IoT device accessing a 5G network using a non-direct connection method.

[0034] Figure 4 is a schematic flowchart of a business control method 400 according to an embodiment of this application.

[0035] Figure 5 is a schematic flowchart of a business control method 500 according to an embodiment of this application.

[0036] Figure 6 is a schematic flowchart of a business control method 600 according to an embodiment of this application.

[0037] Figure 7A is a flowchart of the first implementation of Embodiment 1 of this application.

[0038] Figure 7B is a flowchart of the second implementation of Embodiment 1 of this application.

[0039] Figure 8A is a flowchart of the first implementation method of Embodiment 2 of this application.

[0040] Figure 8B is a flowchart of the second implementation of Embodiment 2 of this application.

[0041] Figure 9 is a schematic block diagram of a terminal device 900 according to an embodiment of the present application.

[0042] Figure 10 is a schematic block diagram of a terminal device 1000 according to an embodiment of this application.

[0043] Figure 11 is a schematic block diagram of a first network element 1100 according to an embodiment of this application.

[0044] Figure 12 is a schematic block diagram of a second network element 1200 according to an embodiment of the present application.

[0045] Figure 13 is a schematic structural diagram of a communication device 1300 according to an embodiment of this application.

[0046] Figure 14 is a schematic structural diagram of a chip 1400 according to an embodiment of this application. Detailed Implementation

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

[0048] The technical solutions of this application embodiment can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, Advanced Long Term Evolution (LTE-A) systems, New Radio (NR) systems, evolution systems of NR systems, LTE-based access to unlicensed spectrum (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, Non-Terrestrial Networks (NTN) systems, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th-Generation (5G) systems, or other communication systems.

[0049] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.

[0050] In one implementation, the communication system in this application embodiment can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) network deployment scenario.

[0051] In one embodiment, the communication system in this application can be applied to unlicensed spectrum, wherein the unlicensed spectrum can also be considered as shared spectrum; or, the communication system in this application can also be applied to licensed spectrum, wherein the licensed spectrum can also be considered as non-shared spectrum.

[0052] This application describes various embodiments in conjunction with network devices and terminal devices. The terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc.

[0053] Terminal devices can be stations (STAION, ST) in WLANs, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in next-generation communication systems such as NR networks, or terminal devices in future evolved Public Land Mobile Network (PLMN) networks, etc.

[0054] In the embodiments of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (such as airplanes, balloons and satellites).

[0055] In the embodiments of this application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical care, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

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

[0057] In the embodiments of this application, the network device can be a device for communicating with mobile devices, such as an access point (AP) in a WLAN, an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or an NTN network, etc.

[0058] By way of example and not limitation, in this embodiment, the network device may have mobility characteristics; for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station located on land, water, or other similar locations.

[0059] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0060] Figure 1 illustrates an exemplary communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and the coverage area of ​​each network device 110 may include other numbers of terminal devices 120; this embodiment does not limit the scope of the present application.

[0061] In one embodiment, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which are not limited in this application.

[0062] Network equipment can be further divided into access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks used to communicate with the access network equipment. Access network equipment can be evolved Node Bs (eNBs or e-NodeBs) in Long-Term Evolution (LTE), Next-Generation Radio (NR) (mobile communication system), or Authorized Auxiliary Access Long-Term Evolution (LAA-LTE) systems, such as macro base stations, micro base stations (also called "small base stations"), pico base stations, access points (APs), transmission points (TPs), or new generation Node Bs (gNodeBs).

[0063] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Taking the communication system shown in Figure 1 as an example, the communication device may include network devices and terminal devices with communication functions. The network devices and terminal devices can be specific devices in this application embodiment, which will not be described in detail here. The communication device may also include other devices in the communication system, such as network controllers, mobility management entities, and other network entities. This application embodiment does not limit this.

[0064] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0065] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0066] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0067] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0068] Passive Internet of Things (Ambient IoT, AIoT) networks are a type of wireless communication technology suitable for short-range, low-data-rate communication. Ambient IoT devices (AIoT devices) mainly combine radio frequency energy harvesting technology, backscattering technology, and low-power computing technology to achieve the advantage of device nodes not carrying a power supply.

[0069] The core of radio frequency energy harvesting is to convert radio frequency energy into direct current. The energy can be stored in batteries or capacitors, or it can be directly used to drive logic circuits, digital chips or sensors to complete functions and applications such as modulation and transmission of backscattered signals, and acquisition and processing of sensing information.

[0070] Figure 2A is a schematic diagram of the 5G architecture. The UE connects to the Access Network (AN) via the Uu interface to establish an access layer connection, exchanging access layer messages and radio data. The UE connects to the Access and Mobility Management Function (AMF) via the N1 interface to establish a non-access layer (NAS) connection, exchanging NAS messages. The AMF (Access and Mobility Management Function) is the mobility management function in the core network, and the SMF (Session Management Function) is the session management function in the core network. In addition to managing the UE's mobility, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. The PCF (Policy Control Function) is the policy management function in the core network, responsible for formulating policies related to UE mobility management, session management, and charging. The UPF (User Plane Function) is the user plane function in the core network, transmitting data with the external data network via the N6 interface and with the AN via the N3 interface.

[0071] With the development of 5G systems, the 3GPP standard has included the requirement for 5G systems to support Ambient IoT terminal access to the network. The main scenarios targeted have the following characteristics:

[0072] - The environment is extreme and not suitable for ordinary terminals to work in;

[0073] -Use terminals with very low power consumption and cost;

[0074] - Battery-free terminal.

[0075] Ambient IoT communication systems can be used in scenarios such as wireless industrial sensing networks, smart agriculture, smart warehousing and logistics, and smart homes.

[0076] Based on the energy source and usage method of Ambient IoT terminals, Ambient IoT terminals can be divided into the following types:

[0077] (1) Passive Ambient IoT Terminal:

[0078] Passive Ambient IoT terminals do not require an internal battery. When a passive Ambient IoT terminal is near a network device (such as a reader in a Radio Frequency Identification (RFID) system), it falls within the near-field range radiated by the network device's antenna. Therefore, the passive Ambient IoT terminal's antenna generates an induced current through electromagnetic induction, which drives the terminal's low-power chip circuitry. This enables demodulation of the forward link signal and modulation of the backward link signal. For the backscatter link, the passive Ambient IoT terminal uses backscattering to transmit signals.

[0079] It can be seen that the passive Ambient IoT terminal does not require a built-in battery to drive either the forward or reverse link, making it a true Ambient IoT terminal.

[0080] Passive Ambient IoT terminals do not require batteries, and their RF and baseband circuits are very simple. For example, they do not require LNA (low noise amplifier), PA (power amplifier), crystal oscillator, ADC, etc. Therefore, they have many advantages such as small size, light weight, very low price, and long service life.

[0081] This type of terminal device can also be characterized by: 1) no battery; 2) obtaining energy from the surrounding environment (such as radio waves, solar energy, wind energy, mechanical energy, etc.); 3) no USIM card. It can also store some energy from the surrounding environment, but the amount of energy is very small, so it supports far fewer functional logics than ordinary mobile phone terminals.

[0082] (2) Semi-passive Ambient IoT terminal

[0083] Semi-passive Ambient IoT terminals do not have conventional batteries installed, but they can use RF energy harvesting modules to collect radio wave energy and store it in an energy storage unit (such as a capacitor). Once the energy storage unit receives energy, it can drive the low-power chip circuitry of the semi-passive Ambient IoT terminal, enabling demodulation of forward link signals and modulation of backward link signals. For the backscatter link, the Ambient IoT terminal uses backscattering to transmit signals.

[0084] It can be seen that the semi-passive Ambient IoT terminal does not require a built-in battery to drive either the forward or reverse link. Although it uses energy stored in a capacitor during operation, the energy comes from the radio energy collected by the energy harvesting module, thus making it a true Ambient IoT terminal.

[0085] Semi-passive Ambient IoT terminals inherit many advantages from passive Ambient IoT terminals, thus possessing advantages such as small size, light weight, very low price, and long service life.

[0086] (3) Active Ambient IoT Terminal

[0087] In some scenarios, the Ambient IoT terminals used can also be active Ambient IoT terminals, which can have a built-in battery. The battery powers the low-power chip circuitry of the active Ambient IoT terminal, enabling demodulation of the forward link signal and modulation of the backward link signal. However, for the backscatter link, the active Ambient IoT terminal uses backscattering to transmit signals. Therefore, the Ambient IoT feature of this type of terminal is that the signal transmission in the backward link does not require the terminal's own power, but instead uses backscattering.

[0088] Active Ambient IoT terminals have built-in batteries that power RFID chips, increasing tag read / write distance and improving communication reliability. Therefore, they are used in scenarios with relatively high requirements for communication distance and read latency. These Ambient IoT terminals can be tags or ordinary devices.

[0089] Figure 2A is a schematic diagram of the basic principle of Ambient IoT communication. In an RFID system, a reader is a device that reads information from or writes information to electronic tags. When the RFID system is working, the reader transmits radio frequency energy to form an electromagnetic field within a certain area; the size of the area depends on the transmission power. Electronic tags within the reader's coverage area are triggered, sending the data stored within them or modifying the data stored within them according to the reader's instructions. The reader communicates with the electronic tags wirelessly in a non-contact, two-way manner, reading and writing data to achieve target identification and data exchange. Electronic tags generally consume little power and may not even require a power source or battery. For example, passive electronic tags can receive microwave signals transmitted from the reader and obtain energy through an electromagnetic induction coil to power themselves briefly, thus completing information exchange. RFID has a relatively short transmission range and is used for local management and communication of goods, such as warehouse inventory management, record management, access card management, and electronic toll payment on highways.

[0090] The design of novel electronic tags, known as passive IoT tags or ambient IoT tags, is also being considered in 3GPP networks. Unlike RFID, these electronic tags can communicate using the frequency resources of the 3GPP network. The electronic tags in this application include, but are not limited to, RFID tags, passive IoT tags, and ambient IoT tags.

[0091] Current electronic tags are used for local management and communication of goods. The distance between passive electronic tags and readers is generally about 1 meter, while the distance between active electronic tags and readers is about 100 meters. Therefore, it is inconvenient to remotely read, write, or inventory electronic tags, which limits the application scenarios of electronic tags.

[0092] In related technologies, several different access methods are provided for Ambient IoT devices to access 5G networks, including direct connection and non-direct connection methods. Figure 3A is a schematic diagram of an Ambient IoT device accessing a 5G network using the direct connection method, in which the Ambient IoT device directly connects to the wireless network. Figure 3B is a schematic diagram of an Ambient IoT device accessing a 5G network using the non-direct connection method, in which the Ambient IoT device accesses the wireless network through an intermediate node, which can be a UE (User Equipment). The non-direct connection method has the following advantages over the direct connection method: it can reduce the impact on existing 3GPP standards; and it can extend the coverage area. In the non-direct connection method, how to achieve differentiated control of the Ambient IoT reader to improve the efficiency of AIoT service operations is a technical problem that needs to be solved.

[0093] Figure 4 is a schematic flowchart of a business control method 400 according to an embodiment of this application. This method can optionally be applied to the systems shown in Figures 1, 2A, 2B, or 3B, but is not limited thereto. The method includes at least a portion of the following:

[0094] S410. The terminal device executes the first service based on the identification information corresponding to the first service.

[0095] The identification information is determined based on the feature information of the first service and the authorization information of the terminal device. The authorization information includes the feature information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

[0096] The first service may include AIoT services or AIoT service operations. For example, AIoT services or AIoT service operations may include inventory operations or command operations.

[0097] In some implementations, the characteristic information of the first service includes at least one of the following:

[0098] (1) Business attributes;

[0099] (2) Time period information;

[0100] (3) Regional information.

[0101] The business attributes may include at least one of the following: business provider information, business identifier, and application identifier.

[0102] For example, service provider information includes a service ID.

[0103] For example, the service identifier includes at least one of Single Network Slice Selection Assistance Information (S-NSSAI) and Data Network Name (DNN).

[0104] For example, application identifiers include Application ID or Application Function ID (AF ID).

[0105] The regional information may include at least one of the following: community information, tracking area information, and geographic location information.

[0106] For example, cell information includes the cell ID.

[0107] For example, tracking area information includes tracking area ID or tracking area code.

[0108] For example, geographic location information includes geographic region information.

[0109] For example, the identification information corresponding to the first service may include the reader ID.

[0110] The authorization information of the terminal device may include the characteristic information of the first service that the terminal is allowed to perform, and the identification information corresponding to the first service.

[0111] For example, the authorization information of a certain terminal device A is shown in Table 1 below:

[0112] Table 1

[0113] In Table 1 above, rows two through four contain the characteristic information of the first service that terminal device A is allowed to perform, and row one contains the identification information corresponding to that first service. Different terminal devices may use the same or different identification information for the first service when performing the same first service with the same characteristic information. For example, as shown in Table 1, when terminal device A performs the first service specified in rows two through four of Table 1, the identification information corresponding to that first service is Reader ID a. Other terminal devices may use different identification information when performing the same first service; for example, terminal device B may use Reader ID b when performing the first service.

[0114] In some implementations, when a terminal device receives a request for a first service, it can determine whether to execute the first service and the corresponding identification information (that is, the identification information used by the terminal device when executing the first service) based on the feature information of the first service and the authorization information of the terminal device.

[0115] Alternatively, in other embodiments, the network device can determine whether the terminal device is executing the first service and the corresponding identification information based on the characteristic information of the first service and the authorization information of the terminal device, and send the identification information to the terminal device if the terminal device is executing the first service. For example, before step S410, the terminal device receives the identification information corresponding to the first service sent by the first network element. The first network element may include an AMF (Advanced Feature Filter).

[0116] The authorization information for the terminal device can be pre-configured or sent to the terminal device by the network device.

[0117] For example, the method described above also includes the terminal device receiving authorization information. This authorization information is the authorization information for the terminal device itself.

[0118] In some examples, the terminal device receives the authorization information by receiving a registration acceptance message sent by a first network element, which carries the authorization information. The first network element may include an AMF (Advanced Management Function).

[0119] For example, a terminal device can send a registration request message to the AMF. The AMF obtains the terminal device's subscription data from network elements such as the UDM, and returns a registration receipt message to the terminal device based on the subscription data. The registration receipt message carries the terminal device's authorization information.

[0120] In other examples, the terminal device receives the authorization information as follows: the terminal device receives a Management Terminal Device Policy Command message sent by a second network element, which carries the authorization information. The second network element may include a PCF (Programmable Component Filter). The Management Terminal Device Policy Command message received by the terminal device may be forwarded via a first network element; that is, the terminal device receives the Management Terminal Device Policy Command message sent by the second network element through the first network element.

[0121] For example, after a terminal device registers with the network, the AMF sends the terminal device's first service authorization request to the PCF. The PCF then sends the terminal device's management terminal device policy command message, which is transmitted to the terminal device via the AMF. The management terminal device policy command message carries the terminal device's authorization information.

[0122] Through the various methods described above, the terminal device receives authorization information sent by the network device, or the terminal device is pre-configured with authorization information in other ways; when the terminal device receives a service request for an AIoT service from the network side, it can determine the identification information (such as Reader ID) corresponding to the AIoT service based on the characteristic information of the AIoT service and the authorization information (or, the network device can send the identification information corresponding to the AIoT service to the terminal), and use the identification information (such as Reader ID) when executing the AIoT service.

[0123] For example, when a UE performs an inventory service for an AIoT device, the UE sends an inventory message to the AIoT device, which carries the corresponding Reader ID. The AIoT device responds and reports its AIoT Device ID and Reader ID. Subsequently, the UE can report the AIoT Device ID and Reader ID to the network. This allows the UE to use different Reader IDs at different times, locations, or for different services, and enables the UE to perform AIoT service operations from different service providers simultaneously, thus making AIoT service operations more efficient.

[0124] This application also proposes a service control method, which can be applied to a first network element, such as an AMF. Figure 5 is a schematic flowchart of a service control method 500 according to an embodiment of this application. This method can optionally be applied to the systems shown in Figures 1, 2A, 2B, or 3B, but is not limited thereto. The method includes at least a portion of the following:

[0125] S510. The first network element determines the terminal device that performs the first service based on the feature information of the first service and the authorization information of the terminal device; the authorization information includes the feature information of the first service that the terminal device is allowed to perform.

[0126] S520, The first network element sends a message to instruct the terminal device to perform a first service.

[0127] The first network element may include an AMF.

[0128] The first service may include AIoT services or AIoT service operations. For example, AIoT services or AIoT service operations may include inventory operations or command operations.

[0129] In some implementations, the characteristic information of the first service includes at least one of the following:

[0130] (1) Business attributes;

[0131] (2) Time period information;

[0132] (3) Regional information.

[0133] The business attributes may include at least one of the following: business provider information, business identifier, and application identifier.

[0134] For example, service provider information includes a service ID.

[0135] For example, the service identifier includes at least one of Single Network Slice Selection Assistance Information (S-NSSAI) and Data Network Name (DNN).

[0136] For example, application identifiers include Application ID or Application Function ID (AF ID).

[0137] The regional information may include at least one of the following: community information, tracking area information, and geographic location information.

[0138] For example, cell information includes the cell ID.

[0139] For example, tracking area information includes tracking area ID or tracking area code.

[0140] For example, geographic location information includes geographic region information.

[0141] For example, the identification information corresponding to the first service may include the reader ID.

[0142] Through the above process, the first network element can determine the terminal device that performs the first service based on the characteristic information of the first service, and send a message to the terminal device to instruct the terminal device to perform the first service.

[0143] In some examples, the authorization information may also include the identification information corresponding to the first service.

[0144] The first network element can also determine the identification information corresponding to the first service based on the feature information of the first service and the authorization information of the terminal device, and send the identification information corresponding to the first service.

[0145] Through the above process, the first network element can not only determine the terminal device that performs the first service, but also determine the identification information corresponding to the first service, and instruct the terminal device to perform the first service and the identification information corresponding to the first service.

[0146] Through the above methods, the first network element can trigger the terminal device to perform AIoT services.

[0147] Furthermore, the first network element can also send authorization information to the terminal device.

[0148] In some examples, the first network element can send authorization information to the UE during the UE registration process. For example:

[0149] The first network element receives the registration request message from the terminal device;

[0150] The first network element sends a subscription data request message for the terminal device to the third network element; the third network element may include a UDM.

[0151] The first network element receives a subscription data response message sent by the third network element. The subscription data response message carries the feature information of the first service that the terminal device is allowed to perform and / or the identification information corresponding to the first service.

[0152] The first network element sends a registration acceptance message to the terminal device, which carries the authorization information of the terminal device.

[0153] In some examples, the first network element can send authorization information to the UE after the UE has registered with the network. For example:

[0154] The first network element sends an authorization request for the first service to the second network element; the second network element may include a PCF.

[0155] The first network element receives the management terminal device policy command message sent by the second network element.

[0156] The first network element sends a management terminal device policy command message to the terminal device, which carries the authorization information of the terminal device.

[0157] Through the above process, the first network element or the second network element can authorize terminal devices to perform AIoT services.

[0158] For a specific example of the first network element execution method 500 in this embodiment, please refer to the relevant description of the first network element, such as AMF, in the above method 400. For the sake of brevity, it will not be repeated here.

[0159] This application also proposes a service control method, which can be applied to a second network element, such as a PCF. Figure 6 is a schematic flowchart of a service control method 600 according to an embodiment of this application. This method can optionally be applied to the systems shown in Figures 1, 2A, 2B, or 3B, but is not limited thereto. The method includes at least a portion of the following:

[0160] S610. The second network element sends a management terminal device policy command message. The management terminal device policy command message carries the authorization information of the terminal device. The authorization information includes the characteristic information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

[0161] The second network element may include a PCF.

[0162] The first service may include AIoT services or AIoT service operations. For example, AIoT services or AIoT service operations may include inventory operations or command operations.

[0163] In some implementations, the characteristic information of the first service includes at least one of the following:

[0164] (1) Business attributes;

[0165] (2) Time period information;

[0166] (3) Regional information.

[0167] The business attributes may include at least one of the following: business provider information, business identifier, and application identifier.

[0168] For example, service provider information includes a service ID.

[0169] For example, the service identifier includes at least one of Single Network Slice Selection Assistance Information (S-NSSAI) and Data Network Name (DNN).

[0170] For example, application identifiers include Application ID or Application Function ID (AF ID).

[0171] The regional information may include at least one of the following: community information, tracking area information, and geographic location information.

[0172] For example, cell information includes the cell ID.

[0173] For example, tracking area information includes tracking area ID or tracking area code.

[0174] For example, geographic location information includes geographic region information.

[0175] For example, the identification information corresponding to the first service may include the reader ID.

[0176] The authorization information of the terminal device may include the characteristic information of the first service that the terminal is allowed to perform, and the identification information corresponding to the first service.

[0177] Through the above process, the second network element can send authorization information for AIoT services to the terminal device.

[0178] In some examples, the second network element can send management terminal device policy command messages through the first network element. For example, the first network element may include an AMF (Advanced Management Function).

[0179] Specifically, for example, the second network element receives an authorization request for the first service sent by the first network element;

[0180] The second network element sends a management terminal device policy command message to the first network element, and the management terminal device policy command message carries the authorization information of the terminal device.

[0181] The first network element sends the management terminal device policy command message to the terminal device.

[0182] The above process enables the configuration of authorization information for terminal devices. Using this authorization information, the terminal device can execute authorized AIoT services and use the corresponding Reader ID when executing these services.

[0183] For a specific example of the second network element execution method 600 in this embodiment, please refer to the relevant description of the second network element, such as PCF, in the above method 400. For the sake of brevity, it will not be repeated here.

[0184] The present application will now be described in detail with reference to the accompanying drawings and specific embodiments. In the following embodiments, the first service is an AIoT service operation and the identification information corresponding to the first service (that is, the identification information used by the terminal device when performing the first service) is a Reader ID, as an example.

[0185] Example 1:

[0186] This example describes the authorization process for the UE.

[0187] Figure 7A is a flowchart of the first implementation of Embodiment 1 of this application. As shown in Figure 7A, this implementation includes the following steps:

[0188] S701. The process of the UE initiating registration with the core network element (such as AMF) includes sending a registration request. The registration request carries the UE identification information and may also carry the AIoT service request supported by the UE, such as inventory or command.

[0189] S702. After receiving the registration request, the AMF sends a UE subscription data acquisition request to the UDM or the service provider's database to obtain the UE's subscription data.

[0190] S703, UDM returns a subscription data response to AMF, which carries subscription data. The subscription data may include whether the UE is allowed to perform AIoT service operations. AIoT service operations may include inventory and / or commands. If the UE is allowed to perform AIoT service operations, it may further carry the service provider, service identifier or application identifier (which can be identified by service ID, S-NSSAI, DNN, application ID or AF ID), and the Reader ID used to execute these services.

[0191] Alternatively, it can further carry the time period or region corresponding to the permitted AIoT business operations, as well as the Reader ID used in those time periods or regions.

[0192] S704. Based on the subscription data received in step S703, the AMF returns a registration acceptance message to the UE. This message includes the service provider, service identifier, or application identifier (which can be identified using service id, S-NSSAI, DNN, application ID, or AF ID) corresponding to the UE's AIoT service operation, and the Reader ID used when performing the AIoT service operation. It can further limit the permitted service providers, service identifiers, or application identifiers (which can be identified using service id, S-NSSAI, DNN, application ID, or AF ID) for allowed AIoT service operations. Additionally, it can carry the time period or area corresponding to the permitted AIoT service operation. The UE is only permitted to perform AIoT service operations within this specific time period and uses the corresponding Reader ID when performing the AIoT service operation; or, the UE is only permitted to perform AIoT service operations within this specific area and uses the corresponding Reader ID when performing the AIoT service operation. The area information can be cell information (such as cell ID), tracking area information (such as tracking area code / id), or specific geographical location information. The format of information carried in the registration acceptance message is shown in Table 2 below:

[0193] Table 2

[0194] In Table 2, Reader ID a is used when the time of the AIoT service operation meets the corresponding time period a and the UE's location information meets the corresponding location area a. Reader ID b is used when the time of the AIoT service operation meets the corresponding time period b. Reader ID c is used when the UE's location information meets the corresponding location area c. It should be noted that the time period or area information here can be multiple time periods or multiple areas.

[0195] The mapping between services and Reader IDs can be formatted as shown in Table 3. A Reader ID can correspond to one or more services.

[0196] Table 3

[0197] As shown in Table 3, Reader ID j is used under the condition that the AIoT service operation being performed satisfies the corresponding service-j or service-k.

[0198] For services that correspond to a large number of AIoT Devices, the format shown in Table 4 below can be used. Here, one service corresponds to multiple Reader IDs:

[0199] Table 4

[0200] As shown in Table 4, Reader ID j and Reader ID k are used under the condition that the AIoT service operation meets the corresponding service-j. For different AIoT devices, the UE can use different Reader IDs when performing the AIoT service operation.

[0201] The Reader ID can also be adopted in the manner shown in Table 5. In this way, the corresponding AIoT service operation is performed when the time of the AIoT service operation meets the corresponding time period 'a' and the UE's location information meets the corresponding location region 'a'.

[0202] Table 5

[0203] S705, the UE returns a registration completion message to the core network element (such as AMF).

[0204] In the example above, the Core Network (CN) authorizes the AIoT service operations that the UE can perform. The CN provides the UE with authorization information, which authorizes the AIoT service operations that the UE is allowed to perform, as well as the Reader ID used when performing the AIoT service operation. Processes unrelated to this application, such as authentication processes, are omitted in the above process.

[0205] Figure 7B is a flowchart of a second implementation of Embodiment 1 of this application. As shown in Figure 7B, this implementation includes the following steps:

[0206] S711, UE initiates the registration process and registers with the network.

[0207] S712, AMF sends an authorization request for AIoT service operation to PCF.

[0208] S713, PCF sends management terminal device policy command messages to AMF.

[0209] S714, the AMF sends a management terminal device policy command message to the UE. This management terminal device policy command message includes the service provider, service identifier, or application identifier (which can be identified by service id, S-NSSAI, DNN, application ID, or AF ID) corresponding to the AIoT service operation performed by the UE, as well as the Reader ID used when performing the AIoT service operation. It can also further limit the service provider, service identifier, or application identifier corresponding to the allowed AIoT service operation (which can be identified by service id, S-NSSAI, DNN, application ID, or AF ID); in addition, it can also carry the time period or area corresponding to the allowed AIoT service operation.

[0210] The UE is only permitted to perform AIoT service operations within a specific time period, and uses the corresponding Reader ID when performing such operations; alternatively, the UE is only permitted to perform AIoT service operations within a specific area, and uses the corresponding Reader ID when performing such operations. The information for this area can be cell information (e.g., cell ID), tracking area information (e.g., tracking area code / id), or specific geographical location information. Examples of the format of information carried in the management terminal device policy command message can be found in Tables 2 to 5 above.

[0211] In the example above, the PCF authorizes the UE to perform AIoT service operations. The PCF provides the UE with authorization information, which is used to authorize the AIoT service operations that the UE is allowed to perform, as well as the Reader ID used when performing the AIoT service operation.

[0212] Example 2:

[0213] This embodiment describes the process of the network side triggering the UE to perform AIoT service operations. After the UE is triggered to perform AIoT service operations, it can use authorization information to determine whether to perform AIoT service operations and the Reader ID used when performing AIoT service operations. The UE can be authorized using the method described in Embodiment 1, or other methods can be used to authorize the UE.

[0214] Figure 8A is a flowchart of the first implementation of Embodiment 2 of this application. As shown in Figure 8A, this implementation includes the following steps:

[0215] S801. The Application Function (AF) sends an AIoT service request to the AMF; or, the AF sends an AIoT service request to the AMF through the Network Exposure Function (NEF); or, the AF sends an AIoT service request to the AMF through an AIoT NF (a network element specifically deployed for AIoT services). The AIoT service request may carry the requested AIoT service, as well as the service provider, service identifier, or application identifier (which can be identified by service id, S-NSSAI, DNN, application ID, or AF ID), the time period or area corresponding to the AIoT service, and the area information may be cell information (such as cell ID), tracking area information (such as tracking area code / id), or specific geographical location information; it may also carry the UE identifier executing the AIoT service.

[0216] S802. The AMF determines which UEs will execute the AIoT service based on the AIoT service request. For example, the AMF decides which UEs will execute the AIoT service based on its service attributes; service attributes include the service provider, service identifier, or application identifier corresponding to the service, which can be identified using service ID, S-NSSAI, DNN, or application ID. Alternatively, the AMF determines which UEs will execute the AIoT service based on the corresponding region and / or time period; specifically, the AMF can determine which UEs will participate in the inventory based on the region and / or time period corresponding to the AIoT service, and the region and / or time period allowed for the UE to execute the AIoT service (this information can be part of the UE's authorization information).

[0217] S803, AMF sends an AIoT service request to the gNB of the identified UE, and the AIoT service request carries the service information of the AIoT service.

[0218] S804 and gNB send an AIoT service request to the UE, which carries the service information of the AIoT service.

[0219] The AIoT service request can be a NAS message. If the UE is in an idle state, the gNB can send a paging message to the UE, which carries the AIoT service request.

[0220] S805. The UE can determine the Reader ID to use when performing the AIoT service (such as an AIoT Service operation) based on its own authorization information. For example, the Reader ID can be determined based on the time period, location, and / or the service attributes of the AIoT Service operation (such as service provider, service identifier, or application identifier, which can be identified by service id, S-NSSAI, DNN, application id, or AF ID).

[0221] S806. The UE performs the AIoT Service operation and carries the Reader ID determined in step S805 in the AIoT service operation message sent to the corresponding AIoT device (Decide).

[0222] In the subsequent process, the AIoT Device responds and reports the AIoT Device ID and Reader ID; the UE reports the AIoT Device ID and Reader ID to the AF through the network.

[0223] Through the above process, the UE can use different Reader IDs at different times or locations, and the UE can also use different Reader IDs for different services. This allows the UE to perform AIoT service operations for different service providers or services simultaneously, making AIoT service operations more efficient.

[0224] Figure 8B is a flowchart of the second implementation of Embodiment 2 of this application. As shown in Figure 8B, this implementation includes the following steps:

[0225] S811. The Application Function (AF) sends an AIoT service request to the AMF; or, the AF sends an AIoT service request to the AMF through the NEF; or, the AF sends an AIoT service request to the AMF through an AIoT NF (a network element specifically deployed for AIoT services). The AIoT service request may carry the requested AIoT service, as well as the service provider, service identifier, or application identifier (which can be identified by service id, S-NSSAI, DNN, application ID, or AF ID), the time period or area corresponding to the AIoT service, and the area information may be cell information (such as cell ID), tracking area information (such as tracking area code / id), or specific geographical location information; it may also carry the UE identifier executing the AIoT service.

[0226] S812. The AMF determines which UEs will execute the AIoT service based on the AIoT service request. For example, the AMF determines which UEs will execute the AIoT service based on the service attributes of the AIoT service; service attributes include the service provider, service identifier, or application identifier corresponding to the service, which can be identified using service ID, S-NSSAI, DNN, or application ID. Alternatively, the AMF determines which UEs will execute the AIoT service based on the corresponding region and / or time period; specifically, the AMF can determine which UEs will participate in the inventory based on the region and / or time period corresponding to the AIoT service, and the region and / or time period allowed for the UE to execute the AIoT service (this content can be part of the UE's authorization information).

[0227] While selecting the UE, the AMF can also determine the Reader ID to be used when conducting AIoT services (such as AIoT Service operation) based on the UE's authorization information. For example, the Reader ID can be determined based on the time period, location, and / or the service attributes of the AIoT Service operation (such as service provider, service identifier, or application identifier, which can be identified by service id, S-NSSAI, DNN, application id, or AF ID).

[0228] S813, AMF sends an AIoT service request to the gNB of the identified UE. The AIoT service request carries the service information of the AIoT service and may also carry the Reader ID used by the UE when performing the AIoT service.

[0229] S814 and gNB send an AIoT service request to the UE. The AIoT service request carries the service information of the AIoT service and may also carry the Reader ID used by the UE when performing the AIoT service.

[0230] The AIoT service request can be a NAS message. If the UE is in an idle state, the gNB can send a paging message to the UE, which carries the AIoT service request and the Reader ID.

[0231] S815, the UE performs the AIoT Service operation and carries the Reader ID received in step S814 in the AIoT service operation message sent to the corresponding AIoT device (Decide).

[0232] In the subsequent process, the AIoT Device responds and reports the AIoT Device ID and Reader ID; the UE reports the AIoT Device ID and Reader ID to the AF through the network.

[0233] Through the above process, the UE can use different Reader IDs at different times or locations, and the UE can also use different Reader IDs for different services. This allows the UE to perform AIoT service operations for different service providers or services simultaneously, making AIoT service operations more efficient.

[0234] This application also proposes a terminal device. FIG9 is a schematic block diagram of a terminal device 900 according to an embodiment of this application. The terminal device 900 may include:

[0235] The first processing module 910 is used to execute the first service based on the identification information corresponding to the first service; wherein,

[0236] The identification information is determined based on the feature information of the first service and the authorization information of the terminal device. The authorization information includes the feature information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

[0237] In some implementations, the characteristic information of the first service includes at least one of the following:

[0238] Business attributes;

[0239] Time period information;

[0240] Regional information.

[0241] In some implementations, the business attributes include at least one of the following: business provider information, business identifier, and application identifier.

[0242] In some implementations, the service provider information includes a service identifier.

[0243] In some implementations, the service identifier includes at least one of Single Network Slice Selection Auxiliary Information (S-NSSAI) and Data Network Name (DNN).

[0244] In some implementations, the application identifier includes the application function AF identifier ID.

[0245] In some implementations, the area information includes at least one of cell information, tracking area information, and geographic location information.

[0246] This application also proposes a terminal device. FIG10 is a schematic block diagram of a terminal device 1000 according to an embodiment of this application. The terminal device 1000 may include: a first processing module 910 and a first transceiver module 1020; wherein...

[0247] The first transceiver module 1020 is used to receive the identification information corresponding to the first service sent by the first network element.

[0248] In some implementations, the first processing module 910 is further configured to determine the identification information corresponding to the first service based on the feature information of the first service and the authorization information of the terminal device.

[0249] In some implementations, the first transceiver module 1020 is also used to receive authorization information.

[0250] In some implementations, the first transceiver module 1020 is used to receive a registration acceptance message sent by the first network element, the registration acceptance message carrying authorization information.

[0251] In some implementations, the first transceiver module 1020 is used to receive a management terminal device policy command message sent by the second network element, the management terminal device policy command message carrying authorization information.

[0252] In some implementations, the first transceiver module 1020 is used to receive management terminal device policy command messages sent by the second network element through the first network element.

[0253] In some implementations, the first network element includes an AMF.

[0254] In some implementations, the second network element includes a PCF.

[0255] In some implementations, the first service includes AIoT services.

[0256] The terminal devices 900 and 1000 in this application embodiment can implement the corresponding functions of the terminal devices in the aforementioned method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in terminal devices 900 and 1000 can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in terminal devices 900 and 1000 in this application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0257] Figure 11 is a schematic block diagram of a first network element 1100 according to an embodiment of the present application. The first network element 1100 may include:

[0258] The second processing module 1110 is used to determine the terminal device that performs the first service based on the feature information of the first service and the authorization information of the terminal device; the authorization information includes the feature information of the first service that the terminal device is allowed to perform.

[0259] The second transceiver module 1120 is used to send a message instructing the terminal device to perform the first service.

[0260] In some implementations, the authorization information also includes identification information corresponding to the first service.

[0261] In some implementations, the second processing module 1110 is further configured to determine the identification information corresponding to the first service based on the feature information of the first service and the authorization information of the terminal device;

[0262] In some implementations, the second transceiver module 1120 is also used to send identification information corresponding to the first service.

[0263] In some implementations, the characteristic information of the first service includes at least one of the following:

[0264] Business attributes;

[0265] Time period information;

[0266] Regional information.

[0267] In some implementations, the business attributes include at least one of the following: business provider information, business identifier, and application identifier.

[0268] In some implementations, the service provider information includes a service identifier.

[0269] In some implementations, the service identifier includes at least one of S-NSSAI and DNN.

[0270] In some implementations, the application identifier includes the AF ID.

[0271] In some implementations, the area information includes at least one of cell information, tracking area information, and geographic location information.

[0272] In some implementations, the second transceiver module 1120 is also used to send authorization information for the terminal device.

[0273] In some implementations, the second transceiver module 1120 is used to send a registration acceptance message for the terminal device, the registration acceptance message carrying the authorization information of the terminal device.

[0274] In some embodiments, the second transceiver module 1120 is further configured to: receive a registration request message from a terminal device; send a subscription data request message from the terminal device to a third network element; and receive a subscription data response message from the third network element, wherein the subscription data response message carries feature information of a first service permitted by the terminal device and / or identification information corresponding to the first service.

[0275] In some implementations, the third network element includes a UDM.

[0276] In some implementations, the second transceiver module 1120 is used to send a management terminal device policy command message for the terminal device, which carries authorization information.

[0277] In some implementations, the second transceiver module 1120 is further configured to send an authorization request for the first service to the second network element and receive a management terminal device policy command message sent by the second network element.

[0278] In some implementations, the second network element includes a PCF.

[0279] In some implementations, the first network element includes an AMF.

[0280] In some implementations, the first service includes AIoT services.

[0281] The first network element 1100 in this application embodiment can realize the corresponding function of the first network element in the aforementioned method embodiment. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the first network element 1100 can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the first network element 1100 of the application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0282] Figure 12 is a schematic block diagram of a second network element 1200 according to an embodiment of the present application. The network device 1200 may include:

[0283] The third transceiver module 1210 is used to send management terminal device policy command messages. The management terminal device policy command messages carry the authorization information of the terminal device. The authorization information includes the feature information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

[0284] In some implementations, the characteristic information of the first service includes at least one of the following:

[0285] Business attributes;

[0286] Time period information;

[0287] Regional information.

[0288] In some implementations, the business attributes include at least one of the following: business provider information, business identifier, and application identifier.

[0289] In some implementations, the service provider information includes a service identifier.

[0290] In some implementations, the service identifier includes at least one of Single Network Slice Selection Auxiliary Information (S-NSSAI) and Data Network Name (DNN).

[0291] In some implementations, the application identifier includes the application function AF identifier ID.

[0292] In some implementations, the area information includes at least one of cell information, tracking area information, and geographic location information.

[0293] In some implementations, the third transceiver module 1210 is also used to send management terminal device policy command messages to the first network element.

[0294] In some implementations, the third transceiver module 1210 is further configured to receive an authorization request for a first service sent by the first network element.

[0295] In some implementations, the first network element includes an AMF.

[0296] In some implementations, the second network element includes a PCF.

[0297] In some implementations, the first service includes AIoT services.

[0298] Figure 13 is a schematic structural diagram of a communication device 1300 according to an embodiment of this application. The communication device 1300 includes a processor 1310, which can call and run computer programs from memory to enable the communication device 1300 to implement the methods in the embodiments of this application.

[0299] In one embodiment, the communication device 1300 may further include a memory 1320. The processor 1310 can retrieve and run computer programs from the memory 1320 to enable the communication device 1300 to implement the methods described in the embodiments of this application.

[0300] The memory 1320 can be a separate device independent of the processor 1310, or it can be integrated into the processor 1310.

[0301] In one embodiment, the communication device 1300 may further include a transceiver 1330, and the processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0302] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0303] In one embodiment, the communication device 1300 may be a terminal device in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0304] In one embodiment, the communication device 1300 may be the first network element in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the first network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0305] In one embodiment, the communication device 1300 may be a second network element in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the second network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0306] Figure 14 is a schematic structural diagram of a chip 1400 according to an embodiment of this application. The chip 1400 includes a processor 1410, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0307] In one embodiment, chip 1400 may further include memory 1420. Processor 1410 can retrieve and run computer programs from memory 1420 to implement the methods executed by a terminal device or network device in this embodiment.

[0308] The memory 1420 can be a separate device independent of the processor 1410, or it can be integrated into the processor 1410.

[0309] In one embodiment, the chip 1400 may further include an input interface 1430. The processor 1410 can control the input interface 1430 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0310] In one embodiment, the chip 1400 may further include an output interface 1440. The processor 1410 can control the output interface 1440 to communicate with other devices or chips; specifically, it can output information or data to other devices or chips.

[0311] In one embodiment, the chip can be applied to the terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0312] In one implementation, the chip can be applied to the first network element in the embodiments of this application, and the chip can implement the corresponding processes implemented by the first network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0313] In one implementation, the chip can be applied to the second network element in the embodiments of this application, and the chip can implement the corresponding processes implemented by the second network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0314] The chips used in network equipment and terminal equipment can be the same chip or different chips.

[0315] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0316] The processors mentioned above can be general-purpose processors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processors mentioned above can be microprocessors or any conventional processor.

[0317] The aforementioned memory can be volatile memory or non-volatile memory, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM).

[0318] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0319] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

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

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

[0322] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A business control method, comprising: The terminal device executes the first service based on the identification information corresponding to the first service; wherein, The identification information is determined based on the feature information of the first service and the authorization information of the terminal device. The authorization information includes the feature information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

2. The method according to claim 1, wherein, The characteristic information of the first service includes at least one of the following: Business attributes; Time period information; Regional information.

3. The method according to claim 2, wherein, The business attributes include at least one of the following: business provider information, business identifier, and application identifier.

4. The method according to claim 3, wherein, The service provider information includes a service identifier.

5. The method according to claim 3, wherein, The service identifier includes at least one of Single Network Slice Selection Assistance Information (S-NSSAI) and Data Network Name (DNN).

6. The method according to claim 3, wherein, The application identifier includes the application function AF identifier ID.

7. The method according to claim 2, wherein, The regional information includes at least one of the following: community information, tracking area information, and geographic location information.

8. The method according to any one of claims 1-7 further includes the terminal device receiving identification information corresponding to the first service sent by the first network element.

9. The method according to any one of claims 1-7 further includes, wherein the terminal device determines the identification information corresponding to the first service based on the feature information of the first service and the authorization information of the terminal device.

10. The method according to any one of claims 1-9, further comprising the terminal device receiving the authorization information.

11. The method according to claim 10, wherein, The terminal device receives the authorization information, including: The terminal device receives a registration acceptance message sent by the first network element, and the registration acceptance message carries the authorization information.

12. The method according to claim 10, wherein, The terminal device receives the authorization information, including: The terminal device receives a management terminal device policy command message sent by the second network element, and the management terminal device policy command message carries the authorization information.

13. The method according to claim 12, wherein, The terminal device receives a management terminal device policy command message sent by the second network element, including: The terminal device receives a management terminal device policy command message sent by the second network element through the first network element.

14. The method according to claim 8, 11 or 13, wherein, The first network element includes the Access and Mobility Management Function (AMF).

15. The method according to claim 12 or 13, wherein, The second network element includes a policy management function (PCF).

16. The method according to any one of claims 1-15, wherein, The first business includes passive Internet of Things (AIoT) business.

17. A business control method, comprising: The first network element determines the terminal device to perform the first service based on the feature information of the first service and the authorization information of the terminal device. The authorization information includes feature information of the first service that the terminal device is allowed to perform; The first network element sends a message to instruct the terminal device to perform a first service.

18. The method according to claim 17, wherein the authorization information further includes identification information corresponding to the first service.

19. The method of claim 18, further comprising: The first network element determines the identification information corresponding to the first service based on the feature information of the first service and the authorization information of the terminal device; The first network element sends the identification information corresponding to the first service.

20. The method according to any one of claims 17-19, wherein, The characteristic information of the first service includes at least one of the following: Business attributes; Time period information; Regional information.

21. The method according to claim 20, wherein, The business attributes include at least one of the following: business provider information, business identifier, and application identifier.

22. The method according to claim 21, wherein, The service provider information includes a service identifier.

23. The method according to claim 21, wherein, The service identifier includes at least one of S-NSSAI and DNN.

24. The method according to claim 21, wherein, The application identifier includes the AF ID.

25. The method according to claim 20, wherein, The regional information includes at least one of the following: community information, tracking area information, and geographic location information.

26. The method according to any one of claims 17-25, further comprising the first network element sending authorization information of the terminal device.

27. The method according to claim 26, wherein, The first network element sends authorization information to the terminal device, including: The first network element sends a registration acceptance message to the terminal device, the registration acceptance message carrying the authorization information of the terminal device.

28. The method according to claim 27, further comprising, before the first network element sends the registration acceptance message of the terminal device: The first network element receives the registration request message from the terminal device; The first network element sends a subscription data request message for the terminal device to the third network element; The first network element receives a subscription data response message sent by the third network element. The subscription data response message carries feature information of the first service that the terminal device is allowed to perform and / or identification information corresponding to the first service.

29. The method according to claim 28, wherein, The third network element includes User Data Management (UDM).

30. The method according to claim 26, wherein, The first network element sends authorization information to the terminal device, including: The first network element sends a management terminal device policy command message to the terminal device, the management terminal device policy command message carrying the authorization information.

31. The method according to claim 30, further comprising, before the first network element sends the management terminal device policy command message of the terminal device: The first network element sends an authorization request for the first service to the second network element; The first network element receives the management terminal device policy command message sent by the second network element.

32. The method according to claim 31, wherein, The second network element includes PCF.

33. The method according to any one of claims 17-32, wherein, The first network element includes AMF.

34. The method according to any one of claims 17-33, wherein, The first business includes AIoT business.

35. A business control method, comprising: The second network element sends a management terminal device policy command message, which carries the authorization information of the terminal device. The authorization information includes the feature information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

36. The method according to claim 35, wherein, The characteristic information of the first service includes at least one of the following: Business attributes; Time period information; Regional information.

37. The method of claim 36, wherein, The business attributes include at least one of the following: business provider information, business identifier, and application identifier.

38. The method according to claim 37, wherein, The service provider information includes a service identifier.

39. The method according to claim 37, wherein, The service identifier includes at least one of Single Network Slice Selection Assistance Information (S-NSSAI) and Data Network Name (DNN).

40. The method of claim 37, wherein, The application identifier includes the application function AF identifier ID.

41. The method according to claim 36, wherein, The regional information includes at least one of the following: community information, tracking area information, and geographic location information.

42. The method according to any one of claims 35-41, wherein, The second network element sends a management terminal device policy command message, including: The second network element sends the management terminal device policy command message through the first network element.

43. The method according to claim 42 further includes the second network element receiving an authorization request for a first service sent by the first network element.

44. The method according to claim 42 or 43, wherein, The first network element includes AMF.

45. The method according to any one of claims 35-44, wherein, The second network element includes PCF.

46. ​​The method according to any one of claims 35-45, wherein, The first business includes AIoT business.

47. A terminal device, comprising: The first processing module is used to execute the first service based on the identification information corresponding to the first service; wherein, The identification information is determined based on the feature information of the first service and the authorization information of the terminal device. The authorization information includes the feature information of the first service that the terminal device is allowed to perform and the identification information corresponding to the first service.

48. A first network element, comprising: The second processing module is used to determine the terminal device that will perform the first service based on the feature information of the first service and the authorization information of the terminal device. Terminal equipment; The authorization information includes feature information of the first service that the terminal device is allowed to perform; The second transceiver module is used to send a message instructing the terminal device to perform a first service.

49. A second network element, comprising: The third transceiver module is used to send management terminal device policy command messages. The management terminal device policy command messages carry authorization information of the terminal device. The authorization information includes feature information of a first service that the terminal device is allowed to perform and identification information corresponding to the first service.

50. A terminal device, comprising: A transceiver, a processor, and a memory, wherein the memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to invoke and run the computer program stored in the memory to cause the terminal device to perform the method as described in any one of claims 1 to 16.

51. A network device, comprising: A transceiver, a processor, and a memory, wherein the memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to invoke and run the computer program stored in the memory to cause the network device to perform the method as described in any one of claims 17 to 46.

52. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 46.

53. A computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the method as described in any one of claims 1 to 46.

54. A computer program product comprising computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 46.

55. A computer program that causes a computer to perform the method as described in any one of claims 1 to 46.

Images