Communication method and apparatus

Abstract

Embodiments of the present application relate to the field of communications, and provide a communication method and apparatus, capable of implementing quality of service (QoS) parameter-based scheduling of low-complexity terminal devices. The method comprises: receiving a QoS parameter of a first service from a core network element; paging at least one terminal apparatus for executing the first service; and when at least one terminal apparatus for executing the first service is paged, on the basis of the QoS parameter, scheduling the at least one terminal apparatus to execute the first service.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on September 28, 2023, with application number 202311295149.2 and application name “Communication Method and Device,” the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of communications, and in particular to communication methods and devices. Background Art

[0003] With the evolution and development of the fifth generation (5G) Internet of Things (IoT), the demand for lower power consumption terminal devices is increasing. Radio frequency identification (RFID) technology provides technical support for low power consumption and supports microwatt-level power consumption. Lower power consumption terminal devices are usually also low-complexity terminal devices, such as tags (also known as RFID terminals). Tags use low-precision, low-power medium- and low-frequency ring oscillators or oscillators with no local oscillation to receive downlink signals. When the tag is working, the energy and carrier for communication come from the reader, and communication is based on the reflected carrier. Specifically, the reader charges the tag by sending an excitation signal to the tag. The tag receives the signaling sent by the reader and sends the signaling to the reader through the reflected signal. In this way, the reader can identify the tag's identity (ID) and perform operations such as reading and writing on the tag.

[0004] Currently, per-terminal device Quality of Service (QoS) parameters are assigned during session establishment after the device accesses the network. This process of establishing sessions and configuring QoS parameters for each device is complex and unsuitable for low-complexity devices, making it impossible to schedule these devices based on QoS parameters.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a communication method and apparatus that can achieve QoS-guaranteed service transmission for low-complexity terminal devices.

[0007] To achieve the above objectives, this application adopts the following technical solutions:

[0008] In a first aspect, a communication method is provided. The method can be performed by an access network device, or by a component of the access network device, such as a processor, chip, or chip system of the access network device. It can also be implemented by a logic module or software that implements all or part of the functions of the access network device. The method includes: receiving quality of service (QoS) parameters for a first service from a core network element; paging at least one terminal device executing the first service; and, upon paging the at least one terminal device executing the first service, scheduling the at least one terminal device to execute the first service based on the QoS parameters.

[0009] Based on this communication method, the access network device obtains QoS parameters (service-level OoS parameters) for each service from the core network network element, such as the QoS parameters of the first service, and can schedule at least one paged terminal device to perform the first service based on the QoS parameters of the first service. There is no need to configure QoS parameters for each terminal device, which simplifies the processing flow of QoS parameters between the terminal device and the network, reduces signaling overhead, and thus enables flexible QoS-based scheduling of terminal devices (such as low-complexity terminal devices). In an embodiment of the present application, the core network network element can be an access and mobility management network element, such as the access and mobility management network element is the access and mobility management function (AMF) in 5G.

[0010] In one possible design, paging at least one terminal device executing a first service may include: receiving first indication information from a core network element. The first indication information is used to indicate that the first service needs to be executed. Paging at least one terminal device executing the first service based on the first indication information. Based on this design, the access network device may trigger paging of the terminal device based on the first indication information sent by the core network element, so as to schedule at least one paged terminal device to execute the first service based on the QoS parameters of the first service.

[0011] In one possible design scheme, the first indication information and QoS parameters can be carried in the same message to reduce signaling overhead.

[0012] In one possible design, the QoS parameters may include at least one of the following: a data transmission delay requirement for executing the first service, a priority of the first service, and a reliability requirement for transmitting the first service. The data transmission delay requirement for executing the first service is a data transmission delay requirement for one or more terminal devices. For example, the data transmission delay may include a delay requirement for obtaining data of the first service collected by one or more terminal devices. The priority of the first service may refer to an execution priority of the first service, which can ensure the order in which the first service is executed when multiple services exist. The reliability requirement for transmitting the first service is used to ensure the reliability of data transmission of the first service.

[0013] In one possible design, the method provided in an embodiment of the present application may further include: sending second indication information to a core network element. The second indication information is used to indicate that the first service is being executed by the terminal device. Based on this design, the access network device may also notify the core network element of the execution status of the first service via the second indication information, so that the core network element can trigger subsequent services.

[0014] In a possible design scheme, the method provided in the embodiment of the present application may further include: sending a third indication message to the core network network element. The third indication message is used to indicate the cessation of scheduling the first service or the cessation of data transmission of the first service. Based on this design scheme, the access network device may also actively send a third indication message to the core network network element to inform the cessation of scheduling the first service or the cessation of data transmission of the first service, so as to achieve flexible start and end of service transmission processes. For example, the access network device may send the third indication message when resources are limited, or may send the third indication message when QoS requirements are not met, so as to achieve service transmission control of the first service.

[0015] In one possible design scheme, the third indication information may include the reason for stopping scheduling the first service, or the reason for stopping data transmission of the first service, so as to avoid the core network element performing erroneous operations due to unknown reasons.

[0016] In one possible design, the method provided in an embodiment of the present application may further include receiving fourth indication information from a core network element. The fourth indication information is used to instruct the access network device to stop data transmission of the first service. Thus, the access network device can stop data transmission of the service based on the fourth indication information issued by the core network element, thereby enabling flexible initiation and termination of service transmission processes.

[0017] In a second aspect, a communication method is provided. This method can be performed by a first terminal device, or by a component of the first terminal device, such as a processor, chip, or system-on-chip of the first terminal device. It can also be implemented by a logic module or software that implements all or part of the functions of the first terminal device. The method includes receiving identification information from an access network device. The identification information is used to identify quality of service (QoS) parameters. When a first service is required, the identification information is sent to the access network device.

[0018] Based on this communication method, after the access network device obtains the QoS parameters from the core network, it can assign identification information for identifying the QoS parameters to the first terminal device, so that when the first terminal device needs to execute the first service, the access network device can determine the corresponding QoS parameters through the identification information reported by the first terminal device, which simplifies the QoS acquisition process. The first terminal device does not need to perform a complete QoS negotiation and determination process with the access network and the core network every time it initiates a service. The corresponding QoS parameters can be simply determined through the identification information, thereby realizing flexible scheduling of the first terminal device (such as a low-complexity terminal device) to execute the first service.

[0019] In one possible design, receiving identification information from the access network device may include: receiving a registration acceptance message from the access network device during the process of initiating registration by the first terminal device. The registration acceptance message includes the identification information. Typically, the service process is performed after the registration process. Assigning identification information to the first terminal device during the registration process allows the first terminal device to directly use the identification information in subsequent service processes to trigger scheduling of the first service by the access network device, eliminating the need for further information acquisition. This simplifies the process and reduces service latency.

[0020] In one possible design scheme, receiving identification information from the access network device may include: receiving a first message from the access network device during the transmission process between the first terminal device and the access network device. The first message includes identification information. In an embodiment of the present application, the first message may be an RRC message. Thus, the access network device may also allocate identification information to the first terminal device during the data transmission process with the first terminal device. In the scenario where the first terminal device accesses the network again, the identification information may be directly used to trigger the access network device to schedule the first service without the need to obtain it again, thereby simplifying the process and reducing the service waiting delay.

[0021] In one possible design, sending the identification information to the access network device may include sending the identification information to the access network device during a process in which the first terminal device initiates random access again. Based on this design, the access network device may receive the identification information from the first terminal device during the next random access process and trigger service scheduling for the first terminal device based on the identification information.

[0022] In one possible design, sending the identification information to the access network device may include sending a radio resource control (RRC) message to the access network device. The RRC message includes the identification information. Based on this design, the access network device may also obtain the identification information from the first terminal device from the RRC message and trigger service scheduling for the first terminal device based on the identification information.

[0023] In one possible design scheme, the QoS parameters may include at least one of the following: a priority of the first service, a data transmission delay requirement for executing the first service, and a reliability requirement for transmitting the first service.

[0024] In a possible design solution, the identification information may be an identification of the first terminal device or a QoS identification or a context identification of the first terminal device.

[0025] In a third aspect, a communication method is provided. This method can be performed by an access network device, or by a component of the access network device, such as a processor, chip, or chip system of the access network device. It can also be implemented by a logic module or software that implements all or part of the functions of the access network device. The method includes: receiving quality of service (QoS) parameters from a core network element; and sending identification information to a first terminal device, where the identification information is used to identify the QoS parameters.

[0026] In a possible design solution, the method provided in the embodiment of the present application may further include: receiving identification information from the first terminal device, and scheduling the first terminal device to execute the first service according to the identification information.

[0027] In one possible design, receiving identification information from the first terminal device may include: receiving identification information from the first terminal device during a process in which the first terminal device re-initiates random access.

[0028] In one possible design scheme, receiving identification information from the first terminal device may include: receiving a radio resource control RRC message from the first terminal device, the RRC message including the identification information.

[0029] In one possible design, sending the identification information to the first terminal device may include: sending a registration acceptance message to the first terminal device during the process of the first terminal device initiating registration, wherein the registration acceptance message includes the identification information.

[0030] In one possible design, sending the identification information to the first terminal device may include: sending a first message to the first terminal device during a transmission process between the first terminal device and the access network device, wherein the first message includes the identification information.

