Communication method and device

Abstract

The embodiment of the invention provides a communication method and device, relates to the field of communication, and can realize scheduling based on QoS (Quality of Service) parameters for low-complexity terminal equipment. The method comprises: receiving a quality of service (QoS) parameter of a first service from a network element of a core network; and paging the at least one terminal device executing the first service, and scheduling the at least one terminal device to execute the first service according to the QoS parameter under the condition that the at least one terminal device executing the first service is paged.

Description

Technical Field

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

[0002] 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 called RFID terminals). Tags use low-precision, low-power medium-low frequency ring oscillators or oscillators without local oscillation to receive downlink signals. When the tag is working, the energy and carrier of the communication come from the reader, and the 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 signal sent by the reader, and sends the signal 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.

[0003] At present, the quality of service (QoS) parameters for each terminal device are QoS parameters allocated during the session establishment process after the terminal device accesses the network. This process of establishing a session and configuring QoS parameters for each terminal device is relatively complicated and is not suitable for low-complexity terminal devices, so it is impossible to implement scheduling of low-complexity terminal devices based on QoS parameters. Summary of the invention

[0004] The embodiments of the present application provide a communication method and apparatus, which can realize service transmission with guaranteed QoS for low-complexity terminal devices.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions:

[0006] In a first aspect, a communication method is provided, which can be executed by an access network device, or by a component of the access network device, such as a processor, a chip, or a chip system of the access network device, or by a logic module or software that can implement all or part of the functions of the access network device. The method includes: receiving a quality of service QoS parameter of a first service from a core network network element. Paging at least one terminal device that executes the first service. When paging to at least one terminal device that executes the first service, scheduling at least one terminal device to execute the first service according to the QoS parameter.

[0007] Based on the communication method, the access network device obtains the 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 according to the QoS parameters of the first service, without configuring QoS parameters for each terminal device, simplifying the processing flow of QoS parameters between the terminal device and the network, and reducing signaling overhead, so as to realize flexible QoS-based scheduling of terminal devices (such as low-complexity terminal devices). In the 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.

[0008] In a possible design scheme, paging at least one terminal device that performs 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 performed. Paging at least one terminal device that performs the first service according to the first indication information. Based on this design scheme, the access network device may trigger paging of the terminal device according to the first indication information sent by the core network element, so as to schedule at least one paged terminal device to perform the first service according to the QoS parameters of the first service.

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

[0010] In a 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, such as a 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 there are multiple services, and the reliability requirement for transmitting the first service is used to ensure the reliability of data transmission of the first service.

[0011] In a possible design scheme, the method provided in the embodiment of the present application may further include: sending a second indication information to a core network element. The second indication information is used to indicate that the first service is executed by the terminal device. Based on this design scheme, the access network device may also inform the core network element of the execution status of the first service through the second indication information, so that the core network element triggers subsequent services.

[0012] In a possible design scheme, the method provided in the embodiment of the present application may also include: sending a third indication message to a core network element. The third indication message is used to indicate to stop scheduling the first service or to stop 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 element to inform the situation of stopping scheduling the first service or stopping data transmission of the first service, so as to realize flexible start and termination of service transmission process. 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 realize service transmission control of the first service.

[0013] 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 an erroneous operation due to unknown reasons.

[0014] In a possible design scheme, the method provided in the 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 the data transmission of the first service. Thus, the access network device can stop the data transmission of the service according to the fourth indication information issued by the core network element, and can realize flexible start and end of the service transmission process.

[0015] In a second aspect, a communication method is provided, which can be executed by a first terminal device, or by a component of the first terminal device, such as a processor, a chip, or a chip system of the first terminal device, or by a logic module or software that can implement 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 a quality of service QoS parameter. When the first service needs to be executed, the identification information is sent to the access network device.

[0016] Based on this communication method, after the access network device obtains the QoS parameters from the core network, it can allocate 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, thereby simplifying 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.

[0017] In a 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. Usually, the service process is after the registration process, and the identification information is allocated to the first terminal device during the registration process, so that the first terminal device can directly use the identification information in the subsequent service process to trigger the access network device to schedule the first service without obtaining it again, thereby simplifying the process and reducing the service waiting delay.

[0018] In a possible design scheme, receiving identification information from an access network device may include: receiving a first message from the access network device during transmission 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 data transmission with the first terminal device. When 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 having to obtain it again, thereby simplifying the process and reducing service waiting delay.

[0019] In a possible design, sending identification information to the access network device may include: sending identification information to the access network device during the process of the first terminal device initiating random access again. Based on this design, the access network device may receive identification information from the first terminal device during the next random access process, and trigger service scheduling for the first terminal device according to the identification information.

[0020] In one possible design, sending 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 according to the identification information.

