Service request method, network side equipment and storage medium

Abstract

The invention discloses a service request method, network side equipment and a storage medium, and belongs to the technical field of wireless communication, the service request method comprises the following steps: a first radio access network RAN node receives an environment energy enabled Internet of Things AIoT service request sent by a core network node, the AIoT service request carries information of an AIoT reader-writer or an AIoT device; the first RAN node forwards the AIoT service request to a second RAN node, and the second RAN node is used for paging the AIoT reader-writer or the AIoT device executing the AIoT service.

Description

Technical Field

[0001] This application belongs to the field of wireless communication technology, specifically relating to a service request method, network-side device, and storage medium. Background Technology

[0002] In the Ambient Power-Enabled Internet of Things (AIoT) of related technologies, a possible connection topology is as follows: Figure 1a As shown, the base station functions as an AIoT reader; this base station can be called a Radio Access Network (RAN) reader. The application server communicates with AIoT devices via the core network and the base station for data transmission and signaling exchange. Another possible connection topology is as follows... Figure 1b As shown, the intermediate node undertakes the function of AIoT reader / writer. This intermediate node can be a user terminal (User Equipment, UE), which can be called a UE reader / writer. The application server transmits data and exchanges signaling with AIoT devices through the core network, base station and UE.

[0003] However, in related technologies, base stations that communicate with the core network may be unable to communicate with AIoT devices or AIoT readers for some reason. This may cause service requests sent by the application server to the AIoT device through the core network to fail to reach the AIoT device or AIoT reader, thereby preventing the AIoT service from being executed. Summary of the Invention

[0004] This application provides a service request method, a network-side device, and a storage medium, which can solve the problem that service requests sent from the core network to AIoT devices cannot reach the AIoT devices or AIoT readers.

[0005] In a first aspect, a service request method is provided, comprising: a first radio access network (RAN) node receiving an ambient energy-enabled Internet of Things (AIoT) service request sent by a core network node, wherein the AIoT service request carries information about an AIoT reader or AIoT device; the first RAN node forwarding the AIoT service request to a second RAN node, wherein the second RAN node is used to page the AIoT reader or AIoT device performing the AIoT service.

[0006] Secondly, a service request execution method is provided, comprising: a second RAN node receiving an AIoT service request forwarded by a first RAN node, wherein the AIoT service request carries information about an AIoT reader or AIoT device; and the second RAN node paging the AIoT reader or AIoT device executing the AIoT service.

[0007] Thirdly, a service request apparatus is provided, comprising: a receiving module for receiving an AIoT service request sent by a core network node, wherein the AIoT service request carries information about an AIoT reader or AIoT device; and a sending module for forwarding the AIoT service request to a second RAN node, wherein the second RAN node is used to page the AIoT reader or AIoT device performing the AIoT service.

[0008] Fourthly, a service request execution apparatus is provided, comprising: a receiving module for receiving an AIoT service request forwarded by a first RAN node, wherein the AIoT service request carries information about an AIoT reader or AIoT device; and a sending module for paging the AIoT reader or AIoT device executing the AIoT service.

[0009] Fifthly, a service request apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0010] In a sixth aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect, or implementing the steps of the method as described in the second aspect.

[0011] In a seventh aspect, a network-side device is provided, including a processor and a communication interface, wherein the processor is configured to perform the steps of the method described in the first aspect, or to perform the steps of the method described in the second aspect, and the communication interface is configured to be coupled to the processor.

[0012] Eighthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0013] A ninth aspect provides a wireless communication system, comprising: a first RAN node and a second RAN node, wherein the first RAN node is configured to perform the steps of the method described in the first aspect, and the second RAN node is configured to perform the steps of the method described in the second aspect.

[0014] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0015] Eleventhly, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0016] In this embodiment, after receiving an AIoT service request from the core network node, the first wireless RAN node forwards the AIoT service request to the second RAN node. The second RAN node then pages the AIoT reader or AIoT device that performs the AIoT service. This allows the first RAN node to send the AIoT service request to the second RAN node, which then selects the AIoT reader or AIoT device to perform the AIoT service. This solves the problem that service requests sent from the core network to the AIoT device cannot reach the AIoT device or AIoT reader, ensuring the successful execution of the AIoT service. Attached Figure Description

[0017] Figure 1a This diagram illustrates a block diagram of a wireless communication system to which embodiments of this application may be applied; Figure 1b This diagram illustrates a block diagram of another wireless communication system to which embodiments of this application may be applied; Figure 2a This is a schematic diagram of label inventory in related technologies; Figure 2b This is a schematic diagram of the signaling between the reader and the tag in related technologies; Figure 3a A flowchart for an AIoT device inventory process in related technologies; Figure 3b A flowchart for another type of AIoT device inventory in related technologies; Figure 4 This is a flowchart of a business request method in an embodiment of this application; Figure 5 This is another flowchart of the business request method in the embodiments of this application; Figure 6 This is an interactive flowchart of a business request method in an embodiment of this application; Figure 7 This is another interactive flowchart of the business request method in the embodiments of this application; Figure 8 This is another interactive flowchart of the business request method in the embodiments of this application; Figure 9 This is a schematic diagram of a service request device in an embodiment of this application; Figure 10 This is another structural schematic diagram of the service request device in the embodiments of this application; Figure 11 This illustration shows a structural diagram of a communication device provided in an embodiment of this application; Figure 12 This diagram illustrates the hardware structure of a network-side device according to an embodiment of this application. Detailed Implementation

[0018] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0019] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0020] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc.; an indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0021] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0022] Figure 1a and Figure 1bBlock diagrams of a wireless communication system applicable to embodiments of this application are shown below. The wireless communication system includes a core network (CN) device 11, a RAN node 12, a terminal 13, and an AIoT device 14. The terminal 13 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in the embodiments of this application. RAN node 12 can also be referred to as RAN equipment, radio access network function, or radio access network unit. RAN node 12 may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.In this context, a base station may be referred to as a Node B (NB), an Evolved Node B (eNB), a Next Generation Node B (gNB), a New Radio Node B (NR Node B), an Access Point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a Radio Base Station, a Radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The base station is not limited to any specific technical terminology. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for introduction, and the specific type of base station is not limited.

[0023] Core network equipment 11, also known as a core network node, core network function, or core network element, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), and Local NEF. The core network equipment (NEF, or L-NEF) includes the following functions: Binding Support Function (BSF), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0024] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0025] The AIoT device 14 features ultra-low complexity and ultra-low power consumption. It is a device used to implement IoT services. The AIoT device 14 can be powered through energy harvesting; it may not have a battery or may have limited energy storage capacity (e.g., using a capacitor). This type of device has low overall power consumption, including low-power signal reception and low-power signal transmission. Due to its low overall power consumption, the energy for communication can be derived from the environment, such as wind power, kinetic energy, heat energy, or radio frequency (RF) signals. It can also be referred to as an Ambient IoT or Passive IoT device, or a response device.

[0026] In related technologies, environmental IoT devices can be characterized based on their energy storage capacity and ability to generate and transmit radio frequency signals. AIoT devices 14 can be of the following types: 1) Device A: No energy storage, no independent signal generation / amplification, i.e., backscatter transmission.

[0027] 2) Device B: It has energy storage but no independent signal generation, i.e., backscatter transmission. The use of stored energy can include amplification of the reflected signal.

[0028] 3) Device C: It has energy storage and independent signal generation, i.e., an active radio frequency component for transmission.

[0029] In related technologies, tags in Radio Frequency Identification (RFID) systems are also considered AIoT devices14. A reader identifies the IDs and reads data from backscatter communication (BSC) devices (i.e., tags) within the coverage area. Since RFID was initially used for automated inventory management of large quantities of goods, the process of identifying tags and reading data is also known as inventory management.

