Communication methods, and devices

Abstract

The present application relates to communication methods, devices, a computer-readable storage medium, a computer program product, and a computer program. A method comprises: a first device sending a first message, wherein the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

Description

Communication method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method, device, computer-readable storage medium, computer program product, and computer program. Background Art

[0002] In related technologies, electronic tags in radio frequency identification (RFID) systems are used for local management and communication of items. However, the distance between the electronic tags and the reader / writer is short, which makes it inconvenient to read, write or inventory the electronic tags remotely, thus limiting the use scenarios of the electronic tags. Based on this, the 3GPP network considers designing a new type of electronic tag. This new type of electronic tag can be called an Ambient IoT (Ambient power-enabled IoT, Environmental Collection Internet of Things) (hereinafter referred to as A-IoT or AIoT) tag or AIoT device. Unlike RFID, this AIoT tag or AIoT device can use the frequency resources of the 3GPP network for communication. However, how to improve the communication efficiency of AIoT tags or AIoT devices under the 3GPP network becomes a problem that needs to be solved.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a communication method, device, computer-readable storage medium, computer program product, and computer program.

[0005] An embodiment of the present application provides a communication method, including:

[0006] The first device sends a first message, where the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

[0007] An embodiment of the present application provides a communication method, including:

[0008] The second device receives a first message sent by the first device, where the first message carries a group service identifier of the first group and one or more commands corresponding to the first group.

[0009] An embodiment of the present application provides a communication method, including:

[0010] The core network device sends a second message, where the second message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0011] An embodiment of the present application provides a first device, including:

[0012] The first communication unit is configured to send a first message, wherein the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

[0013] An embodiment of the present application provides a second device, including:

[0014] The second communication unit is configured to receive a first message sent by a first device, wherein the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

[0015] An embodiment of the present application provides a core network device, including:

[0016] The third communication unit is configured to send a second message, wherein the second message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0017] An embodiment of the present application provides a first device, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and execute the computer program stored in the memory, so that the first device performs the above method.

[0018] An embodiment of the present application provides a second device, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and execute the computer program stored in the memory, so that the second device performs the above method.

[0019] An embodiment of the present application provides a core network device, comprising: a transceiver, a processor, and a memory. The memory is used to store a computer program, the transceiver is used to communicate with other devices, and the processor is used to call and execute the computer program stored in the memory, so that the core network device performs the above method.

[0020] The embodiment of the present application provides a chip for implementing the above method.

[0021] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method.

[0022] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a device to perform the above method when the computer program is executed by the device.

[0023] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above method.

[0024] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above method.

[0025] By adopting the solution provided in this embodiment, the first device can send a first message that carries the group service identifier of the first group and one or more commands corresponding to the first group. Thus, by sending the first message, the first device can enable each device in the first group to obtain the commands to be executed, thereby improving communication efficiency between the first device and each device in the first group. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0027] Figure 2 is a schematic diagram of the basic communication principle of the AIoT system.

[0028] Figure 3 is a schematic diagram of the 5G network system architecture.

[0029] Figure 4 is a schematic diagram of the scenario of the direct connection method of AIoT devices accessing the 5G network.

[0030] Figure 5 is a schematic diagram of a scenario in which an AIoT device accesses a 5G network in a non-direct connection manner.

[0031] FIG6 is a schematic flowchart of a communication method according to an embodiment of the present application.

[0032] FIG7 is a schematic flowchart of a communication method according to another embodiment of the present application.

[0033] FIG8 is a schematic flowchart of a communication method according to yet another embodiment of the present application.

[0034] FIG9 is a schematic flowchart of a communication method of a device in a direct connection mode according to an embodiment of the present application.

[0035] FIG10 is a schematic flowchart of a communication method of a device in a non-direct connection mode according to an embodiment of the present application.

[0036] FIG11 is a schematic flowchart of a method for a device to obtain a group service identifier in a direct connection mode according to another embodiment of the present application.

[0037] FIG12 is a schematic flowchart of a method for a device to obtain a group service identifier in a non-direct connection mode according to another embodiment of the present application.

[0038] FIG13 is a schematic block diagram of a first device according to an embodiment of the present application.

[0039] FIG14 is a schematic block diagram of a second device according to an embodiment of the present application.

[0040] FIG15 is a schematic block diagram of a core network device according to an embodiment of the present application.

[0041] FIG16 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0042] FIG17 is a schematic block diagram of a chip according to an embodiment of the present application.

[0043] FIG18 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0044] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

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

[0046] Generally speaking, traditional communication systems 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 communications, but will also support, 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, and the embodiments of the present application may also be applied to these communication systems. In one possible implementation, the communication system in the embodiment of the present application may be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario. In one possible implementation, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to an authorized spectrum, where the authorized spectrum may also be considered a non-shared spectrum.

[0047] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, where the terminal device may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next-generation communication system such as a NR network, or a terminal device in a future-evolved Public Land Mobile Network (PLMN) network, etc. In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (such as an airplane, a balloon, and a satellite, etc.). In an embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, 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, 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. As an example and not a limitation, in an embodiment of the present application, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices developed by applying wearable technology to intelligently design 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 clothing or accessories. Wearable devices are more than just hardware devices; they also enable powerful functionality through software support, data interaction, and cloud-based interaction.In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0048] In an embodiment of the present application, a network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in a WLAN, a base station (BTS) in a GSM or CDMA, a base station (NodeB, NB) in a WCDMA, an evolved base station (eNB or eNodeB) in an LTE, or 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 a network device in an NTN network. As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, 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 set up in a location such as land or water. In an embodiment of the present application, the network device may provide services for a cell, and the terminal device may communicate with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0049] Figure 1 exemplarily shows a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In a possible implementation, the communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application. In a possible implementation, 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 is not limited in this embodiment of the present application. Among them, the network device may include an access network device and a core network device. That is, the wireless communication system also includes multiple core networks for communicating with the access network device. The access network equipment may be an evolutionary base station (evolutional node B, which may be referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro base station, access point (AP), transmission point (TP) or new generation Node B (gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system. It should be understood that the equipment with communication functions in the network / system in the embodiment of the present application may be referred to as communication equipment. Taking the communication system shown in Figure 1 as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment in the embodiment of the present application, which will not be repeated here; the communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited in the embodiment of the present application.

[0050] To facilitate understanding of the embodiments of the present application, the following briefly describes the basic processes and basic concepts involved in the embodiments of the present application. It should be understood that the basic processes and basic concepts introduced below do not limit the embodiments of the present application.

[0051] Ambient IoT (Ambient power-enabled IoT) is a wireless communication technology suitable for short-range, low-speed communications. Ambient IoT (hereinafter referred to as A-IoT or AIoT) devices primarily combine radio frequency energy harvesting, backscattering, and low-power computing technologies to achieve the advantage of eliminating the need for power supply devices.

[0052] Figure 2 shows the basic components of an A-IoT system, which includes a reader and a tag. The tag can perform functions such as energy harvesting, backscatter communication, and low-power computing. Energy harvesting refers to radio frequency energy collection, which converts radio frequency energy into direct current (DC). The energy can be stored in batteries or capacitors, or collected and used directly to drive logic circuits, digital chips, or sensor devices, completing functions and applications such as modulation and transmission of backscatter signals and collection and processing of sensor information. The tag is a type of A-IoT device.

[0053] With the development of 5G systems, the 3GPP standard has introduced requirements for 5G systems to support A-IoT device access to the network. A-IoT device access to the network primarily targets scenarios with the following characteristics: extreme environments unsuitable for ordinary terminals; terminals with very low power consumption and cost; and battery-free terminals. A-IoT systems can be used in scenarios such as wireless industrial sensing networks, smart agriculture, smart warehousing and logistics, and smart homes. Based on the energy source and usage of A-IoT devices, A-IoT devices (or A-IoT terminals, or Ambient IoT terminals) can be categorized as follows:

[0054] 1) Passive Ambient IoT Terminals: Passive A-IoT terminals do not require internal batteries. When approaching a network device (such as an RFID reader), they are within the near-field radiation generated by the network device's antenna. Therefore, the passive A-IoT terminal antenna generates an induced current through electromagnetic induction, which drives a low-power chip circuit to demodulate the forward link signal and modulate the reverse link signal. For the backscatter link, the passive A-IoT terminal uses backscattering to transmit signals. As can be seen, passive A-IoT terminals do not require internal batteries to power either the forward link or the reverse link, making them true ambient IoT terminals.

[0055] Passive A-IoT terminals do not require batteries, and the RF circuit and baseband circuit 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.

[0056] Passive A-IoT devices also have the following characteristics: no battery; they draw energy from the surrounding environment (such as radio waves, solar energy, wind energy, mechanical kinetic energy, etc.); and they do not have a USIM card. They can also store a certain amount of energy from the surrounding environment, but the energy is very low, so the functional logic they support is much less than that of ordinary mobile phone terminals.

[0057] 2) Semi-passive Ambient IoT Terminals: These terminals do not have conventional batteries installed on them, but can use RF energy harvesting modules to harvest radio wave energy and store the harvested energy in an energy storage unit (such as a capacitor). After the energy storage unit obtains energy, it can drive low-power chip circuits to perform tasks such as demodulating forward link signals and modulating backward link signals. For backscatter links, semi-passive A-IoT terminals use backscattering to transmit signals. As can be seen, semi-passive A-IoT terminals do not require built-in batteries to drive either the forward link or the reverse link. Although energy stored in capacitors is used during operation, the energy comes from radio energy harvested by the energy harvesting module, making them true Ambient IoT terminals.

