CN117641320A

CN117641320A - Service flow routing method and device

Info

Publication number: CN117641320A
Application number: CN202210980340.XA
Authority: CN
Inventors: 于游洋; 时书锋; 宗在峰
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-08-16
Filing date: 2022-08-16
Publication date: 2024-03-01
Also published as: WO2024037256A1

Abstract

The application provides a service flow routing method and device. The method comprises the following steps: the method comprises the steps that a first terminal device sends a first registration message, wherein the first registration message carries first capability information, and the first capability information indicates that the first terminal device has PIN network management capability; the first terminal equipment acquires a first PIN network local routing rule from a strategy control function network element, wherein the first PIN network local routing rule is related to first capability information; the first terminal device sends a first PIN network local routing rule to the second terminal device. In the method, a network side can generate a first PIN network local routing rule, and then the first PIN network local routing rule is sent to second terminal equipment through first terminal equipment with PIN network management capability, so that the second terminal equipment can execute local routing on the service flow, realize transmission of the service flow under a PIN network architecture, and realize local routing of the service flow in the PIN network under control of the network side.

Description

Service flow routing method and device

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a service flow routing method and apparatus.

Background

With the continuous enhancement of 5G core network (5G core,5 gc) network functions and more abundant terminal devices, management and control of personal internet of things (internet of things, ioT) networks (personal IoT network, PIN) by operators are the goal of the next stage network enhancement.

In the related art, a PIN network architecture is proposed, and the PIN network includes a PIN network management function device (PIN Element with management capability, PMEC), a PIN network gateway function device (PIN Element with gateway capability, PEGC), and other PIN elements. PEMC and PEGC are 5GC access capable user equipment that can access 5GC through third generation partnership project (3rd generation partnership project,3GPP) or non-3GPP (non-3 GPP) access technologies. Other PIN elements are end devices, such as smart wearable devices, smart home devices, etc.

However, only a PIN network architecture is proposed in the related art, and a communication scheme under the PIN network architecture has not been proposed yet.

Disclosure of Invention

The embodiment of the application provides a service flow routing method and device, which can realize the communication flow under a PIN network architecture and can realize the local routing of the service flow in the PIN network under the control of a network side.

In a first aspect, a service flow routing method is provided, including the following steps: the method comprises the steps that a first terminal device sends a first registration message, wherein the first registration message carries first capability information, and the first capability information indicates that the first terminal device has PIN network management capability; the first terminal equipment acquires a first PIN network local routing rule from a strategy control function network element, wherein the first PIN network local routing rule is related to first capability information; the first terminal device sends a first PIN network local routing rule to the second terminal device.

In the method, a network side can generate a first PIN network local routing rule, and then the first PIN network local routing rule is sent to second terminal equipment through first terminal equipment with PIN network management capability, so that the second terminal equipment can execute local routing on the service flow, realize transmission of the service flow under a PIN network architecture, and realize local routing of the service flow in the PIN network under control of the network side.

In one possible implementation, the first PIN network local routing rule includes one or more of the following information: data network name or slice information indicating that the traffic flow in the protocol data unit (protocol data unit, PDU) session to which the data network name or slice information corresponds is allowed to be routed locally. In the implementation, the network side generates PIN network local routing rules for realizing local routing by taking PDU session as granularity, and controls the routing of the service flow.

Optionally, the first PIN network local routing rule further includes local routing indication information, where the local routing indication information indicates that a local routing is allowed for a traffic flow in a PDU session corresponding to a data network name or slice information.

In one possible implementation, the first PIN network local routing rule includes a list of device identifications. In the implementation, the service flow corresponding to the equipment identifier allows local routing, and the network side generates PIN network local routing rules for realizing the local routing by taking the service flow as granularity to control the routing of the service flow.

Optionally, the first PIN network local routing rule includes local routing indication information, where the local routing indication information indicates that a traffic flow corresponding to a device identifier in the device identifier list is allowed to perform local routing.

The first terminal equipment can also receive the corresponding relation between the address information from the second terminal equipment and the equipment identifier, and the equipment identifier is determined by the second terminal equipment based on the equipment identifier list; the first terminal equipment acquires a local routing rule of the second PIN network according to the corresponding relation; the first terminal device sends a second PIN network local routing rule to the second terminal device. The second terminal equipment is based on the local policy or the user preference and the determined equipment identification, so that the second PIN network local routing rule acquired by the first terminal equipment is related to the local policy or the user preference of the second terminal equipment, and the second terminal equipment can execute local routing on the service flow based on the second PIN network local routing rule to realize the local routing of the service flow in the PIN network.

In one possible implementation, when the first terminal device obtains the second PIN network local routing rule according to the correspondence, the first terminal device may send the correspondence to the policy control function network element and receive the second PIN network local routing rule from the policy control function network element. In the implementation, the network side generates PIN network local routing rules for realizing local routing by taking the service flow as granularity, and controls the routing of the service flow.

In one possible implementation, when the first terminal device obtains the second PIN network local routing rule according to the correspondence, the first terminal device may generate the second PIN network local routing rule according to the correspondence. In this implementation, the first terminal device may itself generate a PIN network local routing rule for implementing local routing, and control routing of the traffic flow.

In one possible implementation, the second PIN network local routing rules include one or more of the following information: address information or device identification, the address information or device identification indicates that the traffic flow corresponding to the address information or device identification allows local routing.

In a second aspect, a service flow routing method is provided, including the following steps: the second terminal equipment sends a second registration message, wherein the second registration message carries second capability information, and the second capability information indicates that the second terminal equipment has PIN network gateway capability; the second terminal equipment acquires a first PIN network local routing rule; and the second terminal equipment executes local routing on the acquired service flow according to the local routing rule of the first PIN network.

In one possible implementation, when the second terminal device obtains the first PIN network local routing rule, the first PIN network local routing rule may be obtained from the policy control function network element, where the first PIN network local routing rule is related to the second capability information; or the first PIN network local routing rule may be obtained from the first terminal device, where the first PIN network local routing rule is related to first capability information, and the first capability information indicates that the first terminal device has PIN network management capability. In this implementation, the second terminal device may directly obtain the PIN network local routing rule for local routing from the policy control function network element, or may obtain the PIN network local routing rule through the first terminal device, and then perform local routing on the service flow, so that transmission of the service flow under the PIN network architecture may be implemented, and local routing of the service flow in the PIN network may be implemented.

In one possible implementation, when the second terminal device performs local routing on the acquired service flow according to the first PIN network local routing rule, if the acquired service flow is matched with the first PIN network local routing rule, the second terminal device sends the service flow to the destination terminal device of the service flow in the PIN network where the second terminal device is located.

In one possible implementation, the traffic flow matches the first PIN network local routing rule, including one or more of: the flow description information in the local routing rule of the first PIN network comprises information carried by data packets in service flows; and/or the data network name in the first PIN network local routing rule comprises the data network name of the PDU session corresponding to the service flow; and/or slice information in the local routing rule of the first PIN network comprises slice information of PDU session corresponding to the service flow; and/or the destination terminal equipment corresponding to the destination address information carried in the service flow and the second terminal equipment belong to the same PIN network.

In one possible implementation, the data network name in the first PIN network local routing rule includes a data network name of a PDU session corresponding to an uplink traffic flow or a data network name of a PDU session corresponding to a downlink traffic flow.

In one possible implementation, the slice information in the first PIN network local routing rule includes slice information of a PDU session corresponding to an uplink traffic flow or slice information of a PDU session corresponding to a downlink traffic flow.

In one possible implementation, the first PIN network local routing rule includes one or more of the following information: the data network name or slice information indicates that the traffic flow in the PDU session corresponding to the data network name or slice information is allowed to be routed locally.

In one possible implementation, the first PIN network local routing rule includes a list of device identifications.

The second terminal equipment can determine the equipment identifier and address information corresponding to the equipment identifier in the equipment identifier list when executing local routing on the acquired service flow according to the first PIN network local routing rule; sending the corresponding relation between the address information and the equipment identifier to first terminal equipment; acquiring a second PIN network local routing rule from the first terminal equipment; and if the acquired service flow is matched with the local routing rule of the second PIN network, the second terminal equipment sends the service flow to the target terminal equipment of the service flow in the PIN network where the second terminal equipment is located.

In one possible implementation, when the second terminal device determines the device identity in the device identity list, one or more PIN members may be determined in the PIN member list; and/or one or more PIN gateway devices may be determined in the PIN gateway device list.

In one possible implementation, the traffic flow matches the second PIN network local routing rule, including one or more of: the flow description information in the local routing rule of the second PIN network comprises information carried by the data packet in the service flow; and/or the PIN members in the local routing rule of the second PIN network comprise the PIN members corresponding to the service flow; and/or the PIN member in the local routing rule of the second PIN network comprises a destination terminal device corresponding to the service flow; and/or the address information in the second PIN network local routing rule comprises destination address information in the traffic flow.

In one possible implementation, the PIN members in the second PIN network local routing rule include PIN members and/or destination terminal devices corresponding to the uplink traffic flow or PIN members and/or destination terminal devices corresponding to the downlink traffic flow.