[0030] Figure 2a A schematic diagram of the inventory process for a tag is shown, such as... Figure 2aAs shown, after the reader sends a query command, the tag responds with a reply. For example, the tag generates a 16-bit random number and sends it to the reader. Then, the reader sends the sequence to the tag via an acknowledgment (ACK) command. After the tag successfully verifies the sequence in the ACK, it sends the relevant data to the reader.

[0031] Figure 2b The commonly used control commands in RFID are shown in Table 1.

[0032] Table 1.

[0033] Figure 3a It shows in Figure 1a The business process diagram for AIoT inventory under the topology connection shown is as follows: Figure 3a As shown, this business process mainly includes the following steps: Step 1: The AIoT core network sends an inventory request to the AIoT RAN nodes; Step 2: The AIoT RAN node sends an inventory response to the AIoT core network; Step 3: The AIoT RAN node and AIoT devices perform the inventory process through the AIoT interface; Step 4a: The AIoT RAN node sends an inventory report to the AIoT core network; Step 4b, optionally, if there are multiple AIoT devices, the AIoT RAN node continues to send inventory reports of other AIoT devices to the AIoT core network.

[0034] Figure 3b It shows in Figure 1b The business process diagram for AIoT inventory under the topology connection shown is as follows: Figure 3b As shown, this business process mainly includes the following steps: Step 1: The AIoT core network sends an inventory request to the AIoT-enabled gNB; Step 2: The AIoT-enabled gNB sends an inventory response to the AIoT core network; Step 3: The AIoT-enabled gNB, AIoT-enabled UE, and AIoT device perform the inventory process through the AIoT interface and the air interface (Uu). Step 4a: The AIoT RAN node sends an inventory report to the AIoT core network; Step 4b, optionally, if there are multiple AIoT devices, the AIoT RAN node continues to send inventory reports of other AIoT devices to the AIoT core network.

[0035] However, in related technologies, base stations communicating with the core network may be unable to communicate with AIoT devices or AIoT readers for various reasons. For example, in dual connectivity (DC) deployment scenarios, such as the 4G and 5G dual connectivity (EUTRA-NR Dual Connectivity, EN-DC) scenario, the EN-DC master node (MN) only supports the Long Term Evolution (LTE) air interface, and the MN cannot directly execute AIoT tasks / services with AIoT devices (LTE Uu does not support AIoT technology). Another example is when RAN node 1 receives an AIoT task / service request initiated by the CN node; if BS1 resources are insufficient or the AIoT device is not within BS1 coverage, BS1 cannot execute the AIoT task / service with the AIoT device. This may result in the application server's service requests sent to the AIoT device through the core network failing to reach the AIoT device or AIoT reader, thus preventing the execution of AIoT services.

[0036] To address the aforementioned issues, this application provides a service request method, network-side device, and storage medium. In the technical solution provided in this application, a CN node (e.g., an AIoT function node, AMF node) initiates an AIoT service request to RAN node 1 (e.g., a dual-connection master node MN). RAN node 1 selects RAN node 2 (e.g., a dual-connection auxiliary node SN, or a RAN node adjacent to RAN node 1) and forwards the AIoT service request to RAN node 2. RAN node 2 then selects an AIoT reader / AIoT device (AIoT terminal / device) to execute the AIoT service. Alternatively, the CN node (e.g., an AIoT function node, AMF node) forwards the AIoT service request to RAN node 2 (e.g., a dual-connection auxiliary node SN) through RAN node 1 (e.g., a dual-connection master node MN). RAN node 2 then selects an AIoT reader / AIoT device (AIoT terminal / device) to execute the AIoT service.

[0037] The technical solutions provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0038] Figure 4 This diagram illustrates a service request method according to an embodiment of this application. This method 400 can be executed by a first RAN node. In other words, the method can be executed by software or hardware installed on the first RAN node. Figure 4 As shown, the method may include the following steps.

[0039] S410, the first RAN node receives an AIoT service request sent by the core network node, wherein the AIoT service request carries information about an AIoT reader or AIoT device.

[0040] In this embodiment of the application, the core network node (e.g., AIoT function or AMF) can send an AIoT service request carrying information about the AIoT reader or AIoT device to the first RAN node when the AIoT reader or AIoT device needs to perform AIoT services. For example, the AIoT service request may carry the identification information of the AIoT reader or AIoT device, or the location information of the AIoT reader or AIoT device.

[0041] S412, the first RAN node forwards the AIoT service request to the second RAN node, wherein the second RAN node is used to page the AIoT reader or AIoT device performing the AIoT service.

[0042] Optionally, in this embodiment of the application, the AIoT service request may carry AIoT service resource request information, which may include at least one of the following: 1) First information, the first information is used to instruct the configuration of AIoT service resources for the AIoT reader or AIoT device through the Signalalling RadioBearer (SRB) 3; 2) Second information, which is used to instruct the configuration of AIoT service resources for the AIoT reader or AIoT device by splitting SRB 1; 3) Third information, which is used to instruct the AIoT reader or AIoT device to configure AIoT service resources through a dedicated SRB. In other words, the third information instructs the configuration of AIoT service resources through a newly added SRB.

[0043] In this embodiment, after receiving an AIoT service request, the first RAN node can forward the AIoT service request to the second RAN node, which then pages the AIoT reader or AIoT device executing the AIoT service. This allows the first RAN node to send the AIoT service request to the second RAN node, which then selects the AIoT reader or AIoT device to execute the AIoT service. This solves the problem that service requests sent from the core network to the AIoT device cannot reach the AIoT device or AIoT reader, ensuring the successful execution of the AIoT service.

[0044] In some embodiments, the information of the AIoT reader or AIoT device includes: the location information of the AIoT reader or AIoT device. In S412, the first RAN node forwarding the AIoT service request to the second RAN node may include: the first RAN node forwarding the AIoT service request to the second RAN node based on the location information of the AIoT reader or AIoT device, or whether the second RAN node supports AIoT services, wherein the second RAN node supports AIoT services. For example, if the first RAN node is MN, MN can interact with surrounding secondary nodes (SNs) to select an SN that supports AIoT services as the second RAN node. Alternatively, based on the location information of the AIoT reader or AIoT device, an SN whose coverage area includes the location of the AIoT reader or AIoT device and which supports AIoT services can be selected as the second RAN node.

[0045] In one embodiment, the AIoT reader or the AIoT device is located within the coverage area of ​​the second RAN node. The location of the AIoT reader or the AIoT device can be determined using the location information of the AIoT reader or the AIoT device.

[0046] In the above embodiments, the first RAN node can select a second RAN node whose coverage area includes the location of the AIoT reader or the AIoT device or supports AIoT services, based on the location information of the AIoT reader or the AIoT device, and forward the AIoT service request to the second RAN node. This ensures that the second RAN node can page the AIoT reader or the AIoT device, thus ensuring the successful execution of subsequent AIoT services.

[0047] In some implementations, in the above embodiments, after S412, the method may further include the following steps: Step 1: The first RAN node receives feedback information sent by the second RAN node in response to the AIoT service request; Step 2: If the feedback information indicates that the second RAN node accepts the AIoT service request, the first RAN node and the second RAN node negotiate to configure AIoT service resources for the AIoT reader or AIoT device.

[0048] In the above implementation, when the first RAN node receives feedback information instructing the second RAN node to accept the AIoT service request, it negotiates with the second RAN node to configure AIoT service resources for the AIoT reader or AIoT device, thereby enabling the AIoT reader or AIoT device to use the AIoT service resources to transmit AIoT service data and ensuring the successful execution of the AIoT service.

