Communication method and communication device

Abstract

A communication method and a communication device relate to the technical field of communication. The method comprises the following steps: determining first information, wherein the first information is used for the AIoT access network equipment to send second information to first AIoT core network equipment; and sending a first message, the first message comprising the second information and the first information, and the second information comprising data and / or signaling related to the AIoT service. According to the method provided by the invention, the first information is used for enabling the AIoT access network equipment to know which AIoT core network equipment the second information sent by the AIoT equipment is sent to, so that the AIoT access network equipment is helped to send the received second information to the related AIoT core network equipment.

Description

Technical Field

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

[0002] Ambient Internet of Things (AIoT) is an advanced Internet of Things (IoT) technology that emphasizes integrating IoT devices into the environment, making them part of the environment rather than independent entities. The goal of AIoT is to create a fully immersive environment where devices and sensors are virtually invisible, yet still provide a wealth of information and services.

[0003] AIoT includes four topologies: the first is bidirectional communication between AIoT devices and base stations; the second is communication between AIoT devices and base stations through intermediate nodes; the third is AIoT devices sending data or signaling to base stations and receiving data or signaling from auxiliary nodes, or AIoT devices receiving data or signaling from base stations and sending data or signaling to auxiliary nodes; and the fourth is bidirectional communication between AIoT devices and terminal devices.

[0004] In the first topology, when an AIoT access network device connects to multiple AIoT core network devices, the AIoT access network device cannot determine which AIoT core network device to send the information sent by the AIoT device to. Summary of the Invention

[0005] This application provides a communication method and a communication device, which enables AIoT access network devices to send received information to relevant AIoT core network devices.

[0006] In a first aspect, a communication method is provided, the method comprising: determining first information, the first information being used by the AIoT access network device to send second information to a first AIoT core network device; and sending a first message, the first message including the second information and the first information, the second information including data and / or signaling related to AIoT services.

[0007] For example, the communication method can be implemented by an AIoT device, or by modules, units, processors, circuits, chips, or chip systems included in the AIoT device.

[0008] The method provided in this application uses first information to enable the AIoT access network device to know which AIoT core network device to send the second information sent by the AIoT device to. Therefore, after the AIoT device determines the first information, it sends a first message to the AIoT access network device. The first message includes the first information and the second information, which helps the AIoT access network device to send the received second information to the relevant AIoT core network device.

[0009] In some embodiments, the first information includes at least one of the following: first identification information, second identification information, third identification information, or fourth identification information; the first identification information is used to identify the first AIoT core network device; the second identification information is used to identify the operator; the third identification information is used to identify the AIoT service; and the fourth identification information is used to identify the server.

[0010] In this embodiment of the application, the first identification information, the second identification information, the third identification information and the fourth identification information enable the AIoT access network device to know which AIoT core network device to send the second information sent by the AIoT device to.

[0011] It should be noted that AIoT core network equipment can be AMF, TMF, AIoT Function (AIoTF) network element, AIoT Management Function (AIoTMF) network element, or other core network element / node / device that supports / enables AIoT. The specific name is not limited.

[0012] For example, when the AIoT core network device is an AMF, the first identification information is used to identify the identifier corresponding to the AMF; the second identification information is used to identify the operator to which the AMF belongs; the third identification information is used to identify the AIoT service corresponding to the AMF; and the fourth identification information is used to identify the identifier of the server corresponding to the AMF.

[0013] For example, when the AIoT core network device is a TMF, the first identification information is used to identify the identifier corresponding to the TMF; the second identification information is used to identify the operator to which the TMF belongs; the third identification information is used to identify the AIoT service corresponding to the TMF; and the fourth identification information is used to identify the identifier of the server corresponding to the TMF.

[0014] This application does not specifically limit the network elements corresponding to the AIoT core network devices.

[0015] In some embodiments, the first identification information includes at least one of the following: the region ID of the first AIoT core network device, the group ID / set ID of the first AIoT core network device, or the pointer ID of the first AIoT core network device.

[0016] It should be noted that the first identification information may also include other identifications, but this application embodiment does not specifically limit this.

[0017] In some embodiments, the third identification information includes at least one of the following: Task ID, Transaction ID, Session ID, or Service ID.

[0018] It should be noted that the third identification information may also include other identifications, but this application embodiment does not specifically limit this.

[0019] In some embodiments, determining the first information includes receiving a third message, the third message including the first information.

[0020] In this implementation, the AIoT device receives a third message, which includes the first information.

[0021] For example, the third message could be a paging message sent by an AIoT access network device.

[0022] In some embodiments, the first information may also be pre-configured by the AIoT device.

[0023] In a second aspect, a communication method is provided, the method comprising: receiving a first message, the first message including second information and first information, the first message being used by the AIoT access network device to send the second information to a first core network device, the second information including data and / or signaling related to AIoT services; and sending the second information to the first AIoT core network device based on the first message.

[0024] For example, the communication method can be implemented by an AIoT access network device, or by modules, units, processors, circuits, chips or chip systems included in the AIoT access network device.

[0025] The method provided in this application uses first information to enable an AIoT access network device to know which AIoT core network device to send the second information sent by the AIoT device to. The first message includes first information and second information. Therefore, after receiving the first message, the AIoT access network device sends the received second information to the relevant AIoT core network device (the first AIoT core network device).

[0026] In some embodiments, before receiving the first message, the method further includes: receiving a fourth message sent by an AIoT core network device, the fourth message including the first information; and sending a third message to the AIoT device, the third message including the first information.

[0027] In this implementation, before the AIoT access network device receives the first message sent by the AIoT device, the AIoT access network device receives a fourth message (e.g., the fourth message may be a service request message) sent by the AIoT core network device. The fourth message carries the first information. Then, when the AIoT access network device sends a third message to the AIoT device (e.g., the third message may be a paging message), it carries the first information. After receiving the first information, the AIoT device sends a first message to the AIoT access network device. The first message includes the first information and the second information.

[0028] In some embodiments, the first information includes at least one of the following: first identification information, second identification information, third identification information, or fourth identification information; the first identification information is used to identify the first AIoT core network device; the second identification information is used to identify the operator; the third identification information is used to identify the AIoT service; and the fourth identification information is used to identify the server.

[0029] In this embodiment of the application, the first identification information, the second identification information, the third identification information and the fourth identification information enable the AIoT access network device to know which AIoT core network device to send the second information sent by the AIoT device to.

[0030] In some embodiments, the first identification information includes at least one of the following: the region ID of the first AIoT core network device, the group ID / set ID of the first AIoT core network device, or the pointer ID of the first AIoT core network device.

[0031] It should be noted that the first identification information may also include other identifications, but this application embodiment does not specifically limit this.

[0032] In some embodiments, the third identification information includes at least one of the following: Task ID, Transaction ID, Session ID, or Service ID.

[0033] It should be noted that the third identification information may also include other identifications, but this application embodiment does not specifically limit this.