[0058] Semi-passive A-IoT terminals inherit many advantages of passive A-IoT terminals, so they have many advantages such as small size, light weight, very low price and long service life.

[0059] 3) Active Ambient IoT Terminals: In some scenarios, active Ambient IoT terminals can also be equipped with built-in batteries. The battery powers the low-power chip circuitry in active A-IoT terminals, enabling forward link signal demodulation and reverse link signal modulation. However, for backscatter links, active A-IoT terminals use backscattering to transmit signals. Therefore, the Ambient IoT nature of these terminals lies in the fact that reverse link signal transmission does not require the terminal's own power, but instead utilizes backscattering. Active A-IoT terminals have built-in batteries to power the RFID chip, increasing the tag's read and write range and improving communication reliability. Therefore, they are suitable for scenarios with relatively high requirements for communication distance and read latency. These A-IoT terminals can be tags or standard devices.

[0060] The 5G network system architecture is shown in Figure 3. Specifically, NSSF (Network Slice Selection Function) is mainly used to manage network slice-related information, such as selecting network slices for terminal devices; AUSF (Authentication Server Function) is used to complete the identity authentication function for user access; UDM (Unified Data Management) is used to manage and store contract data and authentication data; AMF (Access and Mobility Management Function) is used to complete mobility management, security anchor and secure UE policy management, etc.; SMF (Session Management Function) is used to complete session management, UE IP address allocation and management, etc.; PCF (Policy Control Function) is responsible for formulating policies related to UE mobility management, session management, billing, etc.; AF (Application Function) is used for external application servers; UPF (User Plane Function) is responsible for user plane processing, etc.; DN (Data Network) is the 5GC external data network (such as the Internet). Data is transmitted between various nodes in the 5G Core Network (5G Core Network), between user equipment (UE) and 5G Core Network nodes, between the UE and the Radio Access Network ((R)AN), and between the RAN and 5G Core Network nodes through corresponding interfaces. For example, as shown in Figure 3: Data is transmitted between the AMF and NSSF in the 5G Core Network (5G Core Network) via interface N22; data is transmitted between the AMF and the SMF via interface N11; data is transmitted between the AMF and the AUSF via interface N12; and data is transmitted between the AMF and the UDM via interface N8. Data is transmitted between the SMF and the UPF via interface N4. The UPF transmits data to the external data network via interface N6 and to the AN via interface N3. The UE connects to the AN via the Uu interface for access stratum communication and wireless data transmission. The UE connects to the AMF via the N1 interface for non-access stratum (NAS) communication and exchanges NAS messages. Data is transmitted between the RAN and the AMF via interface N2, and between the RAN and the UPF via interface N3. It should be understood that the above only describes the interfaces between some nodes, and other interfaces between other 5GC nodes in Figure 3 are not described one by one.

[0061] In a radio frequency identification (RFID) system, a reader / writer is a device that reads or writes information from an electronic tag. During operation, the reader / writer transmits radio frequency energy within an area, creating an electromagnetic field. The size of this area depends on the transmission power. When an electronic tag within the reader / writer's coverage area is triggered, the tag transmits its stored data or modifies it according to the reader / writer's commands. The reader / writer uses radio frequency (RF) to conduct contactless, two-way data communication with the tag, reading and writing to the tag, thereby achieving target identification and data exchange. Electronic tags generally consume little power and may not even require a power source or battery. For example, passive tags can receive microwave signals from the reader / writer and obtain energy from an electromagnetic induction coil to temporarily power themselves and complete information exchange. RFID has a short transmission range and is used for local management and communication of items, such as inventory management within warehouses, file management, access card management, and electronic highway toll payment. In an RFID system, command-type services (which may include read / write commands) are serial, meaning that a command for one tag must be completed before another tag's command can be processed. For example, in an RFID system, after completing the inventory and command of one tag, another tag's inventory and command can be processed, and so on.

[0062] In existing radio frequency identification (RFID) systems, electronic tags are used for local object management and communication. The distance between a passive tag and a reader is typically around one meter, while the distance between an active tag and a reader is around 100 meters. This makes it difficult to remotely read, write, or perform inventory checks on the tags, limiting their use cases.

[0063] Based on this, 3GPP networks are considering designing new electronic tags, called Passive IoT tags or Ambient IoT tags (or AIoT devices). Unlike RFID, these Passive IoT tags or Ambient IoT tags (or AIoT devices) can communicate using 3GPP network frequency resources. As shown in Figures 4 and 5, 3GPP TR38.848 currently provides several different access methods for Ambient IoT (AIoT devices) to access 5G networks, including a direct connection method (Figure 4) and an indirect connection method (Figure 5). In the direct connection method (or direct connection mode) shown in Figure 4, AIoT devices and base stations can directly transmit AIoT data / signals. In the indirect connection method (or indirect connection mode) shown in Figure 5, AIoT devices access the wireless network base station through an intermediate node (which can be a UE), and data transmission between the intermediate node and the base station is carried out over the Uu interface. Compared to the direct connection method, the indirect connection method has the following advantages: it can reduce the impact on the existing 3GPP network and extend coverage. However, if the serial command processing method of the RFID system is still used in the 3GPP cellular system, it will lead to very low efficiency. Therefore, how to improve the efficiency of AIoT devices in executing or processing commands in the 3GPP system becomes a problem that needs to be solved.

[0064] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the objects associated before and after are in an "or" relationship. It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B. In the description of the embodiments of this application, the term "corresponding" can mean that there is a direct or indirect correspondence between the two, or it can mean that there is an association relationship between the two, or it can mean a relationship between indication and indication, configuration and configuration, etc.

[0065] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0066] Figure 6 is a schematic flow chart of a communication method according to an embodiment of the present application. The method includes at least part of the following contents.

[0067] S610: The first device sends a first message, where the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

[0068] FIG7 is a schematic flow chart of a communication method according to another embodiment of the present application. The method includes at least part of the following contents.

[0069] S710. The second device receives a first message sent by the first device, where the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

[0070] FIG8 is a schematic flow chart of a communication method according to another embodiment of the present application. The method includes at least part of the following contents.

[0071] S810. The core network device sends a second message, where the second message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0072] Here, the first group may also be referred to as the first AIoT group. The first group includes one or more devices, each of which is an AIoT device. In some possible examples, the AIoT device may also be replaced by any one of an Internet of Things device, a zero-power device, a low-power device, an RFID tag, a Passive IoT tag, and an AIoT tag, which are not exhaustive here.

[0073] The second device may be a first AIoT device. The first AIoT device may belong to the first group or not belong to the first group.

[0074] The first device may be one of the following: a second access network device, a terminal.

[0075] The second access network device may be an access network device serving one or more AIoT devices and / or second devices in the first group.

[0076] The terminal can be an intermediate device, proxy device, or relay device for one or more AIoT devices and / or the second device in the first group, that is, one or more AIoT devices and / or the second device in the first group can interact with the network-side device through the terminal. In some possible examples, the terminal can also be called an Intermediate Node, a proxy UE, an intermediate UE, a relay device, and the like.

[0077] The core network device may be a control plane network element, such as an AMF.

[0078] The group service identifier may also be alternatively called information used for group communication, or group information, or an identifier used for group service, or a group service related identifier, etc., and all possible names are not limited or enumerated here.

[0079] The group service identifier includes at least one of the following: a group identifier (Group ID), a group session identifier (Group Session ID), a group service identifier (Group Service ID), a slice identifier, a DNN (Data Network Name), and a device identifier mask (Device ID Mask).

[0080] That is to say, the group service identifier of the first group may include at least one of the following: the Group ID of the first group, the Group Session ID of the first group, the Group Service ID of the first group, the slice identifier corresponding to the first group, the DNN corresponding to the first group, and the Device ID Mask corresponding to the first group.

[0081] The slice identifier may refer to an identifier of a network slice. For example, the network slice identifier may be S-NSSAI (Single Network Slice Selection Assistance Information); accordingly, the slice identifier corresponding to the first group may be the S-NSSAI corresponding to the first group.

[0082] The Device ID Mask corresponding to the first group can be the first K consecutive identical bits of the identification of all AIoT devices in one or more AIoT devices included in the first group; K can be an integer greater than or equal to 1, the value of K should be less than the length of the identification of each AIoT device, and K is equal to the length of the consecutive identical bits of the identification of each AIoT device in the first group. For example, the length of the identification (ID) of each AIoT device in the first group is 20 bits, and the first 10 bits of the ID of each AIoT device are the same, then K can be equal to 10, and the corresponding Device ID Mask corresponding to the first group should be equal to the first 10 bits of the ID of each AIoT device. It should be pointed out that this is only an exemplary explanation. In actual processing, the identical bits of the IDs of all AIoT devices contained in different groups may be different. Therefore, the length and content of the Device ID Mask corresponding to different groups may be different. This does not limit or exhaustively list all possible situations.

[0083] Each of the one or more commands corresponding to the first group may include: a read command (or read command) and / or a write command (or write command). Exemplarily, the command may also be a command-type service, for example, a command-type service includes at least one of the specific content of a read service, the specific content of a write service, and the like.

[0084] The read command may include description information of specific content to be read from the device. For example, the read command may include description information of at least one of the following contents to be read from the device: content of a specified time period, content of a specified type, content of a specified service, etc.

[0085] The write command may include specific content to be written to the device. In some possible examples, the specific content to be written to the device may be determined by the AF. In some possible examples, in addition to including the specific content to be written to the device, the write command may also indicate writing to a specified memory of the device, etc., which are not limited here.

[0086] Optionally, the one or more commands corresponding to the first group include: a first command corresponding to the first group, where the first command corresponding to the first group is a command that each device in the first group needs to execute.