[0049] In the above embodiments, optionally, when the first RAN node and the second RAN node negotiate the configuration of AIoT service resources for the AIoT reader or AIoT device, they can negotiate to stagger the working time of the air interface (Uu) and AIoT to reduce interference. For example, the first RAN node and the second RAN node negotiate the time division multiplexing (TDM) mode to configure the AIoT service resources on time units without air interface transmission.

[0050] In the above embodiments, optionally, the feedback information may include at least one of the following: 1) Fourth information, the fourth information being used to instruct the second RAN node to accept the AIoT service request; 2) Fifth information, which is used to instruct the second RAN node to agree to configure resources for the AIoT reader or AIoT device; 4) Sixth information, which is used to indicate the AIoT service resources that the second RAN node recommends to be configured for the AIoT reader or AIoT device.

[0051] The feedback information provided above allows the first RAN node to know the specific details of the second RAN node's acceptance of the AIoT service request.

[0052] In some embodiments, prior to S410, the method may further include: the first RAN node sending information about a second RAN node related to the first RAN node to the core network node. For example, the first RAN node may send information about an SN node related to the first RAN node to the core network node, or the first RAN node may send information about neighboring RAN nodes of the first RAN node to the core network node. Optionally, the information about the second RAN node may include at least one of the following: location information, identification information, address information, and capability information of the second RAN node, which is not limited in specific embodiments of this application.

[0053] In the above embodiments, since the first RAN node sends the information of the second RAN node to the core network node in advance, the core network node can directly select the second RAN node to receive the AIoT service request when sending it, and transparently forward the AIoT service request to the second RAN node through the first RAN node. Therefore, in some implementations of these embodiments, S412 may include: the first RAN node forwarding the AIoT service request to the second RAN node based on the destination address of the AIoT service request. Here, the destination address is the address corresponding to the second RAN node; therefore, after receiving the AIoT service request, the first RAN node transparently forwards the AIoT service request to the second RAN node.

[0054] In some embodiments of the above examples, after S412, the method may further include the following steps: Step 1: The first RAN node receives feedback information sent by the second RAN node in response to the AIoT service request; Step 2: The first RAN node forwards the feedback information to the core network node.

[0055] In the above implementation, after receiving the AIoT service request, the second RAN node can send feedback information to the core network node through the first RAN node, and the first RAN node forwards the feedback information to the core network node.

[0056] In some implementations, when the feedback information indicates that the second RAN node accepts the AIoT service request, the first RAN node and the second RAN node negotiate the AIoT service resources configured for the AIoT reader or AIoT device. Then, the first RAN node can send confirmation information to the core network node, wherein the confirmation information confirms that the first RAN node and the second RAN node have completed the negotiation. Through these implementations, the first RAN node can negotiate the AIoT service resources configured for the AIoT reader or AIoT device with the second RAN node, thereby enabling the transmission of AIoT services using these AIoT service resources. Furthermore, the first RAN node can send confirmation information to the core network node, allowing the core network node to know that the first RAN node and the second RAN node have completed the negotiation, and thus execute the AIoT service.

[0057] In some implementations, when the feedback information indicates that the second RAN node rejects the AIoT service request, the feedback information includes at least one of the following: 1) First indication information, wherein the first indication information is used to instruct the second RAN node to reject the AIoT service request; 2) Second indication information, which is used to instruct the second RAN node to refuse to configure resources for the AIoT reader or AIoT device; 3) Third indication information, which is used to indicate the reason for the second RAN node's rejection.

[0058] Through the above implementation method, the core network node can know the specific circumstances under which the second RAN node rejects the above AIoT service request, and then can reselect the second RAN node to send the AIoT service request.

[0059] In some implementations, when the feedback information instructs the second RAN node to accept the AIoT service request, the content of the feedback information is similar to that in the above embodiments and may include at least one of the following: 1) Fourth information, the fourth information being used to instruct the second RAN node to accept the AIoT service request; 2) Fifth information, which is used to instruct the second RAN node to agree to configure resources for the AIoT reader or AIoT device; 4) Sixth information, which is used to indicate the AIoT service resources that the second RAN node recommends to be configured for the AIoT reader or AIoT device.

[0060] In the above embodiments, optionally, after the first RAN node and the second RAN node negotiate the AIoT service resources configured for the AIoT reader or AIoT device, the method further includes one of the following: 1) The first RAN node pages the AIoT reader or AIoT device through the second RAN node. In some embodiments, the AIoT service request sent by the core network device may include paging information, or the core network device may send paging information to the first RAN node in addition to the AIoT service request. The first RAN node may then page the AIoT reader or AIoT device through the second RAN node based on the paging information.

[0061] 2) The first RAN node forwards the paging information to the second RAN node, wherein the paging information instructs the second RAN node to initiate a paging message for the AIoT reader or AIoT device. In some embodiments, if the second RAN node has paging capabilities, the first RAN node can forward the paging information to the second RAN node, which then initiates a paging message for the AIoT reader or AIoT device. For example, the core network node can transparently forward the paging information to the second RAN node through the first RAN node, and the second RAN node can then initiate a paging message for the AIoT reader or AIoT device based on this paging information.

[0062] In the above embodiments, the first RAN node can be MN, and the second RAN node can be SN.

[0063] In one implementation, the first RAN node can be the MN in a dual-connection or multi-connection configuration, and the second RAN node can be the SN in a dual-connection or multi-connection configuration.

[0064] In the first embodiment, S412 may include: the first RAN node paged the AIoT reader or AIoT device and forwarded the AIoT service request to an adjacent second RAN node. For example, when the AIoT reader or AIoT device is in Radio Resource Control (RRC) idle state or RRC-INACTIVE state, the first RAN node forwards the AIoT service request to the adjacent second RAN node, which then pages the AIoT reader or AIoT device. Simultaneously, the first RAN node may also page the AIoT reader or AIoT device. In these embodiments, the first RAN node can page the AIoT reader or AIoT device and forward the AIoT service request to the adjacent second RAN node, which then pages the AIoT reader or AIoT device. Therefore, it is possible to ensure that the AIoT reader or AIoT device is paged as much as possible.

[0065] In the second embodiment, S412 may include: if the first RAN node fails to page the AIoT reader or AIoT device, it forwards the AIoT service request to an adjacent second RAN node. For example, if the AIoT reader or AIoT device is in RRC-idle or RRC-INACTIVE mode, the first RAN node pages the AIoT reader or AIoT device. If the AIoT reader or AIoT device does not respond to the first RAN node's page, the first RAN node forwards the AIoT service request to an adjacent second RAN node, which then pages the AIoT reader or AIoT device. In these embodiments, the first RAN node can forward the AIoT service request to an adjacent second RAN node if pager failure occurs, ensuring that the AIoT reader or AIoT device is paged.

[0066] In the above embodiments, the failure of the first RAN node to page the AIoT reader or AIoT device may include the following two situations: 1) After the first RAN node sends a paging message, it does not receive a paging response from the AIoT reader or AIoT device within a specified time; 2) After the first RAN node sends a paging message, it receives a response from the AIoT reader or AIoT device within a specified time, but the paging fails for some reason, such as the paging failure caused by an uplink collision when the AIoT reader or AIoT device responds to the paging.

[0067] In the third embodiment, S412 may include: when the AIoT reader or AIoT device is in an inactive state, the first RAN node directly forwards the AIoT service request to an adjacent second RAN node. For example, when the AIoT reader or AIoT device is in an RRC inactive state, the first RAN node directly forwards the AIoT service request to an adjacent second RAN node, which then pages the AIoT reader or AIoT device to ensure that the AIoT reader or AIoT device is paged.

