Communication method and related apparatus

Abstract

Provided in the embodiments of the present application are a communication method and a related apparatus. The method is applied to a first device, and comprises: acquiring an air interface configuration of an access network device, wherein the air interface configuration comprises one or more of the following parameters of an air interface: an uplink and downlink transmission period size, a downlink slot start time, an uplink slot end time, and an uplink and downlink slot resource configuration; and on the basis of the air interface configuration, generating instance configuration information of a deterministic network, wherein the instance configuration information comprises one or more of the following parameters of the deterministic network: a periodic cycle start time, a period length, an edge shaping configuration, and a link rate. Using the method of the embodiments of the present application enables better generation of instance configuration information of a deterministic network after the deterministic network (such as a deterministic IP transport network or DIP transport network) is introduced into a wireless communication architecture, thereby reducing the waiting latency for transmission and avoiding data accumulation.

Description

Communication methods and related devices

[0001] This application claims priority to Chinese Patent Application No. 202410925424.2, filed on July 10, 2024, entitled "Communication Method and Related Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication, and more particularly to communication methods and related devices. Background Technology

[0003] The system architecture of wireless communication networks (such as 5G) is divided into two parts: the access network and the core network. It mainly includes the following key logical network elements: Radio Access Network (RAN), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), User Data Management (UDM), Unified Data Repository (UDR), Application Function (AF), Data Network (DN), etc. As shown in Figure 1, among which:

[0004] RAN is a device that provides wireless access for terminal devices (such as mobile phones, IoT terminal devices, etc.), including but not limited to evolved Node B (eNodeB), Wi-Fi access point (AP), and Worldwide Interoperability for Microwave Access (WiMAX) base station (BS).

[0005] AMF is primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover.

[0006] SMF is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User Provider for Forwarding) to provide packet forwarding capabilities.

[0007] PCF is responsible for providing policies to AMF and SMF, such as slice selection policies and Quality of Service (QoS) policies.

[0008] UDM is used to store user data, such as contract information and authentication / authorization information.

[0009] UDR provides storage capabilities for contract data, policy data, and capability-related data.

[0010] The AF is responsible for providing services to the 3GPP network, such as influencing service routing and interacting with the PCF for policy control.

[0011] UPF is primarily responsible for processing user messages, such as forwarding and billing.

[0012] DN is a carrier network that provides data transmission services to users, such as IP Multimedia Service (IMS) and the Internet.

[0013] NSSF (Network Slice Selection Function) provides the ability to select network slices.

[0014] AUSF (Authentication Service Function) is responsible for authenticating users' access to the 5G network.

[0015] UDM (Unified Data Management) is used for user contract management, access authorization, and authentication information generation.

[0016] The main function of NSACF (Network Slice Access Control) is to monitor and control the number of user equipment (UE) registered on each network slice, as well as the number of PDU (Protocol Data Unit) sessions established on each network slice.

[0017] NSSAAF (Network Slicing and SNPN (Standard Non-Public Network) authentication and authorization function) is used to authenticate devices requesting access to a network slice and determine whether they are authorized to access the slice. Terminal devices (such as UEs) establish a PDU session between the terminal device and the RAN, then to the UPF, and finally to the DN to access the DN.

[0018] Those skilled in the art are attempting to introduce deterministic networks into wireless communication architectures. For example, a deterministic network (such as a DIP transport network) can be configured between the RAN and UPF. The RAN can provide feedback to the core network of the wireless communication architecture (such as 5GS) based on the time-sensitive communication assistance information (TSCAI) of the Time-Sensitive Communication (TSC) stream and its own scheduling status. The core network can then perform corresponding adjustment operations based on the information provided by the RAN, such as adjusting the TSC stream packet transmission configuration (e.g., packet transmission time) of the UPF end station in the deterministic network. After introducing a deterministic network into the wireless communication architecture, when the deterministic network is a DIP transport network, how to generate instance configuration information for the DIP transport network is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0019] This application discloses a communication method and related apparatus that can better generate instance configuration information of deterministic networks after introducing deterministic networks into a wireless communication architecture.

[0020] In a first aspect, embodiments of this application provide a communication method applied to a first device, the method comprising:

[0021] Obtain the air interface configuration of the access network device, wherein the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

[0022] Instance configuration information for a deterministic network is generated based on the air interface configuration, wherein the instance configuration information includes one or more of the following: the cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network.

[0023] In scenarios where wireless networks support deterministic networks (such as deterministic IP transport networks or DIP transport networks), deterministic networks are characterized by periodic forwarding, and air interface time slot configuration is usually also periodic. Therefore, when uplink / downlink data packets arrive at the access network device (such as RAN), additional waiting latency is easily introduced due to waiting for the transmission cycle of the deterministic network edge nodes / air interface. On the other hand, the amount of data that a deterministic network can forward within a forwarding cycle is limited, and air interface transmission resources are usually also limited. Therefore, the instance configuration information used by the deterministic network is generated based on the air interface configuration information provided by the access network device to achieve node-level configuration of the deterministic network. In this process, the instance configuration information of the deterministic network matches the periodic characteristics of air interface transmission, thus reducing the aforementioned waiting latency and avoiding data backlog.

[0024] In one possible implementation of the first aspect, obtaining the air interface configuration of the access network device includes:

[0025] Send a first request message, wherein the first request message is used to request the air interface configuration of the access network device;

[0026] Receive the air interface configuration of the access network device.

[0027] In this implementation, the first device actively requests the air interface configuration of the access network device from other devices.

[0028] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, obtaining the air interface configuration of the access network device includes:

[0029] Receive the air interface configuration of the access network device, wherein the air interface configuration may be triggered by subscription;

[0030] The method further includes:

[0031] Send a response message, wherein the response message is used to indicate that the deterministic network configuration was successful.

[0032] In this implementation, the first device passively receives the air interface configuration of the access network device sent by other devices through a subscription method.

[0033] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the first device includes a control plane function (CPF).

[0034] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the cycle start time of the deterministic network is derived from the uplink time slot end time and the size of the uplink and downlink transmission cycles.

[0035] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the parameter for deriving the cycle start time further includes the link delay between the network device and the edge device of the deterministic network.

[0036] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the shaping window in the edge shaping configuration of the deterministic network is derived based on the downlink time slot start time and the uplink / downlink transmission cycle size.

[0037] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the parameters for deriving the shaping window further include the link delay between the network device and the edge device of the deterministic network.

[0038] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the period length of the deterministic network is determined based on the size of the uplink and downlink transmission periods.

[0039] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the uplink and downlink time slot resource configuration includes the PRB information of the access network device.

[0040] In conjunction with the first aspect, or any of the above possible implementations of the first aspect, in yet another possible implementation of the first aspect, the uplink and downlink time slot resource configuration is used to determine the number of downlink PRBs required for the maximum downlink data volume to arrive in one deterministic network cycle and the number of uplink PRBs required for the maximum uplink data volume that can be forwarded in one deterministic network cycle. The link rate and the number of instances in the deterministic network are derived from the downlink PRB number, the uplink PRB number, and the PRB information of the network device.

[0041] Secondly, embodiments of this application provide a communication method applied to a second device (such as OAM, edge device, etc.), the method comprising:

[0042] Obtain the air interface configuration of the access network device, wherein the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

[0043] The air interface configuration of the access network device is sent to the first device, wherein the air interface configuration is used to generate instance configuration information of the deterministic network, and the instance configuration information includes one or more of the following: periodic cycle start time, period length, edge shaping configuration, and link rate of the deterministic network.

[0044] In scenarios where wireless networks support deterministic networks (such as deterministic IP transport networks or DIP transport networks), deterministic networks are characterized by periodic forwarding, and air interface time slot configuration is usually also periodic. Therefore, when uplink / downlink data packets arrive at the access network device (such as RAN), additional waiting latency is easily introduced due to waiting for the transmission cycle of the deterministic network edge nodes / air interface. On the other hand, the amount of data that a deterministic network can forward within a forwarding cycle is limited, and air interface transmission resources are usually also limited. Therefore, the instance configuration information used by the deterministic network is generated based on the air interface configuration information provided by the access network device to achieve node-level configuration of the deterministic network. In this process, the instance configuration information of the deterministic network matches the periodic characteristics of air interface transmission, thus reducing the aforementioned waiting latency and avoiding data backlog.

[0045] In conjunction with the second aspect, one possible implementation of the second aspect also includes:

[0046] Receive a first request message from a first device, wherein the first request message is used to request the air interface configuration of the access network device.

[0047] In this implementation, the second device sends the air interface configuration of the access network device to the first device only after the first device sends the first request message; that is, the second device passively sends the air interface configuration to the first device.

[0048] In conjunction with the second aspect, or any of the above-mentioned possible implementations of the second aspect, another possible implementation of the second aspect further includes:

[0049] Send the first request message to the access network device;

