Communication method and related apparatus
By obtaining the delay parameters of non-periodic services in the 5G system, determining the configuration cycle of transmission resources, and using the resources configured in the periodically, the problem that non-periodic services cannot meet the delay requirements is solved, and low-delay transmission is achieved.
Patent Information
- Application Number
- PCT/CN2024/081036
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-08
- Filing Date
- 2024-03-11
- Publication Date
- 2024-11-14
AI Technical Summary
In 5G mobile communication systems, non-periodic services cannot obtain semi-static scheduling, resulting in the inability to meet their transmission delay requirements because the wireless access network cannot provide temporary resource configuration.
By obtaining the delay parameters of non-periodic services, determining the configuration cycle of transmission resources, so that the access network equipment can use the resources configured in cycles to transmit, realizing semi-static scheduling, avoiding the delay caused by temporary resource allocation, and satisfying non-periodic services. low latency demand.
It realizes low-latency transmission of non-cyclical services in 5G systems, meets the demand for transmission delay of non-cyclical services, and avoids the delay caused by temporary resource allocation.
Smart Images

Figure CN2024081036_14112024_PF_FP_ABST
Abstract
Description
Communication method and related device
[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on May 8, 2023, with application number 202310512669.8 and application name “Communication Methods and Related Devices”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communications, and in particular to a communication method and related devices. Background Art
[0003] Currently, in some communication systems, such as fifth-generation (5G) mobile communication systems, for some periodic services, centralized network configuration (CNC) can be used to configure the 5G system with a transmission time window and flow period, enabling the radio access network (RAN) to periodically schedule resources used to transmit data packets for periodic services (for example, semi-static scheduling). This scheduling method eliminates the need for temporary allocation of scheduling resources and allows for faster data packet transmission, ensuring the low latency requirements of periodic services.
[0004] However, for some non-periodic services, RAN cannot provide semi-persistent scheduling and requires temporary resource allocation, which may not meet the transmission delay requirements of non-periodic services.
[0005] Summary of the Invention
[0006] The present application provides a communication method and related devices to ensure the transmission delay of non-periodic services.
[0007] In the first aspect, the present application provides a communication method, which includes: obtaining a delay parameter of a first service, wherein the delay parameter is related to a delay requirement, a packet delay budget (PDB) requirement or PDB, and the first service is a non-periodic service; based on the delay parameter, determining a configuration period of a transmission resource, and the transmission resource is used to transmit data packets of the first service.
[0008] For downlink transmission, the latency requirement is the time it takes for a packet to enter the user plane function (UPF) on the core network and exit the terminal. The PDB requirement is the time it takes for a packet to enter the UPF on the core network and exit the terminal. Specifically, the PDB requirement is the difference between the latency requirement and the first processing duration of the terminal. The PDB defines the upper limit on the possible delay of a packet between the terminal and the N6 termination point of the UPF.
[0009] In the present application, based on the delay parameters of the non-periodic service, the configuration period of the transmission resources of the non-periodic service is determined, so that the access network equipment does not need to temporarily configure resources every time it receives a non-periodic service, but can use the periodically configured transmission resources to transmit the received non-periodic service, thereby realizing semi-static scheduling of resources and avoiding the delay caused by temporarily configuring resources when the service arrives, thereby helping to meet the transmission delay requirements of the non-periodic service.
[0010] In one possible implementation, the method is applied to a time sensitive communication time synchronization function (TSCTSF), which can be executed by the TSCTSF, or by a component configured in the TSCTSF (such as a chip, a chip system, etc.), or by a logic module or software that can implement all or part of the TSCTSF function. This application does not limit this.
[0011] In this implementation, the delay parameter may be the delay requirement.
[0012] Optionally, obtaining the delay parameter of the first service includes: receiving a first request message from an application function (AF) or a network exposure function (NEF), wherein the first request message indicates the delay requirement, and the delay requirement is the sum of the PDB requirement and the time length for the terminal to process the data packet.
[0013] Optionally, the sum of the configuration period and the PDB requirement is less than or equal to the delay requirement, and the method further includes: determining the PDB requirement based on the delay requirement; and sending a second request message to a policy control function (PCF), wherein the second request message indicates the configuration period and the PDB requirement.
[0014] The PDB requirement is the difference between the delay requirement and the time it takes for the terminal to process a data packet.
[0015] Since the sum of the configuration period and the PDB requirement is less than the delay requirement of the first service, even if the access network device receives a data packet of the first service outside the configuration period, it can send the data packet through the terminal within the delay required by the first service, thereby meeting the low-latency transmission requirements of non-periodic services.
[0016] In another possible implementation, the method is applied to PCF and can be executed by PCF, or it can be executed by components configured in PCF (such as chips, chip systems, etc.), or it can be implemented by a logic module or software that can implement all or part of the PCF functions. This application does not limit this.
[0017] In this implementation, the delay parameter may be the PDB requirement.
[0018] Optionally, obtaining the delay parameter of the first service includes: receiving a first request message from one of the following network elements, where the first request message indicates a PDB requirement of the first service: TSCTSF, AF, NEF.
[0019] It should be understood that receiving the first request message from one of the following network elements includes: receiving the first information from the TSCTSF, receiving the first information from the AF, or receiving the first information from the NEF.
[0020] Optionally, obtaining the delay parameter of the first service includes: receiving a first request message from one of the following network elements, where the first request message indicates the delay requirement of the first service: AF, NEF.
[0021] It should be understood that receiving the first request message from one of the following network elements includes: receiving the first information from the AF, or receiving the first information from the NEF.
[0022] Optionally, the sum of the configuration period and the PDB is less than or equal to the PDB requirement, and the method further includes: determining the PDB based on the first request message; and sending first information to a session management function (SMF), wherein the first information includes the configuration period and the PDB.
[0023] Since the sum of the configuration period and the PDB is less than the PDB requirement of the first service, even if the access network device receives a data packet of the first service outside the configuration period, it can send the data packet to the terminal within the delay required by the first service, thereby meeting the low-latency transmission requirements of non-periodic services.
[0024] Optionally, the configuration period is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; the data network name (DNN) is a first value; the single network slice selection assistance information (S-NSSAI) is a second value; or the first request message does not include the period of the first service.
[0025] Among them, the first preset threshold and the second preset threshold are respectively a preset time length, and the two can be the same or different, for example, the first preset threshold is 4 milliseconds (ms) and the second preset threshold is 5ms; or, the first preset threshold and the second preset threshold are both 4ms.
[0026] The above-mentioned DNN and S-NSSAI may refer to the DNN and S-NSSAI corresponding to the protocol data unit (PDU) session, or may refer to the DNN or S-NSSAI in the request message from the AF as a specific DNN or S-NSSAI. The first value and the second value are respectively predefined parameter values, for example, the first value is 2 and the second value is 3.
[0027] Optionally, the method further includes: generating indication information, where the indication information is used to indicate that the first service is a non-periodic service; and sending the indication information.
[0028] Exemplarily, if the indication information is generated by the TSCTSF, the TSCTSF sends the indication information to the PCF; if the indication information is generated by the PCF, the PCF sends the indication information to the SMF.
[0029] Optionally, the indication information is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; DNN is a first value; S-NSSAI is a second value; or the first request message does not include the period of the first service.
[0030] For the description of the first preset threshold and the second preset threshold, please refer to the above description and will not be repeated here.
[0031] Optionally, the method further includes: obtaining scheduling status information from a radio access network (RAN), the scheduling status information including uplink and downlink ratios of the air interface, scheduling timing and other parameters; determining the configuration period of the transmission resources based on the delay parameter includes: determining the configuration period based on the delay parameter and the scheduling status information.
[0032] Optionally, the method further includes: receiving an expected value of the configuration period from the RAN; and determining the configuration period of the transmission resource based on the delay parameter includes: determining multiple values of the configuration period based on the delay parameter and the expected value; or determining a value range of the configuration period based on the delay parameter and the expected value.
[0033] Optionally, the method further includes: generating flow direction information; and sending the flow direction information. The flow direction information includes a flow direction, where the flow direction refers to a transmission direction of a data packet, including uplink transmission and downlink transmission, i.e., the flow direction refers to whether the data packet of the first service is an uplink transmission data packet or a downlink transmission data packet.
[0034] In another possible implementation, the method is applied to a RAN and may be executed by the RAN, or by a component configured in the RAN (such as a chip, a chip system, etc.), or by a logic module or software capable of implementing all or part of the RAN functions. This application is not limited to this.
[0035] In this implementation, the delay parameter may be the PDB authorized by the PCF for the first service based on the PDB requirement.
[0036] Optionally, the acquiring the delay parameter of the first service includes: receiving the PDB from the SMF.
[0037] Optionally, before determining the configuration period of the transmission resources based on the delay parameter, the method further includes: receiving indication information, the indication information indicating that the first service is a non-periodic service; and determining the access network AN PDB based on the indication information and the PDB.
[0038] Optionally, the method further includes: acquiring a data packet of the first service; and transmitting the data packet using the most recently configured transmission resources.
[0039] On the second aspect, the present application provides a communication method, which can be executed by PCF, or by components configured in PCF (such as chips, chip systems, etc.), or by logic modules or software that can implement all or part of the PCF functions. The present application does not limit this.
[0040] Exemplarily, the method includes: receiving a second request message, the second request message indicating a configuration period and a PDB requirement of a transmission resource, the transmission resource being used to transmit data packets of a first service, the first service being a non-periodic service; determining a PDB, the PDB being less than or equal to the PDB requirement; and sending a first message to the SMF, the first message indicating the PDB and the configuration period.
[0041] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving indication information, where the indication information is used to indicate that the first service is a non-periodic service.
[0042] Optionally, determining the PDB includes: determining the PDB based on at least one of the following: the PDB requirement, DNN or S-NSSAI.
[0043] In a third aspect, the present application provides a communication device, comprising a module or unit for executing the method in any possible implementation of any of the above aspects.
[0044] It should be understood that each module or unit can implement corresponding functions by executing computer programs.
[0045] In a fourth aspect, the present application provides another communication device, comprising a processor, wherein the processor is configured to execute the method described in any aspect and any possible implementation of any aspect.
[0046] The apparatus may further include a memory for storing instructions and data. The memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the method described in the above aspects may be implemented.
[0047] The apparatus may further include a communication interface, where the communication interface is used for the apparatus to communicate with other devices. Exemplarily, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces.
[0048] In a fifth aspect, the present application provides a chip system comprising at least one processor for supporting the implementation of the functions involved in any of the above aspects and any possible implementation of any aspect, for example, receiving or processing the data and / or information involved in the above method.
[0049] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.
[0050] The chip system can be composed of chips, or can include chips and other discrete devices.
[0051] In a sixth aspect, the present application provides a computer program product, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute a method in any possible implementation of any of the above aspects.
[0052] In the seventh aspect, the present application provides a computer-readable storage medium, which stores a computer program (also referred to as code, or instructions) which, when run on a computer, enables the computer to execute a method in any possible implementation of any of the above aspects.
[0053] In an eighth aspect, the present application provides a communication system, including the aforementioned TSCTSF and PCF.
[0054] Optionally, the communication system may further include other network elements that interact with the TSCTSF and / or PCF in the solution provided in this application.
[0055] It should be understood that the second to eighth aspects of the present application correspond to the technical solutions of the first aspect of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0056] FIG1 is a schematic diagram of a network architecture based on a service-oriented architecture according to an embodiment of the present application;
[0057] FIG2 is a schematic diagram of a network architecture based on a point-to-point interface provided in an embodiment of the present application;
[0058] FIG3 is a 5G QoS model based on quality of service flow provided in an embodiment of the present application;
[0059] FIG4 is a schematic diagram of a rule flow for mapping QoS flows to AN resources provided in an embodiment of the present application;
[0060] Figure 5 is a system architecture diagram of the intercommunication between 3GPP network and TSN;
[0061] FIG6 is a schematic diagram showing the relationship between latency requirements and PDB requirements;
[0062] FIG7 is a schematic diagram of burst arrival time;
[0063] Figure 8 is a schematic diagram of the network architecture of the newly added TSCTSF network element;
[0064] 9 to 12 are schematic flow charts of the communication method provided in the embodiments of the present application;
[0065] 13 and 14 are schematic block diagrams of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0066] The technical solution in this application will be described below with reference to the accompanying drawings.
[0067] The technical solution provided in this application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, world-wide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) mobile communication system or new radio access technology (NR), satellite communication system, etc.
[0068] The technical solution provided in this application can also be applied to future communication systems, such as the sixth generation (6G) mobile communication system, etc. This application does not limit this.
[0069] Before introducing the communication method provided in the embodiments of the present application, a brief introduction to the network elements involved in the present application is given:
[0070] 1. Terminal: may be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. In the embodiments described below, terminal device, terminal, and UE may be used interchangeably but have the same meaning.
[0071] The terminal device may be a device that provides voice / data connectivity to users, such as a handheld device or vehicle-mounted device with wireless connection function. At present, some examples of terminals may include: mobile phones, tablet computers, computers with wireless transceiver functions (such as laptops, PDAs, etc.), mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (PLMNs). terminal equipment in network, PLMN, etc.
[0072] Furthermore, terminal devices can also be end devices in the Internet of Things (IoT) system. IoT is a crucial component of future information technology development. Its primary technical feature is connecting objects to the Internet through communications technology, thereby enabling intelligent networks that interconnect humans and machines, and objects and things. IoT technology, for example, utilizes narrowband (NB) technology to achieve massive connectivity, deep coverage, and power-saving terminals.
[0073] In addition, terminal devices can also include sensors such as smart printers, train detectors, and gas stations. Their main functions include collecting data (part of the terminal devices), receiving control information and downlink data from network devices, and sending electromagnetic waves to transmit uplink data to network devices.
[0074] 2. Access network (AN) equipment: The access network can provide network access functions for authorized users in a specific area, and can use transmission tunnels of different qualities according to the user level, business requirements, etc. The access network can be an access network that adopts different access technologies. There are currently two types of wireless access technologies: 3rd Generation Partnership Project (3GPP) access technology and non-3GPP (non-3GPP) access technology. 3GPP access technology refers to access technology that complies with 3GPP standards and specifications. For example, the access network equipment in the 5G system is called the next generation node base station (gNB). Non-3GPP access technology refers to access technology that does not comply with 3GPP standards and specifications, for example, the air interface technology represented by the access point (AP) in wireless fidelity (Wi-Fi).
[0075] A radio access network (RAN) is a network that implements network access functions based on wireless communication technologies. The RAN manages radio resources, provides access services to terminal devices, and forwards control signals and user data between the terminal and the core network.
[0076] The radio access network equipment may include, for example, but is not limited to: a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved node B, or home node B, HNB), a baseband unit (BBU), an AP in a Wi-Fi system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc. It can also be a gNB or transmission point (TRP or TP) in a 5G (e.g., NR) system, one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or a network node constituting a gNB or transmission point, such as a BBU, or a distributed unit (DU), or a base station in a next-generation communication 6G system. This application does not limit the specific technology and specific device form adopted by the radio access network equipment. The radio access network equipment may include a gNB-centralized unit (CU) and a gNB-DU. The gNB-CU and gNB-DU are connected via the F1 interface. The CU and the core network are connected via the next generation (NG) interface. The gNB-DU includes physical layer (PHY), medium access control (MAC), and radio link control (RLC) layer functions to provide access services to relay devices attached to the access network equipment. The gNB-DU may connect to the gNB-CU via the F1 interface. The gNB-DU may also connect to a terminal device or the mobile-termination (MT) function of a mobile relay via the Uu interface.
[0077] The gNB-CU performs radio resource control (RRC) for all relay devices and terminal devices under its control. For example, it can store relay and terminal device contexts. The gNB-CU can connect to the DU function of other relay devices through the F1 interface.
[0078] The following is an introduction to the network elements of the core network.
[0079] 3. Application Function (AF) Network Element: This element provides application layer services to terminal devices. When providing services to terminal devices, the AF has requirements for QoS and charging policies, which it must notify the network of. The AF also requires feedback from the core network regarding application-related information.
[0080] 4. Policy Control Function (PCF) Network Element: This element, also referred to as PCF, is responsible for generating and managing user, session, and quality of service (QoS) flow processing policies. It supports a unified policy framework to manage network behavior, provides policy rules for network entities to implement, and accesses subscription information from a unified data repository (UDR).
[0081] 5. Session Management Function (SMF) Network Element: This element is often referred to as SMF. It is primarily used for user plane function (UPF) network element selection and reselection, Internet Protocol (IP) address allocation, session establishment, modification, and release, and quality of service (QoS) control.
[0082] 6. Access and Mobility Management Function (AMF) Network Element: This element is referred to as AMF. It is responsible for performing registration, connection, reachability, and mobility management. It provides a session management message transmission channel for the UE and SMF, and provides authentication and authorization for user access. It is the access point for the terminal and the wireless core network control plane.
[0083] 7. Unified Data Management (UDM) Element: This element is referred to as UDM. It manages user identification, subscription data, authentication data, and user registration with service network elements (e.g., the AMF and SMF currently providing services to the terminal). If a user switches to a different AMF, the UDM will send a deregistration message to the old AMF, requesting it to delete user-related information.
[0084] 8. User Plane Function (UPF) Network Element: This element is often referred to as the UPF. It is responsible for forwarding and receiving user data from terminal devices. It receives user data from the data network and transmits it to the terminal device via the access network equipment. The UPF network element also receives user data from the terminal device via the access network equipment and forwards it to the data network. The transmission resources and scheduling functions provided by the UPF network element to the terminal device are managed and controlled by the SMF network element.
[0085] 9. Network Exposure Function (NEF) Network Element: This element can be referred to as NEF for short. It is mainly used to support the exposure of capabilities and events.
[0086] 10. Data network (DN): A data network that provides data transmission services to users, such as IP Multimedia Service (IMS) and the internet. A UE accesses a data network through a protocol data unit (PDU) session established between the UE and the DN.
[0087] To facilitate understanding of the embodiments of the present application, the 5G network architecture applicable to the embodiments of the present application will be described in detail below with reference to Figures 1 and 2.
[0088] Figure 1 is a schematic diagram of a network architecture based on a service-oriented architecture according to an embodiment of the present application. As shown in Figure 1, the 5G network architecture may include three parts: the terminal part, the data network (DN), and the operator network part.
[0089] Among them, the operator network may include one or more of the following network elements: authentication server function (AUSF) network element, NEF network element, PCF network element, UDM network element, network repository function (NRF) network element, AF network element, AMF network element, SMF network element, AN network element, UPF network element, and network slice selection function (NSSF) network element, etc. In the above-mentioned operator network, the part other than the wireless access network part can be called the core network part. In the network shown in Figure 1, each network element can communicate based on a service-based interface, among which Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nusf, Namf, and Npcf in Figure 1 are service-based interfaces. It should be understood that the functions of some network elements can refer to the description in the above network element introduction, and the specific ones can refer to known technologies, which will not be repeated here.
[0090] Figure 2 is a schematic diagram of a network architecture based on a point-to-point interface provided by an embodiment of the present application. The network elements included in the network shown in Figure 2 and their related descriptions can be referred to the description in Figure 1. The network architecture shown in Figure 2 differs from that in Figure 1 in that the interfaces between the network elements in the network architecture shown in Figure 2 are point-to-point interfaces, rather than service-based interfaces.
[0091] It should be understood that FIG1 and FIG2 are merely schematic diagrams, and the network architecture may further include other network elements, such as TSCTSF, which are not shown in FIG1 and FIG2.
[0092] Currently, in communication systems, such as the 5G system (5GS), a 5G QoS model based on quality of service (QoS) flows has been proposed to ensure end-to-end service quality (QoS quality) (as shown in Figure 3). This 5G QoS model supports both guaranteed bit rate QoS flows (GBR QoS flows) and non-GBR QoS flows. Among them, whether a QoS flow is "GBR" or "Non-GBR" depends on its QoS configuration. The QoS configuration of a QoS flow includes the following parameters: 1. The QoS configuration of each QoS flow will include the QoS parameters: 5QI, ARP; 2. The QoS configuration of each Non-GBR QoS flow may also include the parameter: reflective QoS attribute (RQA); 3. The QoS configuration of each GBR QoS flow will also include the parameters: guaranteed flow bit rate (GFBR) and maximum flow bit rate (MFBR); 4. The QoS configuration of each GBR QoS flow may also include: indication control and maximum packet loss rate.
[0093] A UE can establish one or more PDU sessions with the 5G network, and one or more QoS flows can be established in each PDU session. Each QoS flow is identified by a QoS flow identifier (QFI). In 5GS, QoS flows are controlled by the SMF, which can be pre-configured or established and modified through PDU sessions.
[0094] The characteristics of a QoS flow consist of the following three parts:
[0095] 1. QoS configuration (profile) on the AN side: The configuration is provided to the AN by the SMF through the N2 interface, or is pre-configured in the AN.
[0096] It should be noted that the characteristic information of a QoS flow sent by the SMF to the AN is called a "QoS profile", where the characteristic information of the QoS flow includes the content shown in the following Table 1:
[0097] Table 1
[0098] 2. QoS rules on the UE side: They can be provided to the UE by the SMF through N1 (for example, explicitly configured to the UE through signaling in the PDU session establishment / modification process), or derived by the UE through the reflective QoS mechanism.
[0099] 3. Uplink and downlink packet detection rule(s), PDR(s) rules on the UPF side: PDR(s) are provided to UPF by SMF through the N4 interface.
[0100] In the NR system, the granularity of QoS is related to the protocol layer: IP flows at the IP layer, QoS flows at the NAS layer, and data radio bearers (DRBs) at the AS layer. At the NAS layer, IP flows are mapped to QoS flows using QoS rules. At the AS layer, QoS flows are mapped to DRBs. The protocol that completes the mapping of QoS flows to DRBs at the AS layer is the Service Data Adaptation Protocol (SDAP). As shown in Figure 4, for uplink data, the UE matches data packets according to QoS rules, and the packets are transmitted upstream from the matching QoS flows and their corresponding AN channels. For downlink data, the UPF matches data packets according to the PDR, and the packets are transmitted downstream from the matching QoS flows and their corresponding AN channels. If a data packet does not match any QoS rule or PDR, it will be discarded by the UE or UPF.
[0101] For example, the UE performs classification and marking of uplink user plane data services by associating uplink data with corresponding QoS flows based on QoS rules. QoS rules have the following characteristics: 1. A QoS rule contains: the QFI of the associated QoS flow, the packet filter set (a filter list), and the priority; 2. A QoS flow can have multiple QoS rules; 3. Each PDU session must be configured with a default QoS rule, which is associated with a QoS flow.
[0102] 5QI is a scalar that indexes a 5G QoS feature. Some 5QIs are standardized, some are pre-configured, and some are dynamically defined. For standardized 5QIs, simply including the 5QI in signaling on the NG interface suffices. For dynamically defined 5QIs, the parameters listed in Table 2 below must be explicitly configured in signaling.
[0103] Table 2
[0104] The binding mechanism is the process of associating a service data flow (defined in PCC rules via a service data flow (SDF) template) with a QoS flow that is considered to transport the service data flow.
[0105] Since PCC rules are based on the SDF granularity, and the 5G QoS model is based on the QoS Flow granularity, that is, the RAN performs scheduling based on the QoS Flow granularity, it is necessary to map the SDF to the QoS flow for QoS control.
[0106] The binding mechanism consists of the following three steps:
[0107] 1. Session binding: Make a one-to-one correspondence between AF sessions and PDU sessions.
[0108] 2. PCC rule authorization: This is performed by the PCF to authorize PCC rules and assign QoS parameters to them.
[0109] 3. QoS flow binding: This process maps PCC rules to QoS flows. This process is performed by the SMF, associating PCC rules with QoS flows within a PDU session. Binding parameters include: 5QI; ARP; QNC; priority; average window; and maximum data burst capacity. PCC rules with different attributes are bound to different QoS flows.
[0110] Specifically, when the PCF provides the PCC rule, the SMF shall evaluate whether there is a QoS flow with the same QoS parameters as the binding parameters. If there is no such QoS flow, the SMF shall use the parameters in the PCC rule to derive the QoS parameters of the new QoS flow. The PCC rule shall be bound to the QoS flow, and then a new QoS flow shall be established according to the QoS parameters; if there is a QoS flow with the same QoS parameters as the binding parameters, the SMF shall bind the PCC rule to the QoS flow.
[0111] In the 5G system, for some periodic services, a centralized network configuration (CNC) is used to configure a transmission time window and a flow period for the 5G system, thereby enabling the RAN to periodically schedule resources for transmitting data packets of periodic services (e.g., semi-persistent scheduling).
[0112] The following describes the semi-scheduling method for periodic services in conjunction with the architecture shown in FIG5 .
[0113] Figure 5 shows a system architecture diagram for intercommunication between the 3rd Generation Partnership Project (3GPP) network and time-sensitive networking (TSN). As shown in Figure 5, the 3GPP 5GS and TSN translator (TT) function as a logical TSN bridge. The 5GS exchanges information with nodes in the TSN network through the control plane TT (AF). The exchanged information includes: 5GS bridge capability information, TSN configuration information, time scheduling information for TSN input and output ports, time synchronization information, etc. The TSN translator on the UE side can be called the device-side TSN translator (DS-TT) and may be located inside or outside the UE. The TSN translator on the UPF side can be called the network-side TSN translator (NW-TT) and is located inside the UPF.
[0114] For example, the 5GS as a whole acts as a TSN bridge. The CNC configures the sending time window and flow period for each TSN bridge based on the information reported by the 5GS bridge and other bridges to ensure end-to-end deterministic latency.
[0115] The following example illustrates user-plane packet processing: After a packet is transmitted from the TSN system to the NW-TT, it is sent to the DS-TT. The DS-TT then sends the packet within a preconfigured time window (i.e., gating scheduling parameters) configured by the CNC. To ensure timely delivery, the packet must arrive at the DS-TT before the preset send time and be buffered at the DS-TT until the send time window is reached.
[0116] As shown in Figure 6, for specific messages with deterministic latency requirements, 5GS needs to determine the corresponding PDB based on the latency requirements of the message and ensure that the transmission time of the message between the UE and the UPF is no longer than the PDB. In other words, the message will arrive at the DS-TT in advance so that it can catch up with the sending time window configured by the CNC. Among them, the latency requirement refers to the end-to-end latency requirement. For example, the latency requirement refers to the time required for the message to enter the core network and be sent from the terminal. The PDB is determined by the PCF based on the PDB requirement, or as an example, the PDB requirement refers to the time required for the message to enter the core network and reach the terminal. Compared with the above latency requirement, the PDB requirement does not include the processing time of the terminal for the message. In other words, latency requirement = PDB requirement + terminal processing time (which can be called UE-DS-TT residence time).
[0117] Since 3GPP and TSN are connected and adopt a black box model, the CNC can configure the time of arrival at and departure from the 5GC according to the flow granularity. The uncertainty caused by air interface transmission and wired transmission between the UE and the UPF is eliminated by caching at the endpoint TT. For example, the TSN AF determines the time when the TSN flow arrives at the 5GS entrance based on the scheduling information of the TSN flow obtained from the CNC. The time of the flow entrance can be the time when the downlink TSN flow arrives at the NW-TT entrance, such as the downlink (DL) burst arrival time (burst arrival time) in Figure 7, or the time when the uplink TSN flow arrives at the DS-TT entrance. The TSN AF includes the flow scheduling information in the time sensitive communication assistance container (TSCAC) through the PCF and provides it to the SMF. Based on the received information, the SMF further determines the time to arrive at the NG-RAN in the downlink direction, such as the time sensitive communication assistance information (TSCAI) burst arrival time in Figure 7, or the time when the uplink direction is sent from the UE, and provides it to the RAN as TSCAI information so that the RAN node can reserve resources in advance.
[0118] The downlink TSCAI burst arrival time = DL burst arrival time + DL CN PDB.
[0119] TSCAI includes the following information: 1. Flow direction: indicates whether the TSC flow is in the uplink or downlink direction; 2. Period: refers to the interval between the start times of two adjacent bursts; 3. Burst arrival time: can be the burst arrival time in the downlink or uplink direction. The downlink direction refers to the time when the burst arrives at the RAN node entrance, and the uplink direction refers to the time when the burst arrives at the UE exit.
[0120] It should be understood that SMF will bind a specific service to a QoS flow, that is, there is a corresponding relationship between the QoS flow and the service data flow. For delay-sensitive services, it is generally believed that there is a one-to-one correspondence between the QoS flow and the service data flow.
[0121] However, for non-TSN delay-sensitive service flows, also known as time-sensitive communication (TSC) service flows, TSC services in non-TSN scenarios are enabled by adding a TSCTSF. The network architecture of the newly added TSCTSF network element is shown in Figure 8. The functions of TSCTSF include:
[0122] 1. Associate the time synchronization service request from AF to the AF session;
[0123] 2. Interact with DS-TT / NW-TT PMIC / BMIC to manage and control DS-TT / NW-TT;
[0124] 3. Check the availability of 5GS bridge or 5GS node information reported by PCF;
[0125] 4. Create a TSC assistance container based on the service type parameters provided by the AF / NEF and provide it to the PCF;
[0126] For example, the AF sends a delay requirement (requested delay) to the TSCTSF, and the TSCTSF subtracts the terminal processing time from the delay requirement to obtain a PDB requirement (requested PDB), and sends the requested PDB to the PCF.
[0127] 5. Determine the 5GS bridge delay based on the UE-DS-TT dwell time and provide it to the PCF.
[0128] In summary, the aforementioned periodic services facilitate periodic scheduling (such as semi-persistent scheduling) by RAN nodes. This scheduling approach eliminates the need for temporary allocation of scheduling resources, enabling faster data packet transmission and ensuring low latency for periodic services. However, for non-periodic services, the RAN cannot provide semi-persistent scheduling and requires temporary resource allocation, potentially failing to meet the latency requirements of some non-periodic services.
[0129] In view of this, an embodiment of the present application provides a communication method and related devices, in which the configuration period of resources for transmitting non-periodic services is determined based on the delay parameters of non-periodic services, so that the access network equipment that receives non-periodic services no longer needs to temporarily configure resources for each non-periodic service received, but can use periodically configured transmission resources to transmit the received non-periodic services, thereby realizing semi-static scheduling of resources, avoiding the delay caused by the service reaching the temporarily configured resources, and thus helping to meet the transmission delay requirements of non-periodic services.
[0130] Before introducing the method provided in the embodiments of the present application, the following points are explained.
[0131] First, in the embodiments of this application, prefixes such as "first" and "second" are used solely to distinguish between different items belonging to the same category and do not constrain the order, size, or quantity of the items. For example, a "first request message" and a "second request message" are simply different messages; there is no size or priority relationship between them.
[0132] Second, "sending" and "receiving" in the embodiments of the present application indicate the direction of signal transmission. For example, "sending a second request message to the PCF" can be understood as the destination end of the request message being the PCF, which can include direct sending, as well as indirect sending by other units or modules. "Receiving a first request message from the AF or NEF" can be understood as the source end of the request message being the AF or NEF, which can include receiving it directly from the AF or NE, as well as receiving it indirectly from the AF or NE through other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface.
[0133] In other words, sending and receiving can be carried out between network elements, for example, between TSCTSF and PCF; it can also be carried out within a network element, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, wiring or interface.
[0134] It is understood that before information is sent from the source to the destination, it may undergo necessary processing, such as encoding and modulation. After receiving the information from the source, the destination may also perform corresponding processing, such as decoding and demodulation, to interpret the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated here.
[0135] Third, in the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship, but does not exclude the situation where the previous and next associated objects are in an "and" relationship. The specific meaning can be understood in conjunction with the context. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, c can be single or multiple.
[0136] The communication method provided in the embodiment of the present application is described in detail below in conjunction with Figure 9. The method can be applied to the network architecture shown in Figure 1 or Figure 2, but the embodiment of the present application is not limited thereto.
[0137] Figure 9 is a schematic flow chart of a communication method 900 provided in an embodiment of the present application. It should be understood that this method can be executed by a TSCTSF, PCF, or RAN, or by a chip, chip system, or processor supporting the TSCTSF, PCF, or RAN, and this application is not limited thereto. As shown in Figure 9, method 900 includes steps S901 and S902. The steps shown in Figure 9 are described in detail below.
[0138] S901: Obtain a delay parameter of a first service.
[0139] The first service is a non-periodic service. For example, the first service may be a distributed energy service or a microgrid service.
[0140] The delay parameter is related to the delay requirement, the PDB requirement, or the PDB. In other words, the delay parameter includes the delay requirement, the PDB requirement, or the PDB.
[0141] For the description of latency requirements, PDB requirements and PDB, please refer to the description in FIG6 above, which will not be repeated here.
[0142] S902: Determine a configuration period of transmission resources based on the delay parameter.
[0143] The transmission resource is used to transmit a data packet of the first service. The data packet of the first service can also be referred to as a data flow of the first service or a service flow of the first service. It should be understood that the different names are due to different protocol sides, but the essence is the same, so this application does not limit this.
[0144] It should be understood that the configuration period refers to the period for configuring transmission resources. For example, the transmission resources may be configured once at intervals of time T, where T is the above-mentioned configuration period.
[0145] Exemplarily, the delay parameter indicates that the delay requirement of the first service is 4 ms, and the determined configuration period should be no greater than 4 ms, for example, may be 1 ms.
[0146] In an embodiment of the present application, the configuration period of the transmission resources of the non-periodic service is determined based on the delay parameters of the non-periodic service, so that the access network device no longer needs to temporarily configure resources for each non-periodic service received, but can transmit the non-periodic service on the transmission resources periodically configured based on the configuration period, thereby ensuring the transmission delay of the non-periodic service.
[0147] The following describes the method of the embodiment of the present application in detail by taking the method 900 applied to TSCTSF, PCF or RAN as an example.
[0148] In example 1, the method 900 is applied to TSCTSF, and the delay parameter is the delay requirement.
[0149] Optionally, the acquiring of the delay parameter of the first service includes: the TSCTSF receiving a first request message from the AF or the NEF, where the first request message indicates a requested delay.
[0150] Optionally, the method 900 further includes: the TSCTSF determining a requested PDB based on the latency requirement, where the sum of the configuration period and the PDB requirement is less than or equal to the latency requirement; and sending a second request message to the PCF, where the second request message indicates the configuration period and the PDB requirement. Correspondingly, the PCF receives the second request message, determines a PDB, where the PDB is less than or equal to the PDB requirement; and sends a first message to the SMF, where the first message includes the PDB and the configuration period.
[0151] It should be understood that the requested PDB determined by the TSCTSF is the difference between the requested delay and the UE-DS-TT residence time, and the sum of the requested PDB determined by the TSCTSF and the configuration period should not be greater than the requested delay.
[0152] For example, in 5GS, the delay requirement in this application can be expressed as requested 5GS delay, the PDB requirement can be expressed as requested 5GS PDB, and the configuration period can be expressed as periodicity.
[0153] In Example 2, the method 900 is applied to PCF, and the above delay parameter is a PDB requirement.
[0154] In a possible implementation, the obtaining of the delay parameter of the first service may include: the PCF receiving a first request message from one of the following network elements, where the first request message indicates a PDB requirement of the first service: TSCTSF, AF, or NEF.
[0155] Exemplarily, obtaining the delay parameter of the first service includes: the PCF receiving a first request message from the TSCTSF; the PCF receiving a first request message from the AF; or the PCF receiving a first request message from the NEF, where the first request message indicates a PDB requirement.
[0156] Optionally, the method 900 further includes: the PCF determines the PDB based on the PDB requirement, and the sum of the configuration period and the PDB is less than or equal to the PDB requirement; and sends first information to the SMF, where the first information indicates the configuration period and the PDB.
[0157] In another possible implementation, the obtaining of the delay parameter of the first service may include: the PCF receiving a first request message from one of the following network elements, where the first request message indicates the delay requirement of the first service: AF, NEF.
[0158] Exemplarily, obtaining the delay parameter of the first service includes: the PCF receiving a first request message from the AF; or the PCF receiving a first request message from the NEF, where the first request message indicates a delay requirement.
[0159] Optionally, the method 900 further includes: the PCF determines the PDB based on the latency requirement, and the sum of the configuration period and the PDB is less than or equal to the PDB requirement; and sends first information to the SMF, where the first information indicates the configuration period and the PDB.
[0160] It should be understood that the PDB requirement here is the difference between the received delay requirement and the time length for the terminal to process the data packet.
[0161] In combination with the above-mentioned example 1 and example 2, when the method 900 is applied to the TSCTSF or PCF, the method 900 may further include: obtaining scheduling status information from the RAN, where the scheduling status information includes parameters such as uplink and downlink ratio of the air interface and scheduling timing.
[0162] Exemplarily, the determining of the configuration period of the transmission resources based on the delay parameter includes: determining the configuration period based on the delay parameter and scheduling status information.
[0163] In combination with the above-mentioned Example 1 and Example 2, when method 900 is applied to TSCTSF or PCF, the method 900 further includes: receiving an expected value of the configuration period from the RAN; and determining multiple values or value ranges of the configuration period based on the delay parameter and the expected value.
[0164] It should be understood that the expected value may be a value of a configuration period of transmission resources for transmitting the first service determined by the RAN based on the current resource configuration.
[0165] That is, the TSCTSF or PCF can determine multiple configuration cycles, or determine a value range of a configuration cycle based on the delay parameter and the expected value, so that the RAN can determine an appropriate configuration cycle from the multiple configuration cycles or the value range of the configuration cycle.
[0166] In combination with the above-mentioned Example 1 and Example 2, when method 900 is applied to TSCTSF or PCF, the above-mentioned configuration period is determined when at least one of the following items is met: the latency requirement is less than or equal to the first preset threshold; the PDB requirement is less than or equal to the second preset threshold; the data network name (DNN) is the first value; the single network slice selection assistance information (S-NSSAI) is the second value; or, the first request message does not include the period of the first service.
[0167] Among them, the first preset threshold and the second preset threshold are respectively a preset time length, and the two can be the same or different, for example, the first preset threshold is 4 milliseconds (ms) and the second preset threshold is 5ms; or, the first preset threshold and the second preset threshold are both 4ms.
[0168] The DNN and S-NSSAI may refer to the DNN and S-NSSAI corresponding to the PDU session, or may refer to the DNN or S-NSSAI in the request message from the AF as a specific DNN or S-NSSAI. For example, when the first value is 1, the TSCTSF or PCF needs to determine the configuration period, and when the second value is 3, the TSCTSF or PCF needs to determine the configuration period.
[0169] For example, if the first request message does not include the period of the first service, it can be determined that the first service is not a periodic service. Therefore, based on this, the TSCTSF or PCF can determine that it is necessary to determine the configuration period corresponding to the first service.
[0170] In combination with the above-mentioned Example 1 and Example 2, when the method 900 is applied to the TSCTSF or PCF, the method 900 further includes: generating indication information, where the indication information is used to indicate that the first service is a non-periodic service; and sending the indication information.
[0171] Exemplarily, when the method 900 is executed by the TSCTSF, the TSCTSF sends indication information to the PCF, and correspondingly, the PCF receives the indication information.
[0172] Optionally, the PCF determining the PDB may include: determining the PDB based on the received indication information; or determining the PDB based on at least one of the following: PDB requirement, DNN, or S-NSSAI.
[0173] It should be understood that the description of DNN and S-NSSAI can refer to the previous description and will not be repeated here.
[0174] It should also be understood that, if the PCF receives the indication information, the determined PDB should be less than or equal to the above PDB requirement. If the PCF does not receive the indication information, the PCF may determine the PDB based on DNN or S-NSSAI, etc.
[0175] Exemplarily, when the method 900 is executed by the PCF, the PCF sends indication information to the SMF, and correspondingly, the SMF receives the indication information.
[0176] Exemplarily, the above-mentioned indication information can be determined when at least one of the following items is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; the DNN is a first value; the S-NSSAI is a second value; or the first request message does not include the period of the first service.
[0177] For the description of the first preset threshold, the second preset threshold, DNN, S-NSSAI, etc., please refer to the relevant description above and will not be repeated here.
[0178] It should be understood that the content indicated by the above indication information and the content indicated by the second request message can be indicated by the same information; or, they can be indicated by different information respectively.
[0179] Example 3: The method 900 is applied to a RAN, and the above-mentioned delay parameter is a PDB authorized by the PCF for the first service based on a PDB requirement.
[0180] Exemplarily, the obtaining of the delay parameter of the first service includes: receiving a PDB from a PCF.
[0181] Optionally, before determining the configuration period of the transmission resource based on the delay parameter, the method 900 further includes: receiving indication information from the SMF; determining the configuration period of the transmission resource based on the delay parameter, including: determining the configuration period based on the delay parameter and the indication information.
[0182] It should be understood that the RAN may not generate TSCAI, but may perform semi-persistent scheduling (SPS), configured grant (CG) or dynamic grant (DG) according to the period.
[0183] Optionally, the method 900 further includes: the RAN obtains a data packet, where the data packet is a data packet of the first service; and the RAN transmits the data packet using the most recently configured transmission resources.
[0184] The following describes the communication method provided by this application based on the embodiment shown in Figure 9, taking the execution entities as TSCTSF, PCF, and RAN as examples, and in conjunction with Figures 10 to 12. The content already described in the embodiment shown in Figure 9 is not repeated here. The flowcharts shown in Figures 10 to 12 illustrate the method from the perspective of network element interaction.
[0185] Figure 10 is a schematic flow chart of another communication method 1000 provided by an embodiment of the present application. As shown in Figure 10, the method 1000 may include steps S1001 to S1012. The steps shown in Figure 10 are described in detail below.
[0186] S1001: The terminal establishes a PDU session.
[0187] The process of establishing a PDU session will not be described in detail here.
[0188] S1002: The AF / NEF sends a first request message to the TSCTSF. Correspondingly, the TSCTSF receives the first request message.
[0189] The first request message indicates the delay requirement of the first service, which is a non-periodic service. For the description of the delay requirement, please refer to the relevant description in Figure 6 above, which will not be repeated here.
[0190] S1003: TSCTSF determines the configuration period and PDB requirement of transmission resources based on the latency requirement.
[0191] The sum of the PDB requirement and the configured period must be less than or equal to the latency requirement minus the UE-DS-TT residence time. The UE-DS-TT residence time is the time required to forward data packets within the UE and the DS-TT. Specifically, it is the time required to forward data packets between the UE ingress and the DS-TT port in the downlink direction, or between the DS-TT port and the UE egress in the uplink direction.
[0192] For the description of the TSCTSF generation configuration period and the description of the transmission resources, please refer to the relevant description in the above method 900, which will not be repeated here.
[0193] It should be understood that the TSCTSF in the above S1003 may also determine only the configuration period of the transmission resources based on the delay requirement, without determining the PDB requirement.
[0194] Optionally, the TSCTSF may subscribe to scheduling status information from the RAN through the PCF or SMF, and determine the requested PDB and the configuration period based on the scheduling status information and the latency requirement; alternatively, when the TSCTSF is based on the period of the RAN feedback tendency (i.e., the expected value of the above-mentioned configuration period), the TSCTSF uses the period of the RAN feedback tendency as a reference for determining the requested PDB and the configuration period. For example, the TSCTSF generates one or more periods (i.e., multiple values of the above-mentioned configuration period) or a periodicity range (i.e., the value range of the above-mentioned configuration period) based on the period of the RAN feedback tendency and the latency requirement for selection by the RAN.
[0195] S1004: The TSCTSF sends a second request message to the PCF. Correspondingly, the PCF receives the second request message.
[0196] The second request message indicates PDB requirements and configuration period.
[0197] S1005: The TSCTSF generates indication information, where the indication information indicates that the first service is a non-periodic service.
[0198] S1006, TSCTSF sends the indication information to PCF.
[0199] It should be understood that S1005 and S1006 are optional steps. When S1005 is not executed, S1006 does not need to be executed. When S1005 is executed, S1006 may or may not be executed. This is not limited here. Whether S1005 is executed can be determined based on the conditions for generating indication information shown in method 1000 above. For example, if the latency requirement is greater than the first preset threshold, or if the first request message indicates a configuration period, S1005 may not be executed.
[0200] In one design, the TSCTSF may further generate flow direction information and send the information to the PCF, which then sends the information to the SMF. The flow direction information refers to information carrying a flow direction, which refers to the transmission direction of a data packet, including uplink transmission and downlink transmission. That is, the flow direction indicates whether the data packet of the first service is an uplink transmission data packet or a downlink transmission data packet.
[0201] S1007: The PCF determines the PDB, which is smaller than or equal to the PDB requirement.
[0202] For the relevant description of PCF determining PDB, please refer to the description in method 900, which will not be repeated here.
[0203] S1008: PCF sends the PDB and configuration cycle to SMF. Correspondingly, SMF receives the PDB and configuration cycle.
[0204] It should be understood that the PDB and the configuration cycle may be indicated by the same information, such as the first information in method 900 .
[0205] Optionally, upon receiving the instruction information, the PCF may continue to execute S1009, where the PCF sends the instruction information to the SMF. Correspondingly, the SMF receives the instruction information. It is understandable that upon receiving the instruction information, the PCF may not execute S1009.
[0206] S1010: The SMF sends a PDB and a configuration cycle to the RAN. Correspondingly, the RAN receives the PDB and the configuration cycle.
[0207] As above, the PDB and the configuration period may be indicated by the same information, for example, the first information.
[0208] Optionally, when the SMF receives the indication information from the PCF, it may continue to execute S1011, and the SMF sends the indication information to the RAN.
[0209] Optionally, upon receiving the indication, the SMF may dynamically adjust the received configuration period and send the adjusted configuration period to the RAN. For example, if the SMF previously received the cumulative rate ratio from the UPF, the SMF uses the cumulative rate ratio to correct the period in the TSCAC and sets the TSCAI period to the corrected value.
[0210] Optionally, if the SMF receives flow direction information, it can instruct the terminal or UPF to periodically generate dummy data packets based on the flow direction carried in the flow direction information. For example, if no service data packet is received within the corresponding period, a dummy data packet is generated, and if a service data packet is received within the corresponding period, the service data packet is delivered.
[0211] S1012: The RAN configures transmission resources based on the configuration period, and determines the AN PDB based on the PDB.
[0212] For the description of AN PDB, please refer to the description of the prior art and will not be repeated here.
[0213] Exemplarily, when the RAN obtains the data packet of the first service, it transmits the data packet using the most recently configured transmission resources.
[0214] Optionally, after receiving the indication information, if the RAN does not receive the data packet within the corresponding configuration period, it does not consider the packet lost; or, if the data packet is received in advance, it does not consider the packet lost even if the buffering time exceeds the PDB.
[0215] It should be noted that the indication information in method 1000 is not necessarily transparently transmitted when forwarded between network elements. For example, the indication information sent by the PCF to the SMF includes aperiodic indication 1, indicating that the SDF is an aperiodic service, and the indication information sent by the SMF to the RAN includes aperiodic indication 2, indicating that the QoS Flow is an aperiodic service.
[0216] In this embodiment of the present application, the TSCTSF determines the configuration period of the transmission resources for the first service based on the latency parameters of the first service. This allows the RAN to use periodically configured transmission resources to transmit received non-periodic services, rather than temporarily configuring resources each time a non-periodic service is received. This implements semi-static resource scheduling, avoids the delay caused by temporarily configuring resources upon service arrival, and thus helps meet the transmission latency requirements of non-periodic services. Secondly, because the sum of the configuration period and the PDB requirement is less than the latency requirement of the first service, even if the RAN receives a data packet for the first service outside of the configuration period, the data packet can be buffered on the air interface for a maximum of one period and can be transmitted within the required PDB time, thus meeting the low-latency transmission requirements of non-periodic services.
[0217] FIG11 is a schematic flow chart of another communication method 1100 provided in an embodiment of the present application. As shown in FIG11 , the method 1100 may include steps S1101 to S1109. Each step shown in FIG11 is described in detail below.
[0218] S1101: The terminal establishes a PDU session. This process is the same as S1001 above.
[0219] S1102: The AF / NEF / TSCTSF sends a first request message to the PCF. Correspondingly, the PCF receives the first request message.
[0220] The first request message indicates a delay requirement of the first service or a PDB requirement of the first service.
[0221] S1103: The PCF determines the configuration period and PDB of the transmission resources based on the first request message.
[0222] For the description of the PCF generation configuration period and the configuration period, please refer to the relevant description in the above method 900, which will not be repeated here.
[0223] Exemplarily, the first request message indicates a delay requirement of the first service, and the sum of the configuration period and the PDB is less than or equal to the delay requirement and the time for the terminal to process the data packet.
[0224] Exemplarily, the first request message indicates a PDB requirement of the first service, and the sum of the configuration period and the PDB is less than or equal to the PDB requirement.
[0225] It should be understood that the configuration period determined by the PCF may be smaller than the PDB or AN PDB. With this design, scheduling according to the configuration period will not cause the service transmission time to exceed the PDB or AN PDB.
[0226] Optionally, the PCF may subscribe to scheduling status information from the RAN through the PCF or SMF, and determine the requested PDB and the configuration period (periodicity) based on the scheduling status information and the latency requirement; alternatively, when the PCF is based on the period of the RAN feedback tendency (i.e., the expected value of the above-mentioned configuration period), the PCF uses the period of the RAN feedback tendency as a reference for determining the requested PDB and the configuration period. For example, the TSCTSF generates multiple periods (i.e., multiple values of the above-mentioned configuration period) or a period range (i.e., the value range of the above-mentioned configuration period) based on the period of the RAN feedback tendency and the latency requirement for selection by the RAN.
[0227] S1104: PCF sends the PDB and configuration cycle to SMF. Correspondingly, SMF receives the PDB and configuration cycle.
[0228] It should be understood that the PDB and the configuration cycle can be indicated by the same information, for example, the first information in the above method 900.
[0229] S1105: The PCF generates indication information, where the indication information indicates that the first service is a non-periodic service.
[0230] S1106: The PCF sends the indication information to the SMF, and the SMF receives the indication information accordingly.
[0231] It should be understood that S1105 and S1106 are optional steps. If S1105 is not executed, S1106 need not be executed. If S1005 is executed, S1106 may or may not be executed. This is not limited here. Regarding the description of whether S1105 is executed, please refer to the description of S1005 in method 1000 and will not be repeated here.
[0232] In one design, the PCF may also generate flow direction information and send the information to the SMF. A description of the flow direction information may refer to the relevant description in method 1000 and will not be repeated here.
[0233] S1107: The SMF sends the PDB and configuration cycle to the RAN. Correspondingly, the RAN receives the PDB and configuration cycle.
[0234] As above, the PDB and the configuration period may be indicated by the same information, for example, the first information in the above method 900 .
[0235] Optionally, when the SMF receives the instruction information from the PCF, it may continue to execute S1108, where the SMF sends the instruction information to the RAN, and the RAN receives the instruction information accordingly.
[0236] Optionally, upon receiving an indication from the PCF, the SMF may dynamically adjust the received configuration period and send the adjusted configuration period to the RAN. For example, if the SMF previously received a cumulative rate ratio from the UPF, the SMF uses the cumulative rate ratio to correct the period in the TSCAC and sets the TSCAI period to the corrected value.
[0237] Optionally, if the SMF receives flow direction information, it can instruct the terminal or UPF to generate dummy data packets periodically according to the flow direction carried in the flow direction information.
[0238] S1109 , the RAN configures transmission resources based on the configuration period, and determines the AN PDB based on the PDB.
[0239] For the description of AN PDB, please refer to the previous description and will not be repeated here.
[0240] Exemplarily, when the RAN obtains the data packet of the first service, it uses the most recently configured transmission resources to transmit the data packet.
[0241] Optionally, after receiving the indication information, if the RAN does not receive the data packet within the corresponding period, it does not consider the packet to be lost; or, if the data packet is received in advance, it does not consider the packet to be lost even if the buffering time exceeds the PDB.
[0242] It should be noted that the instruction information in method 1100 is not necessarily transparently transmitted when forwarded between network elements. For details, please refer to the relevant description in the above method 1000, which will not be repeated here.
[0243] In this embodiment of the present application, the PCF determines the configuration period of the transmission resources for the first service based on the latency parameters of the first service. This allows the RAN to use periodically configured transmission resources to transmit received non-periodic services, rather than temporarily configuring resources each time a non-periodic service is received. This implements semi-static resource scheduling, avoids the delay caused by temporarily configuring resources upon service arrival, and thus helps meet the transmission latency requirements of non-periodic services. Secondly, because the sum of the configuration period and the PDB is less than the PDB requirement of the first service, even if the RAN receives a data packet for the first service outside of the configuration period, the data packet can be buffered on the air interface for a maximum of one period and can be transmitted within the required PDB time, thus meeting the low-latency transmission requirements of non-periodic services.
[0244] FIG12 is a schematic flow chart of another communication method 1200 provided in an embodiment of the present application. As shown in FIG12 , the method 1200 includes steps S1201 to S1209. Each step shown in FIG12 is described in detail below.
[0245] S1201: The terminal establishes a PDU session. This process is the same as S1001.
[0246] S1202: The AF / NEF / TSCTSF sends a first request message to the PCF. Correspondingly, the PCF receives the first request message.
[0247] The first request message indicates a delay requirement of the first service or a PDB requirement of the first service.
[0248] For the description of latency requirements and PDB requirements, please refer to the relevant description in Figure 6, which will not be repeated here.
[0249] S1203: The PCF determines a PDB based on the first request message, where the PDB is smaller than or equal to the PDB requirement.
[0250] For the description of PCF determining PDB, please refer to the relevant description in the above example 1 or example 2, which will not be repeated here.
[0251] S1204: PCF sends the PDB to SMF, and SMF receives the PDB accordingly.
[0252] S1205: The PCF generates indication information, where the indication information indicates that the first service is a non-periodic service.
[0253] S1206, PCF sends the indication information to SMF.
[0254] It should be understood that S1205 and S1206 are optional steps. If S1205 is not executed, S1206 need not be executed. If S1205 is executed, S1206 may or may not be executed. This is not limited here. Regarding whether S1205 is executed, please refer to the relevant description of S1005 in method 1000, and will not be repeated here.
[0255] In one design, the PCF may also generate flow direction information and send the information to the SMF. The flow direction information may be described in the previous section and will not be repeated here.
[0256] S1207: The SMF sends the PDB to the RAN, and the RAN receives the PDB accordingly.
[0257] Optionally, when the SMF receives the instruction information from the PCF, it may continue to execute S1208, where the SMF sends the instruction information to the RAN, and the RAN receives the instruction information accordingly.
[0258] S1209: RAN generates an AN PDB and a configuration cycle of transmission resources based on the PDB.
[0259] The sum of this configuration cycle and AN PDB is less than PDB.
[0260] Exemplarily, when the RAN obtains the data packet of the first service, it uses the most recently configured transmission resources to transmit the data packet.
[0261] Optionally, after receiving the indication information, if the RAN does not receive the data packet within the corresponding period, it does not consider the packet to be lost; or, if the data packet is received in advance, it does not consider the packet to be lost even if the buffering time exceeds the PDB.
[0262] It should be noted that the instruction information in method 1200 is not necessarily transparently transmitted when forwarded between network elements. For details, please refer to the relevant description in the above method 1000, which will not be repeated here.
[0263] In this embodiment of the present application, the RAN determines the configuration period of the transmission resources for the first service based on the latency parameters of the first service. This eliminates the need for the RAN to temporarily configure resources each time a non-periodic service is received. Instead, the RAN can use the periodically configured transmission resources to transmit the received non-periodic service. This implements semi-static resource scheduling, avoids the delay caused by temporarily configuring resources upon service arrival, and thus helps meet the transmission latency requirements of the non-periodic service. Secondly, because the sum of the configuration period and the AN PDB is less than the PDB of the first service, even if the RAN receives a data packet of the first service outside of the configuration period, the data packet can be buffered on the air interface for a maximum of one period and can be transmitted within the required AN PDB time, thus meeting the low-latency transmission requirements of the non-periodic service.
[0264] It should be understood that the size of the serial numbers of the above processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0265] The method of the embodiment of the present application is described in detail above in conjunction with Figures 1 and 12. The device of the embodiment of the present application will be described in detail below in conjunction with Figures 13 and 14.
[0266] Figure 13 is a schematic block diagram of a communication device 1300 provided in an embodiment of the present application. As shown in Figure 13, the device 1300 includes a transceiver module 1310 and a processing module 1320. The device 1300 can be used to execute the method performed by the TSCTSF, PCF, or RAN in the above method embodiments.
[0267] Among them, the transceiver module 1310 is used to: obtain the delay parameters of the first service, the delay parameters are related to the delay requirement, the packet delay budget PDB requirement or PDB, and the first service is a non-periodic service; the processing module 1320 is used to: determine the configuration period of the transmission resources based on the delay parameters, and the transmission resources are used to transmit the data packets of the first service.
[0268] In a possible implementation, the device 1300 is the aforementioned TSCTSF, or a chip or chip system of TSCTSF.
[0269] Exemplarily, the transceiver module 1310 is specifically used to: receive a first request message from the application function AF or the network open function NEF, where the first request message indicates the delay requirement, which is the sum of the PDB requirement and the time length for the terminal to process the data packet.
[0270] Optionally, the processing module 1320 is also used to: determine the PDB requirement based on the delay requirement, and the sum of the configuration period and the PDB requirement is less than or equal to the delay requirement; the transceiver module 1320 is also used to: send a second request message to the policy control function PCF, and the second request message indicates the configuration period and the PDB requirement.
[0271] Optionally, the configuration period is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; DNN is a first value; S-NSSAI is a second value; or, the first request message does not include the period of the first service.
[0272] Optionally, the processing module 1320 is further configured to: generate indication information, where the indication information is used to indicate that the first service is a non-periodic service; and the transceiver module 1310 is further configured to: send the indication information.
[0273] Optionally, the indication information is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; DNN is a first value; S-NSSAI is a second value; or the first request message does not include the period of the first service.
[0274] Optionally, the transceiver module 1310 is further configured to: obtain scheduling status information from a radio access network RAN, the scheduling status information; and the processing module 1320 is specifically configured to: determine the configuration period based on the delay parameter and the scheduling status information.
[0275] Optionally, the transceiver module 1310 is further used to: receive an expected value of the configuration period from the RAN; the processing module 1320 is specifically used to: determine multiple values of the configuration period based on the delay parameter and the expected value; or, determine a value range of the configuration period based on the delay parameter and the expected value.
[0276] A more detailed description of the transceiver module 1310 and the processing module 1320 can be directly obtained by referring to the relevant description in the embodiment shown in FIG9 , which will not be repeated here.
[0277] In another possible implementation, the device 1300 is the aforementioned PCF, or a chip or chip system of the PCF.
[0278] In one design, the transceiver module 1310 is specifically used to: receive a first request message from one of the following network elements, where the first request message indicates the PDB requirement of the first service: TSCTSF, AF, NEF.
[0279] Optionally, the transceiver module 1310 is specifically configured to: receive a first request message from one of the following network elements, where the first request message indicates a delay requirement of the first service: AF, NEF.
[0280] Optionally, the processing module 1320 is further used to: determine the PDB based on the first request message, and the sum of the configuration period and the PDB is less than or equal to the PDB requirement; the transceiver module 1310 is further used to: send first information to the MF, and the first information includes the configuration period and the PDB.
[0281] Optionally, the configuration period is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; DNN is a first value; S-NSSAI is a second value; or, the first request message does not include the period of the first service.
[0282] Optionally, the processing module 1320 is further configured to: generate indication information, where the indication information is used to indicate that the first service is a non-periodic service; and the transceiver module 1310 is further configured to: send the indication information.
[0283] Optionally, the indication information is determined when at least one of the following is met: the latency requirement is less than or equal to a first preset threshold; the PDB requirement is less than or equal to a second preset threshold; DNN is a first value; S-NSSAI is a second value; or the first request message does not include the period of the first service.
[0284] Optionally, the transceiver module 1310 is further configured to: obtain scheduling status information from a radio access network RAN, the scheduling status information; and the processing module 1320 is specifically configured to: determine the configuration period based on the delay parameter and the scheduling status information.
[0285] Optionally, the transceiver module 1310 is further used to: receive an expected value of the configuration period from the RAN; the processing module 1320 is specifically used to: determine multiple values of the configuration period based on the delay parameter and the expected value; or, determine a value range of the configuration period based on the delay parameter and the expected value.
[0286] In another design, the transceiver module 1310 is also used to: receive a second request message, the second request message indicates the configuration period and packet delay budget PDB requirement of the transmission resources, the transmission resources are used to transmit data packets of a first service, and the first service is a non-periodic service; the processing module 1320 is also used to: determine the PDB, the PDB is less than or equal to the PDB requirement; the transceiver module 1310 is also used to: send first information, the first information includes the PDB and the configuration period.
[0287] Optionally, the transceiver module 1310 is further used to: receive indication information, where the indication information is used to indicate that the first service is a non-periodic service.
[0288] Optionally, the processing module 1320 is specifically configured to: determine the PDB based on at least one of the following: the PDB requirement, DNN, or S-NSSAI.
[0289] A more detailed description of the transceiver module 1310 and the processing module 1320 can be directly obtained by referring to the relevant description in the embodiment shown in FIG9 , which will not be repeated here.
[0290] In another possible implementation, the device 1300 is the aforementioned RAN, or a chip or chip system of the RAN.
[0291] Exemplarily, the transceiver module 1310 is specifically configured to receive the PDB from the SMF.
[0292] Optionally, the transceiver module 1310 is further configured to: receive indication information, where the indication information indicates that the first service is a non-periodic service.
[0293] Optionally, the transceiver module 1310 is further configured to: obtain a data packet, where the data packet is a data packet of the first service; and transmit the data packet using the most recently configured transmission resources.
[0294] A more detailed description of the transceiver module 1310 and the processing module 1320 can be directly obtained by referring to the relevant description in the embodiment shown in FIG9 , which will not be repeated here.
[0295] It should be noted that the apparatus 1300 may include a sending module but not a receiving module. Alternatively, the apparatus 1300 may include a receiving module but not a sending module. This may depend on whether the above solution executed by the apparatus 1300 includes both a sending action and a receiving action.
[0296] Figure 14 is another schematic block diagram of a communication device provided in an embodiment of the present application. As shown in Figure 14, device 1400 includes one or more processors 1410. The processor 1410 can be a general-purpose processor or a dedicated processor. For example, it can be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the device (such as TSCTSF, PCF, RAN, or chip), execute software programs, and process software program data.
[0297] Optionally, in one design, processor 1410 may include a program (also referred to as code or instructions), which may be executed on processor 1410 to cause apparatus 1400 to perform the method performed by the TSCTSF, PCF, or RAN in the above method embodiments. In yet another possible design, apparatus 1400 includes circuitry (not shown in FIG. 14 ) configured to implement the functionality of the TSCTSF, PCF, or RAN in the above method embodiments.
[0298] Exemplarily, the processor 1410 may be configured to execute computer programs or instructions in the memory to implement the steps performed by the TSCTSF, PCF, or RAN in the method embodiment shown in any one of the embodiments shown in FIG. 9 to FIG. 12 .
[0299] Optionally, the device 1400 may include one or more memories 1420 on which programs (sometimes also referred to as codes or instructions) are stored. The programs can be run on the processor 1410, so that the device 1400 executes the method performed by the TSCTSF, PCF or RAN in the above embodiments.
[0300] Optionally, the processor 1410 and / or the memory 1420 may include an artificial intelligence (AI) module, which is used to implement AI-related functions. The AI module may be implemented through software, hardware, or a combination of software and hardware. For example, the AI module may include a wireless intelligent controller (RIC) module. For example, the AI module may be a near real-time RIC or a non-real-time RIC.
[0301] Optionally, data may be stored in the processor 1410 and / or the memory 1420. The processor and memory may be provided separately or integrated together.
[0302] Optionally, the apparatus 1400 may further include a communication interface 1430. The processor 1410 may also be sometimes referred to as a processing unit, which controls the apparatus (e.g., TSCTSF, PCF, or RAN). The communication interface 1430 may also be sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, etc., which is used to implement the transceiver function of the apparatus.
[0303] Optionally, the apparatus 1400 further includes a communication interface 1430. The processor 1410 and the communication interface 1430 are coupled to each other. It is understood that the communication interface 1430 may be a transceiver or an input / output interface.
[0304] When the apparatus 1400 is used to implement the method of FIG9 , the processor 1410 is used to perform the functions of the processing unit described above, and the communication interface 1430 is used to perform the functions of the transceiver module described above. Whether the communication interface 1430 is used for sending or receiving can be determined by whether the method implemented by the apparatus 1400 is used for sending or receiving.
[0305] When the device 1400 is a chip implemented in a TSCTSF, the chip implements the functions of the TSCTSF in the above method embodiments. The TSCTSF chip receives signals from other modules in the TSCTSF, which may be signals sent by the AF or NEF to the TSCTSF; or sends signals to other modules in the TSCTSF, which may be signals sent by the TSCTSF to the PCF.
[0306] When the device 1400 is a chip implemented in a PCF, the chip implements the PCF functionality described in the method embodiments. The PCF chip receives signals from other modules within the PCF, such as signals sent by the AF / NEF / TSCTSF to the PCF; or sends signals to other modules within the PCF, such as signals sent by the PCF to the SMF.
[0307] When the apparatus 1400 is a chip used in a RAN, the chip implements the RAN functions described in the method embodiments. The RAN chip receives signals from other modules in the RAN, which may be signals sent by the SMF to the RAN; or the RAN chip sends signals to other modules in the RAN (such as a radio frequency module or antenna), which may be signals sent by the RAN to the terminal.
[0308] It is understood that when the apparatus 1400 is a TSCTSF, PCF, or RAN, the communication interface 1430 may be a transceiver, specifically including a transmitter and a receiver, where the transmitter is used to transmit signals and the receiver is used to receive signals. When the apparatus 1400 is a chip applied to the TSCTSF, PCF, or RAN, the communication interface 1430 may be an input / output circuit, where the input circuit may be used for receiving and the output interface may be used for transmitting.
[0309] It should be noted that the above method embodiments can be applied to or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by hardware integrated logic circuits in the processor or by software instructions.
[0310] The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.
[0311] The steps of the method disclosed in the embodiments of this application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.
[0312] The memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0313] The methods provided in the above embodiments can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product may include one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic disk), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).
[0314] The present application also provides a computer-readable medium having a computer program stored thereon. When the computer program is executed by a computer, the functions of the TSCTSF, PCF or RAN in any of the above method embodiments are implemented.
[0315] The present application also provides a computer program product, which, when executed by a computer, implements the functions of TSCTSF, PCF or RAN in any of the above method embodiments.
[0316] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0317] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0318] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0319] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0320] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0321] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0322] The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the scope of protection of the present application.
Claims
1. A communication method, characterized in that: include: Acquire a delay parameter of a first service, where the delay parameter is related to a delay requirement, a packet delay budget (PDB) requirement, or a PDB, and the first service is a non-periodic service; Based on the delay parameter, a configuration period of transmission resources is determined, and the transmission resources are used to transmit data packets of the first service.
2. The method according to claim 1, characterized in that The method is applied to a time-sensitive communication time synchronization function TSCTSF, and the delay parameter is the delay requirement; The obtaining of the delay parameter of the first service includes: A first request message is received from an application function AF or a network opening function NEF, where the first request message indicates the delay requirement.
3. The method according to claim 2, characterized in that The sum of the configuration period and the PDB requirement is less than or equal to the delay requirement, and the method further includes: Based on the latency requirement, determining the PDB requirement; A second request message is sent to a policy control function PCF, where the second request message indicates the configuration period and the PDB requirement.
4. The method according to claim 3, characterized in that The PDB requirement satisfies: the PDB requirement = the delay requirement - the time length for the terminal to process a data packet.
5. The method according to claim 1, characterized in that The method is applied to PCF, and the delay parameter is the PDB requirement; The obtaining of the delay parameter of the first service includes: A first request message is received from one of the following network elements, where the first request message indicates a PDB requirement for the first service: TSCTSF, AF, NEF.
6. The method according to claim 1, characterized in that The method is applied to PCF, and the delay parameter is the delay requirement; The obtaining of the delay parameter of the first service includes: A first request message is received from one of the following network elements, where the first request message indicates a delay requirement of the first service: AF, NEF.
7. The method according to claim 5 or 6, characterized in that: The sum of the configuration period and the PDB is less than or equal to the PDB requirement, and the method further includes: Determine the PDB based on the first request message; First information is sent to a session management function SMF, where the first information indicates the configuration period and the PDB.
8. The method according to any one of claims 2 to 7, characterized in that The configuration period is determined when at least one of the following conditions is met: The delay requirement is less than or equal to a first preset threshold; The PDB requirement is less than or equal to a second preset threshold; The network name DNN is the first value; The single network slice selection auxiliary information S-NSSAI is a second value; or, The first request message does not include a period of the first service.
9. The method according to any one of claims 2 to 8, characterized in that The method further comprises: Generate indication information, where the indication information is used to indicate that the first service is a non-periodic service; The instruction information is sent.
10. The method according to claim 9, characterized in that The indication information is determined when at least one of the following is satisfied: The delay requirement is less than or equal to a first preset threshold; The PDB requirement is less than or equal to a second preset threshold; DNN is the first value; S-NSSAI is the second value; or, The first request message does not include a period of the first service.
11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: Obtaining scheduling status information from a radio access network RAN; The determining, based on the delay parameter, a configuration period of the transmission resource includes: The configuration period is determined based on the delay parameter and the scheduling status information.
12. The method according to any one of claims 1 to 10, characterized in that The method further comprises: receiving an expected value of the configuration cycle from the RAN; Based on the delay parameter and the expected value, multiple values or value ranges of the configuration period are determined.
13. The method according to claim 1, characterized in that The method is applied to RAN, the delay parameter is the PDB authorized by the PCF for the first service based on the PDB requirement; The obtaining of the delay parameter of the first service includes: Receive the PDB from the SMF.
14. The method according to claim 13, characterized in that Before determining the configuration period of the transmission resource based on the delay parameter, the method further includes: receiving instruction information; Based on the indication information and the PDB, an access network AN PDB is determined.
15. The method according to claim 13 or 14, characterized in that The method further comprises: Obtaining a data packet of the first service; The data packet is transmitted using the transmission resources that were most recently configured.
16. A communication method, characterized in that: Applied to the policy control function PCF, the method comprises: receiving a second request message, where the second request message indicates a configuration period and a packet delay budget (PDB) requirement of a transmission resource, where the transmission resource is used to transmit a data packet of a first service, where the first service is a non-periodic service; Determining a PDB, the PDB being less than or equal to the PDB requirement; First information is sent to a session management function SMF, where the first information indicates the PDB and the configuration period.
17. The method according to claim 16, characterized in that The method further comprises: Indication information is received, where the indication information indicates that the first service is a non-periodic service.
18. The method according to claim 16, characterized in that Determining the PDB comprises: The PDB is determined based on at least one of: the PDB requirement, the DNN, or the S-NSSAI.
19. A communication device, characterized in that: Comprising means for implementing the method as claimed in any one of claims 1 to 18.
20. A communication device, characterized in that: The device comprises a processor configured to cause the communication device to implement the method according to any one of claims 1 to 18 by executing a computer program and / or a logic circuit.
21. The device according to claim 20, characterized in that The system also includes a memory for storing a computer program and / or a configuration file of the logic circuit.
22. The device according to claim 20 or 21, characterized in that A communication interface is also included for inputting and / or outputting signals.
23. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 18 is performed.
24. A computer program product, characterized in that The invention comprises a computer program which, when being executed, implements the method according to any one of claims 1 to 18.
Citation Information
Patent Citations
Method for processing a data stream and communication device
CN113596910A
Apparatus and method for supporting burst arrival time reference clock based on time-sensitive communication assistance information in wireless communication network
CN113767680A
Method for splitting end-to-end QoS (Quality of Service) demand information, terminal and network side equipment
CN114071586A
Deadline-based delivery for downlink traffic with jitter
US20230135681A1
Method and apparatus for service scheduling, and system
WO2022193127A1