[0068] In the first to third embodiments described above, optionally, after forwarding the AIoT service request to the adjacent second RAN node, the method further includes: the first RAN node negotiating with the second RAN node to allocate AIoT service resources for the AIoT reader or AIoT device. Through this optional implementation, the first RAN node can negotiate with the second RAN node to allocate AIoT service resources for the AIoT reader or AIoT device, thereby enabling subsequent transmission of AIoT service data based on these AIoT service resources.

[0069] In the above embodiments, optionally, the first RAN node and the second RAN node negotiate the AIoT service resources configured for the AIoT reader or AIoT device, including one of the following: 1) The first RAN node and the second RAN node negotiate to configure AIoT service resources for the AIoT reader or AIoT device through SRB 3; 2) The first RAN node and the second RAN node negotiate to configure AIoT service resources for the AIoT reader or AIoT device by splitting SRB 1; 3) The first RAN node and the second RAN node negotiate to configure AIoT service resources for the AIoT reader or AIoT device through a dedicated SRB.

[0070] Through the above optional implementation methods, the first RAN node and the second RAN node can negotiate the way to configure AIoT service resources for the AIoT reader or AIoT device.

[0071] Based on the same technical concept, this application also provides another service request method. This method is executed by the aforementioned second RAN node.

[0072] It should be noted that the following embodiments mainly describe the operation of the second RAN node. For other matters not covered, please refer to the relevant description of method 400 above.

[0073] Figure 5 This diagram illustrates another flowchart of a service request method provided in an embodiment of this application, whereby the method 500 can be executed by a second RAN node. In other words, the method can be executed by software or hardware installed on the second RAN node. Figure 5 As shown, the method mainly includes the following steps.

[0074] S510, the second RAN node receives the AIoT service request forwarded by the first RAN node, wherein the AIoT service request carries information about an AIoT reader or AIoT device.

[0075] The first RAN node can forward AIoT service requests to the second RAN node using the various implementation methods described in method 400 above. For details, please refer to the relevant descriptions in method 400 above, which will not be repeated here.

[0076] S512, the second RAN node pages the AIoT reader or AIoT device performing the AIoT service.

[0077] In this embodiment of the application, after receiving an AIoT service request, the second RAN node can page the AIoT reader or AIoT device that performs the AIoT service, and then perform the AIoT service through the paged AIoT reader or AIoT device to ensure the successful execution of the AIoT service.

[0078] In some embodiments, after S510, the method may further include: the second RAN node sending feedback information regarding the AIoT service request. In these embodiments, the second RAN node can use this feedback information to indicate whether it accepts the AIoT service request.

[0079] Optionally, if the feedback information indicates that the second RAN node accepts the AIoT service request, the feedback information may include at least one of the following: 1) Fourth information, the fourth information being used to instruct the second RAN node to accept the AIoT service request; 2) Fifth information, which is used to instruct the second RAN node to agree to configure resources for the AIoT reader or AIoT device; 4) Sixth information, which is used to indicate the AIoT service resources that the second RAN node recommends to be configured for the AIoT reader or AIoT device.

[0080] Optionally, if the feedback information indicates that the second RAN node rejects the AIoT service request, the feedback information may include at least one of the following: 1) First indication information, which is used to instruct the second RAN node to reject the AIoT service request; 2) Second indication information, which is used to instruct the second RAN node to refuse to configure resources for the AIoT reader or AIoT device; 3) Third indication information, which is used to indicate the reason for the second RAN node's rejection.

[0081] In some embodiments, the method may further include: when the feedback information indicates that the second RAN node accepts the AIoT service request, the second RAN node negotiates with the first RAN node to allocate AIoT service resources to the AIoT reader or AIoT device. By negotiating the AIoT service resources allocated to the AIoT reader or AIoT device, AIoT services can be subsequently transmitted using the allocated AIoT service resources.

[0082] In some implementations of these embodiments, the AIoT service resources negotiated between the second RAN node and the first RAN node for the AIoT reader or AIoT device may include one of the following: 1) The second RAN node negotiates with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device through SRB 3; 2) The second RAN node negotiates with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device by splitting SRB 1; 3) The second RAN node negotiates with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device through a dedicated SRB.

[0083] During the aforementioned negotiation process, the AIoT service resources negotiated between the second RAN node and the first RAN node can stagger the working hours of the Uu port and AIoT, thereby reducing interference.

[0084] In some embodiments, S512 may include: the second RAN node forwarding a paging message sent by the first RAN node, wherein the paging message is used to page the AIoT reader or AIoT device. In these embodiments, the first RAN node can page the AIoT reader or AIoT device through the second RAN node, thereby avoiding the problem that AIoT service requests cannot reach the AIoT reader or AIoT device because the first RAN node cannot directly write to the AIoT reader or AIoT device for communication.

[0085] In other embodiments, S512 may include: the second RAN node receiving paging information sent by the first RAN node, and initiating a paging message for the AIoT reader or AIoT device based on the paging information. In these embodiments, the first RAN node may forward the paging information sent by the core network node to the second RAN node, which then initiates the paging message for the AIoT reader or AIoT device. The paging information may be transparently forwarded by the core network node through the first RAN node, or the first RAN node may select the second RAN node to forward the paging information based on the received paging information.

[0086] In some embodiments, S512 may include: the second RAN node initiating a paging message for the AIoT reader or AIoT device based on the received AIoT service request. In these embodiments, the AIoT service request may carry paging information for the AIoT reader or AIoT device. The first RAN node may forward the AIoT service request to the second RAN node after receiving it, and the second RAN node may initiate paging of the AIoT reader or AIoT device. In these embodiments, the first RAN node may initiate a paging message for the AIoT reader or AIoT device based on the AIoT service request, or it may directly forward the AIoT service request. The first RAN node may forward the AIoT service request to the second RAN node if paging of the AIoT reader or AIoT device fails, or it may forward the AIoT service request to the second RAN node before receiving a paging response from the AIoT reader or AIoT device. For details, please refer to the relevant description in method 400 above.

[0087] In some embodiments, after S512, the method may further include: receiving a paging response sent by the AIoT reader or AIoT device, and forwarding AIoT service data between the core network node and the AIoT reader or AIoT device. In these embodiments, after receiving the paging response sent by the AIoT reader or AIoT device, the second RAN node can forward the AIoT service data between the core network node and the AIoT reader or AIoT device through the second RAN node; alternatively, the second RAN node may directly forward the AIoT service data between the core network node and the AIoT reader or AIoT device to the core network node and the AIoT reader or AIoT device, depending on the capabilities of the second RAN node.

[0088] In this embodiment, taking a DC scenario as an example, assuming an AIoT reader (e.g., an AIoT UE reader) or AIoT device is covered by the secondary node SN1, the CN node (e.g., an AIoT function node, AMF node) initiates an AIoT service request to the MN. The MN can then interact with surrounding secondary nodes SN based on the location information of the AIoT reader or AIoT device, forwarding the AIoT service request to SN1 and negotiating with SN1 to configure AIoT service resources for the AIoT reader or AIoT device. The MN can select an SN based on whether the SN supports AIoT services. Figure 6 This diagram illustrates an interaction flow for a business request method, such as... Figure 6 As shown, the interaction flow of the business request method in this scenario includes the following steps: S601, the CN node sends a service request to the MN, which carries information about the AIoT reader or AIoT device.

[0089] S602, MN interacts with the surrounding SN and selects SN1.