[0031] In one possible design, the method provided in the embodiment of the present application may further include: if the first terminal device is released to an inactive state or undergoes reselection or cell switching to another access network device, retaining the context of the first terminal device, wherein the context of the first terminal device includes QoS parameters.

[0032] In one possible design scheme, the QoS parameters may include at least one of the following: a priority of the first service, a data transmission delay requirement for executing the first service, and a reliability requirement for transmitting the first service.

[0033] In a possible design solution, the identification information may be an identification of the first terminal device or a QoS identification or a context identification of the first terminal device.

[0034] Among them, the technical effects of the method described in the third aspect can be found in the relevant description of the technical effects of the method described in the second aspect, and will not be repeated here.

[0035] In a fourth aspect, a communication device is provided. The communication device includes: a module, unit, or means for executing the method described in any one of the first to third aspects, and the module, unit, or means can be implemented by hardware, software, or by executing the corresponding software implementation through hardware. The hardware or software includes one or more modules or units corresponding to the above functions, such as a transceiver module and a processing module. For example, the transceiver module is used to indicate the transceiver function of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver function.

[0036] In one possible design solution, the transceiver module may include a receiving module and a sending module, wherein the sending module is used to implement the sending function of the communication device described in the fourth aspect, and the receiving module is used to implement the receiving function of the communication device described in the fourth aspect.

[0037] In one possible design, the communication device described in the fourth aspect may further include a storage module that stores a program or instruction. When the processing module executes the program or instruction, the communication device described in the third aspect can execute the method described in any one of the first to third aspects.

[0038] Among them, the communication device described in the fourth aspect can be a terminal device or an access network device, or it can be a chip (system) or other parts or components that can be set in the terminal device or access network device, or it can be a device that includes a terminal device or access network device. This application does not limit this.

[0039] In a fifth aspect, a communication device is provided, comprising: a processor; the processor is configured to execute the method described in any one of the first to third aspects above.

[0040] In some possible designs, the communication device also includes: a memory; the memory is used to store computer programs or instructions; accordingly, the processor is used to execute the computer programs or instructions stored in the memory, so that the communication device executes the method described in any one of the first to third aspects above.

[0041] In one possible design, the processor can be integrated with the memory.

[0042] In some possible designs, the communication device further includes: a communication interface; the communication interface is used to communicate with modules outside the communication device.

[0043] Among them, the communication device described in the fourth aspect can be a terminal device or an access network device, or it can be a chip (system) or other parts or components that can be set in the terminal device or access network device, or it can be a device that includes a terminal device or access network device. This application does not limit this.

[0044] In some possible designs, when the communication device is a chip system, it can be composed of a chip, or it can include a chip and other discrete devices.

[0045] In a sixth aspect, a communication device is provided, comprising: a transceiver and a processor, wherein the transceiver is used to exchange information between the communication device and other communication devices, and the processor executes program instructions to perform the method described in any one of the first to third aspects above.

[0046] In one possible design, the communication device described in aspect 6 may further include a memory. The memory may be integrated with the processor or provided separately. The memory may be used to store the computer program and / or data involved in the method described in any one of aspects 1 to 3 above.

[0047] It can be understood that when the communication device provided in any one of the fourth to sixth aspects is a chip, the above-mentioned sending action / function can be understood as output, and the above-mentioned receiving action / function can be understood as input.

[0048] In the seventh aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer-readable storage medium is run on a communication device, the communication device can execute the method described in any one of the first to third aspects above.

[0049] In an eighth aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, enables the communication device to execute the method described in any one of the first to third aspects above.

[0050] In a ninth aspect, a communication system is provided, comprising an access network device for executing the method described in the first aspect.

[0051] In a tenth aspect, a communication system is provided, comprising a first terminal device for executing the method described in the second aspect and an access network device for executing the method described in the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] FIG1 is a schematic diagram of the architecture of an RFID system;

[0053] Figure 2 is a flow chart of interaction between a tag and a reader;

[0054] FIG3 is a schematic diagram of a 5G QoS establishment process;

[0055] FIG4 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0056] FIG5 is a schematic diagram of a scenario applied to a communication system according to an embodiment of the present application;

[0057] FIG6 is a schematic diagram of another scenario applied to a communication system according to an embodiment of the present application;

[0058] FIG7 is a schematic diagram of another scenario applied to a communication system provided by an embodiment of the present application;

[0059] FIG8 is a schematic diagram of another scenario applied to a communication system provided by an embodiment of the present application;

[0060] FIG9 is a flow chart of a communication method provided in an embodiment of the present application;

[0061] FIG10 is a flow chart of another communication method provided in an embodiment of the present application;

[0062] FIG11 is a flow chart of another communication method provided in an embodiment of the present application;

[0063] FIG12 is a flow chart of another communication method provided in an embodiment of the present application;

[0064] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0065] FIG14 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0066] The technical solution in this application will be described below with reference to the accompanying drawings.

[0067] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as universal mobile telecommunications system (UMTS), code division multiple access (CDMA) system, wireless local area network (WLAN), wireless fidelity (Wi-Fi) system, wired network, vehicle to everything (V2X) communication system, device-to-device (D2D) communication system, Internet of Vehicles communication system, 4th generation (4G) mobile communication system, such as long term evolution (LTE) system, world-wide interoperability for microwave access (WiMAX) communication system, 5G mobile communication system, such as new radio (NR) system, and future communication systems, such as sixth generation (6G) mobile communication system.

[0068] This application will present various aspects, embodiments, or features in the context of systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these aspects may also be used.

[0069] Before describing the embodiments of the present application, the related technologies involved in the embodiments of the present application are described.

[0070] 1. RFID

[0071] RFID technology is a contactless automatic identification technology. As shown in Figure 1, the RFID system includes a tag and a reader. The reader may have an integrated antenna for transceiver processing, or the reader and antenna may be separate. Specifically, the reader charges a low-cost tag by sending an excitation signal to the tag. The tag receives the signal from the reader and sends a signal back to the reader via a reflected signal. This allows the reader to identify the tag's ID, read and write to the tag, and perform other operations on the tag, which are not specifically defined here.

[0072] A reader / writer can also be referred to as a reader, exciter, excitation source, RF source, or interrogator, without limitation. The excitation signal can also be referred to as a carrier signal, RF signal, or wireless signal, without limitation. A tag uses a low-precision, low-power, medium- to low-frequency ring oscillator or a completely local oscillator-free device to receive downlink signals. Tags can also be referred to as low-power terminal devices, tag devices, or passive devices.

[0073] Given the low-power advantages of RFID communication technology, the 5G passive ambient internet of things (A-IoT) has emerged. To meet ultra-low power requirements, A-IoT tags also use low-precision, low-power, medium- and low-frequency ring oscillators, or even no local oscillator at all, to receive downlink signals. This reception method can further reduce the power consumption of the tag's downlink reception. However, for such low-power reception methods, only amplitude detection, such as envelope detection, can be performed, as low-precision ring oscillators alone cannot guarantee accurate demodulation of signal phase information.

[0074] Tags have low cost and design complexity, but poor coverage and limited adaptability. 5G A-IoT research requires enhanced coverage design. Currently, the 3rd Generation Partnership Project (3GPP) standard states that 5G A-IoT can include the following three types of devices:

[0075] Device A: No energy storage, cannot generate signals independently, and uses reflection transmission;

[0076] Device B: has energy storage, cannot generate signals independently, and uses reflection transmission;

[0077] Device C: has energy storage, can generate signals independently, and has active video components for transmission.

[0078] 2. Inventory

[0079] The tag receives the mask information and flag bit specified by the reader. If the tag's storage area information matches the received mask information, and the tag's saved flag bit is consistent with the received flag bit, it can enter the inventory process, that is, initiate random access to the reader and complete the corresponding instructions indicated by the reader.

[0080] 3. Interaction process between tag and reader

[0081] Please refer to Figure 2, which is a flow chart of the interaction between a tag and a reader. As shown in Figure 2, tag access includes the following steps:

[0082] S201: The reader sends a select command to the tag. Correspondingly, the tag receives the select command from the reader.

[0083] The selection command is used to select one or a group of tags for access. The selection command may include a selected (SL) identifier (or an inventoried identifier) ​​and a mask.

[0084] The tag receives a select command from the reader and determines whether the information stored in the corresponding location in its own memory area matches the mask information in the select command. If so, the tag considers itself to meet the read / write selection criteria. At this point, the tag can set the state of a certain inventory flag, for example, setting the first inventory flag from state A to state B. Conversely, tags that do not match the reader's selection criteria will set the first inventory flag from state B to A. A / B here can also be replaced by 0 / 1, without limitation.

[0085] S202: The reader sends a query command to the tag. Correspondingly, the tag receives the query command from the reader.

[0086] The query command is used to initialize an inventory cycle. The query command carries flag information (such as a selection flag or an inventory flag) and a parameter Q used by the tag to calculate the total number of time slots allocated by the reader for random access.

[0087] The tag that meets the selection criteria of the reader determines whether its own flag information is consistent with the flag information in the reader query command. If they are consistent, the tag calculates the access time slot range according to the Q value as [0, 2 Q -1]. The label can be in [0, 2 Q-1] and save it as the counter. Whenever the tag receives a query reply (QueryRep) command, counter = counter - 1. When counter is equal to 0, the tag can send a random number, such as a 16-bit random number or pseudo-random number (RN16).