[0050] The step of obtaining the air interface configuration of the access network device includes:

[0051] Receive the air interface configuration sent by the access network device.

[0052] In this implementation, the second device does not store the air interface configuration of the access network device. Therefore, after receiving the first request message, it needs to send the first request message to the access network device to request the air interface configuration. After obtaining the air interface configuration, it then sends the air interface configuration to the first device.

[0053] In conjunction with the second aspect, or any of the above-mentioned possible implementations of the second aspect, another possible implementation of the second aspect further includes:

[0054] Receive air interface configuration sent by the access network device, wherein the air interface configuration may be triggered by subscription;

[0055] Send the air interface configuration to the first device;

[0056] Receive a response message sent by the first device, wherein the response message is used to indicate that the deterministic network configuration is successful;

[0057] Send the response message to the network device.

[0058] In this implementation, the second device receives the air interface configuration actively sent by the access network device through a subscription method, and then sends the air interface configuration to the first device. Subsequently, after receiving the response for the air interface configuration from the first device, the second device sends the response to the access network device.

[0059] Thirdly, embodiments of this application provide a communication method applied to an access network device, the method comprising:

[0060] Determine the air interface configuration, wherein the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration;

[0061] Send the air interface configuration, wherein the air interface configuration is used to generate instance configuration information for a deterministic network, and the instance configuration information includes one or more of the following: periodic cycle start time, period length, edge shaping configuration, and link rate of the deterministic network.

[0062] In scenarios where wireless networks support deterministic networks (such as deterministic IP transport networks or DIP transport networks), deterministic networks are characterized by periodic forwarding, and air interface time slot configuration is usually also periodic. Therefore, when uplink / downlink data packets arrive at the access network device (such as RAN), additional waiting latency is easily introduced due to waiting for the transmission cycle of the deterministic network edge nodes / air interface. On the other hand, the amount of data that a deterministic network can forward within a forwarding cycle is limited, and air interface transmission resources are usually also limited. Therefore, the instance configuration information used by the deterministic network is generated based on the air interface configuration information provided by the access network device to achieve node-level configuration of the deterministic network. In this process, the instance configuration information of the deterministic network matches the periodic characteristics of air interface transmission, thus reducing the aforementioned waiting latency and avoiding data backlog.

[0063] In conjunction with the third aspect, in one possible implementation of the third aspect, the sending of the air interface configuration includes:

[0064] Send air interface configuration according to the subscription rules;

[0065] The method further includes:

[0066] Receive a response message, wherein the response message is used to indicate that the deterministic network configuration is successful.

[0067] In this implementation, the access network device actively sends the air interface configuration by subscribing.

[0068] In conjunction with the third aspect, or any of the above possible implementations of the third aspect, another possible implementation of the third aspect further includes:

[0069] Receive a first request message sent by a second device, wherein the first request message is used to request the air interface configuration of the access network device;

[0070] Send the aforementioned air interface configuration to the second device.

[0071] In this implementation, the access network device sends the air interface configuration only after receiving the first request message, i.e., it passively sends the air interface configuration.

[0072] Fourthly, embodiments of this application provide a communication device, which can be a first device or a component or functional module within the first device, wherein:

[0073] The communication device includes a module for performing the method described in the first aspect or any possible implementation thereof;

[0074] Alternatively, the communication device includes a processor for performing the method described in the first aspect or any possible implementation thereof.

[0075] Fifthly, embodiments of this application provide a communication device, which can be a second device or a component or functional module within a second device, wherein:

[0076] The communication device includes a module for performing the method described in the second aspect or any possible implementation thereof;

[0077] Alternatively, the communication device includes a processor for performing the method described in the second aspect or any possible implementation thereof.

[0078] Sixthly, embodiments of this application provide a communication device, which can be an access network device or a device or functional module within an access network device, wherein:

[0079] The communication device includes a module for performing the method described in the third aspect or any possible implementation of the third aspect;

[0080] Alternatively, the communication device includes a processor for performing the method described in the third aspect or any possible implementation thereof.

[0081] In a seventh aspect, embodiments of this application provide a communication device, characterized in that it includes a logic circuit and an interface, the logic circuit and the interface being coupled; the interface is used for inputting and / or outputting information, wherein:

[0082] The logic circuit is used to perform the method described in the first aspect or any possible implementation thereof, or...

[0083] The logic circuit is used to execute the method described in the second aspect or any possible implementation thereof, or...

[0084] The logic circuit is used to execute the method described in the third aspect or any possible implementation thereof.

[0085] Eighthly, embodiments of this application provide a computer-readable storage medium for storing a computer program, wherein:

[0086] When the computer program is executed, it is capable of implementing the first aspect or any possible implementation of the first aspect, or...

[0087] When the computer program is executed, it is capable of implementing the second aspect or any possible implementation of the second aspect, or...

[0088] When the computer program is executed, it is capable of implementing the third aspect or any possible implementation of the third aspect.

[0089] Ninthly, embodiments of this application provide a communication system, which includes a first device, a second device, and an access network device, wherein:

[0090] The first device is used to perform the method described in the first aspect or any possible implementation thereof;

[0091] The second device is used to perform the method described in the second aspect or any possible implementation thereof;

[0092] The access network device is used to perform the method described in the third aspect or any possible implementation thereof. Attached Figure Description

[0093] The accompanying drawings used in the embodiments of this application are described below.

[0094] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0095] Figure 2 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0096] Figure 3 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0097] Figure 4 is a schematic diagram of a DIP transmission network provided in an embodiment of this application;

[0098] Figure 5 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0099] Figure 6 is a schematic diagram of the periodic relationship between a RAN and a DIP transmission network provided in an embodiment of this application;

[0100] Figure 7 is a schematic diagram of the periodic relationship between another RAN and DIP transmission network provided in an embodiment of this application;

[0101] Figure 8 is a schematic diagram of the periodic relationship between another RAN and DIP transmission network provided in an embodiment of this application;

[0102] Figure 9 is a schematic diagram of the periodic relationship between another RAN and DIP transmission network provided in an embodiment of this application;

[0103] Figure 10 is a schematic diagram of a link latency scenario provided by an embodiment of this application;

[0104] Figure 11 is a schematic diagram of the periodic relationship between another RAN and DIP transmission network provided in an embodiment of this application;

[0105] Figure 12 is a schematic diagram illustrating the principle of generating instance configuration information according to an embodiment of this application;

[0106] Figure 13 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0107] Figure 14 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0108] Figure 15 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0109] Figure 16 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0110] Figure 17 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0111] Figure 18 is a schematic diagram of another communication device provided in an embodiment of this application;

[0112] Figure 19 is a schematic diagram of the structure of another communication device provided in an embodiment of this application. Detailed Implementation

[0113] The embodiments of this application are described below with reference to the accompanying drawings.

[0114] Explanation of relevant concepts:

[0115] Deterministic IP (DIP): Explicit routing can be achieved through SRv6, and its network identifier (SID) can be used to identify the DIP transmission path planned at the node level.

[0116] Cycle length: refers to the duration of one DIP forwarding cycle;

[0117] Cycle count: refers to the maximum number of cycle counts supported by a DIP instance. For example, the Tagged Cyclic Queuing and Forwarding (TCQF) mechanism supports 3 or more cycle alternations.

[0118] DIP ingress edge node: can perform edge shaping on the service flow and distribute data packets to different DIP cycles for transmission.

[0119] DIP instances provide deterministic QoS guarantees for service flows, such as latency and jitter. Each instance has its own configuration information. A DIP transport network can have one or more instances, each instance can be a subnet, and each instance has its own configuration information.

[0120] Link speed: refers to the link speed that a DIP instance can provide for the transmission of service flow data packets, which generally corresponds to the interface speed of the DIP instance interface.

[0121] Please refer to Figures 2 and 3, which are schematic diagrams of the architecture of two communication systems provided in the embodiments of this application. These two communication systems introduce deterministic IP (DIP) networks into cellular networks, such as 5G systems (5GS), that is, the 5GS transmission network supports DIP.

[0122] The communication system includes UE401, RAN402, AMF403, SMF404, PCF405, AF406, UPF407, DN408, OAM409, and edge node 410, among which:

[0123] User equipment (UE) 401 can be such as mobile phones, Internet of Things (IoT) terminal devices, etc.

[0124] RAN402 is a device that provides radio access for UEs, including but not limited to evolved Node B (eNodeB), Wi-Fi access point (AP), and Worldwide Interoperability for Microwave Access (WiMAX) base station (BS).

[0125] The AMF403 is primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover.

[0126] The SMF404 is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User Packet Forwarder) to provide packet forwarding capabilities.

[0127] PCF405 is responsible for providing policies to AMF and SMF, such as slice selection policies and Quality of Service (QoS) policies.