[0090] Optionally, MN can select an SN based on the location information of the AIoT reader or AIoT device or whether the SN supports AIoT services. The selected SN1 can be a SN whose coverage includes the location of the AIoT reader or AIoT device or a SN that supports AIoT services.

[0091] S603, MN forwards the above service request to SN1.

[0092] The service request may include AIoT service resource request information, which may include one of the following: 1) Information instructing the SN to configure AIoT service resources for the AIoT reader or AIoT device via SRB 3; 2) Information instructing the SN to configure AIoT service resources for the AIoT reader or AIoT device via split SRB 1; 3) Information instructing the SN to configure AIoT service resources for AIoT readers or AIoT devices via the new SRB.

[0093] S604, SN1 decides to respond to this service request.

[0094] After receiving a service request from MN, SN1 decides to respond to the service request. SN1 may send feedback information back to MN. Optionally, the feedback information from SN1 may include at least one of the following: 1) Information instructing SN to agree to MN's business requests; 2) Information instructing the SN to agree to configure AIoT radio resources for the AIoT reader or AIoT device; 3) Suggestions from SN1 for configuring AIoT wireless resources to MN, such as SN1 suggesting a configuration method similar to that for SRB.

[0095] S605, MN and SN1 negotiate to configure AIoT service resources for AIoT readers or AIoT devices.

[0096] The negotiation of AIoT service resources between MN and SN1 nodes may include how to stagger the working hours of Uu and AIoT to reduce interference, such as MN and SN1 negotiating the TDM pattern.

[0097] S606, MN pages AIoT readers or AIoT devices via SN1.

[0098] Once the SN and MN have agreed, the MN can page the AIoT reader or AIoT device through SN1 at the request of the CN node. Alternatively, if SN1 has paging capabilities, the CN can transparently forward paging information to SN1 through the MN, and SN1 can then page the AIoT reader or AIoT device. For example, the MN can feed back the selected SN1 information to the core network node, and the core network node can transparently forward the paging information to SN1 through the MN. Or, the MN can send the received paging information to SN1.

[0099] S607, SN1 receives the paging response from the AIoT reader or AIoT device, and the CN node and the AIoT reader or AIoT device can forward AIoT service data through MN and SN1.

[0100] In this embodiment, taking a DC scenario as an example, assuming the AIoT reader (e.g., AIoT UE reader) or AIoT device is covered by the secondary node SN1, the MN can feed back SN information related to the MN to the CN node (e.g., AIoT function, AMF), such as SN identifier (ID), SN cell information, SN address, etc. When the CN node initiates an AIoT service request to the AIoT reader or AIoT device, the CN node can directly forward the AIoT service request to the SN1 connected to the MN (transparently forwarding it to SN1 to the MN). The AIoT service request sent by the CN node to SN1 may include request information for configuring AIoT service resources for the AIoT reader or AIoT device. The CN node selects SN1 based on whether the SN supports AIoT services. Figure 7This illustrates another interactive flow diagram for a business request method, such as... Figure 7 As shown, the interaction flow of the business request method in this scenario includes the following steps: S701, the MN feeds back relevant SN information of the MN to the CN node, such as SN ID, SN address and SN cell information.

[0101] S702, the CN node transparently forwards AIoT service requests to SN1 through the MN. The AIoT service request carries information about the AIoT reader or AIoT device.

[0102] Optionally, the CN node can select an SN based on the location information of the AIoT reader or AIoT device, or whether the SN supports AIoT services. The selected SN1 can be a SN whose coverage includes the location of the AIoT reader or AIoT device or a SN that supports AIoT services.

[0103] The AIoT service request may carry AIoT service resource request information, which may include one of the following: 1) Information instructing the SN to configure AIoT service resources for the AIoT reader or AIoT device via SRB 3; 2) Information instructing the SN to configure AIoT service resources for the AIoT reader or AIoT device via split SRB 1; 3) The AIoT reader or AIoT device SN configures AIoT service resources for the AIoT reader or AIoT device through the new SRB.

[0104] S703, SN1 decides to respond to this service request.

[0105] S704, SN1 transparently forwards SN1's feedback information (ACK or NACK) to the CN node through MN.

[0106] After SN1 receives the service request sent by MN, SN1 decides to respond to the service request. SN1 can transparently forward the feedback information to the CN node.

[0107] Optionally, if SN1 rejects the request initiated by the CN node, SN1's feedback information shall include at least one of the following: 1) Information instructing the SN to reject the service request of the CN node, wherein the information instructing the SN to reject the request of the CN node is forwarded to the CN node through the MN.

[0108] 2) Instructs the SN to refuse to configure AIoT radio resources for the AIoT reader or AIoT device; 3) Reasons for rejection, such as insufficient SN1 resources, the AIoT reader or AIoT device not being covered by SN, or the AIoT reader or AIoT device not responding to paging.

[0109] Optionally, if SN1 accepts the request initiated by MN, then SN1's feedback information includes at least one of the following: 1) Information instructing the SN to agree to the CN node's service request; 2) Instruct the SN to agree to configure AIoT radio resources for the AIoT reader or AIoT device.

[0110] S705, MN and SN1 negotiate to configure AIoT service resources for AIoT readers or AIoT devices.

[0111] The negotiation of AIoT service resources between MN and SN1 nodes may include how to stagger the working hours of Uu and AIoT to reduce interference, such as MN and SN1 negotiating the TDM pattern.

[0112] S706, MN sends a confirmation to the CN node regarding the negotiation with SN1.

[0113] S707, MN pages AIoT readers or AIoT devices via SN1.

[0114] Once the SN and MN have agreed, the MN can page the AIoT reader or AIoT device through SN1 at the request of the CN node. Alternatively, if SN1 has paging capabilities, the CN can transparently forward paging information to SN1 through the MN, and SN1 can then page the AIoT reader or AIoT device.

[0115] S708, SN1 receives the paging response from the AIoT reader or AIoT device, and the CN node and the AIoT reader or AIoT device can forward AIoT service data through MN and SN1.

[0116] In this embodiment, when an AIoT reader (e.g., an AIoT UE reader) or AIoT device is covered by BS2, the CN node initiates an AIoT service request to BS1. The AIoT service request may include information about the AIoT reader or AIoT device and information about the neighboring BS2. The AIoT service request may also include AIoT service resource request information. Figure 8 This illustrates another interactive flow diagram for a business request method, such as... Figure 8 As shown, the interaction flow of the business request method in this scenario includes the following steps: S801, the CN node sends a service request to BS1, which carries information about the AIoT reader or AIoT device.

[0117] S802, BS1 paging AIoT reader or AIoT device.

[0118] This step is optional.

[0119] S803, BS1 decides to forward the AIoT service request to BS2.

[0120] Optionally, BS1 may decide to forward the AIoT service request to BS2 if it does not receive a paging response from the AIoT reader or device after paging it. Alternatively, BS1 may decide to forward the AIoT service request to BS2 after paging the AIoT reader or device but before determining whether the AIoT reader or device has responded to the paging. Or, BS1 may directly decide to forward the AIoT service request upon receiving it without initiating paging.

[0121] For example, when the UE reader is processing the RRC_IDLE state, and BS1 receives an AIoT service request initiated by the CN node, BS1's behavior may include one of the following: 1) BS1 pages the AIoT reader or AIoT device. If the AIoT reader or AIoT device does not respond to the BS1 page, BS1 forwards the AIoT service request to BS2, and BS2 can also page the AIoT reader or AIoT device.

[0122] 2) BS1 can page AIoT readers or AIoT devices. At the same time, BS1 can forward AIoT service requests to BS2, and BS2 can also page AIoT readers or AIoT devices.