[0034] In some embodiments, when the first information is third identification information, the method further includes: saving the third identification information; sending the second information to the first AIoT core network device includes: matching the third identification information with the first information in the first message; when the third identification information and the first information are successfully matched, sending the second information to the first AIoT core network device, wherein the first information corresponds to the service of the first AIoT core network device.

[0035] In this implementation, when the first information is the third identification information, and the third identification information is used to identify the AIoT service corresponding to the first AIoT core network device, the AIoT access network device saves the third identification information and then matches it with the first information in the first message. When the third identification information and the first information match successfully, it indicates that the service in the first information corresponds to the service of the first AIoT core network device.

[0036] In some embodiments, the fourth message includes at least one of the following: inventory service, location service, sensing service, or command service.

[0037] It should be noted that the fourth message may also include other business requests, but this application embodiment does not specifically limit this.

[0038] Thirdly, a communication method is provided, the method comprising: sending a first request message to a first network element, the first request message being used to request information from a first AIoT core network device, the first AIoT access network device being used to receive second information, the second information including data and / or signaling related to AIoT services; receiving a first message, the first message including information from the first AIoT core network device; and sending the second information to the first AIoT core network device based on the first message.

[0039] For example, the communication method can be implemented by an AIoT access network device, or by modules, units, processors, circuits, chips or chip systems included in the AIoT access network device.

[0040] The method provided in this application involves an AIoT access network device receiving second information from another AIoT device. Since the AIoT access network device does not know which AIoT core network device to send the second information to, it sends a first request message to a first network element to request information about the first AIoT core network device related to the second information. Finally, it receives the first message sent by the first network element. This first message is used by the AIoT access network device to send the second information to the first AIoT core network device; the first message includes information about the first AIoT core network device.

[0041] In some embodiments, the first information includes at least one of the following: first identification information, second identification information, third identification information, or fourth identification information; the first identification information is used to identify the first AIoT core network device; the second identification information is used to identify the operator; the third identification information is used to identify the AIoT service; and the fourth identification information is used to identify the server.

[0042] In this embodiment of the application, the first identification information, the second identification information, the third identification information and the fourth identification information enable the AIoT access network device to know which AIoT core network device to send the second information sent by the AIoT device to.

[0043] In some embodiments, the first identification information includes at least one of the following: the Region ID of the first AIoT core network device, the Group ID / Set ID of the first AIoT core network device, or the Pointer of the first AIoT core network device.

[0044] It should be noted that the first identification information may also include other identifications, but this application embodiment does not specifically limit this.

[0045] In some embodiments, the third identification information includes at least one of the following: Task ID, Transaction ID, Session ID, or Service ID.

[0046] It should be noted that the third identification information may also include other identifications, but this application embodiment does not specifically limit this.

[0047] Fourthly, a communication device is provided, comprising: a module (e.g., including a processing module and a communication module) for performing the steps of the first aspect or any possible implementation thereof; or a module for performing the steps of the second aspect or any possible implementation thereof; or a module for performing the steps of the third aspect or any possible implementation thereof. For example, the communication device may be an AIoT device or an AIoT device may include the communication device, or the communication device may be an AIoT access network device or an AIoT access network device may include the communication device.

[0048] Fifthly, a communication device is provided, the device comprising at least one processor, the at least one processor being configured to execute: the method of the first aspect or any possible implementation thereof, or the method of the second aspect or any possible implementation thereof, or to execute the method of the second aspect or any possible implementation thereof, or to execute the method of the third aspect or any possible implementation thereof.

[0049] In one possible implementation, the communication device may further include a memory storing a computer program, and at least one processor executes the method of the first aspect or any possible implementation thereof, or the method of the second aspect or any possible implementation thereof, or the method of the third aspect or any possible implementation thereof, by executing the computer program stored in the memory. Optionally, the processor and the memory may be integrated together.

[0050] In one possible implementation, at least one processor executes the method of the first aspect or any possible implementation of the first aspect, or the method of the second aspect or any possible implementation of the second aspect, or the method of the third aspect or any possible implementation of the third aspect, through logic circuits or processing circuits.

[0051] In one possible implementation, the communication device may further include interface circuitry for performing specific signal transmission and reception. For example, the communication device may be a terminal, a component within the terminal (a chip, chip system, or processor), or a logic module or software capable of implementing all or part of the terminal's functions.

[0052] For example, the communication device can be a network device, a component (chip, chip system, or processor) in a network device, or a logical node, logical module, or software that can implement all or part of the functions of a network device. Attached Figure Description

[0053] Figure 1 A schematic diagram of the application framework involving RIC modules under the O-RAN architecture is shown.

[0054] Figure 2 An example diagram of an O-RAN system is shown.

[0055] Figure 3 A schematic diagram of the network architecture provided in an embodiment of this application is shown.

[0056] Figure 4 A schematic diagram of the protocol stack for Topology 1 is shown.

[0057] Figure 5 A schematic interactive diagram of an example communication method provided in an embodiment of this application is shown.

[0058] Figure 6 A schematic interactive diagram of another communication method provided in an embodiment of this application is shown.

[0059] Figure 7 A schematic interactive diagram of another communication method provided in an embodiment of this application is shown.

[0060] Figure 8 A schematic block diagram of a communication device provided in an embodiment of this application is shown.

[0061] Figure 9 A schematic block diagram of another communication device provided in an embodiment of this application is shown. Detailed Implementation

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

[0063] In the description of the embodiments of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in the embodiments of this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of the embodiments of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or the order of execution, and that the words "first" and "second" do not necessarily imply that they are different.

[0064] In the various method embodiments of this application, the order of the sequence numbers does not imply the order of execution. The execution order should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0065] It is understood that in the embodiments of this application, descriptions such as "under the circumstances," "if," "when," and "if..." can be used interchangeably. Furthermore, these descriptions all refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require any judgment action during implementation, nor do they imply any other limitations.

[0066] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0067] In the embodiments of this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined according to their inherent logical relationships to form new embodiments, implementation methods, methods, or implementation approaches. The embodiments of this application described below do not constitute a limitation on the scope of protection of this application.

[0068] The AIoT device in this application embodiment can also be called a terminal device. This terminal device specifically implements AIoT functions. It can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless core network element, user agent, user device, or terminal device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to users, and can be used to connect people, objects, and machines, such as handheld devices with wireless connectivity, vehicle-mounted devices, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes, etc. Optionally, the terminal device can act as a base station. For example, the terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) communications. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0069] The AIoT access network device in this embodiment can be an access device through which a terminal wirelessly accesses the network architecture. It is primarily responsible for air interface-side radio resource management, quality of service (QoS) management, data compression, and encryption. The access network device can also be called a radio access network (RAN) device, such as a base station. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, or a device that performs base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network equipment.

[0070] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0071] In some deployments, the access network device in this application embodiment may refer to a CU or a DU, or the access network device may include both a CU and a DU. The gNB may also include an AAU.