[0087] Specifically, the first command corresponding to the first group may refer to a command (read command (or read command) and / or write command (or write command)) that each AIoT device in the first group needs to execute.

[0088] Optionally, the one or more commands corresponding to the first group include: multiple second commands corresponding to the first group, wherein different commands in the multiple second commands corresponding to the first group are commands to be executed by different devices in the first group.

[0089] It should be noted that different devices in the first group may correspond to different second commands, or different devices in the first group may correspond to the same second command, both of which are within the protection scope of this embodiment.

[0090] In some possible examples, each of the multiple second commands corresponding to the first group further corresponds to, is bound to, or is associated with an identifier or number of a different device in the first group. The identifier of the device may be an ID of the device; and the number of the device may refer to a specific number of the device in the first group.

[0091] For example, each second command corresponding to the first group may include an identifier or number of a device associated or corresponding to the second command. For example, any second command corresponding to the first group may occupy multiple bits, wherein a first portion of bits is used to carry the identifier or number of the device corresponding or associated with the second command, and a second portion of bits is used to carry the specific content of the second command.

[0092] In some possible examples, the arrangement order of the multiple second commands corresponding to the first group in the message can be used to determine the device in the first group corresponding to each second command in the multiple second commands.

[0093] A first correspondence exists between the arrangement order of the plurality of second commands corresponding to the first group and the devices in the first group. The first correspondence may be pre-configured in each device in the first group; and / or the correspondence may be pre-configured in at least one of the AF, the core network device, and the first device.

[0094] For example, the number of multiple second commands corresponding to the first group is 2, namely second command 1 and second command 2. These two second commands are arranged in order from low to high (or vice versa) according to the fields occupied by them, as second command 1 to second command 2. The first corresponding relationship can be that the second command 1 at the lowest bit corresponds to device 1 in the first group, and the second command 2 at the highest bit corresponds to devices 2 and 3 in the first group.

[0095] In some possible implementations, before the core network device sends the second message, the process may further include: the core network device receiving a sixth message, wherein the sixth message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0096] Specifically, the core network device receiving the sixth message may refer to the core network device receiving the sixth message sent by the AF. Exemplarily, taking the core network device as an AMF as an example, the core network device receiving the sixth message sent by the AF may include one of the following: the AMF receiving the sixth message sent by the AF; the AMF receiving the sixth message sent by the AF through the NEF.

[0097] Optionally, the sixth message may further carry location information corresponding to the first group, wherein the location information includes at least one of the following: relevant information of a tracking area (TA), relevant information of a cell, and a geographical location.

[0098] That is to say, in the sixth message received by the core network device, in addition to carrying the group service identifier of the first group and one or more commands corresponding to the first group, it can also carry at least one of the following: relevant information of the TA corresponding to the first group, relevant information of the cell corresponding to the first group, and the geographical location corresponding to the first group.

[0099] The TA-related information may include one or more TA-related information, wherein the relevant information of any TA may include at least one of the following: a TAC (Tracking Area Code) corresponding to the TA and a TAI (Tracking Area Identity) corresponding to the TA.

[0100] The relevant information of the cell may include relevant information of one or more cells, wherein the relevant information of any one cell may be an identifier of the cell; the identifier of the cell may be represented as a Cell ID, or the identifier corresponding to the cell may be a PCI (Physical Cell Identifier).

[0101] The geographic location may include one or more geographic areas. The one or more geographic areas may be represented by coordinates of one or more geographic areas, wherein the coordinates of any one of the geographic areas may be the coordinates of the center point of the geographic area and / or the coordinates of one or more boundary locations of the geographic area, etc.; any one of the coordinates may be represented by GPS coordinates.

[0102] In some possible implementations, the AIoT device accesses the network using a direct connection mode (or direct connection method).

[0103] The core network device sends the second message, including: the core network device sends the second message to a first device, wherein the first device is determined based on the location information corresponding to the first group, and the first device is a second access network device or a terminal.

[0104] When the AIoT device accesses the network in direct connection mode, the first device is the second access network device.

[0105] The manner in which the core network device determines the second access network device may include one of the following:

[0106] When the location information corresponding to the first group is relevant information of a TA corresponding to the first group, the core network device determines, based on the relevant information of the TA corresponding to the first group, an access network device in the same TA as the first group as the second access network device;

[0107] When the location information corresponding to the first group is relevant information of a cell corresponding to the first group, the core network device determines, based on the relevant information of the cell corresponding to the first group, an access network device corresponding to the cell where the first group is located as the second access network device;

[0108] When the location information corresponding to the first group is the geographical location corresponding to the first group, the core network device determines, based on the geographical location corresponding to the first group, relevant information about a TA corresponding to the first group; and, based on the relevant information about the TA corresponding to the first group, the core network device determines, as the second access network device, an access network device in the same TA as the first group.

[0109] In the case where the location information corresponding to the first group is the geographical location corresponding to the first group, the core network device determines the relevant information of the cell corresponding to the first group based on the geographical location corresponding to the first group, and the core network device determines the access network device corresponding to the cell where the first group is located as the second access network device based on the relevant information of the cell corresponding to the first group.

[0110] Optionally, one TA may correspond to one or more access network devices; accordingly, the core network device determines the access network device in the same TA as the first group as the second access network device based on the relevant information of the TA corresponding to the first group, which may be: the core network device determines one or more access network devices in the same TA as the first group based on the relevant information of the TA corresponding to the first group; and determines one access network device from the one or more access network devices in the same TA as the first group as the second access network device. Exemplarily, determining one access network device as the second access network device from the one or more access network devices in the same TA as the first group may refer to one of the following: when there is only one access network device in the same TA as the first group, using the access network device as the second access network device; when there are multiple access network devices in the same TA as the first group, arbitrarily selecting one access network device from the multiple access network devices as the second access network device.

[0111] Optionally, a cell may be covered by one or more access network devices; accordingly, the core network device determines the access network device corresponding to the cell where the first group is located as the second access network device based on the relevant information of the cell corresponding to the first group, which may be: the core network device determines one or more access network devices covering the cell where the first group is located based on the relevant information of the cell corresponding to the first group; and determines one access network device as the second access network device from the one or more access network devices covering the cell where the first group is located. Exemplarily, determining one access network device as the second access network device from the one or more access network devices covering the cell where the first group is located may refer to one of the following: in the case where there is only one access network device covering the cell where the first group is located, using the access network device as the second access network device; in the case where there are multiple access network devices covering the cell where the first group is located, arbitrarily selecting one access network device from the multiple access network devices as the second access network device.

[0112] In some embodiments, after the core network device selects the second access network device, it may send a second message to the second access network device. Here, the core network device may generate the second message by extracting the group service identifier of the first group and one or more commands corresponding to the first group carried in the sixth message, and adding the group service identifier of the first group and the one or more commands corresponding to the first group to the second message.

[0113] Correspondingly, before the first device sends the first message, the method further includes: the first device receiving the group service identifier of the first group and one or more commands corresponding to the first group.

[0114] When the AIoT device accesses the network in direct connection mode, the first device receives the group service identifier of the first group and one or more commands corresponding to the first group, including: the first device receives a second message sent by the core network device, wherein the second message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0115] Specifically, the first device is a second access network device, that is, before the second access network device sends the first message, it can include: the second access network device receives the second message sent by the core network device.

[0116] Furthermore, after the second access network device receives the second message, it may execute the process of sending the first message. Accordingly, the second device receiving the first message sent by the first device may refer to: the second device receiving the first message sent by the second access network device.

[0117] The content carried by the first message may be consistent with that of the second message, that is, the first message may also carry the group service identifier of the first group and one or more commands corresponding to the first group.

[0118] The message type of the first message is one of the following: a broadcast message, a paging message, or a paging-like message. Exemplarily, the message type of the first message may be a broadcast message, in which case the broadcast message carries the group service identifier of the first group and one or more commands corresponding to the first group. Exemplarily, the message type of the first message may be a paging message or a paging-like message, in which case the paging message or paging-like message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0119] In some possible implementations, the AIoT device accesses the network using a non-direct connection mode. In this implementation, the first device is a terminal.

[0120] In one embodiment, the core network device sends the second message, including: the core network device sends the second message to a first device, wherein the first device is determined based on location information corresponding to the first group, and the first device is a terminal.

[0121] The core network device may determine the terminal in one of the following ways:

[0122] When the location information corresponding to the first group is relevant information of a TA corresponding to the first group, the core network device selects a terminal in the same TA as the first group based on the relevant information of the TA corresponding to the first group;

[0123] When the location information corresponding to the first group is relevant information of a cell corresponding to the first group, the core network device selects a terminal in the cell where the first group is located based on the relevant information of the cell corresponding to the first group;

[0124] When the location information corresponding to the first group is the geographical location corresponding to the first group, the core network device determines relevant information about a TA corresponding to the first group based on the geographical location corresponding to the first group, and the core network device selects a terminal in the same TA as the first group based on the relevant information about the TA corresponding to the first group;

[0125] When the location information corresponding to the first group is the geographical location corresponding to the first group, the core network device determines the relevant information of the cell corresponding to the first group based on the geographical location corresponding to the first group, and the core network device selects the terminal in the cell where the first group is located based on the relevant information of the cell corresponding to the first group.

[0126] Optionally, the core network device selects a terminal in the same TA as the first group based on the relevant information of the TA corresponding to the first group. This may be: the core network device determines one or more candidate terminals with the first capability that are in the same TA as the first group based on the relevant information of the TA corresponding to the first group; and selects a terminal from one or more candidate terminals with the first capability that are in the same TA as the first group.