[0123] When the UE reader or AIoT device is in RRC_INACTIVE mode, the CN node sends a service request to the gNB BS1 to which the UE reader is anchored. When BS1 receives the service request initiated by the CN node, BS1's behavior may include one of the following: 1) BS1 pages the UE reader via gNB BS2 and forwards the AIoT service request to BS2. BS2 then pages the UE reader.

[0124] 2) BS1 pages the AIoT reader or AIoT device. If the AIoT reader or AIoT device does not respond to the BS1 page, BS1 forwards the AIoT service request to BS2, and BS2 can also page the AIoT reader or AIoT device.

[0125] 3) BS1 can page AIoT readers or AIoT devices. At the same time, BS1 can forward AIoT service requests to BS2, and BS2 can also page AIoT readers or AIoT devices.

[0126] S804, BS1 forwards the above service request to BS2.

[0127] The service request may include AIoT service resource request information, which may include one of the following: 1) Information instructing the SN to configure AIoT service resources for the AIoT reader or AIoT device via SRB 3; 2) Information instructing the SN to configure AIoT service resources for the AIoT reader or AIoT device via split SRB 1; 3) Information instructing the SN to configure AIoT service resources for AIoT readers or AIoT devices via the new SRB.

[0128] S805, BS1 and BS2 negotiate the resources configured for AIoT readers or AIoT devices.

[0129] When negotiating AIoT service resources between BS1 and BS2 nodes, it may include how to stagger the working hours of Uu and AIoT to reduce interference, such as BS1 and BS2 negotiating TDM patterns.

[0130] S806, BS2 paging AIoT reader or AIoT device.

[0131] S807, BS2 receives the paging response from the AIoT reader or AIoT device, and the CN node and the AIoT reader or AIoT device can forward AIoT service data through BS1 or BS2.

[0132] In the technical solution provided in this application embodiment, when RAN node 1 receives an AIoT service request from CN node, RAN node 1 forwards the AIoT service request to the adjacent RAN node 2 and negotiates with RAN node 2 to execute the AIoT service request. The technical solution provided in this application embodiment can solve the problem of how to complete the AIoT service request issued by CN node in scenarios such as (NG)EN-DC or RAN node 1 being unable to page the AIoT reader / writer or AIoT device, thus improving the applicability of AIoT services.

[0133] The service request method provided in this application can be executed by a service request device. This application uses the execution of the service request method by a service request device as an example to illustrate the service request device provided in this application.

[0134] This application provides a service request device. As an example, the service request device may be a communication device or a component within a communication device, such as a chip. The communication device may be a network-side device or a server, etc. Exemplarily, the network-side device may include, but is not limited to, the types of RAN nodes 12 listed above; this application does not impose specific limitations.

[0135] The service request device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0136] For details, see Figure 9 When the service request device is a first RAN node or a component within the first RAN node, the service request device 900 includes a receiving module 901 for receiving an AIoT service request sent by a core network node, wherein the AIoT service request carries information about an AIoT reader or AIoT device; and a sending module 902 for forwarding the AIoT service request to a second RAN node, wherein the second RAN node is used to page the AIoT reader or AIoT device performing the AIoT service.

[0137] In one optional implementation, the information of the AIoT reader or AIoT device includes: the location information of the AIoT reader or AIoT device; the sending module 902 forwards the AIoT service request to the second RAN node, including: based on the location information of the AIoT reader or AIoT device, or whether the second RAN node supports AIoT services, forwarding the AIoT service request to the second RAN node, wherein the second RAN node supports AIoT services.

[0138] In one embodiment, the location of the AIoT reader or the AIoT device is within the coverage area of ​​the second RAN node.

[0139] In an optional implementation, the receiving module 901 is further configured to receive feedback information sent by the second RAN node in response to the AIoT service request; such as Figure 9 As shown, the device may further include a processing module 903, which is used to negotiate with the second RAN node to configure AIoT service resources for the AIoT reader or AIoT device when the feedback information indicates that the second RAN node accepts the AIoT service request.

[0140] In an optional implementation, the sending module 902 is further configured to send information about a second RAN node related to the first RAN node to the core network node.

[0141] In an optional implementation, the sending module 902 forwards the AIoT service request to the second RAN node, including: forwarding the AIoT service request to the second RAN node based on the destination address of the AIoT service request.

[0142] In an optional implementation, the receiving module 901 is further configured to receive feedback information sent by the second RAN node in response to the AIoT service request; the sending module 902 is further configured to forward the feedback information to the core network node.

[0143] In one alternative implementation, such as Figure 9 As shown, it may also include a processing module 903, which is used to negotiate with the second RAN node to configure AIoT service resources for the AIoT reader or AIoT device when the feedback information indicates that the second RAN node accepts the AIoT service request; the sending module 902 is also used to send confirmation information to the core network node, wherein the confirmation information is used to confirm that the first RAN node and the second RAN node have completed the negotiation.

[0144] In an optional implementation, when the feedback information indicates that the second RAN node rejects the AIoT service request, the feedback information includes at least one of the following: The first indication information is used to instruct the second RAN node to reject the AIoT service request; The second indication information is used to instruct the second RAN node to refuse to configure resources for the AIoT reader or AIoT device. The third indication information is used to indicate the reason for the second RAN node's rejection.

[0145] In one alternative implementation, the sending module 902 is further configured to: The AIoT reader or AIoT device is paged through the second RAN node; The paging information is forwarded to the second RAN node, wherein the paging information is used to instruct the second RAN node to initiate a paging message for the AIoT reader or AIoT device.

[0146] In one alternative implementation, the first RAN node is the master node and the second RAN node is the slave node.

[0147] In one optional implementation, the sending module 902 forwards the AIoT service request to the second RAN node, including one of the following: Page the AIoT reader or AIoT device and forward the AIoT service request to the adjacent second RAN node; If paging the AIoT reader or AIoT device fails, the AIoT service request will be forwarded to the adjacent second RAN node. If the AIoT reader or AIoT device is inactive, the AIoT service request is directly forwarded to the adjacent second RAN node.

[0148] In one alternative implementation, such as Figure 9As shown, it also includes: a processing module 903, used to negotiate with the second RAN node to configure AIoT service resources for the AIoT reader or AIoT device.

[0149] In an optional implementation, the AIoT service request also carries AIoT service resource request information.

[0150] In one optional implementation, the AIoT service resource request information includes at least one of the following: The first information is used to instruct the configuration of AIoT service resources for the AIoT reader or AIoT device via the signaling radio bearer SRB 3; The second information is used to instruct the configuration of AIoT service resources for the AIoT reader or AIoT device by splitting SRB 1; The third information is used to instruct the configuration of AIoT service resources for the AIoT reader or AIoT device through a dedicated SRB.

[0151] In one optional implementation, the feedback information includes at least one of the following: The fourth information is used to instruct the second RAN node to accept the AIoT service request; The fifth piece of information is used to instruct the second RAN node to agree to configure resources for the AIoT reader or AIoT device; The sixth information is used to indicate the AIoT service resources that the second RAN node recommends to be configured for the AIoT reader or AIoT device.

[0152] In an optional implementation, the processing module 903 negotiates with the second RAN node the AIoT service resources configured for the AIoT reader or AIoT device, including one of the following: Negotiate with the second RAN node to configure AIoT service resources for the AIoT reader or AIoT device via SRB 3; Negotiate with the second RAN node to configure AIoT service resources for the AIoT reader or AIoT device by splitting SRB 1; Negotiate with the second RAN node to configure AIoT service resources for the AIoT reader or AIoT device via a dedicated SRB.