[0128] AF406 is responsible for providing services to the 3GPP network, such as influencing service routing and interacting with the PCF for policy control.

[0129] The UPF407 is primarily responsible for processing user messages, such as forwarding and billing.

[0130] DN408 is a carrier network that provides data transmission services to users, such as IP Multimedia Service (IMS) and the Internet.

[0131] Operations, Administration and Maintenance (OAM) 409: The network administrator responsible for the operation, administration and maintenance of each RAN (and its associated systems).

[0132] Edge node 410 refers to a network node located at the edge of the DIP transmission network, which is responsible for performing edge shaping and forwarding, flow control and other functions of the DIP transmission network.

[0133] It should be noted that the mapping in SMF, RAN, and UPF refers to the parameter mapping between 5GS and DIP transport network to support the interoperability of the two technical architectures. It can map 5GS parameters to corresponding parameters in DIP transport network or vice versa.

[0134] The system shown in Figure 2 is a distributed architecture, with the CPF located in the edge node of the DIP transport network. Optionally, the CPF in the edge node can subsequently generate instance configuration information for the DIP transport network.

[0135] The system shown in Figure 3 is a centralized architecture. The CPF is located in the DetNet Controller (centralized controller) of the DIP transport network. Optionally, the instance configuration information of the DIP transport network can be generated by the CPF in the DetNet Controller.

[0136] As can be seen, the deployment location of CPF differs between the architecture shown in Figure 2 and the architecture shown in Figure 3.

[0137] Optionally, the CPF in a DIP transport network may also include the network management of the DIP transport network.

[0138] A DIP transport network typically contains multiple instances, each of which can be a subnet. For example, DIP instance 1, DIP instance 2, and DIP instance 3 in Figures 2 and 3 can be different subnets within different DIP transport networks, and each instance has its own configuration information. Optionally, a DIP transport network may also have only one instance, corresponding to only one instance configuration information.

[0139] DIP (Digital Injection Protocol) transport network is a DetNet technology architecture. Figure 4 illustrates the technical principle of DIP transport network. It introduces a periodic scheduling mechanism for forwarding on the data plane and proposes efficient path planning and resource allocation algorithms on the control plane, aiming to achieve a large-scale, scalable, end-to-end deterministic low-latency network system. DIP transport network has the following characteristics: a) It does not allow arbitrary sending (receiving) of data packets, allocating a specific sending (receiving) time period for each data packet, thereby avoiding bursts, queuing delays within control nodes, and eliminating long-tail effects; b) It adopts a periodic shaping and scheduling mechanism, thereby forming isolation between periods and avoiding micro-bursts and their hop-by-hop accumulation; c) The upper bound of the system's end-to-end latency and the upper limit of jitter are determined. Specifically, DIP has the following main functions: 1) Implementing admission control on the control plane: The control plane of the ingress edge node can record the resource reservation status of each flow. Based on the resource reservation results, the ingress edge node can decide whether a deterministic flow is allowed to enter the network for deterministic forwarding. The resource reservation status of the data flow can be dynamically refreshed to achieve resource reservation renewal. 2) Path planning and resource reservation at the control plane: Deterministic path planning for data stream transmission is implemented, based on distributed routing algorithms or centralized path calculation, to plan transmission paths for data streams and support pre-reservation of necessary deterministic resources along the route. 3) Path binding at the data plane: Resource reservation for DIP transmission is reflected at the nodes of the data forwarding path; subsequent data packet transmissions need to be bound to this path; path binding technology can be coupled with label carrying technology. 4) Deterministic periodic forwarding at the data plane: Ingress edge nodes embed a time period number into the data packet based on the time it is sent. After receiving the packet, intermediate nodes perform deterministic periodic forwarding according to the period mapping, ensuring that the data packet carries a local time period number when it is sent, until the data packet reaches the egress edge node.

[0140] Specific implementation mechanisms of DIP transmission networks include Tagged Cyclic Queuing and Forwarding (TCQF) and Cycle Specified Queuing and Forwarding (CSQF), among others:

[0141] a) TCQF supports more than two cycles, indicating the cycle number through an existing or new packet header field called a tag, replacing the cycle mapping in TSN's purely synchronous receive clock-based Cyclic Queuing Forwarding (CQF) (the cyclic mapping is calculated by the controller plane, taking into account link, intra-node forwarding delays, and cycle clock offsets). The TCQF option helps the receiving port identify the time period from which packets are sent from the upstream router; it can be used to determine the output port cycle buffer for queuing packets. The target advantages of TCQF include low end-to-end jitter, ease of high-speed hardware implementation, the optional ability to support a large number of flows in large networks by applying TCQF to deterministic network DetNet() aggregations instead of applying it individually to each DetNet flow (via DiffServ-style aggregation), and support for wide-area DetNet networks with arbitrary link delays and delay variations, and low-precision clock synchronization.

[0142] b) CSQF improves upon CQF by explicitly specifying the transmission period of each node along the path (using SR segment identifiers (SIDs)), enabling end-to-end bounded latency. SR is a source routing technique that does not maintain per-flow status at intermediate and egress nodes. SR-based CSQF supports flow aggregation, which is beneficial for scaling to macro networks. CSQF defines a new field, Cycle Segment, to identify cycle periods. Cycle Segment identifies the interface / link and the cycle period of the interface / link. To specify which interface and cycle a packet should be transmitted to, simply append a cycle segment to the packet. By appending a list of cycle segments to a packet, not only can explicit packet routing be achieved, but the transmission period of each node along the path can also be specified without requiring per-flow status at intermediate and egress nodes.

[0143] In DIP scenarios supported by cellular networks (such as 5GS system transport network (5GS TN)), the periodic forwarding characteristic of DIP transport networks, coupled with the periodic air interface time slot configuration of cellular networks, can lead to additional waiting delays and data backlogs when uplink / downlink data packets arrive at the RAN due to waiting for the transmission cycle of the DIP transport network edge nodes / air interface. Therefore, this embodiment of the application generates instance configuration information for the DIP transport network based on the air interface configuration provided by the cellular network, reducing the aforementioned waiting delays and avoiding data backlogs. For ease of understanding, the air interface configuration process is explained in detail below with reference to Figure 5.

[0144] It should be understood that, in this application, for the sake of simplicity, the name DIP is used as an example to illustrate deterministic networks (or deterministic network protocols, or deterministic network technologies, or technologies based on circular queuing and forwarding mechanisms), but this application does not limit the name of deterministic networks.

[0145] Please refer to Figure 5. Figure 5 illustrates a communication method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 2 or Figure 3. For example, the first device mentioned in this method can be a CPF or other network element in the architecture shown in Figure 2 or Figure 3. This method can also be implemented based on other architectures. The method includes, but is not limited to, the following steps:

[0146] Step S501: The first device obtains the air interface configuration of the access network device.

[0147] Access network equipment can be devices such as RAN that can provide network access for terminal devices (such as UE).

[0148] There are several ways for the first device to obtain the air interface configuration. Examples are given below:

[0149] Method A: The first device actively obtains the air interface configuration. For example, the first device sends (directly or indirectly) a first request message to other devices, wherein the first request message is used to request the air interface configuration of the access network device; after receiving the first request message, the other device responds to the first request message and returns the air interface configuration to the first device. Correspondingly, the first device receives the air interface configuration from the access network device. The other device can be the access network device or a device that can communicate with the access network device (such as edge devices of deterministic networks (such as deterministic IP transmission networks or DIP transmission networks), OAM, etc.).

[0150] Method B: The first device passively acquires the air interface configuration. For example, other devices send the air interface configuration to the first device according to subscription rules, which define that the air interface configuration is sent when a new air interface configuration is generated. Optionally, other devices can also periodically send (directly or indirectly) the air interface configuration of the access network device to the first device. Correspondingly, the first device receives the air interface configuration. The other device can be an access network device or a device capable of communicating with the access network device (such as edge devices in deterministic networks (e.g., deterministic IP transmission networks or DIP transmission networks), OAM, etc.).

[0151] Method C: The first device stores the air interface configuration itself. For example, the first device is an access network device. In this case, the first device has its own air interface configuration. Optionally, the air interface configuration can be generated by the access network device itself.

[0152] In this embodiment of the application, the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, uplink and downlink time slot resource configuration, physical resource block (PRB) information, etc.

[0153] Information about the PRB may include, for example, the size (or specifications) of the PRB.

[0154] Step S502: The first device generates instance configuration information for the deterministic network based on the air interface configuration.

[0155] The instance configuration information includes one or more of the following: cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network (such as a deterministic IP transport network or DIP).

[0156] The following descriptions will be based on the deterministic network, specifically the DIP transmission network.