[0021] In a 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.

[0022] In a possible design scheme, 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.

[0023] In a third aspect, a communication method is provided, which can be executed by an access network device, or by a component of the access network device, such as a processor, a chip, or a chip system of the access network device, or can be implemented by a logic module or software that can implement all or part of the functions of the access network device. The method includes: receiving a quality of service QoS parameter from a core network network element. Sending identification information to a first terminal device, the identification information being used to identify the QoS parameter.

[0024] 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.

[0025] In a possible design scheme, 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.

[0026] 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.

[0027] In a 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.

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

[0029] In a 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 reselects or the cell is switched to another access network device, the context of the first terminal device is still retained. The context of the first terminal device includes QoS parameters.

[0030] In a 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.

[0031] In a possible design scheme, 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.

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

[0033] 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 aspect to the third aspect, and the module, unit, or means can be implemented by hardware, software, or by hardware executing the corresponding software implementation. 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 execute functions of the communication device other than the transceiver function.

[0034] In a 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.

[0035] In a possible design scheme, the communication device described in the fourth aspect may further include a storage module, which 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.

[0036] 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 an access network device, and this application does not limit this.

[0037] 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.

[0038] 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 program 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.

[0039] In one possible design, the processor may be integrated with the memory.

[0040] In some possible designs, the communication device also includes: a communication interface; the communication interface is used to communicate with a module outside the communication device.

[0041] 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 an access network device, and this application does not limit this.

[0042] 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.

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

[0044] In a possible design scheme, the communication device described in the sixth aspect may also include a memory. The memory may be integrated with the processor or may be separately provided. The memory may be used to store the computer program and / or data involved in the method described in any one of the first to third aspects above.

[0045] 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.

[0046] In the seventh aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. 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.

[0047] 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.

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

[0049] 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

[0050] Figure 1 A schematic diagram of the architecture of an RFID system;

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

[0052] Figure 3 A schematic diagram of a 5G QoS establishment process;

[0053] Figure 4 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0054] Figure 5 A schematic diagram of a scenario applied to a communication system provided in an embodiment of the present application;

[0055] Figure 6 A schematic diagram of another scenario applied to a communication system provided in an embodiment of the present application;

[0056] Figure 7 A schematic diagram of another scenario applied to a communication system provided in an embodiment of the present application;

[0057] Figure 8 A schematic diagram of another scenario applied to a communication system provided in an embodiment of the present application;

[0058] Fig. 9 A flow chart of a communication method provided in an embodiment of the present application;

[0059] Fig.10 A flowchart of another communication method provided in an embodiment of the present application;

[0060] Fig.11 A flowchart of another communication method provided in an embodiment of the present application;

[0061] Fig.12 A flowchart of another communication method provided in an embodiment of the present application;

[0062] Fig.13 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0063] Fig.14 A schematic diagram of the structure of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0064] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0065] 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, worldwide 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.

[0066] 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. In addition, combinations of these schemes may also be used.

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

[0068] 1. RFID

[0069] RFID technology is a contactless automatic identification technology. Figure 1 ,like Figure 1 As shown, the RFID system includes a tag and a reader. The reader integrates an antenna, and the antenna is used for transceiver processing, or the reader and the antenna are separately set. Specifically, the reader charges the tag by sending an excitation signal to the low-cost tag, and the tag receives the signal sent by the reader and sends the signal to the reader through the reflected signal. In this way, the reader can identify the ID of the tag, and the reader can read and write the tag. The reader can also perform other operations on the tag, which are not limited here.

[0070] The reader / writer may also be called a reader, an exciter, an excitation source, a radio frequency source, or an interrogator, etc., without limitation. The excitation signal may also be called a carrier signal, a radio frequency signal, or a wireless signal, etc., without limitation. The tag uses a low-precision, low-power medium-low frequency ring oscillator or a completely local oscillator to receive downlink signals. The tag may also be called a low-power terminal device, a tag device, a passive device, etc.

[0071] In view of the advantage of RFID communication technology in low power consumption, 5G passive Internet of Things (Ambient Internet of Things, A-IoT) came into being. In order to meet the ultra-low power consumption requirements, the tags in A-IoT also use low-precision and low-power medium-low frequency ring oscillators or completely no local oscillator to receive downlink signals. This receiving method can further reduce the power consumption of the tag downlink reception. For this kind of low-power receiving method, only amplitude detection such as envelope detection can be performed, because only low-precision ring oscillators cannot guarantee accurate demodulation of signal phase information.

[0072] The tag cost is low, the design complexity is also low, the coverage is poor, and the applicable scenarios are limited. During the research process of 5G A-IoT, coverage enhancement design is needed. At present, the 3rd Generation Partnership Project (3GPP) standard agrees that 5G A-IoT can include the following three types of devices:

[0073] Device A: has no energy storage, cannot generate signals independently, and uses reflection transmission;

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

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

[0076] 2. Inventory

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

[0078] 3. Interaction process between tag and reader

[0079] See also Figure 2 , Figure 2 Figure 1 is a flow chart of the interaction between a tag and a reader. Figure 2As shown, tag access includes the following steps:

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

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

[0082] The tag receives the selection command from the reader and determines whether the information stored in the corresponding position of the tag's own storage area is consistent with the mask information in the selection command. If they are consistent, the tag considers that it meets the selection criteria for reading and writing. At this time, the tag can set the state of a certain inventory flag, such as setting the state A of the first inventory flag to state B. Conversely, the tag that does not match the reader's selection condition sets the first inventory flag from state B to A. A / B here can also be replaced by 0 / 1, without limitation.

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

[0084] 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.

[0085] 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 it is 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] randomly selects a value k and saves it as a counter value (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 (16-bit random or pseudo-random, RN16).

[0086] 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.

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

[0088] RN16 is used to indicate the temporary ID of the tag. When the tag receives the query command, if the tag confirms that counter = 0, it selects a 16-bit random number as RN16 and feeds the RN16 back to the reader. If the reader detects that the tag feeds back RN16, it means that the inventory process is proceeding normally, and the reader performs the next action. Specifically, RN16 is carried in message (message, Msg) 3 and sent. Msg3 is also called message three or the third message.

[0089] S204: The reader sends an ACK message to the tag. Correspondingly, the tag receives the ACK message from the reader.

[0090] 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.

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

[0092] 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, and the tag sends uplink data to the reader, such as the electronic product code (EPC), which is used to indicate the real ID of the tag.

[0093] Optionally, after the tag completes random access, the following interaction process still exists between the tag and the reader:

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

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

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

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

[0098] When 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. The QueryRep signaling can also be used to trigger the next access opportunity, that is, the tag whose counter is not 0 performs a subtraction operation. When counter = 0, the tag can initiate the next random access.

[0099] 5G QoS

[0100] See also Figure 3 , the QoS of 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 interacts with the user plane function (UPF), the policy control function (PCF) and the unified data management (UDM) to exchange UE registration information and obtain the UE's QoS information.

[0101] 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. SMF can construct a QoS flow template through a service data flow (SDF) template, where the SDF template is defined in the policy and charging control (PCC) framework. The SDF template contains one or more SDF filters that can filter the service data flow.

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

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

[0104] 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.

[0105] QoS flow is the smallest carrier of 5G QoS. QoS flow is the smallest granularity of 5G services. When the management of PDU session in the control plane process is completed, the user plane channel is established, and the QoS flow carries data packets on the user plane channel to transmit data.

[0106] 5G QoS framework overview:

[0107] 1) Based on QoS flow, this is the finest granularity of QoS differentiation, that is, QoS parameters and features are bound to a QoS flow. QoS parameters include latency, priority, special data representation, etc. These parameters jointly determine the final priority of a QoS flow. Features are similar to data packet headers. If all the above parameters are written into a data packet, the data will be too lengthy. For this reason, we choose to define a paradigm and define parameters of various levels in advance, and only use simple data to express various features. That is, features are a collection of individual parameters.

[0108] 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).

[0109] 3) Next generation radio access network (NG-RAN) can establish a (data) radio bearer according to the logic in NG-RAN, or NG-RAN 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.

[0110] After the QoS flow is determined, the UE, NG-RAN, and UPF will know the corresponding QoS flow information in advance. Therefore, QFI is even more important as an identifier. QFI is carried in the general packet radio service (GPRS) tunneling protocol (GTP)-user plane (user, U) encapsulation header and sent through the N3 (and N9) interface (i.e., AN to UPF section), that is, the encapsulation header remains unchanged during the end-to-end transmission.

[0111] 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.

[0112] based on Figure 3 In the process shown, QoS parameters are all used to establish QoS-related configuration information for per UE after the session is established. This process of per UE establishing a session and configuring QoS parameters is relatively complicated and is not suitable for ultra-low-complexity terminal devices (such as tags), so it is impossible to implement QoS-based scheduling for low-complexity terminal devices.

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

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

[0115] First, in the embodiments of the present application, "used for indication" may include being used for direct indication and being used for indirect indication. When describing that a certain "indication information" is used to indicate A, it may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must carry A.

[0116] 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, the information to be indicated can be directly 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, the indication of specific information can also be achieved with the help of the arrangement order of each piece of information agreed in advance (for example, stipulated by the protocol), thereby reducing the indication overhead to a certain extent. At the same time, the common parts of each piece of information can also be identified and indicated uniformly to reduce the indication overhead caused by indicating the same information separately.