[0088] In one possible scenario, the time slot corresponding to the reader sending the Query is 0, and a tag with an initial counter value of 0 is generated. The tag can initiate access after receiving the Query.

[0089] S203: The tag sends RN16 to the reader. Correspondingly, the reader receives RN16 from the tag.

[0090] RN16 indicates the tag's temporary ID. When the tag receives a query command and confirms that counter = 0, it selects a 16-bit random number as RN16 and sends this RN16 back to the reader. If the reader detects that the tag has sent back RN16, it indicates that the inventory process is proceeding normally and proceeds to the next step. Specifically, RN16 is sent in message (Msg) 3, also known as message three or the third message.

[0091] S204: The reader sends an acknowledgment message (ACK) to the tag. Correspondingly, the tag receives the acknowledgment message from the reader.

[0092] ACK is used to indicate that the reader has successfully received the RN16 sent by the tag. The ACK includes the 16-bit random number previously sent by the tag, which is used by the tag to verify whether the ACK matches.

[0093] S205: The tag sends uplink data to the reader / writer. Correspondingly, the reader / writer receives the uplink data from the tag.

[0094] The tag confirms that the 16-bit random number included in the ACK is the same as the RN16 sent by the tag, indicating that the tag random access is successful. The tag then sends uplink data to the reader, such as the electronic product code (EPC). The EPC is used to indicate the real ID of the tag.

[0095] Optionally, after the tag completes random access, the following interaction process may occur between the tag and the reader:

[0096] S206: The reader sends a first instruction to the tag. Correspondingly, the tag receives the first instruction from the reader.

[0097] The first instruction is used to instruct the tag to perform a read operation, a write operation, or a read-write operation. After receiving the first instruction, the tag responds to the first instruction and performs the read operation, the write operation, or the read-write operation.

[0098] S207: The tag sends a first response to the reader. Correspondingly, the reader receives the first response from the tag.

[0099] The first response is a response message to the first instruction, which is used to indicate that the tag completes an operation, a write operation, or a read-write operation, etc.

[0100] After the reader finishes processing a tag, it can also send a query reply (QueryRep) command to the tag. After receiving the QueryRep command, the tag in communication with the reader flips the inventory flag, such as setting it from B to A. This QueryRep signaling can also be used to trigger the next access opportunity. That is, if the counter of a tag is not 0, it will decrement it by 1. When the counter = 0, the tag can initiate the next random access.

[0101] 5G QoS

[0102] As shown in Figure 3, the QoS for each user equipment (UE) is the QoS parameter assigned during the session establishment process after each UE accesses the network. Specifically, the UE sends a session establishment request to the session management function (SMF) through the AMF. After receiving the session establishment request, the SMF exchanges UE registration information with the user plane function (UPF), policy control function (PCF), and unified data management (UDM) to obtain the UE's QoS information.

[0103] After completing the session establishment process, the UE and UPF have a QoS flow template corresponding to the service. A QoS flow template contains multiple packet filters and priorities. The SMF can construct a QoS flow template through a service data flow (SDF) template. The SDF template is defined in the policy and charging control (PCC) framework and contains one or more SDF filters that can filter service data flows.

[0104] When a downlink data packet arrives, the UPF uses a filter to map it to a QoS flow, then performs QoS control corresponding to that QoS flow and marks the data packet with a QoS flow ID (QFI) in the header of the upper-layer encapsulation protocol. The packet is then sent to the access network (radio access network, RAN) via the N3 Tunnel corresponding to that QoS flow. After receiving the data packet, the RAN finds the corresponding DRB and QoS parameters based on the QFI, performs QoS control, and then sends the data packet to the UE via the data radio bearer (DRB).

[0105] When the UE sends uplink data, it is mapped to a QoS flow through a filter and then sent to the corresponding DRB. After receiving the data, the RAN performs QoS control based on the QFI, finds the corresponding N3 Tunnel, and sends the data packet to the UPF.

[0106] Each protocol data unit (PDU) session has a default QoS rule without a QoS flow template. The QoS flow established with this QoS rule is similar to the default bearer in the evolved packet system (EPS) network. Any data that cannot be matched to other QoS flows is mapped to this QoS flow for transmission.

[0107] QoS flow is the smallest carrier of 5G QoS. QoS flow is the smallest granularity of 5G services. After the management of the PDU session on the control plane is completed, the user plane channel is established. The QoS flow carries data packets on the user plane channel to transmit data.

[0108] 5G QoS Framework Overview:

[0109] 1) Based on QoS flows: This is the finest granularity of QoS differentiation, where QoS parameters and features are bound to a QoS flow. QoS parameters include latency, priority, and special data representation. These parameters collectively determine the ultimate priority of a QoS flow. Features are similar to data packet headers. If all of these parameters were included in a single packet, the data would be overly lengthy. Therefore, we have chosen to define a paradigm that predefines parameters at various levels, allowing us to express various features using simple data. In other words, a feature is a collection of individual parameters.

[0110] 2) Each QoS flow is identified by a QFI, which is unique in a PDU session (the same QFI is allowed to appear in two PDU sessions).

[0111] 3) The next generation radio access network (NG-RAN) can establish a single data radio bearer based on the NG-RAN logic, or it can combine multiple QoS flows into the same data radio bearer. There is no strict one-to-one relationship between data radio bearers and QoS flows.

[0112] Once a QoS flow is determined, the UE, NG-RAN, and UPF are all aware of the corresponding QoS flow information. Therefore, the QFI becomes even more important as an identifier. The QFI is carried in the General Packet Radio Service (GPRS) Tunneling Protocol (GTP) user plane (user, U) encapsulation header and sent over the N3 (and N9) interface (i.e., from the AN to the UPF). This means that the encapsulation header remains unchanged during the end-to-end transmission.

[0113] Packets marked with the same QFI receive the same flow forwarding processing (such as scheduling, admission threshold), guaranteed bit rate (GBR) QoS flow: the flow bit rate needs to be guaranteed; non-guaranteed bit rate (NGBR) QoS flow: the flow bit rate does not need to be guaranteed, etc.

[0114] Based on the process shown in Figure 3, QoS parameters are configured for each UE after the session is established. This per-UE session establishment and QoS parameter configuration process is relatively complex and unsuitable for ultra-low-complexity terminal devices (such as tags), making it impossible to implement QoS-based scheduling for low-complexity terminal devices.

[0115] To this end, an embodiment of the present application provides a communication method that can implement QoS-based scheduling for low-complexity terminal devices.

[0116] In order to better understand the embodiments of the present application, the following explanations are made before introducing the embodiments of the present application.

[0117] First, in the embodiments of the present application, "used to indicate" can include being used for direct indication and being used for indirect indication. When describing a certain "indication information" as being used to indicate A, it can include the indication information directly indicating A or indirectly indicating A, and does not necessarily mean that the indication information carries A.

[0118] The information indicated by the indication information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, it is also possible to use the arrangement order of each piece of information agreed in advance (such as specified in the protocol) to achieve the indication of specific information, thereby reducing the indication overhead to a certain extent. At the same time, it is also possible to identify the common parts of each piece of information and indicate them uniformly to reduce the indication overhead caused by indicating the same information separately.

[0119] In addition, the specific indication method can also be various existing indication methods, such as but not limited to the above-mentioned indication methods and various combinations thereof. The specific details of the various indication methods can be referred to the prior art and will not be repeated herein. As can be seen from the above, for example, when it is necessary to indicate multiple information of the same type, there may be a situation where the indication methods for different information are different. In the specific implementation process, the required indication method can be selected according to specific needs. The embodiment of the present application does not limit the selected indication method. In this way, the indication method involved in the embodiment of the present application should be understood to cover various methods that can enable the party to be indicated to obtain the information to be indicated.

[0120] The information to be indicated can be sent as a whole, or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The specific sending method is not limited in this application. Among them, the sending period and / or sending time of these sub-information can be predefined, for example, predefined according to the protocol, or configured by the transmitting device by sending configuration information to the terminal device. Among them, the configuration information can, for example, but not limited to, include one or a combination of at least two of RRC signaling, media access control (MAC) layer signaling and physical layer signaling. Among them, MAC layer signaling, for example, includes MAC-control element (CE); physical (PHY) layer signaling, for example, includes downlink control information (DCI).

[0121] Second, in the embodiments of the present application, the first, second, and various numerical numbers are merely distinctions made for ease of description and are not intended to limit the scope of the embodiments of the present application. For example, different indication information is used to distinguish one from another. For another example, the first indication information and the second indication information are merely used to distinguish different areas and do not limit their order of precedence. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and order of execution, and words such as "first" and "second" do not necessarily limit them to be different.

[0122] Third, in the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all mean that the device (such as a terminal device or an access network device) will make corresponding processing under certain objective circumstances. It does not limit the time, and does not require the device (such as a terminal device or an access network device) to have a judgment action when implementing it, nor does it mean that there are other limitations.

[0123] At the same time, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0124] In addition, in the embodiments of the present application, the expression " / " is used to indicate that the objects associated with each other are in an "or" relationship; for example, A / B can represent: A or B. The expression "and / or" is used to indicate that the objects associated with each other can be in an and relationship or an or relationship; for example, A and / or B can represent the following situations: A exists alone, B exists alone, and A and B exist at the same time, where A and B can be single or multiple. "At least one of the following" or similar expressions is used to indicate any combination of the listed items; for example, at least one of A, B and / or C can represent the following situations: A exists alone, B exists alone, C exists alone, A and B exist at the same time, B and C exist at the same time, A and C exist at the same time, and A, B and C exist at the same time, where A, B, and C can be single or multiple.

