Service scheduling method and apparatus, and device and medium

Abstract

Provided in the present disclosure are a service scheduling method and apparatus, and a device and a medium. The method comprises: sending a resource request message to a first network-side device, wherein the resource request message is used for requesting resource configuration information for scheduling a passive Internet-of-Things service; receiving a response message sent by the first network-side device on the basis of the resource request message, wherein the response message includes the resource configuration information; and scheduling the passive Internet-of-Things service on the basis of the resource configuration information. In the present technical solution, it is ensured that a terminal device can acquire the resource configuration information for scheduling the passive Internet-of-Things service, thereby meeting the scheduling requirements of the terminal device for passive Internet-of-Things services.

Description

Service scheduling methods, devices, equipment and media

[0001] This disclosure claims priority to Chinese Patent Application No. 2025100715587, filed on January 16, 2025, entitled "Business Scheduling Method, Apparatus, Equipment and Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of communication technology, and in particular to a service scheduling method, apparatus, device and medium. Background Technology

[0003] In passive IoT technology, the resource configuration information used for scheduling passive IoT services between terminal devices and passive IoT devices in a non-directly connected architecture is configured for the terminal by the network-side equipment. The network-side equipment configures the resource configuration information for scheduling passive IoT services for the terminal device through dedicated Radio Resource Control (RRC) signaling. Furthermore, this resource configuration information serves a certain cell validity period; when the terminal device undergoes cell handover, the previously configured resource configuration information may become invalid. In this case, if the terminal has a need to schedule passive IoT services, the terminal device will be unable to continue scheduling passive IoT services. Summary of the Invention

[0004] To solve the above-mentioned technical problems, or at least partially solve them, this disclosure provides a service scheduling method, apparatus, equipment, and medium.

[0005] This disclosure provides a service scheduling method applied to a terminal device, comprising: sending a resource request message to a first network-side device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services; receiving a response message sent by the first network-side device according to the resource request message, wherein the response message includes resource configuration information; and scheduling passive IoT services according to the resource configuration information.

[0006] This disclosure provides a service scheduling method applied to a first network-side device, comprising: acquiring a resource request message sent by a terminal device, the resource request message being used to request resource configuration information for scheduling passive IoT services; determining the resource configuration information based on the resource request message; and sending a response message to the terminal device, the response message carrying the resource configuration information.

[0007] This disclosure provides a service scheduling method applied to a second network-side device, comprising: acquiring a first message sent by a first network-side device, the first message being used to request the acquisition of context information of the terminal device; generating a second message based on the first message and sending the second message to the first network-side device, wherein the second message includes a response message carrying resource configuration information.

[0008] This disclosure also provides a terminal device, including: a memory, a transceiver, and a processor: the memory for storing a computer program; the transceiver for sending and receiving data under the control of the processor; and the processor for reading the computer program in the memory and performing the following operations: sending a resource request message to a first network-side device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services; receiving a response message sent by the first network-side device according to the resource request message, wherein the response message includes resource configuration information; and scheduling passive IoT services according to the resource configuration information.

[0009] This disclosure also provides a first network-side device, which includes a memory, a transceiver, and a processor: the memory stores a computer program; the transceiver transmits and receives data under the control of the processor; and the processor reads the computer program from the memory and performs the following operations: acquiring a resource request message sent by a terminal device, the resource request message being used to request resource configuration information for scheduling passive IoT services; determining the resource configuration information based on the resource request message; and sending a response message to the terminal device, the response message carrying the resource configuration information.

[0010] This disclosure also provides a second network-side device, which includes a memory, a transceiver, and a processor: the memory stores a computer program; the transceiver sends and receives data under the control of the processor; and the processor reads the computer program from the memory and performs the following operations: obtaining a first message sent by a first network-side device, the first message requesting context information of the terminal device; generating a second message based on the first message and sending the second message to the first network-side device, wherein the second message includes a response message carrying resource configuration information.

[0011] This disclosure also provides a service scheduling apparatus, which is applied to a terminal device and includes: a first sending module, configured to send a resource request message to a first network-side device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services; a receiving module, configured to receive a response message sent by the first network-side device according to the resource request message, wherein the response message includes resource configuration information; and a scheduling processing module, configured to schedule passive IoT services according to the resource configuration information.

[0012] This disclosure also provides a service scheduling apparatus, which is applied to a first network-side device and includes: an acquisition module, configured to acquire a resource request message sent by a terminal device, the resource request message being used to request resource configuration information for scheduling passive IoT services; a determination module, configured to determine the resource configuration information based on the resource request message; and a second sending module, configured to send a response message to the terminal device, the response message carrying the resource configuration information.

[0013] This disclosure also provides a service scheduling device, which is applied to a second network-side device and includes: a message acquisition module, configured to acquire a first message sent by a first network-side device, the first message being used to request the acquisition of context information of the terminal device; and a message sending module, configured to generate a second message based on the first message and send the second message to the first network-side device, wherein the second message includes a response message, the response message carrying resource configuration information.

[0014] This disclosure also provides a processor-readable storage medium storing a computer program for executing the above-described service scheduling method.

[0015] The technical solution provided in this disclosure has the following advantages compared with the prior art:

[0016] The passive IoT service scheduling scheme provided in this embodiment involves a terminal device sending a resource request message to a first network-side device. This resource request message requests resource configuration information for scheduling the passive IoT service. The terminal device then receives a response message from the first network-side device, which includes the resource configuration information. The passive IoT service is then scheduled based on this resource configuration information. This technical solution ensures that the terminal device can obtain the resource configuration information for scheduling the passive IoT service, thereby satisfying the terminal device's scheduling requirements for the passive IoT service.

[0017] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0018] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0019] Figure 1 is a flowchart illustrating a service scheduling method provided in an embodiment of this disclosure;

[0020] Figure 2 is a flowchart illustrating another service scheduling method provided in an embodiment of this disclosure;

[0021] Figure 3 is a flowchart illustrating another service scheduling method provided in this embodiment of the present disclosure;

[0022] Figure 4 is a schematic diagram of the structure of a terminal device provided in an embodiment of this disclosure;

[0023] Figure 5 is a schematic diagram of the structure of a network-side device provided in an embodiment of this disclosure;

[0024] Figure 6 is a schematic diagram of a service scheduling device provided in an embodiment of this disclosure;

[0025] Figure 7 is a schematic diagram of another service scheduling device provided in an embodiment of this disclosure;

[0026] Figure 8 is a schematic diagram of another service scheduling device provided in the embodiments of this disclosure. Detailed Implementation

[0027] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0028] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0029] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0030] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0031] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0032] The method and apparatus are based on the same concept of the application. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and the repeated parts will not be described again.

[0033] The technical solutions provided in this disclosure can be applied to a variety of systems. For example, applicable systems may include Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, and 6G (sixth generation mobile communication technology) systems. These systems may include terminal equipment and network equipment. The systems may also include a core network component, such as the Evolved Packet Core (EPC) or the 5G Core Network (5GC).