[0157] In this context, a deterministic network (such as a deterministic DIP transport network or a DIP transport network) may have one or more instances, each of which can be a subnet. Each instance has corresponding instance configuration information. Therefore, the instance configuration information generated by the first device may be one or more. When there are multiple subnets, the first device can generate instance configuration information for all subnets (i.e., all instance configuration information) or instance configuration information for some subnets (i.e., partial instance configuration information). Each instance configuration information includes one or more of the following: the cycle start time, cycle length, edge shaping configuration, link rate, etc., of the deterministic IP transport network. In addition to these information, the instance configuration information may also include other information related to the DIP transport network, which will not be listed here.

[0158] Optionally, the cycle start time can be an absolute time; the edge shaping configuration can include one or more parameters such as shaping rate r and shaping window, where the shaping window is also called the forwarding window reserved for deterministic flow within the cycle; the link rate is also called the equivalent link speed or remaining bandwidth resources.

[0159] For ease of understanding, the parameters included in the instance configuration information of the DIP transmission network are illustrated in Table 1 below.

[0160] Table 1

[0161] To facilitate understanding, the generation principles of the parameters in the instance configuration information will be explained one by one below. Some parameters can be directly calculated to produce a definite result, while others are calculated or have their range (or conditions) limited. Results within the range (or that meet the conditions) are all valid results.

[0162] Regarding the cycle start time DipStartTime and the shaping window ShapingWindow in the edge shaping configuration of the DIP transport network:

[0163] Optionally, the cycle start time of the deterministic IP transport network is derived from the uplink timeslot end time and the uplink / downlink transmission cycle size. Optionally, the shaping window in the edge shaping configuration of the deterministic IP transport network is derived from the downlink timeslot start time and the uplink / downlink transmission cycle size. Optionally, there may be a correlation between the cycle start time and the shaping window, for example, using one quantity as one of the input parameters for deriving the other quantity. For ease of understanding, the following example illustrates this:

[0164] 1) Uplink direction: Uplink timeslot end time (UL-DipOffset) = the end time (relative time) of the last uplink timeslot within the uplink and downlink transmission cycles (dl-UL-TransmissionPeriodicity). For example: UL-DipOffset = (DipStartTime) mod (dl-UL-TransmissionPeriodicity)

[0165] 2) Downlink direction: Downlink slot start time (DL-DipOffset) = Start time of the first downlink slot within the uplink / downlink transmission period (dl-UL-TransmissionPeriodicity). For example: DL-DipOffset = (DipStartTime + ShapingWindow) mod (dl-UL-TransmissionPeriodicity)

[0166] Regarding the cycle length (DipCycleLength) of DIP transmission networks:

[0167] Optionally, the cycle length of the deterministic IP transmission network is determined based on the uplink and downlink transmission cycle size. For ease of understanding, the following example illustrates this:

[0168] 1) When dl-UL-TransmissionPeriodicity≤DipCycleLength, for example: DipCycleLength=n*dl-UL-TransmissionPeriodicity;

[0169] Optional, ShapingWindow = m*dl-UL-TransmissionPeriodicity

[0170] Here, the ShapingWindow is constrained again to ensure that a DIP instance simultaneously meets the aforementioned uplink and downlink requirements. n and m are any positive integers, and m ≤ n.

[0171] 2) When dl-UL-TransmissionPeriodicity > DipCycleLength, for example:

[0172] k*DipCycleLength=dl-UL-TransmissionPeriodicity, where k is any positive integer.

[0173] To better understand the solutions of this application embodiment, the effects of the generated deterministic IP transmission network configuration parameters are illustrated below with reference to the accompanying drawings.

[0174] Figure 6 illustrates the case where UL-DipOffset = the end time of the last uplink time slot within the uplink / downlink transmission period dl-UL-TransmissionPeriodicity of the network device (e.g., RAN), and dl-UL-TransmissionPeriodicity ≤ DipCycleLength, specifically the case where 4*dl-UL-TransmissionPeriodicity = DipCycleLength, where the downlink (DL) and uplink (UL) time slot ratio is 1:2.

[0175] Figure 7 illustrates the case where DL-DipOffset = the start time of the first downlink time slot within the uplink / downlink transmission period dl-UL-TransmissionPeriodicity of the network device (e.g., RAN), and dl-UL-TransmissionPeriodicity ≤ DipCycleLength, specifically the case where 4*dl-UL-TransmissionPeriodicity = DipCycleLength, where the downlink (DL) and uplink (UL) time slot ratio is 1:2.

[0176] Figure 8 illustrates the following: UL-DipOffset = the end time of the last uplink time slot within the uplink / downlink transmission period dl-UL-TransmissionPeriodicity of the network device (e.g., RAN), DL-DipOffset = the start time of the first downlink time slot within the uplink / downlink transmission period dl-UL-TransmissionPeriodicity, and dl-UL-TransmissionPeriodicity ≤ DipCycleLength. Specifically, 3*dl-UL-TransmissionPeriodicity = DipCycleLength, and 2*dl-UL-TransmissionPeriodicity = ShapingWindow. In this case, the downlink (DL) and uplink (UL) time slot ratio is 1:3, and both uplink and downlink are matched.

[0177] Figure 9 illustrates the case where UL-DipOffset = the end time of the last uplink time slot within the uplink / downlink transmission period dl-UL-TransmissionPeriodicity of the network device (e.g., RAN) air interface, and dl-UL-TransmissionPeriodicity > DipCycleLength. Specifically, dl-UL-TransmissionPeriodicity = 4 * DipCycleLength, where the downlink (DL) and uplink (UL) time slot ratio is 4:2.

[0178] In one of the alternative schemes, when the edge node of the DIP transmission network is separated from the network device (such as RAN), there is also a parameter called Delay_EdgeNode2RAN for the link delay between the edge node and the network device, as shown in Figure 10.

[0179] (1) When deploying the network, the link length between the edge node and the network device (such as RAN) is configured to be very short compared to the total link length between the network device and the functional device (such as UPF). Therefore, the link delay Delay_EdgeNode2RAN between the edge node and the network device can be ignored at this time. In fact, the time when the last data packet in the ShapingWindow is sent out is difficult to align with the end time of the ShapingWindow, that is, there is a time surplus (guard band). The remaining window time eliminates part of the link delay impact.

[0180] (2) The impact of the link delay Delay_EdgeNode2RAN between the edge node and the network device on the instance configuration information can also be further considered. For example, the impact on the cycle start time and the shaping window in the edge shaping configuration. In this case, the cycle start time DipStartTime and the shaping window ShapingWindow in the edge shaping configuration can be derived using the following relationship (for example only):

[0181] UL-DipOffset=(DipStartTime-Delay_EdgeNode2RAN)mod(dl-UL-TransmissionPeriodicity)

[0182] DL-DipOffset=(DipStartTime+ShapingWindow+Delay_EdgeNode2RAN)mod(dl-UL-TransmissionPeriodicity)

[0183] Figure 11 illustrates the case where the last uplink time slot within the uplink / downlink transmission period dl-UL-TransmissionPeriodicity of a network device (such as a RAN) ends at UL-DipOffset, and dl-UL-TransmissionPeriodicity≤DipCycleLength, taking into account the impact of link delay Delay_EdgeNode2RAN.

[0184] The configuration of the cycle start time DipStartTime, the shaping window ShapingWindow, and the cycle length DipCycleLength avoids the delay caused by data packets waiting to be scheduled during transmission.

[0185] Regarding the edge shaping rate or link rate r of the DIP transport network, and the number of instances N in the DIP transport network:

[0186] Optionally, the uplink and downlink time slot resource configuration is used to determine the number of downlink PRBs required for the maximum downlink data volume to arrive in one deterministic IP cycle and the number of uplink PRBs required for the maximum uplink data volume to be forwarded in one DIP cycle. The link rate and the number of instances N are derived from the number of downlink PRBs (referred to as the number of downlink time slot resources N_DL), the number of uplink PRBs (referred to as the number of uplink time slot resources N_UL), and the information (such as the size) of the PRBs of the network device.

[0187] To facilitate understanding, the derivation process is illustrated below with an example:

[0188] Based on the above formula, given the values ​​of N_DL, N_UL, and PRB, the ShapingWindow for a deterministic IP transport network can be determined. x r1 x r2 x And one or more of N. Here, PRB is the basic unit of data resource allocation; for example, uplink and downlink service channels (PDSCH and PUSCH) can be scheduled in units of PRBs. N_DL is the number of downlink PRBs required for the maximum amount of downlink data arriving in one DIP cycle of air interface transmission, and N_UL is the number of uplink PRBs corresponding to the maximum amount of uplink data that can be forwarded in one DIP cycle of air interface transmission. Each of the N instances corresponds to one instance configuration information, therefore there are N instances corresponding to N instance configuration information. ShapingWindow x It is the integer window contained in the x-th instance configuration information out of N instance configuration information, r1 x It is the downlink edge shaping rate or link (or interface) speed contained in the configuration information of the xth instance, r2 x It is the uplink edge shaping rate or link (or interface) speed contained in the configuration information of the xth instance.