[0153] See Figure 10When the service request device is a second RAN node or a component of the second RAN node, the service request device 1000 includes a receiving module 1001 for receiving an AIoT service request forwarded by a first RAN node, wherein the AIoT service request carries information about an AIoT reader or AIoT device; and a sending module 1002 for paging the AIoT reader or AIoT device performing the AIoT service.

[0154] In an optional implementation, the sending module 1002 is further configured to send feedback information in response to the AIoT service request.

[0155] In one alternative implementation, such as Figure 10 As shown, the device may further include a processing module 1003, which is used to negotiate with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device when the feedback information indicates that the second RAN node accepts the AIoT service request.

[0156] In an optional implementation, the processing module 1003 negotiates with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device, including one of the following: Negotiate with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device via SRB 3; Negotiate with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device by splitting SRB 1; Negotiate with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device via a dedicated SRB.

[0157] In one optional implementation, the feedback information includes at least one of the following: The fourth information is used to instruct the second RAN node to accept the AIoT service request; The fifth piece of information is used to instruct the second RAN node to agree to configure resources for the AIoT reader or AIoT device; The sixth information is used to indicate the AIoT service resources that the second RAN node recommends to be configured for the AIoT reader or AIoT device.

[0158] In an optional implementation, when the feedback information indicates that the second RAN node rejects the AIoT service request, the feedback information includes at least one of the following: The first indication information is used to instruct the second RAN node to reject the AIoT service request; The second indication information is used to instruct the second RAN node to refuse to configure resources for the AIoT reader or AIoT device. The third indication information is used to indicate the reason for the second RAN node's rejection.

[0159] In one optional implementation, the sending module 1002 pages the AIoT reader or AIoT device performing the AIoT service, including one of the following: Forward the paging message sent by the first RAN node, wherein the paging message is used to page the AIoT reader or AIoT device; Receive paging information sent by the first RAN node, and initiate a paging message to page the AIoT reader or AIoT device based on the paging information; Based on the received AIoT service request, a paging message is initiated to page the AIoT reader or AIoT device.

[0160] In an optional implementation, the receiving module 1001 is further configured to receive a paging response sent by the AIoT reader or AIoT device; the sending module 1002 is further configured to forward AIoT service data between the core network node and the AIoT reader or AIoT device.

[0161] The service request device provided in this application embodiment can achieve Figures 4 to 8 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0162] like Figure 11 As shown, this application embodiment also provides a communication device 1100, including a processor 1101 and a memory 1102. The memory 1102 stores a program or instructions that can run on the processor 1101. For example, when the communication device 1100 is a RAN node, when the program or instructions are executed by the processor 1101, they implement the various steps of the above-described service request method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0163] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 4The steps of the method embodiment shown in Figure 5 are applicable. This network-side device embodiment corresponds to the method embodiment of the first RAN node or the second RAN node described above. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0164] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 9 Or the service request device shown in 10. Figure 12 As shown, the network-side device 1200 includes: an antenna 1201, a radio frequency (RF) device 1202, a baseband device 1203, a processor 1204, and a memory 1205. The antenna 1201 is connected to the RF device 1202. In the uplink direction, the RF device 1202 receives information through the antenna 1201 and transmits the received information to the baseband device 1203 for processing. In the downlink direction, the baseband device 1203 processes the information to be transmitted and sends it to the RF device 1202. The RF device 1202 processes the received information and transmits it through the antenna 1201.

[0165] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1203, which includes a baseband processor.

[0166] The baseband device 1203 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 12 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 1205 via a bus interface to call the program in the memory 1205 and execute the network device operation shown in the above method embodiment.

[0167] The network-side device may also include a network interface 1206, such as a Common Public Radio Interface (CPRI).

[0168] Specifically, the network-side device 1200 in this application embodiment further includes: instructions or programs stored in memory 1205 and executable on processor 1204, wherein processor 1204 calls the instructions or programs in memory 1205 to execute. Figure 9 The methods executed by the modules shown in 10 can achieve the same technical effect, but to avoid repetition, they will not be described in detail here.

[0169] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described business request method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0170] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0171] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described service request method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0173] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described business request method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0174] This application embodiment also provides a service request system, including: a first RAN node and a second RAN node, wherein the first RAN node can be used to execute the steps of the service request method 400 as described above, and the second RAN node can be used to execute the steps of the service request method 500 as described above.

[0175] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0176] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0177] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A business request method, characterized in that, include: The first radio access network (RAN) node receives an environmental energy-enabled Internet of Things (AIoT) service request sent by the core network node, wherein the AIoT service request carries information about an AIoT reader or AIoT device. The first RAN node forwards the AIoT service request to the second RAN node, wherein the second RAN node is used to page the AIoT reader or AIoT device performing the AIoT service.

2. The method according to claim 1, characterized in that, The information of the AIoT reader or AIoT device includes: the location information of the AIoT reader or AIoT device; the first RAN node forwards the AIoT service request to the second RAN node, including: The first RAN node forwards the AIoT service request to the second RAN node based on at least one of the location information of the AIoT reader or the AIoT device and whether the second RAN node supports AIoT services, wherein the second RAN node supports AIoT services.

3. The method according to claim 1 or 2, characterized in that, After the first RAN node forwards the AIoT service request to the second RAN node, the method further includes: The first RAN node receives feedback information sent by the second RAN node in response to the AIoT service request; When the feedback information indicates that the second RAN node accepts the AIoT service request, the first RAN node and the second RAN node negotiate and configure AIoT service resources for the AIoT reader or AIoT device.

4. The method according to claim 1, characterized in that, Before the first radio access network (RAN) node receives the environmental energy-enabled IoT (AIoT) service request sent by the core network node, the method further includes: The first RAN node sends information about the second RAN node related to the first RAN node to the core network node.

5. The method according to claim 4, characterized in that, The first RAN node forwards the AIoT service request to the second RAN node, including: The first RAN node forwards the AIoT service request to the second RAN node based on the destination address of the AIoT service request.

6. The method according to claim 4 or 5, characterized in that, After the first RAN node forwards the AIoT service request to the second RAN node, the method further includes: The first RAN node receives feedback information sent by the second RAN node in response to the AIoT service request; The first RAN node forwards the feedback information to the core network node.

7. The method according to claim 6, characterized in that, The method further includes: When the feedback information indicates that the second RAN node accepts the AIoT service request, the first RAN node and the second RAN node negotiate and configure AIoT service resources for the AIoT reader or AIoT device. The first RAN node sends an acknowledgment message to the core network node, wherein the acknowledgment message is used to confirm that the first RAN node and the second RAN node have completed the negotiation.

8. The method according to claim 6, characterized in that, If the feedback information indicates that the second RAN node rejects the AIoT service request, the feedback information includes at least one of the following: The first indication information is used to instruct the second RAN node to reject the AIoT service request; The second indication information is used to instruct the second RAN node to refuse to configure resources for the AIoT reader or AIoT device. The third indication information is used to indicate the reason why the second RAN node rejects the AIoT service request.

9. The method according to claim 3 or 7, characterized in that, After the first RAN node and the second RAN node negotiate the AIoT service resources configured for the AIoT reader or AIoT device, the method further includes one of the following: The first RAN node paged the AIoT reader or AIoT device through the second RAN node; The first RAN node forwards the paging information to the second RAN node, wherein the paging information is used to instruct the second RAN node to initiate a paging message for the AIoT reader or AIoT device.

10. The method according to any one of claims 2 to 9, characterized in that, The first RAN node is the master node, and the second RAN node is the slave node.