[0127] The first capability may refer to the ability to serve as an intermediate device, proxy device, or relay device for one or more AIoT devices. It should be noted that the capabilities of any candidate terminal may be pre-reported to the core network device, and this embodiment does not limit the manner in which any candidate terminal reports its own capabilities.

[0128] Selecting a terminal from one or more candidate terminals with first capability in the same TA as the first group may include one of the following: when there is only one candidate terminal with first capability in the same TA as the first group, using the candidate terminal as the terminal; when there are multiple candidate terminals with first capability in the same TA as the first group, selecting any one from multiple candidate terminals as the terminal.

[0129] Optionally, the core network device selects a terminal in the cell where the first group is located based on the relevant information of the cell corresponding to the first group. This may be: the core network device determines one or more candidate terminals with the first capability in the cell where the first group is located based on the relevant information of the cell corresponding to the first group; and selects a terminal from one or more candidate terminals with the first capability in the cell where the first group is located.

[0130] Among them, selecting a terminal from one or more candidate terminals with first capability in the cell where the first group is located may include one of the following: when there is only one candidate terminal with first capability in the cell where the first group is located, using the candidate terminal as the terminal; when there are multiple candidate terminals with first capability in the cell where the first group is located, selecting any one from multiple candidate terminals as the terminal.

[0131] In some embodiments, after selecting a terminal, the core network device may send a second message to the terminal. Here, the core network device generates the second message in the same manner as in the previous embodiment and is not further described. In this embodiment, the second message may be a Non Access Stratum (NAS) message.

[0132] Correspondingly, the first device receives the group service identifier of the first group and one or more commands corresponding to the first group, including: the terminal receives a second message sent by the core network device, wherein the second message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0133] After the terminal receives the second message sent by the core network device, the terminal may execute the process of sending the first message. Accordingly, the second device receiving the first message sent by the first device may refer to: the second device receiving the first message sent by the terminal.

[0134] The content carried by the first message may be consistent with that of the second message, that is, the first message may also carry the group service identifier of the first group and one or more commands corresponding to the first group.

[0135] The message type of the first message is one of the following: a broadcast message, a paging message, or a paging-like message.

[0136] Exemplarily, the first message may be a broadcast message, in which case the broadcast message may also be a sidelink broadcast message or a second group service command message. Exemplarily, the first message may be a paging message or a paging-like message, which carries the group service identifier of the first group and one or more commands corresponding to the first group. Additionally, in this case, the paging message may also be a sidelink paging message, and the paging-like message may also be a sidelink paging-like message.

[0137] In one embodiment, the core network device sends the second message, including: the core network device sends the second message to a first access network device, wherein the first access network device is determined based on location information corresponding to the first group.

[0138] The manner in which the core network device determines the first access network device is similar to the manner in which the core network device determines the second access network device in the aforementioned embodiment, and is not described again.

[0139] In this embodiment, after the core network device selects the first access network device, it can send a second message to the first access network device. Here, the core network device generates the second message in the same manner as in the above embodiment and will not be described in detail.

[0140] It should be pointed out that the function of the first access network device is different from that of the second access network device in the direct connection mode of the aforementioned embodiment. The function of the second access network device in the aforementioned embodiment is to receive a second message carrying the group service identifier of the first group and one or more commands corresponding to the first group, and directly broadcast the first message carrying the group service identifier of the first group and one or more commands corresponding to the first group to the AIoT device (including the second device and one or more AIoT devices in the first group); while in this embodiment, although the first access network device also needs to receive the second message carrying the group service identifier of the first group and one or more commands corresponding to the first group, the first access network device does not directly broadcast the first message carrying the group service identifier of the first group and one or more commands corresponding to the first group to the AIoT device.

[0141] Specifically, after the first access network device receives the second message sent by the core network device, the processing of the first access network device may include: the first access network device sends a third message to the first device (i.e., the terminal), wherein the third message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0142] Accordingly, before the first device sends the first message, the method further includes: the first device receiving the group service identifier of the first group and one or more commands corresponding to the first group. The method further includes: the first device receiving the group service identifier of the first group and one or more commands corresponding to the first group, wherein the method further includes: the first device receiving a third message sent by the first access network device, wherein the third message carries the group service identifier of the first group and one or more commands corresponding to the first group. In other words, the terminal receives the third message sent by the first access network device.

[0143] Optionally, the first access network device may also select a first device, i.e., a terminal. The first access network device may select a terminal in a manner such that: the first access network device selects the terminal (i.e., the first device) from one or more candidate terminals with the first capability that the first access network device manages. For example, when the first access network device manages only one candidate terminal with the first capability, the first access network device selects the candidate terminal as the terminal (i.e., the first device); or, when the first access network device manages multiple candidate terminals with the first capability, the first access network device selects any one of the multiple candidate terminals as the terminal (i.e., the first device).

[0144] The third message may be an AS (Access Stratum) message.

[0145] Exemplarily, the message type of the third message is one of the following: proprietary signaling, broadcast message, paging message, and paging-like message.

[0146] For example, the third message may be proprietary signaling or proprietary signaling corresponding to the terminal. In this case, the first access network device may carry the group service identifier of the first group and one or more commands corresponding to the first group in the proprietary signaling and send the message to the terminal. For example, the third message may be a paging message or a paging-like message. The first access network device may carry the group service identifier of the first group and one or more commands corresponding to the first group in the paging message or the paging-like message and send the message to the terminal. For example, the third message may be a broadcast message. The first access network device may carry the group service identifier of the first group and one or more commands corresponding to the first group in the broadcast message and send the message to the terminal.

[0147] Furthermore, after the terminal receives the third message sent by the first access network device, it can execute the processing of sending the first message. The content carried by the first message can be consistent with the third message, that is, the first message can also carry the group service identifier of the first group and one or more commands corresponding to the first group.

[0148] Accordingly, the second device receiving the first message sent by the first device may refer to the second device receiving the first message sent by the terminal. The first message is one of the following: a broadcast message, a paging message, or a quasi-paging message. The relevant description of the terminal sending the first message is the same as that in the previous embodiment and is not repeated here.

[0149] In some possible implementations, one or more commands corresponding to the first group may be generated by the first device. Furthermore, the first message is also actively generated and sent by the first device. This embodiment does not limit the triggering conditions or triggering methods for the first device to generate or send the first message. In other words, the first device (which may be a second access network device or a terminal) can directly execute the processing of sending the corresponding command to one or more devices in the first group.

[0150] In some possible implementations, after the second device receives the first message sent by the first device, the further step further includes: when the group service identifier of the group to which the second device belongs is consistent with the group service identifier of the first group, the second device executes a command corresponding to the second device, wherein the command corresponding to the second device is one of the one or more commands corresponding to the first group.

[0151] In this embodiment, the first device may be a second access network device or a terminal. That is, the following description of the second device in this embodiment may apply to the second device accessing the network in a direct connection mode or an indirect connection mode. The first device referred to in each description provided in this embodiment may be a second access network device or a terminal, and will not be described separately below.

[0152] Among them, the relevant description of the group service identifier is similar to that of the aforementioned embodiment and will not be repeated. That is to say, the group service identifier of the group where the second device is located may include at least one of the following: the Group ID of the group where the second device is located, the Group Session ID of the group where the second device is located, the Group Service ID of the group where the second device is located, the slice identifier corresponding to the group where the second device is located, the DNN corresponding to the group where the second device is located, and the Device ID Mask corresponding to the group where the second device is located. It should be pointed out that the type of the group service identifier of the group where the second device is located and the group service identifier of the first group should be the same, for example, the group service identifiers are all Group IDs, or are all Group Session IDs, etc., and no exhaustive or limiting list is made here.

[0153] The second device may be the first AIoT device, which may be any AIoT device in the first group, or may not belong to the first group. Therefore, after receiving the first message, the second device needs to determine whether it belongs to the first group. If it determines that it belongs to the first group, it executes the command corresponding to the second device.

[0154] Specifically, the processing performed by the second device after receiving the first message may include: the second device determining whether the group service identifier of the group to which the second device belongs is consistent with the group service identifier of the first group carried in the first message; if the group service identifier of the group to which the second device belongs is consistent with the group service identifier of the first group, the second device executing the command corresponding to the second device. Furthermore, the processing may also include: if the group service identifier of the group to which the second device belongs is inconsistent with the group service identifier of the first group, the second device performing no processing.

[0155] Here, the second device determines whether the group service identifier of the group to which it belongs is consistent with the group service identifier of the first group carried in the first message. That is, the second device determines whether it belongs to the first group based on whether the group service identifier of the group to which it belongs is consistent with the group service identifier of the first group carried in the first message. Furthermore, if the group service identifier of the group to which the second device belongs is consistent with the group service identifier of the first group, the second device can determine that it belongs to the first group and then execute the command corresponding to the second device. Conversely, if the group service identifier of the group to which the second device belongs is inconsistent with the group service identifier of the first group, the second device determines that it does not belong to the first group and the second device does not need to execute the command corresponding to the second device.

[0156] Before the second device executes the command corresponding to the second device, the method may further include: the second device determining a command corresponding to the second device from one or more commands corresponding to the first group.

[0157] Optionally, the one or more commands corresponding to the first group include: a first command corresponding to the first group, which is a command to be executed by each device in the first group; and a command corresponding to the second device is the first command corresponding to the first group.

[0158] In this case, the second device may determine the command corresponding to the second device based on the one or more commands corresponding to the first group: the second device may directly determine the first command corresponding to the first group as the command corresponding to the second device.

[0159] Optionally, the one or more commands corresponding to the first group include: a plurality of second commands corresponding to the first group, wherein different second commands among the plurality of second commands corresponding to the first group are commands to be executed by different devices in the first group;