[0189] The configuration of the link rate r and the number of instances N in the DIP transport network helps the deterministic IP transport network configure transport network resources based on air interface information, thereby avoiding data packet backlog during transmission and improving resource utilization.

[0190] The above method can be used to generate configuration information for one or more instances. Figure 12 illustrates this using N instance configuration information as an example.

[0191] Optionally, if the first device is a network device, the network device can send the instance configuration information to the functional devices in the DIP transport network for the functional devices to use; if the first device is a device in the DIP transport network, the first device can directly use the instance configuration information.

[0192] It should be noted that this application may instruct the derivation of the possible ranges for some parameters that need to be obtained, that is, to limit the range of their values. After limiting the range, a value can be randomly selected within the range or a suitable value can be selected through some algorithms as the final value of the parameter.

[0193] In the method shown in Figure 5, in scenarios where the wireless network supports deterministic networks (such as deterministic IP transport networks or DIP transport networks), deterministic networks have the characteristic of periodic forwarding, and air interface time slot configuration is usually also periodic. Therefore, when uplink / downlink data packets arrive at the access network device (such as RAN), additional waiting delays are easily introduced due to waiting for the transmission cycle of the deterministic network edge nodes / air interface. On the other hand, the amount of data that a deterministic network can forward in one forwarding cycle is limited, and air interface transmission resources are usually also limited. Therefore, the instance configuration information used by the deterministic network is generated based on the air interface configuration information provided by the access network device to realize node-level configuration of the deterministic network. In this process, the instance configuration information of the deterministic network matches the periodic characteristics of air interface transmission, thus reducing the aforementioned waiting delays and avoiding data backlog.

[0194] The method shown in Figure 5 covers a variety of situations. To facilitate understanding, the following examples, in conjunction with Figures 13, 14, 15, and 16, illustrate four specific processes for obtaining air interface configuration and generating instance configuration information.

[0195] Please refer to Figure 13, which illustrates a communication method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 2 or Figure 3. For example, the first device mentioned in this method is the CPF or other nodes in the architecture shown in Figure 2 or Figure 3. Some concepts, operations, and logical relationships in the method shown in Figure 13 can be referred to the relevant descriptions of the embodiments shown in Figure 2 or Figure 3. It includes, but is not limited to, the following steps:

[0196] Step S1301: CPF starts configuring a deterministic network (such as a deterministic IP transport network or a DIP transport network) instance.

[0197] This step requires preparing the necessary parameters beforehand, such as performing condition checks or monitoring to determine whether to configure a DIP transport network instance and the parameters required for that instance. Optionally, this step can be omitted.

[0198] Step S1302: CPF sends the first request message to the edge node.

[0199] In this embodiment, the CPF (located in the edge node or DetNet Controller of the DIP transport network) requests air interface configuration from the access network device (such as the RAN) through the edge node. The first request message is used to request the air interface configuration of the access network device. This first request message includes the identity information of the access network device (such as the RAN) (e.g., the device ID or gNB ID of the access network device) and the identity information of the DIP transport network instance (e.g., the DIP instance identifier). The CPF in the DIP transport network correctly obtains the air interface configuration of the access network device corresponding to the currently configured DIP transport network instance based on this information.

[0200] As one implementation, the first request message can be to subscribe to the air interface configuration (which has changed) of the access network device, that is, when the air interface configuration of the access network device changes, the edge node needs to report the (changed) air interface configuration of the access network device to the CPF.

[0201] Step S1303: The edge node receives the first request message.

[0202] Specifically, the edge node analyzes the first request message and learns that the CPF requires the air interface configuration of the access network device. However, the edge node does not have the air interface configuration, so the edge node needs to obtain the instance information from other devices (such as access network devices).

[0203] Step S1304: The edge node sends the first request message to the access network device.

[0204] The edge node can process the previously received first request message to obtain a new first request message, such as adding the edge node's address information or device identification information, and then send the new first request message to the access network device; optionally, the edge node can also directly forward the first request message to the access network device, which is equivalent to the first request message being transparently transmitted at the access network device.

[0205] Step S1305: The access network device receives the first request message.

[0206] In this implementation, the access network device determines its own air interface configuration, or another device determines the air interface configuration for the network device and sends it to the access network device for storage. Therefore, the access network device contains the access network device's air interface configuration. Based on this first request message, the access network device can determine that it needs to send (or return) the air interface configuration to the edge node.

[0207] Step S1306: The access network device sends the air interface configuration to the edge node.

[0208] Step S1307: The edge node receives the air interface configuration.

[0209] Step S1308: The edge node sends the air interface configuration to the CPF.

[0210] The edge node can add its address information or device identification information to the previously received air interface configuration and then send the air interface configuration to the access network device. Optionally, the edge node can also directly forward the air interface configuration to the access network device, which is equivalent to the air interface configuration being transparently transmitted at the access network device.

[0211] Step S1309: The CPF receives the air interface configuration from the access network device.

[0212] It should be noted that the specific implementation of step S1309 can be referred to the relevant description of step S501, and will not be repeated here.

[0213] Step S1310: The CPF generates instance configuration information for the deterministic IP transport network based on the air interface configuration.

[0214] It should be noted that the specific implementation of step S1310 can be referred to the relevant description of step S502, and will not be repeated here.

[0215] It should be noted that steps S1302-S1305 are optional; that is, a subscription request is not necessarily required. Access network devices (such as RAN) can send air interface configurations to edge nodes based on operator policies or configurations. Similarly, edge nodes can send air interface configurations to CPFs based on operator policies or configurations.

[0216] Please refer to Figure 14, which illustrates a communication method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 2 or Figure 3. For example, the first device mentioned in this method is the CPF or other nodes in the architecture shown in Figure 2 or Figure 3. Some concepts, operations, and logical relationships in the method shown in Figure 14 can be referred to the relevant descriptions of the embodiments shown in Figure 2 or Figure 3. It includes, but is not limited to, the following steps:

[0217] Step S1401: The access network device sends the air interface configuration to the edge node.

[0218] Optionally, access network devices (such as RANs) can subscribe to (or request) the CPF of a deterministic network (such as a deterministic IP transport network or DIP transport network) to perform corresponding deterministic network (such as a deterministic IP transport network or DIP transport network) instance configuration based on operator policies or configurations. The access network device can carry the air interface configuration in a subscription message (or request message), which includes the access network device's identity information (such as the access network device's device ID or gNB ID) and the identity information of the deterministic network (such as a deterministic IP transport network or DIP transport network) instance (such as a DIP instance identifier). This allows the deterministic network (such as a deterministic IP transport network or DIP transport network) to configure or adjust the correct deterministic network (such as a transport network DIP) instance, or it can send the above information to the CPF after receiving the deterministic network (such as a deterministic IP transport network or DIP transport network) instance configuration.

[0219] Step S1402: Edge node receive air interface configuration.

[0220] For example, an edge node receives a subscription message that includes the air interface configuration. Of course, it's also possible that the air interface configuration is not included in the subscription message but sent separately; the specific sending method is not limited here.

[0221] Step S1403: The edge node sends the air interface configuration to the CPF.

[0222] The edge node can add its address information or device identification information to the previously received air interface configuration (or subscription message) and then send the air interface configuration (or subscription message) to the access network device. Optionally, the edge node can also directly forward the air interface configuration (or subscription message) to the access network device, which is equivalent to the air interface configuration (or subscription message) being transparently transmitted at the access network device.

[0223] Step S1404: The CPF receives the air interface configuration.

[0224] For example, CPF receives a subscription message that includes the air interface configuration. Of course, it's also possible that the air interface configuration is not included in the subscription message but sent separately; the specific sending method is not limited here.

[0225] It should be noted that the specific implementation of step S1404 can be referred to the relevant description of step S501, and will not be repeated here.

[0226] Step S1405: The CPF generates instance configuration information for a deterministic network (such as a deterministic IP transport network) based on the air interface configuration.

[0227] It should be noted that the specific implementation of step S1405 can be referred to the relevant description of step S502, and will not be repeated here.

[0228] Step S1406: CPF sends a response message to the edge node.

[0229] Specifically, the CPF returns a response message to the access network device through the edge node of the DIP transport network, indicating whether the configuration for an instance of a deterministic network (such as a deterministic IP transport network or a DIP transport network) was successful or failed.

[0230] Step S1407: The edge node receives the response message.

[0231] Step S1408: The edge node sends the response message to the access network device.

[0232] Step S1409: The access network device receives the response message.

[0233] Specifically, the response message is a response to the subscription message previously sent by the access network device.