[0034] The terminal devices involved in the embodiments of this disclosure can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in 5G or 6G systems, the terminal device may be called User Equipment (UE). Wireless terminal devices can be USB storage devices, other personal computer memory devices, and dongles. They can also communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices. For example, they can be portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the radio access network. Examples of such devices include Personal Communication Service (PCS) telephones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), personal computers, tablets, and Machine-type Communication (MTC) terminal devices. Wireless terminal devices can also be referred to as systems, subscriber units, subscriber stations, mobile stations, mobile devices, remote stations, access points, remote terminals, access terminals, user terminals, user agents, user devices, and wireless access devices and routers / modems that meet the limitations of this definition, but are not limited to these in the embodiments of this disclosure.

[0035] The network device involved in the embodiments of this disclosure can be a network-side device, which may include multiple cells providing services to terminals. Depending on the specific application, the network-side device may also be called an access point, or a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of this disclosure may be an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G network-side device (gNB) in a next generation system, or a Home evolved Node B (HeNB), relay node, femto, pico, network test equipment, etc., and is not limited in the embodiments of this disclosure. In some network architectures, network devices may include centralized unit (CU) nodes and distributed unit (DU) nodes, which may also be geographically separated.

[0036] Passive IoT technology refers to the use of battery-free devices to achieve IoT functions. Passive IoT devices absorb energy from the surrounding environment, such as electromagnetic waves, light, and heat, and then use reflection to achieve the communication function of sending information to a reader.

[0037] As mentioned above, passive IoT technology supports a non-directly connected architecture. This architecture can be a new topology where network-side devices and passive IoT devices do not communicate directly. Instead, the terminal device acts as an intermediary node, and the network-side devices communicate with the passive IoT devices through the terminal device. In this non-directly connected structure, the network-side device provides the terminal device with resource configuration information for scheduling passive IoT services. Under the coverage of the network-side device, the terminal device acts as a reader, sending instructions to the passive IoT device (e.g., an A-IoT device) to execute passive IoT services. The passive IoT device then returns the service operation result to the terminal device based on the instructions, and the terminal device then sends the returned result back to the network-side device.

[0038] For this non-directly connected architecture, the resource configuration information for terminal devices to schedule passive IoT services is controlled by the network-side equipment. Specifically, the network-side equipment configures the resource configuration information for scheduling passive IoT services for the terminal devices via dedicated Radio Resource Control (RRC) signaling. Furthermore, this resource configuration information is only valid in the serving cell where the terminal device is located when it obtains the resource configuration information; that is, if the terminal switches cells, the previously obtained resource configuration information may become invalid.

[0039] In some communication scenarios, the service requirements of terminal devices cannot be perceived by the network side. For example, when a terminal device is in an inactive RRC state, the network cannot detect it during cell handover; when a terminal device moves within the Radio Access Network Notification Area (RNA), the network does not detect the cell handover occurring within the RNA. Similarly, if a terminal device moves out of the RNA and has passive IoT service requirements, the network cannot detect it; or, if a terminal device in a connected state initiates RRC reconstruction due to link quality issues, the terminal device may choose to re-establish the RRC connection in a new cell, in which case the network cannot detect whether the terminal device has passive IoT service scheduling requirements in the new cell.

[0040] To address the aforementioned technical problems, this disclosure proposes a service scheduling method. The method will be explained below with reference to specific embodiments.

[0041] Figure 1 is a flowchart illustrating a service scheduling method according to an embodiment of this disclosure. This method can be executed by a service scheduling device, which can be implemented using software and / or hardware, and is generally integrated into a terminal device. As shown in Figure 1, the method includes:

[0042] Step 101: Send a resource request message to the first network-side device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services.

[0043] Here, the first network-side device can be understood as the network-side device corresponding to the cell where the terminal device is currently camped (or accessed). The description of the corresponding camped or accessed cell will differ depending on the state of the terminal device.

[0044] In this embodiment, a resource request message is sent to the first network-side device. This resource request message contains a request for resource configuration information for scheduling passive IoT services. Specifically, in this embodiment, the terminal device sends a resource request message to the first network-side device to request resource configuration information for scheduling passive IoT services. This resource configuration information may include frequency domain resources or time domain resources for scheduling passive IoT services, etc.

[0045] In some possible embodiments, sending a resource request message to the first network-side device may include at least one of the following:

[0046] (1) If it is determined that the request is to obtain the initial resource configuration information for scheduling passive IoT services, a resource request message is sent to the first network-side device.

[0047] (2) If it is determined that the resource configuration information used for scheduling passive IoT services has failed, a resource request message is sent to the first network-side device. The resource configuration information for scheduling passive IoT services may be obtained by the terminal device in the RRC connected state through the RRC reconfiguration message or other signaling messages, or obtained through the RRC connection release message during the process of releasing the terminal device to the RRC inactive state.

[0048] In this example, the acquired resource configuration information used for scheduling passive IoT services is determined to be invalid through at least one of the following methods:

[0049] 1) The terminal device performs cell reselection or cell selection.

[0050] In this example, for instance, when the terminal device is in an RRC inactive state, it may perform cell reselection when moving within the RAN or when moving out of the RAN; for instance, when the terminal device is in an RRC active state, it may perform cell selection; for instance, when the terminal device is in an RRC connected state, it may initiate an RRC connection reconstruction process due to reasons such as poor link quality, in which case the terminal device will first perform cell selection. In this embodiment, after the terminal device performs cell reselection or cell selection, the configured resource configuration information is considered invalid.

[0051] 2) Timeout of timers associated with resource configuration information for passive IoT services.

[0052] In this example, the network-side device pre-configures a timer associated with resource configuration information used for scheduling passive IoT services. This timer starts timing after being configured for the terminal device. If the timer expires, the configured resource configuration information is considered invalid.

[0053] Step 102: Receive a response message sent by the first network-side device based on the resource request message, wherein the response message includes resource configuration information.

[0054] In one embodiment of this disclosure, a response message sent by a first network-side device based on a resource request message is received, wherein the response message includes resource configuration information. Thus, the terminal device proactively requests resource configuration information from the first network-side device, and based on the resource configuration information returned by the first network-side device, the terminal device's need to schedule passive IoT services can be met.

[0055] It should be noted that the message types of resource request messages and corresponding response messages differ in different application scenarios, as shown in the following examples:

[0056] In some possible embodiments, the network-side device sends an RRC connection release message (RRC Release message) to the terminal device. The RRC connection release message carries RNA (RNA can be shared across network-side devices). After receiving the RRC connection release message, the terminal device switches to the RRC inactive state (RRC inactive state). At this time, if the terminal moves within the RNA, the terminal device will not notify the network-side device. Alternatively, the terminal device may update the RNA. For example, the terminal device may perform periodic RNA updates, such as by using a timer configuration information configured by the network-side device to indicate periodic RNA updates. If the timer expires, the terminal device will perform an RNA update. Alternatively, the terminal device may perform event-triggered RNA updates, such as when the terminal moves out of the RNA area. When performing an RNA update, the terminal device initiates an RRC connection recovery process. Since cell reselection may occur when the terminal device performs an RNA update, the terminal device sends an RRC connection recovery request message (RRC Resume Request message) to the first network-side device. The RRC connection recovery request message is also used to request resource configuration information for scheduling passive IoT services. The first network-side device responds with an RRC connection release message, which contains resource configuration information. After receiving the RRC connection release message, the terminal device switches to the RRC inactive state and schedules passive IoT services in the new cell based on the resource configuration information.

[0057] In this embodiment, the resource request message includes an RRC connection recovery request message, and the response message includes an RRC connection release message.

[0058] In some possible embodiments, when the terminal device is in RRC connected state, it may initiate an RRC connection reconstruction process due to reasons such as low link quality. The terminal device sends an RRC connection reconstruction request message to the first network-side device. Since RRC reconstruction involves the selection of a new cell, the RRC connection reconstruction request message is also used to request resource configuration information for scheduling passive IoT services. The first network-side device, upon receiving the RRC connection reconstruction request message and learning that the terminal device is reconstructing the RRC connection, sends an RRC reconstruction message to the terminal device. This RRC reconstruction message instructs the terminal device to establish an RRC connection in the selected new cell. The first network-side device also sends an RRC reconfiguration message to the terminal device. Since the terminal device switches to the new cell, the RRC reconfiguration message also includes resource configuration information for scheduling passive IoT services in order for the terminal device to perform passive IoT service scheduling in the new cell. Therefore, in this example, the resource request message may include the RRC connection reconstruction request message, and the response message includes the RRC reconfiguration message. The terminal device receives the RRC reconstruction message sent by the first network-side device before receiving the RRC reconfiguration message.

[0059] In actual execution, when the resource request message includes the RRC connection recovery request message, before sending the resource request message to the first network side device where the serving cell is located, i.e. before restoring the RRC connection, it is also necessary to perform Unified Access Control (UAC). UAC includes two concepts: access identifier and access category. The access identifier represents the user's identity characteristics and can be written in the SIM card. The access category represents the service attribute of the terminal device initiating access.

[0060] In this embodiment, the RRC connection is also restored based on the UAC mechanism. In this embodiment, when the resource request message includes the RRC connection restoration request message, before sending the resource request message to the first network-side device, access control is performed based on the access category and the access identifier of the terminal device, and it is determined that the terminal device is allowed to send the RRC connection restoration request message. The access category includes a predefined passive IoT service access category, that is, a predefined access category specifically for passive IoT service access, or the access category includes the access category selected from the predefined access categories, that is, an access category can be selected from the predefined existing access categories as the access category for passive IoT service access.

[0061] In another embodiment of this disclosure, if the terminal device does not allow the sending of the RRC connection recovery request message, the terminal device will not send the RRC connection recovery request message and may perform UAC verification again until the terminal device allows the sending of the RRC connection recovery request message, at which point the RRC connection recovery request message will be sent.

[0062] Step 103: Schedule passive IoT services based on resource configuration information.

[0063] In this embodiment, after the terminal device requests resource configuration information from the first network-side device, it can schedule passive IoT services according to the resource configuration information.

[0064] In some possible embodiments, an activation command sent by the first network-side device is also acquired. This activation command can be any signaling, such as, but not limited to, any one of MAC Control Element (MAC CE) signaling or Downlink Control Information (DCI) signaling. After acquiring the activation command and activating the resource configuration information according to the activation command, the terminal device can then schedule passive IoT services based on the resource configuration information.

[0065] Therefore, in the embodiments of this disclosure, the terminal device can obtain resource configuration information for scheduling passive IoT services, ensuring the terminal device's scheduling needs for passive IoT services. For example, when a terminal device in RRC connection state initiates RRC reconstruction due to link quality issues, the terminal device may choose to re-establish the RRC connection in a new cell. However, the first network-side device currently in the cell may not be aware of whether the terminal device has scheduling needs for passive IoT services in the new cell. Through this embodiment, the terminal device can obtain resource configuration information for scheduling passive IoT services, ensuring the terminal device's scheduling needs for passive IoT services.

[0066] For example, when a terminal device in the RRC inactive state moves within the RNA, the network will not provide the terminal device with the latest resource configuration information for scheduling passive IoT device links because it is unaware that the terminal device has entered a new cell. Alternatively, when a terminal device in the RRC inactive state performs a periodic RNA update or moves out of the RNA, the first network-side device currently in the network may not be able to confirm whether the terminal device has a scheduling requirement for passive IoT services, and therefore will not provide the latest resource configuration information for scheduling passive IoT device links. Through this embodiment, the terminal device can obtain the resource configuration information for scheduling passive IoT services even in scenarios where the relevant network-side devices do not actively send resource configuration information, thus ensuring the terminal device's scheduling requirements for passive IoT services.

[0067] In summary, the service scheduling method of this embodiment sends a resource request message to a first network-side device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services, and receives a response message from the first network-side device based on the resource request message, wherein the response message includes resource configuration information, and then schedules the passive IoT services according to the resource configuration information. In this technical solution, it is ensured that the terminal device can obtain the resource configuration information for scheduling passive IoT services, thereby satisfying the terminal device's scheduling requirements for passive IoT services.

[0068] In actual implementation, when the terminal device is in the inactive state of Radio Resource Control (RRC), the terminal device may have a need for RNA updates. For example, the terminal device may perform periodic RNA updates, i.e., based on the timer configuration information of the network-side device that indicates periodic RNA updates, and perform RNA updates if the timer expires. Alternatively, the terminal device may also perform event-triggered RNA updates, such as triggering RNA updates when the terminal moves out of the RNA area. Therefore, in one embodiment of this disclosure, the resource request message is also used to request the radio access network to notify the area RNA update.

[0069] In this embodiment, the first network-side device generates RNA configuration information in response to a resource request message. The RNA configuration information includes at least one of the following: an updated list of RNA cells, an updated list of tracking areas (TAs), and timer configuration information indicating periodic updates of the RNA (e.g., indicating that the RNA is updated every 48 hours).

[0070] In one embodiment of this disclosure, when the instruction message does not request an RNA update, the first network-side device may also proactively send RNA configuration information to the terminal device as needed by the scenario. That is, the first network-side device may also proactively update the RNA configuration information of the terminal device. The circumstances under which the first network-side device sends RNA configuration information can be set according to the scenario requirements.

[0071] After obtaining the RNA configuration information, the terminal device performs RNA update processing based on the RNA configuration information.

[0072] In summary, the service scheduling method of this disclosure allows the terminal device to request RNA updates via resource request messages to obtain RNA configuration information sent by the first network-side device, and then perform RNA update processing based on the RNA configuration information. This achieves the simultaneous acquisition of resource configuration information and, when needed, the acquisition of updated RNA configuration information, satisfying both the terminal device's scheduling requirements for passive IoT services and its need for RNA updates.