[0160] The command corresponding to the second device is a second command corresponding to the second device among the multiple second commands corresponding to the first group.

[0161] In this case, since different second commands corresponding to the first group are for different devices in the first group, the second device needs to further determine the second command corresponding to the second device from the multiple second commands corresponding to the first group as the command corresponding to the second device.

[0162] In some possible examples, each of the multiple second commands corresponding to the first group further corresponds to, is bound to, or is associated with an identifier or number of a different device in the first group. In this example, the second device determines the command corresponding to the second device based on the one or more commands corresponding to the first group. This can be done by: the second device selects the second command corresponding to its own number or identifier from the multiple second commands corresponding to the first group based on its own number or identifier, and uses the selected second command as the command corresponding to the second device.

[0163] In some possible examples, the order in which the multiple second commands corresponding to the first group are arranged in the message can be used to determine the device in the first group to which each of the multiple second commands corresponds. In this example, the second device can determine the command corresponding to the second device based on the one or more commands corresponding to the first group by selecting the second command corresponding to itself from the multiple second commands based on the first correspondence, and using the selected second command as the command corresponding to the second device. The description of the first correspondence is the same as in the previous embodiment and is not repeated here.

[0164] The second device executes the command corresponding to the second device, which may include at least one of the following: when the command corresponding to the second device includes a read command, the second device reads the corresponding content based on the read command, and the second device reports the read content; when the command corresponding to the second device includes a write command, the second device locally writes the specific content indicated by the write command (or indicates writing).

[0165] Optionally, the second device reporting the read content may refer to: the second device reporting the read content to the first device.

[0166] Correspondingly, the processing of the first device after sending the first message may further include: the first device receives the read content reported by the second device, and sends the read content reported by the second device to the core network device.

[0167] The processing of the core network device after sending the second message may include: the core network device receiving the read content reported by the second device sent by the first device, and sending the read content reported by the second device to the AF. The core network device sending the read content reported by the second device to the AF may include: the core network device sending the read content reported by the second device directly to the AF; or the core network device sending the read content reported by the second device to the AF via the NEF.

[0168] Optionally, after the second device locally writes the specific content indicated by the write command (or instructs writing), it may also include: the second device sends a response message to the first device, and the response message can be used to indicate that the second device has completed writing.

[0169] Correspondingly, the processing of the first device after sending the first message may also include: the first device receives a response message sent by the second device, and sends the response message of the second device to the core network device.

[0170] The processing of the core network device after sending the second message may include: the core network device receiving the response message of the second device sent by the first device, and sending the response message of the second device to the AF. The core network device sending the response message of the second device to the AF may include: the core network device sending the response message of the second device directly to the AF; or the core network device sending the response message of the second device to the AF through the NEF.

[0171] It should be pointed out that after any AIoT device in the first group receives the first message sent by the first device, the processing performed is the same as that of the second device, so they are not described one by one; in addition, after any AIoT device that does not belong to the first group receives the first message sent by the first device, the processing performed is also the same as that of the second device, and they are not described one by one here.

[0172] In conjunction with Figure 9, an exemplary description of the processing scenario of the direct connection mode (or direct connection method) of the above embodiment is given. In the scenario shown in Figure 9, both devices (i.e., Device 1 and Device 2 in Figure 9) are AIoT devices, and any one of the two devices can be the first AIoT device or the second device in the above embodiment. For example, Device 1 can be the second device in the above embodiment, or Device 2 can be the second device in the above embodiment. The first group can include Device 1 and / or Device 2, gNB is the first device in the above embodiment (the first device is specifically the second access network device), and AMF is the core network device in the above embodiment. Specifically, the following processing steps are included:

[0173] In step 900, Device 1 and Device 2 pre-configure information for group communication (i.e., Device 1 and Device 2 respectively pre-configure the group service identifiers of their respective groups), where the information for group communication can be represented by a group ID, a group session ID, a group service ID, an S-NSSAI, a DNN, or a Device ID Mask.

[0174] In step 901, the AF sends a group service command message to the AMF (or the AF sends it to the AMF through the NEF). The group service command message is the sixth message in the aforementioned embodiment. The group service command message may carry group information and specific command content. The group information is the group service identifier of the first group in the aforementioned embodiment, and the command is one or more commands corresponding to the first group in the aforementioned embodiment (specifically, it may be the first command corresponding to the first group in the aforementioned embodiment).

[0175] Optionally, the group service command message may also carry possible location information of the AIoT Device (i.e., location information corresponding to the first group), where the location information may be a specific address location (or geographic location), or TAI, or cell ID.

[0176] In step 902, the AMF sends a group service command to the relevant gNB. The group service command carries group information and command details. The group service command sent by the AMF to the gNB may be carried by the second message in the aforementioned embodiment.

[0177] In this step, the AMF may determine the relevant gNB based on the TAI or Cell ID in the group service command message. Furthermore, if the location information carried in the group service command message is an address (or geographic location), the AMF may map the specific address to TAI or Cell ID information and then determine the gNB based on the TAI or Cell ID. The specific manner in which the AMF determines the relevant gNB is the same as in the previous embodiment and is not further described.

[0178] Step 903: The gNB sends a group service command.

[0179] The group service command may be carried by the first message in the aforementioned embodiment. As described in the aforementioned embodiment, the first message may be a broadcast message, a paging message, or a paging-like message. Therefore, the gNB may send the group service command by: sending a paging message (as shown in Figure 9); or sending a paging-like message (as shown in Figure 9); or broadcasting the group service command. In this step, if the gNB broadcasts the group service command, the group information and command details are directly included in the group service command. If the gNB sends the group service command via a paging or paging-like message, the group information and command details are included in the paging or paging-like message (as shown in Figure 9).

[0180] In step 904, if the received group information is consistent with the pre-configured information for group communication, Device 1 processes the command based on the specific content of the command. The processing by Device 1 based on the specific content of the command may include: Device 1 performing an operation according to the command or reporting some information.

[0181] It should be understood that step 904 only illustrates the processing performed by Device 1 when the received group information is consistent with the pre-configured information for group communication. In actual processing, when Device 1 executes step 904, it may specifically include: Device 1 determines whether the received group information is consistent with the pre-configured information for group communication; if so, it processes the information based on the specific content of the command; if not, it does not process the information.

[0182] It should also be noted that FIG9 illustrates only step 904 executed by Device 1 for the sake of brevity. In fact, Device 2 will also perform a similar process as that of Device 1 in step 904, but the illustration is not repeated for the sake of brevity.

[0183] Another exemplary description of the processing scenario of the non-direct connection mode (or non-direct connection method) of the above embodiment is provided in conjunction with Figure 10. In the scenario shown in Figure 10, the device is the first AIoT device, i.e., the second device, the UE is the first device in the above embodiment, the gNB is the first access network device in the above embodiment, and the AMF is the core network device in the above embodiment. Specifically, the processing steps include the following:

[0184] In step 1000, the device pre-configures information for group communication (i.e., pre-configures the group service identifier of the group in which it is located), where the information for group communication can be represented by group ID, group session ID, group service ID, S-NSSAI, DNN, or Device ID Mask.

[0185] Step 1001 is the same as step 901 and will not be described again.

[0186] In step 1002, the AMF sends a group service command to the relevant gNB. The group service command carries group information and command details. The group service command sent by the AMF to the gNB may be carried by the second message in the aforementioned embodiment.

[0187] Here, step 1002 is similar to step 902, except that the gNB selected in step 1002 does not interact directly with the device (i.e., indirect connection mode), while the gNB selected in step 902 interacts directly with the gNB (i.e., direct connection mode).

[0188] Step 1003: The gNB sends a group service command to the UE.

[0189] Specifically, the group service command sent by the gNB in ​​step 1003 can be carried by the third message in the aforementioned embodiment.

[0190] Here, the third message can be one of the following: dedicated signaling, a broadcast message, a paging message, or a paging-like message. For example, the gNB can send the group service command via dedicated signaling, or any of the following: broadcast, paging, or paging-like messages. If the gNB sends the group service command message via broadcast, the message can directly carry the group information and command details. Alternatively, if the gNB sends the group service command message via paging or paging-like messages, the paging or paging-like messages can carry the group information and command details. Alternatively, if the gNB sends the group service command message via UE-specific signaling, the dedicated signaling can carry the group information and command details.

[0191] Step 1004: The UE broadcasts a group service command.

[0192] The group service command may be carried by the first message in the aforementioned embodiment. As described in the aforementioned embodiment, the first message may be one of a broadcast message, a paging message, and a paging-like message. Therefore, the UE may send the group service command in the following ways: the UE sends the group service command by sending a paging message (as shown in FIG10 ); or, the UE may send the group service command through a paging-like message; or, the UE broadcasts the group service command. In this step, if the UE broadcasts the group service command, the group information and the specific content of the command are directly carried in the group service command; if the UE sends the group service command through a paging or paging-like message, the group information and the specific content of the command are carried in the paging or paging-like message (as shown in FIG10 ).

[0193] In step 1005, if the received group information is consistent with the pre-configured information for group communication, the device processes the command based on the specific content of the command. The processing based on the specific content of the command may include: the device performing an operation according to the command or reporting some information.

[0194] It should be understood that step 1005 merely illustrates the processing performed by the device when the received group information is consistent with the pre-configured information for group communication. In actual processing, when the device executes step 1005, the device may specifically determine whether the received group information is consistent with the pre-configured information for group communication. If so, the device performs processing based on the specific content of the command; if not, no processing is performed.