[0234] Please refer to Figure 15, which illustrates a communication method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 2 or Figure 3. For example, the first device mentioned in this method is the CPF or other nodes in the architecture shown in Figure 2 or Figure 3. Some concepts, operations, and logical relationships in the method shown in Figure 15 can be referred to the relevant descriptions of the embodiments shown in Figure 2 or Figure 3. It includes, but is not limited to, the following steps:

[0235] Step S1501: CPF starts configuring a deterministic network (such as a deterministic IP transport network or a DIP transport network) instance.

[0236] This step requires preparing the necessary parameters beforehand, such as performing condition checks or monitoring to determine whether to configure a DIP transport network instance and the parameters required for that instance. Optionally, this step can be omitted.

[0237] Step S1502: CPF sends a first request message to OAM.

[0238] Specifically, the first request message is used to request the air interface configuration of the access network device;

[0239] In this embodiment, the CPF (located at the edge node or in the DetNet Controller of the deterministic network, such as a deterministic IP transport network or a DIP transport network) requests air interface configuration information from the OAM. The first request message is used to request the air interface configuration of the access network device. This first request message includes the identity information of the access network device (such as the RAN) (such as the device ID or gNB ID of the access network device) and the identity information of the instance of the deterministic network (such as the DIP instance identifier). The OAM uses this information to locate the corresponding access network device (such as the RAN) and collects (or obtains) the air interface configuration of that access network device.

[0240] As one implementation, the request can be to subscribe to the air interface configuration of the access network device (when it changes), that is, when the air interface configuration of the access network device changes, the OAM needs to report the (changed) air interface configuration of the access network device to the CPF.

[0241] Step S1503: OAM receives the first request message.

[0242] Specifically, by analyzing the first request message, the edge node can determine the air interface configuration of the access network device that the CPF needs.

[0243] Step S1504: OAM obtains the air interface configuration of the access network device.

[0244] In this implementation, the OAM determines the air interface configuration itself, or other devices determine the air interface configuration for the network devices and send it to the OAM for storage. Therefore, the OAM has the air interface configuration of the access network devices.

[0245] Step S1505: OAM sends the air interface configuration to CPF.

[0246] Step S1506: The CPF receives the air interface configuration.

[0247] It should be noted that the specific implementation of step S1506 can be referred to the relevant description of step S501, and will not be repeated here.

[0248] Step S1507: The CPF generates instance configuration information for a deterministic network (such as a deterministic IP transport network) based on the air interface configuration.

[0249] It should be noted that the specific implementation of step S1507 can be referred to the relevant description of step S502, and will not be repeated here.

[0250] It should be noted that steps S1502-S1503 are optional, meaning that the above subscription request is not necessarily required. OAM can send the air interface configuration of the access network device to CPF based on operator policies or configurations.

[0251] Please refer to Figure 16, which illustrates a communication method provided in an embodiment of this application. This method can be implemented based on the architecture shown in Figure 2 or Figure 3. For example, the first device mentioned in this method is the CPF or other nodes in the architecture shown in Figure 2 or Figure 3. Some concepts, operations, and logical relationships in the method shown in Figure 16 can be referred to the relevant descriptions of the embodiments shown in Figure 2 or Figure 3. It includes, but is not limited to, the following steps:

[0252] Step S1601: The access network device sends the air interface configuration to the OAM.