[0072] The AIoT core network elements in this application embodiment may include user plane function (UPF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, network slice selection function (NSSF) network elements, authentication server function (AUSF) network elements, unified data management (UDM) network elements, NEF network elements, NRF network elements, network slice-specific authentication and authorization function (NSSAAF) network elements, network slice admission control function (NSACF) network elements, edge application server discovery function (EASDF) network elements, service communication proxy (SCP) network elements, charging function (CHF) network elements, and location management function (LMF) network elements. Among them, the UPF network element is mainly responsible for the transmission of user data, while other network elements can be called control plane function network elements, which are mainly responsible for authentication, authorization, registration management, session management, mobility management and policy control, so as to ensure reliable and stable transmission of user data.

[0073] Before introducing the communication method provided in this application, the relevant background technology will be explained in detail.

[0074] 1. Passive Radio Frequency Identification (RFID)

[0075] An RFID system consists of a reader and tags. The reader reads information from the tags or writes information to the tags. The reader and tags communicate without contact. The tags are simple in function, requiring activation from the reader to transmit information; that is, the tag converts the wireless signal emitted by the reader into energy to power itself. Tags support power consumption in the microwatt or hundreds of microwatts range, limiting their ability to support complex designs.

[0076] If RFID is applied to communication systems, such as 5G systems, then base stations can act as readers, performing the functions of a reader / writer. Currently, RFID technology can be used to identify targets.

[0077] 2. Ambient Internet of Things (AIoT) technology.

[0078] With the development of communication technology, the 3rd generation partnership project (3GPP) has defined AIoT technology.

[0079] AIoT technology encompasses both network devices and Type I terminal devices, or in other words, AIoT-based communication systems include both network devices and Type I terminal devices. Type I terminal devices can be devices with AIoT terminal device functionality. In this case, both readers and AIoT terminal devices can be implemented based on cellular network infrastructure. In other words, both readers and AIoT terminal devices can be devices within a cellular network. For example, the functionality of a reader can be implemented by network devices, such as base stations. AIoT terminal devices can be implemented by terminals within a cellular network, such as ultra-low power, ultra-low complexity IoT terminals, i.e., Type I terminals. Non-contact data communication can occur between network devices and Type I terminal devices, allowing network devices to read information from Type I terminal devices and / or store information in Type I terminals. AIoT technology can be used to implement one or more of the following services: inventory, positioning, sensing, and command. In terms of application scope, AIoT technology can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, or environmental monitoring.

[0080] The inventory management process involves using a reader to write data to AIoT devices within the coverage area. Successfully connected devices need to send their unique identifier to the reader. This process, also known as inventory counting, retrieves tag identification information. For example, the reader can use commands like query and confirmation to obtain tag identification information. To facilitate tag inventory, tags include four types of session identifiers, each corresponding to two inventory states: A and B. The inventory state is indicated by a sessionInventoried flag. When a reader selects a tag, the select command sent to it includes a session identifier, which the tag then stores. When the reader performs inventory management on the tag, the query command sent includes the session identifier. At this point, the tag can flip its inventory state from A to B. If the reader sends another query command to perform inventory management, since the tag's inventory state is B, it will not respond to the reader, thus preventing the same tag from being inventoryed multiple times in a single inventory cycle.

[0081] Location services use location signals to pinpoint the location of tags.

[0082] The sensing service involves tags reporting sensing data to the base station, such as temperature data.

[0083] Command operations can include at least one of the following: read operations, write operations, or lock operations:

[0084] Read service: The read service can read the electronic product code (EPC), tag identifier (TID) in the tag's storage area, the content stored in the tag's reserved area, or the content stored in the user's storage area.

[0085] Write service: The write service can perform write operations on the tag's storage area. That is, the BS sends a downlink command and data, instructing the tag to write the data into its own storage area (memory).

[0086] Kill the tag: The kill tag can make the tag permanently unusable.

[0087] Locking: Locking can lock the information of a tag, preventing read or write operations on that tag. Alternatively, locking can also lock a storage area, preventing or allowing read or write operations on that storage area.

[0088] The above are just examples. Other business processes or operations can be performed between the tag and the reader, which will not be illustrated here.

[0089] In AIoT, terminal devices can be divided into three categories: Device A, Device B, and Device C.

[0090] Device A (similar to a passive tag): It has no energy storage, cannot generate signals independently, and uses backscattering to transmit signals.

[0091] Device B (similar to a semi-passive tag): It has energy storage but cannot generate signals independently. It uses backscattering to transmit signals, and its stored energy can amplify the reflected signals.

[0092] Device C (similar to an active tag): It has energy storage, can generate signals independently, and has active radio frequency components for transmission.

[0093] For device A (passive tag / device) and B (semi-passive tag / device), the tag needs to obtain a carrier signal from an external source for backscatter communication.

[0094] For device C (active tag / device), it can actively generate carrier waves, so it can communicate actively without relying on external devices / nodes.

[0095] In addition, the RAN1#116 meeting further defined the following three categories of AIoT devices: Device 1, Device 2a, and Device 2b.

[0096] Device 1: ~1μW peak power consumption, with energy storage function, initial sampling frequency offset (SFO) reaches 10X ppm, cannot amplify DL and UL signals. It requires an external carrier signal for backscatter communication to perform uplink transmission.

[0097] Device 2a: Peak power consumption less than or equal to several hundred μW, with energy storage function, initial sampling frequency offset (SFO) reaching 10X ppm, capable of DL and / or UL signal amplification. Requires an external carrier signal for backscatter communication for uplink transmission.

[0098] Device 2b: Peak power consumption less than or equal to several hundred μW, with energy storage function, initial sampling frequency offset (SFO) reaching 10X ppm, and capable of DL and / or UL signal amplification. The device can perform uplink transmission without relying on an externally provided carrier.

[0099] For Device 1 and Device 2a, the tag needs to obtain a carrier signal from an external source for backscatter communication;

[0100] For Device 2b, it can actively generate carrier waves, so it can communicate actively without relying on external devices / nodes.

[0101] 3. RIC and AI architecture in O-RAN.

[0102] Figure 1 This diagram illustrates an application framework involving RIC modules within the O-RAN architecture. Figure 1 As shown, the communication system includes a RAN intelligent controller (RIC). RICs include near-real-time RICs (near-RT RICs) and non-real-time RICs (non-RT RICs).

[0103] The near real-time RIC is used for model training and inference. For example, it can be used to train an AI model and then use that model for inference. The near real-time RIC can obtain network-side and / or terminal-side information from RAN nodes (e.g., CU, CU-CP, CU-UP, DU, and / or RU) and / or terminals. This information can be used as training data or inference data. Optionally, the near real-time RIC can deliver the inference results to the RAN nodes and / or terminals. Optionally, inference results can be exchanged between CU and DU, and / or between DU and RU. For example, the near real-time RIC delivers the inference results to the DU, and the DU sends them to the RU.

[0104] Non-real-time RICs are used for model training and inference. For example, they are used to train AI models and then use those models for inference. Non-real-time RICs can obtain network-side and / or terminal-side information from RAN nodes (e.g., CUs, CU-CPs, CU-UPs, DUs, and / or RUs) and / or terminals. This information can be used as training data or inference data, and the inference results can be delivered to RAN nodes and / or terminals. Optionally, inference results can be exchanged between CUs and DUs, and / or between DUs and RUs; for example, a non-real-time RIC delivers inference results to a DU, which then forwards them to an RU.

[0105] Furthermore, near real-time RICs and non-real-time RICs can also be configured as separate network elements. Optionally, near real-time RICs and non-real-time RICs can also be part of other devices. For example, near real-time RICs can be set in RAN nodes (e.g., CU, DU), while non-real-time RICs can be set in OAM, cloud servers, core network devices, or other network devices.

[0106] In a communication system, network elements are connected via interfaces (e.g., NG, Xn) or over-the-air interfaces. These network element nodes, such as core network equipment, access network nodes (RAN nodes), terminals, or one or more devices in the OAM, are equipped with one or more AI modules (only one is shown in the figure for clarity). The access network node can be a single RAN node or can include multiple RAN nodes, for example, including CU and DU. The CU and / or DU can also be equipped with one or more AI modules. Optionally, the CU can be further divided into CU-CP and CU-UP. One or more AI models are configured in the CU-CP and / or CU-UP.

[0107] AI modules are used to implement corresponding AI functions. AI modules deployed in different network elements can be the same or different. Depending on the parameter configuration, the AI ​​module can implement different functions. The AI ​​module model can be configured based on one or more of the following parameters: structural parameters (e.g., at least one of the following: number of neural network layers, neural network width, inter-layer connections, neuron weights, neuron activation function, or biases in the activation function), input parameters (e.g., the type and / or dimension of the input parameters), or output parameters (e.g., the type and / or dimension of the output parameters). The biases in the activation function can also be referred to as the neural network biases.

[0108] An AI module can have one or more models. A model can infer an output, which includes one or more parameters. The learning, training, or inference processes of different models can be deployed on different nodes or devices, or they can be deployed on the same node or device.

[0109] 4. CU, DU, RU architecture in O-RAN

[0110] Figure 2 An example diagram of an O-RAN system is shown, such as Figure 2As shown, the O-RAN system may include other components besides those shown in the figure. As illustrated, the access network equipment (RAN, such as an eNB, gNB, or next-generation access network equipment) communicates with the core network (CN) via a backhaul link and with the user equipment (UE) via an air interface.

[0111] In some examples, the CU is a logical node that carries the Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which can be interfaces such as E2 interfaces. Optionally, the CU may have some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the RLC layer and lower layers) through interfaces, which can be interfaces such as the F1 interface. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is the application protocol of the F1 interface, defining the F1 signaling procedures in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0112] In some examples, the CU can be split into CU-CP (Control Unit-Control Plane) and CU-UP (Control Unit-User Plane). CU-CP is a logical node carrying the RRC layer and PDCP-C (Control plane part of PDCP) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function (AMF) elements, such as the Access and Mobility Management Function (AMF) in a 5G system. The AMF element is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. CU-UP is a logical node carrying the SDAP layer and PDCP-U (User plane part of PDCP) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements in the core network, such as the UPF (User Plane Function) in a 5G system, are responsible for data forwarding and receiving in terminal devices. The above CU and DU configurations are merely examples; the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or only some protocol layer processing functions. For example, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency. Functions that require low latency can be placed in the DU, while functions that do not require low latency can be placed in the CU.