[0117] In addition, the specific indication method may 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 refer 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, different indication methods may be used for different information. In the specific implementation process, the desired 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.

[0118] 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 pre-defined, for example, pre-defined according to the protocol, or can be configured by the transmitting device by sending configuration information to the terminal device. Among them, the configuration information can include, for example, but not limited to, one or a combination of at least two of RRC signaling, media access control (media access control, MAC) layer signaling and physical layer signaling. Among them, MAC layer signaling, for example, includes MAC-control element (control element, CE); physical (physical, PHY) layer signaling, for example, includes downlink control information (downlink control information, DCI).

[0119] Second, in the embodiments of the present application, the first, second and various digital numbers are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application. For example, to distinguish different indication information. For another example, the first indication information and the second indication information are only used to distinguish different areas, and their order is not limited. Those skilled in the art can understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not necessarily limit them to be different.

[0120] Third, in the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all mean that under certain objective circumstances, the device (such as a terminal device or an access network device) will make corresponding processing, which is not a time limit, 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.

[0121] Meanwhile, in the embodiments of the present 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 the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0122] 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 are 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.

[0123] Finally, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present 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 the present application are also applicable to similar technical problems.

[0124] The following first introduces the system architecture involved in the embodiment of the present application:

[0125] 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 devices, components, modules, etc. discussed in conjunction with the figures. In addition, combinations of these schemes may also be used.

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

[0127] Understandable, Figure 4 The communication system shown may also include other network devices, such as access network device 401b and / or access network device 301c; Figure 4 The communication system shown may also include other second-type terminals, such as the second-type terminal 403b. Figure 4 The communication system shown may also include other first category terminals.

[0128] in, Figure 4 In the provided communication system, 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.

[0129] 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.

[0130] 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.

[0131] A communication connection 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.

[0132] 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.

[0133] The first type of terminal is a device with extremely low power consumption and / or extremely low complexity or a device in a device with extremely low power consumption and / or extremely low complexity. The first type of terminal can be called a terminal device in the Internet of Things, and can also be called 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 back-reflection terminal / device, a backscatter terminal, a passive IoT, a reflector, a reflection terminal, or an ambient signal device, etc. In the following method embodiments, the first type of terminal is taken as an example of a terminal device for explanation.

[0134] 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 handset, a laptop computer, a machine type communication (MTC) terminal, a computer with a 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, 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 a terminal function, and a wireless terminal in a smart city. unit, RSU), etc., flying equipment (e.g., intelligent robot, hot air balloon, drone, airplane), etc. The terminal of the present application may also be a vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit built into the 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.

[0135] 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 a device that can support the terminal device to realize the function, such as a chip system. The device can 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 a device that can support the terminal device to realize the function, such as a chip system. The device can 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.

[0136] The access network device may also be referred to as a RAN node, a network device, a RAN entity or an access node, etc., which is located on the network side of the above-mentioned communication system to help the terminal device achieve wireless access, and has a device with wireless transceiver function 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, etc. 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 the 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 by software functions running on hardware, or by 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.

[0137] In another possible scenario, multiple RAN nodes collaborate to assist the terminal device 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 can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).

[0138] 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, CU, CU-CP, CU-UP, DU and RU are described as examples in this application. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0139] In the embodiments of the present application, the form of the access network device is not limited. The device for realizing the function of the access network device may be the access network device; or it may be a device capable of supporting the access network device to realize the function, such as a chip system. The device may be installed in the access network device or used in conjunction with the access network device.

[0140] In an embodiment of the present application, the communication system may further include a core network element, which 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.

[0141] besides, Figure 4 The communication system shown 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 a 5G system, the session management network element may be a session management function (session management function, SMF), the network exposure network element may be a network exposure function (network exposure function, NEF), and the policy control network element may be a policy control function (policy control function, PCF), and there is no limitation on this.

[0142] Understandable, Figure 4 In the example, 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 an access network device. Figure 4 The second type of terminal in can be configured as a mobile base station.

[0143] Above Figure 4 In the communication system shown, the access network device can be used to implement the reading and writing functions of the reader / writer, and the second type of terminal can be used to assist the access network device in implementing the reading and writing functions of the reader / writer. It can be understood that Figure 4 In the provided communication system, any access network device can be used to assist other access network devices in the communication system to implement the reading and writing functions of the reader / writer. For example, an integrated access and backhaul (IAB) device can be used to assist the base station to implement the functions of the reader / writer. Or, Figure 4 Any second-category terminal in the provided communication system can be used to assist other second-category terminals in realizing the reading and writing functions of the reader / writer.

[0144] In the following examples, the access network device 401a, the first type of terminal 402a and the second type of terminal 403a are described.

[0145] In a possible design scheme, 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.