[0125] Finally, the network architecture and business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0126] The following first introduces the system architecture involved in the embodiments of the present application:

[0127] The embodiments of the present application will present various aspects, embodiments, or features around a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these solutions may also be used.

[0128] For example, Figure 4 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. As shown in Figure 4, the communication system includes a network device (access network device 401a), multiple first-type terminals (first-type terminal 402a and first-type terminal 402b), and a second-type terminal (second-type terminal 403a).

[0129] It is understood that the communication system shown in FIG4 may further include other network devices, such as access network device 401b and / or access network device 401c; the communication system shown in FIG4 may further include other second-category terminals, such as second-category terminal 403b. In addition, the communication system shown in FIG4 may further include other first-category terminals.

[0130] In the communication system provided in FIG4 , a communication connection can be established between the access network device and the first type terminal. For example, a communication connection can be established between the access network device 401a and the first type terminal 402a, or between the access network device 401a and the first type terminal 402b, or between the access network device 401c and the first type terminal 402b.

[0131] A communication connection may also be established between the access network device and the second type of terminal. For example, the access network device 401a may establish a communication connection with the second type of terminal 403a.

[0132] A communication connection may also be established between the first type terminal and the second type terminal. For example, a communication connection may be established between the first type terminal 402a and the second type terminal 403b, or between the first type terminal 402b and the second type terminal 403b.

[0133] Communication connections may also be established between different access network devices. For example, a communication connection may be established between access network device 401b and access network device 401c.

[0134] A communication connection may also be established between different second-category terminals. For example, a communication connection may be established between the second-category terminal 403a and the second-category terminal 403b.

[0135] The first type of terminal is an extremely low-power and / or extremely low-complexity device or a device in an extremely low-power and / or extremely low-complexity device. The first type of terminal can be referred to as a terminal device in the Internet of Things, and can also be referred to as an A-IoT device, an A-IoT terminal, a passive A-IoT, a terminal device, a terminal device, a passive tag, a tag, a tag device, a passive device, a passive device, a semi-active device, a battery-free terminal / device, a battery-free terminal / device, a retroreflective terminal / device, a backscatter terminal, a passive IoT, a reflector, a reflection terminal, or an ambient signal device. In the following method embodiments, the first type of terminal is described as a terminal device.

[0136] The second type of terminal may be a terminal with transceiver functions, or may be a chip or chip system provided in the terminal. The second type of terminal may also be referred to as UE, access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication equipment, user agent or user device. The terminal in the embodiments of the present application can be a mobile phone, a cellular phone, a smart phone, a tablet computer, a wireless data card, a personal digital assistant (PDA), a wireless modem, a handheld device (handset), a laptop computer, a machine type communication (MTC) terminal, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a smart home device (for example, a refrigerator, a television, an air conditioner, an electric meter, etc.), an intelligent robot, a robotic arm, a workshop equipment, a wireless terminal in unmanned driving, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a vehicle-mounted terminal, a roadside unit with terminal function, or a wireless terminal in a vehicle-mounted terminal. The terminal device of the present application may also be an onboard module, onboard module, onboard component, onboard chip or onboard unit built into a vehicle as one or more components or units. The terminal device may also be other devices with terminal functions, for example, the terminal device may also be a device that functions as a terminal in D2D communication.

[0137] The embodiments of the present application do not limit the device forms of the second type of terminal and the first type of terminal. The device for realizing the function of the first type of terminal may be a terminal device; or it may be a device that can support the terminal device to realize the function, such as a chip system. The device may be installed in the terminal device or used in combination with the terminal device. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. The device for realizing the function of the second type of terminal may be a terminal device; or it may be a device that can support the terminal device to realize the function, such as a chip system. The device may be installed in the terminal device or used in combination with the terminal device. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

[0138] The access network device may also be referred to as a RAN node, network device, RAN entity, or access node, etc. It is located on the network side of the above-mentioned communication system to help terminal devices achieve wireless access, and is a device with wireless transceiver functions or a chip or chip system that can be set in the device. The access network device includes but is not limited to: a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a Wi-Fi system. The access network device may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, an open radio access network (ORAN), or a wireless controller in a centralized radio access network (CRAN) scenario. Optionally, the RAN node may also be a server, a wearable device, a vehicle, or an on-board device, etc. For example, the access network device in V2X technology may be a road side unit (RSU). All or part of the functions of the access network device in this application may also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform). The access network device in this application may also be a logical node, logical module, or software that can implement all or part of the functions of the access network device.

[0139] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0140] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0141] The embodiments of this application do not limit the form of the access network device. The device used to implement the functions of the access network device can be the access network device; it can also be a device that supports the access network device to implement the functions, such as a chip system. The device can be installed in the access network device or used in conjunction with the access network device.

[0142] In an embodiment of the present application, the communication system may further include a core network element. The core network element is a device deployed in the core network to provide services for terminal devices. The core network element may also be referred to as a core network device. In systems using different wireless access technologies, the names of core network elements with similar wireless communication functions may be different. In an embodiment of the present application, the core network element may be an access and mobility management element. For example, when the method of an embodiment of the present application is applied to a 5G system, the access and mobility management element may be an AMF. When the method of an embodiment of the present application is applied to an LTE system, the access and mobility management element may be a mobility management entity (MME). For the convenience of description only, in an embodiment of the present application, the above-mentioned devices that can provide services for terminal devices are collectively referred to as core network elements.

[0143] In addition, the communication system shown in Figure 4 may also include other core network elements, such as a session management network element, a network exposure network element, a policy control network element, etc. When the method of the embodiment of the present application is applied to the 5G system, the session management network element can be a session management function (SMF), the network exposure network element can be a network exposure function (NEF), and the policy control network element can be a policy control function (PCF), without limitation.

[0144] It is understood that in Figure 4, the roles of the access network device and the second type of terminal may be relative, and the second type of terminal may be configured as the access network device. For example, the second type of terminal in Figure 4 may be configured as a mobile base station.

[0145] In the communication system shown in FIG4 , the access network device can be used to implement the read / write functions of the reader / writer, and the second-type terminal can be used to assist the access network device in implementing the read / write functions of the reader / writer. It is understood that in the communication system provided in FIG4 , any access network device can be used to assist other access network devices in the communication system in implementing the read / write functions of the reader / writer. For example, an integrated access and backhaul (IAB) device can be used to assist a base station in implementing the functions of the reader / writer. Alternatively, any second-type terminal in the communication system provided in FIG4 can be used to assist other second-type terminals in implementing the read / write functions of the reader / writer.

[0146] In the following examples, the access network device 401a, the first type of terminal 402a and the second type of terminal 403a are used for explanation.

[0147] In one possible design, the second type of terminal is used to assist the access network device in sending downlink data, that is, the second type of terminal assisted downlink. When the second type of terminal is a UE, it can also be called UE assisted downlink.

[0148] In this case, as shown in Figure 5, access network device 401a can provide a carrier for first-category terminal 402a. Access network device 401a can also receive uplink data from first-category terminal 402a, and can also send downlink data to second-category terminal 403b, which in turn sends the downlink data to first-category terminal 402a.

[0149] Alternatively, as shown in Figure 6, the second-type terminal 403b can provide a carrier for the first-type terminal 402a. The access network device 401a can receive uplink data from the first-type terminal 402a and send downlink data to the second-type terminal 403b. The second-type terminal 403b then sends the downlink data to the first-type terminal 402a.

[0150] In one possible design, the second-type terminal 403b is used to assist the access network device 401a in receiving uplink data, that is, the second-type terminal assisted uplink. When the second-type terminal is a UE, it can also be called UE assisted uplink.

[0151] In this case, as shown in Figure 7, the access network device 401a can provide a carrier for the first type of terminal 402a, the access network device 401a sends downlink data to the first type of terminal 402a, the first type of terminal 402a sends uplink data to the second type of terminal 403b, and the second type of terminal 403b then sends the uplink data to the access network device 401a.

[0152] Alternatively, as shown in Figure 8, the second type terminal 403b can provide a carrier for the first type terminal 402a, the access network device 401a sends downlink data to the first type terminal 402a, the first type terminal 402a sends uplink data to the second type terminal 403b, and the second type terminal 403b then sends the uplink data to the access network device 401a.

[0153] Among them, the access network device 401a and the first type terminal 402a can communicate through the Uu interface, the access network device 401a and the second type terminal 403b can communicate through the Uu interface, and the second type terminal 403b and the first type terminal 402a can communicate through a sidelink.

[0154] The communication method provided in the embodiment of the present application will be described in detail below with reference to Figures 9 to 12.

[0155] For example, Figure 9 is a flow chart of a communication method provided in an embodiment of the present application. The subject that executes the access network device action in the method may also be a device / module in the access network device, such as a chip, processor, processing unit, etc. in the access network device; the subject that executes the core network element action in the method may also be a device / module in the core network element, such as a chip, processor, processing unit, etc. in the core network element, and the embodiment of the present application does not specifically limit this. In addition, the steps executed by a single execution subject in the method may also be divided into steps executed by multiple execution subjects, and these execution subjects may be logically and / or physically separated.