[0195] Optionally, in the process illustrated in Figure 10, the AMF may also send a group service command through the NAS signaling of the UE, that is, step 1002 may be replaced by the AMF sending a group service command to the relevant UE according to the TAI or cell id, and then step 1003 does not need to be executed and the UE directly executes step 1004.

[0196] In some possible implementations, the first message may carry a group service identifier of each group in a plurality of groups and one or more commands corresponding to each group, wherein the plurality of groups includes the first group.

[0197] That is, in addition to carrying the group service identifier of the first group and one or more commands corresponding to the first group, the first message can also carry the group service identifier of each other group in one or more other groups and one or more commands corresponding to each other group.

[0198] The description of the group service identifier is the same as that in the above embodiment, and will not be repeated. The one or more commands corresponding to each group are also similar to the description of the one or more commands corresponding to the first group in the above embodiment, and will not be repeated.

[0199] In this embodiment, the core network device processes the sixth message similarly to the preceding embodiment. The only difference is that the sixth message carries the group service identifier of each of the multiple groups, one or more commands corresponding to each group, and the multiple groups include the first group. Furthermore, the sixth message may also carry location information corresponding to each group.

[0200] In this embodiment, the core network device sends a second message before the first device sends the first message, and the first device receives the second message sent by the core network device. The related processing is similar to the above embodiment, except that the second message carries the group service identifier of each group in the multiple groups and one or more commands corresponding to each group, and the multiple groups include the first group. In addition, the first device receives the third message sent by the first access network device and other related processing is similar to the above embodiment, except that the third message carries the group service identifier of each group in the multiple groups and one or more commands corresponding to each group, and the multiple groups include the first group.

[0201] Alternatively, in this implementation, the first message may also be actively generated and sent by the first device, which will not be described in detail here.

[0202] Still taking any AIoT device as the second device as an example, after the second device receives the first message sent by the first device, it also includes: when the group service identifier of the group where the second device is located is consistent with the group service identifier of the first group among the multiple groups, the second device executes the command corresponding to the second device, wherein the command corresponding to the second device is determined based on one or more commands corresponding to the first group.

[0203] Specifically, the processing after the second device receives the first message may include: the second device determines whether the group service identifier of the group to which it belongs is consistent with the group service identifier of any one of the multiple groups carried by the first message; if the group service identifier of the group to which the second device belongs is consistent with the group service identifier of the first group, the second device determines the command corresponding to the second device from the one or more commands corresponding to the first group, and executes the command corresponding to the second device. In addition, it may also include: if the group service identifier of the group to which the second device belongs is inconsistent with the group service identifier of each group in the multiple groups, the second device does not process. The processing method for the second device to determine the command corresponding to the second device from the one or more commands corresponding to the first group is the same as the above embodiment and will not be repeated.

[0204] The processing after the second device executes the corresponding command is the same as that in the above embodiment and will not be elaborated on.

[0205] In some possible implementations, the group service identifier of the group to which the second device belongs may be pre-configured, or may be obtained by the second device during a registration process.

[0206] In one embodiment, the group service identifier of the group in which the second device is located is preconfigured. It should be noted that the group service identifier of the group in which the second device is located may be preconfigured on both the second device and the network side.

[0207] The timing for pre-configuring the group service identifier of the group to which the second device belongs is within the scope of protection of this embodiment as long as it is before the second device receives the first message sent by the first device. The method for pre-configuring the group service identifier of the group to which the second device belongs can be pre-written into the second device or using other pre-configuration methods, which are not limited or exhaustive in this embodiment.

[0208] In one embodiment, before the second device receives the first message sent by the first device, the method further includes: the second device receives a fourth message sent by the core network device, wherein the fourth message carries a group service identifier of the group to which the second device belongs.

[0209] Correspondingly, before the core network device sends the second message, the method further includes: the core network device sends a fourth message to the second device, wherein the fourth message carries the group service identifier of the group to which the second device belongs.

[0210] This embodiment does not limit the method for generating or determining the group service identifier of the group to which the second device belongs.

[0211] Optionally, before the second device receives the fourth message sent by the core network device, the process further includes: the second device sends a fifth message to the core network device, wherein the fifth message is used for registration and the fifth message carries the identifier of the second device. Correspondingly, before the core network device sends the fourth message to the second device, the process further includes: the core network device receives the fifth message sent by the second device, wherein the fifth message is used for registration and the fifth message carries the identifier of the second device.

[0212] The fifth message may be one of the following: a registration request message or a registration update message. Preferably, the fifth message may be a registration request message during an initial registration process. For example, in addition to carrying the identifier of the second device, the fifth message may also carry a registration type, which may be an initial registration.

[0213] After the core network device receives the fifth message sent by the second device and before the core network device sends the fourth message to the second device, it may also include: the core network device sends a request to obtain the contract data of the second device to the UDM or the service provider's database, and the acquisition request may carry the identifier of the second device; the core network device receives the contract data of the second device returned by the UDM or the service provider's database (which may be carried by the contract data acquisition response); the core network device determines the group service identifier of the group to which the second device belongs based on the contract data of the second device.

[0214] Optionally, the contract data of the second device may include the group service identifier of the group to which the second device belongs; accordingly, the core network device determines the group service identifier of the group to which the second device belongs based on the contract data of the second device, which may be: the core network device extracts the group service identifier of the group to which the second device belongs from the contract data of the second device.

[0215] The fourth message may be a registration acceptance message.

[0216] Optionally, the second device and the core network device may interact through NAS messages. For example, the fifth message and the fourth message may both be NAS messages.

[0217] Optionally, when the second device accesses the network in direct connection mode, the interaction between the second device and the core network device can be forwarded through the second access network device, that is, the aforementioned fifth message and / or fourth message can both be forwarded between the second device and the core network device through the second access network device.

[0218] Optionally, when the second device accesses the network in a non-direct connection mode, the interaction between the second device and the core network device can be forwarded through the terminal and / or the first access network device, that is, the aforementioned fifth message and / or fourth message can both be forwarded between the second device and the core network device through the terminal and / or the first access network device.

[0219] In conjunction with Figure 11, an exemplary description of the process of obtaining the group service identifier in the above embodiment is given. The scenario shown in Figure 11 is that if the device (i.e., the second device) is in direct connection mode and the device is not configured with group information, the group information is allocated and updated during the registration process, specifically including:

[0220] In step 1101, the device initiates a registration process with a core network element (AMF, for example). Specifically, the device sends a registration request (i.e., the fifth message in the aforementioned embodiment) to the AMF. The registration request carries the device's identification information and the registration type, which is initial registration.

[0221] Step 1102: After receiving the registration request, AMF sends a request to the UDM to obtain the subscription data of the Device.

[0222] In step 1103, the UDM (or the service provider's database) returns the device's subscription data to the AMF (which can be carried in the subscription data acquisition response).

[0223] In step 1104, the AMF returns a registration acceptance message (i.e., the fourth message in the aforementioned embodiment) to the device, which carries the group service identifier (i.e., the group service identifier of the group to which the device belongs). This group service identifier can be used for communication processing in the aforementioned examples (such as the examples provided in Figures 9 or 10).

[0224] It should also be noted with respect to Figure 11 that the Device illustrated in Figure 11 accesses the network in a direct connection manner (or mode), so the interaction between the Device and the AMF can be forwarded through the gNB.

[0225] In conjunction with Figure 12, another exemplary description of the process of obtaining the group service identifier in the above embodiment is provided. The scenario shown in Figure 12 is that if the device (i.e., the second device) is in non-direct connection mode and the device is not configured with group information, the group information is allocated and updated during the registration process, specifically including:

[0226] In step 1201, the device initiates registration with the core network element (AMF, for example). Step 1201 is similar to step 1101, except that the device can initiate registration with the AMF through the UE and / or gNB (i.e., send a registration request). Alternatively, step 1201 can also be the process of the device directly initiating registration with the AMF (i.e., sending a registration request).

[0227] Steps 1202 to 1203 are the same as steps 1102 to 1103 in the above example and are not described again.

[0228] In step 1204, the AMF returns a Registration Accept to the Device, which carries the group service identifier (i.e., the group service identifier of the group to which the Device belongs). Step 1204 is similar to step 1104, except that the AMF may return the Registration Accept to the Device through the UE and / or gNB. Alternatively, in step 1204, the AMF may directly return the Registration Accept to the Device.

[0229] As can be seen, by adopting the above solution, the first device can send a first message carrying the group service identifier of the first group and one or more commands corresponding to the first group. In this way, by sending the first message, the first device can enable each device in the first group to obtain the commands to be executed. This can improve the communication efficiency between the first device and each device in the first group, and further improve the processing efficiency of the commands to be executed by each device in the first group.

[0230] FIG13 is a schematic diagram of the composition structure of a first device according to an embodiment of the present application, including:

[0231] The first communication unit 1301 is configured to send a first message, where the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

[0232] The one or more commands corresponding to the first group include: a first command corresponding to the first group, where the first command corresponding to the first group is a command that needs to be executed by each device in the first group.

[0233] The one or more commands corresponding to the first group include: a plurality of second commands corresponding to the first group, wherein different commands in the plurality of second commands corresponding to the first group are commands to be executed by different devices in the first group.

[0234] The group service identifier includes at least one of the following: a group identifier, a group session identifier, a group service identifier, a slice identifier, a data network name DNN, and a device identifier mask.

[0235] The first message is one of the following: a broadcast message, a paging message, or a paging-like message.

[0236] The first communication unit is configured to receive the group service identifier of the first group and one or more commands corresponding to the first group.

[0237] The first communication unit is used to perform one of the following: receiving a second message sent by a core network device, wherein the second message carries the group service identifier of the first group and one or more commands corresponding to the first group; receiving a third message sent by a first access network device, wherein the third message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0238] The first device is a second access network device or a terminal.