[0146] In this case, if Figure 5 As shown, the access network device 401a can provide a carrier for the first type terminal 402a. The access network device 401a can also receive uplink data from the first type terminal 402a, and the access network device 401a can also send downlink data to the second type terminal 403b, and the second type terminal 403b then sends the downlink data to the first type terminal 402a.

[0147] Or, if Figure 6 As shown, the second type terminal 403b device 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 the access network device 401a can also send downlink data to the second type terminal 403b, and the second type terminal 403b then sends the downlink data to the first type terminal 402a.

[0148] In a possible design scheme, 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.

[0149] In this case, if Figure 7 As shown, 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.

[0150] Or, if Figure 8 As shown, 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.

[0151] 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.

[0152] The following will be combined Figure 9-12 The communication method provided in the embodiment of the present application is described in detail.

[0153] For example, Fig. 9 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 core network element action in the method can 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 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.

[0154] like Fig. 9 As shown, the communication method includes the following steps:

[0155] 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.

[0156] In the embodiment of the present application, the QoS parameters are configured based on the granularity of the service. One QoS parameter corresponds to one service. The QoS parameter of the first service is used by the access network device to schedule the terminal device executing the first service. The QoS parameter of the first service can support at least one terminal device to execute the first service. Figure 4 The first type of terminal shown is, for example, a tag, and 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, such as an inventory service, a sensing service, a reading service, a writing service, an inactivation service, etc. The service involved in the embodiment of the present application can also be referred to as an A-IoT service. It should be understood that the QoS parameter can be used to indicate the service quality requirement for at least one terminal device to complete a certain service, or to ensure the service quality of the first service.

[0157] 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 reflect, or indicate) 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 time the core network or application layer sends the first service trigger signaling (such as the first indication information described below), or from the time the access network device receives the first service trigger signaling, and the deadline is as in the example above, and there is no limitation on this. By way of example, the transmitted service data may be identification information of the terminal device.

[0158] 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 executing 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 executing the first service, and the service data transmission delay requirement between the access network device and the core network. It should be understood that the core network element for the final data reporting can be the core network element that sends the QoS parameters of the first service, or other network elements in other core networks, without limitation.

[0159] In addition to the delay requirement, the QoS parameters of the first service may also include: the priority of the first service, and / or the reliability requirement for transmitting the first service, etc. Among them, 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, and the reliability requirement for transmitting the first service may refer to the reliability requirement for the service data of the first service, for example, the requirements for the bit error rate, jitter, packet loss rate, etc. of the transmission.

[0160] 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 a possible design, the access and mobility management element may send the QoS parameters of the first service to the access network device based on the triggering of the network open element or the session management element. The network open element may be an NEF in 5G, and the session management element may be an SMF in 5G.

[0161] Exemplarily, the network open network element or the session management network element sends a second message to the access and mobility management network element, and accordingly, the access and mobility management network element can 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 the service identifier of the first service, the service mode of the first service, and the service type of the first service. The service identifier is used to identify the service, and may also be called a transaction ID. The service mode may include an inventory mode, a read mode, or a write mode, etc. Optionally, the second message may also include geographic area information, information (such as a mask or filtering information) for selecting a terminal device for executing the first service, etc., wherein the geographic area information is used to indicate the area range where the first service can be executed or the area range where the first service is required to be executed, and can be used to select a terminal device within a specified area to execute the first service.

[0162] Further, the access and mobility management network element sends a third message to the policy control network element according to the second message, and correspondingly, the policy control network element receives the third message from the access and mobility management network element. The third message is used to request the 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 the QoS policy information to the access and mobility management network element according to the third message, and correspondingly, the access and mobility management network element receives the 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 according to 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 the embodiment of the present application, the policy control network element may be the PCF in 5G.

[0163] 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.

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

[0165] After the access network device obtains the QoS parameters of the first service, it can page at least one terminal device to execute 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 execute 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 randomly accessed terminal device supports the first service. The specific implementation process of paging the terminal device can refer to the above Figure 2 The relevant description of the random access process shown is not repeated here. In the embodiment of the present application, the access network device can specify the relevant transmission or scheduling strategy according to the QoS parameter, and the access network device can also consider the QoS parameter when paging at least one terminal device to perform the first service, such as determining the configuration of the terminal device under the paging according to the QoS parameter.

[0166] In a possible design, the access network device may receive first indication information from a core network element, and page at least one terminal device that performs a first service according to the first indication information. The first indication information is used to indicate that the first service needs to be performed or the first indication information is used to indicate that at least one terminal device can be selected to perform the first service. In other words, the access network device may page the terminal device to perform the first service based on the triggering of the core network element.

[0167] 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) 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), and when receiving a certain service type, the access network device needs to wait for the core network release indication to be received before releasing the terminal device, or release it after there is no data transmission for a period of time, etc.