[0156] As shown in FIG9 , the communication method includes the following steps:

[0157] S901: A core network element sends QoS parameters of a first service to an access network device. Correspondingly, the access network device receives the QoS parameters of the first service from the core network element.

[0158] In the embodiment of the present application, the QoS parameters are configured based on the granularity of the service, and one QoS parameter corresponds to one service. The QoS parameters of the first service are used by the access network device to schedule the terminal device that executes the first service. The QoS parameters of the first service can support at least one terminal device to execute the first service. Among them, the terminal device is the first type of terminal shown in Figure 4 above, such as a label. The first service is a service that the terminal device can support. The first service can be a certain type of service or a certain service. For example, the first service can be an inventory service, a perception service, a reading service, a writing service, an inactivation service, etc. The service involved in the embodiment of the present application can also be called an A-IoT service. It should be understood that the QoS parameter can be used to express the service quality requirements for at least one terminal device to complete a certain service, or to ensure the service quality of the first service.

[0159] The QoS parameters of the first service include the data transmission delay requirement for executing or completing the first service. The data transmission delay requirement may refer to (or be reflected in, or be expressed in) the delay requirement for one or more terminal devices executing the first service to complete the collection and reporting of service data, or may refer to the delay requirement for the access network device to receive all service data reported by one or more terminal devices executing the first service, or may refer to the delay requirement for the access network device to transmit all service data reported by one or more terminal devices executing the first service to the core network network element or server, and there is no limitation on this. The starting timing time for executing the first service may be from the first service trigger signaling (such as the first indication information described below) sent by the core network or application layer, or from the access network device to the first service trigger signaling received. The end time is as shown in the example above, and there is no limitation on this. For example, the transmitted service data may be identification information of the terminal device.

[0160] If the data transmission delay requirement refers to the delay requirement for the access network device to transmit all service data reported by one or more terminal devices performing the first service to the core network, then the data transmission delay requirement includes the service data transmission delay requirement between the access network device and the one or more terminal devices performing the first service, as well as the service data transmission delay requirement between the access network device and the core network. It should be understood that the core network element to which the data is ultimately reported can be the core network element that sends the QoS parameters for the first service, or it can be another network element in another core network, without limitation.

[0161] In addition to latency requirements, the QoS parameters of the first service may also include: priority of the first service, and / or reliability requirements for transmitting the first service, etc. The priority of the first service may refer to the execution priority of the first service, which is used to indicate the order in which the first service is executed when there are multiple services. The reliability requirements for transmitting the first service may refer to reliability requirements for transmitting service data of the first service, such as requirements for the bit error rate, jitter, packet loss rate, etc.

[0162] In an embodiment of the present application, the core network element may be an access and mobility management element, which may be an AMF in 5G. In one possible design, the access and mobility management element may send QoS parameters for the first service to the access network device based on a trigger from a network openness element or a session management element. The network openness element may be an NEF in 5G, and the session management element may be an SMF in 5G.

[0163] Exemplarily, the network open network element or the session management network element sends a second message to the access and mobility management network element. Accordingly, the access and mobility management network element may receive the second message from the network open network element or the session management network element. The second message is used to request the execution of the first service, and the second message may include at least one of a service identifier of the first service, a service mode of the first service, and a service type of the first service. The service identifier is used to identify the service and may also be referred to as a transaction ID. The service mode may include an inventory mode, a read mode, or a write mode. Optionally, the second message may further include geographical area information, information for selecting a terminal device for executing the first service (such as a mask or filtering information), etc. The geographical area information is used to indicate the area range in which the first service can be executed or the area range in which the first service is required to be executed, and may be used to select a terminal device within a specified area to execute the first service.

[0164] Furthermore, the access and mobility management network element sends a third message to the policy control network element based on the second message, and accordingly, the policy control network element receives the third message from the access and mobility management network element. The third message is used to request QoS policy information of the first service, and the third message includes the service identifier of the first service. Thus, the policy control network element sends QoS policy information to the access and mobility management network element based on the third message, and accordingly, the access and mobility management network element receives QoS policy information from the policy control network element. The QoS policy information includes the QoS parameters of the first service and the service processing rules of the access network device, etc. The service processing rules may refer to how the access network device completes the scheduling of the first service based on the QoS parameters of the first service. Thus, the access and mobility management network element can send the QoS parameters of the first service to the access network device. In an embodiment of the present application, the policy control network element may be a PCF in 5G.

[0165] It should be understood that the "first message", "second message", "third message", etc. in the embodiments of the present application can be message names defined by existing protocols, or other message names. For example, the third message can be a QoS request message, which is not limited to this.

[0166] S902: The access network device pages at least one terminal device executing a first service.

[0167] After the access network device obtains the QoS parameters of the first service, it can page at least one terminal device to perform the first service. Exemplarily, the access network device can send a paging message, which is used to page at least one terminal device to access the network to perform the first service. The paging process in the embodiment of the present application can be considered as a message that triggers random access of the terminal device, and the terminal device that randomly accesses supports the first service. The specific implementation process of paging the terminal device can refer to the relevant description of the random access process shown in Figure 2 above, which will not be repeated here. In the embodiment of the present application, the access network device can specify relevant transmission or scheduling strategies based on the QoS parameters, and the access network device can also consider the QoS parameters when paging at least one terminal device to perform the first service, such as determining the configuration of the terminal device under the paging based on the QoS parameters.

[0168] In one possible design, an access network device may receive first indication information from a core network element and, based on the first indication information, page at least one terminal device that is to execute a first service. The first indication information may indicate that the first service needs to be executed or may indicate that at least one terminal device may be selected to execute the first service. In other words, the access network device may page a terminal device to execute the first service based on a trigger from the core network element.

[0169] In one possible implementation, the access network device may receive fifth indication information from the core network network element, and the fifth indication information may be used to indicate the type of the first service or the transmission type of the first service. The transmission type may indicate the data transmission situation, such as whether there are multiple data transmissions or only a single data transmission. Specifically, in the case where the terminal device has multiple data transmissions, such as the terminal device has N (N is a positive integer) pairs of uplink and downlink transmissions, in the case of a single data transmission, such as uploading only one uplink data, the access network device may send a release to it (optionally, a confirmation receipt indication may also be sent to the terminal before the release), when receiving a certain service type, the access network device needs to wait for receiving a release indication from the core network before releasing the terminal device, or release it only after there is no data transmission for a period of time, etc.

[0170] In a possible implementation, the first indication information and the QoS parameters may be carried in the same message. In other words, the first indication information and the QoS parameters may be sent together to reduce signaling overhead.

[0171] In a possible implementation, at least two of the first indication information, the QoS parameter, and the fifth indication information may be carried in the same message.

[0172] In the embodiment of the present application, the first service may be triggered by the application server or the application layer through the core network in addition to being triggered by the core network.

[0173] S903: When at least one terminal device executing the first service is paged, the access network device schedules the at least one terminal device to execute the first service according to the QoS parameters.

[0174] In the embodiment of the present application, scheduling at least one terminal device to execute the first service may also be replaced by formulating a transmission strategy, determining a scheduling strategy, etc.

[0175] After the access network device determines at least one terminal device supporting the first service, it may determine a scheduling strategy based on the QoS parameters of the first service. The scheduling strategy may include selecting which terminal devices to execute the first service, what resources to allocate to the selected terminal devices, how much bandwidth to allocate, what coding method to use, the modulation order, and the number of transmission repetitions, etc., without limitation. Selecting which terminal devices to execute the first service may include selecting the number and location of the terminal devices executing the first service. It should be understood that the location of the terminal device may refer to a relative location, such as location information relative to the access network device, or may refer to a specific geographic location.

[0176] Exemplarily, the QoS parameters for a first service include a data transmission delay requirement for executing the first service. The first service is an inventory service, and the delay requirement is 100 milliseconds (ms). The access network device is required to collect the application layer identifiers of all terminal devices executing the inventory service within 100 ms and send the collected application layer identifiers to the core network or server. Thus, the access network device can determine which of the paged terminal devices can support the inventory service within the data transmission delay based on the data transmission delay requirement and factors such as the total number of paged terminal devices and the distance between each terminal device and the access network. The device can then allocate data transmission resources to the selected terminal devices, thereby instructing the selected terminal devices to report their application layer identifiers.

[0177] When there are multiple services that need to be executed, the access network equipment can determine whether the priority of the first service is higher than any service other than the first service among the multiple services based on the priority of the first service. If so, the terminal device is scheduled to execute the first service first. If not, the terminal device is scheduled to execute the first service in order of the priorities of the multiple services.

[0178] It should be understood that when the first service includes multiple QoS parameters, the access network device can schedule the terminal device to perform the first service in combination with multiple QoS parameters, or it can consider part of the QoS parameters to schedule the terminal device to perform the first service, and there is no limitation on this.

[0179] After the access network device schedules the terminal device to execute the first service based on the QoS parameters of the first service, or after the access network device obtains the service data reported by the terminal device, in one possible design scheme, the access network device can send second indication information to the core network element, and the core network element accordingly receives the second indication information from the access network device. The second indication information is used to indicate that the first service is being executed by the terminal device. In other words, after completing the scheduling of the first service, the access network device can inform the core network element of the execution status of the first service, such as whether execution has started, the number of terminal devices executing the first service, and the service data reporting status.