[0113] In some examples, a DU is a logical node that carries the radio link control (RLC) layer, medium access control (MAC) layer, higher physical layer (Higher PHY) layer, and other functions. In some examples, a DU can control at least one RU. The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0114] In some examples, the RU is a logical node carrying both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar entities. In some examples, the Low-PHY includes PHY processing functions such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0115] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a fronthaul link through the Lower-Layer Split CUS-Plane (LLS-CUS) interface. LLS-CUS may include LLS-C and LLS-U interfaces providing the control plane (C-Plane) and user plane (U-Plane), respectively. In some examples, the control plane (C-Plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0116] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0117] First, the network architecture diagram involved in this application will be explained. Figure 3 A schematic diagram of the network architecture provided in an embodiment of this application is shown, such as... Figure 3 Figure (a) shows the first topology, where there is bidirectional communication between the AIoT device and the network device. Communication between the network device and the AIoT device includes environmental IoT data and / or signaling. This architecture includes network devices that send signaling to the AIoT device and network devices that receive signaling from the AIoT device; that is, there is uplink and downlink data / signaling transmission between the network device and the AIoT device.

[0118] like Figure 3 Figure (b) shows the second topology, where AIoT devices and network devices communicate bidirectionally through an intermediate node. In this structure, the intermediate node can be a repeater, IAB node, terminal device, or other device that enables environmental IoT. The intermediate node transmits AIoT data and / or signaling between the network device and the AIoT device.

[0119] like Figure 3 Figure (c) shows the third topology, in which AIoT devices send downlink data or signaling to the base station and receive data or signaling from auxiliary nodes;

[0120] Or, such as Figure 3 Figure (d) shows the fourth topology, where AIoT devices receive data or signaling from network devices and send data or signaling to auxiliary nodes. In this architecture, auxiliary nodes can be repeaters, IABs, UEs, or other devices that enable the Internet of Things (IoT).

[0121] like Figure 3 As shown in Figure (e), the AIoT device communicates bidirectionally with the terminal device. The communication between the AIoT device and the terminal device includes environmental IoT data and / or signaling.

[0122] In the above Figure 3In the architecture shown in Figure (a), when an AIoT access network device is connected to multiple AIoT core network devices, the AIoT access network device cannot determine which AIoT core network device to report the data sent by the AIoT device to.

[0123] For example, Figure 4 A schematic diagram of the protocol stack for the first topology architecture is shown, such as... Figure 4 As shown, an Upper Layer exists between AIoT devices and AIoT core network devices. The Upper Layer is used to transmit AIoT data or signaling, and the data sent by the AIoT devices is included in the Upper Layer. AIoT access network devices are used to forward the data or signaling sent by the AIoT devices.

[0124] It should be understood that the Upper Layer can be a NAS layer.

[0125] It should be noted that, Figure 4 This is an example of a protocol stack for the first topology architecture. Of course, there are other protocol stacks for the first topology architecture, but this application does not specifically limit them.

[0126] In summary, when an AIoT access network device is connected to multiple AIoT core network devices, how the AIoT access network device can send the data sent by the AIoT device to the corresponding AIoT core network device is a problem that needs to be solved.

[0127] It is worth noting that under the 5G architecture, the next-generation radio access network (NG-RAN) supports the non-access stratum node selection function (NNSF). When NG-RAN is directly connected to multiple access and mobility management functions (AMFs), NG-RAN determines which AMF the terminal device will send uplink data to based on the 5G subscription temporary mobile subscriber identity (5G-S-TMSI) assigned to the terminal device by the AMF.

[0128] It should be understood that the NNSF is responsible for selecting appropriate network nodes (such as eNodeB or gNodeB) for terminal devices to access according to certain rules and policies. The main purpose of the NNSF is to optimize the use of network resources and determine that terminal devices can obtain the best quality of service.