In a third aspect, a service flow routing method is provided, including the following steps: the method comprises the steps that a policy control function network element receives a policy acquisition message, wherein the policy acquisition message carries indication information, and the indication information indicates that a first terminal device has personal internet of things PIN network management capability or a second terminal device has PIN network gateway capability; the strategy control function network element determines to allow the local route according to the indication information; the policy control function network element sends a first PIN network local routing rule.

The policy control function network element may also receive a correspondence between address information and a device identifier, where the device identifier is determined by the second terminal device in the device identifier list; the strategy control function network element generates a second PIN network local routing rule according to the corresponding relation; the policy control function network element sends the second PIN network local routing rule to the first terminal device.

In a fourth aspect, a communication apparatus is provided, which may be a first terminal device or a second terminal device or a policy control function network element, or a chip arranged in the first terminal device or the second terminal device or the policy control function network element. The communication device may implement the method provided in any of the above aspects.

The communication device comprises corresponding modules, units or means (means) for implementing the above method, where the modules, units or means may be implemented by hardware, software, or implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

In a fifth aspect, a communication device is provided, including a transceiver unit. Optionally, the communication device further comprises a processing unit. The communications apparatus may implement any aspect or any method provided by any of the aspects.

In a sixth aspect, a communication device is provided that includes a processor. The processor may be operative to perform the methods provided by any one of the above aspects or any implementation of any one of the aspects. Optionally, the apparatus further comprises a memory, the processor being coupled to the memory, the memory storing a computer program or instructions, the processor being executable to cause the apparatus to perform any one of the above aspects or to implement the provided method.

In a seventh aspect, a communication device is provided that includes an interface circuit and a logic circuit coupled to the interface circuit. The interface circuit may be a code/data read/write interface circuit for receiving computer-executable instructions (stored in memory, possibly read directly from memory, or possibly via other means) and transmitting to the logic circuit for causing the logic circuit to execute the computer-executable instructions to perform the methods provided by any one of the above aspects or any one of the other aspects.

In some possible designs, the communication device may be a chip or a system-on-chip.

In an eighth aspect, a communications apparatus is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory and may receive signals via the receiver and transmit signals via the transmitter to perform any one of the above aspects or to implement the provided methods.

In the alternative, the processor may be one or more, and the memory may be one or more. Alternatively, the memory may be integrated with the processor or the memory may be separate from the processor.

In a specific implementation process, the memory may be a non-transient (non-transitory) memory, for example, a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips, where the type of the memory and the manner of disposing the memory and the processor are not limited in this application.

The communication device may be a chip, and the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor, implemented by reading software code stored in a memory, which may be integrated in the processor, or may reside outside the processor, and exist separately.

In a ninth aspect, there is provided a processor comprising: input circuit, output circuit and processing circuit. The processing circuitry is to receive signals through the input circuitry and to transmit signals through the output circuitry such that the processor performs any one of the above aspects or implements the provided methods.

In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the output signal may be output by, for example and without limitation, a transmitter and transmitted by a transmitter, and the input circuit and the output circuit may be the same circuit, which functions as the input circuit and the output circuit, respectively, at different times. The specific implementation of the processor and various circuits is not limited in this application.

In a tenth aspect, there is provided a communication apparatus comprising: logic circuitry and an input-output interface for communicating with a module external to the communication device; the logic circuitry is to run a computer program or instructions to perform the methods provided by any of the designs of any of the above aspects. The communication means may be the first terminal device or the second terminal device or the policy control function network element in any of the above aspects, or a device comprising the first terminal device or the second terminal device or the policy control function network element, or a device, such as a chip, comprised in the first terminal device or the second terminal device or the policy control function network element.

Alternatively, the input/output interface may be a code/data read/write interface circuit, or a communication interface, for receiving a computer program or instructions (stored in a memory, possibly read directly from the memory, or possibly via other means) and transmitting to the input/output interface for causing the input/output interface to run the computer program or instructions to perform the method of any of the above aspects.

Alternatively, the communication device may be a chip.

In an eleventh aspect, there is provided a computer program product comprising: a computer program (which may also be referred to as code, or instructions) which, when executed, causes a computer to perform any one of the above aspects or any one of the aspects to carry out the provided method.

In a twelfth aspect, there is provided a computer readable medium storing a computer program (which may also be referred to as code, or instructions) which, when run on a computer, causes the computer to perform any one of the above aspects or to implement the provided method.

In a thirteenth aspect, there is provided a chip system comprising a processor and an interface for supporting a communication device to implement any one of the above aspects or any one of the aspects to implement the provided functionality. In one possible design, the chip system further includes a memory for holding the necessary information and data of the aforementioned communication device. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

In a fourteenth aspect, a chip arrangement is provided, the chip arrangement comprising an input interface and/or an output interface. The input interface may implement any of the above aspects or any of the aspects implementing the provided receiving functionality, and the output interface may implement any of the above aspects or any of the aspects implementing the provided transmitting functionality.

A fifteenth aspect provides a functional entity for implementing the method provided by any one of the above aspects or any one of the aspects.

A sixteenth aspect provides a communication system comprising the first terminal device of the first aspect, the second terminal device of the second aspect and the policy control function network element of the third aspect.

The technical effects of any one of the second to sixteenth aspects may be referred to as the technical effects of the first aspect, and are not described herein.

Drawings

FIG. 1 is a schematic diagram of a communication system;

FIG. 2 is a schematic diagram of a communication system;

FIG. 3 is a schematic diagram of a PIN network architecture;

fig. 4 is a schematic diagram of a service flow routing process provided in an embodiment of the present application;

fig. 5 is a schematic diagram of a service flow routing process provided in an embodiment of the present application;

Fig. 6 is a schematic diagram of a service flow routing process provided in an embodiment of the present application;

fig. 7 is a schematic diagram of a service flow routing process provided in an embodiment of the present application;

fig. 8 is a schematic diagram of a service flow routing process provided in an embodiment of the present application;

fig. 9 is a schematic diagram of a service flow routing process provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

The present application will be described in further detail with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to a mobile communication system. For example, the mobile communication system may be a fourth generation (4th Generation,4G) communication system (e.g., a long term evolution (long term evolution, LTE) system), a fifth generation mobile communication (5 th-generation, 5G) communication system (e.g., a New Radio (NR) system), and a future mobile communication system such as 6G, etc. The mobile communication system supports a plurality of access technologies, for example, a 5GC support a plurality of access technologies, or a 5GC and evolved packet core network (evolved packet core, EPC) converged network supports a plurality of access technologies. The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided in the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

Fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present application, including: user equipment, (radio) access network equipment, user plane network elements, data networks, access management network elements, session management network elements, application network elements, unified data management network elements, policy control network elements, network deployment network elements and the like. The individual network elements involved in the network architecture are described separately below.