[0180] It should be understood that in some cases, the second indication information may also indicate that the first service has not been executed or cannot be executed, such as because the first service has a low priority and is not yet executed, or because the first service cannot be executed due to resource constraints. Optionally, the second indication information may also indicate the reason why the first service has not been executed or cannot be executed.

[0181] In one possible scenario, the access network device may also send a third indication message to the core network network element, and correspondingly, the core network network element receives the third indication message from the access network device. The third indication message is used to indicate to stop scheduling the first service or stop transmitting data of the first service or stop executing the transmission of the first service. Stopping scheduling the first service may mean that the access network device stops allocating scheduling resources for the terminal device to execute the first service, and stopping transmitting data of the first service or stopping transmitting the first service may mean that the access network device stops receiving service data sent by the terminal device or stops sending service data of the first service to the terminal device, or stops any uplink / downlink signal or data used to support the transmission of the first service. It may also mean that the access network device stops receiving service data sent by the terminal device and stops transmitting service data of the first service to the core network. There is no limitation on this.

[0182] In one possible implementation, the third indication information may include a reason for stopping scheduling of the first service, or a reason for stopping data transmission of the first service. For example, the current data transmission does not meet QoS requirements (such as latency requirements and reliability requirements), resources are limited, overloaded (load is too large), or the collection and transmission of service data of all scheduled terminal devices has been completed.

[0183] In another possible scenario, the core network network element may send a fourth indication message to the access network device, and correspondingly, the access network device receives the fourth indication message from the core network network element. The fourth indication message is used to instruct the access network device to stop the data transmission of the first service, and the fourth indication message may include the service identifier of the first service. Optionally, the fourth indication message may also include the reason for stopping the data transmission of the first service. Optionally, the fourth indication message may also indicate the time to stop the transmission, that is, how long it will take to stop the data transmission of the first service. Exemplarily, after receiving the fourth indication message, the access network device may stop transmitting the service data of the first service to the core network, or may instruct the terminal device to stop the data transmission of the first service, such as sending an indication message to the terminal device to stop transmission or release the connection state, or may stop sending any signal or carrier to the terminal device.

[0184] Optionally, after receiving the fourth indication information, the access network device may also send already received data to the core network. That is, after receiving the fourth indication information, if the access network device still has collected data that has not been fully sent, it will continue to send the collected data to the core network until all the collected data has been sent. Exemplarily, when the core network element sends the fourth indication information, it may indicate whether to send the collected data that has not yet been transmitted to the core network to the core network.

[0185] In one possible implementation, if the QoS parameter is a latency requirement (such as the time to complete an instruction or service), and the access network device has not received a response signaling or a completion indication from the first terminal device or the core network within the indicated time, the access network device may also re-trigger the first service, that is, resend the service triggering signaling to instruct the first terminal device to perform the collection and transmission operations of the service again.

[0186] It should be understood that the access network device or core network element does not rely on QoS parameters to send the above-mentioned stop or start indication, and it can dynamically indicate according to actual conditions (such as resource conditions, overload conditions).

[0187] Based on the communication method shown in Figure 9, the access network device obtains QoS parameters (service-level OoS parameters) for each service from the core network network element, such as the QoS parameters of the first service, and can schedule at least one paged terminal device to perform the first service based on the QoS parameters of the first service. There is no need to configure QoS parameters for each terminal device, which simplifies the processing flow of QoS parameters between the terminal device and the network, reduces signaling overhead, and thus enables flexible QoS-based scheduling of terminal devices (such as low-complexity terminal devices).

[0188] It should be noted that in the embodiments of the present application, QoS parameters may also be referred to as QoS rules, QoS requirements, QoS services or QoS information, etc., without limitation to this.

[0189] The communication method shown in Figure 9 is described in detail below in conjunction with 5GS. For example, the core network element is AMF, the access network device is gNB, and the terminal device is a tag.

[0190] For example, FIG10 is a flow chart of a communication method provided in an embodiment of the present application. As shown in FIG10 , the communication method includes the following steps:

[0191] S1001. The NEF sends a first signaling to the AMF. Correspondingly, the AMF receives the first signaling from the NEF.

[0192] Among them, the specific description of the first signaling can refer to the relevant description of the second message in the above S901, which will not be repeated here.

[0193] It should be understood that the NEF can send the first signaling to the AMF through the SMF.

[0194] S1002: The AMF sends a QoS request to the PCF. Correspondingly, the PCF receives the QoS request from the AMF.

[0195] The specific description of the QoS request can be found in the relevant description of the third message in S901 above, which will not be repeated here.

[0196] It should be understood that AMF can send QoS requests to PCF through SMF.

[0197] S1003. The PCF sends QoS policy information to the AMF. Correspondingly, the AMF receives the QoS policy information from the PCF.

[0198] The specific description of the QoS policy information can be found in the related description of the QoS policy information in S901 above, which will not be repeated here.

[0199] It should be understood that PCF can send QoS policy information to AMF through SMF.

[0200] S1004. The AMF sends a second signaling to the gNB. Correspondingly, the gNB receives the second signaling from the AMF.

[0201] Among them, the second signaling may include the QoS parameters of the first service and the first indication information. The QoS parameters of the first service can refer to the relevant description in the above S901, and the first indication information can refer to the relevant description in the above S902, which will not be repeated here.

[0202] S1005. The gNB executes the first service according to the QoS parameter scheduling tag 1 of the first service.

[0203] S1006. The gNB executes the first service according to the QoS parameter scheduling tag 2 of the first service.

[0204] The scheduling process of S1005 and S1006 can refer to the relevant description in the above S903 and will not be repeated here.

[0205] Figures 9 and 10 above illustrate how, before a terminal device accesses the network, the network triggers service execution (downlink triggering), and the access network device schedules the terminal device based on the acquired service-level QoS parameters. The present application also provides a communication method that, based on a trigger from a terminal device, allows the access network device to schedule the terminal device based on the acquired service-level QoS parameters.

[0206] For example, Figure 11 is a flow chart of a communication method provided in an embodiment of the present application. Among them, the subject that executes the access network device action in the method can also be a device / module in the access network device, such as a chip, processor, processing unit, etc. in the access network device; the subject that executes the first terminal device action in the method can also be a device / module in the first terminal device, such as a chip, processor, processing unit, etc. in the first terminal device, and the embodiment of the present application does not make specific limitations on this. In addition, the steps executed by a single execution subject in the method can also be divided into steps executed by multiple execution subjects, and these execution subjects can be logically and / or physically separated.

[0207] As shown in FIG11 , the communication method includes the following steps:

[0208] S1101: A core network element sends QoS parameters to an access network device. Correspondingly, the access network device receives the QoS parameters from the core network element.

[0209] For QoS parameters, it can be a service-level QoS parameter for each terminal device (such as the first terminal device), which supports a terminal device to perform the service (such as the first service). At this time, the QoS parameter can be called the QoS parameter of the first terminal device that supports the first service. Among them, the QoS parameter may include at least one of the following: the priority of the first service, the data transmission delay requirement for performing the first service, and the reliability requirement for transmitting the first service. It should be understood that the QoS parameter is configured for each terminal device, and the data transmission delay requirement for performing the first service and the reliability requirement for transmitting the first service are also for a terminal device. Please refer to the relevant description in S901 above, and no further details will be given. In the embodiment of the present application, the terminal device is the first type of terminal shown in Figure 4 above. The specific priority can be that the same type of service has different priorities, or different service types have different priorities. For example, the priority of inventory service 1 is higher than that of inventory service 2, and inventory service 1 is higher than that of reading service 1. In other words, the QoS parameter can be bound to the service type, or there can be multiple QoS parameter configurations under the same service type.

[0210] In one possible scenario, the QoS parameter may be a QoS parameter for each service, which may support at least one terminal device to perform the service (e.g., a first service), and the at least one terminal device includes the first terminal device. In this case, the QoS parameter may be referred to as a QoS parameter for the first service, and it may be understood that the QoS parameter includes QoS parameters corresponding to at least one terminal device supporting the first service. In this case, the specific description of the QoS parameter can be found in the relevant description in S901 above and will not be repeated here.

[0211] In the embodiment of the present application, the core network element may be an access and mobility management element or a session management element. The access and mobility management element may be an AMF in 5G, and the session management element may be an SMF in 5G.

[0212] In one possible design scheme, the access and mobility management network element or the session management network element may determine the QoS parameters (for transmission by the first terminal device) to be sent to the access network device based on the QoS parameters supported by the first terminal device. The QoS parameters supported by the first terminal device may be those reported to the access and mobility management network element or the session management network element by the first terminal device during the process of initiating registration after completing the first random access. For example, the QoS parameters supported by the first terminal device are carried in the registration request. It should be understood that the registration request also includes the identifier of the first terminal device and related registration information. Alternatively, the access and mobility management network element or the session management network element may request QoS parameters from the policy control network element based on the QoS parameters supported by the first terminal device. In one possible scenario, when the core network network element is a session management network element, the QoS parameters supported by the first terminal device may be forwarded to the session management network element through the access and mobility management network element.