[0073] Figure 2 is a flowchart illustrating another service scheduling method provided in this embodiment of the present disclosure. This method can be executed by a service scheduling device, which can be implemented in software and / or hardware, and is generally integrated into a first network-side device. As shown in Figure 2, the method includes:

[0074] Step 201: Obtain the resource request message sent by the terminal device. The resource request message is used to request resource configuration information for scheduling passive IoT services.

[0075] Step 202: Determine the resource configuration information based on the resource request message.

[0076] In this embodiment, since the terminal device is within the coverage area of ​​the first network-side device, the first network-side device determines the resource configuration information for scheduling passive IoT devices for the terminal device.

[0077] Step 203: Send a response message to the terminal device, the response message carrying resource configuration information.

[0078] In this embodiment, since the terminal device is within the coverage area of ​​the first network-side device, the terminal device of the first network-side device sends a response message, which carries resource configuration information.

[0079] It should be noted that the method of sending response messages to the terminal device differs in different application scenarios, as shown in the following examples:

[0080] In one embodiment of this disclosure, when the last network-side device serving the terminal device was the first network-side device, that is, when the terminal device did not undergo a network-side device switch, the first network-side device generates a response message carrying resource configuration information and sends the response message to the terminal device. In other words, when no network-side device switch occurs, the first network-side device generates and sends the response message.

[0081] In one embodiment of this disclosure, when the last network-side device serving the terminal device was a second network-side device (the cell before the handover) that was different from the first network-side device (i.e., the cell currently accessed or camped), that is, when the terminal device has already undergone a network-side device handover, the first network-side device sends a first message to the second network-side device. The first message is used to request the acquisition of the terminal device's context information. The message type of the first message can be any message type. For example, the first message can be a UE context extraction message, or a newly defined new interface message for requesting the UE context from the second network-side device, etc.

[0082] In this embodiment, the first message may include at least one of the following: an indication message, a terminal device context relocation request, and resource configuration information. The terminal device context relocation request is used to request the context information of the terminal device from the second network-side device. The indication message is used to assist the second network-side device in deciding whether to perform the terminal device context relocation operation. When the first message contains resource configuration information for scheduling passive IoT services, if the second network-side device refuses to perform the terminal device context relocation, the first network-side device cannot take over the terminal device because it cannot obtain the terminal device context information. The second network-side device, which continues to serve the terminal device, generates the above-mentioned response message based on the resource configuration information in the first message.

[0083] In this embodiment, the first network-side device obtains a second message fed back by the second network-side device based on the first message. The message type of the second message can be: a UE context extraction success response message, or a UE context extraction failure message, or the second message can be a newly defined new interface message used to send a feedback message based on the first message to the first network-side device, etc.

[0084] In one embodiment of this disclosure, when the second message contains the context information of the terminal, the first network-side device generates a response message based on the resource request message and sends the response message to the terminal device. The response message carries resource configuration information, that is, the first network-side device can take over the terminal device based on the context information of the terminal device. Thus, the first network-side device generates a response message carrying resource configuration information.

[0085] In one embodiment of this disclosure, if the second message does not contain terminal device context information, the first network-side device cannot take over the terminal device because it has not obtained the terminal device context information. The second network-side device that continues to serve the terminal device generates a response message. That is, the first network-side device extracts the response message carrying resource configuration information generated by the second network-side device in the second message and sends the response message to the terminal device.

[0086] When the second network-side device fails to perform context relocation of the terminal device, it generates a response message. Since the cell where the terminal device is currently located is within the coverage area of ​​the first network-side device, the resource configuration information for scheduling passive IoT services is generated by the first network-side device. When generating the second message, the second network-side device also needs to obtain the resource configuration information for scheduling passive IoT services generated by the first network-side device.

[0087] When the first message contains resource configuration information for scheduling passive IoT services, the second network-side device directly extracts the resource configuration information for scheduling passive IoT services from the first message and generates a response message based on the resource configuration information for scheduling passive IoT services.

[0088] When the first message does not include resource configuration information, the second network-side device also sends a third message to the first network-side device. The third message is used to request the resource configuration information for scheduling passive IoT services. Thus, before obtaining the second message fed back by the second network-side device based on the first message, the first network-side device obtains the third message sent by the second network-side device. In response to the obtained third message, the first network-side device sends the resource configuration information for scheduling passive IoT services to the second network-side device.

[0089] In one embodiment of this disclosure, the response message may further include: RNA configuration information, which includes at least one of the following: an updated RNA cell list, an updated Tracking Area (TA) list, and timer configuration information indicating periodic RNA updates. When the indication message includes a Radio Access Network Notification Area (RAN) RNA update request, the RNA configuration information is generated based on the RNA update request; that is, the terminal device can actively request an RNA update, and the first network-side device responds to the update request by generating the RNA configuration information. When the indication message does not include a RAN RNA update request, the RNA configuration information may be actively generated by the first network-side device according to scenario requirements.

[0090] In summary, the service scheduling method of this embodiment involves a first network-side device acquiring a resource request message sent by a terminal device. The resource request message contains resource configuration information requested by the terminal device for scheduling passive IoT services. The first network-side device determines the resource configuration information based on the resource request message and sends a response message to the terminal device, carrying the resource configuration information. The terminal device then schedules the passive IoT services based on the resource configuration information in the response message. In this technical solution, the first network-side device can provide resource configuration information according to the terminal device's request, ensuring that the terminal device can obtain the resource configuration information for scheduling passive IoT services, thereby satisfying the terminal device's scheduling requirements for passive IoT services.

[0091] Figure 3 is a flowchart illustrating another service scheduling method provided in this disclosure. This method can be executed by a service scheduling device, which can be implemented in software and / or hardware, and is generally integrated into a second network-side device. As shown in Figure 3, the method includes:

[0092] Step 301: Obtain the first message sent by the first network-side device. The first message is used to request the acquisition of the context information of the terminal device.

[0093] In this embodiment, when the first network-side device and the second network-side device are different, that is, when the terminal device undergoes a network-side device switch, the second network-side device also obtains the first message sent by the first network-side device.

[0094] Step 302: Generate a second message based on the first message and send the second message to the first network-side device. The second message includes a response message, which carries resource configuration information.

[0095] In one embodiment of this disclosure, a second network-side device generates a second message based on a first message and sends the second message to a first network-side device. The second network-side device can determine whether to perform terminal device context relocation based on the first message. For example, it can be pre-agreed with the second network-side device (this can be an agreement between any control terminal and the second network-side device, or an agreement between the first network-side device and the first network-side device) that the first message includes a resource request message. When the reason for obtaining resource configuration information included in the resource request message is a pre-defined reason (such as RNA update), the second network-side device performs terminal device context relocation. Alternatively, it can be pre-agreed with the second network-side device that the second network-side device performs terminal device context relocation when the first message includes both a terminal device context relocation request and resource configuration information. Or, it can be pre-agreed that the second network-side device performs terminal device context relocation when the message type of the first message is a newly defined interface message.

