WO2024037256A1 - 一种业务流路由方法及装置 - Google Patents

一种业务流路由方法及装置 Download PDF

Info

Publication number
WO2024037256A1
WO2024037256A1 PCT/CN2023/106911 CN2023106911W WO2024037256A1 WO 2024037256 A1 WO2024037256 A1 WO 2024037256A1 CN 2023106911 W CN2023106911 W CN 2023106911W WO 2024037256 A1 WO2024037256 A1 WO 2024037256A1
Authority
WO
WIPO (PCT)
Prior art keywords
local routing
pin
terminal device
network
service flow
Prior art date
Application number
PCT/CN2023/106911
Other languages
English (en)
French (fr)
Inventor
于游洋
时书锋
宗在峰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024037256A1 publication Critical patent/WO2024037256A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the present application relates to the field of communication technology, and in particular, to a service flow routing method and device.
  • 5G core 5G core
  • 5GC 5G core network
  • IoT Internet of things
  • the PIN network includes PIN network management function equipment (PIN element with management capability, PMEC), PIN network gateway function equipment (PIN element with gateway capability, PEGC), and other PIN Elements.
  • PEMC and PEGC are user equipment with 5GC access capabilities, which can access 5GC through the 3rd generation partnership project (3GPP) or non-3GPP (non-3GPP) access technology.
  • 3GPP 3rd generation partnership project
  • non-3GPP non-3GPP (non-3GPP) access technology.
  • Other PIN Elements are end devices, such as smart wearable devices, smart home devices, etc.
  • the related technology only proposes a PIN network architecture, and has not yet proposed a communication solution under the PIN network architecture.
  • Embodiments of the present application provide a business flow routing method and device, which implements the communication process under the PIN network architecture, and can realize local routing of business flows in the PIN network under the control of the network side.
  • a service flow routing method including the following process: a first terminal device sends a first registration message, the first registration message carries first capability information, and the first capability information indicates that the first terminal device has PIN network management capabilities. ; The first terminal device obtains the first PIN network local routing rule from the policy control function network element, and the first PIN network local routing rule is related to the first capability information; the first terminal device sends the first PIN network local routing rule to the second terminal device routing rules.
  • the network side can generate the first PIN network local routing rules, and then send them to the second terminal device through the first terminal device with PIN network management capabilities, so that the second terminal device can perform local routing on the business flow, achieving The transmission of business flows under the PIN network architecture, and the local routing of business flows within the PIN network under the control of the network side.
  • the first PIN network local routing rule includes one or more of the following information: data network name or slice information, where the data network name or slice information indicates the protocol data corresponding to the data network name or slice information.
  • Service flows within a protocol data unit (PDU) session are allowed to be routed locally.
  • the network side uses PDU sessions as the granularity to generate PIN network local routing rules for implementing local routing and control the routing of business flows.
  • the first PIN network local routing rule also includes local routing indication information, which indicates that local routing is allowed for the service flow in the PDU session corresponding to the data network name or slice information.
  • the first PIN network local routing rule includes a device identification list.
  • the service flow corresponding to the device identification allows local routing.
  • the network side uses the service flow as the granularity to generate PIN network local routing rules for implementing local routing to control the routing of the service flow.
  • the first PIN network local routing rule includes local routing indication information, and the local routing indication information indicates that the service flow corresponding to the device identification in the device identification list is allowed to perform local routing.
  • the first terminal device may also receive the correspondence between the address information and the device identification from the second terminal device.
  • the device identification is determined by the second terminal device based on the device identification list; the first terminal device obtains the local route of the second PIN network based on the correspondence.
  • the second terminal device determines the device identity based on the local policy or user preference. Therefore, the second PIN network local routing rule obtained by the first terminal device is related to the local policy or user preference of the second terminal device.
  • the second terminal device determines the device identity based on the second terminal device.
  • Two PIN network local routing rules can perform local routing on business flows and realize local routing of business flows within the PIN network.
  • the first terminal device when it obtains the second PIN network local routing rule according to the corresponding relationship, it can send the corresponding relationship to the policy control function network element and receive the second PIN network local routing rule from the policy control function network element. routing rules.
  • the network side uses the service flow as the granularity to generate PIN network local routing rules for implementing local routing, and controls the routing of the service flow.
  • the first terminal device when the first terminal device obtains the second PIN network local routing rule based on the corresponding relationship, the first terminal device may generate the second PIN network local routing rule based on the corresponding relationship.
  • the first terminal device can generate PIN network local routing rules by itself for implementing local routing, and control the routing of the service flow.
  • the second PIN network local routing rule includes one or more of the following information: address information or device identification, which indicates that the service flow corresponding to the address information or device identification is allowed to proceed locally. routing.
  • a service flow routing method including the following process: a second terminal device sends a second registration message, the second registration message carries second capability information, and the second capability information indicates that the second terminal device has PIN network gateway capability ; The second terminal device acquires the local routing rules of the first PIN network; the second terminal device performs local routing on the acquired service flow according to the local routing rules of the first PIN network.
  • the second terminal device when the second terminal device obtains the first PIN network local routing rule, it can obtain the first PIN network local routing rule, the first PIN network local routing rule and the second capability from the policy control function network element The information is related; or the first PIN network local routing rule can be obtained from the first terminal device, the first PIN network local routing rule is related to the first capability information, and the first capability information indicates that the first terminal device has the PIN network management capability.
  • the second terminal device can directly obtain the PIN network local routing rules for local routing from the policy control function network element, or can obtain the PIN network local routing rules through the first terminal device, and then perform local routing on the service flow. Routing can realize the transmission of business flows under the PIN network architecture and the local routing of business flows within the PIN network.
  • the second terminal device 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 matches the first PIN network local routing rule, the second terminal device The 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 matches the first PIN network local routing rule, including one or more of the following: the flow description information in the first PIN network local routing rule includes information carried by the data packets in the service flow; and /or the data network name in the first PIN network local routing rule contains the data network name of the PDU session corresponding to the service flow; and/or the slicing information in the first PIN network local routing rule contains the slicing information of the PDU session corresponding to the service flow ; and/or the destination terminal device corresponding to the destination address information carried in the service flow and the second terminal device belong to the same PIN network.
  • the data network name in the first PIN network local routing rule includes the data network name of the PDU session corresponding to the uplink service flow, or the data network name of the PDU session corresponding to the downlink service flow.
  • the slicing information in the first PIN network local routing rule includes slicing information of the PDU session corresponding to the uplink service flow, or slicing information of the PDU session corresponding to the downlink service flow.
  • the first PIN network local routing rule includes one or more of the following information: data network name or slice information, which indicates the PDU session corresponding to the data network name or slice information. Traffic flows in are allowed to be routed locally.
  • the first PIN network local routing rule includes a device identification list.
  • the second terminal device When the second terminal device performs local routing on the acquired service flow according to the local routing rules of the first PIN network, it can determine the device identifier and the address information corresponding to the device identifier in the device identifier list; send the address information and the address information corresponding to the device identifier to the first terminal device. Correspondence between device identifiers; obtain the local routing rules of the second PIN network from the first terminal device; if the obtained business flow matches the local routing rules of the second PIN network, the second terminal device in the PIN network where the second terminal device is located Within, the service flow is sent to the destination terminal device of the service flow.
  • the second terminal device when the second terminal device determines the device identification in the device identification list, it may determine one or more PIN members in the PIN member list; and/or it may determine one or more PIN members in the PIN gateway device list.
  • a PIN gateway device when the second terminal device determines the device identification in the device identification list, it may determine one or more PIN members in the PIN member list; and/or it may determine one or more PIN members in the PIN gateway device list.
  • a PIN gateway device when the second terminal device determines the device identification in the device identification list, it may determine one or more PIN members in the PIN member list; and/or it may determine one or more PIN members in the PIN gateway device list.
  • the service flow matches the second PIN network local routing rule, including one or more of the following: the flow description information in the second PIN network local routing rule includes information carried by the data packets in the service flow; and /or the PIN member in the second PIN network local routing rule contains the PIN member corresponding to the service flow; and/or the PIN member in the second PIN network local routing rule contains the destination terminal device corresponding to the service flow; and/or the second PIN
  • the address information in the network local routing rules includes the destination address information in the service flow.
  • the PIN members in the local routing rules of the second PIN network include PIN members corresponding to the upstream service flow. and/or the destination terminal equipment, or the PIN member corresponding to the downstream service flow and/or the destination terminal equipment.
  • the second PIN network local routing rule includes one or more of the following information: address information or device identification, which indicates that the service flow corresponding to the address information or device identification is allowed to proceed locally. routing.
  • a service flow routing method including the following process: the policy control function network element receives a policy acquisition message, the policy acquisition message carries indication information, and the indication information indicates that the first terminal device has the personal Internet of Things PIN network management capability or the third The second terminal device has the PIN network gateway capability; the policy control function network element determines to allow local routing according to the instruction information; the policy control function network element sends the first PIN network local routing rule.
  • the first PIN network local routing rule includes one or more of the following information: data network name or slice information, which indicates the PDU session corresponding to the data network name or slice information. Traffic flows in are allowed to be routed locally.
  • the first PIN network local routing rule includes a device identification list.
  • the policy control function network element can also receive the corresponding relationship between the address information and the device identification.
  • the device identification is determined in the device identification list for the second terminal device; the policy control function network element generates the second PIN network local routing rule according to the corresponding relationship; the policy The control function network element sends the second PIN network local routing rule to the first terminal device.
  • the second PIN network local routing rule includes one or more of the following information: address information or device identification, which indicates that the service flow corresponding to the address information or device identification is allowed to proceed locally. routing.
  • a communication device may be a first terminal device or a second terminal device or a policy control function network element, or may be configured as a first terminal device or a second terminal device or a policy control function network element. in the chip.
  • the communication device can implement the method provided in any of the above aspects.
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method.
  • the modules, units, or means can be implemented by hardware, software, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • a communication device including a transceiver unit.
  • the communication device further includes a processing unit.
  • the communication device may implement any aspect or any one of the aspects implement the provided method.
  • a communication device including a processor.
  • the processor may be used to perform any of the above aspects or implement any of the methods provided in any of the aspects.
  • the device further includes a memory, the processor is coupled to the memory, and the memory is used to store computer programs or instructions.
  • the processor can execute the programs or instructions in the memory, so that the device can perform any of the above aspects or any of the above. Either of the aspects implements the provided method.
  • a seventh aspect provides a communication device, which includes an interface circuit and a logic circuit, and the logic circuit is coupled to the interface circuit.
  • the interface circuit may be a code/data read-write interface circuit, which is used to receive computer execution instructions (computer execution instructions are stored in the memory, may be read directly from the memory, or may pass through other devices) and transmitted to the logic circuit , so that the logic circuit runs the computer execution instructions to perform any of the above aspects or any of the aspects to implement the provided method.
  • the communication device may be a chip or a system on a chip.
  • a communication device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute any one of the above aspects or any one of the aspects to implement the provided method.
  • processors there can be one or more processors, and there can also be one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated on the same chip as the processor, or can be set in different On the chip, this application does not limit the type of memory and the arrangement of the memory and the processor.
  • ROM read-only memory
  • the communication device can be a chip, and the processor can be implemented by hardware or software.
  • the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor
  • the processor can be a general-purpose processor that is implemented by reading software code stored in a memory.
  • the memory can be integrated into the processor, or it can be located outside the processor and exist independently.
  • a processor including: an input circuit, an output circuit and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes any of the above aspects or any one of the aspects to implement the provided method.
  • the above-mentioned processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, the receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by the transmitter, and the input circuit and the output A circuit may be the same circuit that functions as an input circuit and an output circuit at different times.
  • This application does not limit the specific implementation methods of the processor and various circuits.
  • a communication device including: a logic circuit and an input-output interface, the input-output interface being used to communicate with a module outside the communication device; the logic circuit being used to run a computer program or instructions to execute any of the above Any method provided by the design.
  • the communication device 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 including the above-mentioned first terminal device or the second terminal device or the policy control function network element, or the above-mentioned first terminal device or the second terminal device or the policy control function network element.
  • a device included in the first terminal equipment or the second terminal equipment or the policy control function network element such as a chip.
  • the input/output interface may be a code/data read-write interface circuit, or a communication interface, which is used to receive computer programs or instructions (the computer programs or instructions are stored in the memory, may be read directly from the memory, or may be through other devices) and transmitted to the input and output interface, so that the input and output interface runs a computer program or instructions to perform any of the above methods.
  • the communication device may be a chip.
  • a computer program product includes: a computer program (which can also be called a code, or an instruction).
  • a computer program which can also be called a code, or an instruction.
  • the computer program When the computer program is run, it causes the computer to execute any of the above aspects or aspects. Any of the methods provided.
  • a computer-readable medium stores a computer program (which can also be called a code, or an instruction), and when it is run on a computer, it causes the computer to execute any one of the above aspects or any one of the above. Either aspect implements the provided method.
  • a chip system in a thirteenth aspect, includes a processor and an interface for supporting a communication device to implement any of the above aspects or any of the functions provided by any of the aspects.
  • the chip system further includes a memory for storing necessary information and data of the communication device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a fourteenth aspect provides a chip device, the chip device including an input interface and/or an output interface.
  • the input interface can implement the receiving function provided by any of the above aspects or any one of the aspects
  • the output interface can implement the sending function provided by any of the above aspects or any of the aspects.
  • a fifteenth aspect provides a functional entity, which is used to implement any of the above aspects or any of the methods provided in any aspect.
  • a sixteenth aspect provides a communication system, including 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.
  • Figure 1 is a schematic diagram of the architecture of a communication system
  • Figure 2 is a schematic diagram of the architecture of a communication system
  • Figure 3 is a schematic diagram of a PIN network architecture
  • Figure 4 is a schematic diagram of a service flow routing process provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of a service flow routing process provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram of a service flow routing process provided by an embodiment of the present application.
  • Figure 7 is a schematic diagram of a service flow routing process provided by an embodiment of the present application.
  • Figure 8 is a schematic diagram of a service flow routing process provided by an embodiment of the present application.
  • Figure 9 is a schematic diagram of a service flow routing process provided by an embodiment of the present application.
  • Figure 10 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 11 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the mobile communication system may be a fourth generation (4th Generation, 4G) communication system (for example, a long term evolution (LTE) system), a fifth generation mobile communication (5th generation, 5G) communication system (for example, New radio (NR) system), and future mobile communication systems such as 6G.
  • 4G fourth generation
  • 5G fifth generation mobile communication
  • NR New radio
  • 6G future mobile communication systems
  • Mobile communication systems support multiple access technologies.
  • 5GC supports multiple access technologies
  • EPC evolved packet core
  • the network architecture and business scenarios described in the embodiments of this application are for the purpose of explaining the technical solutions of the embodiments of this application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of this application.
  • Those of ordinary skill in the art will know that with the network With the evolution of architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
  • Figure 1 is a schematic diagram of a network architecture provided by an embodiment of the present application, including: user equipment, (wireless) access network equipment, user plane network elements, data network, access management network elements, session management network elements, application network elements, unified data management network elements, policy control network elements and network opening network elements, etc.
  • Each network element involved in the network architecture is described below.
  • User equipment can also be called access terminal, terminal, terminal equipment, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, User agent or user device, etc.
  • the terminal can be a device with wireless transceiver function, such as a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) ) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, transportation security Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless Wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, Terminals in 5G networks or terminals in future evolution networks, etc.
  • PDAs personal digital assistants
  • wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones. Use, such as various types of smart bracelets, smart jewelry, etc. for physical sign monitoring.
  • Access network equipment can also be called access equipment or access network elements.
  • R)AN can manage wireless resources and serve as user equipment. Provide access services and complete the forwarding of user equipment data between user equipment and the core network.
  • R)AN can also be understood as a base station in the network.
  • the access network device in the embodiment of the present application may be any communication device with wireless transceiver functions used to communicate with user equipment.
  • the access network equipment includes but is not limited to: evolved node B (evolved node B, eNB), wireless network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller) , BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved NodeB, HeNB, or home node B, HNB), indoor baseband processing unit (building base band unit, BBU), transceiver point (transmit receive point, TRP) or transmission point (TP), etc., etc., can also be 5G, such as the next generation base station or next generation node B (generation node B, gNB) in the NR system, or the transmission point (TRP or TP ), one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be
  • gNB may include centralized units (CUs) and DUs.
  • the gNB may also include an active antenna unit (AAU).
  • CU implements some functions of gNB
  • DU implements some functions of gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, media access control (MAC) layer and physical (physical, PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical layer
  • the RRC layer information is generated by the CU, and will eventually be encapsulated by the PHY layer of the DU into PHY layer information, or converted from the PHY layer information.
  • high-level signaling such as RRC layer signaling
  • the access network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the CU can be divided into access network equipment in the access network (radio access network, RAN), or the CU can be divided into access network equipment in the core network (core network, CN). This application does not Make limitations.
  • User plane network element As an interface with the data network, it completes functions such as user plane data forwarding, session/flow-level accounting statistics, and bandwidth limitation. That is, packet routing and forwarding and quality of service (QoS) processing of user plane data, etc.
  • QoS quality of service
  • the user plane network element may be a user plane function (UPF) network element.
  • UPF user plane function
  • Data network used to provide a network for transmitting data.
  • the data network may be a data network (DN).
  • Access management network element mainly used for mobility management and access management.
  • the access management network element can be the access and mobility management function (AMF), which mainly performs functions such as mobility management and access authentication/authorization. In addition, it is also responsible for transmitting user policies between the terminal and the policy control function (PCF) network element.
  • AMF access and mobility management function
  • PCF policy control function
  • Session management network element mainly used for session management, Internet protocol (IP) address allocation and management of user equipment, selection of manageable user plane functions, policy control and charging The endpoint of the functional interface and downstream data notification, etc.
  • IP Internet protocol
  • the session management network element can be a session management function (SMF) network element, which completes terminal IP address allocation, UPF selection, accounting and QoS policy control, etc.
  • SMF session management function
  • the application network element can be an application function (AF) network element, which represents the application function of a third party or operator. It is the interface for the 5G network to obtain external application data. It mainly Used to convey the requirements from the application side to the network side.
  • AF application function
  • Unified data management network element responsible for the management of user identification, contract data, authentication data, and user service network element registration management.
  • the unified data management network element may be unified data management (UDM).
  • Policy control network element including user subscription data management function, policy control function, charging policy control function, QoS control, etc., a unified policy framework used to guide network behavior, which is a control plane functional network element (such as AMF, SMF network Yuan, etc.) provides policy rule information, etc.
  • a control plane functional network element such as AMF, SMF network Yuan, etc.
  • the policy control network element may be the PCF.
  • Network open network element In the 5G communication system, the network open network element can be a network open function (NEF) network element, which is mainly used to expose 3GPP network function services to AF. and capabilities, and also allows AF to provide information to 3GPP network functions.
  • NEF network open function
  • the network architecture may include more or fewer network elements than the network elements shown above.
  • the above network architecture may also include an authentication server responsible for authenticating user equipment and determining the legitimacy of the user equipment.
  • the authentication server can be an authentication server function (AUSF) network element.
  • AUSF authentication server function
  • the above network architecture supports the radio access technology (RAT) defined by 3GPP to access the core network (CN).
  • the RAT defined by 3GPP includes long term evolution (long term evolution, LTE), 5G RAN, etc.
  • the above network architecture also supports non-3GPP (non-3GPP, N3G or N3GPP) access technologies through non-3GPP interworking function (N3IWF) or next generation packet data gateway (ngPDG). into the core network.
  • N3IWF non-3GPP interworking function
  • ngPDG next generation packet data gateway
  • the 5G network architecture is shown in Figure 2, including the local public land mobile network (HPLMN) and non-3GPP network.
  • HPLMN public land mobile network
  • the UE can access 5GC through 3GPP access in HPLMN, and can access 5GC through untrusted non-3GPP access.
  • N3IWF is the non-3GPP access gateway.
  • the non-3GPP access network may include, for example, a non-trusted wireless local area network (WLAN) access network
  • the N3IWF device may include, for example, a router.
  • WLAN wireless local area network
  • the 5G core network also supports trusted non-3GPP access and/or wired network access.
  • the trusted non-3GPP access network may include, for example, a trusted WLAN network
  • the wired network may include, for example, fixed home network access (hereinafter referred to as fixed network). wait.
  • the 5G core network supports trusted non-3GPP access, its 5G network architecture is similar to Figure 2.
  • the untrusted non-3GPP access in Figure 2 can be replaced with a trusted non-3GPP access, and the N3IWF can be replaced with a trusted non-3GPP gateway function (TNGF).
  • TNGF trusted non-3GPP gateway function
  • the 5G core network supports wired network access, its 5G network architecture is similar to Figure 2.
  • the untrusted non-3GPP access in Figure 2 can be replaced by a wired network access, and the N3IWF can be replaced by a wireline access gateway function (W-AGF).
  • Access network equipment between the UE and the access gateway may include WLAN access point (AP), fixed access network equipment (fixed access network, FAN), switches, routers, etc.
  • non-3GPP access technologies include trusted WLAN access, untrusted WLAN access, or wired network access and other access technologies. Regardless of whether it is a trusted non-3GPP access or an untrusted non-3GPP access, the core network can use the 3GPP access core network architecture and service interface shown in Figure 1, or it can use the network shown in Figure 2 architecture and point-to-point interface protocols.
  • the above network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (such as a cloud platform).
  • the above network elements or functions can be divided into one or more services.
  • instances of the above-mentioned functional network elements, or instances of services included in the above-mentioned functional network elements, or service instances that exist independently of network functions may be called service instances.
  • the above network element or function can be implemented by one device, or can be implemented by multiple devices together, or can be a functional module in one device, which is not specifically limited in the embodiments of this application.
  • a PIN network architecture is shown in Figure 3, including PEMC and PEGC.
  • the PIN network may also include a PIN Element, which is also called a PIN member and may be other UEs besides PEMC and PEGC, such as the UE and/or N3GPP device as shown in Figure 3.
  • PEMC and PEGC are user equipment with 5GC access capabilities and can access 5GC through 3GPP access technology or non-3GPP access technology.
  • the connection between PEGC and PEMC is established based on the PC5 interface.
  • PEMC is the management node in the PIN network, has 5GC access capabilities, and can independently access 5GC.
  • PEGC is the gateway node in the PIN network.
  • PEGC also has 5GC access capabilities, so it can also independently access and register for 5GC.
  • All PIN members in the PIN network establish connections with PEGC, and PIN members can access based on non-3GPP access technologies such as wireless fidelity (Wi-Fi) or Bluetooth.
  • Wi-Fi wireless fidelity
  • Bluetooth wireless fidelity
  • the PIN Element node can be an end device with 5GC access capability, or it can be an end device without 5GC access capability, which is referred to as the end device below.
  • Terminal devices can belong to third-party service providers, such as smart wearable devices, smart home devices, etc.
  • the embodiment of the present application provides a service flow routing method, which can realize the communication process under the PIN network architecture, and can realize the local routing of the service flow in the PIN network under the control of the network side.
  • Figure 4 is a schematic diagram of a service flow routing method provided by an embodiment of the present application. The method includes the following steps:
  • the second terminal device sends a second registration message, and accordingly, 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 device has PIN network gateway capability.
  • the second terminal device is PEGC.
  • the second management function network element is a network element that provides access management functions for the second terminal device.
  • the second management function network element is an AMF serving PEGC.
  • the second terminal device obtains the local routing rules of the first PIN network.
  • S403 The second terminal device performs local routing on the acquired service flow according to the local routing rules of the first PIN network.
  • the second terminal device with PIN network gateway capability can perform local routing on the business flow according to the obtained local routing rules of the first PIN network, and can realize the transmission of the business flow under the PIN network architecture, and can realize the internal routing of the business flow within the PIN network. Local routing of business flows.
  • the second terminal device can obtain the local routing rules of the first PIN network through the following 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.
  • the first PIN network local routing rule is related to the first capability information.
  • the first capability information indicates that the first terminal device has PIN network management capabilities.
  • the first terminal device is PEMC.
  • the first terminal device may obtain the first PIN network local routing rule from the policy control function network element.
  • the current method is shown in Figure 5, including the following steps:
  • the first terminal device sends a first registration message, and accordingly, 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 device has PIN network management capabilities.
  • the first access management function network element is a network element that provides access management functions for the first terminal device.
  • the first access management function network element is an AMF serving 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.
  • the first terminal device obtains the first PIN network local routing rule from the policy control function network element.
  • 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 capabilities.
  • the policy control function network element determines to allow local routing based on the indication information, and sends the first PIN network local routing rule.
  • the policy control function network element determines that the first terminal device needs to transmit data in the PIN network based on the first terminal device having PIN network management capabilities.
  • There are usually services that can be routed locally in the PIN network for example, based on service characteristics (such as Internet (internet services, data packet transmission services, etc.) determine the services that allow local routing, so 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 on whether to allow local routing. Therefore, the policy control function network element can carry relevant information about the policy in the first PIN network local routing rule.
  • S503 The first terminal device sends the first PIN network local routing rule to the second terminal device.
  • the first PIN network local routing rule is related to the second capability information.
  • 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 the PIN network gateway capability.
  • the policy control function network element determines to allow local routing based on the indication information, and sends the first PIN network local routing rule. For example, the policy control function network element determines that the second terminal device needs to transmit data in the PIN network based on the second terminal device having the PIN network gateway capability.
  • There are usually services that can be routed locally in the PIN network for example, based on service characteristics (such as Internet services, data packet transmission services, etc.) determine the services that allow local routing, so 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 on whether to allow local routing. Therefore, the policy control function network element can carry relevant information about the policy in the first PIN network local routing rule.
  • Local routing means that service flows are transmitted through terminals in the PIN network (such as through PEGC, or directly between two terminal devices) without passing through nodes in the operator's network (such as RAN or UPF network elements in the 5G network) )transmission.
  • the policy control network element can decide whether the service is allowed to be routed locally. For data on services within the PIN network, such as but not limited to data sharing within the home network (such as casting mobile phone screens to TVs) or home appliance control (such as adjusting air conditioner temperature through mobile phones), these services do not pass through nodes in the operator's network. Transmission can also be implemented, and then the policy control function network element can decide to allow local routing for this type of service.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • video call services For business data on the Internet, such as but not limited to Internet Protocol (IP) Multimedia Subsystem (IMS) voice, or video call services, such services are guaranteed through nodes in the operator's network If the service quality of the service flow or the execution of charging are required to achieve voice communication or video calls between the two parties, then the policy control function network element can decide that such services are not allowed to be routed locally.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • the first PIN network local routing rule in the above embodiment may contain different information.
  • the following describes the possible implementation method 1 and implementation method 2.
  • the above-mentioned first PIN network local routing rule may include data network name (data network name, DNN) and/or slice information (slice info).
  • the data network name indicates that the service flow in the PDU session corresponding to the data network name is allowed to be routed locally.
  • the slice information indicates that the service flow in the PDU session corresponding to the slice information is allowed to be routed locally.
  • the above-mentioned first PIN network local routing rule may also include local routing indication information.
  • the local routing indication information indicates that the service flow in the PDU session corresponding to the data network name or slice information is allowed to proceed locally. routing.
  • the above S403 includes if the obtained service flow matches the local routing rule of the first PIN network, 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 obtained 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.
  • the service flow matches the local routing rule of the first PIN network, including one or more of the following situations:
  • Case 1.1 The flow description information in the local routing rule of the first PIN network contains the information carried by the data packets in the service flow.
  • the flow description information includes at least one of the five-tuple information, and the five-tuple information includes the source IP address, the destination IP address, the source port number, and the destination IP address. At least one of the port number or protocol type.
  • the source IP address is the IP address of the terminal device sending the uplink service flow
  • the source port number is the port number of the terminal device sending the uplink service flow.
  • the destination IP address is the IP address of the terminal device receiving the downlink service flow
  • the destination port number is the port number of the terminal device receiving the downlink service flow.
  • the flow description information may be a five-tuple, a triple, or a four-tuple, etc.
  • the five-tuple in the local routing rule of the first PIN network contains the five-tuple carried by the data packet in the business flow. That is, the five-tuple carried by the data packet in the business flow is the five-tuple in the local routing rule of the first PIN network.
  • a subset of indicating that the service flow belongs to the service flow that allows local routing.
  • the flow description information includes at least one of the source MAC address or the destination MAC address.
  • the source MAC address is the MAC address of the terminal device sending the uplink service flow.
  • the destination MAC address is the MAC address of the terminal device receiving the downlink service flow.
  • Case 1.2 The data network name in the first PIN network local routing rule contains the data network name of the PDU session corresponding to the service flow.
  • the data network name in the first PIN network local routing rule includes the data network name of the PDU session corresponding to the uplink service flow, and/or the data network name of the PDU session corresponding to the downlink service 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. The data network name is used to determine whether the service flow corresponding to the PDU session allows local routing.
  • Case 1.3 The slicing information in the local routing rule of the first PIN network contains the slicing information of the PDU session corresponding to the service flow.
  • the slicing information in the first PIN network local routing rule includes slicing information of the PDU session corresponding to the uplink service flow, and/or slicing information of the PDU session corresponding to the downlink service flow.
  • the slicing information is one of the attributes of the PDU session, and the slicing information is used to determine whether the service flow corresponding to the PDU session allows local routing.
  • the slice information may include network slice selection assistance information (NSSAI), or single NSSAI (single-NSSAI, S-NSSAI).
  • Case 1.4 The destination terminal device corresponding to the destination address information carried in the service flow and the second terminal device belong to the same PIN network.
  • the destination terminal device and the second terminal device belong to the same PIN network, it means that the service flow can be received by the destination terminal device without passing through nodes in the operator's network, so the service flow can be allowed to be routed locally.
  • the second terminal device determines the PDU session corresponding to the obtained service flow. For example, the PDU session corresponding to the service flow is determined based on the source IP address in the received service flow.
  • the second terminal device based on the received service flow Find the destination terminal device using the destination IP address.
  • the PDU session corresponding to the address also allows local routing (the PDU session corresponding to the source IP address and the PDU session corresponding to the destination IP address
  • the PDU session corresponding to the IP address belongs to the same PDU session, and it is known that the PDU session allows local routing), then the second terminal
  • the device sends the above service flow data packet directly to the above destination terminal device without going through nodes in the operator network, such as 5GC.
  • the second terminal device performs local routing.
  • the second terminal device passes the above service flow data through
  • the PDU session is sent to the 5GC, that is, the second terminal device does not perform local routing.
  • the end device sends the service flow data packet to the 5GC through the PDU session, that is, the second end device does not perform local routing.
  • the second terminal device will pass the above service flow data
  • the packet is sent to the 5GC via PDU session, i.e. the second end device does not perform local routing.
  • the second terminal device first determines whether local routing is possible by obtaining the source IP address of the service flow, and then makes further judgment based on the judgment result.
  • the order may not be limited, but may be flexibly arranged according to actual 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 determines whether the PDU session corresponding to the source IP address and the PDU session corresponding to the destination IP address support local routing. When both the corresponding PDU session and the PDU session corresponding to the destination IP address support local routing, local routing is performed.
  • the above-mentioned first PIN network local routing rule may include a device identification list, where the service flow corresponding to the device identification in the device identification list is allowed to perform local routing.
  • Device identification may include but is not limited to MAC address, IP address, device name, etc. The device identification can be used to identify PIN members and/or PEGC.
  • the first PIN network local routing rule may also include local routing indication information. The local routing indication information indicates that the service flow corresponding to the device identification in the device identification list is allowed to perform local routing.
  • the second terminal device performs local routing on the obtained service flow, that is, the second terminal device performs local routing on the obtained service flow.
  • the service flow is sent to the destination terminal device of the service flow.
  • the service flow matches the device identification list in the first PIN network local routing rule means that the device identification list in the first PIN network local routing rule contains the device identification corresponding to the service flow.
  • the second terminal device performs local routing on the acquired service flow according to the first PIN network local routing rules and in combination with local policies and/or user preferences. That is to say, the range that has been allowed local routing is further limited according to the local policy and/or user preference of the second terminal device, which can enhance the user's sense of control and optimize the user experience.
  • the second terminal device determines the device identification and the address information corresponding to the device identification in the above-mentioned device identification list according to the local policy and/or user preference, and sends the corresponding relationship between the address information and the device identification to the first terminal device,
  • the first terminal device obtains the second PIN network local routing rule according to the corresponding relationship, and then sends the second PIN network local routing rule to the second terminal device. If the obtained business flow matches the second PIN network local routing rule, the first terminal device
  • 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.
  • IP addresses are usually randomly assigned, they may change during the communication process (that is, the same device may be assigned different IP addresses during two communication processes). If the second terminal device only reports the IP address, the local routing rules of the second PIN network can only be determined based on the reported IP address. If the IP address of the terminal changes, the second terminal device will be determined based on the second PIN network. The device located by the IP address in the local routing rule is different from the device actually corresponding to the service flow, resulting in an error in the local routing of the service flow.
  • the device identification is the contract information of the device and is fixed during the communication process. If the second terminal device reports the corresponding relationship, the local routing rules of the second PIN network are determined based on the corresponding relationship. If the second PIN network local routing rule includes a device identifier, the second terminal device can match the device identifier corresponding to the service flow with the device identifier in the second PIN network local routing rule to decide whether to allow local routing. If the second PIN network local routing rule includes an IP address, the second terminal device can match the IP address in the service flow with the IP address in the second PIN network local routing rule to decide whether to allow local routing (in the terminal). When the IP address changes, since the first terminal device has PIN network management capabilities, the first terminal device can obtain that the IP address of the terminal has changed.
  • the first terminal device can report the IP address of the terminal, the policy control function network element updates the IP address in the second PIN network local routing rule, and then downloads the updated second PIN network local routing rule. sent to the second terminal device).
  • the second PIN network local routing rule includes a device identification and an IP address
  • the second terminal device matches the IP address in the service flow with the IP address in the second PIN network local routing rule to decide whether to allow local routing. Since The header of the service flow data packet carries the IP address, so on the basis of ensuring accurate local routing of the service flow, the decision-making efficiency of the second terminal device can be improved. That is to say, by reporting the correspondence between the address information and the device identification, the second terminal device can ensure more accurate local routing of the service flow.
  • the second terminal device may determine one or more PIN members in the PIN member list, and/or determine one or more PIN gateway devices in the PIN gateway device list.
  • the terminal devices corresponding to one or more PIN gateway devices determined by the second terminal device are allowed to perform local routing.
  • the terminal device corresponding to the PIN gateway device refers to the terminal device that can communicate with the PIN gateway device, that is, the terminal device sent to The service flow of the terminal device is forwarded through the PIN gateway device.
  • 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 except the second terminal device.
  • the first terminal device obtains the second PIN network local routing rule according to the corresponding relationship by: sending the corresponding relationship to the policy control function network element, and the policy control function network element generates the second PIN according to the corresponding relationship. network local routing rules, and then sends the second PIN network local routing rules to the first terminal device.
  • the policy control function network element determines that the device identifier in the corresponding relationship allows local routing, and then includes the address information corresponding to the device identifier that allows local routing in the generated second PIN network local routing rule.
  • the first terminal device obtains the local routing rule of the second PIN network according to the corresponding relationship: A terminal device generates a second PIN network local routing rule based on the corresponding relationship. Specifically, if the first terminal device determines that the device identifier in the corresponding relationship allows local routing, then the address information in the corresponding relationship is included in the generated second PIN network local routing rule.
  • the second PIN network local routing rule obtained through the above method includes address information.
  • the address information indicates that the service flow corresponding to the address information is allowed to be routed locally.
  • the above-mentioned second PIN network local routing rule may also include a device identification.
  • the device identifier indicates that the service flow corresponding to the device identifier is allowed to be routed locally.
  • the service flow matches the local routing rules of the second PIN network, including one or more of the following situations:
  • Case 2.1 The flow description information in the local routing rule of the second PIN network contains the information carried by the data packets in the service flow.
  • This situation 2.1 is similar to the above situation 1.1 and will not be described again here.
  • Case 2.2 The PIN member in the local routing rule of the second PIN network contains the PIN member corresponding to the service flow.
  • the PIN members corresponding to the service flow in the second PIN network local routing rule include the PIN members corresponding to the uplink service flow, and/or the PIN members corresponding to the downlink service flow.
  • the PIN member corresponding to the uplink service flow is the member that sends the uplink service flow
  • the PIN member corresponding to the downlink service flow is the PIN member that receives the downlink service flow.
  • PIN members are uniquely identified through device identification.
  • Case 2.3 The PIN member in the local routing rule of the second PIN network contains the destination terminal device corresponding to the service flow.
  • the destination terminal device corresponding to the service flow in the second PIN network local routing rule refers to the terminal device that receives the service flow.
  • the destination terminal device can be determined by the destination IP address in the service flow, or by the device identification corresponding to the destination IP address. Sure.
  • This situation indicates that the destination address information in the service flow belongs to the address information in the local routing rule of the second PIN network, indicating that the service flow belongs to a service flow that allows local routing.
  • the "PDU session” involved in the embodiment of this application may be a PDU session that supports one or more access technologies.
  • the access technology may be, but is not limited to, one or more of the following access types: 3GPP access, non-3GPP access, LTE access, 5GRAN access, trusted non-3GPP access, and untrusted non -3GPP access, 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.
  • a PDU session includes one or more QoS flows.
  • the "service flow” involved in the embodiment of this application includes service data flow (SDF), IP data flow, Ethernet data flow (or Ethernet flow) or at least one QoS flow.
  • a QoS flow includes one or more SDFs.
  • An SDF contains one or more IP streams, or one or more Ethernet streams.
  • IP data packets or Ethernet data packets in an SDF correspond to the same service data flow description information.
  • An IP flow includes one or more IP data packets, and the IP data packets in an IP flow have the same IP five-tuple information.
  • An Ethernet stream includes one or more Ethernet data packets, and the Ethernet data packets in an Ethernet stream have the same Ethernet stream description information.
  • the Ethernet flow description information includes at least one of a source MAC address or a destination MAC address.
  • service data packets include IP data packets or Ethernet data packets.
  • Figure 6 is a schematic diagram of a service flow routing process, including the following steps:
  • UE1 registers with the network and creates a PIN network as PEMC.
  • the AMF serving PEMC obtains the first PIN network local routing rule from the PCF or PIN network function (NF).
  • the first PIN network local routing rule includes DNN information and/or slice information, and optionally local route indication information.
  • the local routing indication information indicates that the service flow in the PDU session corresponding to the DNN information and/or slice information is allowed to perform local routing. If the first PIN network local routing rule does not include local routing indication information, the DNN information and/or slice information itself indicates that the service flow in the PDU session corresponding to the DNN information and/or slice information is allowed to perform local routing.
  • DNN information can be information of one DNN or multiple DNN(s).
  • the AMF serving PEMC refers to the AMF that provides access management services for PEMC.
  • S603 The AMF serving PEMC sends the first PIN network local routing rule to PEMC.
  • PEMC receives the first PIN network local routing rule.
  • the local routing rules of the first PIN network please refer to the above embodiment and will not be repeated here. narrate.
  • S604 and S601 ⁇ S603 is not limited.
  • PEGC establishes a connection with PEMC, and PEMC sends the first PIN network local routing rule to PEGC.
  • the SMF serving PEGC provides session management services for PEGC.
  • S605 and S606 are not limited.
  • PEGC performs local routing on the acquired service flow according to the local routing rules of the first PIN network.
  • the network side sends PIN network local routing rules to PEMC, PEMC sends the PIN network local routing rules to PEGC, and then PEGC implements local routing of service flows in the PIN network.
  • PEMC can also establish a PDU session, and the SMF serving PEGC provides session management services for the PEMC.
  • the steps for PEMC to establish a PDU session are not shown in Figure 6 above.
  • Figure 7 is a schematic diagram of a service flow routing process, including the following steps:
  • the AMF serving PEGC obtains the first PIN network local routing rule from the PCF or PIN NF.
  • the first PIN network local routing rule includes DNN information and/or slice information, and optional local routing indication information.
  • the AMF serving PEGC refers to the AMF that provides access management services for PEGC.
  • S704 The AMF serving PEGC sends the first PIN network local routing rule to PEGC. Correspondingly, PEGC receives the first PIN network local routing rule.
  • the network side sends PIN network local routing rules to PEGC, and PEGC implements local routing of service flows in the PIN network.
  • Figure 8 is a schematic diagram of a service flow routing process, including the following steps:
  • the AMF serving PEMC obtains the first PIN network local routing rule from the PCF or PIN NF.
  • the first PIN network local routing rule includes a PIN member identification list and/or a PEGC identification list, and optional local routing indication information.
  • the PIN member identifier is used to uniquely identify a UE in the PIN network.
  • PEGC member ID is used to uniquely identify a PEGC.
  • the AMF serving PEMC refers to the AMF that provides access management services for PEMC.
  • S804 The AMF serving PEMC sends the first PIN network local routing rule to PEMC.
  • PEMC sends the first PIN network local routing rule to PEGC.
  • PEGC After PEGC receives the above-mentioned first PIN network local routing rule, it can have two different implementation methods. Method 1: refer to S805. Method 2: Refer to S806 ⁇ 809.
  • PEGC performs local routing on the acquired service flow according to the local routing rules of the first PIN network.
  • the PEGC performs local routing on the service flow.
  • the PEGC where the destination terminal device is located refers to the PEGC through which the service flow sent to the destination terminal device is forwarded.
  • PEGC selects a device identity from the PIN member identity list and/or PEGC identity list, and sends the device identity and the IP address corresponding to the device identity to PEMC.
  • the device identity includes a PIN member identity and/or a PEGC identity.
  • the PEGC can select the PIN member identity from the PIN member identity list, and/or select the PEGC identity from the PEGC identity list.
  • PEMC stores the corresponding relationship between the device identifier and the IP address, and generates the second PIN network local routing rule based on the corresponding relationship.
  • the local routing rules of the second PIN network please refer to the above embodiments and will not be described again here.
  • PEMC sends the second PIN network local routing rule to PEGC.
  • PEGC performs local routing on the acquired service flow according to the local routing rules of the second PIN network.
  • PEGC when the destination IP address is included in the local routing rule of the second PIN network, PEGC performs local routing on the service flow.
  • the network sends the first PIN network local routing rule to PEMC, PEMC generates the second PIN network local routing rule, and PEGC implements local routing of service flows in the PIN network.
  • the first PIN network local routing rule is taken as an example.
  • the first PIN network local routing rule includes a PIN member identification list and/or a PEGC identification list.
  • the first PIN network local routing rule may not include the PIN member identification list and the PEGC identification list.
  • PEGC can determine the PIN member ID and/or PEGC ID according to local policies and/or user preferences, and then perform local routing on the acquired service flow.
  • the PIN member identification and/or PEGC identification may be used to decide which PIN members and/or PEGC are allowed for local routing.
  • the AMF serving PEMC obtains the local routing rule of the first PIN network is used as an example for explanation.
  • the AMF serving PEGC can obtain the first PIN network local routing rule from the PCF or PIN NF, and the AMF serving PEGC sends the first PIN network local routing rule to the PEGC.
  • this solution can be seen in S703 ⁇ S704 in Figure 7.
  • Figure 9 is a schematic diagram of a service flow routing process, including the following steps:
  • PEGC After PEGC receives the above-mentioned first PIN network local routing rule, it can have two different implementation methods. Method 1: refer to S905. Method 2: Refer to S906 ⁇ 910.
  • PEMC sends the corresponding relationship between the device identification and IP address to PCF or PIN NF.
  • the PCF or PIN network element generates the second PIN network local routing rule based on the corresponding relationship.
  • the network sends the first PIN network local routing rule to PEMC, PEMC generates the second PIN network local routing rule, PEMC sends the second PIN network local routing rule to PEGC, and PEGC implements the routing of business flows within the PIN network. Local routing.
  • the AMF/SMF serving PEMC and the AMF/SMF serving PEGC are deployed on different physical network elements.
  • the AMF/SMF serving PEMC and the AMF/SMF serving PEGC can be deployed on the same physical network element, or the AMF and SMF serving PEMC can be deployed on different physical network elements, or the AMF and SMF serving PEGC It can also be deployed on different physical network elements.
  • system and “network” in the embodiments of this application may be used interchangeably.
  • “and/or” describes the association relationship of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, alone There are three situations B.
  • the character "/” generally indicates that the related objects are in an "or” relationship. At least one mentioned in this application refers to one or more; multiple refers to two or more.
  • words such as “first”, “second” and “third” are only used for the purpose of distinguishing the description and cannot be understood as indicating or implying relative importance.
  • the communication device 1000 includes a processing unit 1001 and a transceiver unit 1002.
  • the functions implemented by the optional transceiver unit 1002 can be implemented by the communication interface
  • the transceiver unit may include a receiving unit and/or a sending unit.
  • the apparatus 1000 may be applied to the first terminal device or the second terminal device or the policy control function network element, or be located in the first terminal device or the second terminal device or the policy control function network element.
  • the communication device 1000 can be used to implement the method described in the above method embodiment.
  • the communication device 1000 can perform each of the methods performed by the first terminal device or the second terminal device or the policy control function network element in the above-mentioned methods of Figures 4 to 9. step.
  • the apparatus 1000 is applied to a first terminal device.
  • the processing unit 1001 is configured to generate a first registration message, the first registration message carries first capability information, and the first capability information indicates that the communication device has PIN network management capabilities;
  • Transceiver unit 1002 configured to send a first registration message; obtain a first PIN network local routing rule from the policy control function network element, where the first PIN network local routing rule is related to the first capability information; and send a first PIN network local routing rule to the second terminal device.
  • One PIN network local routing rule One PIN network local routing rule.
  • the first PIN network local routing rule includes one or more of the following information: data network name or slice information, which indicates the data network name or slice information in the PDU session corresponding to the data network name or slice information. Traffic flows allow local routing.
  • the first PIN network local routing rule includes a list of device identifications.
  • the transceiver unit 1002 is also configured to receive the correspondence between the address information and the device identification from the second terminal device, where the device identification is determined by the second terminal device based on the device identification list; obtain the second PIN network local routing rule according to the correspondence; The second terminal device sends the second PIN network local routing rule.
  • the transceiver unit 1002 is specifically configured to send the corresponding relationship to the policy control function network element and receive the second PIN network local routing rule from the policy control function network element.
  • the processing unit 1001 is also configured to generate a second PIN network local routing rule according to the corresponding relationship.
  • the second PIN network local routing rule includes one or more of the following information: address information or device identification, which indicates that the service flow corresponding to the address information or device identification is allowed to perform local routing.
  • the apparatus 1000 is applied to a second terminal device.
  • the processing unit 1001 is configured to send a second registration message, the second registration message carries second capability information, and the second capability information indicates that the communication device has the personal Internet of Things PIN network gateway capability;
  • the transceiver unit 1002 is configured to send the second registration message; obtain the first PIN network local routing rule; and perform local routing on the obtained service flow according to the first PIN network local routing rule.
  • the transceiver unit 1002 is specifically configured to obtain the first PIN network local routing rule from the policy control function network element, where the first PIN network local routing rule is related to the second capability information; or obtain the first PIN network local routing rule from the first terminal device. Obtain the first PIN network local routing rule, the first PIN network local routing rule is related to the first capability information, and the first capability information indicates that the first terminal device has the PIN network management capability.
  • the transceiver unit 1002 is specifically configured to send the service flow to the destination of the service flow in the PIN network where the second terminal device is located if the obtained service flow matches the local routing rule of the first PIN network. Terminal Equipment.
  • the service flow matches the first PIN network local routing rule, including one or more of the following: the flow description information in the first PIN network local routing rule includes information carried by the data packets in the service flow; the first PIN The data network name in the network local routing rule contains the data network name of the PDU session corresponding to the service flow; the slicing information in the first PIN network local routing rule contains the slicing information of the PDU session corresponding to the service flow; the destination address carried in the service flow The destination terminal device corresponding to the information and the second terminal device belong to the same PIN network.
  • the data network name in the first PIN network local routing rule includes the data network name of the PDU session corresponding to the uplink service flow, or the data network name of the PDU session corresponding to the downlink service flow; and/or the first PIN
  • the slicing information in the network local routing rules includes the slicing information of the PDU session corresponding to the uplink service flow, or the slicing information of the PDU session corresponding to the downlink service flow.
  • the first PIN network local routing rule includes one or more of the following information: data network name or slice information, which indicates the data network name or slice information in the PDU session corresponding to the data network name or slice information. Traffic flows allow local routing.
  • the first PIN network local routing rule includes a list of device identifications.
  • the processing unit 1001 is also configured to determine the device identification and the address information corresponding to the device identification in the device identification list;
  • the transceiver unit 1002 is specifically configured to send the corresponding relationship between the address information and the device identification to the first terminal device; from the first terminal device Obtain the local routing rules of the second PIN network; if the acquired service flow matches the local routing rules of the second PIN network, the service flow is sent to the destination terminal device of the service flow in the PIN network where the second terminal device is located.
  • the processing unit 1001 is specifically configured to determine one or more PIN members in the PIN member list; and/or determine one or more PIN gateway devices in the PIN gateway device list.
  • the service flow matches the second PIN network local routing rule, including one or more of the following: the flow description information in the second PIN network local routing rule includes information carried by the data packets in the service flow; the second PIN The PIN member in the network local routing rule includes the PIN member corresponding to the service flow; the PIN member in the second PIN network local routing rule includes the destination terminal device corresponding to the service flow; the address information in the second PIN network local routing rule includes the service flow Destination address information in .
  • the PIN members in the second PIN network local routing rule include PIN members and/or destination terminal equipment corresponding to the uplink service flow, or PIN members and/or destination terminal equipment corresponding to the downlink service flow.
  • the second PIN network local routing rule includes one or more of the following information: address information or device identification, which indicates that the service flow corresponding to the address information or device identification is allowed to perform local routing.
  • the device 1000 is applied to a policy control function network element.
  • the transceiver unit 1002 is configured to receive a policy acquisition message, the policy acquisition message carries indication information, and the indication information indicates that the first terminal device has the personal Internet of Things PIN network management capability or the second terminal device has the PIN network gateway capability;
  • the processing unit 1001 is configured to determine to allow local routing based on the indication information
  • the transceiver unit 1002 is also used to send the first PIN network local routing rule.
  • the first PIN network local routing rule includes one or more of the following information: data network name or slice information, which indicates the data network name or slice information in the PDU session corresponding to the data network name or slice information. Traffic flows allow local routing.
  • the first PIN network local routing rule includes a list of device identifications.
  • the transceiver unit 1002 is also used to receive the corresponding relationship between the address information and the device identification.
  • the device identification is determined by the second terminal device in the device identification list;
  • the processing unit 1001 is also configured to generate the second PIN network local routing rule according to the corresponding relationship;
  • the transceiver unit 1002 is also configured to send the second PIN network local routing rule to the first terminal device.
  • the second PIN network local routing rule includes one or more of the following information: address information or device identification, which indicates that the service flow corresponding to the address information or device identification is allowed to perform local routing.
  • each functional unit in each embodiment of the present application It can be integrated in a processing unit, or it can exist physically alone, or two or more units can be integrated in one unit.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • the transceiver unit may include a receiving unit and/or a transmitting unit.
  • Integrated units may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as independent products. Based on this understanding, the integrated unit can be stored in a storage medium as a computer software product, including a number of instructions to cause a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) Execute all or part of the steps of the methods of each embodiment of the application.
  • a computer device which can be a personal computer, a server, or a network device, etc.
  • processor processor
  • this embodiment of the present application also provides a schematic structural diagram of a communication device 1100.
  • the device 1100 can be used to implement the method described in the above method embodiment. Please refer to the description in the above method embodiment.
  • the communication device 1100 can 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 FIGS. 4 to 9 .
  • 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.
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processor can be used to control communication devices (such as base stations, terminals, or chips, etc.), execute software programs, and process data of software programs.
  • the communication device may include a transceiver unit to implement input (reception) and output (transmission) of signals.
  • the transceiver unit can be a transceiver, a radio frequency chip, etc.
  • the device 1100 includes one or more processors 1101, and the one or more processors 1101 can implement the methods in the embodiments shown above.
  • the processor 1101 can also implement other functions.
  • the processor 1101 can execute instructions to cause the device 1100 to perform the method described in the above method embodiment.
  • the instructions may be stored in whole or in part within processor 1101, such as instructions 1103 may be stored in whole or in part in processor 1101, or instructions 1103 may be stored in processor 1101, and instructions 1104 may be stored in memory 1102 coupled to the processor,
  • Processor 1101 can Synchronously executing instructions 1103 and 1104 causes the device 1100 to perform the method described in the above method embodiment. Instructions 1103 and 1104 are also referred to as computer programs.
  • the communication device 1100 may also include a circuit, and the circuit may implement the functions in the foregoing method embodiments.
  • the device 1100 may include one or more memories 1102 on which instructions 1104 are stored.
  • the instructions may be executed on the processor 1101 so that the device 1100 executes the method described in the above method embodiment.
  • the memory 1102 may also store data.
  • Optional processor 1101 may also store instructions and/or data.
  • one or more memories 1102 may store the corresponding relationships described in the above embodiments, or related parameters or tables involved in the above embodiments.
  • the processor and memory can be set up separately or integrated together.
  • the device 1100 may also include a transceiver 1105 and an antenna 1106.
  • the processor 1101 may be called a processing unit and controls a device (terminal or base station).
  • the transceiver 1105 may be called a transceiver, a transceiver circuit, a transceiver unit, etc., and is used to implement the transceiver function of the device through the antenna 1106.
  • the processor can be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of this application. , general processor, digital signal processor (DSP), off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • FPGA off-the-shelf programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module may be stored in a storage medium located in a memory.
  • the memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory.
  • Erase programmable read-only memory Electrically EPROM, EEPROM
  • Volatile memory may be Random Access Memory (RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM Double Data Rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • synchronous link dynamic random access memory synchronous link DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • Embodiments of the present application also provide a computer-readable medium on which a computer program is stored.
  • the computer program is executed by a computer, the business flow routing method of any of the above method embodiments is implemented.
  • Embodiments of the present application also provide a computer program product, which includes a computer program.
  • a computer program When the computer program is executed by a computer, the business flow routing method of any of the above method embodiments is implemented.
  • An embodiment of the present application also provides a communication system, including a second terminal device and a policy control function network element.
  • the second terminal device and the policy control function network element can implement the service flow routing method of any of the above method examples.
  • the communication system also includes a first terminal device.
  • a computer program product includes one or more computer instructions.
  • Computer instructions When computer instructions are loaded and executed on a computer, processes or functions according to embodiments of the present application are generated in whole or in part.
  • the computer may be the communication device described above.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer-readable storage medium may be the above-mentioned storage medium or the above-mentioned memory.
  • the determination unit or processor 1101 may be one or more logic circuits, a sending unit Or the receiving unit or transceiver 1105 may be an input-output interface, also known as a communication interface, or an interface circuit, or an interface, etc. Or the transceiver 1105 can also be a sending unit and a receiving unit.
  • the sending unit can be an output interface, and the receiving unit can be an input interface.
  • the sending unit and the receiving unit are integrated into one unit, such as an input-output interface.
  • the communication device shown in FIG. 12 includes a logic circuit 1201 and an interface circuit 1202 .
  • the above-mentioned processing unit or processor 1101 can be implemented with a logic circuit 1201, and the transceiver unit or transceiver 1105 can be Implemented using interface circuit 1202.
  • the logic circuit 1201 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc.
  • the interface circuit 1202 can be a communication interface, an input/output interface, etc.
  • the logic circuit and the interface circuit may also be coupled to each other. The embodiments of this application do not limit the specific connection methods of the logic circuit and the interface circuit.
  • the logic circuit 1201 and the interface circuit 1202 may be used to perform functions or operations performed by the above-mentioned network functions or control plane functions, etc.
  • the interface circuit 1202 may be used to receive signals from other communication devices other than the communication device 1200 and transmit them to the logic circuit 1201 or to send signals from the logic circuit 1201 to other communication devices other than the communication device 1200 .
  • the logic circuit 1201 may be used to implement any of the above method embodiments by executing code instructions.
  • the interface circuit 1202 is configured to send a second registration message, the second registration message carries second capability information, and the second capability information indicates that the communication device has the PIN network gateway capability.
  • the second registration message carries second capability information
  • the second capability information indicates that the communication device has the PIN network gateway capability.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be an indirect coupling or communication connection through some interfaces, devices or units, or may be electrical, mechanical or other forms of connection.
  • a unit described as a separate component may or may not be physically separate.
  • a component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present application.
  • each functional unit in various embodiments of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • Storage media can be any available media that can be accessed by the computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种业务流路由方法及装置。该方法包括：第一终端设备发送第一注册消息，第一注册消息携带第一能力信息，第一能力信息指示第一终端设备具有PIN网络管理能力；第一终端设备从策略控制功能网元中获取第一PIN网络本地路由规则，第一PIN网络本地路由规则与第一能力信息相关；第一终端设备向第二终端设备发送第一PIN网络本地路由规则。在该方法中，网络侧可以生成第一PIN网络本地路由规则，然后通过具有PIN网络管理能力的第一终端设备发送给第二终端设备，使得第二终端设备可以对业务流执行本地路由，实现业务流在PIN网络架构下的传输，以及在网络侧的控制下实现PIN网络内业务流的本地路由。

Description

一种业务流路由方法及装置
相关申请的交叉引用
本申请要求在2022年08月16日提交中国专利局、申请号为202210980340.X、申请名称为“一种业务流路由方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种业务流路由方法及装置。
背景技术
随着5G核心网络(5G core，5GC)网络功能的不断增强，且终端设备越来越丰富，运营商对个人物联网(internet of things，IoT)网络(personal IoT network，PIN)的管理与控制是下一阶段网络增强的目标。
相关技术中提出了PIN网络的架构，PIN网络中包含PIN网络管理功能设备(PIN element with management capability，PMEC)、PIN网络网关功能设备(PIN element with gateway capability，PEGC)，与其他PIN Element。PEMC和PEGC是具有5GC接入能力的用户设备，其可以通过第三代合作伙伴项目(3rd generation partnership project，3GPP)或非3GPP(non-3GPP)接入技术接入5GC。其他PIN Element是末端设备，例如智能可穿戴设备、智能家居设备等。
但是相关技术中仅提出了PIN网络架构，还未提出PIN网络架构下的通信方案。
发明内容
本申请实施例提供一种业务流路由方法及装置，实现PIN网络架构下的通信流程，以及可以在网络侧的控制下实现PIN网络内业务流的本地路由。
第一方面，提供一种业务流路由方法，包括如下过程：第一终端设备发送第一注册消息，第一注册消息携带第一能力信息，第一能力信息指示第一终端设备具有PIN网络管理能力；第一终端设备从策略控制功能网元中获取第一PIN网络本地路由规则，第一PIN网络本地路由规则与第一能力信息相关；第一终端设备向第二终端设备发送第一PIN网络本地路由规则。
在该方法中，网络侧可以生成第一PIN网络本地路由规则，然后通过具有PIN网络管理能力的第一终端设备发送给第二终端设备，使得第二终端设备可以对业务流执行本地路由，实现业务流在PIN网络架构下的传输，以及在网络侧的控制下实现PIN网络内业务流的本地路由。
在一种可能的实现中，第一PIN网络本地路由规则包括以下信息中的一种或多种：数据网络名称或切片信息，数据网络名称或切片信息指示数据网络名称或切片信息对应的协议数据单元(protocol data unit，PDU)会话中的业务流允许进行本地路由。在该实现中，网络侧以PDU会话为粒度，生成用于实现本地路由的PIN网络本地路由规则，对业务流的路由进行控制。
可选的，第一PIN网络本地路由规则还包括本地路由指示信息，该本地路由指示信息指示数据网络名称或切片信息对应的PDU会话中的业务流允许进行本地路由。
在一种可能的实现中，第一PIN网络本地路由规则包括设备标识列表。在该实现中，设备标识对应的业务流允许进行本地路由，网络侧以业务流为粒度，生成用于实现本地路由的PIN网络本地路由规则，对业务流的路由进行控制。
可选的，第一PIN网络本地路由规则包括本地路由指示信息，该本地路由指示信息指示设备标识列表中的设备标识对应的业务流允许进行本地路由。
第一终端设备还可以接收来自第二终端设备的地址信息与设备标识的对应关系，设备标识为第二终端设备基于设备标识列表确定；第一终端设备根据对应关系，获取第二PIN网络本地路由规则；第一终端设备向第二终端设备发送第二PIN网络本地路由规则。第二终端设备基于本地策略或用户偏好基于确定设备标识，因此第一终端设备获取到的第二PIN网络本地路由规则与第二终端设备的本地策略或用户偏好相关，第二终端设备基于该第二PIN网络本地路由规则，可以对业务流执行本地路由，实现业务流在PIN网络内的本地路由。
在一种可能的实现中，第一终端设备根据对应关系，获取第二PIN网络本地路由规则时，可以向策略控制功能网元发送对应关系，接收来自策略控制功能网元的第二PIN网络本地路由规则。在该实现中，网络侧以业务流为粒度，生成用于实现本地路由的PIN网络本地路由规则，对业务流的路由进行控制。
在一种可能的实现中，第一终端设备根据对应关系，获取第二PIN网络本地路由规则时，可以是第一终端设备根据对应关系，生成第二PIN网络本地路由规则。在该实现中，第一终端设备可以自身生成用于实现本地路由的PIN网络本地路由规则，对业务流的路由进行控制。
在一种可能的实现中，第二PIN网络本地路由规则包括以下信息中的一种或多种：地址信息或设备标识，地址信息或设备标识指示地址信息或设备标识对应的业务流允许进行本地路由。
第二方面，提供一种业务流路由方法，包括如下过程：第二终端设备发送第二注册消息，第二注册消息携带第二能力信息，第二能力信息指示第二终端设备具有PIN网络网关能力；第二终端设备获取第一PIN网络本地路由规则；第二终端设备根据第一PIN网络本地路由规则，对获取到的业务流执行本地路由。
在一种可能的实现中，第二终端设备获取第一PIN网络本地路由规则时，可以从策略控制功能网元中获取第一PIN网络本地路由规则，第一PIN网络本地路由规则与第二能力信息相关；或者可以从第一终端设备中获取第一PIN网络本地路由规则，第一PIN网络本地路由规则与第一能力信息相关，第一能力信息指示第一终端设备具有PIN网络管理能力。在该实现中，第二终端设备可以直接从策略控制功能网元中获取用于本地路由的PIN网络本地路由规则，或者可以通过第一终端设备获取PIN网络本地路由规则，然后对业务流执行本地路由，可以实现业务流在PIN网络架构下的传输，以及实现PIN网络内业务流的本地路由。
在一种可能的实现中，第二终端设备根据第一PIN网络本地路由规则，对获取到的业务流执行本地路由时，若获取到的业务流与第一PIN网络本地路由规则匹配，第二终端设备在第二终端设备所在的PIN网络内，将业务流发送给该业务流的目的终端设备。
在一种可能的实现中，业务流与第一PIN网络本地路由规则匹配，包括以下一个或多个：第一PIN网络本地路由规则中的流描述信息包含业务流中数据包携带的信息；和/或第一PIN网络本地路由规则中的数据网络名称包含业务流对应的PDU会话的数据网络名称；和/或第一PIN网络本地路由规则中的切片信息包含业务流对应的PDU会话的切片信息；和/或业务流中携带的目的地址信息对应的目的终端设备与第二终端设备属于同一PIN网络。
在一种可能的实现中，第一PIN网络本地路由规则中的数据网络名称包括上行业务流对应的PDU会话的数据网络名称，或者下行业务流对应的PDU会话的数据网络名称。
在一种可能的实现中，第一PIN网络本地路由规则中的切片信息包括上行业务流对应的PDU会话的切片信息，或者下行业务流对应的PDU会话的切片信息。
在一种可能的实现中，第一PIN网络本地路由规则包括以下信息中的一种或多种：数据网络名称或切片信息，数据网络名称或切片信息指示数据网络名称或切片信息对应的PDU会话中的业务流允许进行本地路由。
在一种可能的实现中，第一PIN网络本地路由规则包括设备标识列表。
第二终端设备根据第一PIN网络本地路由规则，对获取到的业务流执行本地路由时，可以在设备标识列表中确定设备标识以及设备标识对应的地址信息；向第一终端设备发送地址信息与设备标识的对应关系；从第一终端设备中获取第二PIN网络本地路由规则；若获取到的业务流与第二PIN网络本地路由规则匹配，第二终端设备在第二终端设备所在的PIN网络内，将业务流发送给该业务流的目的终端设备。
在一种可能的实现中，第二终端设备在设备标识列表中确定设备标识时，可以在PIN成员列表中确定一个或多个PIN成员；和/或可以在PIN网关设备列表中确定一个或多个PIN网关设备。
在一种可能的实现中，业务流与第二PIN网络本地路由规则匹配，包括以下一个或多个：第二PIN网络本地路由规则中的流描述信息包含业务流中数据包携带的信息；和/或第二PIN网络本地路由规则中的PIN成员包含业务流对应的PIN成员；和/或第二PIN网络本地路由规则中的PIN成员包含业务流对应的目的终端设备；和/或第二PIN网络本地路由规则中的地址信息包含业务流中的目的地址信息。
在一种可能的实现中，第二PIN网络本地路由规则中的PIN成员包括上行业务流对应的PIN成员 和/或目的终端设备，或者下行业务流对应的PIN成员和/或目的终端设备。
在一种可能的实现中，第二PIN网络本地路由规则包括以下信息中的一种或多种：地址信息或设备标识，地址信息或设备标识指示地址信息或设备标识对应的业务流允许进行本地路由。
第三方面，提供一种业务流路由方法，包括如下过程：策略控制功能网元接收策略获取消息，策略获取消息携带指示信息，指示信息指示第一终端设备具有个人物联网PIN网络管理能力或者第二终端设备具有PIN网络网关能力；策略控制功能网元根据指示信息，确定允许本地路由；策略控制功能网元发送第一PIN网络本地路由规则。
在一种可能的实现中，第一PIN网络本地路由规则包括以下信息中的一种或多种：数据网络名称或切片信息，数据网络名称或切片信息指示数据网络名称或切片信息对应的PDU会话中的业务流允许进行本地路由。
在一种可能的实现中，第一PIN网络本地路由规则包括设备标识列表。
策略控制功能网元还可以接收地址信息与设备标识的对应关系，设备标识为第二终端设备在设备标识列表中确定；策略控制功能网元根据对应关系，生成第二PIN网络本地路由规则；策略控制功能网元向第一终端设备发送第二PIN网络本地路由规则。
在一种可能的实现中，第二PIN网络本地路由规则包括以下信息中的一种或多种：地址信息或设备标识，地址信息或设备标识指示地址信息或设备标识对应的业务流允许进行本地路由。
第四方面，提供一种通信装置，该通信装置可以为第一终端设备或第二终端设备或策略控制功能网元，或者为设置为第一终端设备或第二终端设备或策略控制功能网元中的芯片。该通信装置可以实现上述任一方面所提供的方法。
通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第五方面，提供一种通信装置，包括收发单元。可选地，该通信装置还包括处理单元。该通信装置可以实现任一方面或任一方面中的任一项实现所提供的方法。
第六方面，提供一种通信装置，包括处理器。该处理器可用于执行上述任一方面或任一方面中的任一项实现所提供的方法。可选地，该装置还包括存储器，该处理器与存储器耦合，存储器中用于存储计算机程序或指令，处理器可以执行存储器中的程序或指令，以使得该装置可以执行上述任一方面或任一方面中的任一项实现所提供的方法。
第七方面，提供一种通信装置，该装置包括接口电路和逻辑电路，逻辑电路与接口电路耦合。该接口电路可以为代码/数据读写接口电路，该接口电路用于接收计算机执行指令(计算机执行指令存储在存储器中，可能直接从存储器读取，或可能经过其他器件)并传输至该逻辑电路，以使该逻辑电路运行计算机执行指令以执行上述任一方面或任一方面中的任一项实现所提供的方法。
在一些可能的设计中，该通信装置可以为芯片或芯片系统。
第八方面，提供一种通信装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行上述任一方面或任一方面中的任一项实现所提供的方法。
可选地，该处理器可以为一个或多个，该存储器也可以为一个或多个。可选地，该存储器可以与该处理器集成在一起，或者该存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请对存储器的类型以及存储器与处理器的设置方式不做限定。
该通信装置可以是一个芯片，该处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第九方面，提供一种处理器，包括：输入电路、输出电路和处理电路。该处理电路用于通过该输入电路接收信号，并通过该输出电路发射信号，使得该处理器执行上述任一方面或任一方面中的任一项实现所提供的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请对处理器及各种电路的具体实现方式不做限定。
第十方面，提供一种通信装置，包括：逻辑电路和输入输出接口，该输入输出接口用于与该通信装置之外的模块通信；该逻辑电路用于运行计算机程序或指令以执行上述任一方面的任一项设计所提供的方法。该通信装置可以为上述任一方面中的第一终端设备或第二终端设备或策略控制功能网元，或者包含上述第一终端设备或第二终端设备或策略控制功能网元的装置，或者上述第一终端设备或第二终端设备或策略控制功能网元中包含的装置，比如芯片。
或者，该输入输出接口可以为代码/数据读写接口电路，或通信接口，该输入输出接口用于接收计算机程序或指令(计算机程序或指令存储在存储器中，可能直接从存储器读取，或可能经过其他器件)并传输至该输入输出接口，以使该输入输出接口运行计算机程序或指令以执行上述任一方面的方法。
可选的，该通信装置可以为芯片。
第十一方面，提供一种计算机程序产品，该计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当该计算机程序被运行时，使得计算机执行上述任一方面或任一方面中的任一项实现所提供的方法。
第十二方面，提供一种计算机可读介质，该计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述任一方面或任一方面中的任一项实现所提供的方法。
第十三方面，提供一种芯片系统，该芯片系统包括处理器和接口，用于支持通信装置实现上述任一方面或任一方面中的任一项实现所提供的功能。在一种可能的设计中，芯片系统还包括存储器，用于保存前述通信装置的必要的信息和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十四方面，提供芯片装置，该芯片装置包括输入接口和/或输出接口。该输入接口可以实现上述任一方面或任一方面中的任一项实现所提供的接收功能，该输出接口可以实现上述任一方面或任一方面中的任一项实现所提供的发送功能。
第十五方面，提供一种功能实体，该功能实体用于实现上述任一方面或任一方面中的任一项实现所提供的方法。
第十六方面，提供一种通信系统，包括上述第一方面的第一终端设备、上述第二方面的第二终端设备和上述第三方面的策略控制功能网元。
其中，第二方面至第十六方面中任一实现所带来的技术效果可参见上述第一方面所带来的技术效果，此处不再赘述。
附图说明
图1为一种通信系统的架构示意图；
图2为一种通信系统的架构示意图；
图3为一种PIN网络架构示意图；
图4为本申请实施例提供的一种业务流路由过程示意图；
图5为本申请实施例提供的一种业务流路由过程示意图；
图6为本申请实施例提供的一种业务流路由过程示意图；
图7为本申请实施例提供的一种业务流路由过程示意图；
图8为本申请实施例提供的一种业务流路由过程示意图；
图9为本申请实施例提供的一种业务流路由过程示意图；
图10为本申请实施例提供的一种通信装置的结构示意图；
图11为本申请实施例提供的一种通信装置的结构示意图；
图12为本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请实施例的技术方案可以应用于移动通信系统。例如，移动通信系统可以为第四代(4th Generation，4G)通信系统(例如，长期演进(long term evolution，LTE)系统)，第五代移动通信(5th-generation，5G)通信系统(例如，新无线(new radio，NR)系统)，及未来的移动通信系统如6G等。移动通信系统支持多种接入技术，例如5GC支持多种接入技术，或者5GC与演进分组核心网络(evolved packet core，EPC)融合网络支持多种接入技术。本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
图1为本申请实施例提供的一种网络架构的示意图，包括：用户设备、(无线)接入网设备、用户面网元、数据网络、接入管理网元、会话管理网元、应用网元、统一数据管理网元、策略控制网元和网络开放网元等。下面对该网络架构中涉及的各个网元分别进行说明。
1、用户设备(user equipment，UE)：用户设备也可称为接入终端、终端、终端设备、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、用户代理或用户装置等。该终端可以是一种具有无线收发功能的设备，例如手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端或者未来演进网络中的终端等。
其中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
2、(无线)接入网设备(radio access network，(R)AN)：接入网设备也可以称为接入设备或接入网网元，(R)AN能够管理无线资源，为用户设备提供接入服务，完成用户设备数据在用户设备和核心网之间的转发，(R)AN也可以理解为网络中的基站。
示例的，本申请实施例中的接入网设备可以是用于与用户设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于：演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved NodeB，HeNB，或home node B，HNB)、室内基带处理单元(building base band unit，BBU)、收发点(transmit receive point，TRP)或者传输点(transmission point，TP)等，等，还可以为5G，如NR系统中的下一代基站或下一代节点B(generation node B，gNB)，或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。RRC层的信息由CU生成，最终会经过DU的PHY层封装变成PHY层信息，或者，由PHY层的信息转变而来。因而， 在这种架构下，高层信令如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的接入网设备，也可以将CU划分为核心网(core network，CN)中的接入网设备，本申请对此不做限定。
3、用户面网元(或用户面功能网元)：作为和数据网络的接口，完成用户面数据转发、基于会话/流级的计费统计，带宽限制等功能。即分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。
在5G通信系统中，该用户面网元可以是用户面功能(user plane function，UPF)网元。
4、数据网络：用于提供传输数据的网络。提供例如运营商服务、互联网接入或第三方服务，包含服务器，服务器端实现视频源编码、渲染等。在5G通信系统中，该数据网络可以是数据网络(data network，DN)。
5、接入管理网元(或接入管理功能网元)：主要用于移动性管理和接入管理等。在5G通信系统中，该接入管理网元可以是接入和移动性管理功能(access and mobility management function，AMF)，主要进行移动性管理、接入鉴权/授权等功能。此外，还负责在终端与策略控制功能(policy control function，PCF)网元间传递用户策略。
6、会话管理网元(或会话管理功能网元)：主要用于会话管理、用户设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是会话管理功能(session management function，SMF)网元，完成终端IP地址分配，UPF选择，及计费与QoS策略控制等。
7、应用网元：在5G通信系统中，该应用网元可以是应用功能(application function，AF)网元，表示第三方或运营商的应用功能，是5G网络获取外部应用数据的接口，主要用于传递应用侧对网络侧的需求。
8、统一数据管理网元：负责用户标识、签约数据、鉴权数据的管理、用户的服务网元注册管理。在5G通信系统中，该统一数据管理网元可以是统一数据管理(unified data management，UDM)。
9、策略控制网元：包括用户签约数据管理功能、策略控制功能、计费策略控制功能、QoS控制等，用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
在5G通信系统中，该策略控制网元可以是PCF。
10、网络开放网元(或网络开放功能)：在5G通信系统中，该网络开放网元可以是网络开放功能(network element function，NEF)网元，主要用于向AF暴露3GPP网络功能的业务和能力，同时也可以让AF向3GPP网络功能提供信息。
可选的，网络架构中包括的网元可以比上述示出的网元更多或更少，例如上述网络架构还可以包括鉴权服务器，负责对用户设备进行鉴权，确定用户设备的合法性，在5G通信系统中，鉴权服务器可以是鉴权服务器功能(authentication server function，AUSF)网元。
上述网络架构支持3GPP定义的无线接入技术(radio access technology，RAT)接入核心网络(core network，CN)，3GPP定义的RAT包括长期演进(long term evolution，LTE)，5G RAN等。上述网络架构还支持非3GPP(non-3GPP，N3G或N3GPP)接入技术通过non-3GPP转换功能(non-3GPP interworking function，N3IWF)或下一代接入网关(next generation packet data gateway，ngPDG)接入核心网络。
当5GC支持non-3GPP接入时，则5G网络架构如图2所示，包括本地公共陆地移动网络(home public land mobile network，HPLMN)和non-3GPP网络。UE可以在HPLMN中通过3GPP接入方式接入5GC，以及可以通过非可信non-3GPP接入(untrusted non-3GPP access)方式接入5GC。其中N3IWF为non-3GPP接入网关。non-3GPP接入网例如可以包括非可信无线局域网(wireless local area network，WLAN)接入网，N3IWF设备例如可以包括路由器等。
需要说明的是，5G核心网络还支持可信的non-3GPP接入和/或有线网络接入。可信的non-3GPP接入网络例如可以包括可信的WLAN网络，有线网络例如可以包括固定家庭网络接入(以下简称固网) 等。当5G核心网络支持可信的non-3GPP接入时，其5G网络架构与图2类似。可将图2中的非可信的non-3GPP接入替换为可信的non-3GPP接入，以及将N3IWF替换为可信的non-3GPP接入网关(trusted non-3GPP gateway function，TNGF)。当5G核心网络支持有线网络接入时，其5G网络架构与图2类似。可将图2中的非可信的non-3GPP接入替换为有线网络接入，以及将N3IWF替换为有线网络接入网关(wireline access gateway function，W-AGF)。UE与接入网关之间的接入网设备可以包括WLAN接入点(access point，AP)，固定接入网设备(fixed access network，FAN)，交换机，路由器等。
可见，non-3GPP接入技术包括可信的WLAN接入、非可信的WLAN接入、或有线网络接入等接入技术。而无论是可信的non-3GPP接入还是非可信的non-3GPP接入，核心网络可以采用图1所示的3GPP接入核心网络架构以及服务接口，或者可以采用图2所示的网络架构以及点对点接口协议。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如云平台)上实例化的虚拟化功能。上述网元或功能可划分出一个或多个服务，进一步，还可能会出现独立于网络功能存在的服务。在本申请中，上述功能网元的实例、或上述功能网元中包括的服务的实例、或独立于网络功能存在的服务实例均可称为服务实例。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
随着5GC网络功能的不断增强，且终端设备越来越丰富。运营商网络对PIN网络的管理与控制成为下一阶段网络增强的目标。一种PIN网络架构如图3所示，包括PEMC和PEGC。PIN网络中还可以包括PIN Element，PIN Element也称为PIN成员，可以是除PEMC和PEGC之外的其他UE，如图3中所示的UE和/或N3GPP设备(device)。
PEMC和PEGC是具有5GC接入能力的用户设备，可以通过3GPP接入技术或non-3GPP接入技术接入5GC。PEGC和PEMC之间基于PC5接口建立连接。PEMC是PIN网络中的管理节点，具有5GC接入能力，可以独立接入5GC。PEGC是PIN网络中的网关节点，PEGC也具有5GC接入能力，因此也可以独立接入并注册5GC。通常PIN网络中的所有PIN成员都与PEGC建立连接，PIN成员可以基于无线保真(wireless fidelity，Wi-Fi)或蓝牙等non-3GPP接入技术进行接入。
PIN Element节点可以是具有5GC接入能力的末端设备，也可以是不具备5GC接入能力的末端设备，后文简称为末端设备。末端设备可以归属于第三方服务提供商，例如智能可穿戴设备，智能家居设备等。
本申请实施例提供了一种业务流路由方法，可以实现PIN网络架构下的通信流程，以及可以在网络侧的控制下实现PIN网络内业务流的本地路由。
图4为本申请实施例提供的一种业务流路由方法示意图。该方法包括以下步骤：
S401：第二终端设备发送第二注册消息，相应的，第二接入管理功能网元接收第二注册消息。其中，第二注册消息携带第二能力信息，第二能力信息指示第二终端设备具有PIN网络网关能力。示例的，第二终端设备为PEGC。第二管理功能网元是为第二终端设备提供接入管理功能的网元，例如第二管理功能网元是服务PEGC的AMF。
S402：第二终端设备获取第一PIN网络本地路由规则。
S403：第二终端设备根据第一PIN网络本地路由规则，对获取到的业务流执行本地路由。
基于上述方案，具有PIN网络网关能力的第二终端设备可以根据获取到的第一PIN网络本地路由规则，对业务流执行本地路由，业务流在PIN网络架构下的传输，以及可以实现PIN网络内业务流的本地路由。
上述S402中，第二终端设备可以通过如下两个示例获取第一PIN网络本地路由规则：
示例1：第二终端设备从第一终端设备获取第一PIN网络本地路由规则。
示例2：第二终端设备从策略控制功能网元获取第一PIN网络本地路由规则。
在该示例1中，第一PIN网络本地路由规则与第一能力信息相关。第一能力信息指示第一终端设备具有PIN网络管理能力。示例的，第一终端设备为PEMC。
可选地，第一终端设备可以从策略控制功能网元获取第一PIN网络本地路由规则。一个可能的实 现方式如图5所示，包括如下步骤：
S501：第一终端设备发送第一注册消息，相应的，第一接入管理功能网元接收第一注册消息。其中，第一注册消息携带第一能力信息，第一能力信息指示第一终端设备具有PIN网络管理能力。第一接入管理功能网元是为第一终端设备提供接入管理功能的网元，例如第一接入管理功能网元是服务PEMC的AMF。第一接入管理功能网元和第二接入管理功能网元可以部署在同一物理网元中，或者可以部署在不同的物理网元中。
S502：第一终端设备从策略控制功能网元获取第一PIN网络本地路由规则。
可选地，第一接入管理功能网元可以向策略控制功能网元发送策略获取消息，该策略获取消息携带指示信息，指示信息指示第一终端设备具有PIN网络管理能力。相应的，策略控制功能网元根据该指示信息，确定允许本地路由，发送第一PIN网络本地路由规则。例如策略控制功能网元根据第一终端设备具有PIN网络管理能力，确定第一终端设备需要在PIN网络中进行数据传输，PIN网络内通常存在可以进行本地路由的业务，例如，基于业务特征(例如互联网(internet)业务、数据包传输业务等)确定允许本地路由的业务，因此策略控制功能网元可以确定允许本地路由。策略控制功能网元中保存有不同业务对应的是否允许进行本地路由的策略，因此策略控制功能网元可以将该策略的相关信息携带在第一PIN网络本地路由规则中。
S503：第一终端设备向第二终端设备发送第一PIN网络本地路由规则。
在该示例2中，第一PIN网络本地路由规则与第二能力信息相关。
可选地，第二接入管理功能网元可以向策略控制功能网元发送策略获取消息，该策略获取消息携带指示信息，指示信息指示第二终端设备具有PIN网络网关能力。相应的，策略控制功能网元根据该指示信息，确定允许本地路由，发送第一PIN网络本地路由规则。例如策略控制功能网元根据第二终端设备具有PIN网络网关能力，确定第二终端设备需要在PIN网络中进行数据传输，PIN网络内通常存在可以进行本地路由的业务，例如，基于业务特征(例如internet业务、数据包传输业务等)确定允许本地路由的业务，因此策略控制功能网元可以确定允许本地路由。策略控制功能网元中保存有不同业务对应的是否允许进行本地路由的策略，因此策略控制功能网元可以将该策略的相关信息携带在第一PIN网络本地路由规则中。
本地路由指业务流通过PIN网络内的终端传输(如通过PEGC传输，或者在两个终端设备之间直接传输)，而不经过运营商网络中的节点(如5G网络中的RAN或UPF网元)传输。一般而言，针对每种业务，策略控制网元可以决策该业务是否允许进行本地路由。对于PIN网络内业务的数据，例如但不限于家庭网络内的数据共享(如手机画面投屏到电视)或家电控制(如通过手机调节空调温度)等，这些业务不通过运营商网络中的节点也可以实现传输，那么策略控制功能网元可以将这类业务决策为允许进行本地路由。对于互联网内业务的数据，例如但不限于网际互连协议(internet protocol，IP)多媒体子系统(IP multimedia subsystem，IMS)语音，或视频通话业务等，这类业务通过运营商网络中的节点保证业务流的服务质量或执行计费，从而才能实现双方的语音通信或视频通话，那么策略控制功能网元可以将这类业务决策为不允许进行本地路由。
根据实际实现的需要，上述实施例中的第一PIN网络本地路由规则中可以包含不同的信息。下面结合可能的实现方式1和实现方式2予以说明。
可能的实现方式1：上述的第一PIN网络本地路由规则可以包括数据网络名称(data network name，DNN)和/或切片信息(slice info)。数据网络名称指示该数据网络名称对应的PDU会话中的业务流允许进行本地路由。切片信息指示该切片信息对应的PDU会话中的业务流允许进行本地路由。
可选的，上述第一PIN网络本地路由规则除了包含DNN和slice info外，还可以包括本地路由指示信息，本地路由指示信息指示数据网络名称或切片信息对应的PDU会话中的业务流允许进行本地路由。
具体的，上述S403包括若获取到的业务流与第一PIN网络本地路由规则匹配，第二终端设备在第二终端设备所在的PIN网络内，将该业务流发送给业务流的目的终端设备。其中，第二终端设备获取到的业务流，可以是第二终端设备接收到的其他终端设备(如末端设备)发送的业务流，或者可以是第二终端设备生成的业务流。
其中，业务流与第一PIN网络本地路由规则匹配，包括以下一个或多个情况：
情况1.1：第一PIN网络本地路由规则中的流描述信息包含业务流中数据包携带的信息。
流描述信息包括五元组中的至少一个，五元组的信息包括源IP地址、目的IP地址、源端口号、目 的端口号、或协议类型中的至少一个。对于终端设备发出的上行业务流，源IP地址为发出上行业务流的终端设备的IP地址，源端口号为发出上行业务流的终端设备的端口号。对于终端设备接收的下行业务流，目的IP地址为接收下行业务流的终端设备的IP地址，目的端口号为接收下行业务流的终端设备的端口号。
示例的，流描述信息可以是五元组、三元组或四元组等。例如，第一PIN网络本地路由规则中的五元组包含业务流中数据包携带的五元组，即业务流中数据包携带的五元组为第一PIN网络本地路由规则中的五元组的子集，表示该业务流属于允许本地路由的业务流。
或者，流描述信息包括源MAC地址，或目的MAC地址中的至少一个。对于终端设备发出的上行业务流，源MAC地址为发出上行业务流的终端设备的MAC地址。对于终端设备接收的下行业务流，目的MAC地址为接收下行业务流的终端设备的MAC地址。
情况1.2：第一PIN网络本地路由规则中的数据网络名称包含业务流对应的PDU会话的数据网络名称。
第一PIN网络本地路由规则中的数据网络名称包括上行业务流对应的PDU会话的数据网络名称，和/或下行业务流对应的PDU会话的数据网络名称。其中，业务流对应的PDU会话指业务流所属的PDU会话。数据网络名称为PDU会话的属性之一，数据网络名称用于确定该PDU会话对应的业务流是否允许本地路由。
情况1.3：第一PIN网络本地路由规则中的切片信息包含业务流对应的PDU会话的切片信息。
第一PIN网络本地路由规则中的切片信息包括上行业务流对应的PDU会话的切片信息，和/或下行业务流对应的PDU会话的切片信息。其中，切片信息为PDU会话的属性之一，切片信息用于确定该PDU会话对应的业务流是否允许本地路由。示例的，切片信息可以包括网络切片选择辅助信息(network slice selection assistance information，NSSAI)，或单个NSSAI(single-NSSAI，S-NSSAI)。
情况1.4：业务流中携带的目的地址信息对应的目的终端设备与第二终端设备属于同一PIN网络。
若目的终端设备与第二终端设备属于同一PIN网络，表示业务流不经过运营商网络中的节点就可以被目的终端设备接收，因此该业务流可以允许本地路由。
以一个示例说明上述几种情况，在上述S403中，第二终端设备确定获取到的业务流对应的PDU会话，例如，根据接收到的业务流中的源IP地址确定业务流对应的PDU会话。
a)如果此PDU会话的业务流允许本地路由，即此PDU会话对应的DNN或切片信息属于PIN网络本地路由规则中包含的DNN或切片信息，则第二终端设备基于接收到的业务流中的目的IP地址查找目的终端设备。
i)当目的IP地址对应的目的终端设备与第二终端设备属于同一PIN网络时，若此目的IP地
址对应的PDU会话也允许本地路由(源IP地址对应的PDU会话和目的IP地址对应的PDU会话
属于不同PDU会话，即，这两个PDU会话均允许本地路由；若源IP地址对应的PDU会话和目的
IP地址对应的PDU会话属于相同PDU会话，上述已知该PDU会话允许本地路由)，则第二终端
设备将上述业务流数据包直接发送给上述目的终端设备，无需经过运营商网络中的节点，如5GC，
即第二终端设备执行本地路由。
若，此目标IP地址对应的PDU会话不允许本地路由，则第二终端设备将上述业务流数据通过
PDU会话发送给5GC，即第二终端设备不执行不本地路由。
ii)否则，即此目的IP地址对应的目的设备与第二终端设备不属于相同PIN网络，则第二终
端设备将业务流数据包通过PDU会话发送给5GC，即第二终端设备不执行本地路由。
b)如果此PDU会话的业务流不允许本地路由，即此PDU会话的DNN或切片信息不属于PIN网络本地路由规则包含的DNN(s)或切片信息，则第二终端设备将上述业务流数据包通过PDU会话发送给5GC，即第二终端设备不执行本地路由。
上述举例中，第二终端设备先通过获取到的业务流的源IP地址确定是否可以本地路由，然后在基于该判断结果的基础上进一步做判断。实际实现中，也可以不限于该先后顺序，而是根据实际需要灵活安排。比如，当业务流对应的目的设备与第二终端设备属于同一PIN网络时，第二终端设备分别判断源IP地址对应的PDU会话和目的IP地址对应的PDU会话是否支持本地路由，在源IP地址对应的PDU会话和目的IP地址对应的PDU会话都支持本地路由时，执行本地路由。
可能的实现方式2：上述的第一PIN网络本地路由规则可以包括设备标识列表，其中设备标识列表中的设备标识对应的业务流允许进行本地路由。设备标识可以包括但不限于MAC地址、IP地址、设备名称等。设备标识可以用于标识PIN成员和/或PEGC。可选的，该第一PIN网络本地路由规则除了包含设备标识列表外，还可以包括本地路由指示信息，本地路由指示信息指示设备标识列表中的设备标识对应的业务流允许进行本地路由。
一个示例中，上述S403中，若获取到的业务流与该第一PIN网络本地路由规则中的设备标识列表匹配，第二终端设备对获取到的业务流进行本地路由，即第二终端设备在第二终端设备所在的PIN网络内，将该业务流发送给该业务流的目的终端设备。其中，业务流与第一PIN网络本地路由规则中的该设备标识列表匹配，是指第一PIN网络本地路由规则中的设备标识列表包含该业务流对应的设备标识。
另一个示例中，在上述S403中，第二终端设备根据第一PIN网络本地路由规则，结合本地策略和/或用户偏好，对获取到的业务流进行本地路由。也就是说，已经被允许本地路由的范围中，进一步根据第二终端设备的本地策略和/用户偏好进行限定，可以提升用户控制感，优化用户体验。
例如，第二终端设备根据本地策略和/或用户偏好，在上述设备标识列表中，确定设备标识以及设备标识对应的地址信息，向第一终端设备发送该地址信息与该设备标识的对应关系，第一终端设备根据该对应关系，获取第二PIN网络本地路由规则，然后向第二终端设备发送第二PIN网络本地路由规则，若获取到的业务流与第二PIN网络本地路由规则匹配，第二终端设备在第二终端设备所在的PIN网络内，将业务流发送给业务流的目的终端设备。
这里考虑到地址信息为IP地址的情况，由于IP地址通常是随机分配的，在通信过程中可能会发生改变(即，同一个设备在两次通信过程中可能被分配到了不同的IP地址)。如果第二终端设备仅上报IP地址，则第二PIN网络本地路由规则也仅能根据该上报的IP地址确定，若终端的IP地址发生了变化，就会导致第二终端设备根据第二PIN网络本地路由规则中的IP地址所定位到的设备，和业务流实际所对应的设备不同，导致业务流本地路由出错。
而设备标识是设备的签约信息，在通信过程中固定不变。如果第二终端设备上报对应关系，则第二PIN网络本地路由规则根据该对应关系确定。若第二PIN网络本地路由规则包括设备标识，则第二终端设备可以根据业务流对应的设备标识与第二PIN网络本地路由规则中的设备标识进行匹配，从而决策是否允许本地路由。若第二PIN网络本地路由规则包括IP地址，则第二终端设备可以根据业务流中的IP地址与第二PIN网络本地路由规则中的IP地址进行匹配，从而决策是否允许本地路由(在终端的IP地址发生变化的情况下，由于第一终端设备具有PIN网络管理能力，因此第一终端设备可以获取到该终端的IP地址发生了变化，若第二PIN网络本地路由规则由策略控制功能网元生成，则第一终端设备可以将该终端的IP地址进行上报，策略控制功能网元对第二PIN网络本地路由规则中的IP地址进行更新，然后将更新后的第二PIN网络本地路由规则下发给第二终端设备)。若第二PIN网络本地路由规则包括设备标识和IP地址，则第二终端设备根据业务流中的IP地址与第二PIN网络本地路由规则中的IP地址进行匹配，从而决策是否允许本地路由，由于业务流数据包的包头携带IP地址，因此在保证准确进行业务流本地路由的基础上，可以提高第二终端设备的决策效率。也就是说，第二终端设备通过上报地址信息与设备标识的对应关系，可以保证更准确地进行业务流的本地路由。
示例的，第二终端设备在设备标识列表中确定设备标识时，可以在PIN成员列表中确定一个或多个PIN成员，和/或在PIN网关设备列表中确定一个或多个PIN网关设备。其中，与第二终端设备确定的一个或多个PIN网关设备所对应的终端设备均允许进行本地路由，与PIN网关设备所对应的终端设备指能够与PIN网关设备通信的终端设备，即发往该终端设备的业务流通过PIN网关设备进行转发。可选的，第二终端设备确定的一个或多个PIN网关设备可以包括该第二终端设备本身，也可以包括除第二终端设备外的其它PIN网关设备。
一种可能的实现中，第一终端设备根据对应关系，获取第二PIN网络本地路由规则可以是：向策略控制功能网元发送对应关系，策略控制功能网元根据该对应关系，生成第二PIN网络本地路由规则，然后向第一终端设备发送该第二PIN网络本地路由规则。具体的，策略控制功能网元确定该对应关系中的设备标识允许进行本地路由，则在生成第二PIN网络本地路由规则中包括允许本地路由的设备标识所对应的地址信息。
另一种可能的实现中，第一终端设备根据对应关系，获取第二PIN网络本地路由规则可以是：第 一终端设备根据该对应关系，生成第二PIN网络本地路由规则。具体的，第一终端设备确定该对应关系中的设备标识允许进行本地路由，则在生成第二PIN网络本地路由规则中包括该对应关系中的地址信息。
通过上述方式获取的第二PIN网络本地路由规则包括地址信息。地址信息指示该地址信息对应的业务流允许进行本地路由。可选的，上述第二PIN网络本地路由规则中，也可以包括设备标识。其中，设备标识指示该设备标识对应的业务流允许进行本地路由。在上述S403中，若获取到的业务流与该第二PIN网络本地路由规则匹配，第二终端设备对获取到的业务流进行本地路由。
其中，业务流与第二PIN网络本地路由规则匹配，包括以下一个或多个情况：
情况2.1：第二PIN网络本地路由规则中的流描述信息包含业务流中数据包携带的信息。
该情况2.1与上述情况1.1相似，在此不赘述。
情况2.2：第二PIN网络本地路由规则中的PIN成员包含业务流对应的PIN成员。
第二PIN网络本地路由规则中的业务流对应的PIN成员包括上行业务流对应的PIN成员，和/或下行业务流对应的PIN成员。上行业务流对应的PIN成员为发出该上行业务流的成员，下行业务流对应的PIN成员为接收该下行业务流的PIN成员。其中，PIN成员通过设备标识进行唯一标识。
情况2.3：第二PIN网络本地路由规则中的PIN成员包含业务流对应的目的终端设备。
第二PIN网络本地路由规则中的业务流对应的目的终端设备指接收该业务流的终端设备，例如目的终端设备可以通过业务流中的目的IP地址确定，或者通过该目的IP地址对应的设备标识确定。
情况2.4：第二PIN网络本地路由规则中的地址信息包含业务流中的目的地址信息。
该情况表示业务流中的目的地址信息属于第二PIN网络本地路由规则中的地址信息，表示该业务流属于允许本地路由的业务流。
本申请实施例中涉及的“PDU会话”可以为支持一种或多种接入技术的PDU会话。接入技术可以是但不限于是以下接入类型中的一个或多个：3GPP接入，non-3GPP接入，LTE接入，5GRAN接入，可信non-3GPP接入，非可信non-3GPP接入，无线局域网(wireless local area network，WLAN)接入，可信WLAN接入，非可信WLAN接入，有线网络接入(固网接入)，可信Wi-Fi接入，或非可信Wi-Fi接入等。一个PDU会话包括一个或多个QoS流。
本申请实施例中涉及的“业务流”包括业务数据流(service data flow，SDF)、IP数据流、以太数据流(或以太流)或至少一个QoS流。一个QoS流包括一个或多个SDF。一个SDF包括一个或多个IP流，或者包括一个或多个以太流。一个SDF中的IP数据包或以太数据包对应相同的业务数据流描述信息。一个IP流包括一个或多个IP数据包，一个IP流中的IP数据包具有相同的IP五元组信息。一个以太流包括一个或多个以太数据包，一个以太流中的以太数据包具有相同的以太流描述信息。该以太流描述信息包括源MAC地址或目的MAC地址中的至少一个。本申请实施例中，业务数据包包括IP数据包或以太数据包等。
基于图4～图5所示的实施例，下面以具体的实施例图6～图9对本申请实施例提供的业务流路由方法进行说明。其中图6～图9和图4～图5中的步骤之间可以相互引用，术语概念也可以相互引用。
图6为一种业务流路由过程的示意图，包括如下步骤：
S601：PEMC注册到网络。
具体的，UE1注册到网络，并作为PEMC创建PIN网络。
S602：服务PEMC的AMF从PCF或PIN网络功能(network function，NF)中获取第一PIN网络本地路由规则，第一PIN网络本地路由规则包括DNN信息和/或切片(slice)信息，以及可选的本地路由指示信息。
如果第一PIN网络本地路由规则包括本地路由指示信息，本地路由指示信息指示DNN信息和/或切片信息对应的PDU会话中的业务流允许进行本地路由。如果第一PIN网络本地路由规则不包括本地路由指示信息，DNN信息和/或切片信息本身指示DNN信息和/或切片信息对应的PDU会话中的业务流允许进行本地路由。DNN信息可以是一个DNN或多个DNN(s)的信息。
其中，服务PEMC的AMF指为PEMC提供接入管理服务的AMF。
S603：服务PEMC的AMF向PEMC发送第一PIN网络本地路由规则。相应的，PEMC接收该第一PIN网络本地路由规则。第一PIN网络本地路由规则的相关描述可以参见上述实施例，此处不再赘 述。
S604：PEGC注册到网络。
其中S604与S601～S603的先后顺序不做限定。
S605：PEGC与PEMC建立连接，PEMC向PEGC发送该第一PIN网络本地路由规则。
S606：PEGC建立PDU会话。
其中，服务PEGC的SMF为PEGC提供会话管理服务。
S605和S606的先后顺序不做限定。
S607：PEGC根据第一PIN网络本地路由规则，对获取到的业务流执行本地路由。
在该实施例中，网络侧向PEMC发送PIN网络本地路由规则，由PEMC将PIN网络本地路由规则发送给PEGC，再由PEGC实现PIN网络内业务流的本地路由。
实际实现中，PEMC也可以建立PDU会话，由服务PEGC的SMF为该PEMC提供会话管理服务，上述图6中未示出PEMC建立PDU会话的步骤。
图7为一种业务流路由过程的示意图，包括如下步骤：
S701的过程参见上述S601。
S702的过程参见上述S604。
S703：服务PEGC的AMF从PCF或PIN NF中获取第一PIN网络本地路由规则，第一PIN网络本地路由规则包括DNN信息和/或切片(slice)信息，以及可选的本地路由指示信息。
其中，服务PEGC的AMF是指为PEGC提供接入管理服务的AMF。
S704：服务PEGC的AMF向PEGC发送第一PIN网络本地路由规则。相应的，PEGC接收该第一PIN网络本地路由规则。
S705～S706的过程参见上述S606～S607。
在该实施例中，网络侧向PEGC发送PIN网络本地路由规则，由PEGC实现PIN网络内业务流的本地路由。
图8为一种业务流路由过程示意图，包括如下步骤：
S801的过程参见上述S601。
S802：服务PEMC的AMF从PCF或PIN NF中获取第一PIN网络本地路由规则，第一PIN网络本地路由规则包括PIN成员标识列表和/或PEGC标识列表，以及可选的本地路由指示信息。
其中，PIN成员标识用于在PIN网络中唯一标识一个UE。PEGC成员标识用于唯一标识一个PEGC。服务PEMC的AMF是指为PEMC提供接入管理服务的AMF。
S803：PEGC注册到网络中，建立PDU会话。
S804：服务PEMC的AMF向PEMC发送第一PIN网络本地路由规则。相应的，PEMC接收到该第一PIN网络本地路由规则后，向PEGC发送第一PIN网络本地路由规则。
PEGC接收到上述第一PIN网络本地路由规则之后，可以有两种不同的实现方式，方式一：参考S805。方式二：参考S806～809。
S805：PEGC根据第一PIN网络本地路由规则，对获取到的业务流执行本地路由。
当业务流中数据包携带的目的IP地址或目的MAC地址属于第一PIN网络本地路由规则包含的PIN成员列表时，或者，当目的IP地址或目的MAC地址对应的目的终端设备属于第一PIN网络本地路由规则包含的PIN成员列表时，或者，目的IP地址或目的MAC地址对应的目的终端设备所在的PEGC属于第一PIN网络本地路由规则包含的PEGC列表时，PEGC对业务流执行本地路由。其中目的终端设备所在的PEGC指发往目的终端设备的业务流通过该PEGC进行转发。
S806：PEGC在PIN成员标识列表和/或PEGC标识列表选择设备标识，将设备标识和设备标识对应的IP地址发送给PEMC。
设备标识包括PIN成员标识和/或PEGC标识，换言之，PEGC可以在PIN成员标识列表选择PIN成员标识，和/或在PEGC标识列表选择PEGC标识。
S807：PEMC存储该设备标识和IP地址的对应关系，基于该对应关系生成第二PIN网络本地路由规则。第二PIN网络本地路由规则的相关描述可以参见上述实施例，此处不再赘述。
S808：PEMC向PEGC发送第二PIN网络本地路由规则。
S809：PEGC根据第二PIN网络本地路由规则，对获取到的业务流执行本地路由。
示例的，当目的IP地址包含第二PIN网络本地路由规则中时，PEGC对业务流执行本地路由。在该实施例中，网络侧向PEMC发送第一PIN网络本地路由规则，PEMC生成第二PIN网络本地路由规则，由PEGC实现PIN网络内业务流的本地路由。
上述的实施例中，以第一PIN网络本地路由规则，第一PIN网络本地路由规则包括PIN成员标识列表和/或PEGC标识列表为例。在一个可替代的方案中，第一PIN网络本地路由规则也可以不包括PIN成员标识列表和PEGC标识列表。在这种情况下，PEGC可以根据本地策略和/或用户偏好，确定PIN成员标识和/或PEGC标识，然后对获取到的业务流执行本地路由。PIN成员标识和/或PEGC标识可以用于决策哪些PIN成员和/或PEGC允许进行本地路由。
上述的实施例中，以服务PEMC的AMF获取第一PIN网络本地路由规则为例进行说明。在一个可替代的方案中，服务PEGC的AMF可以从PCF或PIN NF中获取第一PIN网络本地路由规则，服务PEGC的AMF将第一PIN网络本地路由规则向PEGC发送第一PIN网络本地路由规则，该方案可以参见图7中的S703～S704。
图9为一种业务流路由过程的示意图，包括如下步骤：
S901～S904的过程参见上述S801～S804。
PEGC接收到上述第一PIN网络本地路由规则之后，可以有两种不同的实现方式，方式一：参考S905。方式二：参考S906～910。
S905的过程参见上述S805。
S906的过程参见上述S806。
S907：PEMC向PCF或PIN NF发送该设备标识和IP地址的对应关系。
S908：PCF或PIN NF向PEMC发送第二PIN网络本地路由规则。
PCF或PIN网元基于该对应关系，生成第二PIN网络本地路由规则。
S909～S910的过程参见上述S808～S809。
在该实施例中，网络侧向PEMC发送第一PIN网络本地路由规则，PEMC生成第二PIN网络本地路由规则，PEMC向PEGC发送第二PIN网络本地路由规则，由PEGC实现PIN网络内业务流的本地路由。
图6～图9所示的实施例中，以服务PEMC的AMF/SMF，和服务PEGC的AMF/SMF的部署在不同物理网元为例。实际实现中，服务PEMC的AMF/SMF，和服务PEGC的AMF/SMF可以部署在同一物理网元，或者服务PEMC的AMF和SMF也可以部署在不同的物理网元，或者服务PEGC的AMF和SMF也可以部署在不同的物理网元。
值得说明的是，上述各实施例之间可以单独使用，也可以结合使用。
本申请实施例中的术语“系统”和“网络”可被互换使用。本申请实施例的描述中，“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。本申请中所涉及的至少一个是指一个或多个；多个，是指两个或两个以上。另外，需要理解的是，在本申请的描述中，“第一”、“第二”、“第三”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。在本说明书中描述的参考“一个实施例”或“一些实施例”等意味着在本申请的一个或多个实施例中包括结合该实施例描述的特定特征、结构或特点。由此，在本说明书中的不同之处出现的语句“在一个实施例中”、“在一些实施例中”、“在其他一些实施例中”、“在另外一些实施例中”等不是必然都参考相同的实施例，而是意味着“一个或多个但不是所有的实施例”，除非是以其他方式另外特别强调。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其他方式另外特别强调。方法和装置是基于相同或相似技术构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
基于与上述业务流路由方法的同一技术构思，本申请实施例还提供一种通信装置，如图10所示，通信装置1000包括处理单元1001和收发单元1002。可选的收发单元1002所实现的功能可以由通信接 口完成，收发单元可以包括接收单元和/或发送单元。装置1000可以应用于第一终端设备或第二终端设备或策略控制功能网元，或者位于第一终端设备或第二终端设备或策略控制功能网元中。通信装置1000可以用于实现上述方法实施例中描述的方法，例如通信装置1000能够执行上述图4～图9的方法中由第一终端设备或第二终端设备或策略控制功能网元执行的各个步骤。
在一个可能的实施例中，装置1000应用于第一终端设备。
例如，处理单元1001，用于生成第一注册消息，第一注册消息携带第一能力信息，第一能力信息指示通信装置具有PIN网络管理能力；
收发单元1002，用于发送第一注册消息；从策略控制功能网元中获取第一PIN网络本地路由规则，第一PIN网络本地路由规则与第一能力信息相关；以及向第二终端设备发送第一PIN网络本地路由规则。
在一个实现方式中，第一PIN网络本地路由规则包括以下信息中的一种或多种：数据网络名称或切片信息，数据网络名称或切片信息指示数据网络名称或切片信息对应的PDU会话中的业务流允许进行本地路由。
在一个实现方式中，第一PIN网络本地路由规则包括设备标识列表。
收发单元1002，还用于接收来自第二终端设备的地址信息与设备标识的对应关系，设备标识为第二终端设备基于设备标识列表确定；根据对应关系，获取第二PIN网络本地路由规则；向第二终端设备发送第二PIN网络本地路由规则。
在一个实现方式中，收发单元1002，具体用于向策略控制功能网元发送对应关系，接收来自策略控制功能网元的第二PIN网络本地路由规则。
在一个实现方式中，处理单元1001，还用于根据对应关系，生成第二PIN网络本地路由规则。
在一个实现方式中，第二PIN网络本地路由规则包括以下信息中的一种或多种：地址信息或设备标识，地址信息或设备标识指示地址信息或设备标识对应的业务流允许进行本地路由。
在一个可能的实施例中，装置1000应用于第二终端设备。
例如，处理单元1001，用于发送第二注册消息，第二注册消息携带第二能力信息，第二能力信息指示通信装置具有个人物联网PIN网络网关能力；
收发单元1002，用于发送第二注册消息；获取第一PIN网络本地路由规则；以及根据第一PIN网络本地路由规则，对获取到的业务流执行本地路由。
在一个实现方式中，收发单元1002，具体用于从策略控制功能网元中获取第一PIN网络本地路由规则，第一PIN网络本地路由规则与第二能力信息相关；或者从第一终端设备中获取第一PIN网络本地路由规则，第一PIN网络本地路由规则与第一能力信息相关，第一能力信息指示第一终端设备具有PIN网络管理能力。
在一个实现方式中，收发单元1002，具体用于若获取到的业务流与第一PIN网络本地路由规则匹配，在第二终端设备所在的PIN网络内，将业务流发送给该业务流的目的终端设备。
在一个实现方式中，业务流与第一PIN网络本地路由规则匹配，包括以下一个或多个：第一PIN网络本地路由规则中的流描述信息包含业务流中数据包携带的信息；第一PIN网络本地路由规则中的数据网络名称包含业务流对应的PDU会话的数据网络名称；第一PIN网络本地路由规则中的切片信息包含业务流对应的PDU会话的切片信息；业务流中携带的目的地址信息对应的目的终端设备与第二终端设备属于同一PIN网络。
在一个实现方式中，第一PIN网络本地路由规则中的数据网络名称包括上行业务流对应的PDU会话的数据网络名称，或者下行业务流对应的PDU会话的数据网络名称；和/或第一PIN网络本地路由规则中的切片信息包括上行业务流对应的PDU会话的切片信息，或者下行业务流对应的PDU会话的切片信息。
在一个实现方式中，第一PIN网络本地路由规则包括以下信息中的一种或多种：数据网络名称或切片信息，数据网络名称或切片信息指示数据网络名称或切片信息对应的PDU会话中的业务流允许进行本地路由。
在一个实现方式中，第一PIN网络本地路由规则包括设备标识列表。
处理单元1001，还用于在设备标识列表中确定设备标识以及设备标识对应的地址信息；
收发单元1002，具体用于向第一终端设备发送地址信息与设备标识的对应关系；从第一终端设备 中获取第二PIN网络本地路由规则；若获取到的业务流与第二PIN网络本地路由规则匹配，在第二终端设备所在的PIN网络内，将业务流发送给该业务流的目的终端设备。
在一个实现方式中，处理单元1001，具体用于在PIN成员列表中确定一个或多个PIN成员；和/或在PIN网关设备列表中确定一个或多个PIN网关设备。
在一个实现方式中，业务流与第二PIN网络本地路由规则匹配，包括以下一个或多个：第二PIN网络本地路由规则中的流描述信息包含业务流中数据包携带的信息；第二PIN网络本地路由规则中的PIN成员包含业务流对应的PIN成员；第二PIN网络本地路由规则中的PIN成员包含业务流对应的目的终端设备；第二PIN网络本地路由规则中的地址信息包含业务流中的目的地址信息。
在一个实现方式中，第二PIN网络本地路由规则中的PIN成员包括上行业务流对应的PIN成员和/或目的终端设备，或者下行业务流对应的PIN成员和/或目的终端设备。
在一个实现方式中，第二PIN网络本地路由规则包括以下信息中的一种或多种：地址信息或设备标识，地址信息或设备标识指示地址信息或设备标识对应的业务流允许进行本地路由。
在一个可能的实施例中，装置1000应用于策略控制功能网元。
例如，收发单元1002，用于接收策略获取消息，策略获取消息携带指示信息，指示信息指示第一终端设备具有个人物联网PIN网络管理能力或者第二终端设备具有PIN网络网关能力；
处理单元1001，用于根据指示信息，确定允许本地路由；
收发单元1002，还用于发送第一PIN网络本地路由规则。
在一个实现方式中，第一PIN网络本地路由规则包括以下信息中的一种或多种：数据网络名称或切片信息，数据网络名称或切片信息指示数据网络名称或切片信息对应的PDU会话中的业务流允许进行本地路由。
在一个实现方式中，第一PIN网络本地路由规则包括设备标识列表。
收发单元1002，还用于接收地址信息与设备标识的对应关系，设备标识为第二终端设备在设备标识列表中确定；
处理单元1001，还用于根据对应关系，生成第二PIN网络本地路由规则；
收发单元1002，还用于向第一终端设备发送第二PIN网络本地路由规则。
在一个实现方式中，第二PIN网络本地路由规则包括以下信息中的一种或多种：地址信息或设备标识，地址信息或设备标识指示地址信息或设备标识对应的业务流允许进行本地路由。
需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。例如收发单元可以包括接收单元和/或发送单元。
集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，该集成的单元可以作为计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例方法的全部或部分步骤。
如图11所示，本申请实施例还提供了一种通信装置1100的结构示意图。装置1100可用于实现上述方法实施例中描述的方法，可以参见上述方法实施例中的说明。例如通信装置1100能够执行上述图4～图9的方法中由第一终端设备或第二终端设备或策略控制功能网元执行的各个步骤。
装置1100包括一个或多个处理器1101。处理器1101可以是通用处理器或者专用处理器等。例如可以是基带处理器、或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、终端、或芯片等)进行控制，执行软件程序，处理软件程序的数据。通信装置可以包括收发单元，用以实现信号的输入(接收)和输出(发送)。例如，收发单元可以为收发器，射频芯片等。
装置1100包括一个或多个处理器1101，一个或多个处理器1101可实现上述所示的实施例中的方法。可选的，处理器1101除了实现上述所示的实施例的方法，还可以实现其他功能。
一种设计中，处理器1101可以执行指令，使得装置1100执行上述方法实施例中描述的方法。指令可以全部或部分存储在处理器1101内，如指令1103可以全部或部分存储在处理器1101中，或者指令1103存储在处理器1101中，以及指令1104存储在与处理器耦合的存储器1102中，处理器1101可以 同步执行指令1103和指令1104使得装置1100执行上述方法实施例中描述的方法。指令1103和指令1104也称为计算机程序。
在又一种可能的设计中，通信装置1100还可以包括电路，电路可以实现前述方法实施例中的功能。
在又一种可能的设计中装置1100中可以包括一个或多个存储器1102，其上存有指令1104，指令可在处理器1101上被运行，使得装置1100执行上述方法实施例中描述的方法。可选的，存储器1102中还可以存储有数据。可选的处理器1101中也可以存储指令和/或数据。例如，一个或多个存储器1102可以存储上述实施例中所描述的对应关系，或者上述实施例中所涉及的相关的参数或表格等。处理器和存储器可以单独设置，也可以集成在一起。
在又一种可能的设计中，装置1100还可以包括收发器1105以及天线1106。处理器1101可以称为处理单元，对装置(终端或者基站)进行控制。收发器1105可以称为收发机、收发电路、或者收发单元等，用于通过天线1106实现装置的收发功能。
处理器可以是一个通用中央处理器(central processing unit，CPU)、微处理器、特定应用集成电路(application-specific integrated circuit，ASIC)、一个或多个用于控制本申请方案程序执行的集成电路、通用处理器、数字信号处理器(digital signal processor，DSP)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以存储介质中，该存储介质位于存储器。
存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchronous link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。存储器可以是独立存在，通过通信线路与处理器相连接。存储器也可以和处理器集成在一起。
本申请实施例还提供了一种计算机可读介质，其上存储有计算机程序，该计算机程序被计算机执行时实现上述任一方法实施例的业务流路由方法。
本申请实施例还提供了一种计算机程序产品，包括计算机程序，该计算机程序被计算机执行时实现上述任一方法实施例的业务流路由方法。
本申请实施例还提供了一种通信系统，包括第二终端设备和策略控制功能网元。其中第二终端设备和策略控制功能网元可以实现上述任一方法实例的业务流路由方法。
可选的，通信系统还包括第一终端设备。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是上述通信装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输。计算机可读存储介质可以是上述存储介质或上述存储器。
在一种可能的设计中，当上述通信装置是芯片，如网络设备中的芯片时，或者，如终端设备中的芯片时，确定单元或者处理器1101可以是一个或多个逻辑电路，发送单元或者接收单元或者收发器1105可以是输入输出接口，又或者称为通信接口，或者接口电路，或接口等等。或者收发器1105还可以是发送单元和接收单元，发送单元可以是输出接口，接收单元可以是输入接口，该发送单元和接收单元集成于一个单元，例如输入输出接口。如图12所示，图12所示的通信装置包括逻辑电路1201和接口电路1202。即上述处理单元或者处理器1101可以用逻辑电路1201实现，收发单元或者收发器1105可以 用接口电路1202实现。其中，该逻辑电路1201可以为芯片、处理电路、集成电路或片上系统(system on chip，SoC)芯片等，接口电路1202可以为通信接口、输入输出接口等。本申请实施例中，逻辑电路和接口电路还可以相互耦合。对于逻辑电路和接口电路的具体连接方式，本申请实施例不作限定。
在本申请的一些实施例中，该逻辑电路1201和接口电路1202可用于执行上述网络功能或控制面功能执行的功能或操作等。接口电路1202可以用于接收来自通信装置1200之外的其它通信装置的信号并传输至逻辑电路1201或将来自逻辑电路1201的信号发送给通信装置1200之外的其它通信装置。逻辑电路1201可以通过执行代码指令用于实现上述任一方法实施例。
示例性地，接口电路1202用于发送第二注册消息，第二注册消息携带第二能力信息，第二能力信息指示通信装置具有PIN网络网关能力。通信装置执行的功能或操作可以参照前述方法实施例，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。
总之，以上仅为本申请技术方案的实施例而已，并非用于限定本申请的保护范围。凡在本申请的原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (31)

  1. 一种业务流路由方法，其特征在于，所述方法包括：
    第一终端设备发送第一注册消息，所述第一注册消息携带第一能力信息，所述第一能力信息指示所述第一终端设备具有个人物联网PIN网络管理能力；
    所述第一终端设备从策略控制功能网元获取第一PIN网络本地路由规则，所述第一PIN网络本地路由规则与所述第一能力信息相关；
    所述第一终端设备向第二终端设备发送所述第一PIN网络本地路由规则。
  2. 如权利要求1所述的方法，其特征在于，所述第一PIN网络本地路由规则包括以下信息中的一种或多种：数据网络名称或切片信息，其中，所述数据网络名称或切片信息指示所述数据网络名称，或，所述切片信息对应的协议数据单元PDU会话中的业务流允许进行本地路由。
  3. 如权利要求1所述的方法，其特征在于，所述第一PIN网络本地路由规则包括设备标识列表；
    所述方法还包括：
    所述第一终端设备接收来自所述第二终端设备的地址信息与设备标识的对应关系，所述设备标识为所述第二终端设备基于所述设备标识列表确定；
    所述第一终端设备根据所述对应关系，获取第二PIN网络本地路由规则；
    所述第一终端设备向所述第二终端设备发送所述第二PIN网络本地路由规则。
  4. 如权利要求3所述的方法，其特征在于，所述第一终端设备根据所述对应关系，获取第二PIN网络本地路由规则，包括：
    所述第一终端设备向所述策略控制功能网元发送所述对应关系，接收来自所述策略控制功能网元的所述第二PIN网络本地路由规则。
  5. 如权利要求3所述的方法，其特征在于，所述第一终端设备根据所述对应关系，获取第二PIN网络本地路由规则，包括：
    所述第一终端设备根据所述对应关系，生成所述第二PIN网络本地路由规则。
  6. 如权利要求3-5任一项所述的方法，其特征在于，所述第二PIN网络本地路由规则包括以下信息中的一种或多种：所述地址信息或所述设备标识，其中，所述地址信息或所述设备标识指示所述地址信息，或，所述设备标识对应的业务流允许进行本地路由。
  7. 一种业务流路由方法，其特征在于，所述方法包括：
    第二终端设备发送第二注册消息，所述第二注册消息携带第二能力信息，所述第二能力信息指示所述第二终端设备具有个人物联网PIN网络网关能力；
    所述第二终端设备获取第一PIN网络本地路由规则；
    所述第二终端设备根据所述第一PIN网络本地路由规则，对获取到的业务流执行本地路由。
  8. 如权利要求7所述的方法，其特征在于，所述第二终端设备获取第一PIN网络本地路由规则，包括：
    所述第二终端设备从策略控制功能网元获取所述第一PIN网络本地路由规则，所述第一PIN网络本地路由规则与所述第二能力信息相关；或者
    所述第二终端设备从第一终端设备获取所述第一PIN网络本地路由规则，所述第一PIN网络本地路由规则与第一能力信息相关，所述第一能力信息指示所述第一终端设备具有PIN网络管理能力。
  9. 如权利要求7或8所述的方法，其特征在于，所述第二终端设备根据所述第一PIN网络本地路由规则，对获取到的业务流执行本地路由，包括：
    若获取到的业务流与所述第一PIN网络本地路由规则匹配，所述第二终端设备在所述第二终端设备所在的PIN网络内，将所述业务流发送给所述业务流的目的终端设备。
  10. 如权利要求9所述的方法，其特征在于，所述业务流与所述第一PIN网络本地路由规则匹配，包括以下一个或多个：
    所述第一PIN网络本地路由规则中的流描述信息包含所述业务流中数据包携带的信息；
    所述第一PIN网络本地路由规则中的数据网络名称包含所述业务流对应的协议数据单元PDU会话的数据网络名称；
    所述第一PIN网络本地路由规则中的切片信息包含所述业务流对应的PDU会话的切片信息；
    所述业务流中携带的目的地址信息对应的所述目的终端设备与所述第二终端设备属于同一PIN网络。
  11. 如权利要求10所述的方法，其特征在于，所述第一PIN网络本地路由规则中的数据网络名称包括上行业务流对应的PDU会话的数据网络名称，或者下行业务流对应的PDU会话的数据网络名称；和/或
    所述第一PIN网络本地路由规则中的切片信息包括上行业务流对应的PDU会话的切片信息，或者下行业务流对应的PDU会话的切片信息。
  12. 如权利要求9-11任一项所述的方法，其特征在于，所述第一PIN网络本地路由规则包括以下信息中的一种或多种：数据网络名称或切片信息，其中，所述数据网络名称或切片信息指示所述数据网络名称，或，所述切片信息对应的PDU会话中的业务流允许进行本地路由。
  13. 如权利要求7或8所述的方法，其特征在于，所述第一PIN网络本地路由规则包括设备标识列表；
    所述第二终端设备根据所述第一PIN网络本地路由规则，对获取到的业务流执行本地路由，包括：
    所述第二终端设备在所述设备标识列表中确定设备标识以及所述设备标识对应的地址信息；
    所述第二终端设备向第一终端设备发送所述地址信息与所述设备标识的对应关系；
    所述第二终端设备从所述第一终端设备获取第二PIN网络本地路由规则；
    若获取到的业务流与所述第二PIN网络本地路由规则匹配，所述第二终端设备在所述第二终端设备所在的PIN网络内，将所述业务流发送给所述业务流的目的终端设备。
  14. 如权利要求13所述的方法，其特征在于，所述第二终端设备在所述设备标识列表中确定设备标识，包括：
    所述第二终端设备在PIN成员列表中确定一个或多个PIN成员；和/或
    所述第二终端设备在PIN网关设备列表中确定一个或多个PIN网关设备。
  15. 如权利要求13或14所述的方法，其特征在于，所述业务流与所述第二PIN网络本地路由规则匹配，包括以下一个或多个：
    所述第二PIN网络本地路由规则中的流描述信息包含所述业务流中数据包携带的信息；
    所述第二PIN网络本地路由规则中的PIN成员包含所述业务流对应的PIN成员；
    所述第二PIN网络本地路由规则中的PIN成员包含所述业务流对应的目的终端设备；
    所述第二PIN网络本地路由规则中的地址信息包含所述业务流中的目的地址信息。
  16. 如权利要求15所述的方法，其特征在于，所述第二PIN网络本地路由规则中的PIN成员包括上行业务流对应的PIN成员和/或目的终端设备，或者下行业务流对应的PIN成员和/或目的终端设备。
  17. 如权利要求13-16任一项所述的方法，其特征在于，所述第二PIN网络本地路由规则包括以下信息中的一种或多种：所述地址信息或所述设备标识，其中，所述地址信息或所述设备标识指示所述地址信息，或，所述设备标识对应的业务流允许进行本地路由。
  18. 一种业务流路由方法，其特征在于，所述方法包括：
    策略控制功能网元接收策略获取消息，所述策略获取消息携带指示信息，所述指示信息指示第一终端设备具有个人物联网PIN网络管理能力或者第二终端设备具有PIN网络网关能力；
    所述策略控制功能网元根据所述指示信息，确定允许本地路由；
    所述策略控制功能网元发送第一PIN网络本地路由规则。
  19. 如权利要求18所述的方法，其特征在于，所述第一PIN网络本地路由规则包括以下信息中的一种或多种：数据网络名称或切片信息，其中，所述数据网络名称或切片信息指示所述数据网络名称，或，所述切片信息对应的协议数据单元PDU会话中的业务流允许进行本地路由。
  20. 如权利要求18所述的方法，其特征在于，所述第一PIN网络本地路由规则包括设备标识列表；
    所述方法还包括：
    所述策略控制功能网元接收地址信息与设备标识的对应关系，所述设备标识为所述第二终端设备在所述设备标识列表中确定；
    所述策略控制功能网元根据所述对应关系，生成第二PIN网络本地路由规则；
    所述策略控制功能网元向所述第一终端设备发送所述第二PIN网络本地路由规则。
  21. 如权利要求20所述的方法，其特征在于，所述第二PIN网络本地路由规则包括以下信息中的一 种或多种：所述地址信息或所述设备标识，其中，所述地址信息或所述设备标识指示所述地址信息，或，所述设备标识对应的业务流允许进行本地路由。
  22. 一种通信装置，其特征在于，包括：
    处理单元，用于生成第一注册消息，所述第一注册消息携带第一能力信息，所述第一能力信息指示所述通信装置具有个人物联网PIN网络管理能力；
    收发单元，用于发送所述第一注册消息；从策略控制功能网元获取第一PIN网络本地路由规则，所述第一PIN网络本地路由规则与所述第一能力信息相关；以及向第二终端设备发送所述第一PIN网络本地路由规则。
  23. 一种通信装置，其特征在于，包括：
    处理单元，用于发送第二注册消息，所述第二注册消息携带第二能力信息，所述第二能力信息指示所述通信装置具有个人物联网PIN网络网关能力；
    收发单元，用于发送所述第二注册消息；获取第一PIN网络本地路由规则；以及根据所述第一PIN网络本地路由规则，对获取到的业务流执行本地路由。
  24. 一种通信装置，其特征在于，包括：
    收发单元，用于接收策略获取消息，所述策略获取消息携带指示信息，所述指示信息指示第一终端设备具有个人物联网PIN网络管理能力或者第二终端设备具有PIN网络网关能力；
    处理单元，用于根据所述指示信息，确定允许本地路由；
    所述收发单元，还用于发送第一PIN网络本地路由规则。
  25. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器与所述存储器耦合；
    所述存储器存储有计算机程序或指令；
    所述处理器，用于执行所述存储器中的计算机程序或指令，以使得所述装置执行如权利要求1-21中任一项所述的方法。
  26. 一种通信装置，其特征在于，包括逻辑电路和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述逻辑电路或将来自所述逻辑电路的信号发送给所述通信装置之外的其它通信装置，所述逻辑电路通过执行代码指令用于实现如权利要求1-21中任一项所述的方法。
  27. 一种计算机可读存储介质，其特征在于，包括计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得如权利要求1-21中任一项所述的方法被执行。
  28. 一种计算机程序产品，其特征在于，包括计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得如权利要求1-21中任一项所述的方法被执行。
  29. 一种通信系统，其特征在于，包括用于执行上述权利要求7-17任一项所述方法的第二终端设备，以及用于执行上述权利要求18-21任一项所述方法的策略控制功能网元。
  30. 如权利要求29所述的系统，其特征在于，所述系统还包括用于执行上述权利要求1-6任一项所述方法的第一终端设备。
  31. 一种芯片系统，其特征在于，所述芯片系统包括：
    处理器和存储器，所述处理器与所述存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，实现如权利要求1-21任一项所述的方法。