[0168] 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.

[0169] 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.

[0170] In the embodiment of the present application, the first service may be triggered by the core network as well as by the application server or the application layer through the core network.

[0171] 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.

[0172] 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.

[0173] After the access network device determines at least one terminal device supporting the first service, it can determine a scheduling strategy based on the QoS parameters of the first service. The scheduling strategy may include selecting which terminal devices to perform the first service, what kind of resources to allocate to the selected terminal devices, how much bandwidth, what coding method to use, the modulation order, and the number of transmission repetitions, etc., without limitation. Among them, selecting which terminal devices to perform the first service may include selecting the number and location of the terminal devices that perform 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 geographical location.

[0174] Exemplarily, the QoS parameters of the first service include the data transmission delay requirement for executing the first service, the first service is an inventory service, the delay requirement is 100 milliseconds (ms), and 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. Therefore, the access network device can determine which terminal devices among the paged terminal devices can be supported to execute the inventory service within the data transmission delay according to the data transmission delay requirement combined with the total number of terminal devices paged, the distance between each terminal device and the access network, and other factors, and allocate data transmission resources to the selected terminal device, thereby instructing the selected terminal device to report the application layer identifier.

[0175] 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 among the multiple services except the first service based on the priority of the first service. If so, the terminal device is preferentially scheduled to execute the first service. If not, the terminal device is scheduled to execute the first service in order of the priorities of the multiple services.

[0176] 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 can consider some of the QoS parameters to schedule the terminal device to perform the first service, without limitation.

[0177] After the access network device schedules the terminal device that executes the first service according to the QoS parameters of the first service, or after the access network device obtains the service data reported by the terminal device, in a possible design scheme, the access network device can send a second indication message to the core network network element, and correspondingly, the core network network element receives the second indication message from the access network device. The second indication message is used to indicate that the first service is executed by the terminal device. That is to say, after completing the scheduling of the first service, the access network device can inform the core network network element of the execution status of the first service, such as whether to start execution, the number of terminal devices that execute the first service, and the service data reporting status.

[0178] It should be understood that in some cases, the second indication information may also indicate that the first service is not executed or cannot be executed, such as the first service is not executed temporarily due to a low priority, or the first service cannot be executed due to limited resources. Optionally, the second indication information may also indicate the reason why the first service is not executed or cannot be executed.

[0179] 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 to stop data transmission of the first service or to stop executing the transmission of the first service. Stopping scheduling the first service may mean that the access network device stops allocating scheduling resources to the terminal device to execute the first service, and stopping data transmission of the first service or stopping transmission of 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, and there is no limitation on this.

[0180] In a 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 delay requirements, 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.

[0181] 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 the transmission or release the connection state, or may stop sending any signal or carrier to the terminal device.

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

[0183] 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 from the first terminal device or the core network or received a completion indication within the indicated time, the access network device may also retrigger 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.

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

[0185] based on Fig. 9 In the communication method shown, 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 and can reduce signaling overhead, thereby realizing flexible QoS-based scheduling of terminal devices (such as low-complexity terminal devices).

[0186] 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 thereto.

[0187] The following is combined with 5GS Fig. 9 The communication method shown is described in detail. Take the core network element as AMF, the access network device as gNB, and the terminal device as a tag as an example.

[0188] For example, Fig.10 A flow chart of a communication method provided in an embodiment of the present application. Fig.10 As shown, the communication method includes the following steps:

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

[0190] 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.

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

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

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

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

[0195] S1003. PCF sends QoS policy information to AMF. Correspondingly, AMF receives QoS policy information from PCF.

[0196] Among them, the specific description of the QoS policy information can refer to the relevant description of the QoS policy information in the above S901, which will not be repeated here.

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

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

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

[0200] S1005. gNB executes the first service according to the QoS parameter scheduling label 1 of the first service.

[0201] S1006. gNB executes the first service according to the QoS parameter scheduling label 2 of the first service.

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

[0203] Above Fig. 9 and Fig.10 It shows that before the terminal device accesses the network, the network side triggers the service execution (downlink trigger), and the access network equipment implements the scheduling process of the terminal device according to the obtained service-level QoS parameters. The embodiment of the present application also provides a communication method, which can be based on the triggering of the terminal device, and the access network equipment implements the scheduling process of the terminal device according to the obtained service-level QoS parameters.

[0204] For example, Fig.11 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.

[0205] like Fig.11 As shown, the communication method includes the following steps:

[0206] 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.