[0239] The first group includes one or more devices, each of which is an environment acquisition Internet of Things (AIoT) device.

[0240] FIG14 is a schematic diagram of the structure of a second device according to an embodiment of the present application, including:

[0241] The second communication unit 1401 is configured to receive a first message sent by a first device, where the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

[0242] As shown in FIG14 , the second device further includes:

[0243] The second processing unit 1402 is configured to execute a command corresponding to the second device when the group service identifier of the group to which the second device belongs is consistent with the group service identifier of the first group, wherein the command corresponding to the second device is one of the one or more commands corresponding to the first group.

[0244] The one or more commands corresponding to the first group include: a first command corresponding to the first group, which is a command to be executed by each device in the first group; and a command corresponding to the second device is the first command corresponding to the first group.

[0245] The one or more commands corresponding to the first group include: multiple second commands corresponding to the first group, wherein different second commands among the multiple second commands corresponding to the first group are commands to be executed by different devices in the first group; and the command corresponding to the second device is the second command corresponding to the second device among the multiple second commands corresponding to the first group.

[0246] The first message is one of the following: a broadcast message, a paging message, or a paging-like message.

[0247] The group service identifier of the group to which the second device belongs is preconfigured.

[0248] The second communication unit is configured to receive a fourth message sent by a core network device, wherein the fourth message carries a group service identifier of a group to which the second device belongs.

[0249] The second communication unit is used to send a fifth message to the core network device, wherein the fifth message is used for registration and carries an identifier of the second device.

[0250] The group service identifier includes at least one of the following: a group identifier, a group session identifier, a group service identifier, a slice identifier, a data network name DNN, and a device identifier mask.

[0251] The second device is an AIoT device for collecting Internet of Things in the first environment; the first device is a second access network device or terminal.

[0252] FIG15 is a schematic diagram of the structure of a core network device according to an embodiment of the present application, including:

[0253] The third communication unit 1501 is configured to send a second message, where the second message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0254] The third communication unit is configured to receive a sixth message, wherein the sixth message carries the group service identifier of the first group and one or more commands corresponding to the first group.

[0255] The sixth message also carries location information corresponding to the first group, wherein the location information includes at least one of the following: relevant information of a tracking area TA, relevant information of a cell, and a geographical location.

[0256] The third communication unit is used to perform one of the following: sending the second message to the first access network device, wherein the first access network device is determined based on the location information corresponding to the first group; sending the second message to the first device, wherein the first device is determined based on the location information corresponding to the first group, and the first device is a second access network device or terminal.

[0257] The one or more commands corresponding to the first group include: a first command corresponding to the first group, where the first command corresponding to the first group is a command that needs to be executed by each device in the first group.

[0258] The one or more commands corresponding to the first group include: a plurality of second commands corresponding to the first group, wherein different commands in the plurality of second commands corresponding to the first group are commands to be executed by different devices in the first group.

[0259] The first group includes one or more devices, each of which is an environment acquisition Internet of Things (AIoT) device.

[0260] The third communication unit is configured to send a fourth message to the second device, wherein the fourth message carries a group service identifier of the group to which the second device belongs.

[0261] The third communication unit is configured to receive a fifth message sent by the second device, wherein the fifth message is used for registration and carries an identifier of the second device.

[0262] The second device is an AIoT device that collects information about the Internet of Things (IoT) in the first environment.

[0263] The group service identifier includes at least one of the following: a group identifier, a group session identifier, a group service identifier, a slice identifier, a data network name DNN, and a device identifier mask.

[0264] The device of the embodiment of the present application can realize the corresponding functions of each device in the aforementioned authentication method embodiment. The corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the first device, or the second device, or the core network device can be found in the corresponding description in the above method embodiment, which will not be repeated here. It should be noted that the functions described in the first device, or the second device, or the various modules (sub-module, unit or component, etc.) in the core network device of the application embodiment can be implemented by different modules (sub-module, unit or component, etc.) or by the same module (sub-module, unit or component, etc.).

[0265] Figure 16 is a schematic structural diagram of a communication device 1600 according to an embodiment of the present application. The communication device 1600 includes a processor 1610. The processor 1610 can retrieve and execute a computer program from a memory to enable the communication device 1600 to implement the method according to the embodiment of the present application. In one possible implementation, the communication device 1600 may also include a memory 1620. The processor 1610 can retrieve and execute a computer program from the memory 1620 to enable the communication device 1600 to implement the method according to the embodiment of the present application. The memory 1620 may be a separate device independent of the processor 1610 or integrated into the processor 1610. In one possible implementation, the communication device 1600 may also include a transceiver 1630. The processor 1610 can control the transceiver 1630 to communicate with other devices. Specifically, the transceiver 1630 can send information or data to other devices or receive information or data sent by other devices. The transceiver 1630 may include a transmitter and a receiver. The transceiver 1630 may further include an antenna, which may be one or more antennas.

[0266] In one possible implementation, the communication device 1600 may be the first device, or the second device, or the core network device of the embodiment of the present application, and the communication device 1600 may implement the corresponding processes implemented by the first device, or the second device, or the core network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0267] Figure 17 is a schematic block diagram of a chip 1700 according to an embodiment of the present application. Chip 1700 includes a processor 1710, which can access and execute computer programs from a memory to implement the methods in the embodiments of the present application. In one possible implementation, chip 1700 may also include a memory 1720. Processor 1710 can access and execute computer programs from the memory 1720 to implement the methods performed by the first device, the second device, or the core network device in the embodiments of the present application. Memory 1720 may be a separate device independent of processor 1710 or integrated into processor 1710. In one possible implementation, chip 1700 may also include an input interface 1730. Processor 1710 may control input interface 1730 to communicate with other devices or chips, specifically, to obtain information or data sent by other devices or chips. In one possible implementation, chip 1700 may also include an output interface 1740. The processor 1710 may control the output interface 1740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0268] In one possible implementation, the chip can be applied to the first device, or the second device, or the core network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first device, or the second device, or the core network device in each method of the embodiment of the present application. For the sake of brevity, they are not repeated here. It should be understood that the chip mentioned in the embodiment of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc. The processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or other programmable logic device, transistor logic device, discrete hardware component, etc. Among them, the general-purpose processor mentioned above can be a microprocessor or any conventional processor, etc. The memory mentioned above can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM). It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application can also be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DR RAM), etc. That is, the memory in the embodiment of the present application is intended to include but is not limited to these and any other suitable types of memory.

[0269] Figure 18 is a schematic block diagram of a communication system 1800 according to an embodiment of the present application. The communication system 1800 includes a first device 1810, a second device 1820, and a core network device 1830. The first device 1810 can be used to implement the corresponding functions implemented by the first device in the above-described method. The second device 1820 can be used to implement the corresponding functions implemented by the second device in the above-described method. The core network device 1830 can be used to implement the corresponding functions implemented by the core network device in the above-described method. For the sake of brevity, this description will not be repeated here.

[0270] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0271] It should be understood that in the various embodiments of the present application, the size of the sequence number of each process mentioned above does not mean the order of execution, and 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 embodiment of the present application. Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the present application, which should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claim.

Claims

1. A communication method, comprising: The first device sends a first message, where the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

2. The method according to claim 1, wherein The one or more commands corresponding to the first group include: a first command corresponding to the first group, where the first command corresponding to the first group is a command that needs to be executed by each device in the first group.

3. The method according to claim 1, wherein The one or more commands corresponding to the first group include: a plurality of second commands corresponding to the first group, wherein different commands in the plurality of second commands corresponding to the first group are commands to be executed by different devices in the first group.

4. The method according to any one of claims 1 to 3, wherein: The group service identifier includes at least one of the following: a group identifier, a group session identifier, a group service identifier, a slice identifier, a data network name DNN, and a device identifier mask.

5. The method according to any one of claims 1 to 4, wherein: The first message is one of the following: a broadcast message, a paging message, or a paging-like message.

6. The method according to any one of claims 1 to 5, wherein: Before the first device sends the first message, the method further includes: The first device receives the group service identifier of the first group and one or more commands corresponding to the first group.

7. The method according to claim 6, wherein: The first device receives the group service identifier of the first group and one or more commands corresponding to the first group, including one of the following: The first device receives a second message sent by a core network device, wherein the second message carries a group service identifier of the first group and one or more commands corresponding to the first group; The first device receives a third message sent by the first access network device, wherein the third message carries the group service identifier of the first group and one or more commands corresponding to the first group.

8. The method according to any one of claims 1 to 7, wherein: The first device is a second access network device or a terminal.

9. The method according to any one of claims 1 to 8, wherein: The first group includes one or more devices, each of which is an environment acquisition Internet of Things (AIoT) device.

10. A communication method, comprising: The second device receives a first message sent by the first device, where the first message carries a group service identifier of the first group and one or more commands corresponding to the first group.

11. The method according to claim 10, wherein: After the second device receives the first message sent by the first device, the method further includes: When the group service identifier of the group to which the second device belongs is consistent with the group service identifier of the first group, the second device executes a command corresponding to the second device, wherein the command corresponding to the second device is one of the one or more commands corresponding to the first group.

12. The method according to claim 11, wherein The one or more commands corresponding to the first group include: a first command corresponding to the first group, the first command corresponding to the first group being a command to be executed by each device in the first group; The command corresponding to the second device is the first command corresponding to the first group.

13. The method according to claim 11, wherein The one or more commands corresponding to the first group include: a plurality of second commands corresponding to the first group, wherein different second commands among the plurality of second commands corresponding to the first group are commands to be executed by different devices in the first group; The command corresponding to the second device is a second command corresponding to the second device among the multiple second commands corresponding to the first group.