[0213] In one possible design scheme, the access and mobility management network element or the session management network element can obtain QoS parameters from the policy control network element, and the policy control network element can be the PCF in 5G. Exemplarily, the session management network element makes a QoS request to the policy control network element, and accordingly, the policy control network element receives the QoS request from the session management network element. The QoS request may include the service identifier of the first service and / or the identifier of the first terminal device. Further, the policy control network element sends the QoS parameters to the session management network element, and accordingly, the session management network element receives the QoS parameters from the policy control network element. In a possible scenario, when the core network element is the access and mobility management network element, the QoS parameters can be forwarded to the access and mobility management network element through the session management network element.

[0214] S1102: The access network device sends identification information to the first terminal apparatus. Correspondingly, the first terminal apparatus receives the identification information from the access network device.

[0215] After the access network device receives the QoS parameter, it can assign an identification information to the QoS parameter, and the identification information is used to identify the QoS parameter. Exemplarily, the identification information can be an identifier of the first terminal device, such as EPC, an inactive radio network temporary indentifier (RNTI) (I-RNTI for short), or other RNTIs, or a QoS identifier, such as a 5G QoS identifier (5G QoS identifier, 5QI), or a QoS class identifier (QCI) in 4G, or a context identifier of the first terminal device or other newly assigned identifiers (new ID), which are not limited to this.

[0216] In one possible design, the access network device may send identification information during the registration process initiated by the first terminal device. Exemplarily, the access network device sends a registration acceptance message to the first terminal device, and the first terminal device responds by receiving a registration acceptance message from the access network device. The registration acceptance message indicates that registration is complete and includes identification information.

[0217] In another possible design, the access network device may send identification information during data transmission with the first terminal device after the first terminal device completes the first random access. For example, during data transmission between the first terminal device and the access network device, the access network device may send a first message to the first terminal device. The first message includes identification information, and the first message may be an RRC message, such as an RRC release message or an RRC reconfiguration message.

[0218] Furthermore, after the first terminal device obtains the identification information, it may save the information. The first terminal device may also save the information when entering an idle state or an inactive state, so as to facilitate the execution of the following S1103 and S1104.

[0219] In an embodiment of the present application, when a first terminal device is released to an inactive state, undergoes reselection, or undergoes a cell handover to another access network device, the access network device still retains the context of the first terminal device and the corresponding context identifier. The context of the first terminal device includes QoS parameters. Thus, when the first terminal device re-accesses the network, the QoS parameter acquisition process can be reduced, thereby increasing the access network device's scheduling rate for executing the first service on the first terminal device.

[0220] In a possible scenario, a core network element may allocate identification information to the first terminal device, and the identification information may be forwarded to the first terminal device via an access network device.

[0221] S1103: The first terminal device sends identification information to the access network device. Correspondingly, the access network device receives the identification information from the first terminal device.

[0222] In one possible design scheme, the first terminal device is in a connected state and needs to trigger the execution of the first service. At this time, during the data transmission process between the first terminal device and the access network device, the first terminal device can send an RRC message to the access network device. The RRC message carries identification information, and the identification information can be used by the access network device to determine the saved context information of the first terminal device, such as the supported QoS parameters, or the QoS parameters corresponding to the first service. In addition, at this time, the first terminal device can be in a connection state of completing the first access or a connection state of completing the second access, and there is no limitation on this.

[0223] In one possible design, a first terminal device is in a non-connected state and needs to trigger execution of a first service. In this case, while the first terminal device is initiating random access again, the first terminal device may send identification information to the access network device. For example, the identification information may be carried in Msg3 or in other uplink messages during the random access process to indicate that the first terminal device needs to execute the first service. After the first terminal device completes access, the following S1104 is executed.

[0224] S1104: The access network device schedules the first terminal device to perform the first service according to the identification information.

[0225] After receiving the identification information, the access network device determines the corresponding QoS parameters based on the identification information, and then schedules the first terminal device to perform the first service based on the QoS parameters, such as allocating resources to the first terminal device to perform the first service. For example, if the QoS parameters include a latency requirement of 10ms for performing the first service, more resources may be allocated to the first terminal device for transmitting the service data of the first service due to the short latency. If the QoS parameters include a latency requirement of 50ms for performing the first service, fewer resources may be allocated to the first terminal device for transmitting the service data of the first service due to the long latency.

[0226] In the case where the identification information is the identification of the first terminal device or the context identification of the first terminal device, if the first terminal device supports multiple services, the access network device may not be able to determine which service to execute and the QoS parameters corresponding to which service based on the identification information. In this case, the access network device can implement scheduling of the first service for the first terminal device based on the configured default QoS parameters.

[0227] Based on the communication method shown in Figure 11, after the access network device obtains the QoS parameters of the first terminal device supporting the first service from the core network, it can assign identification information for identifying the QoS parameters to the first terminal device, so that when the first terminal device needs to execute the first service, the access network device can determine the corresponding QoS parameters through the identification information reported by the first terminal device, which simplifies the QoS acquisition process. The first terminal device does not need to perform a complete QoS negotiation and determination process with the access network and the core network every time it initiates a service. The corresponding QoS parameters can be simply determined through the identification information, thereby realizing flexible scheduling of the first terminal device (such as a low-complexity terminal device) to execute the first service.

[0228] The communication method shown in Figure 11 is described in detail below in conjunction with 5GS. For example, the core network element is SMF, the access network device is gNB, and the terminal device is a tag.

[0229] For example, FIG12 is a flow chart of a communication method provided in an embodiment of the present application. As shown in FIG12 , the communication method includes the following steps:

[0230] S1201. The tag initiates a random access procedure to the gNB.

[0231] Among them, the random access process of the tag and the gNB can refer to the relevant description of the process shown in Figure 2 above, and will not be repeated here.

[0232] S1202: The tag sends a registration request to the AMF. In response, the AMF receives the registration request from the tag.

[0233] The registration request includes the tag identifier and related registration information. The specific registration process can be found in the relevant description of the existing implementation and is not repeated here. Optionally, the registration request can include the QoS rule or service supported by the tag, which is equivalent to the QoS parameter. It should be understood that the QoS rule or service supported by the tag is typically service-level, and the tag can send a registration request to the AMF via the gNB.

[0234] S1203. AMF sends the QoS rules or services supported by the label to SMF. Correspondingly, SMF receives the QoS rules or services supported by the label from AMF.

[0235] It should be understood that S1203 is an optional step and may not be executed when the registration request does not include QoS rules or services.

[0236] S1204: QoS rules are acquired between the SMF and the PCF.

[0237] Exemplarily, the SMF sends a QoS request to the PCF. In response, the PCF receives the QoS request from the SMF. The QoS request is used to request the QoS rules supported by the tag. When the tag initiates registration, the SMF can request the PCF to provide QoS rules. Furthermore, the PCF sends the QoS rules to the SMF. In response, the SMF receives the QoS rules from the PCF.

[0238] S1205. The SMF sends the QoS rules to the gNB. In response, the gNB receives the QoS rules from the SMF.

[0239] For details of S1202 to S1205, refer to the relevant description of S1101 above and are not repeated here. The SMF may send the QoS rules to the gNB via the AMF.

[0240] S1206. The gNB sends an RRC release message to the tag. In response, the tag receives the RRC release message from the gNB.

[0241] The RRC release message carries identification information, which is used to identify the QoS rule. The specific implementation process of S1207 can refer to the relevant description in S1102 above, and will not be repeated here.

[0242] S1207. The tag sends identification information to the gNB. In response, the gNB receives the identification information from the tag.

[0243] When the tag initiates random access again, it sends identification information to the gNB. The identification information can be carried in any uplink message in the random access process, such as Msg3, to indicate the service to be executed.

[0244] S1208. The gNB sends an ACK message to the tag. In response, the tag receives the ACK message from the gNB.

[0245] At this point, the tag has completed random access and re-accessed the gNB.

[0246] S1209: The gNB sends a physical downlink control channel (PDCCH) to the tag. In response, the tag receives the PDCCH from the gNB.

[0247] The PDCCH carries scheduling and other control information, such as transport format, resource allocation, uplink scheduling grants, power control, and uplink retransmission information. After the tag accesses the network, the gNB determines the corresponding QoS rules based on the identification information reported in S1208, schedules services for the tag based on the QoS rules, and sends them to the tag via the PDCCH.

[0248] S1210: Data is transmitted between the gNB and the tag.

[0249] After receiving the PDCCH, the tag realizes data transmission of the service according to the scheduling information and related control information in the PDCCH.

[0250] The communication method shown in FIG11 and FIG12 realizes that when an uplink (mobile original, MO) service is triggered, the access network device can perform corresponding scheduling processing according to the QoS requirements of the terminal device or the service transmitted by the terminal device.

[0251] It can be understood that in each of the above embodiments, the methods and / or steps implemented by the access network device can also be implemented by components that can be used for the access network device (such as a processor, chip, chip system, circuit, logic module, or software); the methods and / or steps implemented by the first terminal device can also be implemented by components that can be used for the first terminal device (such as a processor, chip, chip system, circuit, logic module, or software).

[0252] The above mainly introduces the solution provided by this application. Accordingly, this application also provides a communication device, which is used to implement the various methods in the above method embodiments. The communication device can be the access network device in the above method embodiments, or a device including the access network device, or a component that can be used for the access network device, such as a chip or chip system. Alternatively, the communication device can be the first terminal device in the above method embodiments, or a device including the first terminal device, or a component that can be used for the first terminal device, such as a chip or chip system.