[0253] Optionally, the access network device (such as RAN) can subscribe to (or request) the CPF of the deterministic network (such as a deterministic IP transport network or DIP transport network) based on operator policies or configuration to perform the corresponding deterministic network (such as a deterministic IP transport network or DIP transport network) instance configuration. The access network device can carry this air interface configuration in a subscription message (or request message). The subscription message contains the identity information of the access network device (such as the access network device's device ID or gNB ID) and the identity information of the deterministic network (such as a deterministic IP transport network or DIP transport network) instance (such as a DIP instance identifier), so that the deterministic network (such as a deterministic IP transport network or DIP transport network) can configure or adjust the correct deterministic network (such as a deterministic IP transport network or transport network DIP) instance, or it can send the above information to the CPF after obtaining the deterministic network (such as a deterministic IP transport network or DIP transport network) instance configuration.

[0254] Step S1602: OAM receive air interface configuration.

[0255] For example, OAM receives a subscription message that includes the air interface configuration. Of course, it's also possible that the air interface configuration is not included in the subscription message but sent separately; the specific sending method is not limited here.

[0256] Step S1603: OAM sends the air interface configuration to CPF.

[0257] The OAM can add its address information or device identification information to the previously received air interface configuration (or subscription message) and then send the air interface configuration (or subscription message) to the access network device; alternatively, the OAM can also directly forward the air interface configuration (or subscription message) to the access network device, which is equivalent to the air interface configuration (or subscription message) being transparently transmitted at the access network device.

[0258] Step S1604: The CPF receives the air interface configuration.

[0259] For example, CPF receives a subscription message that includes the air interface configuration. Of course, it's also possible that the air interface configuration is not included in the subscription message but sent separately; the specific sending method is not limited here.

[0260] It should be noted that the specific implementation of step S1604 can be referred to the relevant description of step S501, and will not be repeated here.

[0261] Step S1605: The CPF generates instance configuration information for a deterministic network (such as a deterministic IP transport network) based on the air interface configuration.

[0262] It should be noted that the specific implementation of step S1605 can be referred to the relevant description of step S502, and will not be repeated here.

[0263] Step S1606: CPF sends a response message to OAM.

[0264] Specifically, the CPF returns a response message to the access network device via the OAM of the deterministic network (such as a deterministic IP transport network or a DIP transport network), indicating whether the configuration for the instance of the deterministic network (such as a deterministic IP transport network or a DIP transport network) was successful or failed.

[0265] Step S1607: OAM receives the response message.

[0266] Step S1608: OAM sends the response message to the access network device.

[0267] Step S1609: The access network device receives the response message.

[0268] Specifically, the response message is a response to the subscription message previously sent by the access network device.

[0269] The following describes the communication device provided in the embodiments of this application.

[0270] This application divides the communication device into functional modules according to the above method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The communication device of the embodiments of this application will be described in detail below with reference to Figures 17 to 19.

[0271] Figure 17 is a schematic diagram of a communication device provided in an embodiment of this application. As shown in Figure 17, the communication device includes a processing module 1801 and a transceiver module 1802. The transceiver module 1802 can implement corresponding communication functions, and the processing module 1801 is used for data processing. The transceiver module 1802 can also be referred to as an interface, a communication interface, or a communication module, etc.

[0272] In some embodiments of this application, the communication device can be used to perform the actions performed by the transmitting end in the above method embodiments. For example, the transmitting end can be the device itself or a chip or functional module configurable within the device. The transceiver module 1802 is used to perform operations related to transmitting and receiving by the transmitting end in the above method embodiments, and the processing module 1801 is used to perform operations related to processing by the transmitting end in the above method embodiments. The processing module 1801 can perform corresponding operations by calling a computer program or by performing corresponding operations through corresponding hardware circuits. The transceiver module 1802 can perform transmitting and receiving operations independently or under the control of the processing module 1801.

[0273] For example, the communication device shown in FIG17 can be a first device or a component in the first device. The processing module 1801 and the transceiver module 1802 in the communication device can respectively perform the following operations:

[0274] The processing module 1801 is used to obtain the air interface configuration of the access network device, wherein the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

[0275] Processing module 1801 is used to generate instance configuration information of the deterministic network according to the air interface configuration, wherein the instance configuration information includes one or more of the following: periodic cycle start time, period length, edge shaping configuration, and link rate of the deterministic network.

[0276] In scenarios where wireless networks support deterministic networks (such as deterministic IP transport networks or DIP transport networks), deterministic networks are characterized by periodic forwarding, and air interface time slot configuration is usually also periodic. Therefore, when uplink / downlink data packets arrive at the access network device (such as RAN), additional waiting latency is easily introduced due to waiting for the transmission cycle of the deterministic network edge nodes / air interface. On the other hand, the amount of data that a deterministic network can forward within a forwarding cycle is limited, and air interface transmission resources are usually also limited. Therefore, the instance configuration information used by the deterministic network is generated based on the air interface configuration information provided by the access network device to achieve node-level configuration of the deterministic network. In this process, the instance configuration information of the deterministic network matches the periodic characteristics of air interface transmission, thus reducing the aforementioned waiting latency and avoiding data backlog.

[0277] In one possible implementation, regarding the acquisition of the air interface configuration of the access network device, the processing module 1801 is specifically used for:

[0278] A first request message is sent through the transceiver module 1802, wherein the first request message is used to request the air interface configuration of the access network device;

[0279] The air interface configuration of the access network device is received through the transceiver module 1802.

[0280] In this implementation, the first device actively requests the air interface configuration of the access network device from other devices.

[0281] In one possible implementation, regarding the acquisition of the air interface configuration of the access network device, the processing module 1801 is specifically used for:

[0282] The air interface configuration of the access network device is received through the transceiver module 1802, wherein the air interface configuration can be triggered by subscription;

[0283] The transceiver module 1802 is also configured to: send a response message, wherein the response message is used to indicate that the deterministic network configuration is successful.

[0284] In this implementation, the first device passively receives the air interface configuration of the access network device sent by other devices through a subscription method.

[0285] In yet another possible implementation, the first device includes a control plane function (CPF).

[0286] In another possible implementation, the cycle start time of the deterministic network is derived from the uplink time slot end time and the size of the uplink and downlink transmission cycles.

[0287] In another possible implementation, the parameters for deriving the cycle start time also include the link delay between the network device and the edge device of the deterministic network.

[0288] In another possible implementation, the shaping window in the edge shaping configuration of the deterministic network is derived based on the downlink slot start time and the size of the uplink and downlink transmission cycles.

[0289] In another possible implementation, the parameters for deriving the shaping window also include the link latency between the network device and the edge device of the deterministic network.

[0290] In another possible implementation, the period length of the deterministic network is determined based on the uplink and downlink transmission period size.

[0291] In another possible implementation, the uplink and downlink time slot resource configuration includes information about the access network device's PRB.

[0292] In another possible implementation, the uplink and downlink time slot resource configuration is used to determine the number of downlink PRBs required for the maximum amount of downlink data to arrive in a deterministic network cycle and the number of uplink PRBs required for the maximum amount of uplink data that can be forwarded in a deterministic network cycle. The link rate and the number of instances in the deterministic network are derived from the number of downlink PRBs, the number of uplink PRBs, and the PRB information of the network device.

[0293] Reusing Figure 17, in some other embodiments of this application, the communication device shown in Figure 17 can be a second device or a component within a second device, where the second device can be an edge device, OAM, or similar device. The processing module 1801 and / or transceiver module 1802 in this communication device can respectively perform the following operations:

[0294] The transceiver module 1802 is used to obtain the air interface configuration of the access network device, wherein the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

[0295] The transceiver module 1802 is used to send the air interface configuration of the access network device to the first device, wherein the air interface configuration is used to generate instance configuration information of the deterministic network, and the instance configuration information includes one or more of the following: periodic cycle start time, period length, edge shaping configuration, and link rate of the deterministic network.

[0296] In scenarios where wireless networks support deterministic networks (such as deterministic IP transport networks or DIP transport networks), deterministic networks are characterized by periodic forwarding, and air interface time slot configuration is usually also periodic. Therefore, when uplink / downlink data packets arrive at the access network device (such as RAN), additional waiting latency is easily introduced due to waiting for the transmission cycle of the deterministic network edge nodes / air interface. On the other hand, the amount of data that a deterministic network can forward within a forwarding cycle is limited, and air interface transmission resources are usually also limited. Therefore, the instance configuration information used by the deterministic network is generated based on the air interface configuration information provided by the access network device to achieve node-level configuration of the deterministic network. In this process, the instance configuration information of the deterministic network matches the periodic characteristics of air interface transmission, thus reducing the aforementioned waiting latency and avoiding data backlog.

[0297] In one possible implementation:

[0298] The transceiver module 1802 is further configured to receive a first request message from the first device, wherein the first request message is used to request the air interface configuration of the access network device.

[0299] In this implementation, the second device sends the air interface configuration of the access network device to the first device only after the first device sends the first request message; that is, the second device passively sends the air interface configuration to the first device.

[0300] In one possible implementation:

[0301] The transceiver module 1802 is also used to send the first request message to the access network device;

[0302] Regarding the acquisition of the air interface configuration of the access network device, the transceiver module 1802 is specifically used for:

[0303] Receive the air interface configuration sent by the access network device.

[0304] In this implementation, the second device does not store the air interface configuration of the access network device. Therefore, after receiving the first request message, it needs to send the first request message to the access network device to request the air interface configuration. After obtaining the air interface configuration, it then sends the air interface configuration to the first device.

[0305] In yet another possible implementation:

[0306] The transceiver module 1802 is also used to receive the air interface configuration sent by the access network device, wherein the air interface configuration can be triggered by subscription;

[0307] The transceiver module 1802 is also used to send the air interface configuration to the first device;

[0308] The transceiver module 1802 is further configured to receive a response message sent by the first device, wherein the response message is used to indicate that the deterministic network configuration is successful;

[0309] The transceiver module 1802 is also used to send the response message to the network device.

[0310] In this implementation, the second device receives the air interface configuration actively sent by the access network device through a subscription method, and then sends the air interface configuration to the first device. Subsequently, after receiving the response for the air interface configuration from the first device, the second device sends the response to the access network device.

[0311] Reusing Figure 17, in some other embodiments of this application, for example, the communication device shown in Figure 17 can be an edge node or a device in an edge node, and the processing module 1801 and / or transceiver module 1802 in the communication device can respectively perform the following operations:

[0312] Processing module 1801 is used to determine air interface configuration, wherein the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration.

[0313] The transceiver module 1802 is used to send the air interface configuration, wherein the air interface configuration is used to generate instance configuration information of the deterministic network, and the instance configuration information includes one or more of the following: periodic cycle start time, period length, edge shaping configuration, and link rate of the deterministic network.

[0314] In scenarios where wireless networks support deterministic networks (such as deterministic IP transport networks or DIP transport networks), deterministic networks are characterized by periodic forwarding, and air interface time slot configuration is usually also periodic. Therefore, when uplink / downlink data packets arrive at the access network device (such as RAN), additional waiting latency is easily introduced due to waiting for the transmission cycle of the deterministic network edge nodes / air interface. On the other hand, the amount of data that a deterministic network can forward within a forwarding cycle is limited, and air interface transmission resources are usually also limited. Therefore, the instance configuration information used by the deterministic network is generated based on the air interface configuration information provided by the access network device to achieve node-level configuration of the deterministic network. In this process, the instance configuration information of the deterministic network matches the periodic characteristics of air interface transmission, thus reducing the aforementioned waiting latency and avoiding data backlog.

[0315] In one possible implementation, regarding the sending of the air interface configuration, the transceiver module 1802 is specifically used to: send the air interface configuration according to the subscription rules;

[0316] The transceiver module 1802 is also used to receive a response message, wherein the response message is used to indicate that the deterministic network configuration is successful.

[0317] In this implementation, the access network device actively sends the air interface configuration by subscribing.

[0318] In yet another possible implementation:

[0319] The transceiver module 1802 is also configured to receive a first request message sent by the second device, wherein the first request message is used to request the air interface configuration of the access network device;

[0320] The transceiver module 1802 is also used to send the air interface configuration to the second device.

[0321] In this implementation, the access network device sends the air interface configuration only after receiving the first request message, i.e., it passively sends the air interface configuration.

[0322] The specific descriptions of the transceiver module and processing module shown in the above embodiments are merely examples. For the specific functions or execution steps of the transceiver module and processing module, please refer to the above method embodiments, which will not be described in detail here.

[0323] The communication device according to the embodiments of this application has been described above. The following describes possible product forms of the communication device. Any product possessing the functions of the communication device described in FIG17 above falls within the protection scope of the embodiments of this application.

[0324] The following description is merely an example and does not limit the product form of the communication device in the embodiments of this application to this.

[0325] In one possible implementation, in the communication device shown in FIG17, the processing module 1801 can be one or more processors, and the transceiver module 1802 can be a transceiver, or the transceiver module 1802 can also be a transmitting module and a receiving module. The transmitting module can be a transmitter, and the receiving module can be a receiver. The transmitting module and the receiving module are integrated into one device, such as a transceiver. In the embodiments of this application, the processor and the transceiver can be coupled, etc., and the connection method of the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information in the above method can be the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the aforementioned information, the information may need to undergo further processing before being input into the processor.

[0326] As shown in Figure 18, the communication device 190 includes one or more processors 1920 and transceivers 1910. Exemplarily, the transceiver 1910 is used to perform the functions or steps implemented by the transceiver module 1802 shown in Figure 17, and the processor 1920 is used to perform the functions or steps implemented by the processing module 1801 shown in Figure 17. Detailed descriptions of the processor 1920 and transceiver 1910 can be found in Figure 17 or the method embodiments shown above, and will not be elaborated further here.

[0327] The descriptions of the relevant steps and information in the above embodiments can be found in the descriptions of the method embodiments above, and will not be detailed here.

[0328] In various implementations of the communication device shown in Figure 18, the transceiver may include a receiver for performing a receiving function (or operation) and a transmitter for performing a transmitting function (or operation). The transceiver is also used to communicate with other devices / appliances via a transmission medium.

[0329] Optionally, the communication device 190 may further include one or more memories 1930 for storing program instructions and / or data. The memory 1930 is coupled to the processor 1920. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 1920 may operate in conjunction with the memory 1930. The processor 1920 may execute program instructions stored in the memory 1930. Optionally, at least one of the above-mentioned memories may be included in the processor.

[0330] This embodiment does not limit the specific connection medium between the transceiver 1910, processor 1920, and memory 1930. In Figure 18, the memory 1930, processor 1920, and transceiver 1910 are connected via a bus 1940, indicated by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 18, but this does not imply that there is only one bus or one type of bus.

[0331] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0332] In this application embodiment, the memory may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM), etc. Memory is any storage medium capable of carrying or storing program code having instruction or data structure forms, and capable of being read and / or written by a computer (such as the communication device shown in this application), but is not limited to this. The memory in this application embodiment may also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0333] Processor 1920 is primarily used for processing communication protocols and data, controlling the entire communication device, executing software programs, and processing software program data. Memory 1930 is primarily used for storing software programs and data. Transceiver 1910 may include control circuitry and an antenna. The control circuitry is primarily used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is primarily used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are primarily used for receiving user input data and outputting data to the user.