1. User Equipment (UE): a user equipment may also be called an access terminal, terminal device, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, user agent, user device, or the like. The terminal may be a device with wireless transceiving functionality, such as a mobile phone (mobile phone), a tablet (pad), a computer with wireless transceiving functionality, a Virtual Reality (VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in an industrial control (industrial control), a wireless terminal in a self-driving (self-driving), a wireless terminal in a remote medical (remote medium), a wireless terminal in a smart grid (smart grid), a wireless terminal in a transportation security (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication functionality, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network or a future evolution network, etc.

The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wearing and developing wearable devices by applying a wearable technology, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

2. (radio) access network device (radio access network, (R) AN): the access network device may also be referred to as AN access device or AN access network element, where the (R) AN may be capable of managing radio resources, providing access services for the user device, and completing forwarding of user device data between the user device and the core network, and may also be understood as a base station in the network.

By way of example, the access network device in the embodiments of the present application may be any communication device having a wireless transceiver function for communicating with a user device. The access network device includes, but is not limited to: an evolved node B (eNB), a radio network controller (radio network controller, RNC), a Node B (NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (HeNB, or home node B, HNB), an indoor baseband processing unit (building base band unit, BBU), a transceiving point (transmit receive point, TRP), a transmission point (transmission point, TP), etc., and may also be 5G, such as a next generation base station or a next generation node B (generation node B, gNB) in an NR system, or a transmission point (TRP, or TP), one or a group of antenna panels (including a plurality of antenna panels) of a base station in a 5G system, or may also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and DUs. The gNB may also include an active antenna unit (active antenna unit, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB. For example, the CU is responsible for handling non-real time protocols and services, implementing the functions of the radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer. The DUs are responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (radio link control, RLC), medium access control (media access control, MAC) and Physical (PHY) layers. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. The information of the RRC layer is generated by the CU and finally becomes PHY layer information through PHY layer encapsulation of DU, or is converted from the information of the PHY layer. Thus, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be sent by DUs, or by dus+aaus. It is understood that the access network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into access network devices in an access network (radio access network, RAN), or may be divided into access network devices in a Core Network (CN), which is not limited in this application.

3. User plane network element (or user plane functional network element): as an interface with the data network, the functions of user plane data forwarding, charging statistics based on session/stream level, bandwidth limitation and the like are completed. I.e. packet routing and forwarding, quality of service (quality of service, qoS) handling of user plane data, etc.

In a 5G communication system, the user plane network element may be a user plane function (user plane function, UPF) network element.

4. Data network: for providing a network for transmitting data. Providing, for example, operator services, internet access, or third party services, including servers, server-side implementation of video source coding, rendering, etc. In a 5G communication system, the data network may be a Data Network (DN).

5. Access management network element (or access management function network element): the method is mainly used for mobility management, access management and the like. In a 5G communication system, the access management network element may be an access and mobility management function (access and mobility management function, AMF), mainly performing mobility management, access authentication/authorization, etc. In addition, it is responsible for passing user policies between the terminal and the policy control function (policy control function, PCF) network elements.

6. Session management network element (or session management function network element): the method is mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of user equipment, terminal node of selecting manageable user plane functions, strategy control and charging function interfaces, downlink data notification and the like.

In the 5G communication system, the session management network element may be a session management function (session management function, SMF) network element, which performs terminal IP address allocation, UPF selection, charging and QoS policy control, and the like.

7. Application network element: in the 5G communication system, the application network element may be an application function (application function, AF) network element, which represents an application function of a third party or an operator, and is an interface for the 5G network to obtain external application data, and is mainly used for transferring a requirement of an application side on a network side.

8. Unified data management network element: and the management of user identification, subscription data and authentication data is responsible for the registration management of the service network element of the user. In a 5G communication system, the unified data management network element may be a unified data management (unified data management, UDM).

9. Policy control network element: the system comprises a user subscription data management function, a policy control function, a charging policy control function, a QoS control function and the like, and is used for guiding a unified policy framework of network behaviors, providing policy rule information for control plane function network elements (such as AMF, SMF network elements and the like), and the like.

In a 5G communication system, the policy control network element may be a PCF.

10. Network open network element (or network open function): in the 5G communication system, the network element may be a network element with a network opening function (network element function, NEF), which is mainly used for exposing services and capabilities of the 3GPP network function to the AF, and may also enable the AF to provide information to the 3GPP network function.

Optionally, more or fewer network elements may be included in the network architecture than shown above, for example, the network architecture may further include an authentication server, which is responsible for authenticating the user equipment and determining the validity of the user equipment, and in the 5G communication system, the authentication server may be an authentication server function (authentication server function, AUSF) network element.

The above network architecture supports 3GPP defined radio access technologies (radio access technology, RAT) to access a Core Network (CN), 3GPP defined RATs including long term evolution (long term evolution, LTE), 5G RAN, etc. The above network architecture also supports non-3GPP (non-3 GPP, N3G, or N3 GPP) access technologies to access the core network through a non-3GPP switching function (non-3GPP interworking function,N3IWF) or a next generation access gateway (next generation packet data gateway, ngPDG).

When 5GC supports non-3GPP access, then the 5G network architecture is as shown in FIG. 2, including a local public land mobile network (home public land mobile network, HPLMN) and a non-3GPP network. The UE may access the 5GC in the HPLMN through a 3GPP access manner, and may access the 5GC through an untrusted non-3GPP access (untrusted non-3GPP access) manner. Wherein the N3IWF is a non-3GPP access gateway. The non-3GPP access network can include, for example, an untrusted wireless local area network (wireless local area network, WLAN) access network, and the N3IWF device can include, for example, a router or the like.

It should be noted that the 5G core network also supports trusted non-3GPP access and/or wired network access. The trusted non-3GPP access network can include, for example, a trusted WLAN network, and the wired network can include, for example, a fixed home network access (hereinafter referred to as a fixed network), and the like. When the 5G core network supports trusted non-3GPP access, its 5G network architecture is similar to that of FIG. 2. The non-trusted non-3GPP access in FIG. 2 can be replaced with a trusted non-3GPP access, and the N3IWF can be replaced with a trusted non-3GPP access gateway (trusted non-3GPP gateway function,TNGF). When the 5G core network supports network access, its 5G network architecture is similar to that of fig. 2. The non-trusted non-3GPP access in FIG. 2 can be replaced with a wired network access and the N3IWF replaced with a wired network access gateway (wireline access gateway function, W-AGF). The access network devices between the UE and the access gateway may include WLAN Access Points (APs), fixed access network devices (fixed access network, FAN), switches, routers, etc.

It can be seen that non-3GPP access technologies include access technologies such as trusted WLAN access, untrusted WLAN access, or wired network access. Whether trusted non-3GPP access or untrusted non-3GPP access, the core network may employ the 3GPP access core network architecture and service interface shown in FIG. 1, or may employ the network architecture and point-to-point interface protocol shown in FIG. 2.

It will be appreciated that the network elements or functions described above may be either network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). The network elements or functions may be divided into one or more services, and further, services that exist independently of the network functions may also occur. In this application, the instance of the above-mentioned functional network element, or the instance of the service included in the above-mentioned functional network element, or the instance of the service existing independently of the network function may be referred to as a service instance. Alternatively, the network element or the function may be implemented by one device, or may be implemented by a plurality of devices together, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.

With the continuous enhancement of 5GC network functions, terminal devices are becoming more and more abundant. The management and control of the PIN network by the operator network is the goal of the next stage of network enhancement. A PIN network architecture is shown in fig. 3, including PEMC and PEGC. PIN elements, also referred to as PIN members, may also be included in the PIN network, which may be other UEs than PEMCs and PEGCs, such as the UE and/or N3GPP device (device) shown in fig. 3.

PEMC and PEGC are user equipments with 5GC access capability, and can access 5GC through 3GPP access technology or non-3GPP access technology. A connection is established between the PEGC and the PEMC based on the PC5 interface. PEMC is a management node in a PIN network, has 5GC access capability, and can access 5GC independently. PEGC is a gateway node in a PIN network, which also has 5GC access capability, so 5GC can also be accessed and registered independently. Typically all PIN members in the PIN network establish a connection with the PEGC, which can be accessed based on non-3GPP access technologies such as wireless fidelity (wireless fidelity, wi-Fi) or bluetooth.

The PIN Element node may be an end device with 5GC access capability, or may be an end device without 5GC access capability, hereinafter referred to as an end device. The end device may be affiliated with a third party service provider, such as a smart wearable device, a smart home device, etc.

The embodiment of the application provides a service flow routing method, which can realize the communication flow under a PIN network architecture and can realize the local routing of the service flow in the PIN network under the control of a network side.

Fig. 4 is a schematic diagram of a service flow routing method provided in an embodiment of the present application. The method comprises the following steps:

s401: the second terminal device sends a second registration message, and correspondingly, the second access management function network element receives the second registration message. The second registration message carries second capability information, and the second capability information indicates that the second terminal equipment has PIN network gateway capability. The second terminal device is, for example, PEGC. The second management function network element is a network element providing access management functions for the second terminal device, e.g. the second management function network element is an AMF serving PEGC.

S402: the second terminal equipment acquires the first PIN network local routing rule.

S403: and the second terminal equipment executes local routing on the acquired service flow according to the local routing rule of the first PIN network.

Based on the above scheme, the second terminal device with the PIN network gateway capability can execute local routing on the service flow according to the acquired local routing rule of the first PIN network, transmit the service flow under the PIN network architecture, and realize the local routing of the service flow in the PIN network.

In S402 described above, the second terminal device may acquire the first PIN network local routing rule by two examples:

example 1: the second terminal device obtains the first PIN network local routing rule from the first terminal device.

Example 2: the second terminal device obtains the first PIN network local routing rule from the policy control function network element.

In this example 1, the first PIN network local routing rule is associated with the first capability information. The first capability information indicates that the first terminal device has PIN network management capabilities. The first terminal device is, for example, a PEMC.

Alternatively, the first terminal device may obtain the first PIN network local routing rule from the policy control function network element. One possible implementation is shown in fig. 5, comprising the steps of:

s501: the first terminal device sends a first registration message, and correspondingly, the first access management function network element receives the first registration message. The first registration message carries first capability information, and the first capability information indicates that the first terminal equipment has PIN network management capability. The first access management function network element is a network element providing access management functions for the first terminal device, e.g. the first access management function network element is an AMF serving the PEMC. The first access management function network element and the second access management function network element may be deployed in the same physical network element or may be deployed in different physical network elements.

S502: the first terminal device obtains a first PIN network local routing rule from the policy control function network element.

Alternatively, the first access management function network element may send a policy acquisition message to the policy control function network element, where the policy acquisition message carries indication information, and the indication information indicates that the first terminal device has PIN network management capability. Correspondingly, the policy control function network element determines to allow local routing according to the indication information and sends a first PIN network local routing rule. For example, the policy control function network element determines that the first terminal device needs to perform data transmission in the PIN network according to that the first terminal device has a PIN network management capability, and there is typically a service that can perform local routing in the PIN network, for example, a service that allows local routing is determined based on a service feature (for example, internet (internet) service, packet transmission service, etc.), so that the policy control function network element may determine that local routing is allowed. The policy control function network element stores policies corresponding to different services whether to allow local routing, so that the policy control function network element can carry relevant information of the policies in the local routing rules of the first PIN network.

S503: the first terminal device sends a first PIN network local routing rule to the second terminal device.

In this example 2, the first PIN network local routing rule is associated with the second capability information.

Optionally, the second access management function network element may send a policy acquisition message to the policy control function network element, where the policy acquisition message carries indication information, and the indication information indicates that the second terminal device has a PIN network gateway capability. Correspondingly, the policy control function network element determines to allow local routing according to the indication information and sends a first PIN network local routing rule. For example, the policy control function network element determines that the second terminal device needs to perform data transmission in the PIN network according to the second terminal device having the PIN network gateway capability, and there is typically a service that can perform local routing in the PIN network, for example, a service that allows local routing is determined based on a service feature (for example, internet service, data packet transmission service, etc.), so that the policy control function network element can determine that local routing is allowed. The policy control function network element stores policies corresponding to different services whether to allow local routing, so that the policy control function network element can carry relevant information of the policies in the local routing rules of the first PIN network.

Local routing refers to traffic being transmitted through a terminal within the PIN network (e.g., through PEGC or directly between two terminal devices) and not through a node in the carrier network (e.g., RAN or UPF network element in a 5G network). In general, for each service, the policy control network element may decide whether the service allows local routing. For data of services in the PIN network, such as, but not limited to, data sharing (e.g., screen-casting of a mobile phone screen to a television) or home appliance control (e.g., air-conditioning temperature adjustment by a mobile phone) in the home network, the services may also be transmitted without passing through nodes in the carrier network, and then the policy control function network element may decide such services to be allowed to be routed locally. For data of services within the internet, such as but not limited to internet protocol (internet protocol, IP) multimedia subsystem (IP multimedia subsystem, IMS) voice, or video call services, etc., such services guarantee the quality of service of the service flows or perform charging through nodes in the operator network so that both parties can implement voice communication or video call, the policy control function network element may decide such services not to allow local routing.

The first PIN network local routing rules in the above embodiments may contain different information according to the actual implementation requirements. The following is a description of possible implementations 1 and 2.

Possible implementation 1: the first PIN network local routing rules described above may include a data network name (data network name, DNN) and/or slice information (slice info). The data network name indicates that the traffic flow in the PDU session corresponding to the data network name is allowed to be routed locally. The slice information indicates that the traffic flow in the PDU session to which the slice information corresponds is allowed to be routed locally.

Optionally, the first PIN network local routing rule may further include local routing indication information besides DNN and slice info, where the local routing indication information indicates that a local routing is allowed for a service flow in a PDU session corresponding to a data network name or slice information.

Specifically, S403 includes sending, by the second terminal device, the service flow to the destination terminal device of the service flow in the PIN network where the second terminal device is located if the acquired service flow matches the local routing rule of the first PIN network. The service flow acquired by the second terminal device may be a service flow sent by other terminal devices (such as terminal devices) received by the second terminal device, or may be a service flow generated by the second terminal device.

Wherein the traffic flow matches the first PIN network local routing rule, including one or more of the following:

case 1.1: the flow description information in the first PIN network local routing rule contains information carried by the data packet in the service flow.

The flow description information includes at least one of five tuples, and the information of the five tuples includes at least one of a source IP address, a destination IP address, a source port number, a destination port number, or a protocol type. For the uplink traffic flow sent by the terminal device, the source IP address is the IP address of the terminal device sending the uplink traffic flow, and the source port number is the port number of the terminal device sending the uplink traffic flow. For the downlink traffic flow received by the terminal device, the destination IP address is the IP address of the terminal device receiving the downlink traffic flow, and the destination port number is the port number of the terminal device receiving the downlink traffic flow.

By way of example, the flow description information may be a five-tuple, a three-tuple, a four-tuple, or the like. For example, the quintuple in the first PIN network local routing rule includes a quintuple carried by a data packet in the service flow, that is, the quintuple carried by the data packet in the service flow is a subset of the quintuple in the first PIN network local routing rule, which indicates that the service flow belongs to a service flow that allows local routing.

Alternatively, the flow description information includes at least one of a source MAC address, or a destination MAC address. For the uplink traffic flow sent by the terminal device, the source MAC address is the MAC address of the terminal device sending the uplink traffic flow. For the downlink traffic flow received by the terminal device, the destination MAC address is the MAC address of the terminal device that receives the downlink traffic flow.

Case 1.2: the data network name in the first PIN network local routing rule includes a data network name of a PDU session corresponding to the traffic flow.

The data network name in the first PIN network local routing rule includes a data network name of a PDU session corresponding to the uplink traffic flow and/or a data network name of a PDU session corresponding to the downlink traffic flow. The PDU session corresponding to the service flow refers to the PDU session to which the service flow belongs. The data network name is one of the attributes of the PDU session and is used to determine whether the traffic flow corresponding to the PDU session allows local routing.

Case 1.3: the slice information in the first PIN network local routing rule includes slice information of a PDU session corresponding to the traffic flow.

The slice information in the first PIN network local routing rule includes slice information of a PDU session corresponding to an uplink traffic flow and/or slice information of a PDU session corresponding to a downlink traffic flow. The slice information is one of the attributes of the PDU session, and is used for determining whether the service flow corresponding to the PDU session allows local routing. For example, the slice information may include network slice selection assistance information (network slice selection assistance information, NSSAI), or a single-NSSAI (S-NSSAI).

Case 1.4: the destination terminal equipment corresponding to the destination address information carried in the service flow and the second terminal equipment belong to the same PIN network.

If the destination terminal device and the second terminal device belong to the same PIN network, it means that the traffic flow can be received by the destination terminal device without going through a node in the operator network, so that the traffic flow can allow local routing.

In an example illustrating the above several cases, in S403, the second terminal device determines a PDU session corresponding to the acquired service flow, for example, determining a PDU session corresponding to the service flow according to the source IP address in the received service flow.

a) If the service flow of the PDU session allows local routing, that is, DNN or slice information corresponding to the PDU session belongs to DNN or slice information contained in a PIN network local routing rule, the second terminal device searches for the destination terminal device based on the destination IP address in the received service flow.

i) When the destination terminal equipment corresponding to the destination IP address and the second terminal equipment belong to the same PIN network, if the PDU session corresponding to the destination IP address also allows local routing (the PDU session corresponding to the source IP address and the PDU session corresponding to the destination IP address belong to different PDU sessions, namely, both PDU sessions allow local routing; if the PDU session corresponding to the source IP address and the PDU session corresponding to the destination IP address belong to the same PDU session, the PDU session is known to allow local routing, the second terminal device directly sends the service flow packet to the destination terminal device, and the second terminal device performs local routing without going through a node in the operator network, such as 5 GC.

If the PDU session corresponding to the target IP address does not allow the local routing, the second terminal device sends the service flow data to the 5GC through the PDU session, namely the second terminal device does not execute the non-local routing.

ii) if not, the destination device corresponding to the destination IP address and the second terminal device do not belong to the same PIN network, the second terminal device sends the service flow data packet to the 5GC through PDU session, i.e. the second terminal device does not execute local routing.

b) If the service flow of the PDU session does not allow local routing, i.e. DNN or slice information of the PDU session does not belong to DNN(s) or slice information contained in the local routing rule of the PIN network, the second terminal device sends the service flow data packet to the 5GC through the PDU session, i.e. the second terminal device does not execute local routing.