[0253] It is understandable that, in order to realize the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0254] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0255] Taking the communication device as an access network device or terminal device in the above method embodiment as an example, Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in Figure 13, communication device 1300 includes: a processing module 1301 and a transceiver module 1302. Among them, processing module 1301 is used to perform the processing functions of the access network device or terminal device in the above method embodiment. Transceiver module 1302 is used to perform the transceiver functions of the access network device or terminal device in the above method embodiment.

[0256] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

[0257] Since the communication device 1300 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.

[0258] In one possible design solution, in the embodiment of the present application, the transceiver module 1302 may include a receiving module and a sending module (not shown in FIG13 ). The transceiver module is used to implement the sending and receiving functions of the communication device 1300 .

[0259] In one possible design, communication device 1300 may further include a storage module (not shown in FIG. 13 ) storing programs or instructions. When processing module 1301 executes the programs or instructions, communication device 1300 may perform the functions of the access network device or terminal device in any of the methods shown in FIG. 9 to FIG. 12 .

[0260] It should be understood that the processing module 1301 involved in the communication device 1300 can be implemented by a processor or a processor-related circuit component, which can be a processor or a processing unit; the transceiver module 1302 can be implemented by a transceiver or a transceiver-related circuit component, which can be a transceiver or a transceiver unit.

[0261] For example, FIG14 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. The communication device may be an access network device or a terminal device, or may be a chip (system) or other component or assembly that can be provided in the access network device or the terminal device. As shown in FIG14 , the communication device 1400 may include a processor 1401. In one possible design scheme, the communication device 1400 may further include a memory 1402 and / or a transceiver 1403. The processor 1401 is coupled to the memory 1402 and the transceiver 1403, such as by a communication bus.

[0262] The following is a detailed introduction to the various components of the communication device 1400 with reference to FIG14 :

[0263] The processor 1401 is the control center of the communication device 1400 and can be a single processor or a collective term for multiple processing elements. For example, the processor 1401 can be one or more central processing units (CPUs), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0264] In one possible design, the processor 1401 may execute various functions of the communication device 1400 by running or executing software programs stored in the memory 1402 and calling data stored in the memory 1402 .

[0265] In a specific implementation, as an embodiment, the processor 1401 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG14 .

[0266] In a specific implementation, as an embodiment, the communication device 1400 may also include multiple processors, such as the processor 1401 and the processor 1404 shown in FIG14 . Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0267] The memory 1402 is used to store the software program for executing the solution of the present application, and the execution is controlled by the processor 1401. The specific implementation method can refer to the above method embodiment and will not be repeated here.

[0268] In one possible design, the memory 1402 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1402 can be integrated with the processor 1401 or exist independently and be coupled to the processor 1401 through an interface circuit (not shown in FIG. 14 ) of the communication device 1400. This embodiment of the present application does not specifically limit this.

[0269] Transceiver 1403 is used for communication with other communication devices. For example, if communication device 1400 is a terminal device, transceiver 1403 can be used to communicate with a network device or another terminal device. For another example, if communication device 1400 is a network device, transceiver 1403 can be used to communicate with a terminal device or another network device.

[0270] In one possible design, transceiver 1403 may include a receiver and a transmitter (not separately shown in FIG14 ), wherein the receiver is configured to implement a receiving function, and the transmitter is configured to implement a transmitting function.

[0271] In one possible design scheme, the transceiver 1403 can be integrated with the processor 1401, or it can exist independently and be coupled to the processor 1401 through the interface circuit of the communication device 1400 (not shown in Figure 14). This embodiment of the present application does not specifically limit this.

[0272] It should be noted that the structure of the communication device 1400 shown in FIG14 does not constitute a limitation on the communication device. An actual communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0273] In addition, the technical effects of the communication device 1400 can refer to the technical effects of the methods described in the above method embodiments, and will not be repeated here.

[0274] An embodiment of the present application further provides a computer-readable storage medium on which a computer program or instruction is stored. When the computer program or instruction is executed by a computer, the functions of the above-mentioned method embodiment are realized.

[0275] The embodiments of the present application also provide a computer program product, which implements the functions of the above method embodiments when executed by a computer.

[0276] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0277] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0278] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0279] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0280] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0281] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0282] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

Claims

1. A communication method, characterized in that: The method comprises: Receiving a quality of service (QoS) parameter of a first service from a core network element; Paging at least one terminal device executing the first service; In a case where at least one terminal device executing the first service is paged, the at least one terminal device is scheduled to execute the first service according to the QoS parameter.

2. The method according to claim 1, characterized in that The paging at least one terminal device executing the first service includes: receiving first indication information from the core network element, where the first indication information is used to indicate that the first service needs to be executed; At least one terminal device executing the first service is paged according to the first indication information.

3. The method according to claim 2, characterized in that The first indication information and the QoS parameter are carried in the same message.

4. The method according to any one of claims 1 to 3, characterized in that The QoS parameters include at least one of the following: a data transmission delay requirement for executing the first service, a priority of the first service, and a reliability requirement for transmitting the first service.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: Sending second indication information to the core network element, where the second indication information is used to indicate that the first service is executed by the terminal device.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Send third indication information to the core network element, where the third indication information is used to instruct to stop scheduling the first service or to stop data transmission of the first service.

7. The method according to claim 6, characterized in that The third indication information includes the reason for stopping scheduling of the first service, or the reason for stopping data transmission of the first service.

8. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Receive fourth indication information from the core network network element, where the fourth indication information is used to instruct the access network device to stop data transmission of the first service.

9. A communication method, characterized in that: The method comprises: Receiving identification information from an access network device, where the identification information is used to identify a quality of service (QoS) parameter; When the first service needs to be executed, the identification information is sent to the access network device.

10. The method according to claim 9, characterized in that The receiving identification information from the access network device includes: During the process of initiating registration by the first terminal device, a registration acceptance message is received from the access network device, where the registration acceptance message includes the identification information.

11. The method according to claim 9, characterized in that The receiving identification information from the access network device includes: During the transmission between the first terminal device and the access network device, a first message from the access network device is received, where the first message includes the identification information.

12. The method according to any one of claims 9 to 11, characterized in that: The sending the identification information to the access network device includes: When the first terminal device initiates random access again, the identification information is sent to the access network device.

13. The method according to any one of claims 9 to 11, characterized in that: The sending the identification information to the access network device includes: Send an RRC message to the access network device, where the RRC message includes the identification information.

14. The method according to any one of claims 9 to 13, characterized in that: The QoS parameters include at least one of the following: a priority of the first service, a data transmission delay requirement for executing the first service, and a reliability requirement for transmitting the first service.

15. The method according to any one of claims 9 to 14, characterized in that: The identification information is an identification of the first terminal device or a QoS identification or a context identification of the first terminal device.

16. A communication method, characterized in that: The method comprises: Receive QoS parameters from core network elements; Identification information is sent to the first terminal device, where the identification information is used to identify the QoS parameter.

17. The method according to claim 16, characterized in that The method further comprises: receiving identification information from the first terminal device; The first terminal device is scheduled to perform a first service according to the identification information.

18. The method according to claim 17, characterized in that The receiving identification information from the first terminal device includes: In the process of the first terminal device initiating random access again, the identification information is received from the first terminal device.

19. The method according to claim 17, characterized in that The receiving identification information from the first terminal device includes: A radio resource control (RRC) message is received from the first terminal device, the RRC message including the identification information.

20. The method according to any one of claims 16 to 19, characterized in that The sending identification information to the first terminal device includes: During the process of the first terminal device initiating registration, a registration acceptance message is sent to the first terminal device, where the registration acceptance message includes the identification information.

21. The method according to any one of claims 16 to 19, characterized in that The sending identification information to the first terminal device includes: During the transmission between the first terminal device and the access network device, a first message is sent to the first terminal device, where the first message includes the identification information.

22. The method according to any one of claims 16 to 21, characterized in that The method further comprises: If the first terminal device is released to an inactive state or reselection occurs or the cell is switched to another access network device, the context of the first terminal device is still retained, and the context of the first terminal device includes the QoS parameters.

23. The method according to any one of claims 16 to 22, characterized in that The QoS parameters include at least one of the following: a priority of the first service, a data transmission delay requirement for executing the first service, and a reliability requirement for transmitting the first service.

24. The method according to any one of claims 16 to 23, characterized in that The identification information is an identification or a QoS identification of the first terminal device or a context identification of the first terminal device.

25. A communication device, characterized in that: The method comprises a module for executing the method according to any one of claims 1 to 8, or comprises a module for executing the method according to any one of claims 9 to 15, or comprises a module for executing the method according to any one of claims 16 to 24.

26. A communication device, characterized in that: The method comprises a processor configured to execute the method according to any one of claims 1 to 8, or configured to execute the method according to any one of claims 9 to 15, or configured to execute the method according to any one of claims 16 to 24.

27. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, it implements the method as described in any one of claims 1 to 8, or implements the method as described in any one of claims 9 to 15, or implements the method as described in any one of claims 16 to 24.

28. A computer program product, characterized in that The method comprises a computer program code. When the computer program code is executed on a communication device, the communication device implements the method according to any one of claims 1 to 8, or implements the method according to any one of claims 9 to 15, or implements the method according to any one of claims 16 to 24.

Images