[0129] It should also be understood that 5G-S-TMSI is an identity identifier used temporarily to identify users in 5G networks. It is a temporary identity assigned to users by the network, primarily to protect the user's permanent identity (International Mobile Subscriber Identity, IMSI) from being leaked, as the IMSI is easily intercepted by eavesdroppers when transmitted over the radio interface. 5G-S-TMSI is typically assigned by the AMF and stored in both the terminal device and the network. When a terminal device initiates a call or data request, it uses the 5G-S-TMSI instead of the IMSI to identify itself, so even if intercepted over the radio interface, attackers cannot immediately obtain the user's permanent identity information. When the IMSI is needed, the network can query the database to map the 5G-S-TMSI back to the corresponding IMSI. 5G-S-TMSI is part of 5G network security measures designed to enhance user privacy and data protection.

[0130] In view of this, this application provides a communication method, the method comprising: determining first information, the first information being used by an AIoT access network device to send second information to a first AIoT core network device; and sending a first message, the first message including the second information and the first information, the second information including data and / or signaling related to AIoT services. In the method provided by this application, the first information is used to enable the AIoT access network device to know which AIoT core network device to which the second information sent by the AIoT device should be sent, thereby helping the AIoT access network device to send the received second information to the relevant AIoT core network device.

[0131] The communication method provided in the embodiments of this application will be described in detail below.

[0132] The following is combined Figure 5 This application provides a detailed description of an example communication method. Figure 5 This illustration shows a schematic interaction diagram of a communication method provided in an embodiment of this application, which can be applied to the above-mentioned... Figure 3 or Figure 4 The architecture shown can, of course, be applied to other network architectures as well, and this application does not impose any limitations on it.

[0133] like Figure 5 As shown, Figure 5 The method 500 shown may include S510 to S530. The following is in conjunction with… Figure 5 Detail each step in Method 500.

[0134] S510, the AIoT device determines the first information, which is used by the AIoT access network device to send the second information to the first AIoT core network device.

[0135] It should be understood that AIoT devices need to send second information to AIoT core network devices through AIoT access network devices. This second information includes data and / or signaling related to AIoT services.

[0136] It should be noted that this second piece of information can be initiated by an AIoT device (Device-originated autonomous).

[0137] However, when an AIoT access network device is connected to multiple AIoT core network devices, the AIoT access network device cannot know which AIoT core network device to send the second information sent by the AIoT device to.

[0138] In step S510, the first information determined by the AIoT device is used by the AIoT access network device to send the second information to the first AIoT core network device among multiple AIoT core network devices.

[0139] In some possible implementations, the first information includes at least one of the following: first identification information, second identification information, third identification information, or fourth identification information.

[0140] The first identification information is used to identify the first AIoT core network device; the second identification information is used to identify the operator; the third identification information is used to identify the service; and the fourth identification information is used to identify the server.

[0141] In this embodiment, the first AIoT core network device can be identified based on the first identification information, the second identification information, the third identification information, or the fourth identification information, thereby enabling the AIoT access network device to send the second information to the first AIoT core network device.

[0142] Optionally, the first identification information includes at least one of the following: the first AIoT core network device region ID, the first AIoT core network device group ID / set ID, or the first AIoT core network device pointer ID.

[0143] It should be noted that the Region ID of the first AIoT core network device is used to identify the region that the first AIoT core network device is responsible for.

[0144] The Group ID / Set ID of the first AIoT core network device group uniquely identifies a group of first AIoT core network devices within the AIoT core network device area.

[0145] The Pointer identifier for the first AIoT core network device is used to identify one or more first AIoT core network devices within the AIoT core network device group.

[0146] Of course, the first identification information can also be other information used to identify the identification corresponding to the first AIoT core network device, and this application embodiment does not specifically limit this.

[0147] Optionally, the second identification information can be a Public Land Mobile Network Identifier (PLMN ID). The PLMN ID is used to identify a specific mobile network operator within a mobile communication network. The PLMN ID consists of two parts: a mobile country code (MCC) and a mobile network code (MNC). The PLMN ID helps AIoT devices identify their current location and the network they are using.

[0148] Optionally, the third identification information includes at least one of the following: Task ID, Transaction ID, Session ID, or Service ID.

[0149] It should be noted that the third identification information may also include other identifications, but this application embodiment does not specifically limit this.

[0150] Optionally, the fourth identification information can be the server ID.

[0151] For example, the AIoT access network device pre-stores the server ID corresponding to each AIoT core network device, and the server ID can be used to associate with the relevant first AIoT core network device.

[0152] It should be understood that the correspondence between each AIoT core network device and server ID pre-stored in the AIoT access network device can be sent by the AIoT device to the AIoT access network device, or it can be sent by the AIoT core network device.

[0153] It should be noted that AIoT core network equipment can be AMF, tag management function (TMF), AIoT function (AIoTF), AIoT management function (AIoTMF), or other core network elements / nodes / devices that support / enable AIoT. The specific name is not limited.

[0154] For example, when the AIoT core network device is an AMF, the first identification information is used to identify the identifier corresponding to the AMF; the second identification information is used to identify the operator to which the AMF belongs; the third identification information is used to identify the AIoT service corresponding to the AMF; and the fourth identification information is used to identify the identifier of the server corresponding to the AMF.

[0155] For example, when the AIoT core network device is a TMF, the first identification information is used to identify the identifier corresponding to the TMF; the second identification information is used to identify the operator to which the TMF belongs; the third identification information is used to identify the AIoT service corresponding to the TMF; and the fourth identification information is used to identify the identifier of the server corresponding to the TMF.

[0156] This application does not specifically limit the network elements corresponding to the AIoT core network devices.

[0157] S520: The AIoT device sends a first message to the AIoT access network device. The first message includes second information and the first information. The second information includes data and / or signaling related to AIoT services.

[0158] In step S520, after determining the first information, the AIoT device sends a first message to the AIoT access network device. The first message includes the second information and the first information.

[0159] It should be understood that this second piece of information mainly includes data and / or signaling related to AIoT business.

[0160] For example, when the AIoT service is an inventory management service, the second information is the identifier of the AIoT device. Of course, the AIoT service can also be other services, such as location services, sensing services, or commands, etc. Therefore, the specific content of the second information is related to the AIoT service, and this application embodiment does not specifically limit it.

[0161] Based on the first message, the S530 and AIoT access network devices send the second information to the first AIoT core network device.

[0162] In step S530, after receiving the first message, the AIoT access network device obtains the first information in the first message, and then sends the second information to the first AIoT core network device based on the first information.

[0163] For example, when the first information is the second identification information, the AIoT access network device sends the second information to the first AIoT core network device to which the PLMN ID belongs, based on the PLMN ID.

[0164] When the first information is the third identification information, the AIoT access network device sends the second information to the first AIoT core network device according to the service corresponding to the first AIoT core network device.