In the above example, the second terminal device determines whether the local routing can be performed according to the obtained source IP address of the service flow, and then further makes a determination based on the determination result. In practical implementation, the method is not limited to the sequence, and can be flexibly arranged according to practical needs. For example, when the destination device corresponding to the service flow and the second terminal device belong to the same PIN network, the second terminal device respectively determines whether the PDU session corresponding to the source IP address and the PDU session corresponding to the destination IP address support the local routing, and when both the PDU session corresponding to the source IP address and the PDU session corresponding to the destination IP address support the local routing, the local routing is executed.

Possible implementation 2: the first PIN network local routing rule may include a device identifier list, where a service flow corresponding to a device identifier in the device identifier list allows local routing. The device identification may include, but is not limited to, a MAC address, an IP address, a device name, and the like. The device identification may be used to identify PIN members and/or PEGCs. Optionally, the first PIN network local routing rule may further include local routing indication information besides the device identifier list, where the local routing indication information indicates that the service flow corresponding to the device identifier in the device identifier list allows local routing.

In one example, in S403, if the acquired service flow matches with the device identifier list in the local routing rule of the first PIN network, the second terminal device performs local routing on the acquired service flow, that is, the second terminal device sends the service flow to the destination terminal device of the service flow in the PIN network where the second terminal device is located. The service flow is matched with the equipment identification list in the first PIN network local routing rule, which means that the equipment identification list in the first PIN network local routing rule contains the equipment identification corresponding to the service flow.

In another example, in S403, the second terminal device performs local routing on the acquired service flow according to the first PIN network local routing rule, in combination with a local policy and/or user preference. That is, the scope of the allowed local routing is further defined according to the local policy and/or the user preference of the second terminal device, so that the user control feeling can be improved, and the user experience can be optimized.