11. The method according to claim 1, characterized in that, The first RAN node forwards the AIoT service request to the second RAN node, including one of the following: The first RAN node pages the AIoT reader or AIoT device and forwards the AIoT service request to the adjacent second RAN node; If the first RAN node fails to page the AIoT reader or AIoT device, it will forward the AIoT service request to the adjacent second RAN node. If the AIoT reader or AIoT device is inactive, the first RAN node directly forwards the AIoT service request to the adjacent second RAN node.

12. The method according to claim 11, characterized in that, After forwarding the AIoT service request to the adjacent second RAN node, the method further includes: The first RAN node and the second RAN node negotiate and configure AIoT service resources for the AIoT reader or AIoT device.

13. The method according to any one of claims 1 to 12, characterized in that, The AIoT service request also carries AIoT service resource request information.

14. The method according to claim 13, characterized in that, The AIoT service resource request information includes at least one of the following: The first information is used to instruct the configuration of AIoT service resources for the AIoT reader or AIoT device via the signaling radio bearer SRB 3; The second information is used to instruct the configuration of AIoT service resources for the AIoT reader or AIoT device by splitting SRB 1; The third information is used to instruct the configuration of AIoT service resources for the AIoT reader or AIoT device through a dedicated SRB.

15. The method according to claim 3 or 7, characterized in that, The feedback information includes at least one of the following: The fourth information is used to instruct the second RAN node to accept the AIoT service request; The fifth piece of information is used to instruct the second RAN node to agree to configure resources for the AIoT reader or AIoT device; The sixth information is used to indicate the AIoT service resources that the second RAN node recommends to be configured for the AIoT reader or AIoT device.

16. The method according to any one of claims 3, 7, and 12, characterized in that, The first RAN node and the second RAN node negotiate and configure AIoT service resources for the AIoT reader or AIoT device, including one of the following: The first RAN node and the second RAN node negotiate to configure AIoT service resources for the AIoT reader or AIoT device through SRB 3; The first RAN node and the second RAN node negotiate to configure AIoT service resources for the AIoT reader or AIoT device by splitting SRB 1; The first RAN node and the second RAN node negotiate to configure AIoT service resources for the AIoT reader or AIoT device through a dedicated SRB.

17. A business request method, characterized in that, include: The second RAN node receives an AIoT service request forwarded by the first RAN node, wherein the AIoT service request carries information about an AIoT reader or AIoT device. The second RAN node pages the AIoT reader or AIoT device that is performing AIoT services.

18. The method according to claim 17, characterized in that, After the second RAN node receives the AIoT service request forwarded by the first RAN node, the method further includes: The second RAN node sends feedback information in response to the AIoT service request.

19. The method according to claim 18, characterized in that, The method further includes: when the feedback information indicates that the second RAN node accepts the AIoT service request, the second RAN node negotiates with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device.

20. The method according to claim 19, characterized in that, The second RAN node negotiates with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device, including one of the following: The second RAN node negotiates with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device via SRB 3; The second RAN node negotiates with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device by splitting SRB 1; The second RAN node negotiates with the first RAN node to configure AIoT service resources for the AIoT reader or AIoT device through a dedicated SRB.

21. The method according to claim 19, characterized in that, The feedback information includes at least one of the following: The fourth information is used to instruct the second RAN node to accept the AIoT service request; The fifth piece of information is used to instruct the second RAN node to agree to configure resources for the AIoT reader or AIoT device; The sixth information is used to indicate the AIoT service resources that the second RAN node recommends to be configured for the AIoT reader or AIoT device.

22. The method according to claim 18, characterized in that, If the feedback information indicates that the second RAN node rejects the AIoT service request, the feedback information includes at least one of the following: The first indication information is used to instruct the second RAN node to reject the AIoT service request; The second indication information is used to instruct the second RAN node to refuse to configure resources for the AIoT reader or AIoT device. The third indication information is used to indicate the reason for the second RAN node's rejection.

23. The method according to any one of claims 17 to 22, characterized in that, The second RAN node pages the AIoT reader or AIoT device performing AIoT services, including one of the following: The second RAN node forwards the paging message sent by the first RAN node, wherein the paging message is used to page the AIoT reader or AIoT device; The second RAN node receives the paging information sent by the first RAN node and initiates a paging message to page the AIoT reader or AIoT device based on the paging information; The second RAN node initiates a paging message to page the AIoT reader or AIoT device based on the received AIoT service request.

24. The method according to any one of claims 17 to 22, wherein after the second RAN node pages the AIoT reader or AIoT device performing the AIoT service, the method further comprises: Receive the paging response sent by the AIoT reader or AIoT device, and forward the AIoT service data between the core network node and the AIoT reader or AIoT device.

25. A service request device, characterized in that, include: The receiving module is used to receive AIoT service requests sent by the core network node, wherein the AIoT service requests carry information about AIoT readers or AIoT devices. The sending module is used to forward the AIoT service request to the second RAN node, wherein the second RAN node is used to page the AIoT reader or AIoT device performing the AIoT service.

26. The apparatus according to claim 25, characterized in that, The information of the AIoT reader or AIoT device includes: the location information of the AIoT reader or AIoT device; the sending module forwards the AIoT service request to the second RAN node, including: Based on the location information of the AIoT reader or the AIoT device, or whether the second RAN node supports AIoT services, the AIoT service request is forwarded to the second RAN node, wherein the second RAN node supports AIoT services.

27. The apparatus according to claim 26, characterized in that, The receiving module is also used to receive feedback information sent by the second RAN node in response to the AIoT service request; The device further includes a processing module, configured to negotiate with the second RAN node to configure AIoT service resources for the AIoT reader or AIoT device upon receiving a request from the feedback information instructing the second RAN node to accept the AIoT service request.

28. The apparatus according to claim 25, characterized in that, The sending module is also used to send information about a second RAN node related to the first RAN node to the core network node.

29. The apparatus according to claim 28, characterized in that, The sending module forwards the AIoT service request to the second RAN node, including: forwarding the AIoT service request to the second RAN node based on the destination address of the AIoT service request.

30. The apparatus according to claim 25, characterized in that, The sending module will forward the AIoT service request to the second RAN node, including one of the following: Page the AIoT reader or AIoT device and forward the AIoT service request to the adjacent second RAN node; If paging the AIoT reader or AIoT device fails, the AIoT service request will be forwarded to the adjacent second RAN node. If the AIoT reader or AIoT device is inactive, the AIoT service request is directly forwarded to the adjacent second RAN node.

31. The apparatus according to claim 30, characterized in that, Also includes: The processing module is used to negotiate with the second RAN node to configure AIoT service resources for the AIoT reader or AIoT device.

32. A service request device, characterized in that, include: The receiving module is used to receive an AIoT service request forwarded by the first RAN node, wherein the AIoT service request carries information about an AIoT reader or AIoT device. The sending module is used to page the AIoT reader or AIoT device performing AIoT services.

33. The apparatus according to claim 32, characterized in that, The sending module is also used to send feedback information in response to the AIoT service request.

34. The apparatus according to claim 33, characterized in that, Also includes: The processing module is configured to negotiate with the first RAN node to allocate AIoT service resources to the AIoT reader or AIoT device when the feedback information indicates that the second RAN node accepts the AIoT service request.

35. The apparatus according to any one of claims 32 to 34, characterized in that, The sending module pages the AIoT reader or AIoT device performing AIoT services, including one of the following: Forward the paging message sent by the first RAN node, wherein the paging message is used to page the AIoT reader or AIoT device; Receive paging information sent by the first RAN node, and initiate a paging message to page the AIoT reader or AIoT device based on the paging information; Based on the received AIoT service request, a paging message is initiated to page the AIoT reader or AIoT device.

36. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1 to 24.

37. A readable storage medium, characterized in that, A program or instructions are stored on the readable storage medium, which, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 24.

Images