[0165] It should be noted that the AIoT core network equipment mentioned above can be an AMF or a tag management function (TMF). Alternatively, the TMF can also be replaced by a network element with AIoT functionality, a network element with AIoT management functionality, or other core network elements / nodes / devices that support / enable AIoT. This application embodiment does not specifically limit this.

[0166] For example, when the AIoT core network device is an AMF, the interface between the AIoT core network device and the AIoT access network device is the N2 interface, and the information exchanged between the two is included in the NGAP msg.

[0167] For example, when the AIoT core network device is a TMF, a network element with AIoT functionality, a network element with AIoT management functionality, or other core network element / node / device that supports AIoT, the interface between the AIoT core network device and the AIoT access network device is the first interface.

[0168] Specifically, the first interface may be an NG interface, and the information exchanged on the first interface is included in the NGAP msg.

[0169] The first interface may also be an interface defined between AIoT access network devices and AIoT core network devices. The information exchanged on the first interface is included in the XXAP msg. The XXAP may be NGAP, or a simplified version of NGAP, or it may be an application protocol defined for the first interface to provide signaling services between AIoT access network device nodes and AIoT core network devices.

[0170] This application does not specifically limit the interface between AIoT access network devices and AIoT core network devices.

[0171] It should also be noted that after the DU in the AIoT access network device receives the first message, the DU sends the first message to the CU in the AIoT access network device through the F1AP interface, and then the CU sends the second message to the first AIoT core network device.

[0172] The method provided in this application embodiment uses first information to enable the AIoT access network device to know which AIoT core network device to send the second information sent by the AIoT device to. Therefore, after the AIoT device determines the first information, it sends a first message to the AIoT access network device. The first message includes the first information and the second information, which helps the AIoT access network device to send the received second information to the relevant AIoT core network device.

[0173] In the aforementioned method 500, there are two ways for the AIoT device to determine the first information: First, the AIoT device can pre-configure the first information. Second, the AIoT device can receive a third message sent by the AIoT access network device, which includes the first information. The following describes how... Figure 6 The first information for determining AIoT devices is explained in detail.

[0174] Figure 6 This illustration shows a schematic interaction diagram of another communication method provided in an embodiment of this application, which can be applied to the above-mentioned... Figure 3 or Figure 4 The architecture shown can, of course, be applied to other network architectures as well, and this application does not impose any limitations on it.

[0175] like Figure 6 As shown, Figure 6 The method 600 shown may include S610 to S640. The following is in conjunction with… Figure 6 Detail each step in method 600.

[0176] S610, at least one AIoT core network device sends a fourth message to the AIoT access network device, the fourth message including the first information.

[0177] In some possible implementations, the fourth message in step S610 may include an inventory request message, a location service request message, a sensing service request message, or a command message.

[0178] The command messages can include read operations, write operations, lock operations, and disable messages, including temporary or permanent disable messages.

[0179] It should be noted that the fourth message can also be other messages, and this application embodiment does not specifically limit it.

[0180] It should also be noted that the fourth message includes an AIoT device identifier, which is used to identify one or a group of or all AIoT devices. For example, the AIoT device identifier can be a mask or a group ID; this application embodiment does not limit the specific form of the AIoT device identifier.

[0181] For example, when the fourth message is an inventory request message, the fourth message is used to request the identifier of the AIoT device, and the fourth message includes the first information.

[0182] It should also be noted that the AIoT access network device is connected to multiple AIoT core network devices, so multiple core network devices send the fourth message to the AIoT device through the AIoT access network device.

[0183] It should be understood that at least one AIoT core network device can be understood as multiple AIoT core network devices, and when there is at least one AIoT core network device, there is at least one fourth message.

[0184] The S620a AIoT access network device stores the first information in the fourth message.

[0185] When the first information in step S710 is the third identification information, the AIoT access network device can save the first information in the fourth message to facilitate matching when the AIoT device sends the first information.

[0186] It should be noted that step S720a is an optional step. That is, the AIoT access network device can perform this step when the first message is the third identification information. When the first message is the first identification information, the second identification information, or the fourth identification information, the AIoT access network device may not perform this step.

[0187] S620b: The AIoT access network device sends a third message to at least one AIoT device, the third message including the first information.

[0188] After the AIoT access network device receives the fourth message sent by multiple AIoT core network devices, the AIoT access network device sends a third message to the multiple AIoT devices respectively. The third message includes the first information.

[0189] It should be noted that after the CU in the AIoT access network device receives the fourth message, the CU sends the fourth message to the DU in the AIoT access network device through the F1AP interface, and then the DU in the AIoT access network device sends the third message to at least one AIoT device.

[0190] For example, when the fourth message is used to store business messages, the third message may be a paging message, and the paging message includes the first information.

[0191] It should be understood that there is at least one third message; that is, if there are multiple AIoT devices, there will also be multiple third messages. Figure 6 (This will be illustrated using an AIoT device as an example.)

[0192] S630, the AIoT device sends a first message to the AIoT access network device. The first message includes second information and the first information. The second information includes data and / or signaling related to AIoT services.