For example, the second terminal device determines the device identifier and address information corresponding to the device identifier in the device identifier list according to the local policy and/or user preference, sends the corresponding relationship between the address information and the device identifier to the first terminal device, and the first terminal device obtains a second PIN network local routing rule according to the corresponding relationship, then sends the second PIN network local routing rule to the second terminal device, and if the obtained service flow is matched with the second PIN network local routing rule, the second terminal device sends the service flow to the destination terminal device of the service flow in the PIN network where the second terminal device is located.

Here, considering the case where the address information is an IP address, since the IP address is generally randomly allocated, a change may occur during communication (i.e., the same device may be allocated to different IP addresses during two communications). If the second terminal equipment only reports the IP address, the second PIN network local routing rule can only be determined according to the reported IP address, if the IP address of the terminal changes, the equipment positioned by the second terminal equipment according to the IP address in the second PIN network local routing rule is different from the equipment actually corresponding to the service flow, and the local routing error of the service flow is caused.

The device identifier is subscription information of the device, and is fixed in the communication process. If the second terminal equipment reports the corresponding relation, the local routing rule of the second PIN network is determined according to the corresponding relation. If the second PIN network local routing rule includes a device identifier, the second terminal device may match the device identifier in the second PIN network local routing rule according to the device identifier corresponding to the service flow, so as to determine whether to allow local routing. If the second PIN network local routing rule includes an IP address, the second terminal device may match the IP address in the second PIN network local routing rule according to the IP address in the service flow, so as to determine whether to allow local routing (in the case that the IP address of the terminal changes, since the first terminal device has PIN network management capability, the first terminal device may obtain that the IP address of the terminal changes, if the second PIN network local routing rule is generated by the policy control function network element, the first terminal device may report the IP address of the terminal, and the policy control function network element updates the IP address in the second PIN network local routing rule, and then issues the updated second PIN network local routing rule to the second terminal device). If the second PIN network local routing rule comprises the equipment identifier and the IP address, the second terminal equipment is matched with the IP address in the second PIN network local routing rule according to the IP address in the service flow, so that whether the local routing is allowed or not is determined, and the decision efficiency of the second terminal equipment can be improved on the basis of ensuring that the service flow local routing is accurately performed because the packet head of the service flow data packet carries the IP address. That is, the second terminal device can ensure that the local routing of the service flow is performed more accurately by reporting the corresponding relationship between the address information and the device identifier.

For example, the second terminal device may determine the device identity in the device identity list, one or more PIN members in the PIN member list, and/or one or more PIN gateway devices in the PIN gateway device list. The terminal equipment corresponding to the one or more PIN gateway equipment determined by the second terminal equipment allows local routing, and the terminal equipment corresponding to the PIN gateway equipment refers to the terminal equipment capable of communicating with the PIN gateway equipment, namely, the service flow sent to the terminal equipment is forwarded through the PIN gateway equipment. Optionally, the one or more PIN gateway devices determined by the second terminal device may include the second terminal device itself, or may include other PIN gateway devices besides the second terminal device.

In one possible implementation, the first terminal device may obtain, according to the correspondence, a second PIN network local routing rule: and sending the corresponding relation to the strategy control function network element, generating a second PIN network local routing rule by the strategy control function network element according to the corresponding relation, and then sending the second PIN network local routing rule to the first terminal equipment. Specifically, if the policy control function network element determines that the device identifier in the corresponding relationship allows local routing, the second PIN network local routing rule is generated to include address information corresponding to the device identifier allowing local routing.

In another possible implementation, the first terminal device may obtain, according to the correspondence, a second PIN network local routing rule: and the first terminal equipment generates a second PIN network local routing rule according to the corresponding relation. Specifically, if the first terminal device determines that the device identifier in the corresponding relationship allows local routing, the address information in the corresponding relationship is included in the local routing rule of the generated second PIN network.

The second PIN network local routing rule obtained in the above manner includes address information. The address information indicates that the traffic flow corresponding to the address information allows local routing. Optionally, the second PIN network local routing rule may also include a device identifier. Wherein, the device identifier indicates that the service flow corresponding to the device identifier allows local routing. In S403, if the acquired service flow matches the local routing rule of the second PIN network, the second terminal device performs local routing on the acquired service flow.

Wherein the traffic flow matches the second PIN network local routing rule, including one or more of the following:

case 2.1: the flow description information in the second PIN network local routing rule contains information carried by the data packet in the service flow.

This case 2.1 is similar to the case 1.1 described above and will not be described here again.

Case 2.2: the PIN members in the second PIN network local routing rule comprise PIN members corresponding to the traffic flow.

The PIN members corresponding to the traffic flows in the second PIN network local routing rule include PIN members corresponding to the uplink traffic flows and/or PIN members corresponding to the downlink traffic flows. The PIN member corresponding to the uplink service flow is the member sending the uplink service flow, and the PIN member corresponding to the downlink service flow is the PIN member receiving the downlink service flow. Wherein the PIN member is uniquely identified by the device identification.

Case 2.3: the PIN members in the second PIN network local routing rule comprise destination terminal equipment corresponding to the service flow.

The destination terminal device corresponding to the service flow in the second PIN network local routing rule refers to a terminal device that receives the service flow, for example, the destination terminal device may be determined by a destination IP address in the service flow or by a device identifier corresponding to the destination IP address.

Case 2.4: the address information in the second PIN network local routing rule contains destination address information in the traffic flow.

This indicates that the destination address information in the traffic flow belongs to the address information in the local routing rules of the second PIN network, indicating that the traffic flow belongs to a traffic flow that allows local routing.

The "PDU session" referred to in the embodiments of the present application may be a PDU session supporting one or more access technologies. The access technology may be, but is not limited to being, one or more of the following access types: 3GPP access, non-3GPP access, LTE access, 5GRAN access, trusted non-3GPP access, untrusted non-3GPP access, wireless local area network (wireless local area network, WLAN) access, trusted WLAN access, untrusted WLAN access, wired network access (fixed network access), trusted Wi-Fi access, or untrusted Wi-Fi access, etc. One PDU session includes one or more QoS flows.

The "traffic flow" referred to in the embodiments of the present application includes a traffic data flow (service data flow, SDF), an IP data flow, an ethernet data flow (or ethernet flow), or at least one QoS flow. One QoS flow includes one or more SDFs. One SDF includes one or more IP flows or one or more ethernet flows. The IP packets or ethernet packets in one SDF correspond to the same traffic flow description information. An IP flow includes one or more IP packets, and the IP packets in an IP flow have the same IP quintuple information. An ethernet stream comprises one or more ethernet packets, the ethernet packets in an ethernet stream having identical ethernet stream description information. The ethernet flow description information includes at least one of a source MAC address or a destination MAC address. In this embodiment of the present application, the service data packet includes an IP data packet or an ethernet data packet, etc.

Based on the embodiments shown in fig. 4 to 5, the following describes a service flow routing method provided in the embodiments of the present application with specific embodiments in fig. 6 to 9. Wherein steps in fig. 6 to 9 and fig. 4 to 5 may be referred to each other, and term concepts may be referred to each other.

Fig. 6 is a schematic diagram of a traffic routing process, including the steps of:

s601: the PEMC registers with the network.

Specifically, UE1 registers with the network and creates a PIN network as PEMC.

S602: the AMF serving the PEMC obtains a first PIN network local routing rule from a PCF or a PIN Network Function (NF), where the first PIN network local routing rule includes DNN information and/or slice information, and optionally local routing indication information.

If the first PIN network local routing rule comprises local routing indication information, the local routing indication information indicates that the traffic flow in the PDU session corresponding to DNN information and/or slice information is allowed to carry out local routing. If the first PIN network local routing rule does not include local routing indication information, DNN information and/or slice information itself indicates that the traffic flow in the PDU session corresponding to the DNN information and/or slice information is allowed to perform local routing. The DNN information may be information of one DNN or a plurality of DNNs(s).

Wherein, the AMF of the service PEMC refers to an AMF providing access management service for the PEMC.

S603: the AMF serving the PEMC sends a first PIN network local routing rule to the PEMC. Accordingly, the PEMC receives the first PIN network local routing rule. The relevant description of the local routing rule of the first PIN network may be referred to the above embodiment, and will not be repeated here.

S604: PEGC is registered with the network.

The sequence of S604 and S601 to S603 is not limited.

S605: the PEGC establishes a connection with the PEMC, and the PEMC sends the first PIN network local routing rule to the PEGC.

S606: the PEGC establishes a PDU session.

The SMF of the service PEGC provides session management service for the PEGC.

The order of S605 and S606 is not limited.

S607: and the PEGC executes local routing on the acquired service flow according to the local routing rule of the first PIN network.

In this embodiment, the network side sends the local routing rule of the PIN network to the PEMC, and the PEMC sends the local routing rule of the PIN network to the PEGC, and then the PEGC realizes the local routing of the traffic flow in the PIN network.

In a practical implementation, the PEMC may also establish a PDU session, and the SMF serving the PEGC provides a session management service for the PEMC, and the step of establishing the PDU session by the PEMC is not shown in fig. 6.