[0096] Furthermore, when performing terminal device context relocation, the terminal device context information is obtained and a second message is generated, wherein the second message carries the terminal device context information. Subsequently, the first network-side device can take over the terminal device based on the terminal device context information, and the first network-side device generates a response message carrying resource configuration information.

[0097] When the second network-side device does not perform terminal device context relocation, it generates a response message carrying resource configuration information for scheduling passive IoT services. This resource configuration information is generated by the first network-side device. Therefore, the second network-side device needs to obtain the resource configuration information for scheduling passive IoT services generated by the first network-side device. When the first message includes the resource configuration information for scheduling passive IoT services, the second network-side device directly extracts it from the first message. When the first message does not include the resource configuration information for scheduling passive IoT services, the second network-side device sends a third message to the first network-side device. This third message requests the resource configuration information for scheduling passive IoT services, and the second network-side device obtains the resource configuration information for scheduling passive IoT services sent by the first network-side device in response to the third message.

[0098] After the second network-side device obtains the resource configuration information for scheduling passive IoT services, the second network-side device generates a response message carrying the resource configuration information for scheduling passive IoT services, and generates a second message of the response message. That is, if the second network-side device does not perform terminal device context relocation, the second network-side device continues to serve the terminal device, thereby generating a response message carrying resource configuration information.

[0099] The above-described service scheduling method can be applied to scenarios where any terminal device requests resource configuration information for scheduling passive IoT services. To facilitate understanding of the service scheduling method of this disclosure, several specific scenarios are provided below for illustration:

[0100] Scenario 1: In this scenario, the terminal device is released to the RRC inactive state and the terminal device does not move.

[0101] In this example, the terminal device currently stores resource configuration information for scheduling passive IoT services. This resource configuration information can be obtained by the terminal device in RRC connected state through RRC reconfiguration messages or other signaling messages, or obtained through RRC connection release messages during UE release. If the terminal device currently stores resource configuration information, but determines that the resource configuration information is invalid (e.g., the timer associated with the stored resource configuration information has expired); or if the terminal device currently does not have resource configuration information for scheduling passive IoT services, the terminal device requests to obtain the initial resource configuration information for scheduling passive IoT services.

[0102] The terminal device performs access control based on the access category and the access identifier of the terminal device, determines that the terminal device is allowed to send an RRC connection recovery request message, and sends the RRC connection recovery request message to the first network-side device. The RRC connection recovery request message requests the resource configuration information for scheduling passive IoT services.

[0103] After receiving the RRC connection restoration request message, the first network-side device sends an RRC connection release message to the terminal device. The RRC connection release message indicates that the terminal device remains in the RRC inactive state. The RRC connection release message carries resource configuration information for scheduling passive IoT services. Optionally, the first network-side device can also actively generate RNA configuration information, and the RRC connection release message also carries the RNA configuration information.

[0104] When the terminal device receives the RRC connection release message, it remains in the RRC inactive state. It uses application resource configuration information to schedule passive IoT services. If the RRC connection release message also carries RNA configuration information, the terminal device updates the RNA according to the RNA configuration information.

[0105] In this embodiment, the first network-side device may also send a MAC CE or DCI as an activation command to the terminal device to activate the resource configuration information obtained from the RRC connection release message, and then the terminal device can start applying the activated resource configuration information.

[0106] Scenario 2: In this scenario, the terminal device is released into the RRC inactive state and moves within the RNA.

[0107] In this example, the terminal device currently stores resource configuration information for scheduling passive IoT services. This resource configuration information can be obtained by the terminal device in connected state through RRC reconfiguration messages or other signaling messages, or obtained through RRC connection release messages during UE release. If the terminal device currently stores resource configuration information for scheduling passive IoT services, but the terminal device determines that the resource configuration information is invalid—for example, because the terminal device moves within the RNA and reselects to a new cell, the terminal device needs to update the resource configuration information in the new cell—then the terminal device determines that the resource configuration information is invalid. Alternatively, the terminal device currently does not store resource configuration information for scheduling passive IoT services, and the terminal device requests to obtain the initial resource configuration information for scheduling passive IoT services in the new cell it moves to.

[0108] The terminal device performs access control based on the access category and the terminal device's access identifier, determines that the terminal device is allowed to send an RRC connection recovery request message, and sends the RRC connection recovery request message to the first network-side device. The RRC connection recovery request message is used to request resource configuration information for scheduling passive IoT services.

[0109] After receiving the RRC connection restoration request message, if the serving network side device of the terminal device before cell reselection is a second network side device that is different from the first network side device, the first network side device sends a first message to the second network side device. The first message includes at least one of the following: an indication message, a terminal device context relocation request, and resource configuration information. After receiving the first message, the second network side device sends a second message back to the first network side device.

[0110] In the first case in this example: the second network-side device performs terminal device context relocation.

[0111] After the first network-side device obtains the terminal device context information in the second message, the first network-side device generates an RRC connection release message based on the resource request message. The RRC connection release message indicates that the terminal device remains in the RRC inactive state. The RRC connection release message carries resource configuration information. Optionally, the first network-side device may also actively generate RNA configuration information, and the RRC connection release message also carries the RNA configuration information.

[0112] When the terminal device receives the RRC connection release message, it remains in the RRC inactive state and schedules passive IoT services using the resource configuration information. If the RRC connection release message also carries RNA configuration information, the terminal device updates the RNA according to the RNA configuration information.

[0113] In this embodiment, the first network-side device may also send a MAC CE or DCI as an activation command to the terminal device to activate the resource configuration information obtained from the RRC connection release message, and then the terminal device can start applying the activated resource configuration information.

[0114] In the second scenario of this example: the second network-side device did not perform terminal device context relocation.

[0115] In this embodiment, since the second network-side device does not perform terminal device context relocation, the first network-side device does not obtain the terminal device context information in the second message. The second message carries an RRC connection release message with resource configuration information generated by the second network-side device. Optionally, the second network-side device may also actively generate RNA configuration information, and the RRC connection release message also carries the RNA configuration information.

[0116] When the second network-side device generates an RRC connection release message, if the first message carries resource configuration information, the resource configuration information generated by the first network-side device can be extracted from the first message. If the first message does not carry resource configuration information, the second network-side device sends a third message to the first network-side device. The third message is used to request the resource configuration information for scheduling passive IoT services from the first network-side device. After receiving the third message, the first network-side device sends the resource configuration information for scheduling passive IoT services to the second network-side device. Then, the second network-side device generates a response message carrying the resource configuration information for scheduling passive IoT services and carries the response message in the second message.

[0117] The second message carries an RRC connection release message. The first network-side device extracts the RRC connection release message and sends it to the terminal device.