[0334] When the communication device is powered on, the processor 1920 can read the software program in the memory 1930, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1920 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1920. The processor 1920 converts the baseband signal back into data and processes the data.

[0335] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0336] The communication device shown in this application embodiment may also have more components than those in Figure 18, and this application embodiment does not limit this. The methods executed by the processor and transceiver shown above are only examples, and the specific steps executed by the processor and transceiver can be referred to the methods described above.

[0337] In another possible implementation, in the communication device shown in Figure 17, the processing module 1801 can be one or more logic circuits, and the transceiver module 1802 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver module 1802 can also be a transmitting module and a receiving module. The transmitting module can be an output interface, and the receiving module can be an input interface. The transmitting module and the receiving module are integrated into one module, such as an input / output interface. As shown in Figure 19, the communication device shown in Figure 19 includes a logic circuit 2001 and an interface 2002. That is, the processing module 1801 can be implemented using the logic circuit 2001, and the transceiver module 1802 can be implemented using the interface 2002. The logic circuit 2001 can be a chip, a processing circuit, an integrated circuit, or a system-on-a-chip (SoC) chip, etc., and the interface 2002 can be a communication interface, an input / output interface, pins, etc. For example, Figure 19 illustrates the communication device as a chip, which includes the logic circuit 2001 and the interface 2002.

[0338] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method of the logic circuit and the interface is not limited in this embodiment. For example, the logic circuit 2001 can be used to execute the functions or steps implemented by the processing module 1801 shown in FIG. 17, and the interface 2002 can be used to execute the functions or steps implemented by the transceiver module 1802 shown in FIG. 17. For a detailed description of the logic circuit 2001 and the interface 2002, please refer to FIG. 17 or the method embodiment shown above, which will not be detailed here.

[0339] The above description of the communication device is only an example. For a detailed description of the communication device shown in Figure 19, please refer to the above method embodiments or Figure 17 or Figure 18. It will not be described in detail here.

[0340] The communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form, or it can implement the method provided in the embodiments of this application in software form, etc., and the embodiments of this application do not limit it in this way.

[0341] The descriptions of relevant steps and information in the above embodiments can be found in the method embodiments described above, and will not be detailed here. For the specific implementation methods of the embodiments shown in Figure 19, please also refer to the above embodiments, which will not be detailed here.

[0342] This application also provides a communication system, which includes the aforementioned first device, second device, and access network device.

[0343] In addition, this application also provides a computer program for implementing the operations and / or processes performed by various communication devices in the method provided in this application.

[0344] This application also provides a computer-readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by various communication devices in the methods provided in this application.

[0345] This application also provides a computer program product comprising computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by various entities in the method provided in this application to be executed.

[0346] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, or it may be an electrical, mechanical, or other form of connection.

[0347] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of this application.

[0348] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0349] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0350] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to a first device, the method includes: Obtain the air interface configuration of the access network device, wherein the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration. Instance configuration information for a deterministic network is generated based on the air interface configuration, wherein the instance configuration information includes one or more of the following: the cycle start time, cycle length, edge shaping configuration, and link rate of the deterministic network.

2. The method according to claim 1, characterized in that, The acquisition of the air interface configuration of the access network device includes: Send a first request message, wherein the first request message is used to request the air interface configuration of the access network device; Receive the air interface configuration of the access network device.

3. The method according to claim 1, characterized in that, The acquisition of the air interface configuration of the access network device includes: Receive the air interface configuration of the access network device, wherein the air interface configuration is triggered by subscription; The method further includes: Send a response message, wherein the response message is used to indicate that the deterministic network configuration was successful.

4. The method according to any one of claims 1-3, characterized in that, The first device includes a control plane function (CPF).

5. The method according to any one of claims 1-4, characterized in that, The start time of the periodic cycle of the deterministic network is derived from the end time of the uplink time slot and the size of the uplink and downlink transmission cycles.

6. The method according to claim 5, characterized in that, The parameters for deriving the cycle start time also include the link delay between the network device and the edge device of the deterministic network.

7. The method according to any one of claims 1-6, characterized in that, The shaping window in the edge shaping configuration of the deterministic network is derived based on the downlink time slot start time and the size of the uplink and downlink transmission cycles.

8. The method according to claim 7, characterized in that, The parameters for deriving the shaping window also include the link delay between the network device and the edge device of the deterministic network.

9. The method according to any one of claims 1-8, characterized in that, The period length of the deterministic network is determined based on the size of the uplink and downlink transmission periods.

10. The method according to any one of claims 1-9, characterized in that, The uplink and downlink time slot resource configuration includes the PRB information of the access network equipment.

11. The method according to claim 10, characterized in that, The uplink and downlink time slot resource configuration is used to determine the number of downlink PRBs required for the maximum downlink data volume to arrive in one deterministic network cycle and the number of uplink PRBs required for the maximum uplink data volume that can be forwarded in one deterministic network cycle. The link rate and the number of instances in the deterministic network are derived based on the number of downlink PRBs, the number of uplink PRBs, and the PRB information of the network devices.

12. A communication method, characterized in that, Applied to a second device, including: Obtain the air interface configuration of the access network device, wherein the air interface configuration includes one or more of the following: uplink and downlink transmission cycle size, downlink time slot start time, uplink time slot end time, and uplink and downlink time slot resource configuration. The air interface configuration of the access network device is sent to the first device, wherein the air interface configuration is used to generate instance configuration information of the deterministic network, and the instance configuration information includes one or more of the following: periodic cycle start time, period length, edge shaping configuration, and link rate of the deterministic network.

13. The method according to claim 12, characterized in that, Also includes: Receive a first request message from a first device, wherein the first request message is used to request the air interface configuration of the access network device.

14. The method according to claim 13, characterized in that, Also includes: Send the first request message to the access network device; The step of obtaining the air interface configuration of the access network device includes: Receive the air interface configuration sent by the access network device.

15. The method according to claim 12, characterized in that, Also includes: Receive the air interface configuration sent by the access network device, wherein the air interface configuration is triggered by subscription; Send the air interface configuration to the first device; Receive a response message sent by the first device, wherein the response message is used to indicate that the deterministic network configuration is successful; Send the response message to the network device.

16. A communication method, characterized in that, Applied to access network equipment, including: Determine the air interface configuration, wherein the air interface configuration includes one or more of the following: the uplink and downlink transmission cycle size of the air interface, the downlink time slot start time, the uplink time slot end time, and the uplink and downlink time slot resource configuration; Send the air interface configuration, wherein the air interface configuration is used to generate instance configuration information for a deterministic network, and the instance configuration information includes one or more of the following: the periodic cycle start time, the period length, the edge shaping configuration, and the link rate of the deterministic network.

17. The method according to claim 16, characterized in that, Sending the air interface configuration includes: Send air interface configuration according to the subscription rules; The method further includes: Receive a response message, wherein the response message is used to indicate that the deterministic network configuration is successful.

18. The method according to claim 16, characterized in that, Also includes: Receive a first request message sent by a second device, wherein the first request message is used to request the air interface configuration of the access network device; Send the aforementioned air interface configuration to the second device.

19. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1-11; or, the communication device includes a processor for performing the method as described in any one of claims 1-11.

20. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 12-15; or, the communication device includes a processor for performing the method as described in any one of claims 12-15.

21. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 16-18; or, the communication device includes a processor for performing the method as described in any one of claims 16-18.

22. A communication device, characterized in that, Includes logic circuits and interfaces, wherein the logic circuits and interfaces are coupled; The interface is used for inputting and / or outputting information, and the logic circuit is used for performing the method as described in any one of claims 1-18.

23. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which, when executed, performs the method as described in any one of claims 1-18.

24. A communication system, characterized in that, It includes the first device, the second device, and the access network equipment, wherein: The first device is the first device as described in any one of claims 1-11; The second device is the second device as described in any one of claims 12-15; The first device is the access network device as described in any one of claims 16-18.

Images