[0193] When the AIoT access network device sends a third message to at least one AIoT device in step S620b, correspondingly, at least one AIoT device receives the third message, and then the target AIoT device (Figure 6 The AIoT device sends the first message to the AIoT access network device.

[0194] For example, when the fourth message is an inventory service message and the third message is a paging message, the successfully connected AIoT device sends its unique identifier to the AIoT core network device. That is, the first message includes the AIoT device's unique identifier and first information.

[0195] The S640a and AIoT access network devices will match the stored first information with the first information in the first message.

[0196] When the first information in step S730 is the third identification information, the AIoT access network device matches the first information saved in step S620a with the first information in step S630. When the service is successfully matched, the AIoT core network device corresponding to the service is the first AIoT core network device.

[0197] For example, the first information stored in step S620a includes the inventory service sent by the first AIoT core network device, the positioning service sent by the second AIoT core network device, and the sensing service sent by the third AIoT core network device. If the first information carried in the first message in step S630 is the inventory service, then the AIoT access network device can determine that it needs to send the second information to the AIoT core network device corresponding to the inventory service, i.e., the first AIoT core network device.

[0198] It should be noted that step S620 is an optional step. That is, the AIoT access network device can perform this step when the first message is the third identification information. When the first message is the first identification information, the second identification information, or the fourth identification information, the AIoT access network device may not perform this step.

[0199] The S640b AIoT access network device sends the second information to the first AIoT core network device.

[0200] The method provided in this application embodiment involves an AIoT device determining first information through a fourth message sent by an AIoT core network device, and then sending a first message to an AIoT access network device. The first message includes first information and second information, thereby helping the AIoT access network device to send the received second information to the relevant AIoT core network device.

[0201] This application also provides another communication method in which the AIoT access network device obtains information of the first AIoT core network device with the assistance of the first network element, so that the AIoT access network device can send the second information sent by the AIoT device to the relevant AIoT core network device.

[0202] The following is combined Figure 7 This application provides another example of a communication method. Figure 7 This illustration shows a schematic interaction diagram of another communication method provided in an embodiment of this application, which can be applied to the above-mentioned... Figure 3 or Figure 4 The architecture shown can, of course, be applied to other network architectures as well, and this application does not impose any limitations on it.

[0203] like Figure 7 As shown, Figure 7 The method 700 shown may include S710 to S730. The following is in conjunction with… Figure 7 Detail each step in method 700.

[0204] S710, the AIoT device sends second information to the AIoT access network device, the second information including data and / or signaling related to AIoT services.

[0205] In step S710, the AIoT device sends second information to the AIoT access network device, which is related to the AIoT service.

[0206] For example, the second information could be the identifier of an AIoT device related to inventory management.

[0207] Of course, the second information can also be other data and / or signaling related to AIoT services, and this application embodiment does not specifically limit this.

[0208] S720, the AIoT access network device sends a first request message to the first network element based on the second information. The first request message is used to request information from the first AIoT core network device.

[0209] Since the AIoT access network device is connected to multiple AIoT access network devices, when the AIoT access network device receives the second information sent by the AIoT device, it does not know which AIoT core network device to send the second information to.

[0210] In step S720, the AIoT access network device sends a first request message to the first network element, requesting to obtain information about the first AIoT core network device.

[0211] It should be noted that there is a correspondence between the pre-configured AIoT devices and the first AIoT core network devices in this first network element.

[0212] S730, the first network element sends the first information, which includes information about the first AIoT core network device.

[0213] After receiving the first request message sent by the AIoT access network device, the first network element sends first information to the AIoT access network device. The first information is used by the AIoT access network device to send second information to the first AIoT core network device. The first information includes information of the first AIoT core network device.

[0214] Specifically, the detailed description of this first information can be found in methods 600 and 700, and will not be repeated here.

[0215] In some possible implementations, the first information may also include the identifier of the first AIoT core network device.

[0216] The S740 and AIoT access network devices send second information to the first AIoT core network device based on the first information.

[0217] Finally, the AIoT access network device sends the second information to the relevant first AIoT core network device based on the first information.

[0218] The method provided in this application embodiment allows an AIoT access network device to request information about a first AIoT core network device from a first network element after receiving second information sent by an AIoT device, thereby sending the second information to the first AIoT core network device.

[0219] The method embodiments provided in this application have been described above. The apparatus embodiments provided in this application will be described below. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, any content not described in detail can be referred to the method embodiments above. For the sake of brevity, it will not be repeated here.

[0220] Figure 8 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 8 As shown, the communication device 800 may include a transceiver unit 810 and / or a processing unit 820. The transceiver unit 810 can implement corresponding communication functions, and the processing unit 820 is used for data processing. The transceiver unit 810 may also be referred to as a communication interface or communication unit. Optionally, the device 800 may further include a storage unit, which can be used to store instructions and / or data, and the processing unit 820 can read the instructions and / or data in the storage unit to enable the device to implement the aforementioned method embodiments.

[0221] In one possible design, the device 800 can be an AIoT device as described in the above method embodiments. For example, the device 800 can be an AIoT device, or it can be a chip, processor, or chip system that implements the functions of an AIoT device. It can also be a logic node, logic module, or software that can implement all or part of the functions of an AIoT device. The device 800 can be used to execute the steps or processes performed by the AIoT device in any of the above method embodiments.

[0222] Specifically, the processing unit 820 is used to determine first information, which is used by the AIoT access network device to send second information to the first AIoT core network device; the transceiver unit 810 can be used to send a first message, which includes the second information and the first information, and the second information includes data and / or signaling related to AIoT services.

[0223] Optionally, the first information includes at least one of the following: first identification information, second identification information, third identification information, or fourth identification information; the first identification information is used to identify the first AIoT core network device; the second identification information is used to identify the operator; the third identification information is used to identify the AIoT service; and the fourth identification information is used to identify the server.

[0224] Optionally, the first identification information includes at least one of the following: the Region ID of the first AIoT core network device, the Group ID / Set ID of the first AIoT core network device, or the Pointer of the first AIoT core network device.

[0225] Optionally, the third identification information includes at least one of the following: Task ID, Transaction ID, Session ID, or Service ID.

[0226] Optionally, the transceiver unit 810 is also configured to receive a third message, the third message including the first information.

[0227] In one possible design, the device 800 can be an AIoT access network device as described in the above method embodiments, or it can be a chip, processor, or chip system that implements the functions of an AIoT access network device. It can also be a logical node, logical module, or software capable of implementing all or part of the functions of an AIoT access network device. The device 800 can be used to execute the steps or processes performed by the AIoT access network device in any of the above method embodiments.

[0228] Specifically, the transceiver unit 810 can be used to receive a first message, which includes second information and first information. The first message is used by the AIoT access network device to send the second information to the first core network device. The second information includes data and / or signaling related to AIoT services. The transceiver unit 810 is also used to send the second information to the first AIoT core network device based on the first message.

[0229] Optionally, the first information includes at least one of the following: first identification information, second identification information, third identification information, or fourth identification information; the first identification information is used to identify the first AIoT core network device; the second identification information is used to identify the operator; the third identification information is used to identify the AIoT service; and the fourth identification information is used to identify the server.

[0230] Optionally, the first identification information includes at least one of the following: the Region ID of the first AIoT core network device, the Group ID / Set ID of the first AIoT core network device, or the Pointer of the first AIoT core network device.

[0231] Optionally, the third identification information includes at least one of the following: Task ID, Transaction ID, Session ID, or Service ID.

[0232] Optionally, the processing unit 820 is used to store the third identification information; match the third identification information with the first information in the first message; when the third identification information and the first information are successfully matched, send the second information to the first AIoT core network device, wherein the first information corresponds to the service of the first AIoT core network device.

[0233] Optionally, the fourth message includes at least one of the following: inventory service, location service, sensing service, or command service.

[0234] In one possible design, the device 800 can be an AIoT access network device as described in the above method embodiments. For example, the device 800 can be an AIoT access network device, or it can be a chip, processor, or chip system that implements the functions of an AIoT access network device. It can also be a logical node, logical module, or software that can implement all or part of the functions of an AIoT access network device. The device 800 can be used to execute the steps or processes performed by the AIoT access network device in any of the above method embodiments.

[0235] Specifically, the transceiver unit 810 can be used to send a first request message to a first network element, the first request message being used to request information from a first AIoT core network device. The first AIoT access network device is used to receive second information, the second information including data and / or signaling related to AIoT services; receive the first information, the first information including information from the first AIoT core network device; and send the second information to the first AIoT core network device based on the first message.

[0236] Optionally, the first information includes at least one of the following: first identification information, second identification information, third identification information, or fourth identification information; the first identification information is used to identify the first AIoT core network device; the second identification information is used to identify the operator; the third identification information is used to identify the AIoT service; and the fourth identification information is used to identify the server.

[0237] Optionally, the first identification information includes at least one of the following: the Region ID of the first AIoT core network device, the Group ID / Set ID of the first AIoT core network device, or the Pointer of the first AIoT core network device.

[0238] Optionally, the third identification information includes at least one of the following: Task ID, Transaction ID, Session ID, or Service ID.

[0239] It should be understood that the "unit" in device 800 can be implemented in hardware, software, or by hardware executing corresponding software. For example, the "unit" can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, combined logic circuitry, and / or other suitable components supporting the described functions. As another example, transceiver unit 810 can be replaced by transceiver circuitry (e.g., it may include receiving and transmitting circuitry), and processing unit 820 can be replaced by a processor or processing circuitry.

[0240] Figure 9A schematic block diagram of another communication device provided in an embodiment of this application is shown. This communication device 900 may be a first network element, a second network element, or a third network element, or it may be a chip, chip system, or processor, etc., within the first network element, second network element, or third network element that implements the above-described method. This device can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0241] The communication device 900 may include one or more processors 910, which may also be referred to as processing units, and can implement certain control functions. The processor 910 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs.