[0118] When the terminal device receives the RRC connection release message, it remains in the RRC inactive state. The application resource configuration information is used to schedule passive IoT services. If the RRC connection release message also carries RNA configuration information, the terminal device updates the RNA.

[0119] Scenario 3: In this scenario, the terminal device is released into the RRC inactive state, and the terminal device is removed from the RNA.

[0120] In this example, the terminal device currently stores resource configuration information for scheduling passive IoT services. This resource configuration information can be obtained by the terminal device in connected state through RRC reconfiguration messages or other signaling messages, or obtained through RRC connection release messages during UE release. If the terminal device currently stores resource configuration information, but the terminal device determines that the resource configuration information is invalid, for example, due to the terminal device moving out of the RNA and reselecting to a new cell, the terminal device needs to update the resource configuration information for scheduling passive IoT services in the new cell; or, if the terminal device currently does not store resource configuration information for scheduling passive IoT services, the terminal device requests to obtain the initial resource configuration information for scheduling passive IoT services in the new cell it moves to.

[0121] The terminal device performs access control based on the access category and the terminal device's access identifier, determines that the terminal device is allowed to send an RRC connection recovery request message, and sends an RRC connection recovery request message to the first network-side device. The RRC connection recovery request message requests resource configuration information for scheduling passive IoT services and requests RNA updates.

[0122] After receiving the RRC connection restoration request message, if the serving network side device of the terminal device before cell reselection is a second network side device that is different from the first network side device, the first network side device sends a first message to the second network side device. The first message includes at least one of the following: an indication message, a terminal device context relocation request, and resource configuration information.

[0123] After receiving the first message, the second network-side device sends a second message back to the first network-side device.

[0124] In the first case in this example: the second network-side device performs terminal device context relocation.

[0125] The second network-side device can determine whether the terminal device has moved out of the RNA based on the original RNA configuration information stored in the terminal device's context information and the new cell where the terminal device that initiated the connection recovery is located. That is, the second network-side device can determine that the terminal device needs to update its RNA configuration information. The second network-side device generates the updated RNA configuration information and performs terminal device context relocation. When the second network-side device performs terminal device context relocation, the first network-side device obtains the terminal device context information and the updated RNA configuration information carried in the second message. The first network-side device generates an RRC connection release message according to the resource request message. The RRC connection release message indicates that the terminal device remains in the RRC inactive state. The RRC connection release message carries the resource configuration information and the RNA configuration information generated by the second network-side device.

[0126] When the terminal device receives the RRC connection release message, it remains in the RRC inactive state. It uses the application resource configuration information to schedule passive IoT services and updates the RNA according to the RNA configuration information.

[0127] In this embodiment, the first network-side device may also send a MAC CE or DCI as an activation command to the terminal device to activate the resource configuration information obtained from the RRC connection release message, and then the terminal device can start applying the activated resource configuration information.

[0128] In the second scenario of this example: the second network-side device did not perform terminal device context relocation.

[0129] In this embodiment, the second network-side device can determine that the terminal device has moved out of the RNA based on the original RNA configuration information stored in the terminal device context information and the new cell where the terminal device that initiated the connection recovery is located. That is, the second network-side device can determine that the terminal device needs to update the RNA configuration information. The second network-side device generates updated RNA configuration information. However, the second network-side device refuses to perform terminal device context relocation. Then, the second message carries the RRC connection release message generated by the second network-side device, which carries resource configuration information and RNA configuration information.

[0130] When the second network-side device generates an RRC connection release message, it can extract the resource configuration information generated by the first network-side device from the first message. If the first message does not carry resource configuration information for scheduling passive IoT services, the second network-side device sends a third message to the first network-side device. The third message requests the resource configuration information for scheduling passive IoT services from the first network-side device. After receiving the third message, the first network-side device sends the resource configuration information for scheduling passive IoT services to the second network-side device. Then, the second network-side device generates an RRC connection release message carrying both the resource configuration information and RNA configuration information for scheduling passive IoT services. The second message carries the RRC connection release message, which the first network-side device extracts and sends to the terminal device.

[0131] When the terminal device receives the RRC connection release message, it remains in the RRC inactive state. It uses the application resource configuration information to schedule passive IoT services and updates the RNA according to the RNA configuration information.

[0132] Scenario 4: In this scenario, the terminal device is in an RRC connection state, and the terminal device triggers RRC connection reconstruction.

[0133] In this embodiment, the terminal device currently stores resource configuration information for scheduling passive IoT services. This resource configuration information can be obtained by the terminal device in the connected state through RRC reconfiguration messages or other signaling messages. If the terminal device currently stores resource configuration information, but the terminal device determines that the resource configuration information is invalid—for example, if a radio link failure occurs in the serving cell currently accessed by the terminal device, and an RRC reconstruction process is initiated, and the terminal device selects a new cell—then the terminal device determines that the stored resource configuration information is invalid and needs to update the resource configuration information. Alternatively, if the terminal device currently does not store resource configuration information for scheduling passive IoT services, the terminal device requests the initial resource configuration information for scheduling passive IoT services after selecting a new cell.

[0134] The terminal device sends an RRC connection reconstruction request message to the first network-side device corresponding to the selected new cell. The RRC connection reconstruction request message requests the resource configuration information for scheduling passive IoT services. The resource configuration information is used by the terminal device to schedule passive IoT services.

[0135] In the first scenario of this example: when no network-side device handover occurs during cell reselection by the terminal device, the first network-side device receives an RRC connection reconstruction request message from the terminal device, allowing the terminal device to establish an RRC connection in the new cell. The first network-side device sends an RRC reconstruction message to the terminal device, followed by an RRC reconfiguration message carrying resource configuration information for scheduling passive IoT services. Upon receiving the RRC reconfiguration message from the first network-side device, the terminal device applies the resource configuration information for scheduling passive IoT services carried in the RRC reconfiguration message to schedule the passive IoT services. In this embodiment, the first network-side device can also send a MAC CE or DCI as an activation command to the terminal device. The terminal device activates the resource configuration information for scheduling passive IoT services obtained from the RRC reconfiguration message according to the activation command, and only then can the terminal device begin to apply the activated resource configuration information for scheduling passive IoT services.

[0136] In the second scenario of this example: When a network-side device handover occurs while the terminal device selects a new cell, after the first network-side device receives the RRC connection reconstruction request message from the terminal device, the first network-side device sends a first message to the second network-side device that previously or last served the terminal device. Upon receiving the first message, the second network-side device sends a second message back to the first network-side device. When the second network-side device performs terminal device context relocation, the first network-side device can obtain the terminal device's context information based on the second message. Therefore, the first network-side device allows the terminal device to establish an RRC connection in the new cell and sends an RRC reconstruction message to the terminal device. After sending the RRC reconstruction message, an RRC reconfiguration message is sent to the terminal device, carrying resource configuration information for scheduling passive IoT services. After receiving the RRC reconfiguration message from the first network-side device, the terminal device uses the resource configuration information for scheduling passive IoT services carried in the RRC reconfiguration message to schedule passive IoT services. In this embodiment, the first network-side device may also send a MAC CE or DCI as an activation command to the terminal device to activate the resource configuration information obtained from the RRC reconfiguration message, and then the terminal device can start applying the activated resource configuration information.