Fig. 7 is a schematic diagram of a service flow routing process, including the steps of:

the process of S701 is described in S601 above.

The process of S702 is described in S604 above.

S703: the AMF serving the PEGC obtains a first PIN network local routing rule from the PCF or PIN NF, the first PIN network local routing rule including DNN information and/or slice information, and optionally local routing indication information.

The AMF of the service PEGC refers to an AMF that provides access management service for the PEGC.

S704: the AMF serving the PEGC sends the first PIN network local routing rules to the PEGC. Correspondingly, the PEGC receives the first PIN network local routing rule.

The processes of S705 to S706 are described in S606 to S607.

In this embodiment, the network side sends a PIN network local routing rule to the PEGC, and the PEGC implements local routing of the traffic flow in the PIN network.

Fig. 8 is a schematic diagram of a service flow routing process, including the following steps:

the process of S801 is described in S601 above.

S802: the AMF of the service PEMC acquires a first PIN network local routing rule from the PCF or the PIN NF, wherein the first PIN network local routing rule comprises a PIN member identification list and/or a PEGC identification list, and optional local routing indication information.

Wherein the PIN member identification is used to uniquely identify one UE in the PIN network. PEGC member identification is used to uniquely identify one PEGC. The AMF of the service PEMC refers to an AMF that provides access management services for the PEMC.

S803: the PEGC registers into the network, establishing a PDU session.

S804: the AMF serving the PEMC sends a first PIN network local routing rule to the PEMC. Correspondingly, after receiving the first PIN network local routing rule, the PEMC sends the first PIN network local routing rule to the PEGC.

After PEGC receives the first PIN network local routing rule, there may be two different implementations, mode one: reference S805. Mode two: reference S806 to 809.

S805: and the PEGC executes local routing on the acquired service flow according to the local routing rule of the first PIN network.

When a destination IP address or a destination MAC address carried by a data packet in a service flow belongs to a PIN member list contained in a first PIN network local routing rule, or when a destination terminal device corresponding to the destination IP address or the destination MAC address belongs to a PIN member list contained in the first PIN network local routing rule, or when a PEGC corresponding to the destination IP address or the destination MAC address belongs to a PEGC list contained in the first PIN network local routing rule, the PEGC executes local routing on the service flow. The PEGC where the destination terminal device is located refers to forwarding the service flow sent to the destination terminal device through the PEGC.

S806: and the PEGC selects the equipment identifier from the PIN member identifier list and/or the PEGC identifier list, and sends the equipment identifier and the IP address corresponding to the equipment identifier to the PEMC.

The device identifications include PIN member identifications and/or PEGC identifications, in other words, the PEGC may select a PIN member identification from a PIN member identification list and/or a PEGC identification from a PEGC identification list.

S807: and the PEMC stores the corresponding relation between the equipment identifier and the IP address, and generates a second PIN network local routing rule based on the corresponding relation. The relevant description of the local routing rule of the second PIN network may be referred to the above embodiment, and will not be repeated here.

S808: the PEMC sends the second PIN network local routing rule to the PEGC.

S809: and the PEGC executes local routing on the acquired service flow according to the second PIN network local routing rule.

Illustratively, the PEGC performs local routing of the traffic flow when the destination IP address is contained in the second PIN network local routing rule. In this embodiment, the network side sends a first PIN network local routing rule to the PEMC, which generates a second PIN network local routing rule, and the PEGC implements local routing of traffic flows within the PIN network.

In the above embodiment, taking the first PIN network local routing rule, the first PIN network local routing rule includes a PIN member identifier list and/or a PEGC identifier list as an example. In an alternative, the first PIN network local routing rule may also not include a PIN membership identification list and PEGC identification list. In this case, the PEGC may determine PIN member identifications and/or PEGC identifications according to local policies and/or user preferences, and then perform local routing on the acquired traffic. The PIN member identification and/or PEGC identification may be used to decide which PIN members and/or PEGCs allow local routing.

In the above embodiment, the first PIN network local routing rule is taken as an example and described by the AMF serving the PEMC. In an alternative solution, the AMF serving the PEGC may obtain the first PIN network local routing rule from the PCF or the PIN NF, and the AMF serving the PEGC sends the first PIN network local routing rule to the PEGC, which may be referred to as S703 to S704 in fig. 7.

Fig. 9 is a schematic diagram of a traffic routing process, including the steps of:

the processes of S901 to S904 are described in S801 to S804.

After PEGC receives the first PIN network local routing rule, there may be two different implementations, mode one: reference S905. Mode two: reference S906 to S910.

The process of S905 is referred to above in S805.

The process of S906 is described in S806 above.

S907: the PEMC sends the correspondence between the device identification and the IP address to the PCF or PIN NF.

S908: the PCF or PIN NF sends a second PIN network local routing rule to the PEMC.

The PCF or PIN network element generates a second PIN network local routing rule based on the correspondence.

The processes of S909 to S910 are described in S808 to S809 described above.

In this embodiment, the network side sends a first PIN network local routing rule to the PEMC, the PEMC generates a second PIN network local routing rule, the PEMC sends the second PIN network local routing rule to the PEGC, and the PEGC implements local routing of the traffic flow in the PIN network.

In the embodiments shown in fig. 6 to 9, the AMF/SMF serving the PEMC and the AMF/SMF serving the PEGC are deployed in different physical network elements. In practical implementation, the AMF/SMF of the service PEMC and the AMF/SMF of the service PEGC may be deployed on the same physical network element, or the AMF and SMF of the service PEMC may be deployed on different physical network elements, or the AMF and SMF of the service PEGC may be deployed on different physical network elements.

It should be noted that the above embodiments may be used alone or in combination.

The terms "system" and "network" in embodiments of the present application may be used interchangeably. In the description of the embodiment of the present application, "and/or" describing the association relationship of the association object indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. Reference to at least one in this application refers to one or more; plural means two or more. In addition, it should be understood that in the description of this application, the words "first," "second," "third," and the like are used merely for distinguishing between the descriptions and not for indicating or implying any particular importance or order. Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise. The method and the device are based on the same or similar technical conception, and because the principle of solving the problems by the method and the device is similar, the implementation of the device and the method can be mutually referred to, and the repetition is omitted.

Based on the same technical concept as the above-mentioned traffic flow routing method, the embodiment of the present application further provides a communication device, as shown in fig. 10, where the communication device 1000 includes a processing unit 1001 and a transceiver unit 1002. The functions performed by optional transceiver unit 1002 may be performed by a communication interface, and the transceiver unit may comprise a receiving unit and/or a transmitting unit. The apparatus 1000 may be applied to or located in a first terminal device or a second terminal device or a policy control function network element. The communication apparatus 1000 may be configured to implement the method described in the above-described method embodiments, for example, the communication apparatus 1000 may be configured to perform each step performed by the first terminal device or the second terminal device or the policy control function network element in the methods of fig. 4 to 9.

In one possible embodiment, the apparatus 1000 is applied to a first terminal device.

For example, the processing unit 1001 is configured to generate a first registration message, where the first registration message carries first capability information, and the first capability information indicates that the communication device has a PIN network management capability;

a transceiver 1002, configured to send a first registration message; acquiring a first PIN network local routing rule from a strategy control function network element, wherein the first PIN network local routing rule is related to first capability information; and sending the first PIN network local routing rules to the second terminal device.

In one implementation, the first PIN network local routing rule includes one or more of the following information: the data network name or slice information indicates that the traffic flow in the PDU session corresponding to the data network name or slice information is allowed to be routed locally.

In one implementation, the first PIN network local routing rule includes a list of device identifications.

The transceiver 1002 is further configured to receive a correspondence between address information from the second terminal device and a device identifier, where the device identifier is determined by the second terminal device based on the device identifier list; acquiring a local routing rule of the second PIN network according to the corresponding relation; and sending the second PIN network local routing rule to the second terminal equipment.

In one implementation, the transceiver unit 1002 is specifically configured to send the correspondence to the policy control function network element, and receive the second PIN network local routing rule from the policy control function network element.

In one implementation, the processing unit 1001 is further configured to generate a second PIN network local routing rule according to the correspondence.

In one implementation, the second PIN network local routing rule includes one or more of the following information: address information or device identification, the address information or device identification indicates that the traffic flow corresponding to the address information or device identification allows local routing.

In one possible embodiment, the apparatus 1000 is applied to a second terminal device.

For example, the processing unit 1001 is configured to send a second registration message, where the second registration message carries second capability information, and the second capability information indicates that the communication device has a personal internet of things PIN network gateway capability;

a transceiver 1002, configured to send a second registration message; acquiring a first PIN network local routing rule; and executing local routing on the acquired service flow according to the first PIN network local routing rule.

In one implementation, the transceiver unit 1002 is specifically configured to obtain a first PIN network local routing rule from a policy control function network element, where the first PIN network local routing rule is related to the second capability information; or acquiring a first PIN network local routing rule from the first terminal equipment, wherein the first PIN network local routing rule is related to first capability information, and the first capability information indicates that the first terminal equipment has PIN network management capability.