14. The method according to any one of claims 10 to 13, wherein: The first message is one of the following: a broadcast message, a paging message, or a paging-like message.

15. The method according to any one of claims 11 to 13, wherein: The group service identifier of the group to which the second device belongs is preconfigured.

16. The method according to any one of claims 11 to 13, wherein: Before the second device receives the first message sent by the first device, the method further includes: The second device receives a fourth message sent by the core network device, wherein the fourth message carries a group service identifier of the group to which the second device belongs.

17. The method according to claim 16, wherein Before the second device receives the fourth message sent by the core network device, the method further includes: The second device sends a fifth message to the core network device, where the fifth message is used for registration and carries an identifier of the second device.

18. The method according to any one of claims 10 to 17, wherein: The group service identifier includes at least one of the following: a group identifier, a group session identifier, a group service identifier, a slice identifier, a data network name DNN, and a device identifier mask.

19. The method according to any one of claims 10 to 18, wherein: The second device is an AIoT device for collecting Internet of Things in the first environment; the first device is a second access network device or terminal.

20. A communication method, comprising: The core network device sends a second message, where the second message carries the group service identifier of the first group and one or more commands corresponding to the first group.

21. The method according to claim 20, wherein Before the core network device sends the second message, the method further includes: The core network device receives a sixth message, where the sixth message carries the group service identifier of the first group and one or more commands corresponding to the first group.

22. The method according to claim 21, wherein The sixth message also carries location information corresponding to the first group, wherein the location information includes at least one of the following: relevant information of a tracking area TA, relevant information of a cell, and a geographical location.

23. The method according to claim 22, wherein The core network device sends a second message, including one of the following: The core network device sends the second message to the first access network device, wherein the first access network device is determined based on the location information corresponding to the first group; The core network device sends the second message to a first device, wherein the first device is determined based on location information corresponding to the first group, and the first device is a second access network device or a terminal.

24. The method according to any one of claims 20 to 23, wherein: The one or more commands corresponding to the first group include: a first command corresponding to the first group, where the first command corresponding to the first group is a command that needs to be executed by each device in the first group.

25. The method according to claims 20-23, wherein: The one or more commands corresponding to the first group include: a plurality of second commands corresponding to the first group, wherein different commands in the plurality of second commands corresponding to the first group are commands to be executed by different devices in the first group.

26. The method according to any one of claims 20 to 25, wherein: The first group includes one or more devices, each of which is an environment acquisition Internet of Things (AIoT) device.

27. The method according to any one of claims 20 to 26, wherein: Before the core network device sends the second message, the method further includes: The core network device sends a fourth message to the second device, wherein the fourth message carries the group service identifier of the group to which the second device belongs.

28. The method according to claim 27, wherein Before the core network device sends the fourth message to the second device, the method further includes: The core network device receives a fifth message sent by the second device, wherein the fifth message is used for registration and carries an identifier of the second device.

29. The method according to claim 27 or 28, wherein The second device is an AIoT device that collects information about the Internet of Things (IoT) in the first environment.

30. The method according to any one of claims 20 to 29, wherein: The group service identifier includes at least one of the following: a group identifier, a group session identifier, a group service identifier, a slice identifier, a data network name DNN, and a device identifier mask.

31. A first device, comprising: The first communication unit is configured to send a first message, wherein the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

32. The first device according to claim 31, wherein The one or more commands corresponding to the first group include: a first command corresponding to the first group, where the first command corresponding to the first group is a command that needs to be executed by each device in the first group.

33. The first device according to claim 31, wherein The one or more commands corresponding to the first group include: a plurality of second commands corresponding to the first group, wherein different commands in the plurality of second commands corresponding to the first group are commands to be executed by different devices in the first group.

34. The first device according to any one of claims 31 to 33, wherein: The group service identifier includes at least one of the following: a group identifier, a group session identifier, a group service identifier, a slice identifier, a data network name DNN, and a device identifier mask.

35. The first device according to any one of claims 31 to 34, wherein: The first message is one of the following: a broadcast message, a paging message, or a paging-like message.

36. The first device according to any one of claims 31 to 35, wherein: The first communication unit is configured to receive the group service identifier of the first group and one or more commands corresponding to the first group.

37. The first device according to claim 36, wherein The first communication unit is used to perform one of the following: receiving a second message sent by a core network device, wherein the second message carries the group service identifier of the first group and one or more commands corresponding to the first group; receiving a third message sent by a first access network device, wherein the third message carries the group service identifier of the first group and one or more commands corresponding to the first group.

38. The first device according to any one of claims 31 to 37, wherein: The first device is a second access network device or a terminal.

39. The first device according to any one of claims 31 to 38, wherein: The first group includes one or more devices, each of which is an environment acquisition Internet of Things (AIoT) device.

40. A second device comprising: The second communication unit is configured to receive a first message sent by a first device, wherein the first message carries a group service identifier of a first group and one or more commands corresponding to the first group.

41. The second device according to claim 40, wherein The second device further includes: The second processing unit is configured to execute a command corresponding to the second device when the group service identifier of the group to which the second device belongs is consistent with the group service identifier of the first group, wherein the command corresponding to the second device is one of the one or more commands corresponding to the first group.

42. The second device according to claim 41, wherein The one or more commands corresponding to the first group include: a first command corresponding to the first group, the first command corresponding to the first group being a command to be executed by each device in the first group; The command corresponding to the second device is the first command corresponding to the first group.

43. The second device according to claim 41, wherein The one or more commands corresponding to the first group include: a plurality of second commands corresponding to the first group, wherein different second commands among the plurality of second commands corresponding to the first group are commands to be executed by different devices in the first group; The command corresponding to the second device is a second command corresponding to the second device among the multiple second commands corresponding to the first group.

44. The second device according to any one of claims 40 to 43, wherein: The first message is one of the following: a broadcast message, a paging message, or a paging-like message.

45. The second device according to any one of claims 41 to 43, wherein: The group service identifier of the group to which the second device belongs is preconfigured.

46. ​​The second device according to any one of claims 41 to 43, wherein: The second communication unit is configured to receive a fourth message sent by a core network device, wherein the fourth message carries a group service identifier of a group to which the second device belongs.

47. The second device according to claim 46, wherein The second communication unit is used to send a fifth message to the core network device, wherein the fifth message is used for registration and carries an identifier of the second device.

48. The second device according to any one of claims 40 to 47, wherein: The group service identifier includes at least one of the following: a group identifier, a group session identifier, a group service identifier, a slice identifier, a data network name DNN, and a device identifier mask.

49. The second device according to any one of claims 40 to 48, wherein: The second device is an AIoT device for collecting Internet of Things in the first environment; the first device is a second access network device or terminal.

50. A core network device, comprising: The third communication unit is configured to send a second message, wherein the second message carries the group service identifier of the first group and one or more commands corresponding to the first group.

51. The core network device according to claim 50, wherein: The third communication unit is configured to receive a sixth message, wherein the sixth message carries the group service identifier of the first group and one or more commands corresponding to the first group.

52. The core network device according to claim 51, wherein: The sixth message also carries location information corresponding to the first group, wherein the location information includes at least one of the following: relevant information of a tracking area TA, relevant information of a cell, and a geographical location.

53. The core network device according to claim 52, wherein: The third communication unit is used to perform one of the following: sending the second message to the first access network device, wherein the first access network device is determined based on the location information corresponding to the first group; sending the second message to the first device, wherein the first device is determined based on the location information corresponding to the first group, and the first device is a second access network device or terminal.

54. The core network device according to any one of claims 50 to 53, wherein: The one or more commands corresponding to the first group include: a first command corresponding to the first group, where the first command corresponding to the first group is a command that needs to be executed by each device in the first group.

55. The core network device according to claims 50-53, wherein: The one or more commands corresponding to the first group include: a plurality of second commands corresponding to the first group, wherein different commands in the plurality of second commands corresponding to the first group are commands to be executed by different devices in the first group.

56. The core network device according to any one of claims 50 to 55, wherein: The first group includes one or more devices, each of which is an environment acquisition Internet of Things (AIoT) device.

57. The core network device according to any one of claims 50 to 56, wherein: The third communication unit is configured to send a fourth message to the second device, wherein the fourth message carries a group service identifier of the group to which the second device belongs.

58. The core network device according to claim 57, wherein: The third communication unit is configured to receive a fifth message sent by the second device, wherein the fifth message is used for registration and carries an identifier of the second device.

59. The core network device according to claim 57 or 58, wherein: The second device is an AIoT device that collects information about the Internet of Things (IoT) in the first environment.

60. The core network device according to any one of claims 50 to 59, wherein: The group service identifier includes at least one of the following: a group identifier, a group session identifier, a group service identifier, a slice identifier, a data network name DNN, and a device identifier mask.

61. A first device comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, and the processor being used to call and run the computer program stored in the memory, so that the first device executes the method according to any one of claims 1 to 9.

62. A second device comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, and the processor being used to call and run the computer program stored in the memory so that the second device executes the method according to any one of claims 10 to 19.

63. A core network device, comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, and the processor being used to call and run the computer program stored in the memory so that the core network device executes the method as described in any one of claims 20 to 30.

64. A chip comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 9, or claims 10 to 19, or claims 20 to 30.

65. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 1 to 9, or claims 10 to 19, or claims 20 to 30.

66. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 9, or claims 10 to 19, or claims 20 to 30.

67. A computer program causing a computer to perform the method of any one of claims 1 to 9, or claims 10 to 19, or claims 20 to 30.

Images