[0137] In summary, the service scheduling method of this disclosure involves obtaining a first message sent by a first network-side device, the first message being used to request context information of a terminal device; generating a second message based on the first message; and sending the second message to the first network-side device. The second message includes a response message carrying resource configuration information. In this technical solution, when a terminal device switches network-side devices, the first network-side device can obtain a response message carrying resource configuration information for scheduling passive IoT services through interaction with the second network-side device, and then send the response message to the terminal device. This ensures that the terminal device can obtain the resource configuration information for scheduling passive IoT services, thereby meeting the terminal device's scheduling requirements for passive IoT services.

[0138] To implement the above embodiments, this disclosure also proposes a terminal device.

[0139] Figure 4 is a schematic diagram of the structure of a terminal device provided in an embodiment of this disclosure. As shown in Figure 4, the terminal device includes: a memory 410, a transceiver 420, and a processor 430. The memory 410 is used to store computer programs; the transceiver 420 is used to send and receive data under the control of the processor 410; and the processor 430 is used to read the computer program in the memory 410 and perform the following operations:

[0140] Send a resource request message to the first network-side device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services;

[0141] Receive a response message sent by the first network-side device in accordance with the resource request message, wherein the response message includes resource configuration information;

[0142] Passive IoT services are scheduled based on resource allocation information.

[0143] In Figure 4, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors (represented by processors) and memories (represented by memory). The bus architecture can also link various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. A transceiver can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0144] The processor is responsible for managing the bus architecture and general processing, while the memory can store the data used by the processor 600 during operation.

[0145] Optionally, the processor can be a CPU (Central Processing Unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.

[0146] The processor executes any of the methods provided in the embodiments of this disclosure by invoking a program stored in memory, according to the obtained executable instructions. The processor and memory may also be physically separated.

[0147] In one possible implementation of this disclosure, sending a resource request message to the first network-side device includes:

[0148] If it is determined that a request is being made to obtain initial resource configuration information for scheduling passive IoT services, a resource request message is sent to the first network-side device; or

[0149] If it is determined that the acquired resource configuration information used for scheduling passive IoT services has failed, a resource request message is sent to the first network-side device.

[0150] In one possible implementation of this disclosure, the acquired resource configuration information for scheduling passive IoT services is determined to be invalid by at least one of the following methods:

[0151] The terminal device performs cell reselection or cell selection;

[0152] Determine the timer timeout associated with the resource configuration information of the scheduled passive IoT services.

[0153] In one possible implementation of this disclosure, the processor 430 is further configured to:

[0154] Obtain the activation command sent by the first network-side device;

[0155] Activate the resource configuration information according to the activation command.

[0156] In one possible implementation of this disclosure,

[0157] When the terminal device is in an RRC inactive state, the resource request message is also used to request an RNA update.

[0158] In one possible implementation of this disclosure, the resource request message includes a Radio Resource Control (RRC) connection restoration request message, and the response message includes an RRC connection release message; or,

[0159] Resource request messages include RRC connection rebuild request messages, and response messages include RRC reconfiguration messages.

[0160] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0161] To implement the above embodiments, this disclosure also proposes a first network-side device.

[0162] Figure 5 is a schematic diagram of the structure of a first network-side device provided in an embodiment of this disclosure. As shown in Figure 5, the first network-side device includes: a memory 510, a transceiver 520, and a processor 530. The memory 510 is used to store computer programs; the transceiver 520 is used to send and receive data under the control of the processor 510; and the processor 530 is used to read the computer program in the memory 510 and perform the following operations:

[0163] Obtain resource request messages sent by terminal devices. These resource request messages are used to request resource configuration information for scheduling passive IoT services.

[0164] Determine resource configuration information based on the resource request message;

[0165] Send a response message to the terminal device, which carries resource configuration information.

[0166] In Figure 5, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors (represented by processors) and memories (represented by memory). The bus architecture can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface. The transceiver can be multiple components, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor is responsible for managing the bus architecture and general processing, and the memory can store data used by the processor during operation.

[0167] The processor can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0168] In one possible implementation of this disclosure, sending a response message to the terminal device includes:

[0169] Generate a response message carrying the resource configuration information based on the resource configuration information;

[0170] Send a response message to the terminal device.

[0171] In one possible implementation of this disclosure, sending a response message to the terminal device includes: sending a first message to a second network-side device, wherein the first message is used to request the acquisition of context information of the terminal device;

[0172] Receive the second message sent by the second network-side device;

[0173] If the second message contains the terminal's context information, the first network-side device generates a response message based on the resource request message and sends the response message to the terminal device. The response message carries resource configuration information.

[0174] If the second message does not contain terminal device context information, the first network-side device obtains a response message from the second message and sends a response message to the terminal device, the response message carrying resource configuration information.

[0175] In one possible implementation of this disclosure, the response message obtained from the second message carries resource configuration information received from the first network-side device. Before the first network-side device obtains the response message from the second message, the processor 530 is further configured to:

[0176] Obtain a third message sent by the second network-side device, wherein the third message is used to request resource configuration information; send the resource configuration information to the second network-side device.

[0177] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0178] To implement the above embodiments, this disclosure also proposes a second network-side device.

[0179] Figure 5 can also be seen as a structural schematic diagram of a second network-side device provided in an embodiment of this disclosure. As shown in Figure 5, the second network-side device includes: a memory 510, a transceiver 520, and a processor 530. The memory 510 is used to store computer programs; the transceiver 520 is used to send and receive data under the control of the processor 510; and the processor 530 is used to read the computer program in the memory 510 and perform the following operations:

[0180] Obtain the first message sent by the first network-side device. The first message is used to request the context information of the terminal device.

[0181] A second message is generated based on the first message and sent to the first network-side device. The second message includes a response message, which carries resource configuration information.

[0182] In one possible implementation of this disclosure, generating a second message based on a first message includes: determining whether to perform terminal device context relocation based on the first message;

[0183] When performing terminal device context relocation, the terminal device context information is obtained and a second message is generated, wherein the second message carries the terminal device context information;

[0184] When not performing terminal device context relocation, obtain resource configuration information, generate a response message, the response message carries the resource configuration information, and generate a second message carrying the response message.

[0185] In one possible implementation of this disclosure, obtaining resource configuration information includes:

[0186] When the first message includes resource configuration information, extract the resource configuration information from the first message.

[0187] If the first message does not include resource configuration information, a third message is sent to the first network-side device, wherein the third message is used to request resource configuration information.

[0188] Obtain resource configuration information sent by the first network-side device.

[0189] In one possible implementation of this disclosure, the response message further includes RNA configuration information, wherein when the first message includes a radio access network notification area RNA update request, the RNA configuration information is generated based on the RNA update request.