In one implementation manner, the transceiver 1002 is specifically configured to send, if the acquired service flow matches the local routing rule of the first PIN network, the service flow to the destination terminal device of the service flow in the PIN network where the second terminal device is located.

In one implementation, the traffic flow matches the first PIN network local routing rule, including one or more of: the flow description information in the local routing rule of the first PIN network comprises information carried by data packets in service flows; the data network name in the first PIN network local routing rule comprises the data network name of the PDU session corresponding to the service flow; the slice information in the local routing rule of the first PIN network comprises slice information of PDU session corresponding to the service flow; the destination terminal equipment corresponding to the destination address information carried in the service flow and the second terminal equipment belong to the same PIN network.

In one implementation, the data network name in the first PIN network local routing rule includes a data network name of a PDU session corresponding to an uplink traffic flow or a data network name of a PDU session corresponding to a downlink traffic flow; and/or slice information in the local routing rule of the first PIN network comprises slice information of a PDU session corresponding to the uplink service flow or slice information of a PDU session corresponding to the downlink service flow.

The processing unit 1001 is further configured to determine a device identifier and address information corresponding to the device identifier in the device identifier list;

the transceiver 1002 is specifically configured to send a correspondence between address information and a device identifier to a first terminal device; acquiring a second PIN network local routing rule from the first terminal equipment; and if the acquired service flow is matched with the local routing rule of the second PIN network, the service flow is sent to the destination terminal equipment of the service flow in the PIN network where the second terminal equipment is located.

In one implementation, the processing unit 1001 is specifically configured to determine one or more PIN members in the PIN member list; and/or determining one or more PIN gateway devices in the PIN gateway device list.

In one implementation, the traffic flow matches the second PIN network local routing rule, including one or more of: the flow description information in the local routing rule of the second PIN network comprises information carried by the data packet in the service flow; the PIN members in the local routing rule of the second PIN network comprise PIN members corresponding to the service flow; the PIN members in the local routing rule of the second PIN network comprise destination terminal equipment corresponding to the service flow; the address information in the second PIN network local routing rule contains destination address information in the traffic flow.

In one implementation, the PIN members in the second PIN network local routing rule include PIN members and/or destination terminal devices corresponding to the uplink traffic flow or PIN members and/or destination terminal devices corresponding to the downlink traffic flow.

In one possible embodiment, the apparatus 1000 is applied to a policy control function network element.

For example, the transceiver 1002 is configured to receive a policy obtaining message, where the policy obtaining message carries indication information, and the indication information indicates that the first terminal device has a PIN network management capability of the personal internet of things or that the second terminal device has a PIN network gateway capability;

a processing unit 1001, configured to determine that local routing is allowed according to the indication information;

the transceiver unit 1002 is further configured to send the first PIN network local routing rule.

The transceiver 1002 is further configured to receive a correspondence between address information and a device identifier, where the device identifier is determined by the second terminal device in the device identifier list;

the processing unit 1001 is further configured to generate a second PIN network local routing rule according to the correspondence;

the transceiver unit 1002 is further configured to send the second PIN network local routing rule to the first terminal device.

It should be noted that, in the embodiments of the present application, the division of the modules is merely schematic, and there may be another division manner in actual implementation, and in addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units. For example, the transceiver unit may comprise a receiving unit and/or a transmitting unit.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the integrated unit may be stored as a computer software product in a storage medium, comprising instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the methods of the various embodiments of this application.

As shown in fig. 11, the embodiment of the present application further provides a schematic structural diagram of a communication device 1100. The apparatus 1100 may be used to implement the methods described in the method embodiments described above, see the description of the method embodiments described above. For example, the communication apparatus 1100 can perform the steps performed by the first terminal device or the second terminal device or the policy control function network element in the methods of fig. 4 to 9 described above.

The apparatus 1100 includes one or more processors 1101. The processor 1101 may be a general purpose processor or a special purpose processor, or the like. For example, a baseband processor, or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processor may be used to control a communication device (e.g., a base station, a terminal, or a chip, etc.), execute a software program, and process the data of the software program. The communication device may comprise a transceiver unit for enabling input (reception) and output (transmission) of signals. For example, the transceiver unit may be a transceiver, a radio frequency chip, or the like.

The apparatus 1100 includes one or more processors 1101, and the one or more processors 1101 may implement the methods of the embodiments shown above. Alternatively, the processor 1101 may implement other functions in addition to the methods of the embodiments shown above.

In one design, processor 1101 may execute instructions to cause apparatus 1100 to perform the methods described in the method embodiments above. The instructions may be stored in whole or in part within the processor 1101, such as the instructions 1103 may be stored in whole or in part within the processor 1101, or the instructions 1103 may be stored in the processor 1101, and the instructions 1104 may be stored in a memory 1102 coupled to the processor, the processor 1101 may execute the instructions 1103 and the instructions 1104 simultaneously to cause the apparatus 1100 to perform the methods described in the method embodiments described above. Instructions 1103 and 1104 are also referred to as computer programs.

In yet another possible design, the communication device 1100 may further include circuitry that may perform the functions of the foregoing method embodiments.

In yet another possible design, the apparatus 1100 may include one or more memories 1102 having instructions 1104 stored thereon that may be run on the processor 1101 to cause the apparatus 1100 to perform the methods described in the method embodiments above. Optionally, the memory 1102 may also have data stored therein. Instructions and/or data may also be stored in the optional processor 1101. For example, the one or more memories 1102 may store the correspondence described in the above embodiments, or related parameters or tables or the like involved in the above embodiments. The processor and the memory may be provided separately or may be integrated.

In yet another possible design, apparatus 1100 may further include a transceiver 1105 and an antenna 1106. The processor 1101 may be referred to as a processing unit, controlling the apparatus (terminal or base station). The transceiver 1105 may be referred to as a transceiver, a transceiver circuit, a transceiver unit, or the like, for implementing a transceiver function of the device through the antenna 1106.

The processor may be a general purpose central processing unit (central processing unit, CPU), microprocessor, application-specific integrated circuit (ASIC), one or more integrated circuits for controlling the execution of programs in accordance with the present application, a general purpose processor, digital signal processor (digital signal processor, DSP), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be in a storage medium located in a memory.

The memory may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory. The memory may be stand alone and be coupled to the processor via a communication line. The memory may also be integrated with the processor.

The present application also provides a computer readable medium having stored thereon a computer program which, when executed by a computer, implements the traffic flow routing method of any of the method embodiments described above.

The present application further provides a computer program product, which comprises a computer program, and the computer program when executed by a computer implements the service flow routing method of any of the above method embodiments.

The embodiment of the application also provides a communication system which comprises the second terminal equipment and the strategy control function network element. The second terminal device and the policy control function network element can implement the service flow routing method of any method example.

Optionally, the communication system further comprises a first terminal device.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be the communication device described above. Computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. The computer readable storage medium may be the storage medium described above or the memory described above.

In one possible design, when the communication device is a chip, such as a chip in a network device, or a chip, such as a chip in a terminal device, the determining unit or processor 1101 may be one or more logic circuits, and the transmitting unit or receiving unit or transceiver 1105 may be an input/output interface, also referred to as a communication interface, or an interface circuit, or an interface, or the like. Alternatively, the transceiver 1105 may be a transmitting unit and a receiving unit, the transmitting unit may be an output interface, and the receiving unit may be an input interface, and the transmitting unit and the receiving unit are integrated into one unit, for example, the input/output interface. As shown in fig. 12, the communication apparatus shown in fig. 12 includes a logic circuit 1201 and an interface circuit 1202. I.e. the processing unit or processor 1101 may be implemented as logic circuitry 1201 and the transceiver unit or transceiver 1105 may be implemented as interface circuitry 1202. The logic circuit 1201 may be a chip, a processing circuit, an integrated circuit, a system on chip (SoC) chip, or the like, and the interface circuit 1202 may be a communication interface, an input/output interface, or the like. In the embodiment of the application, the logic circuit and the interface circuit may also be coupled to each other. The embodiments of the present application are not limited to specific connection modes of the logic circuit and the interface circuit.

In some embodiments of the present application, the logic 1201 and interface 1202 circuits may be used to perform functions or operations performed by the network functions or control plane functions described above, and the like. The interface circuit 1202 may be used to receive signals from other communication devices than the communication device 1200 and transmit to the logic circuit 1201 or transmit signals from the logic circuit 1201 to other communication devices than the communication device 1200. Logic 1201 may be configured to implement any of the method embodiments described above by executing code instructions.

The interface circuit 1202 is illustratively operable to send a second registration message carrying second capability information indicating that the communication device has PIN network gateway capability. The functions or operations performed by the communication device may refer to the foregoing method embodiments, and are not described herein.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of elements is merely a logical functional division, and there may be additional divisions of actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices, or elements, or may be an electrical, mechanical, or other form of connection.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purposes of the embodiments of the present application.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

From the above description of embodiments, it will be apparent to those skilled in the art that the present application may be implemented in hardware, or firmware, or a combination thereof. When implemented in software, the functions described above may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer.

In summary, the foregoing is merely an example of the technical solution of the present application, and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application should be included in the protection scope of the present application.