[0207] For QoS parameters, it can be a service-level QoS parameter for each terminal device (such as a first terminal device), supporting a terminal device to perform the service (such as a first service). In this case, the QoS parameters can be called QoS parameters for the first terminal device that supports the first service. Among them, the QoS parameters 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 parameters are 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, which will not be elaborated on. In the embodiment of the present application, the terminal device is the above-mentioned Figure 4 The first type of terminal is shown. 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 read service 1. In other words, QoS parameters can be bound to service types, or there can be multiple QoS parameter configurations under the same service type.

[0208] 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 (such as the 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 the QoS parameter of the first service, and it may be understood that the QoS parameter includes the QoS parameters corresponding to at least one terminal device supporting the first service. In this case, the specific description of the QoS parameter may refer to the relevant description in the above S901, which will not be repeated here.

[0209] 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.

[0210] 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 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 via the access and mobility management network element.

[0211] In a 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.

[0212] 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.

[0213] After receiving the QoS parameters, the access network device can assign an identification information to the QoS parameters, and the identification information is used to identify the QoS parameters. 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 QoS identifier (5G QoS identifier, 5QI) in 5G, or a QoS class identifier (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.

[0214] In a possible design, the access network device may send identification information during the process of the first terminal device initiating registration. Exemplarily, the access network device sends a registration acceptance message to the first terminal device, and correspondingly, the first terminal device receives a registration acceptance message from the access network device. The registration acceptance message indicates that the registration is completed, and the registration acceptance message includes the identification information.

[0215] 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. Exemplarily, 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.

[0216] Furthermore, after the first terminal device obtains the identification information, it can save it. The first terminal device also saves it when entering an idle state or an inactive state, so as to execute the following S1103 and S1104.

[0217] In the embodiment of the present application, when the first terminal device is released to an inactive state or reselection or cell switching occurs to other access network devices, the access network device still retains the context and corresponding context identifier of the first terminal device. The context of the first terminal device includes QoS parameters. Therefore, when the first terminal device accesses the network again, the QoS parameter acquisition process can be reduced, and the scheduling rate of the access network device for the first service to the first terminal device can be increased.

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

[0219] 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.

[0220] In one possible design, 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, which can be used by the access network device to determine the context information of the first terminal device that is saved, 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 that completes the first access, or in a connection state that completes the second access, and there is no limitation on this.

[0221] In a possible design, the first terminal device is in a non-connected state and needs to trigger the execution of the first service. At this time, when the first terminal device initiates random access again, the first terminal device can send identification information to the access network device. For example, the identification information can be carried in Msg3 or carried in other uplink messages in the random access process to indicate that the first terminal device needs to execute the first service. After the first terminal device completes the access, the following S1104 is executed.

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

[0223] After receiving the identification information, the access network device determines the corresponding QoS parameters according to the identification information, and then schedules the first terminal device to perform the first service according to the QoS parameters, such as allocating resources to the first terminal device to perform the first service. Exemplarily, if the QoS parameters include a delay requirement of 10ms for performing the first service, more resources can be allocated to the first terminal device for transmitting the service data of the first service due to the short time. If the QoS parameters include a delay requirement of 50ms for performing the first service, fewer resources can be allocated to the first terminal device for transmitting the service data of the first service due to the long time.

[0224] 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 which service corresponds to the QoS parameters 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.

[0225] based on Fig.11In the communication method shown, after the access network device obtains the QoS parameters of the first terminal device supporting the first service from the core network, it can allocate 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, thereby simplifying 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.

[0226] The following is combined with 5GS Fig.11 The communication method shown is described in detail. Take the core network element as SMF, the access network device as gNB, and the terminal device as a tag as an example.

[0227] For example, Fig.12 A flow chart of a communication method provided in an embodiment of the present application. Fig.12 As shown, the communication method includes the following steps:

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

[0229] The random access process between the tag and the gNB can be found in the above Figure 2 The description of the process shown will not be repeated here.

[0230] S1202: The tag sends a registration request to the AMF. Correspondingly, the AMF receives the registration request from the tag.

[0231] Among them, the registration request includes the tag identifier and related registration information. For the specific registration process, please refer to the relevant description in the existing implementation method, which will not be repeated here. Optionally, the registration request may include the QoS rule (rule) or service (service) supported by the tag, and the QoS rule or service is equivalent to the QoS parameter. It should be understood that the QoS rule or service supported by the tag is usually at the service level, and the tag can send a registration request to the AMF through the gNB.

[0232] 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.

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

[0234] S1204. QoS rules are acquired between SMF and PCF.

[0235] Exemplarily, SMF sends a QoS request to PCF. Accordingly, PCF receives the QoS request from SMF. The QoS request is used to request the QoS rules supported by the tag. When the tag initiates registration, SMF can request PCF to provide QoS rules. Further, PCF sends QoS rules to SMF. Accordingly, SMF receives the QoS rules from PCF.

[0236] S1205. SMF sends QoS rules to gNB. Correspondingly, gNB receives QoS rules from SMF.

[0237] For the specific description of S1202 to S1205, please refer to the relevant description in the above S1101, which will not be repeated here. SMF can send QoS rules to gNB through AMF.

[0238] S1206. The gNB sends an RRC release message to the tag. Correspondingly, the tag receives the RRC release message from the gNB.

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

[0240] S1207. The tag sends identification information to the gNB. Correspondingly, the gNB receives the identification information from the tag.

[0241] When the tag initiates random access again, the tag 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.

[0242] S1208. The gNB sends an ACK message to the tag. Correspondingly, the tag receives the ACK message from the gNB.

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

[0244] S1209. The gNB sends a physical downlink control channel (PDCCH) to the tag. Correspondingly, the tag receives the PDCCH from the gNB.

[0245] Among them, PDCCH carries scheduling and other control information, such as transmission format, resource allocation, uplink scheduling permission, power control, and uplink retransmission information. After the tag accesses the network, the gNB can determine the corresponding QoS rules according to the identification information reported in S1208, and schedule services for the tag according to the QoS rules, and send them to the tag through PDCCH.

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

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

[0248] Fig.11 and Fig.12 The communication method shown implements 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.

[0249] 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).

[0250] The above mainly introduces the scheme provided by the present application. Accordingly, the present application also provides a communication device, which is used to implement 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 a 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 a chip system.

[0251] 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. Those skilled in the art should easily realize 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.

[0252] 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 module 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 function division. There may be other division methods in actual implementation.

[0253] Taking the communication device as the access network device or the terminal device in the above method embodiment as an example, Fig.13 Schematic diagram of a communication device provided in an embodiment of the present application. Fig.13 As shown, the communication device 1300 includes: a processing module 1301 and a transceiver module 1302. The processing module 1301 is used to perform the processing function of the access network device or the terminal device in the above method embodiment. The transceiver module 1302 is used to perform the transceiver function of the access network device or the terminal device in the above method embodiment.

[0254] 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.

[0255] 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.

[0256] In a possible design scheme, in the embodiment of the present application, the transceiver module 1302 may include a receiving module and a sending module ( Fig.13 The transceiver module is used to implement the sending function and the receiving function of the communication device 1300.

[0257] In a possible design solution, the communication device 1300 may further include a storage module ( Fig.13 (not shown in the figure), the storage module stores a program or instruction. When the processing module 1301 executes the program or instruction, the communication device 1300 can execute Figures 9 to 12 The function of the access network device or terminal device in any of the methods shown.

[0258] 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.

[0259] For example, Fig.14This 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 components or assemblies that can be set in the access network device or the terminal device. Fig.14 As shown, the communication device 1400 may include a processor 1401. In a possible design, 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, for example, via a communication bus.

[0260] Combine the following Fig.14 The components of the communication device 1400 are described in detail:

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

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

[0263] In a specific implementation, as an embodiment, the processor 1401 may include one or more CPUs, such as Fig.14 CPU0 and CPU1 are shown in FIG.

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

[0265] 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, which will not be repeated here.

[0266] In a possible design, the memory 1402 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices 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, optical disc storage (including compressed optical 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 may be integrated with the processor 1401, or may exist independently and communicate with the processor 1401 through the interface circuit ( Fig.14 1401) is coupled to the processor 1401, which is not specifically limited in the embodiment of the present application.

[0267] The transceiver 1403 is used for communication with other communication devices. For example, the communication device 1400 is a terminal device, and the transceiver 1403 can be used to communicate with a network device, or with another terminal device. For another example, the communication device 1400 is a network device, and the transceiver 1403 can be used to communicate with a terminal device, or with another network device.

[0268] In one possible design, transceiver 1403 may include a receiver and a transmitter ( Fig.14 The receiver is used to implement a receiving function, and the transmitter is used to implement a sending function.

[0269] In a possible design, the transceiver 1403 may be integrated with the processor 1401, or may exist independently and communicate with the processor 1401 through the interface circuit ( Fig.14 1401) is coupled to the processor 1401, which is not specifically limited in the embodiment of the present application.

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

[0271] In addition, the technical effects of the communication device 1400 can refer to the technical effects of the method described in the above method embodiment, which will not be repeated here.

[0272] The embodiment of the present application also 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.

[0273] The embodiment of the present application also provides a computer program product, which implements the functions of the above method embodiment when executed by a computer.

[0274] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. 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, computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more servers that can be integrated with a medium. 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)).

[0275] Those of ordinary skill 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 to be beyond the scope of this application.

[0276] Those skilled in the art can 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.

[0277] In the several embodiments provided in the present 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, 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.

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

[0279] 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 can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks.

[0280] 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 changes to the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" 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