[0190] RNA configuration information includes at least one of the following: an updated list of RNA cells, an updated list of tracking regions (TAs), and timer configuration information indicating periodic RNA updates.

[0191] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0192] To implement the above embodiments, this disclosure also proposes a service scheduling device, which is applied in a terminal device. As shown in FIG6, the service scheduling device includes: a first sending module 610, a receiving module 620, and a scheduling processing module 630, wherein,

[0193] The first sending module 610 is used to send a resource request message to the first network-side device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services;

[0194] The receiving module 620 is used to receive a response message sent by the first network-side device according to the resource request message, wherein the response message includes resource configuration information;

[0195] The scheduling and processing module 630 is used to schedule passive IoT services based on resource configuration information.

[0196] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0197] To implement the above embodiments, this disclosure also proposes a service scheduling device, which is applied to a first network-side device. The first network-side device is the serving network-side device of the current cell when the terminal device sends a resource request message. As shown in FIG7, the service scheduling device includes: an acquisition module 710, a determination module 720, and a second sending module 730, wherein,

[0198] The acquisition module 710 is used to acquire resource request messages sent by terminal devices. The resource request messages are used to request resource configuration information for scheduling passive IoT services.

[0199] The determination module 720 is used to determine resource configuration information based on the resource request message;

[0200] The second sending module 730 is used to send a response message to the terminal device, the response message carrying resource configuration information.

[0201] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0202] To implement the above embodiments, this disclosure also proposes a service scheduling device, which is applied to a second network-side device. The second network-side device is the service network-side device that served the last or most recently served terminal device. As shown in Figure 8, the service scheduling device includes: a message acquisition module 810 and a message sending module 820, wherein...

[0203] The message acquisition module 810 is used to acquire a first message sent by the first network-side device. The first message is used to request the acquisition of the context information of the terminal device.

[0204] The message sending module 820 is used to generate a second message based on the first message and send the second message to the first network-side device. The second message includes a response message, which carries resource configuration information.

[0205] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0206] This disclosure also provides a processor-readable storage medium storing a program for causing the processor to execute the aforementioned service scheduling method.

[0207] Processor-readable storage media can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MOs), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0208] To implement the above embodiments, this disclosure also proposes a computer program product, including a computer program, wherein the computer program executes the above-described service scheduling method when executed by a processor.

[0209] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, apparatus, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0210] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0211] These processor-executable instructions may also be stored in a processor-readable memory that can instruct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0212] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.

[0213] The passive IoT service scheduling method disclosed herein can ensure that terminal devices can obtain resource configuration information for scheduling passive IoT services, thereby meeting the scheduling needs of terminal devices for passive IoT services and having strong industrial applicability.

Claims

1. A service scheduling method, wherein, The method is applied to a terminal device and includes: Send a resource request message to the first network-side device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services; Receive a response message sent by the first network-side device in accordance with the resource request message, wherein the response message includes resource configuration information; The passive IoT services are scheduled based on the resource configuration information.

2. The method as described in claim 1, wherein, Sending the resource request message to the first network-side device includes: If it is determined that a request is made to obtain initial resource configuration information for scheduling passive IoT services, a resource request message is sent to the first network-side device; or If it is determined that the acquired resource configuration information used for scheduling passive IoT services has failed, a resource request message is sent to the first network-side device.

3. The method of claim 2, wherein, Determine that the acquired resource configuration information used for scheduling passive IoT services has become invalid by at least one of the following methods: The terminal device performs cell reselection or cell selection; Determine the timer timeout associated with the resource configuration information of the scheduled passive IoT services.

4. The method as described in any one of claims 1-3, wherein, Also includes: Obtain the activation command sent by the first network-side device; The resource configuration information is activated according to the activation command.

5. The method as described in any one of claims 1-4, wherein, When the terminal device is in an RRC inactive state, the resource request message is also used to request an RNA update.

6. The method as described in any one of claims 1-5, wherein, The resource request message includes a Radio Resource Control (RRC) connection restoration request message, and the response message includes an RRC connection release message; or, The resource request message includes an RRC connection reconstruction request message, and the response message includes an RRC reconfiguration message.

7. A service scheduling method, wherein, The method is applied to a first network-side device, including: Obtain a resource request message sent by a terminal device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services; Based on the resource request message, determine the resource configuration information; A response message is sent to the terminal device, the response message carrying the resource configuration information.

8. The method of claim 7, wherein, Sending a response message to the terminal device includes: Based on the resource configuration information, generate a response message carrying the resource configuration information; The response message is sent to the terminal device.

9. The method of claim 7 or 8, wherein, Sending a response message to the terminal device, including: Send a first message to the second network-side device, the first message being used to request the acquisition of the context information of the terminal device; Receive the second message sent by the second network-side device; If the second message contains the context information of the terminal, the first network-side device generates a response message based on the resource request message and sends the response message to the terminal device, wherein the response message carries resource configuration information. If the second message does not contain the terminal device context information, the first network-side device obtains a response message from the second message and sends the response message to the terminal device, the response message carrying the resource configuration information.

10. The method of claim 9, wherein, The response message obtained from the second message carries resource configuration information received from the first network-side device; Before the first network-side device obtains the response message from the second message, the method further includes: Receive a third message sent by the second network-side device, wherein the third message is used to request the resource configuration information; The resource configuration information is sent to the second network-side device.

11. A terminal device, wherein, include: Memory, transceiver processor: Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Send a resource request message to the first network-side device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services; Receive a response message sent by the first network-side device in accordance with the resource request message, wherein the response message includes resource configuration information; The passive IoT services are scheduled based on the resource configuration information.

12. The terminal device as described in claim 11, wherein, Sending the resource request message to the first network-side device includes: If it is determined that a request is made to obtain initial resource configuration information for scheduling passive IoT services, a resource request message is sent to the first network-side device; or If it is determined that the acquired resource configuration information used for scheduling passive IoT services has failed, a resource request message is sent to the first network-side device.

13. The terminal device as described in claim 12, wherein, Determine that the acquired resource configuration information used for scheduling passive IoT services has become invalid by at least one of the following methods: The terminal device performs cell reselection or cell selection; Determine the timer timeout associated with the resource configuration information of the scheduled passive IoT services.

14. The terminal device as described in any one of claims 11-13, wherein, The processor is also used for: Obtain the activation command sent by the first network-side device; The resource configuration information is activated according to the activation command.

15. A first network-side device, wherein, The first network-side device includes a memory, a transceiver, and a processor. Memory, used to store computer programs; The transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Obtain a resource request message sent by a terminal device, wherein the resource request message is used to request resource configuration information for scheduling passive IoT services; Determine resource configuration information based on the resource request message; A response message is sent to the terminal device, the response message carrying the resource configuration information.

16. A processor-readable storage medium, wherein, The processor-readable storage medium stores a computer program for executing the service scheduling method described in any one of claims 1-10.

Images