Claims

1. A traffic flow routing method, the method comprising:

the method comprises the steps that a first terminal device sends a first registration message, wherein the first registration message carries first capability information, and the first capability information indicates that the first terminal device has personal internet of things PIN network management capability;

the first terminal equipment acquires a first PIN network local routing rule from a strategy control function network element, wherein the first PIN network local routing rule is related to the first capability information;

and the first terminal equipment sends the first PIN network local routing rule to the second terminal equipment.

2. The method of claim 1, wherein the first PIN network local routing rule includes one or more of the following information: and the data network name or the slice information indicates the data network name, or the service flow in the protocol data unit PDU session corresponding to the slice information allows local routing.

3. The method of claim 1, wherein the first PIN network local routing rule comprises a list of device identifications;

the method further comprises the steps of:

The first terminal equipment receives the corresponding relation between the address information from the second terminal equipment and equipment identification, wherein the equipment identification is determined by the second terminal equipment based on the equipment identification list;

the first terminal equipment acquires a second PIN network local routing rule according to the corresponding relation;

and the first terminal equipment sends the second PIN network local routing rule to the second terminal equipment.

4. The method of claim 3, wherein the first terminal device obtains a second PIN network local routing rule according to the correspondence, comprising:

and the first terminal equipment sends the corresponding relation to the strategy control function network element and receives the second PIN network local routing rule from the strategy control function network element.

5. The method of claim 3, wherein the first terminal device obtains a second PIN network local routing rule according to the correspondence, comprising:

and the first terminal equipment generates the second PIN network local routing rule according to the corresponding relation.

6. A method according to any of claims 3-5, wherein the second PIN network local routing rules include one or more of the following information: the address information or the device identifier indicates the address information, or the service flow corresponding to the device identifier allows local routing.

7. A traffic flow routing method, the method comprising:

the second terminal equipment sends a second registration message, wherein the second registration message carries second capability information, and the second capability information indicates that the second terminal equipment has personal internet of things PIN network gateway capability;

the second terminal equipment acquires a first PIN network local routing rule;

and the second terminal equipment executes local routing on the acquired service flow according to the local routing rule of the first PIN network.

8. The method of claim 7, wherein the second terminal device obtains a first PIN network local routing rule, comprising:

the second terminal equipment acquires the first PIN network local routing rule from a strategy control function network element, wherein the first PIN network local routing rule is related to the second capability information; or alternatively

The second terminal device obtains the first PIN network local routing rule from a first terminal device, wherein the first PIN network local routing rule is related to first capability information, and the first capability information indicates that the first terminal device has PIN network management capability.

9. The method according to claim 7 or 8, wherein the second terminal device performs local routing on the acquired traffic flow according to the first PIN network local routing rule, comprising:

And if the acquired service flow is matched with the local routing rule of the first PIN network, the second terminal equipment sends the service flow to the target terminal equipment of the service flow in the PIN network where the second terminal equipment is located.

10. The method of claim 9, wherein the traffic flow matches the first PIN network local routing rule comprising one or more of:

the flow description information in the local routing rule of the first PIN network comprises information carried by the data packet in the service flow;

the data network name in the first PIN network local routing rule comprises the data network name of the protocol data unit PDU session corresponding to the service flow;

the slice information in the local routing rule of the first PIN network comprises slice information of PDU session corresponding to the service flow;

the destination terminal equipment corresponding to the destination address information carried in the service flow and the second terminal equipment belong to the same PIN network.

11. The method of claim 10, wherein the data network name in the first PIN network local routing rule comprises a data network name of a PDU session corresponding to an uplink traffic flow or a data network name of a PDU session corresponding to a downlink traffic flow; and/or

The slice information in the first PIN network local routing rule includes slice information of a PDU session corresponding to an uplink traffic flow or slice information of a PDU session corresponding to a downlink traffic flow.

12. A method according to any of claims 9-11, wherein the first PIN network local routing rules include one or more of the following information: and the data network name or the slice information indicates the data network name or the service flow in the PDU session corresponding to the slice information allows local routing.

13. A method as claimed in claim 7 or 8, wherein the first PIN network local routing rule comprises a list of device identifications;

the second terminal device executes local routing on the acquired service flow according to the first PIN network local routing rule, and the method comprises the following steps:

the second terminal equipment determines equipment identification and address information corresponding to the equipment identification in the equipment identification list;

the second terminal equipment sends the corresponding relation between the address information and the equipment identifier to the first terminal equipment;

the second terminal equipment acquires a second PIN network local routing rule from the first terminal equipment;

And if the acquired service flow is matched with the local routing rule of the second PIN network, the second terminal equipment sends the service flow to the destination terminal equipment of the service flow in the PIN network where the second terminal equipment is located.

14. The method of claim 13, wherein the second terminal device determining a device identification in the list of device identifications comprises:

the second terminal equipment determines one or more PIN members in a PIN member list; and/or

The second terminal device determines one or more PIN gateway devices in a PIN gateway device list.

15. A method according to claim 13 or 14, wherein the traffic flow matches the second PIN network local routing rule, including one or more of:

the flow description information in the local routing rule of the second PIN network comprises information carried by the data packet in the service flow;

the PIN members in the local routing rule of the second PIN network comprise the PIN members corresponding to the service flow;

the PIN members in the local routing rule of the second PIN network comprise destination terminal equipment corresponding to the service flow;

the address information in the second PIN network local routing rule includes destination address information in the traffic flow.

16. The method of claim 15, wherein the PIN members in the second PIN network local routing rule comprise PIN members and/or destination terminal devices corresponding to an uplink traffic flow or PIN members and/or destination terminal devices corresponding to a downlink traffic flow.

17. A method according to any of claims 13-16, wherein the second PIN network local routing rules include one or more of the following information: the address information or the device identifier indicates the address information, or the service flow corresponding to the device identifier allows local routing.

18. A traffic flow routing method, the method comprising:

the method comprises the steps that a policy control function network element receives a policy acquisition message, wherein the policy acquisition message carries indication information, and the indication information indicates that a first terminal device has personal internet of things PIN network management capability or a second terminal device has PIN network gateway capability;

the strategy control function network element determines to allow local routing according to the indication information;

the policy control function network element sends a first PIN network local routing rule.

19. The method of claim 18, wherein the first PIN network local routing rule includes one or more of the following information: and the data network name or the slice information indicates the data network name, or the service flow in the protocol data unit PDU session corresponding to the slice information allows local routing.

20. The method of claim 18, wherein the first PIN network local routing rule comprises a list of device identifications;

the method further comprises the steps of:

the strategy control function network element receives the corresponding relation between address information and equipment identification, wherein the equipment identification is determined in the equipment identification list by the second terminal equipment;

the strategy control function network element generates a second PIN network local routing rule according to the corresponding relation;

and the policy control function network element sends the second PIN network local routing rule to the first terminal equipment.

21. The method of claim 20, wherein the second PIN network local routing rule includes one or more of the following information: the address information or the device identifier indicates the address information, or the service flow corresponding to the device identifier allows local routing.

22. A communication device, comprising:

the processing unit is used for generating a first registration message, wherein the first registration message carries first capability information, and the first capability information indicates that the communication device has personal internet of things PIN network management capability;

a transceiver unit, configured to send the first registration message; acquiring a first PIN network local routing rule from a strategy control function network element, wherein the first PIN network local routing rule is related to the first capability information; and sending the first PIN network local routing rule to a second terminal device.

23. A communication device, comprising:

the processing unit is used for sending a second registration message, wherein the second registration message carries second capability information, and the second capability information indicates that the communication device has personal internet of things PIN network gateway capability;

a transceiver unit, configured to send the second registration message; acquiring a first PIN network local routing rule; and executing local routing on the acquired service flow according to the first PIN network local routing rule.

24. A communication device, comprising:

the receiving and transmitting unit is used for receiving a policy acquisition message, wherein the policy acquisition message carries indication information, and the indication information indicates that the first terminal equipment has personal internet of things PIN network management capability or the second terminal equipment has PIN network gateway capability;

The processing unit is used for determining that the local routing is allowed according to the indication information;

the receiving and transmitting unit is further configured to send a first PIN network local routing rule.

25. A communications apparatus comprising a processor and a memory, the processor coupled to the memory;

the memory stores a computer program or instructions;

the processor for executing a computer program or instructions in the memory to cause the apparatus to perform the method of any of claims 1-21.

26. A communication device comprising logic circuitry and interface circuitry, the interface circuitry to receive signals from or transmit signals to other communication devices than the communication device, the logic circuitry to implement the method of any of claims 1-21 by executing code instructions.

27. A computer-readable storage medium comprising a computer program or instructions which, when run on a computer, cause the method of any one of claims 1-21 to be performed.

28. A computer program product comprising a computer program or instructions which, when run on a computer, cause the method of any one of claims 1-21 to be performed.

29. A communication system comprising a second terminal device for performing the method of any of the preceding claims 7-17 and a policy control function network element for performing the method of any of the preceding claims 18-21.

30. The system of claim 29, further comprising a first terminal device for performing the method of any of the preceding claims 1-6.