Communication method and apparatus
By using PDU sessions and direct communication connections in mobile communication systems, port numbers are dynamically allocated to support the integration of 5G system and TSN, solving the problem of insufficient support for TSN in 5G networks and improving deployment flexibility and service performance.
Patent Information
- Application Number
- PCT/CN2024/078429
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-07-14
- Filing Date
- 2024-02-23
- Publication Date
- 2024-11-28
AI Technical Summary
The existing 5G network has limited support for time-sensitive network (TSN) communication, resulting in insufficient flexibility in TSN deployment and high transmission delay, affecting service performance.
By introducing a communication method in the mobile communication system, utilizing PDU sessions and direct communication connections to support the integration of the 5G system and TSN, dynamically allocate port numbers to improve network support capabilities and deployment flexibility, and reduce transmission delays.
It improves the support capability of mobile communication systems for TSN, enhances network deployment flexibility, reduces transmission delay, and improves service performance.
Smart Images

Figure CN2024078429_28112024_PF_FP_ABST
Abstract
Description
Communication method and device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on May 19, 2023, with application number 202310573595.9 and application name “A TSN bridge transmission method and device”, and claims priority to the Chinese patent application filed with the State Intellectual Property Office on July 14, 2023, with application number 202310872306.5 and application name “A communication method and device”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The embodiments of the present application relate to the field of communications, and in particular to a communication method and apparatus. Background Art
[0003] Time-sensitive networking (TSN) defines a time-sensitive mechanism for Ethernet data transmission, adding determinism and reliability to standard Ethernet to ensure that Ethernet can provide stable and consistent services for the transmission of critical data.
[0004] Traditional TSN is typically deployed over wired Ethernet and can be used in scenarios with high latency and reliability requirements, such as factories. With the development of fifth-generation (5G) mobile communication technology, current 5G networks already support TSN. For example, the 5G system (5GS) can be integrated into TSN as a TSN bridge.
[0005] 5G network support for TSN enables some connections in TSN to be wireless. However, the current 5GS support for TSN communication is limited.
[0006] Summary of the Invention
[0007] The present application provides a communication method and apparatus, which enhance the support capability of a mobile communication system for other networks, thereby increasing the deployment flexibility of the network.
[0008] In a first aspect, a communication method is provided. The method can be executed by a first node, or by a component of the first node, such as a processor, chip, or chip system of the first node, or by a logic module or software that can implement all or part of the functions of the first node. The method includes: assigning a first port number, a second port number, and a third port number to a device-side converter port of a first network bridge; and sending first information to a second node, the first information being used to indicate the first port number, the second port number, and the third port number. The first network bridge includes: a first protocol data unit (PDU) session, a first network-side converter port, and a first device-side converter port; the first network-side converter port is a network-side converter port in the first network bridge associated with the first PDU session and the first node, and the first device-side converter port is a device-side converter port in the first network bridge associated with the first PDU session and the first terminal device. The first network bridge also includes: a first direct communication connection between the first terminal device and the second terminal device, a second device-side converter port and a third device-side converter port; the second device-side converter port is a device-side converter port in the first network bridge associated with the first direct communication connection and the first terminal device, and the third device-side converter port is a device-side converter port in the first network bridge associated with the first direct communication connection and the second terminal device.
[0009] Based on this solution, the bridge provided by this application includes a PDU session and its associated converter port, as well as a direct communication connection between terminal devices and its associated device-side converter port, and the first node is able to assign a port number to the device-side converter port of the bridge, so that the PDU session (such as the user plane tunnel included in the PDU session) and the direct communication connection can be used to support the integration of mobile communication systems (such as 5GS) and other networks (such as TSN), thereby improving the mobile communication system's support capabilities for other networks and thereby improving the deployment flexibility of the network.
[0010] In one possible design, the first information is further used to indicate that the first port number is the port number of the device-side converter port associated with the first PDU session. The first information is further used to indicate that the second port number and the third port number are the port numbers of the device-side converter port associated with the direct communication connection; or, the first information is further used to indicate that the second port number and the third port number are the port numbers of the device-side converter port associated with the first direct communication connection; or, the first information is further used to indicate that the second port number is the port number of the device-side converter port associated with the first direct communication connection and the first terminal device, and the third port number is the port number of the device-side converter port associated with the first direct communication connection and the second terminal device.
[0011] Based on this possible design, through the indication of the first information, the second node can be informed that the first port number is the device-side converter port associated with the PDU session, and the second port number and the third port number are the device-side converter ports associated with the direct communication connection, so that the first node and the second node have the same understanding of each port number, reducing the impact on subsequent business transmission.
[0012] In one possible design, before allocating the second port number and the third port number to the device-side converter port of the first network bridge, the method also includes: receiving second information from a third node, the second information being used to instruct the first node to allocate a port number to the device-side converter port associated with the direct communication connection in the first network bridge.
[0013] Based on this possible design, the first node may allocate a port number to the device-side converter port associated with the direct communication connection in the first network bridge based on the instruction of the third node.
[0014] In one possible design, the second information includes the number of ports and / or the number of direct communication connections. The number of ports is the number of device-side converter ports in the first network bridge that are associated with the direct communication connections and that require port numbers to be allocated by the first node. The number of direct communication connections is used to determine the number of device-side converter ports in the first network bridge that are associated with the direct communication connections and that require port numbers to be allocated by the first node.
[0015] Based on this possible design, the first node can allocate a reasonable number of port numbers to the device-side converter ports associated with the direct communication connections in the first bridge based on the number of ports and / or the number of direct communication connections, avoiding the first node allocating too few or too many port numbers.
[0016] In one possible design, before allocating the second port number and the third port number to the device-side converter port of the first network bridge, the method further includes: receiving third information from a third node, the third information including information of the first direct communication connection.
[0017] Based on this possible design, the first node can assign a port number to the device-side converter port associated with the direct communication connection based on the direct communication connection information. Furthermore, because the first node can obtain the direct communication connection information, in this scenario, the first node can further determine the correspondence between the port number and the port.
[0018] In one possible design, the third information includes a first layer 2 identifier and / or a second layer 2 identifier, wherein the first layer 2 identifier is an identifier associated with the first direct communication connection of the first terminal device, and the second layer 2 identifier is an identifier associated with the first direct communication connection of the second terminal device.
[0019] In one possible design, the third information includes an identifier of the first direct communication connection.
[0020] In one possible design, the third information includes at least one of the following: first identification information, first application information, second identification information, second application information, port management capability information corresponding to the second device-side converter port, residence time corresponding to the second device-side converter port, port management capability information corresponding to the third device-side converter port, or residence time corresponding to the third device-side converter port. The first identification information includes at least one of the following: the media access control (MAC) address of the second device-side converter port, the international mobile subscriber identity (IMSI) of the first terminal device, the temporary mobile subscriber identity (TMSI) of the first terminal device, or the international mobile equipment identity (IMEI) of the first terminal device. The first application information includes at least one of the following: an application identifier associated with the first direct communication connection, an application group identifier associated with the first direct communication connection, an application layer identifier associated with the first direct communication connection, or an identifier of the network served by the first terminal device. The second identification information includes at least one of the following: the MAC address of the third device-side converter port, the IMSI of the second terminal device, the TMSI of the second terminal device, or the IMEI of the second terminal device. The second application information includes at least one of the following: an application identifier associated with the first direct communication connection, an application group identifier associated with the first direct communication connection, an application layer identifier associated with the first direct communication connection, or an identifier of a network served by the second terminal device.
[0021] In one possible design, the third node is a session management network element, a policy control network element, an application function network element, a first terminal device, or a second terminal device.
[0022] In one possible design, the first network bridge also includes: a second PDU session and a fourth device-side converter port; the fourth device-side converter port is a device-side converter port in the first network bridge associated with the second PDU session and the second terminal device.
[0023] In a second aspect, a communication method is provided. The method can be executed by a second node, or by a component of the second node, such as a processor, chip, or chip system of the second node, or by a logic module or software that implements all or part of the functions of the second node. The method includes: obtaining a first port number, a second port number, and a third port number of a device-side converter port of a first network bridge; and sending fourth information to a fourth node, the fourth information indicating the first port number, the second port number, and the third port number, wherein the first port number is the port number of the first device-side converter port, the second port number is the port number of the second device-side converter port, and the third port number is the port number of the third device-side converter port. The first network bridge includes: a first protocol data unit (PDU) session, a first network-side converter port, and a first device-side converter port; the first network-side converter port is the network-side converter port of the first network bridge associated with the first PDU session and the first node, and the first device-side converter port is the device-side converter port of the first network bridge associated with the first PDU session and the first terminal device. The first network bridge also includes: a first direct communication connection between the first terminal device and the second terminal device, a second device-side converter port and a third device-side converter port; the second device-side converter port is a device-side converter port in the first network bridge associated with the first direct communication connection and the first terminal device, and the third device-side converter port is a device-side converter port in the first network bridge associated with the first direct communication connection and the second terminal device.
[0024] Based on this solution, the bridge provided by this application includes PDU sessions and their associated converter ports, as well as direct communication connections between terminal devices and their associated device-side converter ports, and the first node can assign port numbers to the device-side converter ports of the bridge, so that PDU sessions and direct communication connections can be used to support the integration of mobile communication systems (such as 5GS) and other networks (such as TSN), thereby improving the mobile communication system's support capabilities for other networks and thereby improving the deployment flexibility of the network.
[0025] In one possible design, the fourth information is also used to indicate at least one of the following: the first port number is the port number of the device side converter port associated with the PDU session, the second port number and the third port number are the port numbers of the device side converter port associated with the direct communication connection, the second port number and the third port number are the port numbers of the device side converter port associated with the same direct communication connection, the media access control MAC address of the second device side converter port, the residence time corresponding to the second device side converter port, the port management capability information corresponding to the second device side converter port, the MAC address of the third device side converter port, the residence time corresponding to the third device side converter port, or the port management capability information corresponding to the third device side converter port.
[0026] In one possible design, obtaining the first port number, second port number, and third port number of the device-side converter port of the first bridge includes: receiving first information from a first node, where the first information is used to indicate the first port number, the second port number, and the third port number.
[0027] In one possible design, the first information is further used to indicate that the first port number is the port number of the device-side converter port associated with the first PDU session. The first information is further used to indicate that the second port number and the third port number are the port numbers of the device-side converter port associated with the direct communication connection; or, the first information is further used to indicate that the second port number and the third port number are the port numbers of the device-side converter port associated with the first direct communication connection; or, the first information is further used to indicate that the second port number is the port number of the device-side converter port associated with the first direct communication connection and the first terminal device, and the third port number is the port number of the device-side converter port associated with the first direct communication connection and the second terminal device.
[0028] In one possible design, the method further includes sending second information to the first node, where the second information is used to instruct the first node to assign a port number to a device-side converter port associated with the direct communication connection in the first network bridge.
[0029] In one possible design, the second information includes the number of ports and / or the number of direct communication connections. The number of ports is the number of device-side converter ports in the first network bridge that are associated with the direct communication connections and that require port numbers to be allocated by the first node. The number of direct communication connections is used to determine the number of device-side converter ports in the first network bridge that are associated with the direct communication connections and that require port numbers to be allocated by the first node.
[0030] In one possible design, before receiving the first information from the first node, the method further includes: receiving fifth information from the first terminal device or the second terminal device, where the fifth information is information of the first direct communication connection.
[0031] In one possible design, obtaining the first port number, second port number, and third port number of the device-side converter port of the first bridge includes: receiving first indication information from the first node, the first indication information being used to indicate the first port number; and allocating the second port number and the third port number.
[0032] In one possible design, the first network bridge also includes: a second PDU session and a fourth device-side converter port; the fourth device-side converter port is the device-side converter port corresponding to the second terminal device associated with the second PDU session in the first network bridge.
[0033] Among them, the technical effects brought about by any possible design of the second aspect can refer to the technical effects brought about by the corresponding design in the above-mentioned first aspect, and will not be repeated here.
[0034] In a third aspect, a communication method is provided. The method can be executed by a fourth node, or by a component of the fourth node, such as a processor, chip, or chip system of the fourth node, or by a logic module or software capable of implementing all or part of the fourth node's functionality. The method includes: determining sixth information, the sixth information being used to indicate a first network bridge; and sending the sixth information to a fifth node. The first network bridge includes: a first protocol data unit (PDU) session, a first network-side converter port, and a first device-side converter port; the first network-side converter port being the network-side converter port associated with the first PDU session and the first node, and the first device-side converter port being the device-side converter port associated with the first PDU session and the first terminal device. The first network bridge also includes: a first proximity service connection direct communication connection between the first terminal device and a second terminal device, a second device-side converter port, and a third device-side converter port; the second device-side converter port being the device-side converter port associated with the first direct communication connection and the first terminal device, and the third device-side converter port being the device-side converter port associated with the first direct communication connection and the second terminal device.
[0035] Based on this solution, the bridge provided by this application includes PDU sessions and their associated converter ports, as well as direct communication connections between terminal devices and their associated device-side converter ports, so that PDU sessions and direct communication connections can be used to support the integration of mobile communication systems (such as 5GS) and other networks (such as TSN), thereby improving the mobile communication system's support capabilities for other networks and thereby improving the deployment flexibility of the network.
[0036] In one possible design, the sixth information includes at least one of the following: an identifier of the first network bridge, the number of ports in the first network bridge, a first port number, a second port number, a third port number, or port pair information; the first port number is the port number of the first device side converter port, the second port number is the port number of the second device side converter port, and the third port number is the port number of the third device side converter port; the port pair information indicates a port pair in the first network bridge, the port pair includes a first port pair and a second port pair, the first port pair includes the first device side converter port and the first network side converter port, and the second port pair includes the second device side converter port and the third device side converter port.
[0037] Based on this possible design, the fifth node can learn the identifier of the first bridge, the port number of the port in the first bridge, the path in the first bridge, etc., so that the fifth node can reasonably schedule the first bridge.
[0038] In one possible design, the first network bridge also includes: a second PDU session and a fourth device-side converter port; the fourth device-side converter port is a device-side converter port in the first network bridge associated with the second PDU session and the second terminal device.
[0039] In combination with the first aspect, the second aspect, or the third aspect, in one possible design, a PDU session can be associated with at least one quality of service (QoS) flow, and each QoS flow can be associated with a user plane tunnel. Therefore, it can also be considered that the bridge provided in the present application includes a user plane tunnel, a network side converter port associated with the user plane tunnel, and a device side converter port. Furthermore, the bridge also includes a direct communication connection between terminal devices and a device side converter port associated with the direct communication connection.
[0040] In combination with the first aspect, the second aspect, or the third aspect, in a possible design, the direct communication connection can be a PC5 connection, and the two can be replaced with each other.
[0041] In combination with the first aspect, the second aspect, or the third aspect, in one possible design, the terminal device may include a module for mobile communication (which may include Uu communication and direct communication). In this scenario, the terminal device and the device-side converter port (or device-side converter) can be integrated into one device or entity as two or more (possibly corresponding to more than one device-side converter port or entity) functional modules; or, they can be deployed separately, for example, in two or more different devices or entities.
[0042] In combination with the first aspect, the second aspect, or the third aspect, in one possible design, the terminal device may include a device-side converter port (or a device-side converter). For example, the terminal device includes a mobile communication module (for example, a UE module) and a device-side converter port (or a device-side converter) module.
[0043] In a fourth aspect, a communication device is provided, which includes a unit or module, and the unit or module is used to execute any one of the methods described in the first to third aspects above.
[0044] In a fifth aspect, a communication device is provided for implementing various methods. The communication device may be the first node in the first aspect, or a device included in the first node, such as a chip or a chip system; or, the communication device may be the second node in the second aspect, or a device included in the second node, such as a chip or a chip system; or, the communication device may be the fourth node in the third aspect, or a device included in the fourth node, such as a chip or a chip system. The communication device includes a module, unit, or means corresponding to the implementation method, and the module, unit, or means may be implemented by hardware, software, or by executing the corresponding software implementation by hardware. The hardware or software includes one or more modules or units corresponding to the functions.
[0045] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module may be configured to implement the processing functionality of any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a transmitting module, respectively configured to implement the receiving functionality and the transmitting functionality of any of the above aspects and any possible implementations thereof.
[0046] In some possible designs, the transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver or a communication interface.
[0047] In a sixth aspect, a communication device is provided, comprising: a processor and a memory; the memory is configured to store computer instructions, and when the processor executes the instructions, the communication device performs the method described in any aspect. The communication device may be the first node in the first aspect, or a device included in the first node, such as a chip or a chip system; or the communication device may be the second node in the second aspect, or a device included in the second node, such as a chip or a chip system; or the communication device may be the fourth node in the third aspect, or a device included in the fourth node, such as a chip or a chip system.
[0048] In a seventh aspect, a communication device is provided, comprising: a processor and a communication interface; the communication interface is configured to communicate with a module outside the communication device; and the processor is configured to execute a computer program or instruction to cause the communication device to perform the method described in any aspect. The communication device may be the first node in the first aspect, or a device included in the first node, such as a chip or a chip system; or the communication device may be the second node in the second aspect, or a device included in the second node, such as a chip or a chip system; or the communication device may be the fourth node in the third aspect, or a device included in the fourth node, such as a chip or a chip system.
[0049] In an eighth aspect, a communication device is provided, comprising: at least one processor; the processor is configured to execute a computer program or instruction stored in a memory, so that the communication device performs the method described in any aspect. The memory may be coupled to the processor, or may be independent of the processor. The communication device may be the first node in the first aspect, or a device included in the first node, such as a chip or a chip system; or the communication device may be the second node in the second aspect, or a device included in the second node, such as a chip or a chip system; or the communication device may be the fourth node in the third aspect, or a device included in the fourth node, such as a chip or a chip system.
[0050] In a ninth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer-readable storage medium is run on a communication device, the communication device can execute the method described in any one of the aspects.
[0051] In a tenth aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, enables the communication device to execute the method described in any one of the aspects.
[0052] In an eleventh aspect, a communication device is provided (for example, the communication device may be a chip or a chip system), which includes a processor for implementing the functions involved in any one of the first to third aspects.
[0053] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.
[0054] In some possible designs, when the device is a chip system, it can be composed of a chip or include a chip and other discrete devices.
[0055] It can be understood that when the communication device provided in any one of the fourth to eleventh aspects is a chip, the sending action / function of the communication device can be understood as output information, and the receiving action / function of the communication device can be understood as input information.
[0056] Among them, the technical effects brought about by any design method in the fourth to eleventh aspects can refer to the technical effects brought about by different design methods in the first to third aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0057] FIG1 is a schematic diagram of the structure of a TSN network provided by this application;
[0058] FIG2 is a schematic diagram of the structure of a UPF-based 5GS bridge provided by this application;
[0059] FIG3 is a schematic diagram of a bridge structure including a PC5 connection and a PDU session provided by the present application;
[0060] FIG4 is a schematic diagram of an integrated structure of a mobile communication system and TSN provided by the present application;
[0061] FIG5 is a flow chart of a communication method provided by the present application;
[0062] FIG6 is a flow chart of another communication method provided by the present application;
[0063] FIG7 is a flow chart of another communication method provided by the present application;
[0064] FIG8 is a flow chart of another communication method provided by the present application;
[0065] FIG9 is a schematic structural diagram of a communication device provided by the present application;
[0066] FIG10 is a schematic structural diagram of another communication device provided in this application. DETAILED DESCRIPTION
[0067] In the description of this application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in this application is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
[0068] In the description of this application, unless otherwise specified, "plurality" means two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.
[0069] In addition, to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different.
[0070] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.
[0071] It will be understood that the “embodiment” mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It will be understood that in the various embodiments of the present application, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
[0072] It can be understood that in this application, "when" and "if" both mean that corresponding processing will be taken under certain objective circumstances, and do not limit the time, nor do they require any judgment action when implementing, nor do they mean that there are other limitations.
[0073] It is understood that some optional features in the embodiments of the present application may, in certain scenarios, be implemented independently of other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. They may also be combined with other features in certain scenarios as needed. Accordingly, the devices provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described in detail here.
[0074] In this application, unless otherwise specified, the same or similar parts between the various embodiments can refer to each other. In this application, unless otherwise specified and there is no logical conflict between the various embodiments, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following description of the embodiments of this application does not constitute a limitation on the scope of protection of this application.
[0075] Time sensitive networking (TSN) defines a time-sensitive mechanism for Ethernet data transmission, adding determinism and reliability to standard Ethernet.
[0076] For example, a TSN architecture based on centralized configuration can be shown in Figure 1. Referring to Figure 1, the architecture mainly includes a talker, a listener, a bridge, a centralized user configuration (CUC) node, and a centralized network configuration (CNC) node. The talker and listener can be collectively referred to as TSN end stations.
[0077] It should be noted that the number of nodes and network topology shown in Figure 1 are only examples and are not specifically limited in the present application. The following is a brief introduction to the functions of each node in Figure 1:
[0078] A talker is the sender of a service flow and can also be called a sending device. A listener is the receiver of a service flow and can also be called a receiving device. TSN can have multiple senders and multiple receivers. Each sender can send service data to multiple receivers, and each receiver can receive service data from multiple senders. Each sender can support multiple services, and each service can be sent to only one receiver or to multiple receivers. Each sender can also be a receiver, and each receiver can also be a sender.
[0079] Bridge: Also known as a switch. Responsible for scheduling and forwarding traffic flows based on forwarding rules and scheduling information issued by the CNC node. TSN can have multiple bridges, each of which can connect to multiple senders, multiple bridges, or multiple receivers.
[0080] For example, a bridge can have multiple ingress ports and multiple egress ports, so that the bridge can receive data from multiple senders or receive data forwarded by multiple other bridges, and then forward the received data to the receiver or to other bridges.
[0081] In addition, in addition to forwarding business flows, the bridge in TSN also has other functions, such as topology discovery function, determining the bridge identifier and the bridge port identifier, supporting protocols such as the link layer discovery protocol (LLDP), and for example, determining the transmission delay, and after detecting the internal transmission delay of the bridge, reporting the detected transmission delay to the CNC node, etc. The embodiments of the present application do not make specific limitations on this.
[0082] CUC node: Responsible for discovering and managing TSN terminals. For example, the CUC node can obtain the service flow requirements of the TSN terminal and send a flow creation request carrying the service flow requirements to the CNC node; or the CUC node can configure the TSN terminal according to the instructions of the CNC node.
[0083] CNC node: responsible for managing the topology of the TSN user plane (including the topology between each TSN terminal and the bridge) and the capability information of the bridge, and generates the end-to-end (E2E) path of the business flow and the forwarding rules on each bridge based on the flow creation request carrying the business flow requirements provided by the CUC node. Then, the forwarding rules on the bridge (such as the flow characteristics of the business flow, the identification of the inlet and outlet ports during business transmission, etc.) and scheduling information (such as the time information of the inlet port, the flow classification information corresponding to the outlet port, etc.) are sent to the corresponding bridge.
[0084] Traditionally, TSN is deployed over wired Ethernet. With the development of fifth-generation (5G) mobile communication technology, current 5G networks have already implemented support for TSN, making some TSN connections wireless, thereby expanding TSN deployment scenarios.
[0085] For example, the 5G system (5GS) can be integrated into TSN in the form of a TSN bridge, which can be called a 5GS bridge. Specifically, 5GS can interoperate with TSN through a TSN translator (TT). TT can be divided into network-side TT (NW-TT) and device-side TT (DS-TT).
[0086] Typically, a 5GS bridge is based on a user plane function (UPF), that is, a 5GS bridge is associated with a UPF. For example, a 5GS bridge consists of an NW-TT port on the UPF side, a user plane tunnel between the user equipment (UE) and the UPF, and a DS-TT port.
[0087] Among them, UPF is an important component of the 5GS core network, and is mainly responsible for receiving user plane data of the UE and sending user plane data to the UE in the user plane protocol stack. The user plane tunnel between the UE and the UPF can be a user plane tunnel associated with the quality of service (QoS) flow in the protocol data unit (PDU) session. In an embodiment of the present application, the user plane tunnel between the UE and the UPF can also be replaced by a PDU session between the UE and the UPF. After the UE and the UPF establish a connection, at least one PDU session will be established. The PDU session can be used for uplink data transmission of the UE, and can also be used for downlink data transmission. The NW-TT port can provide a connection between the UPF in the 5GS bridge and the TSN network; the DS-TT port is associated with the PDU session, and the DS-TT port can provide a connection between the UE and the TSN network in the 5GS bridge.
[0088] Typically, a DS-TT port is associated with only one PDU session in a bridge. PDU sessions connected to the same TSN network through a UPF are included in one 5GS bridge.
[0089] For example, as shown in Figure 2, 5GS includes two TSN-capable UPFs (i.e., UPF-A and UPF-B) and two TSN-capable UEs (i.e., UE1 and UE2). A PDU session 1A is established between UPF-A and UE1, a PDU session 1B is established between UPF-B and UE1, and a PDU session 2B is established between UPF-B and UE2.
[0090] Because a 5GS bridge is associated with a UPF, the network includes two 5GS bridges. Bridge A is associated with UPF-A and includes the NW-TT port on the UPF-A side, the PDU session 1A between UPF-A and UE1 (which can also be understood as the user plane tunnel associated with PDU session 1A), and the DS-TT port 1A on the UE1 side that is associated with PDU session 1A.
[0091] Bridge B is associated with UPF-B, including the NW-TT port on the UPF-B side, the PDU session 1B between UPF-B and UE1 (which can also be understood as the user plane tunnel associated with PDU session 1B), and the DS-TT port 1B associated with PDU session 1B on the UE1 side. It also includes the PDU session 2B between UPF-B and UE2 (which can also be understood as the user plane tunnel associated with PDU session 2B), and the DS-TT port 2B associated with PDU session 2B on the UE2 side.
[0092] As shown in Figure 2, Bridge A and Bridge B can connect to the TSN network. For example, UE1 can connect to a TSN bridge (e.g., a common TSN bridge) or a TSN terminal (e.g., a talker / listener) via two DS-TT ports. UPF-A or UPF-B can connect to the TSN system via an NW-TT port.
[0093] In addition, in order to support TSN, the 5GS core network needs to support the TSN application function (TSN AF). The TSN AF can be used to provide control plane conversion or translation functions for the integration of 5GS and TSN networks, such as interacting with the CNC. Under this architecture, the core network processes in 5GS, the communication between the UE and the radio access network (RAN) and the UPF, etc. remain hidden in the TSN network, that is, the relevant processes implemented by the 5GS bridge through 5GS are transparent to the entire TSN network. In other words, for the CNC, there is no additional difference between the 5GS bridge and other ordinary TSN bridges.
[0094] The capabilities of each port on the UE / DS-TT side and the UPF / NW-TT side can be integrated as part of the 5GS bridge configuration, reported to the TSN AF, and then further sent to the CNC through the TSN AF for the 5GS bridge to register in the TSN and update the registration information.
[0095] For example, when a UE establishes a PDU session with a UPF in order to support TSN communication, the UPF can allocate a DS-TT port number for the DS-TT port associated with the UE, and the DS-TT port number is associated with the PDU session between the UE and the UPF. The UPF can also report the DS-TT port number to the TSN AF. For example, the UPF can report the DS-TT port number to the TSN AF through the session management function (SMF) and the policy control function (PCF). The TSN AF can finally report information such as the port of the entire bridge to the CNC.
[0096] For example, in the example shown in Figure 2, TSN AF can collect basic information about Bridge A and Bridge B and report it to the CNC. In addition, TSN AF can also receive configuration information from the CNC to assist 5GS in managing the transmission of TSN service data.
[0097] As mentioned above, the currently defined 5GS bridge is based on Uu communication and does not support the 5GS bridge based on sidelink (SL) communication, which limits the function of 5GS in supporting TSN communication. That is, 5GS's support for TSN communication is limited, affecting the flexibility of TSN deployment.
[0098] Furthermore, 5GS bridges based solely on Uu communication may experience high transmission latency, thus impacting TSN service performance. For example, as shown in Figure 2, assuming the sender of TSN service data is a TSN bridge / terminal connected to the DS-TT port corresponding to UE1, and the receiver is a TSN bridge / terminal connected to the DS-TT port corresponding to UE2, then based on the architecture shown in Figure 2, the TSN service data must be transmitted via the ingress port DS-TT1B and PDU session 1B to UPF-B, and then transmitted via PDU session 2B to the egress port DS-TT2B for output. This transmission process may experience high transmission latency.
[0099] Based on this, this application provides a communication method that provides a hybrid bridge based on SL communication and Uu communication, improving the mobile communication system's support for TSN, thereby enhancing the deployment flexibility of TSN. In addition, based on the flexible TSN deployment, it can reduce transmission latency in the bridge and improve service performance.
[0100] The technical solutions of the embodiments of the present application can be used in various communication systems, which may be a third generation partnership project (3GPP) communication system, for example, a fifth generation (5G) or sixth generation (6G) mobile communication system, a sidelink (SL) system, an ultra-wideband (UWB) system, a vehicle to everything (V2X) system, or a device to device (D2D) communication system, a machine to machine (M2M) communication system, an Internet of Things (IoT), and other next generation communication systems. The communication system may also be a non-3GPP communication system, such as a wireless local area network (WLAN) system such as Wi-Fi, without limitation.
[0101] The technical solutions of the embodiments of the present application can be applied to various communication scenarios, for example, one or more of the following communication scenarios: smart home, D2D, V2X, industrial network, IoT, or other scenarios with time-sensitive communication (TSC) requirements.
[0102] Among them, the above-mentioned communication systems and communication scenarios applicable to the present application are only examples. The communication systems and communication scenarios applicable to the present application are not limited to these. They are uniformly described here and will not be repeated below.
[0103] In the communication method of the present application, a network bridge (hereinafter referred to as a first network bridge) is provided. The model of the first network bridge provided by the present application is first introduced below.
[0104] Optionally, the first bridge can provide data forwarding services for the first network. For example, the first network can be Ethernet, such as TSN. Of course, the first network can also be other Ethernets with latency-sensitive communication requirements, which is not specifically limited in this application. The first bridge can communicate with other bridges in the first network, and with data senders or data receivers in the first network.
[0105] Optionally, the first network bridge may include a transmission path based on a user plane tunnel and a transmission path based on a direct communication connection.
[0106] Exemplarily, the user plane tunnel is used to provide a user plane connection between the terminal device and the UPF (or it can also be understood as between the RAN and the UPF). Exemplarily, in 5GS, the user plane tunnel can be a user plane tunnel associated with the QoS flow in the PDU session, or it can be a user plane tunnel associated with the PDU session. In an embodiment of the present application, the user plane tunnel can be replaced by a PDU session, that is, it can be considered that the first bridge includes a transmission path based on the PDU session and a transmission path based on a direct communication connection. In addition, the PDU session can also be replaced by a user plane tunnel. In the future evolving public land mobile network (PLMN), such as a 6G mobile communication system, the user plane tunnel can also be a user plane tunnel associated with the QoS flow in the PDU session, or there can be other implementation forms, which are not specifically limited in this application. The direct communication connection can also be understood as a layer 2 connection (Layer 2Link), or an SL connection, or a D2D connection, or a proximity-based services (ProSe) connection, or a PC5 (ProSe connection 5) connection, etc.
[0107] It should be noted that the following embodiments of this application use a PC5 connection as an example for explanation, that is, the PC5 connection in the following embodiments of this application can be replaced by a direct communication connection. Of course, it can also be replaced by other implementation forms of the direct communication connection, such as a layer 2 connection, an SL connection, or a D2D connection.
[0108] As a possible implementation, the first network bridge includes: a first PDU session, a first network-side converter port, and a first device-side converter port. The first PDU session is a PDU session between the first node and the first terminal device. The first network-side converter port is a network-side converter port in the first network bridge that is associated with the first PDU session and the first node. The first device-side converter port is a device-side converter port in the first network bridge that is associated with the first PDU session and the first terminal device. That is, the first PDU session is associated with two converter ports, wherein the port on the first node (e.g., UPF) side is the first network-side converter port, and the port on the first terminal device side is the first device-side converter port. It can also be understood that the first network-side converter port and the first device-side converter port are associated with the first PDU session, the first network-side converter port is also associated with the first node, and the first device-side converter port is also associated with the first terminal device. Exemplarily, this part can be understood as a transmission path based on the PDU session in the first network bridge.
[0109] The first network bridge further includes: a PC5 connection between at least two terminal devices, and a device-side converter port associated with the PC5 connection and the at least two terminal devices. Exemplarily, this portion can be understood as a transmission path based on the PC5 connection in the first network bridge.
[0110] Exemplarily, the association of a device-side converter port with a terminal device can be understood as follows: the device-side converter port serves as an input port and / or output port of the first network bridge, providing a connection between the terminal device and the first network. Optionally, a PC5 connection between at least two terminal devices can mean that each of the at least two terminal devices has a PC5 connection with at least one other terminal device. Taking the at least two terminal devices including terminal device A, terminal device B, and terminal device C as an example, the PC5 connection between the at least two terminal devices can include at least one of the following: a PC5 connection between terminal device A and terminal device B, a PC5 connection between terminal device A and terminal device C, and a PC5 connection between terminal device B and terminal device C.
[0111] Optionally, there is at least one terminal device among the two terminals associated with a certain PC5 in the first network bridge, and a PDU session exists (or is established) between the terminal device and the first node.
[0112] Exemplarily, based on the above example, when there is a PC5 connection between terminal device A and terminal device B, at least one terminal device among terminal device A and terminal device B has a PDU session with the first node; when there is a PC5 connection between terminal device A and terminal device C, at least one terminal device among terminal device A and terminal device C has a PDU session with the first node; when there is a PC5 connection between terminal device B and terminal device C, at least one terminal device among terminal device B and terminal device C has a PDU session with the first node.
[0113] Taking the example of at least two terminal devices including a first terminal device and a second terminal device, the first network bridge also includes: a first PC5 connection between the first terminal device and the second terminal device, a second device-side converter port, and a third device-side converter port. The second device-side converter port is a device-side converter port in the first network bridge that is associated with the first PC5 connection and the first terminal device, and the third device-side converter port is a device-side converter port in the first network bridge that is associated with the first PC5 connection and the second terminal device. That is, the first PC5 connection is associated with two device-side converter ports, of which the second device-side converter port is on the first terminal device side, and the third device-side converter port is on the second terminal device side. It can also be understood that the second device-side converter port and the third device-side converter port are associated with the first PC5 connection. The second device-side converter port is also associated with the first terminal device, and the third device-side converter port is also associated with the second terminal device.
[0114] Optionally, the first network bridge includes both the PDU session established through the first node and the PC5 connection between the terminal devices. Among them, the device-side converter port associated with the PDU session (such as the first device-side converter port) and the device-side converter port associated with the PC5 connection (such as the second device-side converter port) associated with the same terminal device can be the same or different, and this application does not make specific restrictions on this. That is, the first device-side converter port associated with the first terminal device and the second device-side converter port associated with the first terminal device can be the same or different. In addition, in the following embodiments of the present application, the two different device-side converter ports are used as an example for illustration.
[0115] Optionally, the network-side converter port and the device-side converter port are used to implement interoperability between the mobile communication system (such as 5GS) and the first network. The network-side converter port can serve as an input port and / or output port of the first network bridge, providing a connection between the first node in the mobile communication system and the first network. The device-side converter port can also serve as an input port and / or output port of the first network bridge, providing a connection between a terminal device in the mobile communication system and the first network.
[0116] For example, when the first network is TSN, the network-side converter port may be an NW-TT port, and the device-side converter may be a DS-TT port.
[0117] Optionally, the first node is primarily responsible for processing user messages, such as forwarding and billing. For example, in a 5G mobile communication system, the first node may be a UPF network element. In future mobile communication systems, such as 6G mobile communication systems, the first node may still be a UPF network element, or a network element with UPF-like functions. The first node may also have other names, which are not specifically limited in this application.
[0118] Optionally, the terminal device may include a module for mobile communication (which may include Uu communication and direct communication). In this scenario, the terminal device and the device-side converter port (or device-side converter) may be integrated into one device or entity as two or more (possibly corresponding to more than one device-side converter port or entity) functional modules; or, they may be deployed separately, for example, in two or more different devices or entities, such as the device-side converter port or device-side converter may be an external device of the terminal device. The device-side converter may also be understood as a device-side converter entity, which may be used to control and manage the device-side converter port.
[0119] Optionally, the terminal device may include a device-side converter port (or a device-side converter). For example, the terminal device includes a mobile communication module (eg, a UE module) and a device-side converter port (or a device-side converter) module.
[0120] Exemplarily, as shown in Figure 2, when the terminal device includes a module for mobile communication, and the terminal device and the device-side converter port (device-side converter) are two or more functional modules, the terminal device can be UE1, and the device-side converter ports associated with the terminal device include DS-TT 1A and DS-TT 1B. UE1, DS-TT 1A, and DS-TT 1B can be integrated into one device or entity, or can be independently deployed in multiple different devices or entities. When the terminal device includes a mobile communication module and a device-side converter port (or device-side converter) module, the terminal device can include UE1, DS-TT 1A, and DS-TT 1B. Among them, UE1 can be understood as the mobile communication module of the terminal device, and DS-TT 1A and DS-TT 1B can be understood as the device-side converter port (or device-side converter) modules of the terminal device.
[0121] In the embodiments of this application, the terminal device and the device-side converter port are mainly used as two modules for description. In the case where the terminal device includes a device-side converter port, the device-side converter port associated with the terminal device can also be understood as the device-side converter port of the terminal device or the device-side converter port included in the terminal device. The terminal device in the text can be understood as the terminal device or the mobile communication module (such as UE) in the terminal device according to the situation. In addition, this application does not specifically limit the specific implementation form of the terminal device and the device-side converter port.
[0122] For example, taking the first network as TSN, the first node as UPF, the network side converter port as NW-TT port, and the device side converter port as DS-TT port as an example, a structural diagram of the first bridge can be shown in Figure 3. Referring to Figure 3, UE1 and UE2 can represent the above-mentioned first terminal device and the second terminal device. DS-TT1, DS-TT2, and DS-TT3 represent the above-mentioned first device side converter port, the second device side converter port, and the third device side converter port, respectively. The PC5 connection between UE1 and UE2 represents the above-mentioned first PC5 connection. The PDU session between UE1 and UPF represents the above-mentioned first PDU session. The DS-TT port can provide a connection between the UE and the TSN bridge / terminal, and the NW-TT port can provide a connection between the UPF and the TSN bridge / terminal.
[0123] It is understood that Figure 3 only illustrates the relevant nodes and connections in the data transmission process associated with the first bridge. In addition, in actual implementation, there may also be nodes (such as TSN AF, etc.) and connections related to the bridge configuration process (not shown in Figure 3).
[0124] Optionally, the transmission path based on the PC5 connection in the first network bridge may include only the PC5 connection between two terminal devices and the device-side converter ports corresponding to the two terminal devices. Alternatively, it may include PC5 connections between three or more terminal devices and the device-side converter ports associated with these terminal devices. For example, the first network bridge shown in FIG3 may also include a second PC5 connection between UE1 and UE3, a device-side converter port associated with the second PC5 connection and UE1, and a device-side converter port associated with the second PC5 connection and UE3.
[0125] Exemplarily, the transmission path based on the PC5 connection in the first network bridge may include: at least one PC5 connection and a device-side converter port associated with the at least one PC5 connection. Optionally, any one of the at least one PC5 connection needs to meet at least one of the following requirements:
[0126] 1) A PDU session exists (or has been established) between at least one terminal device associated with the PC5 and the first node included in the first network bridge;
[0127] 2) A PDU session exists (or has been established) between the two terminal devices associated with the PC5 and the first node included in the first network bridge;
[0128] 3) The PC5 connection is located on a specific resource pool or pools, bandwidth part (BWP) or frequency (also known as a channel or carrier);
[0129] 4) The PC5 connection is associated with one or more specific TSN applications or TSN networks.
[0130] Optionally, the PC5 connection between the terminal devices may be a unicast connection, a multicast connection, or a broadcast connection. The embodiment of the present application is described by taking a unicast connection as an example.
[0131] Optionally, on a unicast PC5 connection between two terminal devices, each of the two terminal devices has a layer 2 identifier (ID) for identifying the identity of the terminal device. The layer 2 identifier can be a source identifier or a destination identifier. In addition, multiple PC5 connections can be maintained (or established) between the two terminal devices, and different PC5 connections can correspond to different services, etc. Each terminal device can have a different layer 2 identifier on different PC5 connections. It can also be understood that each terminal device can associate different layer 2 identifiers with different PC5 connections.
[0132] Optionally, when a terminal device has multiple PC5 connections, the multiple PC5 connections of the terminal device can be associated with one device-side converter port on the terminal device side, that is, the multiple layer 2 identifiers of the terminal device (one-to-one corresponding to the multiple PC5 connections) can be associated with one device-side converter port.
[0133] Alternatively, the multiple PC5 connections of the terminal device can be associated with different device-side converter ports on the terminal device side, that is, the multiple layer 2 identifiers of the terminal device (one-to-one corresponding to the multiple PC5 connections) can be associated with different device-side converter ports.
[0134] Alternatively, within the same network bridge, multiple layer 2 identifiers of the terminal device (corresponding one-to-one with multiple PC5 connections) can be associated with different device-side converter ports. Furthermore, within different network bridges, multiple layer 2 identifiers of the terminal device belonging to different network bridges can be associated with different device-side converter ports, or they can be associated with the same device-side converter port.
[0135] For example, if there is a PC5 connection #1 between terminal device 1 and terminal device 2, and a PC5 connection #2 between terminal device 1 and terminal device 3, then terminal device 1 has two PC5 connections, namely PC5 connection #1 and PC5 connection #2. PC5 connection #1 and PC5 connection #2 can both correspond to device-side converter port #1 of terminal device 1; or, PC5 connection #1 and PC5 connection #2 can correspond to device-side converter port #1 and device-side converter port #2 of terminal device 1, respectively.
[0136] Optionally, among the above-mentioned at least two terminal devices, a PDU session may or may not exist between the other terminal devices except the first terminal device and the first node, and this application does not make any specific restrictions on this.
[0137] Optionally, when a PDU session exists between other terminal devices and the first node, the first network bridge may also include the PDU session, the network side converter port of the first node associated with the PDU session, and the device side converter port associated with the PDU session and other terminal devices.
[0138] For example, if a second PDU session exists between the second terminal device and the first node, the first network bridge may further include the second PDU session, a second network-side converter port, and a fourth device-side converter port. The second network-side converter port is the network-side converter port on the first network bridge associated with the second PDU session and the first node. The fourth device-side converter port is the device-side converter port on the first network bridge associated with the second PDU session and the second terminal device.
[0139] Optionally, the second network-side converter port and the first network-side converter port may be the same, that is, the second PDU session and the first PDU session may be associated with the same network-side converter port. Alternatively, the second network-side converter port and the first network-side converter port may be different, that is, the second PDU session and the first PDU session may be associated with different network-side converter ports.
[0140] The above describes the model of the first network bridge and the nodes and connections related to the data transmission process associated with the first network bridge. Furthermore, in actual implementations, nodes related to processes such as the configuration of the first network bridge may also be present. For example, in actual implementations, application function (AF) network elements (e.g., TSN AF network elements), mobility management network elements, session management network elements, policy control network elements, and network openness network elements may also be present.
[0141] Optionally, the AF network element is used to provide a control plane conversion or translation function for the integration of the mobile communication system and the first network. When the first network is TSN, the AF network element may be a TSN AF network element.
[0142] The mobility management network element is primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover. In a 5G mobile communication system, the mobility management network element may be an access and mobility management function (AMF) network element. In future mobile communication systems, such as a 6G mobile communication system, the mobility management network element may still be an AMF network element, or may have other names, which are not specifically limited in this application.
[0143] The session management network element is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating Internet Protocol (IP) addresses to users and selecting the UPF that provides message forwarding functions. In 5G mobile communication systems, the session management network element may be a session management function (SMF) network element. In future mobile communication systems, such as 6G mobile communication systems, the session management network element may still be an SMF network element, or may have other names, which are not specifically limited in this application.
[0144] The policy control network element is primarily responsible for providing policies, such as QoS policies, to mobility management network elements, session management network elements, and terminal devices. In 5G mobile communication systems, the policy control network element may be a policy control function (PCF) network element. In future mobile communication systems, such as 6G mobile communication systems, the policy control network element may still be a PCF network element, or may have other names, which are not specifically limited in this application.
[0145] In addition, the terminal device in the embodiments of the present application can be, for example, a wireless terminal in an IoT, V2X, D2D, M2M, 5G network, or a future evolved PLMN. The terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water (such as a ship); it can also be deployed in the air (such as an airplane, balloon, and satellite).
[0146] Exemplarily, the terminal device may be a narrowband terminal, a drone, an IoT device (e.g., a sensor, an electricity meter, a water meter, etc.), a V2X device, a station (ST) in a WLAN, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with a wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device (also referred to as a wearable smart device), a tablet computer or a computer with a wireless transceiver function, a virtual reality (VR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a smart home, or a similar device. The terminal device can be a mobile or fixed device, and this application does not specifically limit this.
[0147] For example, taking the terminal device as UE, the mobility management network element as AMF network element, the session management network element as SMF network element, the policy control network element as PCF network element, and the AF network element as TSN AF network element as an example, an application architecture provided by an embodiment of the present application can be shown in Figure 4.
[0148] Below with reference to accompanying drawing and above description, the method that embodiment of the present application provides is expanded and described.In embodiment of the present application, each node can perform some or all of the steps in embodiment of the present application, and these steps or operations are only examples, and embodiment of the present application can also perform other operations or the deformation of various operations.In addition, each step can be performed in the different order presented in embodiment of the present application, and it is possible not to perform all the operations in embodiment of the present application.
[0149] For example, the communication method provided in this application can be applied to a scenario where a mobile communication system serves as a bridge for a first network. Of course, it can also be applied to other scenarios with latency-sensitive communication requirements. This application does not specifically limit the application scenarios of this communication method. The above-mentioned exemplary application scenarios do not impose any limitations on the solutions of this application.
[0150] FIG5 is a flow chart of a communication method provided by the present application, which includes the following steps:
[0151] S501: A first node allocates a first port number, a second port number, and a third port number to a device-side converter port of a first network bridge.
[0152] Among them, the first network bridge includes a first PDU session, a first network-side converter port and a first device-side converter port, and also includes a first PC5 connection between the first terminal device and the second terminal device, a second device-side converter port and a third device-side converter port. In addition, it can also be considered that the first network bridge includes at least one first user plane tunnel (at least one first user plane tunnel can be a user plane tunnel associated with the first PDU session), a first network-side converter port and a first device-side converter port, and also includes a first PC5 connection between the first terminal device and the second terminal device, a second device-side converter port and a third device-side converter port. Please refer to the aforementioned relevant description of the first network bridge, which will not be repeated here.
[0153] Optionally, the first port number is the port number of the device-side converter port associated with the first PDU session. That is, the first port number is the port number of the first device-side converter port. For the second port number and the third port number:
[0154] As a first possible implementation, the first node may determine that the second port number and the third port number are device-side converter ports associated with the PC5 connection. However, the first node may not care about, perceive, or determine which PC5 connection in the first network bridge the second port number and the third port number are specifically associated with. For example, if the first network bridge includes other PC5 connections (such as the second PC5 connection) in addition to the first PC5 connection, the first node may not care about, perceive, or determine whether the second port number and the third port number are specifically associated with the first PC5 connection or the second PC5 connection.
[0155] As a second possible implementation, the first node may determine that the second port number and the third port number are device-side converter ports associated with the first PC5 connection. That is, the first node may determine the PC5 connection associated with the second port number and the third port number. However, the first PC5 connection is associated with two device-side converter ports, and the first node does not care about, perceive, or determine the correspondence between the second port number and the third port number and the two device-side converter ports.
[0156] As a third possible implementation, the first node can determine that the second port number is the port number of the device-side converter port associated with the first PC5 connection and the first terminal device (i.e., the second device-side converter port), and the third port number is the port number of the device-side converter port associated with the first PC5 connection and the second terminal device (i.e., the third device-side converter port). That is, the first node can determine that the second port number and the third port number are associated with the first PC5 connection, and can determine the correspondence between the second port number and the third port number and these two device-side converter ports. In other words, the second port number can be determined to be the port number of the second device-side converter port, and the third port number can be determined to be the port number of the third device-side converter port.
[0157] Optionally, the first node may allocate the first port number, the second port number, and the third port number to the device-side converter port of the first bridge in different processes or at different times, which will be described in subsequent embodiments and will not be elaborated here.
[0158] S502: Send first information to the second node. Correspondingly, the second node receives the first information from the first node.
[0159] The first information is used to indicate the first port number, the second port number, and the third port number. The second node may be a session management network element, a policy control network element, or an application function network element.
[0160] Optionally, the first information is further used to indicate that the first port number is the port number of the device-side converter port associated with the first PDU session.
[0161] Optionally, with respect to the second port number and the third port number: corresponding to the first possible implementation in step S501, the first information is further used to indicate that the second port number and the third port number are the port numbers of the device-side converter port associated with the PC5 connection. Corresponding to the second possible implementation in step S501, the first information is further used to indicate that the second port number and the third port number are the port numbers of the device-side converter port associated with the first PC5 connection. Corresponding to the third possible implementation in step S501, the first information is further used to indicate that the second port number is the port number of the device-side converter port associated with the first PC5 connection and the first terminal device, and the third port number is the port number of the device-side converter port associated with the first PC5 connection and the second terminal device.
[0162] Optionally, the first node may indicate the first port number, the second port number, and the third port number to the second node in different processes or messages. That is, the first information may be understood as a general term for information indicating these three port numbers, which will be described in subsequent embodiments and will not be elaborated here.
[0163] S503: The second node obtains a first port number, a second port number, and a third port number of a device-side converter port of the first network bridge.
[0164] Optionally, after receiving the first information, the second node may obtain the first port number of the device-side converter port of the first bridge according to the first information.
[0165] Optionally, the second and third port numbers can be obtained as follows:
[0166] In the case where the first information is further used to indicate that the second port number and the third port number are port numbers of the device-side converter ports associated with the PC5 connection, the second node may assign the second port number and the third port number to the first PC5 connection. In addition, the second node may also determine the second port number as the port number of the second device-side converter port associated with the first PC5 connection, and determine the third port number as the port number of the third device-side converter port associated with the first PC5 connection; or the second node may determine the second port number as the port number of the third device-side converter port associated with the first PC5 connection, and determine the third port number as the port number of the second device-side converter port associated with the first PC5 connection.
[0167] In the case where the first information is also used to indicate that the second port number and the third port number are the port numbers of the device-side converter ports associated with the first PC5 connection, the second node can determine the second port number as the port number of the second device-side converter port associated with the first PC5 connection, and determine the third port number as the port number of the third device-side converter port associated with the first PC5 connection; or, the second node can determine the second port number as the port number of the third device-side converter port associated with the first PC5 connection, and determine the third port number as the port number of the second device-side converter port associated with the first PC5 connection.
[0168] For the convenience of description, the following embodiment of the present application is explained by taking the example in which the second node determines the second port number as the port number of the second device side converter port associated with the first PC5 connection, and determines the third port number as the port number of the third device side converter port associated with the first PC5 connection, that is, the second port number is the port number of the second device side converter port, and the third port number is the port number of the third device side converter port.
[0169] When the first information is also used to indicate that the second port number is the port number of the device converter port connected to the first PC5 and associated with the first terminal device, and the third port number is the port number of the device side converter port associated with the first PC5 connection and the second terminal device, the second node can determine that the second port number is the port number of the second device side converter port, and the third port number is the port number of the third device side converter port.
[0170] Optionally, the second node may not rely on the first information to obtain the second port number and the third port number of the device-side converter port of the first network bridge. The second node may independently assign a port number to the device-side converter port associated with the PC5 connection in the first network bridge. For example, the second node may receive the PC5 connection information in the first network bridge from another node (such as a terminal device, PCF, or TSN AF), and then assign a port number to the device-side converter port associated with the PC5 connection in the first network bridge. In this case, the first node in S501 may not assign the second port number and the third port number, and the first information in S502 may not include information about the second port number and the third port number. The specific method will be described in subsequent embodiments and will not be repeated here.
[0171] S504: The second node sends fourth information to the fourth node. Correspondingly, the fourth node receives the fourth information from the second node.
[0172] Wherein, the fourth node is an application function network element. For example, when the first network is a TSN, the fourth node may be a TSN AF network element. When the second node is an application function network element, the second node and the fourth node are the same network element, and step S504 may not be performed.
[0173] The fourth information is used to indicate the first port number, the second port number, and the third port number. In step S504, the second node may determine that the first port number is the port number of the first device-side converter port, the second port number is the port number of the second device-side converter port, and the third port number is the port number of the third device-side converter port.
[0174] Optionally, when the second node is a session management network element, the session management network element may send the fourth information to the fourth node via the policy control network element. Exemplarily, the session management network element sends the fourth information to the policy control network element, which then forwards the fourth information to the fourth node. For example, the session management network element may send an Npcf_SMPolicyControl_Update service operation message to the policy control network element, with the fourth information carried in the message. The policy control network element may send an Npcf_PolicyAuthorization_Subscribe operation message to the fourth node, with the fourth information carried in the message.
[0175] S505: The fourth node determines sixth information, where the sixth information is used to indicate the first network bridge.
[0176] Optionally, the fourth node may determine the sixth information based on the fourth information from the second node. Exemplarily, the fourth node determining the sixth information may include: the fourth node determining the structure of the first bridge, thereby determining the sixth information for indicating the first bridge.
[0177] S506: The fourth node sends sixth information to the fifth node. Correspondingly, the fifth node receives the sixth information from the fourth node.
[0178] The fifth node may be a control node in the first network. For example, when the first network is TSN, the fifth node may be a TSN CNC node.
[0179] Optionally, the fourth node sending the sixth information to the fifth node can also be understood as the fourth node registering or updating the first bridge with the fifth node. After receiving the sixth information, the fifth node can configure the first bridge, etc., which is not specifically limited in this application.
[0180] Based on this solution, the network bridge provided by this application includes a PDU session and its associated converter port, as well as a PC5 connection between terminal devices and its associated device-side converter port, and the first node is capable of assigning a port number to the device-side converter port of the network bridge, thereby being able to utilize the PDU session and PC5 connection to support the integration of mobile communication systems (such as 5GS) and other networks (such as TSN), thereby improving the mobile communication system's support capabilities for other networks and thereby improving the deployment flexibility of the network. In addition, based on flexible network deployment, it is possible to reduce transmission delays in the network, thereby improving service performance.
[0181] Exemplarily, in the example shown in FIG2 , based on the solution provided by the present application, bridge B may also include a PC5 connection between UE1 and UE2, a DS-TT port associated with the PC5 connection and UE1 (denoted as DS-TT 1C), and a DS-TT port associated with the PC5 connection and UE2 (denoted as DS-TT 2C). Then, assuming that the sender of the TSN service data is the TSN bridge / terminal connected to the DS-TT port associated with UE1, and the receiver is the TSN bridge / terminal connected to the DS-TT port associated with UE2, the TSN service data can be transmitted to UE2 through the ingress port DS-TT 1C and the PC5 connection, and then transmitted from UE2 to the output port DS-TT 2C and output. Compared with the original transmission path, there is no need to transmit through two PDU sessions, thereby reducing the service transmission delay.
[0182] As shown in Figure 6, the embodiment of the present application further provides a communication method, which can be understood as an application of the communication method shown in Figure 5. Referring to Figure 6, the communication method includes the following steps:
[0183] S600: Authorize multiple terminal devices related to the first network, wherein the multiple terminal devices include a first terminal device and a second terminal device.
[0184] Optionally, in step S600, each of the multiple terminal devices may separately determine basic parameters for supporting the first network bridge, such as a mapping relationship between a service type and a destination ID, an Internet Protocol (IP) address of an AF network element, a Media Access Control (MAC) address of the AF network element, a used frequency band, etc. Exemplarily, the destination ID is essentially a layer 2 ID, and the service type and destination ID are used to subsequently establish a PC5 connection.
[0185] Optionally, the basic parameters for supporting the first network bridge may be provided by the terminal device itself, that is, these parameters may be configured when the terminal device leaves the factory, for example, by a universal integrated circuit card (UICC). Alternatively, the basic parameters for supporting the first network bridge may be configured by the network, for example, by a policy control network element. Alternatively, the basic parameters for supporting the first network bridge may also be determined by other means, which is not specifically limited in this application.
[0186] S601. A first PDU session is established between a first terminal device and a first node.
[0187] Exemplarily, the first PDU session is used for delay-sensitive communication, or the first PDU session is used to provide data transmission for the first network.
[0188] Optionally, in step S601, the first terminal device may send a PDU session establishment request message to the session management network element. The PDU session establishment request message may include the MAC address of the first device-side converter port, the dwell time corresponding to the first device-side converter port, the port management capability information corresponding to the first device-side converter port, etc. The session management network element may select a node (i.e., a first node) that supports the first network for the first terminal device based on the content carried in the PDU session establishment request message, and send a session establishment request message to the node to request establishment of a PDU session for the first terminal device.
[0189] Exemplarily, the residence time corresponding to the first device-side converter port can be understood as: the duration between the data packet arriving at the first terminal device from the first device-side converter port (for example, the duration between the moment the data packet is output from the first device-side converter port and the moment the data packet arrives at the first terminal device); or, the duration between the data packet arriving at the first device-side converter port from the first terminal device (for example, the duration between the moment the data packet is output from the first terminal device and the moment the data packet arrives at the first device-side converter port).
[0190] For example, when the first network is TSN, the residence time corresponding to the device-side converter port may be UE-DS-TT residence time, which indicates the time it takes for a data packet to arrive at a terminal device (such as a UE module) from a DS-TT port.
[0191] Exemplarily, the port management capability information corresponding to the first device-side converter port may include a table of service types supported by the first device-side converter port, etc. Alternatively, the port management capability information corresponding to the first device-side converter port may indicate port management information supported by the first device-side converter port. This port management information may include, for example, whether a per-stream filtering policy (PSFP) in a first network (e.g., a TSN network) is supported. For a detailed description of the port management capability information, reference may be made to 3GPP Technical Standard (TS) 23.501.
[0192] Optionally, after receiving the session establishment request message from the session management network element, the first node may assign a port number to the device-side converter port associated with the first PDU session and the first terminal device (i.e., the first device-side converter port). For example, the first node assigns the first port number to the first device-side converter port. That is, the first node assigning the first port number to the device-side converter port of the first network bridge in step S501 may be performed during the PDU session establishment process.
[0193] In addition, the first node may also assign a port number to the first network-side converter port associated with the first PDU session. Furthermore, the first node may also determine a user-plane node identifier for the first node. This user-plane node identifier may also serve as a bridge identifier for the first network bridge. The port number and / or user-plane node identifier of the first network-side converter port may be preconfigured in the first node.
[0194] Afterwards, the first node may send a session establishment response message to the session management network element, with the session establishment response message carrying first indication information, where the first indication information is used to indicate the first port number. That is, the sending of the first information described in step S501 above may include the first indication information, where the first indication information is used to indicate the first port number. Furthermore, the first node may indicate the first port number to the session management network element during the PDU session establishment process. Furthermore, the first indication information may also indicate that the first port number is the port number of the device-side converter port associated with the first PDU session.
[0195] Exemplarily, the first indication information may explicitly indicate the first port number, for example, the first indication information is the first port number; or the first indication information may implicitly indicate the first port number, for example, the first indication information may be an index of the first port number, etc. This application does not impose any specific limitation on this.
[0196] In addition, the session establishment response message may also carry the user plane node identifier of the first node, the port number of the first network-side converter port, etc. After receiving the session establishment response message, the session management network element may save the first port number, the user plane node identifier of the first node, the port number of the first network-side converter port, etc.
[0197] Optionally, in addition to the first terminal device, a PDU session may be established between other terminals and the first node. For example, a second terminal device may also establish a PDU session with the first node. The first user-plane network element also assigns a port number to the device-side converter port associated with the PDU session. For related implementation, refer to the description of establishing a PDU session between the first terminal device and the first node, and will not be repeated here.
[0198] S602: The first terminal device establishes a first PC5 connection with the second terminal device.
[0199] In step S602, the first terminal device establishes a first PC5 connection with the second terminal device. The second terminal device establishes a first PC5 connection with the first terminal device.
[0200] Optionally, the first terminal device may send a direct communication request to the second terminal device. After establishing a secure connection between the first and second terminal devices, the second terminal device may send a direct communication acceptance message to the first terminal device. At this point, the first PC5 connection between the first and second terminal devices can be considered successfully established. Based on this first PC5 connection, data can be sent and received between the first and second terminal devices.
[0201] Optionally, on the first PC5 connection, both the first terminal device and the second terminal device have Layer 2 identifiers. For ease of description, in the following embodiments of this application, the identifier of the first terminal device on the first PC5 connection is referred to as a first Layer 2 identifier, and the identifier of the second terminal device on the first PC5 connection is referred to as a second Layer 2 identifier. The identifier of a terminal device on the PC5 connection can also be referred to as an identifier associated with the PC5 connection. That is, the first Layer 2 identifier can also be understood as the identifier of the first terminal device associated with the first PC5 connection, and the second Layer 2 identifier can also be understood as the identifier of the second terminal device associated with the first PC5 connection.
[0202] The first layer 2 identifier may be a source identifier or a destination identifier used when the first terminal device sends information to the second terminal device, and the second layer 2 identifier may be a source identifier or a destination identifier used when the second terminal device sends information to the first terminal device. The embodiments of the present application are mainly described by taking as an example that the first layer 2 identifier is a source identifier used when the first terminal device sends information to the second terminal device, and the second layer 2 identifier is a source identifier used when the second terminal device sends information to the first terminal device.
[0203] Optionally, the first PC5 connection can be associated with a device-side converter port corresponding to the first terminal device and a device-side converter port corresponding to the second terminal device. For ease of description, the following embodiments of this application use the second device-side converter port as the device-side converter port corresponding to the first terminal device associated with the first PC5 connection, and use the third device-side converter port as the device-side converter port corresponding to the second terminal device associated with the first PC5 connection.
[0204] Optionally, the terminal device identifier on the PC5 connection may correspond to or be associated with a device-side converter port associated with the PC5 connection. For example, the first layer 2 identifier may correspond to or be associated with the second device-side converter port, and the second layer 2 identifier may correspond to or be associated with the third device-side converter port.
[0205] Optionally, the second device-side converter port and the third device-side converter port each correspond to a MAC address. The MAC address corresponding to each device-side converter port can be a globally unique MAC address, i.e., different device-side converter ports correspond to different MAC addresses. Therefore, it can also be considered that the first Layer 2 identifier is associated with the MAC address of the second device-side converter port, and the second Layer 2 identifier is associated with the MAC address of the third device-side converter port.
[0206] Optionally, after the first PC5 connection is established, the first terminal device and the second terminal device may determine an identifier of the first PC5 connection (ie, PC5 link ID), where the PC5 link ID is used to identify the first PC5 connection.
[0207] Optionally, after step S602, the first terminal device and the second terminal device may determine information about the first PC5 connection (PC5 Link profile). Exemplarily, the information about the first PC5 connection may include a source identifier, a destination identifier, an identifier of the first PC5 connection, etc. The information about the first PC5 connection may be used to determine the first network bridge.
[0208] Optionally, in addition to the first PC5 connection, at least one more PC5 connection may be established between the first terminal device and the second terminal device, i.e., multiple PC5 connections may be established between the first terminal device and the second terminal device. Furthermore, in addition to the second terminal device, the first terminal device may also establish a PC5 connection with another terminal device (e.g., at least one third terminal device). In addition to the first terminal device, the second terminal device may also establish a PC5 connection with another terminal device (e.g., at least one fourth terminal device).
[0209] Optionally, the first terminal device has the same or different layer 2 identifiers on multiple PC5 connections. The multiple PC5 connections may include PC5 connections between the first terminal device and another terminal device, and / or PC5 connections between the first terminal device and multiple terminal devices.
[0210] Optionally, the first terminal device can associate multiple device-side converter ports corresponding to the first terminal device for multiple PC5 connections of the first terminal device (different PC5 connections are associated with different device-side converter ports), and the multiple device-side converter ports can have different MAC addresses. Alternatively, the first terminal device can also associate one same device-side converter port for some or all of the multiple PC5 connections (i.e., there are different PC5 connections associated with the same device-side converter port). For example, when the first terminal device has the same layer 2 identifier on multiple PC5 connections, these PC5 connections can share one device-side converter port corresponding to the first terminal device. When the first terminal device has different layer 2 identifiers on multiple PC5 connections, these PC5 connections need to be associated with different device-side converter ports corresponding to the first terminal device.
[0211] Optionally, PC5 connections may be established between other terminal devices (eg, between the fifth terminal device and the sixth terminal device) in addition to the first terminal device and the second terminal device. Implementation of these PC5 connections may refer to the relevant description of the first PC5 connection, which will not be repeated here.
[0212] It should be noted that there is no necessary order for the above steps S601 and S602. Step S601 can be executed first and then step S602, or step S602 can be executed first and then step S601, or steps S601 and S602 can be executed at the same time. This application does not make any specific restrictions on this.
[0213] S603: The third node sends the second information or the third information to the first node. Correspondingly, the first node receives the second information or the third information from the third node.
[0214] Optionally, as shown in FIG7 , the third node may be at least one of a session management network element, a policy control network element, an application function network element (eg, a TSN AF), the first terminal device, or the second terminal device.
[0215] Exemplarily, when the third node sends the second information to the first node, the third node may be a session management network element, a policy control network element, an application function network element, the first terminal device, or the second terminal device. For example, the third node may be a session management network element. When the third node sends the third information to the first node, the third node may be at least one of a session management network element, a policy control network element, an application function network element, the first terminal device, or the second terminal device. That is, multiple nodes may send the third information to the first node.
[0216] It can be understood that when the second node is a session management network element and the third node is also a session management network element, or when the second node is a policy control network element and the third node is also a policy control network element, or when the second node is an application function network element and the third node is also an application function network element, in an embodiment of the present application, the second node and the third node are the same node.
[0217] The second information is used to instruct the first node to assign a port number to the device-side converter port associated with the PC5 connection in the first network bridge. Exemplarily, the second information may include the number of ports and / or the number of PC5 connections. The number of ports is the number of device-side converter ports associated with the PC5 connection in the first network bridge that require the first node to assign a port number. The number of PC5 connections is used to determine the number of device-side converter ports associated with the PC5 connection in the first network bridge that require the first node to assign a port number.
[0218] Exemplarily, the device-side converter port associated with the PC5 connection in the first network bridge that requires the first node to assign a port number can be understood as: a device-side converter port that has not yet been assigned a port number among the device-side converter ports associated with the PC5 connection in the first network bridge at the current moment. For example, assume that the first network bridge includes a first PC5 connection and a second PC5 connection (a PC5 connection between a first terminal device and a third terminal device). If the device-side converter port associated with the second PC5 connection and the first terminal device and the device-side converter port associated with the second PC5 connection and the third terminal device at the current moment have already been assigned a port number, and the second device-side converter port and the third device-side converter port associated with the first PC5 connection have not yet been assigned a port number, then the number of ports can be 2.
[0219] Exemplarily, the reason why the device-side converter port associated with the second PC5 connection and the first terminal device and the device-side converter port associated with the second PC5 connection and the third terminal device have been assigned port numbers at the current moment may be that the second PC5 connection is established before the first PC5 connection, and after the second PC5 connection is established, the third node instructs the first node to assign a port number to the device-side converter port associated with the second PC5 connection.
[0220] For example, the number of PC5 connections can be half the number of ports, or in other words, the number of ports can be twice the number of PC5 connections. For example, based on the above example of the number of ports, the number of PC5 connections is 1, and this one PC5 connection is the first PC5 connection. Both device-side converter ports associated with the first PC5 connection need to be assigned port numbers.
[0221] As a first possible implementation, when the third node is a session management network element and the session management network element sends the second information to the first node, exemplarily, the session management network element can send an N4 session establishment / modification message to the first node, and the N4 session establishment / modification message carries the second information.
[0222] In the case where the third node is a session management network element, a policy control function network element, or an application function network element, before step S603, the method may further include:
[0223] The first terminal device sends the fifth information to the third node, and the second terminal device sends the fifth information to the third node. Accordingly, the third node receives the fifth information from the first terminal device and the fifth information from the second terminal device. The fifth information indicates that the first PC 5 is connected, or in other words, indicates that the first PC 5 is connected.
[0224] Optionally, when the third node is a session management network element, the first terminal device sending the fifth information to the session management network element may include: the first terminal device sending the fifth information to the policy control network element, and the policy control network element then sending the fifth information to the session management network element. The second terminal device sending the fifth information to the session management network element can be implemented by referring to the description of the first terminal device sending the fifth information to the session management network element, and will not be repeated here.
[0225] Optionally, the fifth information sent by the first terminal device includes at least one of the following:
[0226] (1) First layer 2 identification and / or second layer 2 identification.
[0227] Exemplarily, when the fifth information includes the first layer 2 identifier and the second layer 2 identifier, it can also be understood that the fifth information includes the source identifier and destination identifier included in the information when the first terminal device sends information to the second device.
[0228] (2) Identification of the first PC5 connection.
[0229] (3) Identification information of the first PDU session or identification information of the first node or identification information of the first bridge.
[0230] The identification information of the first PDU session or the identification information of the first node is used to indicate that the first PC5 connection and the first PDU session belong to the same bridge. Exemplarily, the identification information of the first node may be a user plane node identifier of the first node.
[0231] (4) First identification information.
[0232] Exemplarily, the first identification information may include at least one of the following: a MAC address corresponding to the converter port on the second device side, an international mobile subscriber identity (IMSI) of the first terminal device, a temporary mobile subscriber identity (TMSI) of the first terminal device, or an international mobile equipment identity (IMEI) of the first terminal device.
[0233] It can be understood that since the MAC address corresponding to the device side converter port is globally unique, it can be considered that the first layer 2 identifier is associated with the MAC address of the second device side converter port, the second layer 2 identifier is associated with the MAC address of the third device side converter port, and the first PC5 connection is associated with the second device side converter port and the third device side converter port. Therefore, when the first identification information includes the MAC address of the second device side converter port, the MAC address can also indicate the first PC5 connection.
[0234] Optionally, when the fifth information only includes the first identification information, the first identification information needs to include the MAC address of the converter port on the second device. Further, the first identification information may include at least one of the IMSI, TSMI or IMEI of the first terminal device.
[0235] Optionally, when the first identification information includes the MAC address of the second device-side converter port, the first identification information can be used to uniquely identify the second device-side converter port. For example, when another terminal device (denoted as the seventh terminal device) selects the same Layer 2 identification as the first terminal device, the third node can identify whether the device-side converter ports of the two terminal devices are the same based on the first identification information.
[0236] For example, if the fifth information does not include the first identification information, the third node may assume that the seventh terminal device and the first terminal device have the same device-side converter port because the seventh terminal device and the first terminal device have the same layer 2 identifier. If the fifth information includes the first identification information, and the PC5 connection-related information sent by the seventh terminal device to the third node includes the third identification information (for uniquely identifying the device-side converter port corresponding to the seventh terminal device), the third node can identify whether the device-side converter ports corresponding to the two terminal devices are the same based on the first identification information and the third identification information.
[0237] (5) Port management capability information corresponding to the converter port on the second device side.
[0238] (6) The dwell time corresponding to the converter port on the second device side.
[0239] The port management capability information and the residence time may refer to the relevant description of the port management capability information and the residence time in the above step S601, which will not be repeated here.
[0240] (7) First application information.
[0241] Optionally, the first application information includes at least one of the following: an application identifier (Application ID) associated with the first PC5 connection, an application group identifier (Application group ID) associated with the first PC5 connection, an application layer identifier (Application Layer ID) associated with the first PC5 connection, or an identifier of a network served by the first terminal device.
[0242] Exemplarily, the application layer identifier refers to the identifier of the terminal device at the application layer, which is used to identify the terminal device. In other words, the application layer identifier associated with the first PC 5 is the identifier of the first terminal device at the application layer, which is used to identify the first terminal device.
[0243] An application identifier is an identifier of an application and is used to identify the application. That is, the application identifier associated with the first PC 5 connection can identify the application associated with (or corresponding to, or serving) the first PC 5 connection. Similarly, the application group identifier associated with the first PC 5 connection can identify the application group associated with (or corresponding to, or serving) the first PC 5 connection.
[0244] Optionally, there may be multiple networks, for example, a second network or a third network in addition to the first network. The identifier of the network served by the first terminal device can also be understood as the identifier of the first network, which means that the first terminal device can be used to serve the first network or is interested in the first network or can provide transmission services to the first network.
[0245] Optionally, there may be multiple applications in the first network, and the first application information reported by the first terminal device can be used to identify the application served by the first terminal device or the application of interest among the multiple applications.
[0246] (8) Second identification information.
[0247] Exemplarily, the second identification information may include at least one of the following: a MAC address corresponding to the converter port on the third device side, the IMSI of the second terminal device, the TMSI of the second terminal device, or the IMEI of the second terminal device.
[0248] Optionally, the first terminal device and the second terminal device may exchange the first identification information and / or the second identification information during the process of establishing the first PC5 connection or after establishing the first PC5 connection.
[0249] Optionally, when the fifth information reported by the first terminal device includes the MAC address corresponding to the converter port on the second device side and the MAC address corresponding to the converter port on the third device side, the first terminal device may not report the first layer 2 identifier and the second layer 2 identifier or report the identifier of the first PC5 connection.
[0250] Optionally, the fifth information sent by the second terminal device includes at least one of the following:
[0251] (9) First Layer 2 Identification and / or Second Layer 2 Identification.
[0252] (10) Identification of the first PC 5 connection.
[0253] (11) Identification information of the first PDU session or identification information of the first node or identification information of the first bridge.
[0254] (12) Second identification information.
[0255] (13) Port management capability information corresponding to the converter port on the third device side.
[0256] (14) The dwell time corresponding to the converter port on the third device side.
[0257] The port management capability information and the residence time may refer to the relevant description of the port management capability information and the residence time in the above step S601, which will not be repeated here.
[0258] (15) Second application information.
[0259] Optionally, the second application information includes at least one of the following: an application identifier (Application ID) associated with the first PC5 connection, an application group identifier (Application group ID) associated with the first PC5 connection, an application layer identifier (Application Layer ID) associated with the first PC5 connection, or an identifier of a network served by the second terminal device.
[0260] (16) First identification information.
[0261] Among them, the description of the parameters included in the fifth information sent by the second terminal device can refer to the introduction of the corresponding parameters included in the fifth information sent by the first terminal device, and will not be repeated here.
[0262] In a possible implementation, the second terminal device may not send the fifth information to the third node. In this case, the second terminal device may send at least one of the above parameters (9)-(16) to the first terminal device, and the first terminal device then carries at least one of the parameters (1)-(16) in the fifth information and sends it to the session management network element.
[0263] Optionally, after receiving the fifth information from the first terminal device and the second terminal device, the third node can determine that there is a first PC5 connection between the first terminal device and the second terminal device, and the first PC5 connection is associated with the second device-side converter port and the third device-side converter port. Afterwards, the third node can determine that there is a user plane connection between the first terminal device and the first node (for example, through a session management network element or the third node itself is a session management network element), and thus can send the second information to the first node. Alternatively, the third node can determine that the bridge corresponding to the first PC5 connection and the bridge corresponding to the first node are the same bridge based on the association information between the first PC5 connection and the first PDU session (or the first node), and thus can send the second information to the first node.
[0264] As a second possible implementation, when the third node is a first terminal device and the first terminal device sends the second information to the first node, the first terminal device can send the second information to the first node after the first PC5 connection is established. In addition, the first terminal device can send the second information to the first node through a PDU session between the first terminal device and the first node.
[0265] As a third possible implementation, when the third node is a second terminal device and the second terminal device sends the second information to the first node, the second terminal device may also send the second information to the first node after the first PC5 connection is established. When a PDU session exists between the second terminal device and the first node, the second terminal device may send the second information to the first node via the PDU session.
[0266] Optionally, the second possible implementation and the third possible implementation described above can be combined, that is, the first terminal device and the second terminal device can both send the second information to the first node. In this scenario, the sum of the number of port numbers that need to be assigned by the first node in the first bridge indicated by the first terminal device and the number of port numbers that need to be assigned by the first node in the first bridge indicated by the second terminal device can be the total number of device-side converter ports that have not yet been assigned port numbers among the device-side converter ports associated with the PC5 connection in the first bridge at the current moment. For example, at the current moment, the two device-side converter ports associated with the first PC5 connection in the first bridge have not yet been assigned port numbers, then the number of port numbers that need to be assigned by the first node indicated by the first terminal device is 1, and the number of port numbers that need to be assigned by the first node indicated by the second terminal device is also 1.
[0267] In other words, the number of port numbers that the first terminal device indicates need to be allocated by the first node in the first network bridge is the number of device-side converter ports in the first network bridge that are currently connected to PC 5 and associated with the first terminal device and that have not yet been allocated port numbers. The number of port numbers that the second terminal device indicates need to be allocated by the first node in the first network bridge is the number of device-side converter ports in the first network bridge that are currently connected to PC 5 and associated with the second terminal device and that have not yet been allocated port numbers.
[0268] Optionally, in the second and third possible implementations, the first and second terminal devices may also send information about the first PC5 connection to a third node. Specifically, the first terminal device sends fifth information to the session management network element, policy control network element, or application function network element, and the second terminal device also sends fifth information to the session management network element, policy control network element, or application function network element. The fifth information sent by each of the first and second terminal devices can refer to the above description. When the first and second terminal devices send information about the first PC5 connection to the policy control network element, the policy control network element, upon receiving the information about the first PC5 connection, may send the information about the first PC5 connection to the session management network element. Upon receiving the information about the first PC5 connection, the third node may determine that a first PC5 connection exists between the first and second terminal devices. Based on the association information between the first PC5 connection and the first PDU session (or the first node), the third node may determine that the bridge corresponding to the first PC5 connection is the same bridge (i.e., the first bridge) as the bridge corresponding to the first node, thereby determining the structure of the first bridge.
[0269] As a fourth possible implementation, when the third node is a policy control network element or an application function network element, the implementation of the policy control network element or the application function network element sending the second information to the first node can refer to the description of the session management network element sending the second information to the first node, which will not be repeated here.
[0270] The third information includes information about the first PC 5 connection. Exemplarily, the third information includes at least one of the following: a first Layer 2 identifier and / or a second Layer 2 identifier, an identifier for the first PC 5 connection, first identification information, first application information, second identification information, second application information, port management capability information corresponding to the second device-side converter port, the resident time corresponding to the second device-side converter port, port management capability information corresponding to the third device-side converter port, or the resident time corresponding to the third device-side converter port. The description of each parameter can be found in the description of the fifth information above and is not repeated here.
[0271] As a first possible implementation, when the third node is a session management network element, the session management network element may send an N4 session establishment / modification message to the first node, with the N4 session establishment / modification message carrying the third information. Furthermore, before the session management network element sends the third information to the first node, the first terminal device and the second terminal device may send fifth information to the session management network element. The session management network element may determine the third information based on the fifth information and then send the third information to the first node. For details, refer to the description of the session management network element sending the second information to the first node, and will not be repeated here.
[0272] As a second possible implementation, when the third node is the first terminal device, the implementation of the first terminal device sending the third information to the first node can refer to the description of the first terminal device sending the second information to the first node, which will not be repeated here.
[0273] As a third possible implementation, when the third node is the second terminal device, the implementation of the second terminal device sending the third information to the first node can refer to the description of the second terminal device sending the second information to the first node, which will not be repeated here.
[0274] As a fourth possible implementation, when the third node is a policy control network element or an application function network element, the implementation of the policy control network element or application function network element sending the third information to the first node can refer to the description of the session management network element sending the second information to the first node, and will not be repeated here. Optionally, in the second and third possible implementations, the first terminal device or the second terminal device may also send the third information to the session management network element, the policy control network element, or the application function network element. In addition, after receiving the third information, the first node may also send information about the connection of the first PC5 to the session management network element, the policy control network element, or the application function network element.
[0275] Optionally, in addition to the first PC5 connection, the first network bridge may further include at least one other PC5 connection between the first terminal device and the second terminal device. Furthermore, the first network bridge may further include at least one PC5 connection between the first terminal device and another terminal device (e.g., a third terminal device). The first network bridge may further include at least one PC5 connection between at least two other terminal devices (e.g., a fifth terminal device and a sixth terminal device).
[0276] In this scenario, the port number included in the second information sent by the third node can be the number of all device-side converter ports currently associated with the PC5 connection that have not yet been assigned a port number. The number of PC5 connections included in the second information can be the number of all PC5 connections currently associated with the device-side converter ports that have not yet been assigned a port number. In addition, when the third node sends the third information to the first node, the third node may also send the first node information about other PC5 connections in the first network bridge, in addition to the first PC5 connection.
[0277] S604: The first node allocates a port number to the device-side converter port associated with the PC 5 in the first network bridge according to the second information or the third information.
[0278] Optionally, after receiving the second information, the first node may assign port numbers to the device-side converter ports associated with the PC5 connection in the first network bridge according to the instructions in the second information. Exemplarily, if the second information includes a port number, the number of port numbers assigned by the first node to the device-side converter ports associated with the PC5 connection in the first network bridge is the same as the port number reported in the second information. If the second information includes a number of PC5 connections, the number of port numbers assigned by the first node to the device-side converter ports associated with the PC5 connection in the first network bridge is twice the number of PC5 connections.
[0279] Exemplarily, after receiving the second information, the first node may allocate, based on the second information, the port number assigned to the device-side converter port of the first network bridge associated with PC 5, including the second port number and the third port number. That is, the allocation of the second port number and the third port number to the device-side converter port of the first network bridge by the first node in step S501 may be performed after receiving the second information from the third node.
[0280] Optionally, after the first node assigns the second and third port numbers according to the second information, the first node may determine that the second and third port numbers are port numbers of the device-side converter ports associated with the PC5 connection. However, the first node may not care about, perceive, or determine which PC5 connection in the first network bridge the second and third port numbers are associated with. For details, see the first possible implementation in step S501 above, which will not be described in detail here.
[0281] Optionally, after receiving the third information, the first node may assign a port number to the device-side converter port associated with the PC 5 connection in the first network bridge according to the third information. Exemplarily, the first node may determine information about the first PC 5 connection based on the third information, thereby assigning a port number to the device-side converter port associated with the first PC 5 connection.
[0282] Exemplarily, after receiving the third information, the first node may allocate, according to the third information, a port number to the device-side converter port of the first network bridge associated with PC 5, including the second port number and the third port number. That is, the allocation of the second port number and the third port number to the device-side converter port of the first network bridge by the first node in step S501 may be performed after receiving the third information from the third node.
[0283] Optionally, after the first node assigns the second port number and the third port number according to the instruction of the third information, the first node can determine that the second port number and the third port number are the device-side converter ports associated with the first PC5 connection. However, the first node may not care about, perceive, or determine the correspondence between the second port number and the third port number and the two device-side converter ports. Alternatively, the first node can determine that the second port number is the port number of the device-side converter port (i.e., the second device-side converter) associated with the first PC5 connection and the first terminal device, and the third port number is the port number of the device-side converter port (i.e., the third device-side converter port) associated with the first PC5 connection and the second terminal device. Please refer to the second and third possible implementations in the above step S501, which will not be repeated here.
[0284] Optionally, in the case where the first network bridge includes multiple PC5 connections, the first node may allocate a port number to a device-side converter port associated with each PC5 connection in the first network bridge according to the second information or information of the multiple PC5 connections.
[0285] S605: The first node sends second instruction information to the second node, wherein the second instruction information is used to instruct the first node to allocate a port number to the device-side converter port associated with the PC 5 in the first network bridge.
[0286] Exemplarily, the port number assigned by the first node to the device-side converter port associated with PC5 in the first network bridge includes the second port number and the third port number. That is, the second indication information can be used to indicate the second port number and the third port number. In this case, it can be considered that the first information includes the second indication information.
[0287] Optionally, in a case where the first node can determine that the second port number and the third port number are the port numbers of the device-side converter port associated with the PC5 connection, the second indication information can also be used to indicate that the second port number and the third port number are the port numbers of the device-side converter port associated with the PC5 connection. Alternatively, in a case where the first node can determine that the second port number and the third port number are the port numbers of the device-side converter port associated with the first PC5 connection, the second indication information can also be used to indicate that the second port number and the third port number are the port numbers of the device-side converter port associated with the first PC5 connection. Alternatively, in a case where the first node can determine that the second port number is the port number of the device-side converter port associated with the first PC5 connection and the first terminal device, and the third port number is the port number of the device-side converter port associated with the first PC5 connection and the second terminal device, the second indication information can also be used to indicate that the second port number is the port number of the device-side converter port associated with the first PC5 connection and the first terminal device, and the third port number is the port number of the device-side converter port associated with the first PC5 connection and the second terminal device.
[0288] Optionally, the second node may be a session management network element, a policy control network element, or an application function network element. In FIG6 , the second node is described as a session management network element as an example.
[0289] Optionally, the first node may also send the second indication information to other nodes. For example, the first node may also send the second indication information to a session management network element (for example, when the second node is not a session management network element), a policy control network element (for example, when the second node is not a policy control network element) or an application function network element (for example, when the second node is not an application function network element), the first terminal device or the second terminal device.
[0290] Optionally, when the second node is a session management network element, the first node may send an N4 session establishment / modification response message to the session management network element, indicating the allocated port number in the N4 session establishment / modification response message. In other words, the second indication information (including the second port number and the third port number) may be indicated in the N4 session establishment / modification response message.
[0291] Optionally, after receiving the second indication information, the session management network element can determine the second port number as the second device side converter port associated with the first PC5 connection, and determine the third port number as the third device side converter port associated with the first PC5 connection, that is, the second port number is the port number of the second device side converter port, and the third port number is the port number of the third device side converter port. Please refer to the relevant instructions in the above step S503 and will not repeat them here.
[0292] Optionally, when there are multiple PC5 connections in the first network bridge, the first node may indicate the port number assigned to the device-side converter port associated with each PC5 connection in the first network bridge, that is, the second indication information may indicate the port number assigned to the device-side converter port associated with multiple PC5 connections in the first network bridge.
[0293] S606: The second node sends fourth information to the fourth node. Correspondingly, the fourth node receives the fourth information from the second node. FIG6 illustrates an example in which the second node is a session management network element and the fourth node is a TSN AF network element.
[0294] The fourth information is used to indicate a first port number, a second port number, and a third port number. The first port number is the port number of the first device-side converter port, the second port number is the port number of the second device-side converter port, and the third port number is the port number of the third device-side converter port. For details, refer to the description in step S504 above and will not be repeated here.
[0295] Optionally, when the second node and the fourth node are the same node (for example, when the second node and the fourth node are both TSN AF), S606 may be an internal implementation step and is not explicitly executed.
[0296] Optionally, the second node may further indicate information about each port in the first network bridge to the fourth node. For example, for the first device-side converter port, in addition to the first port number, the second node may further indicate at least one of the following: a MAC address of the first device-side converter port, a residence time corresponding to the first device-side converter port, and an identifier of the network bridge to which the first device-side converter port belongs (e.g., a user plane node identifier of the first node).
[0297] For the second device side converter port, in addition to the second port number, the second node can also send at least one of the following items: the identifier of the bridge to which the second device side converter port belongs (such as the user plane node identifier of the first node, which can also be understood as the identifier of the first bridge), the MAC address of the second device side converter port, the residence time corresponding to the second device side converter port, the port management capability information corresponding to the second device side converter port, and the information of the device side converter port connected to the same PC5 associated with the second device side converter port.
[0298] For example, the device-side converter port connected to the same PC 5 associated with the second device-side converter is referred to as the third device-side converter port. The device-side converter port connected to the same PC 5 associated with the second device-side converter may also be referred to as the peer port of the second device-side converter port. Information about the peer port may include the port number of the peer port, the resident time corresponding to the peer port, the MAC address of the peer port, and the like.
[0299] For the third device side converter port, in addition to the third port number, the second node can also send at least one of the following: the identifier of the bridge to which the third device side converter port belongs (such as the user plane node identifier of the first node), the MAC address of the third device side converter port, the residence time corresponding to the third device side converter port, the port management capability information corresponding to the third device side converter port, and the information of the device side converter port connected to the same PC5 associated with the third device side converter port.
[0300] For example, the device-side converter port connected to the same PC5 associated with the third device-side converter is referred to as the second device-side converter port. The device-side converter port connected to the same PC5 associated with the third device-side converter can also be referred to as the peer port of the third device-side converter port. For information about the peer port, refer to the aforementioned related description and will not be repeated here.
[0301] Optionally, the second node may also indicate at least one of the following to the fourth node: the first port number is the port number of the device side converter port associated with the PDU session, the second port number and the third port number are the port numbers of the device side converter port associated with the PC5 connection, and the second port number and the third port number are the port numbers of the device side converter port associated with the same PC5 connection.
[0302] That is, in a possible implementation, the second node may indicate to the fourth node the port number and at least one of the identifier of the bridge to which it belongs, the MAC address, the dwell time, the peer port information, the port number type, and the associated PC5 connection.
[0303] Table 1
[0304] It should be noted that Table 1 is only an exemplary illustration of the information that the second node can indicate to the fourth node. In actual applications, the information indicated by the second node to the fourth node may be at least one of some or all of the parameters shown in Table 1, and this application does not make any specific limitations on this.
[0305] As a possible implementation, the at least one item indicated by the second node to the fourth node may be indicated by fourth information, that is, the fourth information may indicate, in addition to the port number, the user plane node identifier of the first node (or the identifier of the first bridge). Furthermore, the fourth information may also indicate at least one of the following:
[0306] The first port number is the port number of the device-side converter port associated with the PDU session.
[0307] The second port number and the third port number are the port numbers of the device side converter ports associated with the PC5 connection.
[0308] The second port number and the third port number are the port numbers of the device-side converter ports associated with the same PC5 connection.
[0309] MAC address of the converter port on the first device side,
[0310] The dwell time corresponding to the converter port on the first device side,
[0311] Port management capability information of the first device-side converter port,
[0312] MAC address of the converter port on the second device side,
[0313] The dwell time corresponding to the converter port on the second device side
[0314] Port management capability information corresponding to the converter port on the second device side,
[0315] Information about the peer port of the converter port on the second device side,
[0316] MAC address of the converter port on the third device side,
[0317] The dwell time corresponding to the converter port on the third device side,
[0318] The port capability information corresponding to the converter port on the third device side, or
[0319] Information about the opposite port of the converter port on the third device.
[0320] As another possible implementation, the at least one item indicated by the second node to the fourth node may be indicated by one or more pieces of information other than the fourth information. That is, in addition to the fourth information, the second node may also send third indication information to the fourth node, where the third indication information indicates the at least one item.
[0321] Optionally, the second node may indicate the correspondence between the port number and at least one of the above parameters to the fourth node through one message, or may indicate the correspondence between the port number and at least one of the above parameters to the fourth node through multiple messages. This application does not make any specific limitations on this.
[0322] It should be noted that the embodiments of the present application do not limit the specific indication form of the above information. For example, the fourth information can indicate the port type of a port number, the user plane node identifier of the first node, the opposite port and other information for a port number. For another example, if the fourth information only contains one user plane node identifier, all port numbers in the fourth information are port numbers associated with the user plane node; for another example, the fourth information includes information on multiple port pairs, and then indicates the port type, capability information and residence time of the two ports in each port pair respectively.
[0323] Optionally, when there are multiple PC5 connections in the first network bridge, the second node may indicate to the fourth node the port number of the device-side converter port associated with each PC5 connection. The second node may also indicate at least one of the following: the identifier of the network bridge to which the device-side converter port associated with each PC5 connection belongs, its MAC address, its dwell time, its peer port information, its port number type, and its associated PC5 connection.
[0324] S607: The fourth node determines sixth information, where the sixth information is used to indicate the first network bridge.
[0325] Optionally, the fourth node may determine the port number of the device-side converter port in the first network bridge based on the fourth information. In addition, the fourth node may also determine the structure of the first network bridge based on the information indicated by the second node in step S606, thereby determining the sixth information used to indicate the first network bridge.
[0326] Optionally, the sixth information includes at least one of the following: an identifier of the first network bridge, the number of ports in the first network bridge, a first port number, a second port number, a third port number, port pair information, or a port pair delay. The first port number is the port number of the converter port on the first device side, the second port number is the port number of the converter port on the second device side, and the third port number is the port number of the converter port on the third device side.
[0327] The port pair information indicates a port pair in the first network bridge. A port pair includes, or is composed of, two ports. Two ports in the same port pair can communicate with each other, or a transmission channel or path exists between the two ports. Exemplarily, the port pairs in the first network bridge include a first port pair and a second port pair, the first port pair including a first device-side converter port and a first network-side converter port, and the second port pair including a second device-side converter port and a third device-side converter port.
[0328] Port pair latency refers to the time it takes for a data packet to travel from one port in a port pair to the other port in the pair. For example, it refers to the time between the moment a data packet is output from one port in the pair and the moment it arrives at the other port in the pair.
[0329] Optionally, when there are multiple PC5 connections in the first network bridge, the sixth information may include the port number of the device-side converter port associated with each PC5 connection and information about a port pair consisting of two device-side converter ports associated with each PC5 connection.
[0330] S608: The fourth node sends the sixth information to the fifth node. Correspondingly, the fifth node receives the sixth information from the fourth node. Please refer to the relevant description in the above step S506, which will not be repeated here.
[0331] Optionally, before step S608, the communication method provided in the embodiment of the present application may further include the following steps AC (not shown in FIG6 ):
[0332] A. The fourth node obtains the propagation delay on the first device side converter port, the second device side converter port, and the third device side converter port, and / or a traffic class table supported by the ports.
[0333] Optionally, the propagation delay on a port can be used to determine the propagation delay between the port and other ports (eg, ports on other bridges). The service type table can be used to map data packets of different priorities to different service types.
[0334] Optionally, in step A, the fourth node may send a subscription request for port management information changes to the first device-side converter, the second device-side converter, and the third device-side converter. Subsequently, the first device-side converter, the second device-side converter, and the third device-side converter may send the propagation delay on the port and / or a table of service types supported by the port to the fourth node via a port management information container (PMIC).
[0335] The device-side converter is used to provide a device-side converter port. The first device-side converter is used to provide a first device-side converter port, the second device-side converter is used to provide a second device-side converter port, and the third device-side converter is used to provide a third device-side converter port.
[0336] Optionally, the first device-side converter and the second device-side converter may be the same or different device-side converters, that is, when a terminal device is associated with multiple device-side converter ports, these device-side converter ports may be associated with the same or different device-side converter ports. For example, multiple device-side converter ports associated with a terminal device may be associated with the same device-side converter; for another example, multiple device-side converter ports associated with PDU sessions associated with a terminal device may be associated with one device-side converter, and multiple device-side converters associated with PC5 connections may be associated with another device-side converter; for another example, each of the multiple device-side converter ports associated with a terminal device may be associated with a different device-side converter.
[0337] For example, when sending a PMIC, the first device-side converter may provide the PMIC to the first terminal device, which then sends the PMIC to the policy control network element, which then forwards the PMIC to the fourth node. The second device-side converter port and the third device-side converter port send the PMIC in a similar manner and are not further described here.
[0338] Optionally, in the case where the first network bridge includes multiple PC5 connections, in step A, the fourth node may obtain the propagation delay on each device-side converter port associated with each PC5 connection, and / or a service type table supported by the port.
[0339] B. The fourth node performs neighbor discovery configuration and neighbor discovery information subscription.
[0340] Exemplarily, the fourth node may send neighbor discovery configuration information to at least one of the first device-side converter, the second device-side converter, and the third device-side converter, and subscribe to neighbor discovery information.
[0341] Optionally, the neighbor discovery configuration information is used to configure and activate a link layer discovery protocol (LLDP) agent on the device-side converter.
[0342] Optionally, when one of the first device side converter, the second device side converter and the third device side converter does not support neighbor discovery, or does not have the neighbor discovery capability, the fourth node can configure another device side converter or a network side converter (for example, a network side converter associated with the first network side converter port) to perform link layer neighbor discovery on behalf of the device side converter that does not support neighbor discovery.
[0343] For example, taking the case where the second device side converter does not have the neighbor discovery capability, the fourth node can send the neighbor discovery configuration information of the second device side converter to the third device side converter to configure and activate the LLDP agent of the third device side converter to perform link layer neighbor discovery on the second device side converter.
[0344] In this case, the third device side converter can send the LLDP frame for searching other neighboring devices instead of the second device side converter. For example, the third device side converter provides the LLDP frame to the second terminal device, and then the second terminal device sends it to the first terminal device through the first PC5 connection (or other PC5 connections between the two). The first terminal device provides the LLDP frame to the second device side converter, and the second device side converter then sends the LLDP frame to other neighboring devices through the second device side converter port.
[0345] In addition, when the second device-side converter receives an LLDP frame, it can provide the LLDP frame to the first terminal device. The first terminal device then forwards the LLDP frame to the second terminal device via the PC5 connection between the first terminal device and the second terminal device (e.g., the first PC5 connection or another PC5 connection between the two). The second terminal device then provides the LLDP frame to the third device-side converter. Ultimately, the third device-side converter determines other neighboring devices (e.g., bridges or TSN terminals) connected to the port of the second device-side converter corresponding to the first terminal device.
[0346] Based on this solution, the second device-side converter corresponding to the first terminal device is not required to have link layer neighbor discovery capability, thereby reducing the capability requirements for the device-side converter.
[0347] Optionally, if the second device-side converter has neighbor discovery capabilities, the LLDP agent of the third device-side converter can be configured to perform link layer neighbor discovery on behalf of the second device-side converter. Based on this solution, the implementation complexity of the second device-side converter can be reduced.
[0348] Optionally, in the case where the first network bridge includes multiple PC5 connections, in step B, the fourth node may perform neighbor discovery configuration for each device-side converter associated with each PC5 connection and subscribe to neighbor discovery information.
[0349] C. The fourth node obtains neighbor discovery information.
[0350] As a possible implementation, when both the second device-side converter and the third device-side converter have neighbor discovery capabilities, the second device-side converter may send first neighbor discovery information to the fourth node to indicate neighbor devices (e.g., other network bridges or TSN terminals) of the second device-side converter port. Furthermore, the third device-side converter may send second neighbor discovery information to the fourth node to indicate neighbor devices (e.g., other network bridges or TSN terminals) of the third device-side converter port.
[0351] As another possible implementation, when the third device side converter has the neighbor discovery capability and the second device side converter does not have the neighbor discovery capability, the third device side converter performs neighbor discovery on behalf of the second device side converter, and the third device side converter sends the first neighbor discovery information and the second neighbor discovery information to the fourth node.
[0352] As another possible implementation, when the third device side converter does not have the neighbor discovery capability and the second device side converter has the neighbor discovery capability, the second device side converter performs neighbor discovery on behalf of the third device side converter, and the second device side converter sends the first neighbor discovery information and the second neighbor discovery information to the fourth node.
[0353] Optionally, in the case where the first network bridge includes multiple PC5 connections, in step C, the fourth node may obtain neighbor discovery information of each device-side converter associated with each PC5 connection.
[0354] Optionally, after steps AC, the fourth node may report the port-related information obtained in steps AC to the fifth node. This port-related information may be reported together with the sixth information in step S608, or separately from the sixth information, as is not specifically limited in this application. After receiving the sixth information and the port-related information obtained in steps AC, the fifth node may determine the structure of the first bridge and the network topology.
[0355] Optionally, after step S608, the communication method may further include the following steps:
[0356] S609: The fifth node sends scheduling information to the fourth node. Correspondingly, the fourth node receives the scheduling information from the fifth node.
[0357] The scheduling information is used to schedule the first bridge to transmit the service flow of the first network (referred to as the service flow to be transmitted), for example, to schedule the first bridge to transmit the service flow of the TSN service or the service flow of the delay-sensitive communication service.
[0358] S610: The fourth node determines QoS information based on the scheduling information, wherein the QoS information can be understood as QoS information corresponding to the scheduling information in a mobile communication system (such as 5GS).
[0359] Optionally, for a service flow to be transmitted, the fourth node may determine, based on the port corresponding to the service flow indicated in the scheduling information, whether the service flow will be transmitted in the first bridge via a PDU session or a PC5 connection. Exemplarily, in step S605 above, the fourth node may obtain a port type, thereby determining, based on the port type, whether the service flow will be transmitted via a PDU session or a PC5 connection.
[0360] For example, if the ingress port corresponding to the service flow is a network-side converter port, and the egress port is a device-side converter port associated with a PDU session, then the service flow corresponds to a downlink PDU session, meaning the service flow will be transmitted via the PDU session, and the transmission direction is downlink. If the ingress port corresponding to the service flow is a device-side converter port associated with a PDU session, and the egress port is a device-side converter port associated with another PDU session, then the service flow corresponds to one downlink PDU session and one uplink PDU session. If both the ingress port and egress port corresponding to the service flow are device-side converters associated with a PC5 connection, then the service flow corresponds to a PC5 connection, meaning the service flow will be transmitted via the PC5 connection.
[0361] Optionally, the specific QoS information determined by the fourth node according to the scheduling information may include the transmission rate and transmission delay corresponding to the service flow.
[0362] Optionally, the fourth node can also determine time sensitive communication assistance information (TSCAI), which may include traffic pattern information of the service flow, such as burst arrival time (Burst Arrival Time), period (Periodicity), flow direction (Flow Direction), and survival time (Survival Time).
[0363] S611: The fourth node sends QoS information to the policy control network element. Correspondingly, the policy control network element receives the QoS information from the fourth node.
[0364] Optionally, when the service flow needs to be transmitted through the PC5 connection, after the policy control network element receives the QoS information, it can modify or establish a QoS flow in the PC5 connection in the first bridge (such as the first PC5 connection) based on the QoS information so that the QoS flow can match the transmission requirements of the service flow.
[0365] Based on the above solution, if the network bridge includes a PC5 connection and its associated device-side converter port, the policy control network element can establish or modify a QoS flow in the PC5 connection based on the QoS information provided by the fourth node to transmit services from the first network. Furthermore, the terminal device associated with the PC5 connection can obtain transmission resources for carrying services based on the TSCAI. In other words, if the network bridge includes a PC5 connection, the PC5 connection is enabled to operate, thereby enabling the transmission of services from the first network.
[0366] Optionally, in step S611, the fourth node may also send TSCAI to the policy control network element. Accordingly, the policy control network element may provide TSCAI to the terminal devices associated with the PC5 connection used to transmit the service flow (such as the first terminal device and the second terminal device associated with the first PC5 connection). When providing the TSCAI, the policy control network element may indicate the QoS flow associated with the TSCAI, or the terminal device may associate the TSCAI with a certain QoS flow by itself. In addition, the terminal device may select resources based on the TSCAI, such as determining the period of periodic resources and the resource size in each period based on the TSCAI, or applying for resources from the RAN based on the TSCAI, that is, when applying for resources, the resource period and / or resource size in each period that the terminal device prefers (or requires) may be indicated.
[0367] Alternatively, the policy control network element can provide the TSCAI to the RAN. When providing the TSCAI, the policy control network element can indicate the QoS flow associated with the TSCAI, or the RAN can associate the TSCAI with a specific QoS flow. After receiving the TSCAI, the RAN can allocate resources based on the TSCAI to the terminal device associated with the PC5 connection used to transmit the service flow. The terminal device can then use the resources allocated by the RAN to transmit the service flow.
[0368] In the communication method provided in the above embodiment, a first node assigns a port number to the device-side converter port associated with PC5 in the first network bridge. Furthermore, an embodiment of the present application also provides a communication method in which a second node assigns a port number to the device-side converter port associated with PC5 in the first network bridge. As shown in FIG8 , the communication method includes the following steps:
[0369] S800: Authorize multiple terminal devices related to the first network. The multiple terminal devices include a first terminal device and a second terminal device. Please refer to the relevant description of step S600 above and will not be repeated here.
[0370] S801. A first PDU session is established between a first terminal device and a first node.
[0371] In step S801, the first node allocates a first port number to a device-side converter port associated with the first PDU session and the first terminal device in the first network bridge. Furthermore, the first node sends first indication information to the session management network element. In response, the session management network element receives the first indication information from the first node. The first indication information indicates the first port number. The implementation of step S801 can be referenced to the relevant description of step S601 above and will not be repeated here.
[0372] S802: The first terminal device and the second terminal device establish a first PC 5 connection. Please refer to the relevant description in the above step S602, which will not be repeated here.
[0373] S803: The terminal device sends the second information or the third information to the second node. Correspondingly, the second node receives the second information or the third information from the terminal device.
[0374] The second information includes the number of ports and / or the number of direct communication connections. The number of ports refers to the number of device-side converter ports in the first network bridge that are associated with the direct communication connections and that require port numbers to be assigned by the second node. The number of direct communication connections is used to determine the number of device-side converter ports in the first network bridge that are associated with the direct communication connections and that require port numbers to be assigned by the second node. The third information includes information about the connection of the first PC 5. The terminal device can be the first terminal device or the second terminal device. For other details of the second or third information, please refer to the relevant description in step S603 above and will not be repeated here.
[0375] Optionally, in this embodiment, the second node may be a session management network element, a policy control network element, or an AF network element. In the case where the second node is a policy control network element or an AF network element, the first terminal device or the second terminal device may further send identification information of the first PDU session, or identification information of the first node (such as a user plane node identifier), or identification information of the first bridge to the second node. This identification information may be used to indicate that the first PC5 connection and the first PDU session belong to the same bridge.
[0376] Optionally, when the second node is a policy control network element or an AF network element, after the session management network element in the above step S801 receives a reply from the first node, it can indicate the first port number, the user plane node identifier of the first node and other information related to the first bridge to the policy control network element or the AF network element.
[0377] S804: The second node allocates a port number to the device-side converter port associated with the PC 5 in the first network bridge according to the second information or the third information.
[0378] Optionally, after receiving the second information or the third information, the second node may assign a port number to the device-side converter port associated with PC5 in the first network bridge. This embodiment of the present application uses an example in which the port number assigned by the second node includes the second port number and the third port number. The implementation of the second node assigning a port number to the device-side converter port associated with PC5 in the first network bridge can be referenced to the description of the first node assigning a port number in step S604 above, and is not further described here.
[0379] S805-S810 are the same as the above steps S606-S611. Please refer to the relevant instructions in steps S606-S611 and will not be repeated here.
[0380] Optionally, when the second node is an AF network element, the second node and the fourth node are the same node, and therefore, the action of the second node sending information to the fourth node in step S805 may not be performed.
[0381] It can be understood that in the method shown in Figure 8, the port number of the device-side converter port associated with the PDU session is assigned by the first node, and the port number of the device-side converter port associated with the PC5 connection is assigned by the second node. In the method shown in Figure 5, the port number of the device-side converter port associated with the PDU session and the port number of the device-side converter port associated with the PC5 connection are both assigned by the first node.
[0382] That is, for the second node, the port number of the device-side converter port associated with the PDU session and the port number of the device-side converter port associated with the PC5 connection can be obtained in the following two ways:
[0383] Method 1: The second node receives information A from the first node, where the information A is used to indicate the port number of the device-side converter port associated with the PDU session and the port number of the device-side converter port associated with the PC5 connection.
[0384] Method 2: The second node receives information B from the first node, which indicates the port number of the device-side converter port associated with the PDU session. The second node also assigns a port number to the device-side converter port associated with the PC5 connection in the first network bridge.
[0385] For example, taking the first port number, the second port number, and the third port number as an example, the second node can obtain these three port numbers in the following two ways:
[0386] Method 1: The second node receives first information from the first node, where the first information is used to indicate the first port number, the second port number, and the third port number.
[0387] Mode 2: The second node receives first indication information from the first node, where the first indication information is used to indicate the first port number, and the second node allocates the second port number and the third port number.
[0388] Based on this solution, while using PDU sessions and PC5 connections to support the integration of the mobile communication system and the first network, the mobile communication system's support capability for the first network bridge is enhanced, while reducing the implementation complexity of the first node in the mobile communication system.
[0389] It is understandable that in each of the above embodiments, the methods and / or steps implemented by the first node may also be implemented by components applicable to the first node (e.g., processor, chip, chip system, circuit, logic module, or software); the methods and / or steps implemented by the second node may also be implemented by components applicable to the second node (e.g., processor, chip, chip system, circuit, logic module, or software); and the methods and / or steps implemented by the fourth node may also be implemented by components applicable to the fourth node (e.g., processor, chip, chip system, circuit, logic module, or software). The chip system may be composed of a chip, or the chip system may include a chip and other discrete devices.
[0390] It is understandable that, in order to realize the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0391] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.
[0392] Communication Device Figure 9 shows a schematic structural diagram of a communication device 90. The communication device 90 includes a processing module 901 and a transceiver module 902. The communication device 90 can be used to implement the functions of the first node, the second node, or the fourth node described above.
[0393] In some embodiments, the communication device 90 may further include a storage module (not shown in FIG. 9 ) for storing program instructions and data.
[0394] In some embodiments, the transceiver module 902, which may also be referred to as a transceiver unit, is configured to implement a transmitting and / or receiving function. The transceiver module 902 may be composed of a transceiver circuit, a transceiver, a transceiver, or a communication interface.
[0395] In some embodiments, the transceiver module 902 may include a receiving module and a sending module, which are respectively used to execute the receiving and sending steps performed by the first node, the second node or the fourth node in the above method embodiments, and / or other processes for supporting the technology described herein; the processing module 901 may be used to execute the processing steps (such as determination, effectiveness, etc.) performed by the first node, the second node or the fourth node in the above method embodiments, and / or other processes for supporting the technology described herein.
[0396] When the communication device 90 is used to implement the function of the first node:
[0397] Processing module 901 is configured to assign a first port number, a second port number, and a third port number to a device-side converter port of a first network bridge; transceiver module 902 is configured to send first information to a second node, the first information being used to indicate the first port number, the second port number, and the third port number. The first network bridge includes: a first PDU session, a first network-side converter port, and a first device-side converter port; the first network-side converter port is the network-side converter port associated with the first PDU session and the first node in the first network bridge, and the first device-side converter port is the device-side converter port associated with the first PDU session and the first terminal device in the first network bridge. The first network bridge also includes: a first direct communication connection between the first terminal device and the second terminal device, a second device-side converter port, and a third device-side converter port; the second device-side converter port is the device-side converter port associated with the first direct communication connection and the first terminal device in the first network bridge, and the third device-side converter port is the device-side converter port associated with the first direct communication connection and the second terminal device in the first network bridge.
[0398] Optionally, before allocating the second port number and the third port number to the device-side converter port of the first network bridge, the transceiver module 902 is further used to receive second information from a third node, where the second information is used to instruct the first node to allocate a port number to the device-side converter port associated with the direct communication connection in the first network bridge.
[0399] Optionally, before allocating the second port number and the third port number to the device-side converter port of the first network bridge, the transceiver module 902 is further configured to receive third information from a third node, where the third information includes information about the first direct communication connection.
[0400] When the communication device 90 is used to implement the function of the second node:
[0401] Processing module 901 is configured to obtain a first port number, a second port number, and a third port number of a device-side converter port of a first network bridge; transceiver module 902 is configured to send fourth information to a fourth node, the fourth information being used to indicate the first port number, the second port number, and the third port number, where the first port number is the port number of the first device-side converter port, the second port number is the port number of the second device-side converter port, and the third port number is the port number of the third device-side converter port. The first network bridge includes: a first PDU session, a first network-side converter port, and a first device-side converter port; the first network-side converter port is the network-side converter port associated with the first PDU session and the first node in the first network bridge, and the first device-side converter port is the device-side converter port associated with the first PDU session and the first terminal device in the first network bridge. The first network bridge also includes: a first direct communication connection between the first terminal device and the second terminal device, a second device-side converter port and a third device-side converter port; the second device-side converter port is a device-side converter port in the first network bridge associated with the first direct communication connection and the first terminal device, and the third device-side converter port is a device-side converter port in the first network bridge associated with the first direct communication connection and the second terminal device.
[0402] Optionally, the processing module 901 is used to obtain the first port number, the second port number and the third port number of the device side converter port of the first bridge, including: the processing module 901 is used to receive the first information from the first node through the transceiver module 902, and the first information is used to indicate the first port number, the second port number and the third port number.
[0403] Optionally, before receiving the first information from the first node, the transceiver module 902 is further configured to receive fifth information from the first terminal device or the second terminal device, where the fifth information is information about the first direct communication connection.
[0404] Optionally, the transceiver module 902 is further configured to send second information to the first node, where the second information is configured to instruct the first node to allocate a port number to a device-side converter port associated with the direct communication connection in the first network bridge.
[0405] Optionally, the processing module 901 is used to obtain the first port number, the second port number and the third port number of the device side converter port of the first network bridge, including: the processing module 901 is used to receive the first indication information from the first node through the transceiver module 902, the first indication information is used to indicate the first port number; the processing module 901 is also used to allocate the second port number and the third port number.
[0406] When the communication device 90 is used to implement the function of the fourth node:
[0407] Processing module 901 is used to determine sixth information, which is used to indicate the first network bridge; transceiver module 902 is used to send the sixth information to the fifth node. The first network bridge includes: a first PDU session, a first network-side converter port, and a first device-side converter port; the first network-side converter port is the network-side converter port associated with the first PDU session and the first node in the first network bridge, and the first device-side converter port is the device-side converter port associated with the first PDU session and the first terminal device in the first network bridge. The first network bridge also includes: a first proximity service connection direct communication connection between the first terminal device and the second terminal device, a second device-side converter port, and a third device-side converter port; the second device-side converter port is the device-side converter port associated with the first direct communication connection and the first terminal device in the first network bridge, and the third device-side converter port is the device-side converter port associated with the first direct communication connection and the second terminal device in the first network bridge.
[0408] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.
[0409] In the present application, the communication device 90 may be presented in the form of functional modules divided in an integrated manner. The "module" here may refer to a specific application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.
[0410] In some embodiments, when the communication device 90 in Figure 9 is a chip or a chip system, the function / implementation process of the transceiver module 902 can be implemented through the input and output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 901 can be implemented through the processor (or processing circuit) of the chip or chip system.
[0411] Since the communication device 90 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.
[0412] As a possible product form, the first node, the second node or the fourth node described in the embodiments of the present application can also be implemented using the following: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.
[0413] As another possible product form, the first node, second node, or fourth node in this application may adopt the composition structure shown in Figure 10, or include the components shown in Figure 10. Figure 10 is a schematic diagram of the composition of a communication device 1000 provided in this application. The communication device 1000 may be a first node or a module, chip, or system-on-chip in the first node; or, it may be a second node or a chip or system-on-chip in the second node; or, it may be a fourth node or a chip or system-on-chip in the fourth node.
[0414] As shown in FIG10 , the communication device 1000 includes at least one processor 1001 and at least one communication interface ( FIG10 is merely an example of an example of a communication interface 1004 and a processor 1001). Optionally, the communication device 1000 may further include a communication bus 1002 and a memory 1003.
[0415] Processor 1001 may be a general-purpose central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. Processor 1001 may also be other devices with processing capabilities, such as circuits, devices, or software modules, without limitation.
[0416] Communication bus 1002 is used to connect the various components in communication device 1000, enabling communication between them. Communication bus 1002 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, for example. Such buses can be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG10 shows a single thick line, but this does not imply that there is only one bus or type of bus.
[0417] Communication interface 1004 is used to communicate with other devices or communication networks. Exemplarily, communication interface 1004 can be a module, circuit, transceiver, or any other device capable of communication. Optionally, communication interface 1004 can also be an input / output interface within processor 1001, used to implement signal input and output to the processor.
[0418] The memory 1003 may be a device with a storage function, used to store instructions and / or data, wherein the instructions may be computer programs.
[0419] Exemplarily, the memory 1003 may be a read-only memory (ROM) or other types of static storage devices that can store static information and / or instructions, or a random access memory (RAM) or other types of dynamic storage devices that can store information and / or instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., without limitation.
[0420] It should be noted that the memory 1003 can exist independently of the processor 1001 or can be integrated with the processor 1001. The memory 1003 can be located within the communication device 1000 or outside the communication device 1000, without limitation. The processor 1001 can be used to execute instructions stored in the memory 1003 to implement the methods provided in the following embodiments of the present application.
[0421] As an optional implementation, the communication device 1000 may further include an output device 1005 and an input device 1006. The output device 1005 communicates with the processor 1001 and can display information in a variety of ways. For example, the output device 1005 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 1006 communicates with the processor 1001 and can receive user input in a variety of ways. For example, the input device 1006 can be a mouse, a keyboard, a touch screen device, or a sensor device.
[0422] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the communication device 90 shown in FIG. 9 may take the form of the communication device 1000 shown in FIG. 10 .
[0423] As an example, the functions / implementation process of the processing module 901 in FIG9 can be implemented by the processor 1001 in the communication device 1000 shown in FIG10 calling the computer-executable instructions stored in the memory 1003. The functions / implementation process of the transceiver module 902 in FIG9 can be implemented by the communication interface 1004 in the communication device 1000 shown in FIG10.
[0424] It should be noted that the structure shown in FIG10 does not constitute a specific limitation on the first node, the second node, or the fourth node. For example, in other embodiments of the present application, the first node, the second node, or the fourth node may include more or fewer components than shown in the figure, or combine or split certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
[0425] In some embodiments, an embodiment of the present application further provides a communication device, which includes a processor for implementing the method in any of the above method embodiments.
[0426] As a possible implementation, the communication device further includes a memory. The memory is used to store necessary computer programs and data. The computer program may include instructions, and the processor may invoke the instructions in the computer program stored in the memory to instruct the communication device to execute any of the above-described method embodiments. Of course, the memory may not be located in the communication device.
[0427] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, and the interface circuit is used to receive computer execution instructions (computer execution instructions are stored in a memory, may be read directly from the memory, or may pass through other devices) and transmit them to the processor.
[0428] As another possible implementation, the communication device further includes a communication interface, where the communication interface is used to communicate with a module outside the communication device.
[0429] It can be understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or include chips and other discrete devices. The embodiments of the present application do not specifically limit this.
[0430] The present application also provides a computer-readable storage medium having a computer program or instruction stored thereon, which implements the functions of any of the above method embodiments when executed by a computer.
[0431] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.
[0432] Those skilled in the art will appreciate that, for the sake of convenience and brevity of description, the specific working processes of the above-described systems, devices, and units may refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0433] It is understood that the systems, devices, and methods described in this application may also be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be through some interface, indirect coupling or communication connection of devices or units, and may be electrical, mechanical, or other forms.
[0434] The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. Components shown as units may or may not be physical units. Some or all of these units may be selected to achieve the objectives of this embodiment as needed.
[0435] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0436] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state drive (SSD)). In the embodiment of the present application, the computer may include the aforementioned device.
[0437] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.
[0438] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.
Claims
1. A communication method, characterized in that: The method is applied to a first node, and the method comprises: assigning a first port number, a second port number, and a third port number to a device-side converter port of a first network bridge; Sending first information to the second node, where the first information is used to indicate the first port number, the second port number, and the third port number; The first network bridge comprises: a first protocol data unit PDU session, a first network side converter port and a first device side converter port; the first network side converter port is a network side converter port associated with the first PDU session and the first node in the first network bridge, and the first device side converter port is a device side converter port associated with the first PDU session and the first terminal device in the first network bridge; The first network bridge also includes: a first direct communication connection between the first terminal device and the second terminal device, a second device-side converter port and a third device-side converter port; the second device-side converter port is a device-side converter port in the first network bridge associated with the first direct communication connection and the first terminal device, and the third device-side converter port is a device-side converter port in the first network bridge associated with the first direct communication connection and the second terminal device.
2. The method according to claim 1, characterized in that The first information is further used to indicate that the first port number is the port number of the device-side converter port associated with the first PDU session; The first information is further used to indicate that the second port number and the third port number are port numbers of device-side converter ports associated with the direct communication connection; or, The first information is further used to indicate that the second port number and the third port number are port numbers of device-side converter ports associated with the first direct communication connection; or, The first information is also used to indicate that the second port number is the port number of the device side converter port associated with the first direct communication connection and the first terminal device, and the third port number is the port number of the device side converter port associated with the first direct communication connection and the second terminal device.
3. The method according to claim 1 or 2, characterized in that: Before allocating the second port number and the third port number to the device-side converter port of the first network bridge, the method further includes: Second information is received from a third node, wherein the second information is used to instruct the first node to allocate a port number to a device-side converter port associated with a direct communication connection in the first bridge.
4. The method according to claim 3, characterized in that The second information includes the number of ports and / or the number of direct communication connections; The number of ports is the number of device-side converter ports in the first network bridge that are associated with the direct communication connection and that require the first node to allocate port numbers; The number of direct communication connections is used to determine the number of device-side converter ports in the first network bridge that are associated with the direct communication connections and that require the first node to allocate port numbers.
5. The method according to claim 1 or 2, characterized in that: Before allocating the second port number and the third port number to the device-side converter port of the first network bridge, the method further includes: Third information is received from a third node, where the third information includes information about the first direct communication connection.
6. The method according to claim 5, characterized in that The third information includes a first layer 2 identifier and / or a second layer 2 identifier; The first layer 2 identifier is an identifier of the first terminal device associated with the first direct communication connection, and the second layer 2 identifier is an identifier of the second terminal device associated with the first direct communication connection.
7. The method according to claim 5 or 6, characterized in that: The third information includes an identifier of the first direct communication connection.
8. The method according to any one of claims 5 to 7, characterized in that: The third information includes at least one of the following: first identification information, first application information, second identification information, second application information, port management capability information corresponding to the second device side converter port, residence time corresponding to the second device side converter port, port management capability information corresponding to the third device side converter port, or residence time corresponding to the third device side converter port; The first identification information includes at least one of the following: a media access control MAC address of a converter port on the second device side, an international mobile subscriber identity IMSI of the first terminal device, a temporary mobile subscriber identity TMSI of the first terminal device, or an international mobile equipment identity IMEI of the first terminal device; The first application information includes at least one of the following: an application identifier associated with the first direct communication connection, an application group identifier associated with the first direct communication connection, an application layer identifier associated with the first direct communication connection, or an identifier of a network served by the first terminal device; The second identification information includes at least one of the following: a MAC address of the converter port on the third device side, an IMSI of the second terminal device, a TMSI of the second terminal device, or an IMEI of the second terminal device; The second application information includes at least one of the following: an application identifier associated with the first direct communication connection, an application group identifier associated with the first direct communication connection, an application layer identifier associated with the first direct communication connection, or an identifier of a network served by the second terminal device.
9. The method according to any one of claims 3 to 8, characterized in that: The third node is a session management network element, the first terminal device or the second terminal device.
10. The method according to any one of claims 1 to 9, characterized in that: The first network bridge also includes: a second PDU session and a fourth device-side converter port; the fourth device-side converter port is a device-side converter port in the first network bridge that is associated with the second PDU session and the second terminal device.
11. A communication method, characterized in that: The method is applied to the second node, and the method includes: Obtain a first port number, a second port number, and a third port number of a device-side converter port of a first network bridge; Sending fourth information to a fourth node, the fourth information being used to indicate the first port number, the second port number, and the third port number, the first port number being the port number of the first device side converter port, the second port number being the port number of the second device side converter port, and the third port number being the port number of the third device side converter port; The first network bridge comprises: a first protocol data unit PDU session, a first network side converter port and the first device side converter port; the first network side converter port is a network side converter port associated with the first PDU session and the first node in the first network bridge, and the first device side converter port is a device side converter port associated with the first PDU session and the first terminal device in the first network bridge; The first network bridge also includes: a first direct communication connection between the first terminal device and the second terminal device, the second device side converter port and the third device side converter port; the second device side converter port is a device side converter port in the first network bridge associated with the first direct communication connection and the first terminal device, and the third device side converter port is a device side converter port in the first network bridge associated with the first direct communication connection and the second terminal device.
12. The method according to claim 11, characterized in that The fourth information is further used to indicate at least one of the following: The first port number is the port number of the device-side converter port associated with the PDU session, The second port number and the third port number are port numbers of the device-side converter ports associated with the direct communication connection, The second port number and the third port number are port numbers of the device-side converter ports associated with the same direct communication connection, a media access control MAC address of the second device-side converter port, The dwell time corresponding to the second device side converter port, The port management capability information corresponding to the port of the second device side converter, the MAC address of the third device-side converter port, The dwell time corresponding to the third device-side converter port, or The port management capability information corresponding to the converter port on the third device side.
13. The method according to claim 11 or 12, characterized in that: Obtaining a first port number, a second port number, and a third port number of a device-side converter port of a first network bridge includes: First information is received from the first node, where the first information is used to indicate the first port number, the second port number, and the third port number.
14. The method according to claim 13, characterized in that The first information is further used to indicate that the first port number is the port number of the device-side converter port associated with the first PDU session; The first information is further used to indicate that the second port number and the third port number are port numbers of device-side converter ports associated with the direct communication connection; or, The first information is further used to indicate that the second port number and the third port number are port numbers of device-side converter ports associated with the first direct communication connection; or, The first information is also used to indicate that the second port number is the port number of the device side converter port associated with the first direct communication connection and the first terminal device, and the third port number is the port number of the device side converter port associated with the first direct communication connection and the second terminal device.
15. The method according to claim 13 or 14, characterized in that The method further comprises: Second information is sent to the first node, where the second information is used to instruct the first node to allocate a port number to a device-side converter port associated with the direct communication connection in the first network bridge.
16. The method according to claim 15, characterized in that The second information includes the number of ports and / or the number of direct communication connections; The port number is the number of devices in the first bridge that are associated with the direct communication connection and that require the first node to allocate port numbers. The number of converter ports; The number of direct communication connections is used to determine the number of device-side converter ports in the first network bridge that are associated with the direct communication connections and that require the first node to allocate port numbers.
17. The method according to any one of claims 13 to 16, characterized in that: Before receiving the first information from the first node, the method further includes: Receive fifth information from the first terminal device or the second terminal device, where the fifth information is information about the first direct communication connection.
18. The method according to claim 11 or 12, characterized in that: Obtaining a first port number, a second port number, and a third port number of a device-side converter port of a first network bridge includes: receiving first indication information from the first node, where the first indication information is used to indicate the first port number; The second port number and the third port number are assigned.
19. The method according to any one of claims 11 to 18, characterized in that: The first network bridge also includes: a second PDU session and a fourth device-side converter port; the fourth device-side converter port is a device-side converter port in the first network bridge that is associated with the second PDU session and the second terminal device.
20. A communication method, characterized in that: The method is applied to the fourth node, and the method includes: determining sixth information, where the sixth information is used to indicate the first network bridge; Sending the sixth information to the fifth node; The first network bridge comprises: a first protocol data unit PDU session, a first network side converter port and a first device side converter port; the first network side converter port is a network side converter port associated with the first PDU session and the first node in the first network bridge, and the first device side converter port is a device side converter port associated with the first PDU session and the first terminal device in the first network bridge; The first network bridge also includes: a first direct communication connection between the first terminal device and the second terminal device, a second device-side converter port and a third device-side converter port; the second device-side converter port is a device-side converter port in the first network bridge associated with the first direct communication connection and the first terminal device, and the third device-side converter port is a device-side converter port in the first network bridge associated with the first direct communication connection and the second terminal device.
21. The method according to claim 20, characterized in that The sixth information includes at least one of the following: The identifier of the first network bridge, the number of ports in the first network bridge, the first port number, the second port number, the third port number or port pair information; the first port number is the port number of the first device side converter port, the second port number is the port number of the second device side converter port, and the third port number is the port number of the third device side converter port; the port pair information indicates the port pair in the first network bridge, the port pair includes the first port pair and the second port pair, the first port pair includes the first device side converter port and the first network side converter port, and the second port pair includes the second device side converter port and the third device side converter port.
22. The method according to claim 20 or 21, characterized in that The first network bridge further includes: A second PDU session and a fourth device-side converter port; the fourth device-side converter port is a device-side converter port in the first network bridge associated with the second PDU session and the second terminal device.
23. A communication device, characterized in that: The communication device includes a processor; the processor is used to run a computer program or instructions so that the communication device performs the method described in any one of claims 1-10, or so that the communication device performs the method described in any one of claims 11-19, or so that the communication device performs the method described in any one of claims 20-22.
24. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions or programs, which, when executed on a computer, cause the method described in any one of claims 1 to 10 to be executed, or cause the method described in any one of claims 11 to 19 to be executed, or cause the method described in any one of claims 20 to 22 to be executed.
25. A computer program product, characterized in that The computer program product includes computer instructions; when part or all of the computer instructions are executed on a computer, the method according to any one of claims 1 to 10 is executed, or the method according to any one of claims 11 to 19 is executed, or the method according to any one of claims 20 to 22 is executed.
Citation Information
Patent Citations
Methods, apparatuses and systems for session establishment in a wireless communication network
CN114008993A
Methods and Apparatuses for Logical TSN Bridge
US20220322254A1
Method and device for communication
WO2020221266A1
Communication method and apparatus
WO2023029488A1
Method, apparatus, and computer program product for local bridging using a multiport device
WO2023079340A1