[0242] In an alternative design, the processor 910 may also store instructions and / or data that can be executed by the processor 910 to cause the communication device 900 to perform the methods described in the above method embodiments.

[0243] In another alternative design, the communication device 900 may include a communication interface 920 for implementing receiving and transmitting functions. For example, the communication interface 920 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0244] Optionally, the communication device 900 may include one or more memories 930, which may store instructions that can be executed on the processor 910, causing the communication device 900 to perform the methods described in the above method embodiments. Optionally, the memories 930 may also store data. Optionally, the processor 910 may also store instructions and / or data. The processor 910 and the memories 930 may be provided separately or integrated together.

[0245] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0246] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0247] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0248] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to execute the various steps or processes performed by the network element / device in any of the above method embodiments.

[0249] This application also provides a computer-readable storage medium storing program code that, when run on a computer, causes the computer to execute the various steps or processes performed by the network element / device in any of the above method embodiments.

[0250] This application also provides a communication device, including a processor and an interface, the interface being used to send and / or receive signals, causing the processor to execute the various steps or processes performed by the network element / device in any of the above method embodiments.

[0251] The above-described device and method embodiments are completely corresponding, with corresponding modules or units performing corresponding steps. For example, a communication unit or communication interface performs the receiving or sending steps in the method embodiment, while other steps besides sending and receiving can be performed by a processing unit or processor.

[0252] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. The embodiments of this application do not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0253] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable storage media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0254] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

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

[0256] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0257] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0258] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

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

[0260] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or parts of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A communication method, characterized in that, The method is applied to an environmental Internet of Things (AIoT) device or a chip in the device, and the method includes: First information is determined, and the first information is used by the AIoT access network device to send second information to the first AIoT core network device; Send a first message, the first message including the second information and the first information, the second information including data and / or signaling related to AIoT services.

2. The method according to claim 1, characterized in that, The first information includes at least one of the following: first identification information, second identification information, third identification information, or fourth identification information; The first identification information is used to identify the first AIoT core network device; The second identification information is used to identify the operator; The third identification information is used to identify AIoT services; The fourth identification information is used to identify the server.

3. The method according to claim 2, characterized in that, The first identification information includes at least one of the following: the region ID of the first AIoT core network device, the group ID / set ID of the first AIoT core network device, or the pointer ID of the first AIoT core network device.

4. The method according to claim 2 or 3, characterized in that, The third identification information includes at least one of the following: Task ID, Transaction ID, Session ID, or Service ID.

5. The method according to any one of claims 1-4, characterized in that, The determination of the first information includes: Receive a third message, the third message including the first information.

6. A communication method, characterized in that, The method is applied to an AIoT access network device or a chip in an AIoT access network device, and the method includes: Receive a first message, the first message including second information and first information, the first message being used by the AIoT access network device to send the second information to the first AIoT core network device, the second information including AIoT service-related data and / or signaling; Based on the first message, the second information is sent to the first AIoT core network device.

7. The method according to claim 6, characterized in that, Before receiving the first message, the method further includes: Receive a fourth message sent by an AIoT core network device, the fourth message including the first information; Send a third message to the AIoT device, the third message including the first information.

8. The method according to claim 7, characterized in that, The first information includes at least one of the following: first identification information, second identification information, third identification information, or fourth identification information; The first identification information is used to identify the first AIoT core network device; The second identification information is used to identify the operator; The third identification information is used to identify AIoT services; The fourth identification information is used to identify the server.

9. The method according to claim 8, characterized in that, The first identification information includes at least one of the following: the region ID of the first AIoT core network device, the group ID / set ID of the first AIoT core network device, or the pointer ID of the first AIoT core network device.

10. The method according to claim 8 or 9, characterized in that, The third identification information includes at least one of the following: Task ID, Transaction ID, Session ID, or Service ID.

11. The method according to any one of claims 8-10, characterized in that, When the first information is third identification information, the method further includes: Save the third identification information; Send the second message to the first AIoT core network device, including: The third identifier information is matched with the first information in the first message; When the third identification information and the first information are successfully matched, the second information is sent to the first AIoT core network device, and the first information corresponds to the service of the first AIoT core network device.

12. The method according to any one of claims 8-11, characterized in that, The fourth message includes at least one of the following: inventory service, positioning service, sensing service, or command service.

13. A communication method, characterized in that, The method is applied to AIoT access network devices, and the method includes: Send a first request message to a first network element. The first request message is used to request information from a first AIoT core network device. The first AIoT access network device is used to receive second information, which includes data and / or signaling related to AIoT services. Receive first information, the first information including information about the first AIoT core network device; The second information is sent to the first AIoT core network device based on the first information.

14. The method according to claim 13, characterized in that, The first information includes at least one of the following: first identification information, second identification information, third identification information, or fourth identification information; The first identification information is used to identify the first AIoT core network device; The second identification information is used to identify the operator; The third identification information is used to identify AIoT services; The fourth identification information is used to identify the server.

15. The method according to claim 14, characterized in that, The first identification information includes at least one of the following: the region ID of the first AIoT core network device, the group ID / set ID of the first AIoT core network device, or the pointer ID of the first AIoT core network device.

16. The method according to claim 14 or 15, characterized in that, The third identification information includes at least one of the following: Task ID, Transaction ID, or Session ID.

17. A communication device, characterized in that, include: A module or unit for performing the method as described in any one of claims 1 to 5, or a module or unit for performing the method as described in any one of claims 6 to 12, or a module or unit for performing the method as described in any one of claims 13 to 16.

18. A communication device, characterized in that, include: A processor and a memory, the processor being coupled to the memory for storing a computer program, the computer program being executed by the processor causing the apparatus to perform the method as claimed in any one of claims 1 to 5, or the method as claimed in any one of claims 6 to 12, or the method as claimed in any one of claims 13 to 16.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed on a computer, causes the computer to perform the method as described in any one of claims 1 to 5, or the method as described in any one of claims 6 to 12, or the method as described in any one of claims 13 to 16.

20. A computer program product, characterized in that, include: A computer program, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 5, or the method as described in any one of claims 6 to 12, or the method as described in any one of claims 13 to 16.

Images