PCT/CN2023/106911 2022-08-16 2023-07-12 一种业务流路由方法及装置 WO2024037256A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210980340.X 2022-08-16
CN202210980340.XA CN117641320A (zh) 2022-08-16 2022-08-16 一种业务流路由方法及装置

Publications (1)

Publication Number Publication Date
WO2024037256A1 true WO2024037256A1 (zh) 2024-02-22

Family

ID=89940662

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/106911 WO2024037256A1 (zh) 2022-08-16 2023-07-12 一种业务流路由方法及装置

Country Status (2)

Country Link
CN (1) CN117641320A (zh)
WO (1) WO2024037256A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200045546A1 (en) * 2017-11-03 2020-02-06 Huawei Technologies Co., Ltd. Internet of Things Communication Method, Apparatus, and System
CN111770545A (zh) * 2019-04-02 2020-10-13 华为技术有限公司 一种业务流路由控制方法、装置及系统
US20210368341A1 (en) * 2020-08-10 2021-11-25 Ching-Yu LIAO Secure access for 5g iot devices and services
WO2022159725A1 (en) * 2021-01-25 2022-07-28 Intel Corporation Federated identity management in fifth generation (5g) system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200045546A1 (en) * 2017-11-03 2020-02-06 Huawei Technologies Co., Ltd. Internet of Things Communication Method, Apparatus, and System
CN111770545A (zh) * 2019-04-02 2020-10-13 华为技术有限公司 一种业务流路由控制方法、装置及系统
US20210368341A1 (en) * 2020-08-10 2021-11-25 Ching-Yu LIAO Secure access for 5g iot devices and services
WO2022159725A1 (en) * 2021-01-25 2022-07-28 Intel Corporation Federated identity management in fifth generation (5g) system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
FUTUREWEI, PHILIPS: "New Use case for FS_PIN: dynamic creation of an on-demand 5G PIN Non-Public-network at home", 3GPP DRAFT; S1-210121, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG1, no. e-Meeting; 20200201, 15 March 2021 (2021-03-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051986251 *

Also Published As

Publication number Publication date
CN117641320A (zh) 2024-03-01

Similar Documents

Publication Publication Date Title
US11722947B2 (en) Apparatus and method for routing data packet to user equipment in LTE-WLAN aggregation system
US20230023571A1 (en) Service processing method for proximity service, device, and system
WO2020108003A1 (zh) 一种用户接入控制方法、信息发送方法及装置
US11811670B2 (en) Packet delay parameter obtaining method, system, and apparatus
WO2020019764A1 (zh) 信息传输方法、设备及计算机可读存储介质
WO2021057794A1 (zh) 配置业务的方法、通信装置和通信系统
KR102469973B1 (ko) 통신 방법 및 장치
CN112636884B (zh) 一种消息传输方法和装置
US20230254922A1 (en) Multipath transmission method and communication apparatus
WO2021238882A1 (zh) 一种实现业务连续性的方法及装置
AU2021308253A1 (en) Communication method and communication apparatus
WO2021058029A1 (zh) 一种控制业务流传输的方法、装置及系统
WO2021115429A1 (zh) 一种通信方法及装置
WO2023284551A1 (zh) 通信方法、装置和系统
WO2024037256A1 (zh) 一种业务流路由方法及装置
US11259205B2 (en) IP multimedia core network subsystem signaling in 5GS
WO2020142884A1 (zh) 切换传输路径的方法及装置
WO2023061207A1 (zh) 一种通信方法、通信装置及通信系统
WO2022222748A1 (zh) 中继通信方法和装置
WO2024078258A1 (zh) 一种路径建立方法及装置
WO2023071866A1 (zh) 指示信息的传输方法、消息传输方法及相关装置
WO2023273880A1 (zh) 传输方式切换的方法和相关装置
WO2022171043A1 (zh) 过滤规则配置和数据传输方法及相关装置
WO2023213156A1 (zh) 通信方法、通信装置及通信系统
WO2023143212A1 (zh) 一种通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23854161

Country of ref document: EP

Kind code of ref document: A1