WO2019062754A1 - 一种通信方法、装置及系统 - Google Patents

一种通信方法、装置及系统 Download PDF

Info

Publication number
WO2019062754A1
WO2019062754A1 PCT/CN2018/107580 CN2018107580W WO2019062754A1 WO 2019062754 A1 WO2019062754 A1 WO 2019062754A1 CN 2018107580 W CN2018107580 W CN 2018107580W WO 2019062754 A1 WO2019062754 A1 WO 2019062754A1
Authority
WO
WIPO (PCT)
Prior art keywords
function entity
terminal
user plane
entity
session management
Prior art date
Application number
PCT/CN2018/107580
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 华为技术有限公司
Priority to BR112020006069-0A priority Critical patent/BR112020006069A2/pt
Priority to EP18861939.9A priority patent/EP3675531B1/en
Priority to EP23199575.4A priority patent/EP4336886A3/en
Publication of WO2019062754A1 publication Critical patent/WO2019062754A1/zh
Priority to US16/824,267 priority patent/US11564284B2/en
Priority to US18/153,928 priority patent/US20230171848A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/46—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for vehicle-to-vehicle communication [V2V]

Definitions

  • the present application relates to the field of mobile communications technologies, and in particular, to a communication method, apparatus, and system.
  • One of the development goals of mobile communication is to establish a wide-ranging interconnection network including various types of terminals, which is one of the starting points for the development of the Internet of Things within the framework of cellular communication.
  • the Internet of Things enables terminals in a terminal group composed of a plurality of terminals to communicate with each other.
  • the general application is more than communication between terminals through the 3rd Generation Partnership Project (3GPP) network.
  • 3GPP 3rd Generation Partnership Project
  • communication between terminals in a terminal group requires a relatively high latency.
  • communication between vehicles within a fleet of vehicles consists of very high latency requirements for communication.
  • the present application provides a communication method, apparatus, and system for reducing communication delay between terminals in a terminal group.
  • the present application provides a communication method that can be performed by a chip within a session management function entity or a session management function entity.
  • the session management function entity may be an SMF entity in 5G communication, and may be another entity having session management function in future communication.
  • the communication method includes: the first session management function entity determines, according to the terminal group information, a user plane function entity accessed by the terminal in the terminal group.
  • the first session management function entity determines a target user plane function entity according to the user plane function entity, and the target user plane function entity is used for communication between terminals in the terminal group.
  • the method redirects the terminal in the terminal group to the same user plane function entity, that is, the target user plane function entity, and realizes the communication between the terminals in the terminal group locally at the target user plane function entity, shortening the communication Path, which reduces communication latency.
  • the first session management function entity determines the target user plane function entity according to the user plane function entity, including: the first session management function entity accesses from the terminal according to one or more of the following factors:
  • the user plane function entity or other user plane function entity selects the target user plane function entity: the service scope of each user plane function entity in the user plane function entity accessed by the terminal, the location of the terminal in the terminal group, and the terminal access The number of terminals in the terminal group served by each user plane function entity in the user plane function entity, and the load of each user plane function entity in the user plane function entity accessed by the terminal.
  • the method considers a plurality of factors comprehensively, and can implement a user plane functional entity with better selection as a user plane functional entity, which is beneficial to improving communication quality.
  • the first session management function entity sends a first notification message to the target user plane function entity, where the first notification message includes tunnel information of the first terminal, and the user plane function entity accessed by the first terminal is different from Target user plane functional entity.
  • the method is used to update the tunnel information of the target user plane function entity, so as to facilitate local communication at the target user plane function entity.
  • the first session management function entity sends a second notification message to the base station accessed by the first terminal, where the second notification message includes tunnel information of the target user plane function entity.
  • the first session management function entity releases the resources of the user plane function entity accessed by the first terminal.
  • the first session management function entity receives first indication information from the policy control function entity, where the first indication information is used to indicate that the first session management function entity selects a terminal for communication in the terminal group.
  • User plane functional entity
  • the first session management function entity receives second indication information from the policy control function entity, and the second indication information is used to indicate that the first session management function entity selects the second terminal in the terminal group.
  • a user plane function entity that performs communication, and the second terminal is a terminal corresponding to the first session management function entity in the terminal group.
  • the first session management function entity determines the target user plane function entity according to the user plane function entity, and the first session management function entity determines the target user plane function entity according to the user plane function entity accessed by the second terminal.
  • the first session management function entity receives a first request message from the target network element, where the first request message is used to request the first session management function entity to select a third terminal in the terminal group to communicate.
  • the user plane function entity, and the third terminal is a terminal corresponding to the target network element in the terminal group.
  • the first session management function entity determines a target user plane function entity, and a user plane function entity that communicates with the third terminal.
  • the target network element is a second session management function entity or an access and mobility management function entity.
  • the previously determined target user plane function entity is used as the target user plane function entity of the terminal corresponding to the target network element, and the target user plane function does not need to be re-selected. Entity helps save money.
  • the first request message includes tunnel information of the base station accessed by the third terminal, and tunnel information of the user plane function entity accessed by the third terminal.
  • the first session management function entity receives a second request message from the target network element, and the second request message is used to request the first session management function entity to select a third terminal in the terminal group to communicate.
  • the user plane function entity, and the third terminal is a terminal corresponding to the target network element in the terminal group.
  • the first session management function entity determines the target user plane function entity according to the user plane function entity, and the first session management function entity determines the target user plane function entity according to the user plane function entity accessed by the second terminal, and the second terminal is A terminal corresponding to the first session management function entity in the terminal group.
  • the target network element is a second session management function entity or an AMF entity.
  • the second request message includes tunnel information of the base station accessed by the third terminal, and tunnel information of the user plane function entity accessed by the third terminal.
  • the first session management function entity receives terminal group information from a control plane functional entity or an application server.
  • the terminal group information includes an identifier of the terminal group and an identifier of the terminal in the terminal group.
  • the first session management function entity stores the identifiers of the target user plane function entity and the terminal group to the context of the terminal in the terminal group, and the context of the terminal in the terminal group is used by the first session management function entity from the terminal group
  • the context of the terminal in the terminal acquires the target user plane function entity; or the first session management function entity locally stores the correspondence between the target user plane function entity and the identifier of the terminal group, and the correspondence relationship is used for the first session management function entity
  • the method stores the determined target user plane function entity to the context of the terminal or stores it locally in the session management function entity, thereby facilitating acquisition of the target user plane function entity.
  • the present application provides a communication method that can be performed by a chip within a policy control function entity or a policy control function entity.
  • the policy control function entity may be a PCF entity in 5G, and may be other entities with policy control functions in future communications.
  • the communication method includes: the policy control function entity acquires terminal group information, and the terminal group information includes at least the identifier of the terminal in the terminal group.
  • the policy control function entity determines the first session management function entity according to the identifier of the terminal in the terminal group, the first session management function entity is used to select the target user plane function entity, and the target user plane function entity is used for the terminal in the terminal group. Communication between.
  • the policy control function entity determines the first session management function entity according to the identifier of the terminal in the terminal group, and the policy control function entity determines the terminal group according to the identifier of the terminal in the terminal group.
  • the session management function entity of the terminal access within.
  • the policy control function entity determines the first session management function entity according to the session management function entity accessed by the terminal.
  • the policy control function entity determines the first session management function entity according to the session management function entity accessed by the terminal, including: the policy control function entity is configured according to the session management function entity corresponding to the terminal in the terminal group. The number of terminals in the terminal group served by each session management function entity determines the first session management function entity.
  • the policy control function entity acquires the terminal group information, including: the policy control function entity receives the terminal group information from the control plane function entity or the application server.
  • the policy control function entity sends first indication information to the first session management function entity, where the first indication information is used to indicate that the first session management function entity selects a terminal for communication in the terminal group.
  • the first indication information is used to indicate that the first session management function entity selects a terminal for communication in the terminal group.
  • User face function entity
  • the policy control function entity sends the second indication information to the first session management function entity, where the second indication information is used to indicate that the first session management function entity selects to use the second terminal in the terminal group.
  • the user plane function entity of the communication, and the second terminal is a terminal corresponding to the first session management function entity in the terminal group.
  • the policy control function entity sends a notification message to the target network element, where the notification message includes terminal group information, address information of the first session management function entity, and the notification message is used to indicate that the target network element will be the first session.
  • the management function entity inserts a session to the third terminal within the terminal group, and instructs the first session management function entity to select a user plane function entity for communication by the third terminal.
  • the target network element is a second session management function entity or an AMF entity
  • the third terminal is a terminal corresponding to the target network element in the terminal group.
  • the application provides an apparatus.
  • the application provides a device, which may be a session management function entity or a chip in a session management function entity.
  • the device has the functionality to implement the various embodiments of the first aspect described above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the session management function entity comprises: a processing unit and a communication unit
  • the processing unit may be, for example, a processor
  • the communication unit may be, for example, a transceiver.
  • the transceiver includes a radio frequency circuit.
  • the session management function entity further includes a storage unit, which may be, for example, a memory.
  • the storage unit stores a computer execution instruction
  • the processing unit is connected to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit, so that the session management function entity performs the above The communication method of any of the first aspects.
  • the chip when the device is a chip within a session management function entity, the chip comprises: a processing unit and a communication unit, which may be, for example, a processor, which may be, for example, an input/ Output interface, pin or circuit.
  • the processing unit may execute computer execution instructions stored by the storage unit to cause the communication method of any of the above aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the session management function entity, such as a read-only Read-only memory (ROM), other types of static storage devices that can store static information and instructions, random access memory (RAM), and the like.
  • ROM read-only Read-only memory
  • RAM random access memory
  • the processor mentioned in any of the above may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more An integrated circuit for controlling program execution of the communication method of the above first aspect.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the application provides an apparatus.
  • the application provides a device, which may be a policy control function entity or a chip in a policy control function entity.
  • the device has the functionality to implement the various embodiments of the second aspect described above.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the policy control function entity comprises: a processing unit and a communication unit
  • the processing unit may be, for example, a processor
  • the communication unit may be, for example, a transceiver.
  • the transceiver includes a radio frequency circuit.
  • the policy control function entity further includes a storage unit, which may be, for example, a memory.
  • the terminal includes a storage unit
  • the storage unit stores a computer execution instruction
  • the processing unit is coupled to the storage unit, and the processing unit executes a computer execution instruction stored by the storage unit to cause the policy control function entity to perform the second aspect Any one of the communication methods.
  • the chip when the device is a chip within a policy control function entity, the chip comprises: a processing unit and a communication unit, which may be, for example, a processor, which may be, for example, an input/ Output interface, pin or circuit.
  • the processing unit may execute computer execution instructions stored by the storage unit to cause the communication method of any of the above second aspects to be performed.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit outside the chip, such as a ROM, in the policy control function entity.
  • Other types of static storage devices, RAM, etc. that can store static information and instructions.
  • the processor mentioned in any of the above may be a general-purpose CPU, a microprocessor, an ASIC, or an integrated circuit of one or more programs for controlling the communication method of the above second aspect.
  • the present application also provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the above aspects.
  • the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • FIG. 1(a) is a schematic diagram of a communication system provided by the present application.
  • FIG. 1(b) is a schematic diagram of a possible network architecture provided by the present application.
  • FIG. 2 is a schematic diagram of a communication method provided by the present application.
  • FIG. 3 is a schematic diagram of a UPF and an SMF of a terminal in a terminal group provided by the present application;
  • FIG. 4 is another schematic diagram of a UPF and an SMF of a terminal in a terminal group provided by the present application;
  • FIG. 5 is another schematic diagram of a UPF and an SMF of a terminal in a terminal group provided by the present application;
  • FIG. 6 is a schematic diagram of a network architecture to which Embodiment 1 applies;
  • FIG. 7 is a schematic diagram of a communication method according to an embodiment of the present application.
  • FIG. 8(a) is a schematic diagram of a network architecture to which Embodiment 2 applies;
  • FIG. 8(b) is another schematic diagram of a network architecture to which Embodiment 2 applies;
  • FIG. 9 is a schematic diagram of a communication method according to an embodiment of the present application.
  • FIG. 10(a) is a schematic diagram of a network architecture to which Embodiment 3 applies;
  • FIG. 10(b) is another schematic diagram of a network architecture to which Embodiment 3 applies;
  • FIG. 11(a) is a schematic diagram of a network architecture to which Embodiment 4 applies;
  • 11(b) is another schematic diagram of a network architecture to which Embodiment 4 applies;
  • FIG. 12 is a schematic diagram of a communication method according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a device according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a device according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of a device according to an embodiment of the present application.
  • FIG. 1(a) is a schematic diagram of a communication system provided by the present application.
  • the communication system includes a user plane functional entity and a session management functional entity.
  • it further includes one or all of an access and mobility management function entity and a policy control function entity.
  • the user plane function entity in the figure may be one or more, and the session management function entity may be one or more.
  • the session management function entity may be one or more.
  • each of the figures is schematically illustrated as an example.
  • the target user plane function entity in the user plane function entity is used for communication between terminals in the terminal group.
  • the session management function entity is configured to determine, according to the terminal group information, a user plane function entity accessed by the terminal in the terminal group. And, according to the user plane function entity, the target user plane function entity is determined.
  • the session management function entity further selects a target user plane function entity from the user plane function entity accessed by the terminal or other user plane function entity according to one or more of the following factors: the terminal access user The service range of each user plane function entity in the polygon function entity and the location of the terminal in the terminal group, the number of terminals in the terminal group served by each user plane function entity in the user plane function entity accessed by the terminal, and the terminal The load of each user plane functional entity in the accessed user plane functional entity.
  • the session management function entity further sends a first notification message to the target user plane function entity, where the first notification message includes tunnel information of the first terminal, and the user plane function entity accessed by the first terminal is different from the target user. Face function entity.
  • the session management function entity sends a second notification message to the base station accessed by the first terminal, where the second notification message includes tunnel information of the target user plane function entity.
  • the policy control function entity is configured to acquire terminal group information, where the terminal group information includes at least an identifier of the terminal in the terminal group. Determining, according to the identifier of the terminal in the terminal group, the first session management function entity, where the first session management function entity is configured to select a target user plane function entity, where the target user plane function entity is used for the terminal group in the terminal group Communication between.
  • the policy control function entity determines, according to the identifier of the terminal in the terminal group, the session management function entity accessed by the terminal in the terminal group. Determining the first session management function entity according to the session management function entity accessed by the terminal.
  • the policy control function entity may determine the first session management function according to the number of terminals in the terminal group served by each session management function entity in the session management function entity corresponding to the terminal in the terminal group. entity.
  • the policy control function entity sends the second indication information to the first session management function entity, where the second indication information is used to indicate that the first session management function entity selects the second terminal in the terminal group to communicate.
  • a user plane function entity where the second terminal is a terminal in the terminal group corresponding to the first session management function entity.
  • the policy control function entity sends a notification message to the target network element, where the notification message includes the terminal group information, address information of the first session management function entity, and the notification message is used to indicate that the target network element will be the first session.
  • the management function entity inserts a session to the third terminal within the terminal group, and instructs the first session management function entity to select a user plane function entity for communication by the third terminal.
  • the target network element is a second session management function entity or an access and mobility management function entity
  • the third terminal is a terminal corresponding to the target network element in the terminal group.
  • any three, or all entities may It is implemented by a physical device, and may be implemented by a plurality of physical devices, and may also be a logical function module in a physical device, which is not specifically limited in this embodiment of the present application.
  • the communication method of the present application can be performed by a device.
  • the device may be a chip in a session management function entity or a session management function entity, or may be a chip in a policy control function entity or a policy control function entity.
  • the session management function entity is also called an SMF (session management function) entity
  • the user plane function entity is also called UPF ((user plane function), policy control function entity).
  • UPF user plane function
  • PCF policy control function
  • AMF Access and Mobility Management Function
  • a session management function entity, a policy control function entity, an access and The mobility management functional entity may also have other names.
  • the present application uses a device as a session management function entity or a policy control function entity as an example to describe a communication method, and the method for implementing a chip in a chip or a policy control function entity in a session management function entity may be The specific description of the communication method of the session management function entity or the policy control function entity will not be repeated.
  • the present application is directed to a method for communication between terminals in a terminal group, where terminals in one terminal group can be represented by terminal identifiers of each terminal, and at least two terminal groups are included in the terminal group.
  • Terminals Each terminal within the terminal group, in a particular application, for example, may be a communication device within a vehicle in the fleet. That is, there is one communication device on each vehicle in the fleet, and the set of communication devices on each vehicle constitutes a terminal group.
  • the communication between the terminals within the terminal group can be used to indicate communication between vehicles within the fleet.
  • the terminals in the terminal group may have other meanings, such as a set of multiple control units in the factory, which may also be referred to as a terminal group.
  • This application does not limit the specific application scenarios of the terminals in the terminal group.
  • FIG. 1(b) is a schematic diagram of a possible network architecture of the present application.
  • the network architecture is a 5G network architecture.
  • the network element in the 5G architecture includes an AMF entity, an SMF entity, and a user plane function UPF entity; and may also include a PCF entity, a terminal (the terminal uses the UE as an example), and a radio access network (RAN). Unified Data Management (UDM) entities, etc.
  • UDM Unified Data Management
  • the control plane function entity is mainly responsible for terminal authentication, application server management, and interaction with the network side control plane.
  • the application server is mainly responsible for providing service authentication and specific services for the terminal.
  • control plane function entity may be a Vehicle to Everything Communication Control Function (V2X Control Function) entity.
  • the application server can be a Vehicle to Everything Communication Application Server (V2X Application Server), which can be used for remote driving, distribution of traffic information, and the like.
  • the RAN device communicates with the AMF entity through the N2 interface, the RAN device communicates with the UPF entity through the N3 interface, the UPF entity and the SMF entity communicate through the N4 interface, and the PCF entity and the control plane control entity pass the N5 interface. Communication, the SMF entity and the PCF entity communicate through the N7 interface, the AMF entity and the UDM entity communicate through the N8 interface, the UPF entity and the UPF entity communicate through the N9 interface, and the SMF entity communicates with the UDM entity through the N10 interface.
  • the AMF entity communicates with the SMF entity through the N11 interface, and the AMF entity communicates with the PCF entity through the N15 interface.
  • the main function of the RAN is to control the user's access to the mobile communication network through wireless.
  • the RAN is part of a mobile communication system. It implements a wireless access technology. Conceptually, it resides between devices (such as mobile phones, a computer, or any remote controller) and provides connectivity to its core network.
  • the RAN device includes, but is not limited to, (g nodeB, gNB), evolved node B (eNB), radio network controller (RNC), node B (node B, NB) in 5G, Base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved node B, or home node B, HNB), baseband unit (BBU), transmission point (transmitting and receiving point, TRP), a transmitting point (TP), a mobile switching center, etc., and may also include a wireless fidelity (wifi) access point (AP) or the like.
  • BSC Base station controller
  • BTS base transceiver station
  • TRP transmission point
  • TRP transmitting and receiving point
  • TP transmitting point
  • AP wireless fidelity
  • the AMF entity is responsible for access management and mobility management of the terminal. In practical applications, it includes the mobility management function in the mobility management entity (MME) in the network framework of long term evolution (LTE). And joined the access management function.
  • MME mobility management entity
  • LTE long term evolution
  • the SMF entity is responsible for session management, such as user session establishment.
  • the UPF entity is a functional network element of the user plane, and is mainly responsible for connecting to an external network, and includes related functions of an LTE serving gateway (SGW) and a public data network gateWay (PDN-GW).
  • SGW LTE serving gateway
  • PDN-GW public data network gateWay
  • the UDM entity can store the subscription information of the user, and implements a backend similar to the Home Subscriber Server (HSS) in the 4G.
  • HSS Home Subscriber Server
  • the PCF entity is used to perform policy control, similar to the Policy and Charging Rules Function (PCRF) in 4G, and is mainly responsible for policy authorization, quality of service (QoS), and generation of charging rules. And the corresponding rules are delivered to the UPF entity through the SMF entity, and the corresponding policies and rules are installed.
  • PCF Policy and Charging Rules Function
  • the terminal in the present application is a device with wireless transceiving function, which can be deployed on land, indoors or outdoors, hand-held or on-board; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (for example) Aircraft, balloons and satellites, etc.)
  • the terminal may be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, industrial control (industrial control) Wireless terminal, wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transport safety, A wireless terminal in a smart city, a wireless terminal in a smart home, and the like.
  • the UE in FIG. 1(b) is a specific example of the terminal.
  • the RAN device, the SMF entity, the UPF entity, the AMF entity, the PCF entity, and the UDM entity of FIG. 1(b) are only one name, and the name does not limit the device itself.
  • the network element or the entity corresponding to the RAN device, the SMF entity, the UPF entity, the AMF entity, the PCF entity, and the UDM entity may also be other names, which is not specifically limited in this embodiment of the present application. .
  • the present application introduces the solution of the present application as a specific embodiment by using the system architecture shown in FIG. 1(b).
  • An SMF entity can manage multiple UPF entities, and the set of service scopes of the multiple UPF entities is the service scope of the SMF entity.
  • the SMF entity manages multiple UPF entities, which may also be referred to as SMF entities corresponding to multiple UPF entities.
  • UPFs For each terminal in a terminal group, after establishing a session of the terminal, such as a packet data unit (PDU) session, including one or more UPF entities on the user plane path of the terminal, these UPFs
  • An entity may be referred to as a UPF entity for terminal access, and may also be referred to as a UPF entity corresponding to the terminal. It may also be referred to as a UPF entity on the session path of the terminal, or may also be referred to as a UPF entity providing services for the terminal.
  • PDU packet data unit
  • one or more SMF entities are included in the control panel path of the terminal, and these SMF entities may also be referred to as an SMF entity for managing the terminal, and may also be referred to as a control plane of the session of the terminal.
  • the present application cross-references different representations.
  • the RAN1 is the base station to which the UE1 accesses
  • the UPF1 is the UPF connected to the RAN1.
  • the UPF entity included in the user plane path of UE2 is UPF3 and UPF4
  • RAN1 is the base station to which UE2 accesses
  • UPF3 is the UPF connected to RAN2.
  • the path of communication of the communication data between the terminal 1 and the terminal 2 is:
  • the present application provides a communication method suitable for the system architecture shown in FIG. 1(a) and FIG. 1(b).
  • the communication method can reduce the communication delay between terminals in the terminal group.
  • the present application uses the session management function entity as the SMF entity, the policy control function entity as the PCF entity, and the user plane function entity as the UPF entity as an example.
  • the communication method of the present application includes:
  • Step 201 The first SMF entity determines, according to the terminal group information, a UPF entity accessed by the terminal in the terminal group.
  • the first SMF entity is an SMF entity for selecting a target UPF entity. For example, when the SMF entity corresponding to the terminal in the terminal group is the same SMF entity, the SMF entity is the first SMF entity.
  • the SMF entity corresponding to the terminal in the terminal group is multiple SMF entities
  • one SMF entity is selected from the multiple SMF entities by the PCF entity as the first SMF entity.
  • an SMF entity other than the SMF entity corresponding to the terminal group may also be selected as the first SMF entity. That is, the selected first SMF entity is not the SMF entity corresponding to the terminal of the terminal group.
  • the terminal group information includes at least the identifier of the terminal in the terminal group, and optionally, the identifier of the terminal group.
  • the terminal group information may be from a PCF entity, may be from other SMF entities, or may be from an AMF entity. The follow-up will be explained separately according to different situations.
  • the first SMF entity can obtain at least a session context of the terminal in the terminal group, such as a PDU session context, according to the terminal group information.
  • the UPF entity accessed by the terminal served by the first SMF entity may be obtained according to the session context of the terminal.
  • the terminal group includes UE1, UE2, and UE3, where UE1 corresponds to UPF1, UE2 corresponds to UPF2, UE3 corresponds to UPF3, and UPF1 and UPF2 are UPF entities covered by the first SMF entity, and UPF3 does not belong to UPF covered by the first SMF entity. entity.
  • the first SMF entity obtains UPF1 and UPF2 according to the context of the terminal, that is, determines that the UPF entity accessed by the terminal in the terminal group is ⁇ UPF1, UPF2 ⁇ .
  • Step 202 The first SMF entity determines the target UPF entity according to the UPF entity.
  • the target UPF entity is for communication between terminals within the terminal group. Communication here refers to local communication and can also be understood as closed loop communication. That is, after receiving the communication data from the first terminal, the target UPF entity sends the communication data to the base station accessed by the second terminal through the local routing information, or to the UPF entity accessed by the second terminal. Rather than transmitting the communication data to another UPF entity accessed by the first terminal, or to the DN, as in the prior art.
  • the RAN1 is the base station to which the UE1 accesses
  • the UPF1 is the UPF connected to the RAN1.
  • the UPF entity included in the user plane path of UE2 is UPF3 and UPF4
  • RAN1 is the base station to which UE2 accesses
  • UPF3 is the UPF connected to RAN2.
  • the path of communication of the communication data between the terminal 1 and the terminal 2 is:
  • the path of the communication data between the UE 1 and the UE 2 may be:
  • the first implementation method may be employed, namely UE1->RAN1->UPF1 (target UPF)->RAN2->UE2.
  • the RAN1 and the RAN2 may be the same RAN or different RANs, which is not limited thereto.
  • the terminal in the terminal group is redirected to the same UPF entity, that is, the target UPF entity, and the communication between the terminals in the terminal group is locally communicated at the target UPF entity, which shortens Communication path, which reduces communication latency.
  • Case 1 The terminal in the terminal group accesses the same UPF entity and corresponds to the same SMF entity.
  • the PCF entity determines that the SMF entity is the first SMF entity.
  • the PCF entity sends the first indication information to the first SMF entity, where the first indication information is used to indicate that the first SMF entity selects a UPF entity used for communication by the terminal in the terminal group, and the indication information carries the terminal group information.
  • the terminal group information includes an identifier of the terminal in the terminal group, and optionally, an identifier of the terminal group.
  • the first SMF entity determines the UPF entity as the target UPF entity.
  • FIG. 3 it is a schematic diagram of UPF and SMF of a terminal in a terminal group provided by the present application.
  • the terminal group includes five terminals, which are UE1, UE2, UE3, UE4, and UE5. And the same UPF entity is accessed on the user plane path, and the same SMF entity is managed on the control plane path.
  • the PCF entity determines that the SMF entity is a first SMF entity, and the first SMF entity determines that the UPF entity is a target UPF entity.
  • the first SMF entity further creates local routing information, and sends the local routing information to the target UPF entity.
  • the local routing information is used to record the association between the downlink tunnel of each terminal in the terminal group and the terminal, so that the target UPF entity can forward the communication data of the source terminal to the destination terminal according to the local routing information, where The communication data includes address information of the destination terminal.
  • the first SMF entity does not need to send local routing information to the target UPF entity, but only needs to send an indication information to the target UPF entity to instruct the Local routing can also forward the communication data of the source terminal directly to the destination terminal.
  • the first SMF entity may not send the local routing information to the target UPF entity, and does not send the foregoing indication information to the target UPF entity, that is, the target UPF.
  • the entity itself has local communication capabilities.
  • the first SMF entity may send some information such as charging rules to the target UPF entity.
  • Case 2 The terminals in the terminal group access different UPF entities and correspond to the same SMF entity.
  • the PCF entity determines that the SMF entity is the first SMF entity.
  • the PCF entity After determining the first SMF entity, the PCF entity sends first indication information to the first SMF entity, where the first indication information is used to indicate that the first SMF entity selects a UPF entity used for communication by the terminal in the terminal group. . That is, the PCF entity instructs the first SMF entity to select a target UPF entity by using the first indication information.
  • the first SMF entity needs to select one UPF entity from the UPF entities as the target UPF entity, because the terminal in the terminal group accesses different UPF entities.
  • the terminal in the terminal group accesses different UPF entities.
  • the first SMF entity may select the target UPF entity from among the UPF entities accessed by the terminals in the terminal group or other UPF entities according to one or more of the following factors:
  • FIG. 4 it is a schematic diagram of UPF and SMF of a terminal in a terminal group provided by the present application.
  • the terminal group includes five terminals, which are UE1, UE2, UE3, UE4, and UE5.
  • UE1-UE3 accesses UPF1
  • UE4 accesses UPF2
  • UE5 accesses UPF3.
  • all are managed by the same SMF entity.
  • the service range of each UPF in UPF1-UPF3 and the location relationship of each UE in UE1-UE5 may be used, for example, whether the UE is away from the central location of the service range of the UPF entity. Closer, the closer the distance, the lower the probability of moving out of the UPF entity. Generally, if the terminals in the terminal group are close to each other, the terminal in the terminal group may be physically regarded as a whole, according to the physical location relationship between the terminal group and the UPF entity. To choose a UPF entity. Specifically, if the terminal group is closer to the central location of a UPF entity, the UPF entity is more likely to be selected.
  • the target UPF may be selected according to the number of groups within the terminal group served by each UPF entity.
  • a target UPF entity is selected from a plurality of UPF entities that have the largest number of served terminals.
  • UPF1 serves 3 terminals
  • UPF2 serves 1 terminal
  • UPF3 serves 1 terminal. Priority is given to selecting UPF1 as the target UPF entity.
  • the target UPF may be selected according to the load of each UPF entity in the UPF entity accessed by the terminal.
  • the target UPF entity is selected from among the few UPF entities with the least load.
  • one target UPF may be selected according to one or more of the above factors.
  • the target UPF may be one UPF entity in the UPF entity accessed by the terminal in the terminal group, or may be another UPF entity other than the UPF entity accessed by the terminal in the terminal group, and the other UPF entity is also affected by the UPF entity.
  • the first SMF entity management For example, when a preferred UPF entity cannot be selected from the UPF entities accessed by the terminals in the terminal group according to the above factors, other UPF entities may be considered.
  • UPF1 is finally selected as the target UPF entity, when UE1-UE5 needs to communicate with each other, it can be locally forwarded through UPF1.
  • the communication path of the communication data may be: UE1->RAN1->UPF1->RAN2->UE4.
  • the communication path of the communication data is: UE1->RAN1->UPF1->DN->UPF2->RAN2->UE4.
  • the method of the present application can shorten the transmission path of communication data, and thus can reduce the delay.
  • Case 3 The terminals in the terminal group access different UPF entities and correspond to different SMF entities.
  • one of the SMF entities may be selected by the PCF entity as the first SMF entity.
  • the PCF entity may obtain the terminal group information, and the terminal group information includes at least the identifier of the terminal in the terminal group, and optionally, the identifier of the terminal group, where the identifier of the terminal group is used to identify a terminal group.
  • the identifier of the terminal is used to identify the terminal.
  • the PCF entity may receive the terminal group information from the control plane function entity or the application server.
  • the terminal group information in the control plane function entity or the application server may be generated when the control plane function entity or the application server establishes the terminal group, or may be sent to the control plane by a certain terminal of the terminal group after establishing the terminal group. Entity or application server.
  • the PCF entity may determine the first SMF entity according to the identifier of the terminal in the terminal group. For example, the PCF entity determines the SMF entity corresponding to each terminal by using the context corresponding to the terminal identifier according to the identifier of the terminal in the terminal group.
  • FIG. 5 is a schematic diagram of UPF and SMF of a terminal in a terminal group provided by the present application.
  • the terminal group includes five terminals, which are UE1, UE2, UE3, UE4, and UE5.
  • UE1-UE3 accesses UPF1, UE4 accesses UPF2, and UE5 accesses UPF3.
  • UE1-UE4 corresponds to SMF1
  • UE5 corresponds to SMF2.
  • an SMF entity is selected from SMF1 and SMF2 as the first SMF entity.
  • the implementation manner is that the PCF entity determines the first SMF entity according to the number of terminals in the terminal group served by each SMF entity in the SMF entity corresponding to the terminal in the terminal group. .
  • the terminal served by SMF1 is UE1-UE4, the number is 4, the terminal served by SMF2 is UE5, and the number is 1, so SMF1 is selected as the first SMF.
  • the first SMF entity may also be selected according to other methods.
  • an SMF entity other than the SMF entity corresponding to the terminal group may also be selected as the first SMF entity. That is, the selected first SMF entity is not the SMF entity corresponding to the terminal of the terminal group. This application does not specifically limit this.
  • the PCF entity may determine, according to information about the terminal in the terminal group, a method for instructing the first SMF entity to select communication between terminals in the terminal group, for example, at least two Indication method.
  • the PCF entity sends the second indication information to the first SMF entity, and then sends a notification message to the target network element.
  • the target network element is an AMF entity or a second SMF entity.
  • the second SMF entity refers to an SMF entity other than the first SMF entity among the SMF entities corresponding to the terminal of the terminal group. For example, referring to FIG. 5, if SMF1 is the first SMF entity, SMF2 is the second SMF entity.
  • the PCF entity first sends the second indication information to the first SMF entity, where the second indication information is used to indicate that the first SMF entity selects a UPF entity used for communication by the second terminal in the terminal group, where the second A terminal refers to a terminal managed by a first SMF entity in a terminal group. It can also be understood that the second terminal is a terminal corresponding to the first SMF entity in the terminal group. Referring to FIG. 5, the second terminal is UE1-UE4.
  • the first SMF entity can select a target UPF entity for the terminal managed by itself, for example, the first SMF entity selects UPF1 as the target UPF entity.
  • the first SMF entity stores the target UPF entity after selecting the target UPF entity.
  • Storage methods include, but are not limited to, the following methods:
  • the storage method is as follows: storing the identifiers of the target UPF entity and the terminal group to the session context of the terminal in the terminal group
  • the target UPF entity is UPF1
  • the session context in the terminal is:
  • the session context of the UE1 includes: an identifier of the terminal group, and an identifier of the UPF1;
  • the session context of the UE2 includes: an identifier of the terminal group and an identifier of the UPF1;
  • the session context of the UE3 includes: an identifier of the terminal group and an identifier of the UPF1;
  • the session context of the UE4 includes: an identifier of the terminal group, and an identifier of the UPF1;
  • the session context of the UE5 includes: an identifier of the terminal group, and an identifier of the UPF1.
  • the session context of the terminal can also be:
  • the session context of the UE1 includes: an identifier of the terminal group, and address information of the UPF1;
  • the session context of the UE2 includes: an identifier of the terminal group, and address information of the UPF1;
  • the session context of the UE3 includes: an identifier of the terminal group, and address information of the UPF1;
  • the session context of the UE4 includes: an identifier of the terminal group, and address information of the UPF1;
  • the session context of the UE5 includes: an identifier of the terminal group, and address information of the UPF1.
  • the first SMF entity locally stores the correspondence between the identifier of the UPF1 and the identifier of the terminal group, for example, may be stored in a table form, or a function mapping relationship, and the like.
  • the PCF entity After transmitting the second indication information to the first SMF entity, the PCF entity further sends a notification message to the target network element, where the notification message includes terminal group information, address information of the first SMF entity, and the notification message is used to indicate the target.
  • the network element inserts the first SMF entity into the session of the third terminal within the terminal group, and instructs the first SMF entity to select the UPF entity for the third terminal to communicate.
  • the SMF2 in FIG. 5 is a second SMF entity.
  • the terminal of the terminal group further corresponds to the SMF3 and the SMF4, the SMF3 and the SMF4 are also referred to as the second SMF entity, that is, the second SMF entity includes the SMF3 and the SMF4.
  • the PCF entity sends a notification message to the SMF2, including the address information of the SMF1 (the first SMF entity), the terminal group information, and optionally, the indication information, which is sent by the SMF2 to the SMF1, and is used to indicate the SMF1.
  • a UPF entity that communicates with the third terminal of the terminal group is selected for communication.
  • the indication information may not be included, and is indicated by an implicit manner, which will be specifically described below.
  • the third terminal refers to a terminal in a terminal group served by the second SMF entity.
  • the third terminal refers to the UE 5.
  • SMF2 After receiving the above information, SMF2 inserts SMF1 into the session of UE5, for example, into the PDU session of UE5. On the other hand, the SMF2 also sends a first request message to the SMF1, which is used to request the SMF1 to be the third terminal, that is, the UE5 selects the UPF entity of the terminal group communication.
  • the SMF2 if the SMF2 receives the indication information sent by the PCF entity, the SMF2 carries the indication information in the first request message and sends the indication information to the SMF1. If the indication information is not included in the notification message, the SMF2 directly carries the terminal group information to the first request message and sends it to the SMF1, and implicitly instructs the SMF1 to select the UPF entity for communication for the third terminal.
  • the terminal group information sent by the SMF2 to the SMF1 includes the identifier of the terminal group and the identifier of the third terminal in the terminal group, or the transmitted terminal group information includes the identifier of the terminal group and the terminal group.
  • the SMF1 After receiving the first request message of the SMF2, the SMF1 obtains the SMF1 entity from the context of the terminal of the terminal group, or from the correspondence between the locally stored target UPF entity and the identifier of the terminal group.
  • the target UPF entity ie, UPF1 selected by the second terminal (ie, UE1-UE4), and then the target UPF entity is used as the target UPF entity of the third terminal (ie, UE5).
  • the SMF1 selects the UPF1 as the target UPF entity of the UE1-UE4 according to the indication of the PCF entity, and then receives the first request message sent by the SMF2, and the SMF1 directly uses the UPF1 as the target UPF entity of the UE5.
  • the target network element is an AMF entity
  • the implementation manner is similar and will not be described again.
  • the PCF entity directly sends a notification message to the target network element.
  • the PCF entity does not send the second indication information to the first SMF entity, but directly sends a notification message to the target network element, where the notification message includes terminal group information, address information of the first SMF entity, and the notification message.
  • the first SMF entity is the SMF1
  • the second SMF entity is the SMF2
  • the PCF entity sends a notification message to the SMF2, where the notification message includes the address information of the SMF1, the terminal group information, and optionally the indication information.
  • the indication information is used to indicate that the SMF1 selects a UPF entity for group communication for the UE1-UE5, or the indication information is used to indicate that the SMF1 selects a UPF entity for the group communication for the UE5.
  • the SMF2 After receiving the notification message of the PCF entity, the SMF2 sends a second request message to the SMF1, where the second request message is used to request the SMF1 to select the UPF entity in which the UE5 in the terminal group communicates, or to request the SMF1 to select the terminal group.
  • UE1-UE5 is a UPF entity that communicates.
  • the SMF2 directly The terminal group information is carried in the second request message and sent to the SMF1, implicitly indicating that the SMF1 selects the UPF entity for communication for the UE1-UE5, or implicitly instructs the SMF1 to select the UPF entity for communication for the UE5.
  • the terminal group information sent by the SMF2 to the SMF1 includes the identifier of the terminal group and the identifier of the third terminal in the terminal group, or the transmitted terminal group information includes the identifier of the terminal group and the terminal group.
  • the SMF1 selects a target UPF entity for the terminal managed by the SMF1 and the terminal managed by the SMF2. For example, the SMF1 selects the UPF1 as the target UPF entity.
  • the specific method for selecting the target UPF entity by the first SMF entity may refer to the specific description of selecting the target UPF entity in the foregoing scenario 2, and details are not described herein again.
  • the communication between the terminals of the terminal group is locally routed through the UPF entity, so that the communication path can be shortened, thereby shortening the transmission path of the communication data, thereby reducing the delay.
  • the first SMF entity does not need to update the tunnel information.
  • the terminal in the terminal group corresponds to different UPF entities, and corresponds to the same SMF entity
  • the first SMF entity may send a first notification message to the target UPF entity, including the tunnel information of the first terminal
  • a terminal indicates a terminal other than the terminal served by the target UPF entity, that is, the UPF entity accessed by the first terminal is different from the target UPF entity.
  • UPF1 is a target UPF entity
  • the first terminal refers to UE4 and UE5.
  • the tunnel information of the first terminal includes tunnel information or UPF tunnel information of the base station accessed by the terminal. Specifically, referring to FIG. 4, the tunnel information of the base station accessed by the UE4, the tunnel information of the base station accessed by the UE5, and the tunnel information of the UPF2 are included. , tunnel information of UPF3.
  • the first SMF entity further sends a second notification message to the base station that is accessed by the first terminal, where the second notification message includes tunnel information of the target UPF entity.
  • the second notification message includes tunnel information of the target UPF entity.
  • a second notification message is also sent to the UE4 and the UE5, including the tunnel information of the UPF1.
  • the resources of the UPF entity accessed by the first terminal may be released, for example, the resources of the UPF2 and the UPF3 are released.
  • the first request message sent by the target network element to the first SMF entity further includes tunnel information of the base station accessed by the third terminal, and/or the UPF accessed by the third terminal. Entity tunnel information.
  • the second request message sent by the target network element to the second SMF entity includes the tunnel information of the base station accessed by the third terminal, and/or the tunnel information of the UPF entity accessed by the third terminal.
  • the first request message or the second request message sent by the SMF2 to the SMF1 further includes tunnel information of the base station accessed by the UE5, and/or tunnel information of the UPF3.
  • the SMF1 sends the tunnel information of the base station accessed by the UE5, the tunnel information of the UPF3, and the tunnel information of the base station accessed by the UE4 and the tunnel information of the UPF2 to the UPF1 (the target UPF entity), and then the UPF1 can be used. Update the tunnel information.
  • the SMF1 also sends the tunnel information of the UPF1 to the UE4 and the UE5, and the UE4 and the UE5 can update the tunnel information.
  • a path between different network elements can be established, so that the target UPF entity and the base stations of the first terminal (UE4, UE5) can communicate with each other.
  • the target UPF entity is used for local communication between terminals in a terminal group, or closed loop communication, thereby shortening a communication path between terminals in the terminal group, and further Can reduce communication delays.
  • each of the foregoing network elements includes a hardware structure and/or a software module corresponding to each function.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the following embodiments are all described by taking a terminal group as a fleet.
  • the terminal in the terminal group may also be referred to as a fleet member.
  • the terminal group information may also be referred to as fleet information, including the fleet identification and the identification of the team members.
  • the control function entity of the application domain may be a V2X control function entity, and the application server may be a V2X application server.
  • the target UPF entity may also be referred to as a service UPF entity.
  • the fleet may be initiated by a UE within the fleet or initiated by a V2X control function (V2X-C) or a V2X Applicaton Server (V2X-AS). If the establishment is initiated by the UE, the UE generates fleet information and sends it to the V2X-C or V2X-AS, the fleet information including at least the fleet identity and the identity of the fleet member (ie UE). If it is initiated by V2X-C or V2X-AS, V2X-C or V2X-AS generates the above fleet information.
  • V2X-C V2X control function
  • V2X-AS V2X Applicaton Server
  • the scenario in the first embodiment is that the UEs in the fleet member list belong to the same UPF and belong to the same SMF.
  • FIG. 6 it is a schematic diagram of a network architecture to which Embodiment 1 is applied.
  • the two UEs in the fleet member list namely UE1 and UE2, are taken as an example for description.
  • the user plane paths of UE1 and UE2 both include UPF and A-UPF (Anchor UPF).
  • UE1->Base Station 1 (RAN1)->UPF->A-UPF->V2XDN->A-UPF->UPF- >RAN2->UE2.
  • a communication provided by the embodiment of the present application includes the following steps:
  • Step 1 The V2X-C or V2X-AS sends the fleet information to the PCF, and the PCF receives the fleet information from the V2X-C or V2X-AS.
  • Step 2 The PCF determines that the UEs in the fleet information are all located in the same SMF.
  • the PCF obtains the context of the team members locally according to the received fleet information, obtains the SMF of each UE from the context of the team members, and the PCF determines that the SMFs of all the UEs are the same SMF.
  • Step 3 The PCF sends indication information to the SMF, and the SMF receives the indication information from the PCF.
  • the indication information carries the fleet information, and the indication information is used to indicate that the SMF selects the service UPF for the fleet, wherein the SMF is the SMF of all the UEs determined in step 2.
  • Step 4 The SMF determines that the UEs in the fleet information are all located in the same UPF.
  • the SMF obtains the context of the team members locally according to the fleet information, and obtains the UPF of each UE from the context of the team members.
  • the SMF determines that the UPFs of all the UEs are the same UPF, and the SMF uses the UPF as the service UPF.
  • Step 5 The SMF sends a local loop information to the UPF, and the UPF receives the local loop information from the SMF.
  • the local loop circuit information includes a correspondence between the UE in the fleet member list and the downlink tunnel.
  • Table 1 gives an example of the information indicating the local loop circuit in the form of a table.
  • the t1 tunnel is a downlink tunnel between the UPF and the RAN1
  • t2 is a downlink tunnel between the UPF and the RAN2.
  • the UPF After receiving the local loop information from the UPF, the UPF will subsequently use the local loop to forward the communication data between the UEs by the information. For example, when UE1 needs to send data to UE2, according to the communication method of this embodiment, the communication flow is: UE1->RAN1->UPF->RAN2->UE2. Among them, the UPF is also called a service UPF.
  • Step 6 The UPF sends a response message to the SMF, and the SMF receives the response message from the UPF.
  • This step 6 is an optional step for receiving the local loop information from the SMF response.
  • Step 7 The SMF sends the fleet information to the UDM.
  • the UDM can store the received fleet information so that other network elements can use the fleet information.
  • This step 7 is an optional step, or the step 7 can also be performed at any step after the step 3.
  • the communication between the UEs forms a local communication in the serving UPF, which can reduce the delay of the data from the UE1 to the UE2, and is beneficial to the instant communication between the team members.
  • the scenario of this embodiment 2 is that the fleet members (UE) in the fleet member list belong to different UPFs but belong to the same SMF.
  • FIG. 8(a) a schematic diagram of a network architecture to which Embodiment 2 is applied is described by taking two UEs in the fleet member list, that is, UE1 and UE2 as an example.
  • the user plane path of UE1 includes UPF1 and A-UPF1 (anchor UPF)
  • the user plane path of UE2 includes UPF2 and A-UPF2 (anchor UPF).
  • UE1 belongs to UPF1, A-UPF1, and SMF
  • UE2 belongs to UPF2, A-UPF2, and SMF.
  • UE1->Base Station 1 (RAN1)->UPF1->A-UPF1->V2XDN->A-UPF2->UPF2- > Base station 2 (RAN2) -> UE2.
  • a communication method provided by the embodiment of the present application includes The following steps:
  • Step 1 The V2X-C or V2X-AS sends the fleet information to the PCF, and the PCF receives the fleet information from the V2X-C or V2X-AS.
  • Step 2 The PCF determines that the UEs in the fleet information are all located in the same SMF.
  • the PCF obtains the context of the team members locally according to the received fleet information, obtains the SMF of each UE from the context of the team members, and the PCF determines that the SMFs of all the UEs are the same SMF.
  • Step 3 The PCF sends indication information to the SMF, and the SMF receives the indication information from the PCF.
  • the indication information carries the fleet information, and the indication information is used to indicate that the SMF selects the service UPF for the fleet, wherein the SMF is the SMF of all the UEs determined in step 2.
  • Step 4 The SMF decides to use UPF1 as the service UPF.
  • the SMF obtains the context of the team members locally according to the fleet information, and obtains the UPF of each UE from the context of the team members. Further, the SMF determines that UE1 belongs to UPF1 and A-UPF1, and determines that UE2 belongs to UPF2 and A-UPF2, and then the SMF is Select one UPF in UPF1 and UPF2 as the service UPF.
  • the method of selecting the service UPF may include, for example, one or more of the following methods:
  • the UPF load on the user plane path of UE1 and UE2, that is, the UPF with a small load is selected as the service UPF according to the load of UPF1 and UPF2.
  • the new UPF refers to the UPF of the UE that does not include the fleet.
  • Step 5 The SMF sends a user plane setup message to the UPF1, and the UPF1 receives the user plane setup message of the SMF.
  • the user plane setup message includes the user plane information of the UE2, the local loopback information, and the tunnel information of the A-UPF2, where the user plane information of the UE2 includes the tunnel information of the UPF1 to the RAN2.
  • UPF1 After UPF1 receives the user plane setup message, UPF1 can obtain the path from UPF1 to RAN2 and the path from UPF1 to A-UPF2.
  • Step 6 The UPF1 sends a response message to the SMF, and the SMF receives the response message from the UPF1.
  • This step 6 is an optional step for receiving a notification message to the SMF response.
  • Step 7 The SMF sends an UPF reselection notification message to the base station 2 (RAN2), and the base station 2 (RAN2) receives the UPF reselection notification message from the SMF.
  • the UPF reselection notification message includes the tunnel information of the UPF1 downlink user plane (referring to the user plane of UE2).
  • the base station 2 can acquire the path of the UPF1, that is, establish the user plane path of the base station 2 (RAN2) to the UPF1.
  • Step 8 The base station 2 (RAN2) sends a response message to the SMF, and the SMF receives a response message from the base station 2 (RAN2).
  • This step 8 is an optional step for receiving an UPF reselection notification message to the SMF.
  • Step 9 The SMF sends a user plane update message to the A-UPF2, and the A-UPF2 receives the user plane update message from the SMF.
  • the user plane update message is used to update the user plane tunnel information, and the user plane update message carries the UPF1 uplink user plane tunnel information, thereby establishing a user plane path of the A-UPF2 to the UPF1.
  • Step 10 A-UPF2 sends a response message to the SMF, and the SMF receives the response message from A-UPF2.
  • the step 10 is an optional step for receiving a user plane update message to the SMF response.
  • Step 11 The SMF sends a UE user plane release message to the UPF2, and the UPF2 receives the UE user plane release message from the SMF.
  • the UPF2 After receiving the UE user plane release message, the UPF2 releases the user plane tunnel information between the UPF2 and the RAN2.
  • Step 12 The SMF sends the fleet information to the UDM.
  • the UDM can store the received fleet information so that other network elements can use the fleet information.
  • This step 12 is an optional step, or the step 12 can also be performed at any step after the step 3.
  • the network side can redirect the in-flight UE to the same UPF as the fleet service UPF, and the communication between the UEs in the fleet can implement local communication at the service UPF.
  • the SMF decision will be UPF1 acts as a fleet service UPF, performs UPF reselection for UE2, and reselects from UPF2 to UPF1. Therefore, after UE2 is reselected to UPF1, the system architecture shown in FIG. 8(a) is updated to the system architecture shown in FIG. 8(b), that is, the path between RAN2 and UPF1 is established, and UPF1 and A- are established.
  • the UPF1 is also called a service UPF. This embodiment method can reduce the delay of data from UE1 to UE2, and facilitate instant communication between fleet members.
  • the scenario of this embodiment 3 is that the UEs in the fleet member list belong to different UPFs but belong to the same SMF.
  • FIG. 10(a) it is a schematic diagram of a network architecture to which Embodiment 3 applies.
  • the user plane of UE2 has only one UPF, that is, the anchor point UPF, called A-UPF2, when the SMF selects UPF1.
  • the user plane tunnel of the anchor UPF cannot be released, that is, the UE2 cannot be reselected to the UPF1 and the user plane tunnel information of the A-UPF2 is released according to the method of Embodiment 2. Therefore, in this implementation, In the scenario of example 3, the UPF redirection can be completed by using the method of inserting the service UPF.
  • the UPF1 is inserted between the RAN2 and the A-UPF2, and the tunnel information of the UPF1, RAN2, and A-UPF2 is updated, thereby reducing the data transmission between the UE1 and the UE2.
  • the communication flow is: UE1->RAN1->UPF1->RAN2->UE2.
  • the UPF1 is also called a service UPF. This embodiment method can reduce the delay of data from UE1 to UE2, and facilitate instant communication between fleet members.
  • the scenario of this embodiment 4 is that the UEs in the fleet member list belong to different UPFs and belong to different SMFs.
  • FIG. 11( a ) a schematic diagram of a network architecture to which the fourth embodiment is applied is described by taking two UEs in the fleet member list, that is, UE1 and UE2 as an example.
  • the user plane path of UE1 includes UPF1 and A-UPF1 (anchor UPF)
  • the user plane path of UE2 includes UPF2 and A-UPF2 (anchor UPF)
  • UE1 belongs to UPF1
  • A-UPF1 anchor UPF
  • SMF1 anchor UPF2
  • UE2 belongs to UPF2, A-UPF2, and SMF2.
  • the user plane path of UE1 is only A-UPF1, that is, the UPF1 in the figure is deleted, and there may be A-UPF1 and a plurality of other UPFs (only one UPF is shown in the figure, that is, UPF1).
  • the number of UPFs in the user plane path of each UE may be at least one.
  • a communication method provided by the embodiment of the present application includes The following steps:
  • Step 1 The V2X-C or V2X-AS sends the fleet information to the PCF, and the PCF receives the fleet information from the V2X-C or V2X-AS.
  • Step 2 The PCF determines that SMF1 is a serving SMF.
  • the PCF obtains the context of the team members locally according to the fleet information, and according to the context, can obtain the SMF of each UE, and determine that the UEs in the fleet belong to different SMFs, specifically, belong to At least two SMFs.
  • the team members are UE1, UE2, UE3, UE4 and UE5, UE1, UE2 and UE3 belong to SMF1, UE4 and UE5 belong to SMF2, for example, UE1, UE2 and UE3 belong to SMF1, UE4 belongs to SMF2, UE5 belongs to SMF3, etc.
  • two UEs, UE1 and UE2 are taken as an example.
  • UE1 belongs to SMF1
  • UE2 belongs to SMF2.
  • the PCF selects one SMF as the SMF
  • the method of selecting the serving SMF may be, for example, selecting an SMF that covers the largest number of UEs in the fleet as the serving SMF.
  • a new SMF may also be selected as the service SMF, and the new SMF refers to the SMF of the UE that does not include the fleet.
  • the PCF selection SMF1 is taken as an example of the service SMF.
  • Step 3 The PCF sends a notification message to the SMF2, and the SMF2 receives the notification message from the PCF.
  • the notification message is used to notify SMF2 to insert SMF1 into the PDU session of UE2, that is, SMF1 also serves as the SMF to which UE2 belongs.
  • the notification message includes:
  • the address of the SMF1 and the first indication information, the first indication information is used to instruct the SMF2 to insert the SMF1 into the PDU session of the UE2, that is, the SMF1 also serves as the SMF to which the UE2 belongs.
  • it also includes:
  • Second indication information which is required to be forwarded by SMF2 to SMF1, and used to indicate that SMF1 is a UE selection service UPF for the fleet.
  • the second indication information may not be included, that is, the SMF1 may be implicitly instructed to select a service UPF for the UE of the fleet.
  • Step 4 The SMF2 sends a session establishment request message to the SMF1, and the SMF1 receives the session establishment request message from the SMF2.
  • the session establishment request message includes:
  • it also includes:
  • information 3) and 4) come from the PCF entity.
  • the SMF1 After receiving the session establishment request message, the SMF1 selects the service UPF, and the method of selecting the method is to refer to the method for selecting the UPF in the second embodiment, and details are not described herein again.
  • step 3 and step 4 may also be replaced by the following steps A: step C:
  • Step A the PCF sends a notification message to the SMF1, and the SMF1 receives the notification message from the PCF.
  • the notification message includes fleet information including the fleet identification and the identification of the team members, and optionally may include an identification of all team members or an identification of only team members managed by SMF1.
  • the notification message further includes indication information, where the indication information is used to indicate that the SMF1 selects the service UPF.
  • the notification message implicitly instructs the SMF1 to select the service UPF by the transmitted fleet information.
  • the SMF1 selects the service UPF, for example, selects UPF1 as the service UPF.
  • the service UPF is also stored.
  • Step B The PCF sends a notification message to the SMF2, and the SMF2 receives the notification message from the PCF.
  • the notification message is used to notify SMF2 to insert SMF1 into the PDU session of UE2, that is, SMF1 also serves as the SMF to which UE2 belongs.
  • the content of the notification message is the same as that of the notification message described in the foregoing step 3. For details, reference is made to the foregoing description.
  • Step C SMF2 sends a session establishment request message to SMF1, and SMF1 receives a session establishment request message from SMF2.
  • the content included in the session establishment request message may refer to the content carried in the session establishment request message described in the foregoing step 4.
  • the fleet information carried in the session establishment request message may include only the team members managed by the SMF2 in the fleet, or may include all members in the team.
  • the SMF1 After receiving the session establishment request message, the SMF1 selects the service UPF for the terminal managed by the SMF2. In the above step A, the SMF1 has selected the service UPF for the terminal managed by the SMF1 and stores it. Therefore, the SMF1 can be directly selected.
  • the service UPF which is the service UPF of the terminal managed by the SMF2, is the UPF1 to be selected as the service UPF of the terminal managed by the SMF2.
  • Step 5 The SMF1 sends a user plane setup message to the UPF1, and the UPF1 receives the user plane setup message from the SMF1.
  • the user plane setup message includes the tunnel information of the UPF2, the uplink tunnel information of the RAN2, and the local loop information.
  • UPF1 After UPF1 receives the user plane setup message, UPF1 can establish a path from UPF1 to UPF2 and establish a path from UPF1 to RAN2.
  • Step 6 The UPF1 sends a response message to the SMF1, and the SMF1 receives the response message from the UPF1.
  • This step 6 is an optional step for receiving a notification message in response to the SMF1.
  • Step 7 The SMF1 sends a response message to the SMF2, and the SMF2 receives the response message from the SMF1.
  • the response message includes a downlink tunnel of UPF1.
  • Step 8 The SMF2 sends a user plane update message to the UPF2, and the UPF2 receives the user plane update message from the SMF2.
  • the user plane update message includes tunnel information of UPF1.
  • UPF2 can establish a path from UPF2 to UPF1.
  • Step 9 UPF2 sends a response message to SMF2, and SMF2 receives a response message from UPF2.
  • This step 9 is an optional step for receiving a user plane update message in response to the SMF2.
  • Step 10 The SMF2 sends a User Plane Tunnel Update message to the Base Station 2 (RAN2), and the Base Station 2 (RAN2) receives the User Plane Tunnel Update message from the SMF2.
  • RAN2 Base Station 2
  • RAN2 Base Station 2
  • the user plane tunnel update message includes a downlink tunnel of the UPF1, and the downlink tunnel of the UPF1 is obtained by the SMF2 in the foregoing step 7.
  • base station 2 can update the user plane path and establish a path from base station 2 (RAN2) to UPF1.
  • Step 11 SMF1 sends the fleet information to the UDM.
  • the UDM can store the received fleet information so that other network elements can use the fleet information.
  • This step 11 is an optional step, or the step 11 can also be performed at any step after the step 4.
  • the network side can redirect the in-vehicle UE to the same SMF, the SMF as the fleet service SMF, and, to the same UPF, the UPF as the fleet service UPF, and the communication between the UEs in the fleet is
  • the local communication is implemented at the service UPF.
  • the service SMF ie, SMF1
  • the service SMF1 decides to use UPF1 as the fleet service UPF, perform UPF insertion for UE2, and insert UPF1 between RAN2 and UPF2.
  • the system architecture shown in FIG. 11(a) is updated to the system architecture shown in FIG.
  • the communication flow is: UE1->RAN1->UPF1->RAN2->UE2.
  • the UPF1 is also called a service UPF. This embodiment method can reduce the delay of data from UE1 to UE2, and facilitate instant communication between fleet members.
  • a schematic diagram of a device provided by the present application which may be a session management function entity, may be executed by a first session management function entity (first SMF) in any of the above embodiments. Entity) method of execution.
  • the apparatus may also be a policy control function entity, which may perform the method performed by the policy control function entity (PCF entity) in any of the above embodiments.
  • PCF entity policy control function entity
  • the apparatus 1300 includes at least one processor 131, a transceiver 132, and optionally a memory 133.
  • the processor 131, the transceiver 132, and the memory 133 are connected by a communication line.
  • the processor 131 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line can include a path for communicating information between the units.
  • the transceiver 132 is configured to communicate with other devices or communication networks, and the transceiver includes a radio frequency circuit.
  • the memory 133 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device may also be an electrically erasable programmabler-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, or a disc storage ( Including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be stored by a computer Any other media taken, but not limited to this.
  • EEPROM electrically erasable programmabler-only memory
  • CD-ROM compact disc read-only memory
  • CD-ROM compact disc read-only memory
  • disc storage Including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • the memory 133 may be independent and connected to the processor 131 via a communication line.
  • the memory 133 can also be integrated with the processor.
  • the memory 133 is used to store application code for executing the solution of the present invention, and is controlled by the processor 131 for execution.
  • the processor 131 is configured to execute application code stored in the memory 133.
  • the processor 131 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 1300 can include multiple processors, such as processor 131 and processor 138 in FIG. Each of these processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • processors such as processor 131 and processor 138 in FIG.
  • processors may be a single-CPU processor or a multi-core processor, where the processor may refer to one or more devices, circuits, and/or A processing core for processing data, such as computer program instructions.
  • the device when the device is a session management function entity, the device may be used to implement the steps performed by the first session management function entity (the first SMF entity) in the communication method of the embodiment of the present invention. , will not repeat them here.
  • the device when the device is a policy control function entity, the device may be used to implement the steps performed by the policy control function entity (PCF entity) in the communication method of the embodiment of the present invention. Let me repeat.
  • PCF entity policy control function entity
  • the application may divide the function module of the session management function entity according to the above method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 14 shows a schematic diagram of a device, which may be the first session management function entity (first SMF entity) involved in the above embodiment,
  • the apparatus includes a processing unit 1401 and a communication unit 1402.
  • the session management function entity is presented in the form of dividing each function module corresponding to each function, or the session management function entity is presented in the form of dividing each function module in an integrated manner.
  • a “module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the session management function entity may be used to implement the steps performed by the first session management function entity (the first SMF entity) in the communication method of the embodiment of the present invention.
  • the first session management function entity the first SMF entity
  • the application may divide the function module of the policy control function entity according to the above method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 15 shows a schematic diagram of a device, which may be a policy control function entity involved in the above embodiment, the device including a processing unit 1501 and a communication unit. 1502.
  • the policy control function entity is presented in the form of dividing each function module corresponding to each function, or the policy control function entity is presented in a form of dividing each function module in an integrated manner.
  • a “module” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • policy control function entity may be used to implement the steps performed by the policy control function entity (PCF entity) in the communication method of the embodiment of the present invention.
  • PCF entity policy control function entity
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a Solid State Disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a Solid State Disk (SSD)
  • embodiments of the present application can be provided as a method, apparatus (device), computer readable storage medium, or computer program product.
  • the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware aspects, which are collectively referred to herein as "module” or "system.”
  • a general purpose processor may be a microprocessor.
  • the general purpose processor may be any conventional processor, controller, microcontroller, or state machine.
  • the processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.
  • the steps of the method or algorithm described in the embodiments of the present application may be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium in the art.
  • the storage medium can be coupled to the processor such that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and the storage medium may be disposed in the ASIC, and the ASIC may be disposed in the terminal device. Alternatively, the processor and the storage medium may also be disposed in different components in the terminal device.
  • the above-described functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, these functions may be stored on a computer readable medium or transmitted as one or more instructions or code to a computer readable medium.
  • Computer readable media includes computer storage media and communication media that facilitates the transfer of computer programs from one place to another.
  • the storage medium can be any available media that any general purpose or special computer can access.
  • Such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other device or data structure that can be used for carrying or storing Other media that can be read by a general purpose or special computer, or a general purpose or special processor.
  • any connection can be appropriately defined as a computer readable medium, for example, if the software is from a website site, server or other remote source through a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or wirelessly transmitted in, for example, infrared, wireless, and microwave, is also included in the defined computer readable medium.
  • DSL digital subscriber line
  • the disks and discs include compact disks, laser disks, optical disks, DVDs, floppy disks, and Blu-ray disks. Disks typically replicate data magnetically, while disks typically optically replicate data with a laser. Combinations of the above may also be included in a computer readable medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请提供一种通信方法、装置及系统。该方法包括：第一会话管理功能实体根据终端群组信息，确定终端群组内的终端接入的用户面功能实体。第一会话管理功能实体根据用户面功能实体，确定目标用户面功能实体，目标用户面功能实体用于终端群组内的终端之间的通信。该方法，将终端群组内的终端重定向至同一用户面功能实体，即目标用户面功能实体，实现终端群组内的终端之间的通信在目标用户面功能实体处本地通信，缩短了通信路径，从而降低了通信时延。

Description

一种通信方法、装置及系统
本申请要求于2017年9月30日提交中国国家知识产权局、申请号为201710923300.0、发明名称为“一种通信方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种通信方法、装置及系统。
背景技术
移动通信的发展目标之一，是建立一个包括各类型终端的广泛的互联互通网络，这也是当前在蜂窝通信框架内发展物联网的出发点之一。物联网使得由多个终端构成的终端群组内的终端之间可以相互通信。
目前，一般应用较多的是终端之间通过第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)网络进行通信。
在一些应用场景中，终端群组内的终端之间的通信对时延要求比较高。例如，由多个车辆构成的车队内的车辆之间的通信，对通信的时延要求非常高。
针对时延要求比较高的通信应用场景，如何降低通信的时延，则是一个亟需解决的问题。
发明内容
本申请提供一种通信方法、装置及系统，用以降低终端群组内的终端之间的通信时延。
第一方面，本申请提供一种通信方法，该方法可由会话管理功能实体或会话管理功能实体内的芯片执行。会话管理功能实体在5G通信中可以是SMF实体，在未来通信中可以是其它具有会话管理功能的实体。该通信方法包括：第一会话管理功能实体根据终端群组信息，确定终端群组内的终端接入的用户面功能实体。第一会话管理功能实体根据用户面功能实体，确定目标用户面功能实体，目标用户面功能实体用于终端群组内的终端之间的通信。该方法，将终端群组内的终端重定向至同一用户面功能实体，即目标用户面功能实体，实现终端群组内的终端之间的通信在目标用户面功能实体处本地通信，缩短了通信路径，从而降低了通信时延。
在一种可能的设计中，第一会话管理功能实体根据用户面功能实体，确定目标用户面功能实体，包括：第一会话管理功能实体根据下列因素中的一个或多个，从终端接入的用户面功能实体中或其他用户面功能实体，选择目标用户面功能实体：终端接入的用户面功能实体中每个用户面功能实体的服务范围和终端群组内的终端的位置、终端接入的用户面功能实体中每个用户面功能实体服务的终端群组内的终端的数量、终端接入的用户面功能实体中每个用户面功能实体的负荷。该方法综合考虑多种因素，可实现选择较优的用户面 功能实体作为用户面功能实体，有利于提高通信质量。
在一种可能的设计中，第一会话管理功能实体向目标用户面功能实体发送第一通知消息，第一通知消息包括第一终端的隧道信息，第一终端接入的用户面功能实体不同于目标用户面功能实体。该方法用于更新目标用户面功能实体的隧道信息，便于实现在目标用户面功能实体处的本地通信。
在一种可能的设计中，第一会话管理功能实体向第一终端接入的基站发送第二通知消息，第二通知消息包括目标用户面功能实体的隧道信息。
在一种可能的设计中，第一会话管理功能实体释放第一终端接入的用户面功能实体的资源。
在一种可能的设计中，第一会话管理功能实体接收来自策略控制功能实体的第一指示信息，第一指示信息用于指示第一会话管理功能实体选择用于终端群组内的终端进行通信的用户面功能实体。
在一种可能的设计中，第一会话管理功能实体接收来自策略控制功能实体的第二指示信息，第二指示信息用于指示第一会话管理功能实体选择用于终端群组内的第二终端进行通信的用户面功能实体，第二终端为终端群组内的对应第一会话管理功能实体的终端。第一会话管理功能实体根据用户面功能实体，确定目标用户面功能实体，包括：第一会话管理功能实体根据第二终端接入的用户面功能实体，确定目标用户面功能实体。
在一种可能的设计中，第一会话管理功能实体接收来自目标网元的第一请求消息，第一请求消息用于请求第一会话管理功能实体选择终端群组内的第三终端进行通信的用户面功能实体，第三终端为终端群组内的对应目标网元的终端。第一会话管理功能实体确定目标用户面功能实体，为第三终端进行通信的用户面功能实体。其中，目标网元为第二会话管理功能实体或接入与移动性管理功能实体。该方法，当接收到来自目标网元的第一请求消息时，则将之前确定的目标用户面功能实体，作为目标网元对应的终端的目标用户面功能实体，无需再重新选择目标用户面功能实体，有利于节约开销。
在一种可能的设计中，第一请求消息包括第三终端接入的基站的隧道信息、第三终端接入的用户面功能实体的隧道信息。
在一种可能的设计中，第一会话管理功能实体接收来自目标网元的第二请求消息，第二请求消息用于请求第一会话管理功能实体选择终端群组内的第三终端进行通信的用户面功能实体，第三终端为终端群组内的对应目标网元的终端。第一会话管理功能实体根据用户面功能实体，确定目标用户面功能实体，包括：第一会话管理功能实体根据第二终端接入的用户面功能实体，确定目标用户面功能实体，第二终端为终端群组内的对应第一会话管理功能实体的终端。其中，目标网元为第二会话管理功能实体或AMF实体。
在一种可能的设计中，第二请求消息包括第三终端接入的基站的隧道信息、第三终端接入的用户面功能实体的隧道信息。
在一种可能的设计中，第一会话管理功能实体接收来自控制面功能实体或应用服务器的终端群组信息。
在一种可能的设计中，终端群组信息包括终端群组的标识和终端群组内的终端的标识。第一会话管理功能实体将目标用户面功能实体和终端群组的标识，存储至终端群组内的终 端的上下文，终端群组内的终端的上下文用于第一会话管理功能实体从终端群组内的终端的上下文，获取目标用户面功能实体；或者，第一会话管理功能实体本地存储目标用户面功能实体和终端群组的标识之间的对应关系，对应关系用于第一会话管理功能实体从对应关系获取目标用户面功能实体。该方法，将确定的目标用户面功能实体存储至终端的上下文或在会话管理功能实体本地存储，便于获取目标用户面功能实体。
第二方面，本申请提供一种通信方法，该方法可由策略控制功能实体或策略控制功能实体内的芯片执行。策略控制功能实体在5G中可以是PCF实体，在未来通信中可以是其它具有策略控制功能的实体。该通信方法包括：策略控制功能实体获取终端群组信息，终端群组信息至少包括终端群组内的终端的标识。策略控制功能实体根据终端群组内的终端的标识，确定第一会话管理功能实体，第一会话管理功能实体用于选择目标用户面功能实体，目标用户面功能实体用于终端群组内的终端之间的通信。
在一种可能的设计中，策略控制功能实体根据终端群组内的终端的标识，确定第一会话管理功能实体，包括：策略控制功能实体根据终端群组内的终端的标识，确定终端群组内的终端接入的会话管理功能实体。策略控制功能实体根据终端接入的会话管理功能实体，确定第一会话管理功能实体。
在一种可能的设计中，策略控制功能实体根据终端接入的会话管理功能实体，确定第一会话管理功能实体，包括：策略控制功能实体根据终端群组内的终端对应的会话管理功能实体中，每个会话管理功能实体服务的终端群组内的终端的数量，确定第一会话管理功能实体。
在一种可能的设计中，策略控制功能实体获取终端群组信息，包括：策略控制功能实体接收来自控制面功能实体或应用服务器的终端群组信息。
在一种可能的设计中，策略控制功能实体向第一会话管理功能实体发送第一指示信息，第一指示信息用于指示第一会话管理功能实体选择用于终端群组内的终端进行通信的用户面功能实体。
在一种可能的设计中，策略控制功能实体向第一会话管理功能实体发送第二指示信息，第二指示信息用于指示第一会话管理功能实体选择用于终端群组内的第二终端进行通信的用户面功能实体，第二终端为终端群组内的对应第一会话管理功能实体的终端。
在一种可能的设计中，策略控制功能实体向目标网元发送通知消息，通知消息包括终端群组信息、第一会话管理功能实体的地址信息，通知消息用于指示目标网元将第一会话管理功能实体插入到终端群组内的第三终端的会话，以及指示第一会话管理功能实体选择用于第三终端进行通信的用户面功能实体。其中，目标网元为第二会话管理功能实体或AMF实体，第三终端为终端群组内的对应目标网元的终端。
第三方面，本申请提供一种装置，本申请提供一种装置，该装置可以是会话管理功能实体，也可以是会话管理功能实体内的芯片。该装置具有实现上述第一方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为会话管理功能实体时，会话管理功能实体包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器， 所述收发器包括射频电路，可选地，所述会话管理功能实体还包括存储单元，该存储单元例如可以是存储器。当会话管理功能实体包括存储单元时，该存储单元存储有计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该会话管理功能实体执行上述第一方面任意一项的通信方法。
在另一种可能的设计中，当该装置为会话管理功能实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第一方面任意一项的通信方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述会话管理功能实体内的位于所述芯片外部的存储单元，如只读存储器(read-only memory，ROM)、可存储静态信息和指令的其他类型的静态存储设备、随机存取存储器(random access memory，RAM)等。
其中，上述任一处提到的处理器，可以是一个通用的中央处理器(Central Processing Unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制上述第一方面的通信方法的程序执行的集成电路。
第四方面，本申请提供一种装置，本申请提供一种装置，该装置可以是策略控制功能实体，也可以是策略控制功能实体内的芯片。该装置具有实现上述第二方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，当该装置为策略控制功能实体时，策略控制功能实体包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是收发器，所述收发器包括射频电路，可选地，所述策略控制功能实体还包括存储单元，该存储单元例如可以是存储器。当终端包括存储单元时，该存储单元存储有计算机执行指令，该处理单元与该存储单元连接，该处理单元执行该存储单元存储的计算机执行指令，以使该策略控制功能实体执行上述第二方面任意一项的通信方法。
在另一种可能的设计中，当该装置为策略控制功能实体内的芯片时，芯片包括：处理单元和通信单元，所述处理单元例如可以是处理器，所述通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行存储单元存储的计算机执行指令，以使上述第二方面任意一项的通信方法被执行。可选地，所述存储单元为所述芯片内的存储单元，如寄存器、缓存等，所述存储单元还可以是所述策略控制功能实体内的位于所述芯片外部的存储单元，如ROM、可存储静态信息和指令的其他类型的静态存储设备、RAM等。
其中，上述任一处提到的处理器，可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述第二方面的通信方法的程序执行的集成电路。
第五方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第六方面，本申请还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
另外，第二方面至第六方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1(a)为本申请提供的通信系统示意图；
图1(b)为本申请提供的一种可能的网络架构示意图；
图2为本申请提供的通信方法示意图；
图3为本申请提供的终端群组内的终端的UPF和SMF的一种示意图；
图4为本申请提供的终端群组内的终端的UPF和SMF的另一种示意图；
图5为本申请提供的终端群组内的终端的UPF和SMF的另一种示意图；
图6为实施例1所适用的网络架构示意图；
图7为本申请实施例提供的一种通信方法示意图；
图8(a)为实施例2所适用的网络架构示意图；
图8(b)为实施例2所适用的网络架构另一示意图；
图9为本申请实施例提供的一种通信方法示意图；
图10(a)为实施例3所适用的网络架构示意图；
图10(b)为实施例3所适用的网络架构另一示意图；
图11(a)为实施例4所适用的网络架构示意图；
图11(b)为实施例4所适用的网络架构另一示意图；
图12为本申请实施例提供的一种通信方法示意图；
图13为本申请实施例提供的一种装置示意图；
图14为本申请实施例提供的一种装置示意图；
图15为本申请实施例提供的一种装置示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
如图1(a)所示，为本申请提供的一种通信系统示意图。该通信系统包括用户面功能实体和会话管理功能实体。可选地，还包括接入与移动性管理功能实体、策略控制功能实体中的一个或全部。
图中的用户面功能实体可以是一个或多个，会话管理功能实体可以是一个或多个。为方便说明，图中均以一个为例进行示意性地说明。
其中，用户面功能实体中的目标用户面功能实体，用于终端群组内的终端之间的通信。
会话管理功能实体，用于根据终端群组信息确定终端群组内的终端接入的用户面功能实体。以及，根据用户面功能实体，确定目标用户面功能实体。
作为一种实现方式，会话管理功能实体还根据下列因素中的一个或多个，从终端接入的用户面功能实体中或其他用户面功能实体，选择目标用户面功能实体：终端接入的用户面功能实体中每个用户面功能实体的服务范围和终端群组内的终端的位置、终端接入的用户面功能实体中每个用户面功能实体服务的终端群组内的终端的数量、终端接入的用户面功能实体中每个用户面功能实体的负荷。
作为一种实现方式，会话管理功能实体还向目标用户面功能实体发送第一通知消息，该第一通知消息包括第一终端的隧道信息，第一终端接入的用户面功能实体不同于目标用户面功能实体。
作为一种实现方式，会话管理功能实体向第一终端接入的基站发送第二通知消息，该第二通知消息包括目标用户面功能实体的隧道信息。
策略控制功能实体，用于获取终端群组信息，终端群组信息至少包括所述终端群组内的终端的标识。根据终端群组内的终端的标识，确定第一会话管理功能实体，所述第一会话管理功能实体用于选择目标用户面功能实体，该目标用户面功能实体用于终端群组内的终端之间的通信。
作为一种实现方式，策略控制功能实体根据终端群组内的终端的标识，确定终端群组内的终端接入的会话管理功能实体。根据终端接入的会话管理功能实体，确定上述第一会话管理功能实体。
作为一种实现方式，策略控制功能实体可以根据终端群组内的终端对应的会话管理功能实体中，每个会话管理功能实体服务的终端群组内的终端的数量，确定上述第一会话管理功能实体。
作为一种实现方式，策略控制功能实体向第一会话管理功能实体发送第二指示信息，第二指示信息用于指示第一会话管理功能实体选择用于终端群组内的第二终端进行通信的用户面功能实体，所述第二终端为所述终端群组内的对应所述第一会话管理功能实体的终端。
作为一种实现方式，策略控制功能实体向目标网元发送通知消息，通知消息包括所述终端群组信息、第一会话管理功能实体的地址信息，通知消息用于指示目标网元将第一会话管理功能实体插入到终端群组内的第三终端的会话，以及指示第一会话管理功能实体选择用于第三终端进行通信的用户面功能实体。其中，目标网元为第二会话管理功能实体或接入与移动性管理功能实体，第三终端为终端群组内的对应目标网元的终端。可选的，图1(a)中的用户面功能实体、会话管理功能实体、接入与移动性管理功能实体和策略控制功能实体中的任两个，或任三个，或全部实体，可以由一个实体设备实现，也可以由多个实体设备共同实现，还可以是一个实体设备内的一个逻辑功能模块，本申请实施例对此不作具体限定。
需要说明的的是，本申请的通信方法可由装置执行。该装置可以是会话管理功能实体或会话管理功能实体内的芯片，还可以是策略控制功能实体或策略控制功能实体内的芯片。
在第五代移动通信技术(5th-Generation，5G)中，会话管理功能实体也称为SMF(session management function)实体，用户面功能实体也称为UPF((user plane function)、策略控制功能实体也称为PCF(policy control function)实体，接入与移动性管理功能实体也称为AMF(Access and Mobility Management Function)实体。在未来通信中，会话管理功能实体、策略控制功能实体、接入与移动性管理功能实体也可能有其他名称。
为方便说明，本申请以装置为会话管理功能实体或策略控制功能实体为例，对通信方法进行说明，对于装置为会话管理功能实体内的芯片或策略控制功能实体内的芯片的实现方法，可参考会话管理功能实体或策略控制功能实体的通信方法的具体说明，不再重复介绍。
本申请，是针对一种终端群组内的终端之间的通信方法进行说明的，其中，一个终端群组内的终端可以使用每个终端的终端标识来表示，且终端群组中至少包括两个终端。终端群组内的每个终端，在具体应用中，例如可以是车队中的一个车辆内的通信装置。即，车队内的每个车辆上有一个通信装置，每个车辆上的通信装置的集合，即构成一个终端群组。终端群组内的终端之间的通信，即可以用于表示车队内的车辆之间的通信。
当然，在其它应用场景下，终端群组内的终端还可以有其他的含义，比如工厂内的多个控制单元构成的集合，也可以称为一个终端群组。本申请对终端群组内的终端的具体应用场景不做限定。
如图1(b)所示，为本申请的一种可能的网络架构示意图。该网络架构为5G网络架构。该5G架构中的网元包括AMF实体、SMF实体和用户面功能UPF实体；还可以包括PCF实体、终端(图中以终端为UE为例)、无线接入网(Radio Access Network，RAN)、统一数据管理(Unified Data Management，UDM)实体等。在应用域，包括控制面功能实体和应用服务器。其中，控制面功能实体主要负责终端的鉴权，应用服务器的管理以及与网络侧控制面的交互等。应用服务器主要负责为终端提供业务鉴权和具体业务。例如，在车联网通信中，控制面功能实体可以是车联网通信控制功能(Vehicle to Everything Communication Control Function，V2X Control Function)实体。应用服务器可以是车联网通信应用服务器(Vehicle to Everything Communication Application Server，V2X Application Server)，可用于远程驾驶，交通信息的分发等。
其中，RAN设备与AMF实体之间通过N2接口通信，RAN设备与UPF实体之间通过N3接口通信，UPF实体与SMF实体之间通过N4接口通信，PCF实体与控制面控制实体之间通过N5接口通信，SMF实体与PCF实体之间通过N7接口通信，AMF实体与UDM实体之间通过N8接口通信，UPF实体与UPF实体之间通过N9接口通信，SMF实体与UDM实体之间通过N10接口通信，AMF实体与SMF实体之间通过N11接口通信，AMF实体与PCF实体之间通过N15接口通信。
RAN的主要功能是控制用户通过无线接入到移动通信网络。RAN是移动通信系统的一部分。它实现了一种无线接入技术。从概念上讲，它驻留某个设备之间(如移动电话、一台计算机，或任何远程控制机)，并提供与其核心网的连接。RAN设备包括但不限于：5G中的(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、 基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(BaseBand Unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等，此外，还可以包括无线保真(wireless fidelity，wifi)接入点(access point，AP)等。
AMF实体负责终端的接入管理和移动性管理，在实际应用中，其包括了长期演进(long term evolution，LTE)中网络框架中移动管理实体(mobility management entity，MME)里的移动性管理功能，并加入了接入管理功能。
SMF实体负责会话管理，如用户的会话建立等。
UPF实体是用户面的功能网元，主要负责连接外部网络，其包括了LTE的服务网关(serving gateway，SGW)和公用数据网网关(public data network GateWay，PDN-GW)的相关功能。
UDM实体可存储用户的签约信息，实现类似于4G中的归属签约用户服务器(Home Subscriber Server，HSS)的后端。
PCF实体用于执行策略控制，类似于4G中的策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)，主要负责策略授权，服务质量(Quality of Service，QoS)以及计费规则的生成，并将相应规则通过SMF实体下发至UPF实体，完成相应策略及规则的安装。
本申请中的终端，是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。例如图1(b)中的UE，为终端的一个具体示例。
需要说明的是，图1(b)的RAN设备、SMF实体、UPF实体、AMF实体、PCF实体和UDM实体等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，RAN设备、SMF实体、UPF实体、AMF实体、PCF实体和UDM实体所对应的网元或实体也可以是其他的名字，本申请实施例对此不作具体限定。
为方便说明，本申请以图1(b)所示的系统架构，作为一个具体的实施例来介绍本申请方案。
针对图1(b)所示的系统架构。一个SMF实体可以管理多个UPF实体，并且，该多个UPF实体的服务范围的集合，即为该SMF实体的服务范围。SMF实体管理多个UPF实体，也可以称为SMF实体对应多个UPF实体。
针对一个终端群组内的每个终端，当建立了终端的会话，例如分组数据单元(packet data unit，PDU)会话后，在终端的用户面路径上包括一个或多个UPF实体，则这些UPF实体可以称为终端接入的UPF实体，也可以称为终端对应的UPF实体，还可以称为终端的 会话路径上的UPF实体，或者还可以称为为该终端提供服务的UPF实体，都表示同一个含义，本申请后续会交叉使用不同的表述方式。
在建立了终端的会话后，在终端的控制面板路径上包括一个或多个SMF实体，则这些SMF实体也可以称为用于管理该终端的SMF实体，也可以称为终端的会话的控制面路径的SMF实体，或者还可以称为终端对应的SMF实体，，或者还可以称为为该终端提供服务的SMF实体，都表示同一个含义，本申请后续会交叉使用不同的表述方式。
目前，若按照现有技术方案，当终端群组内的终端之间进行通信时，通信数据需要经过终端的用户面路径上的所有UPF实体。
例如，针对终端群组内的UE1和UE2，若终端1的用户面路径上包括的UPF实体为UPF1、UPF2，RAN1为UE1接入的基站，且UPF1为与RAN1连接的UPF。UE2的用户面路径上包括的UPF实体为UPF3、UPF4，RAN1为UE2接入的基站，且UPF3为与RAN2连接的UPF。
若按照现有技术的通信方法，终端1与终端2之间的通信数据的经过路径为：
终端1->RAN1->UPF1->UPF2->数据网络(Data Network，DN)->UPF4->UPF3->RAN2->终端2。
可以看出，当终端1的用户面路径上有多个UPF实体，或者终端2的用户面路径上有多个UPF实体时，终端1与终端2之间的通信，需要经过用户面路径上的每个UPF实体，造成通信数据的路径的延长，从而导致终端之间的时延较大。
为解决上述问题，本申请提供一种通信方法，该通信方法适用于图1(a)和图1(b)所示的系统架构。该通信方法可降低终端群组内的终端之间的通信时延。
为方便说明，本申请以会话管理功能实体为SMF实体，策略控制功能实体为PCF实体，用户面功能实体为UPF实体为例进行说明。
下面对本申请的通信方法做具体介绍。如图2所示，为本申请提供的通信方法，包括：
步骤201、第一SMF实体根据终端群组信息，确定终端群组内的终端接入的UPF实体。
该第一SMF实体为用于选择目标UPF实体的SMF实体。例如，当终端群组内的终端对应的SMF实体是同一个SMF实体时,则该SMF实体即为第一SMF实体。
再比如,当终端群组内的终端对应的SMF实体是多个SMF实体时,则从由PCF实体从多个SMF实体中选择一个SMF实体,作为第一SMF实体。
再比如，还可以选择终端群组对应的SMF实体之外的SMF实体，作为第一SMF实体。即，选择的第一SMF实体不是终端群组的终端对应的SMF实体。
终端群组信息至少包括终端群组内的终端的标识，可选的，还包括终端群组的标识。该终端群组信息可以是来自PCF实体，也可以是来自其它SMF实体，还可以是来自AMF实体。后续将会根据不同情形进行分别说明。
第一SMF实体根据终端群组信息，至少可以获取到终端群组内的终端的会话上下文，例如PDU会话上下文。根据终端的会话上下文可以获取第一SMF实体服务的终端所接入的UPF实体。
例如，终端群组包括UE1、UE2、UE3，其中，UE1对应UPF1、UE2对应UPF2、UE3对应UPF3，且UPF1和UPF2为第一SMF实体覆盖的UPF实体，UPF3不属于第一SMF实体覆盖的UPF实体。则，第一SMF实体根据终端的上下文，获取到UPF1、UPF2，即确定终端群组内 的终端接入的UPF实体为{UPF1、UPF2}。
步骤202、第一SMF实体根据UPF实体，确定目标UPF实体。
该目标UPF实体为用于终端群组内的终端之间的通信。这里的通信指的是本地通信，也可以理解为闭环通信。即，该目标UPF实体在接收到来自第一终端的通信数据后，是通过本地路由信息将该通信数据发送至第二终端接入的基站，或者发送至第二终端接入的UPF实体。而不是像现有技术那样，将通信数据发送至第一终端接入的另一个UPF实体，或者发送至DN。
例如，针对终端群组内的UE1和UE2，若终端1的用户面路径上包括的UPF实体为UPF1、UPF2，RAN1为UE1接入的基站，且UPF1为与RAN1连接的UPF。UE2的用户面路径上包括的UPF实体为UPF3、UPF4，RAN1为UE2接入的基站，且UPF3为与RAN2连接的UPF。
若按照现有技术的通信方法，终端1与终端2之间的通信数据的经过路径为：
UE1->RAN1->UPF1->UPF2->DN->UPF4->UPF3->RAN2->UE2。
而按照本申请的通信方法，若将UPF1选择为目标UPF实体，则UE 1与UE 2之间的通信数据的经过路径可以是：
UE1->RAN1->UPF1(目标UPF)->RAN2->UE2。
或者也可以是：
UE1->RAN1->UPF1(目标UPF)->UPF3->RAN2->UE2。
或者也可以是：
UE1->RAN1->UPF1(目标UPF)->UPF4->UPF3->RAN2->UE2。
具体采用哪种方式，可根据实际需要而定。较优地，可采用第一种实现方法，即UE1->RAN1->UPF1(目标UPF)->RAN2->UE2。
需要说明的是，上述RAN1和RAN2可以是相同的RAN，也可以是不同的RAN，对此不做限定。
本申请给出的上述几种更新后的路径，不管采用哪种，相较于现有技术，都缩短了终端之间的通信数据的转发路径。尤其是针对上述第一种实现方法，将终端群组内的终端重定向至同一UPF实体，即目标UPF实体，实现终端群组内的终端之间的通信在目标UPF实体处本地通信，缩短了通信路径，从而降低了通信时延。
下面结合具体的例子进行说明，分不同情形进行说明。
情形一、终端群组内的终端接入的是同一个UPF实体，且对应同一个SMF实体
该情形一中，当终端群组内的所有终端对应的是同一个SMF实体，即由同一个SMF实体管理，则PCF实体确定该SMF实体为第一SMF实体。PCF实体向第一SMF实体发送第一指示信息，第一指示信息用于指示第一SMF实体选择用于终端群组内的终端进行通信的UPF实体，所述指示信息携带终端群组信息。所述终端群组信息包括终端群组内的终端的标识，可选地，还包括终端群组的标识。
当终端群组内的所有终端接入的是同一个UPF实体，则第一SMF实体将该UPF实体确定为目标UPF实体。
如图3所示，为本申请提供的终端群组内的终端的UPF和SMF示意图。其中，终端群组内包括5个终端，分别为UE1、UE2、UE3、UE4、UE5。且在用户面路径上均接入同一个 UPF实体，在控制面路径上，均由同一个SMF实体管理。
该示例中，PCF实体确定该SMF实体为第一SMF实体，第一SMF实体确定该UPF实体为目标UPF实体。
进一步地，作为一种实现方式，第一SMF实体还创建本地路由信息，并将该本地路由信息发送给目标UPF实体。该本地路由信息用于记录终端群组内的每个终端的下行隧道与该终端的关联关系，从而，目标UPF实体可根据该本地路由信息，将源终端的通信数据转发给目的终端，其中，通信数据中包含目的终端的地址信息。
当然，作为另一种实现方式，若目标UPF实体本身具有本地路由能力，则第一SMF实体不需要向目标UPF实体发送本地路由信息，而只需要向目标UPF实体发送一个指示信息，指示其进行本地路由，也可实现将源终端的通信数据，直接转发给目的终端。
以及，作为另一种实现方式，当目标UPF实体本身具有本地路由能力，则第一SMF实体可以不向目标UPF实体发送本地路由信息，也不向目标UPF实体发送上述指示信息，即，目标UPF实体本身就具有本地通信能力。
对于上述任一实现方式，可选地，第一SMF实体可以向目标UPF实体发送一些计费规则等信息。
情形二、终端群组内的终端接入的是不同的UPF实体，且对应同一个SMF实体
该情形二中，当终端群组内的所有终端对应的是同一个SMF实体，即由同一个SMF实体管理，则PCF实体确定该SMF实体为第一SMF实体。
PCF实体在确定了第一SMF实体之后，则向该第一SMF实体发送第一指示信息，该第一指示信息用于指示第一SMF实体选择用于终端群组内的终端进行通信的UPF实体。即，PCF实体通过第一指示信息，指示第一SMF实体选择一个目标UPF实体。
该情形二中，由于终端群组内的终端接入的是不同的UPF实体，则第一SMF实体需要从这些UPF实体中选择一个UPF实体，作为目标UPF实体。当然，也可以是从其它UPF实体中选择目标UPF实体。
第一SMF实体可根据下列因素中的一个或多个，从终端群组内的终端接入的UPF实体中或其他UPF实体中，选择目标UPF实体：
因素1、终端接入的UPF实体中每个UPF实体的服务范围和终端群组内的终端的位置。
因素2、终端接入的UPF实体中每个UPF实体服务的终端群组内的终端的数量。
因素3、终端接入的UPF实体中每个UPF实体的负荷。
如图4所示，为本申请提供的终端群组内的终端的UPF和SMF示意图。其中，终端群组内包括5个终端，分别为UE1、UE2、UE3、UE4和UE5。且在用户面路径上，UE1-UE3接入UPF1，UE4接入UPF2，UE5接入UPF3，在控制面路径上，均由同一个SMF实体管理。
结合图4所示的示例，针对上述因素1，可根据UPF1-UPF3中每个UPF的服务范围和UE1-UE5中每个UE的位置关系，例如，UE是否离UPF实体的服务范围的中心位置比较近，距离越近，则移出UPF实体的概率越低。一般地，如果终端群组内的终端相互之间的距离较近时，在物理上，可将终端群组内的终端作为一个整体，根据该终端群组与UPF实体之间的物理位置关系，来选择UPF实体。具体的，若终端群组越接近一个UPF实体的中心位置，则更倾向于选择该UPF实体。
结合图4所示的示例，针对上述因素2，可根据每个UPF实体服务的终端群组内的数量，选择目标UPF。例如，从服务的终端的数量最多的几个UPF实体中选择目标UPF实体。针对图4，UPF1服务3个终端，UPF2服务1个终端，UPF3服务1个终端，则优先考虑选择UPF1作为目标UPF实体。
结合图4所示的示例，针对上述因素3，可根据终端接入的UPF实体中每个UPF实体的负荷，选择目标UPF。例如，从负荷最小的几个UPF实体中选择目标UPF实体。
在具体选择目标UPF实体时，可根据上述因素中的一个或多个，综合考虑，选择一个目标UPF。该目标UPF可以是终端群组内的终端接入的UPF实体中的一个UPF实体，也可以是终端群组内的终端接入的UPF实体之外的其他UPF实体，该其他UPF实体也受该第一SMF实体管理。例如，当根据上述因素，不能从终端群组内的终端接入的UPF实体中选择一个较佳的UPF实体时，则可以考虑选择其他UPF实体。
针对图4所示的示例，例如，最终选择UPF1作为目标UPF实体，则当UE1-UE5之间需要相互通信时，都可以通过UPF1本地转发。例如，UE1向UE4发送通信数据，则通信数据的通信路径可以是：UE1->RAN1->UPF1->RAN2->UE4。如果按照现有技术，则通信数据的通信路径为：UE1->RAN1->UPF1->DN->UPF2->RAN2->UE4。显然，本申请的方法可以缩短通信数据的传输路径，因而可降低延迟。
情形三、终端群组内的终端接入的是不同的UPF实体，且对应不同的SMF实体
该情形三中，当终端群组内的终端对应的不同的SMF实体时，可由PCF实体从这些SMF实体中选择一个SMF实体，作为第一SMF实体。
例如，PCF实体可以获取终端群组信息，终端群组信息至少包括终端群组内的终端的标识，可选地，还包括终端群组的标识，终端群组的标识用于标识一个终端群组，终端的标识用于标识终端。
具体地，PCF实体可以从控制面功能实体或应用服务器，接收终端群组信息。控制面功能实体或应用服务器中的终端群组信息可以是控制面功能实体或应用服务器建立终端群组时生成的，也可以是终端群组的某个终端建立终端群组后发送至控制面功能实体或应用服务器的。
PCF实体在获取到终端群组信息后，可根据终端群组内的终端的标识，确定第一SMF实体。例如，PCF实体根据终端群组内的终端的标识，通过终端标识对应的上下文，确定每个终端对应的SMF实体。例如，参考图5，为本申请提供的终端群组内的终端的UPF和SMF示意图。其中，终端群组内包括5个终端，分别为UE1、UE2、UE3、UE4、UE5。且在用户面路径上，UE1-UE3接入UPF1，UE4接入UPF2，UE5接入UPF3，在控制面路径上，UE1-UE4对应SMF1，UE5对应SMF2。从而可确定终端群组内的终端对应的SMF实体为SMF1、SMF2。
接着，从SMF1和SMF2中选择一个SMF实体，作为第一SMF实体。在选择第一SMF实体的时候，一种实现方式为，PCF实体根据终端群组内的终端对应的SMF实体中，每个SMF实体服务的终端群组内的终端的数量，确定第一SMF实体。例如，针对图5，SMF1服务的终端为UE1-UE4，数量为4，SMF2服务的终端为UE5，数量为1，因此选择SMF1作为第一SMF。当然，在具体应用中，也可以根据其他方法选择第一SMF实体，例如，还可以选择终端群组对应的SMF实体之外的SMF实体，作为第一SMF实体。即，选择的第一SMF实体不 是终端群组的终端对应的SMF实体。本申请对此不作具体限定。
PCF实体在确定了第一SMF实体之后，可根据终端群组内的终端的信息，确定指示第一SMF实体选择用于终端群组内的终端之间的通信的方法，例如，至少有以下两种指示方法。
指示方法一、PCF实体向第一SMF实体发送第二指示信息，然后向目标网元发送通知消息
其中，目标网元为AMF实体或第二SMF实体。
第二SMF实体指的是终端群组的终端对应的SMF实体中，除第一SMF实体之外的SMF实体。例如，参考图5，若SMF1是第一SMF实体，则SMF2为第二SMF实体。
具体地，PCF实体先向第一SMF实体发送第二指示信息，该第二指示信息用于指示第一SMF实体选择用于终端群组内的第二终端进行通信的UPF实体，其中，第二终端指的是终端群组中由第一SMF实体管理的终端，也可以理解为，第二终端为终端群组内的对应第一SMF实体的终端。结合图5，第二终端即为UE1-UE4。
由于第一SMF实体管理的是部分终端，因此，第一SMF实体可以为自己管理的终端选择一个目标UPF实体，例如，第一SMF实体选择UPF1作为目标UPF实体。
第一SMF实体在选择了目标UPF实体之后，将目标UPF实体存储。存储方法包括但不限于以下几种方法：
存储方法一、将目标UPF实体和终端群组的标识，存储至终端群组内的终端的会话上下文
例如，目标UPF实体为UPF1，在终端的会话上下文为：
UE1的会话上下文包括：终端群组的标识、UPF1的标识；
UE2的会话上下文包括：终端群组的标识、UPF1的标识；
UE3的会话上下文包括：终端群组的标识、UPF1的标识；
UE4的会话上下文包括：终端群组的标识、UPF1的标识；
UE5的会话上下文包括：终端群组的标识、UPF1的标识。
再比如，终端的会话上下文还可以为：
UE1的会话上下文包括：终端群组的标识、UPF1的地址信息；
UE2的会话上下文包括：终端群组的标识、UPF1的地址信息；
UE3的会话上下文包括：终端群组的标识、UPF1的地址信息；
UE4的会话上下文包括：终端群组的标识、UPF1的地址信息；
UE5的会话上下文包括：终端群组的标识、UPF1的地址信息。
存储方法二、本地存储目标UPF实体和终端群组的标识之间的对应关系
第一SMF实体本地存储UPF1的标识和终端群组的标识之间的对应关系，例如可以以表格形式，或函数映射关系存储等，本申请不做限制。
PCF实体在向第一SMF实体发送第二指示信息之后，进一步地，还向目标网元发送通知消息，通知消息包括终端群组信息、第一SMF实体的地址信息，该通知消息用于指示目标网元将第一SMF实体插入到终端群组内的第三终端的会话，以及指示第一SMF实体选择用于第三终端进行通信的UPF实体。
例如，参考图5，若目标网元为第二SMF实体，图5中的SMF2即为一个第二SMF实体。 当然，如果终端群组的终端还对应SMF3、SMF4，则SMF3、SMF4也称为第二SMF实体，即第二SMF实体包括SMF3、SMF4。
PCF实体向SMF2发送通知消息，其中包括SMF1(第一SMF实体)的地址信息、终端群组信息，可选地，还包括指示信息，该指示信息是需要SMF2发送给SMF1的，用于指示SMF1选择用于终端群组的第三终端进行通信的UPF实体。当然，也可以不包括该指示信息，通过隐式方式指示，下面会具体说明。
其中，第三终端指的是第二SMF实体服务的终端群组内的终端，在图5中，第三终端指的是UE5。
SMF2在接收到上述信息后，一方面，将SMF1插入到UE5的会话，例如插入到UE5的PDU会话。另一方面，SMF2还向SMF1发送第一请求消息，该第一请求消息用于请求SMF1为第三终端，即UE5选择终端群组通信的UPF实体。
可选地，若SMF2接收到PCF实体发送的通知消息中包括指示信息，则SMF2将该指示信息携带于第一请求消息中发送至SMF1。若通知消息中不包括指示信息，则SMF2直接将终端群组信息携带于第一请求消息发送至SMF1，隐式指示SMF1为第三终端选择通信的UPF实体。
其中，这里，SMF2向SMF1发送的终端群组信息包括终端群组的标识和终端群组中的第三终端的标识，或者是，发送的终端群组信息包括终端群组的标识和终端群组中的所有终端的标识。
SMF1在接收到SMF2的第一请求消息后，从终端群组的终端的上下文中，或者从本地存储的目标UPF实体和终端群组的标识之间的对应关系中，获取到SMF1实体之前为第二终端(即UE1-UE4)选择的目标UPF实体(即UPF1)，然后将该目标UPF实体，作为第三终端(即UE5)的目标UPF实体。
换句话说，SMF1根据PCF实体的指示，选择了UPF1作为UE1-UE4的目标UPF实体，然后又接收到SMF2发送的第一请求消息，则SMF1直接将该UPF1作为UE5的目标UPF实体。
当然，如果上述目标网元是AMF实体，则实现方式类似，不再赘述。
指示方法二、PCF实体直接向目标网元发送通知消息
该指示方法中，PCF实体不向第一SMF实体发送第二指示信息，而是直接向目标网元发送通知消息，该通知消息包括终端群组信息、第一SMF实体的地址信息，该通知消息用于指示目标网元将第一SMF实体插入到终端群组内的第三终端的会话，以及指示第一SMF实体选择用于第三终端进行通信的UPF实体，或者用于指示第一SMF实体选择用于终端群组的所有终端进行通信的UPF实体。
例如，参考图5，以目标网元为第二SMF实体为例。其中，第一SMF实体为SMF1，第二SMF实体为SMF2，则PCF实体直接向SMF2发送通知消息，该通知消息包括SMF1的地址信息、终端群组信息，可选地，还包括指示信息，该指示信息用于指示SMF1为UE1-UE5选择用于群组通信的UPF实体，或者，该指示信息用于指示SMF1为UE5选择用于群组通信的UPF实体。
SMF2接收到PCF实体的通知消息后，向SMF1发送第二请求消息，该第二请求消息用于请求SMF1选择终端群组内的UE5进行通信的UPF实体，或者用于请求SMF1选择终端群组 内的UE1-UE5进行通信的UPF实体。
可选地，若SMF2从PCF实体接收到的通知消息中包括指示信息，则该第二请求消息包括该指示信息，若SMF2从PCF实体接收到的通知消息中不包括指示信息，则SMF2直接将终端群组信息携带于第二请求消息发送至SMF1，隐式指示SMF1为UE1-UE5选择通信的UPF实体，或隐式指示SMF1为UE5选择通信的UPF实体。
其中，这里，SMF2向SMF1发送的终端群组信息包括终端群组的标识和终端群组中的第三终端的标识，或者是，发送的终端群组信息包括终端群组的标识和终端群组中的所有终端的标识。SMF1在接收到SMF2的第二请求消息后，为SMF1管理的终端和SMF2管理的终端，选择一个目标UPF实体，例如，SMF1选择UPF1作为目标UPF实体。
在该情形三中，第一SMF实体选择目标UPF实体的具体方法，可参考上述情形二中选择目标UPF实体的具体说明，这里不再赘述。
因此，在选择了目标UPF实体之后，终端群组的终端之间的通信则通过该UPF实体本地路由，可缩短通信路径，因而可以缩短通信数据的传输路径，进而降低延迟。
在上述三种情形中，在第一SMF实体选择了终端群组的终端进行通信的目标UPF实体之后，还需要更新其中部分网元的用户面的隧道信息。下面分别说明。
针对上述情形一，终端群组内的终端对应同一个UPF实体，且对应同一个SMF实体，则第一SMF实体不需要更新隧道信息。
针对上述情形二、终端群组内的终端对应不同的UPF实体，且对应同一个SMF实体，则第一SMF实体可以向目标UPF实体发送第一通知消息，其中包括第一终端的隧道信息，第一终端指示的是除目标UPF实体服务的终端之外的终端，即第一终端接入的UPF实体不同于该目标UPF实体。例如，参考图4，若UPF1为目标UPF实体，则第一终端指的是UE4、UE5。
第一终端的隧道信息包括终端接入的基站的隧道信息或UPF隧道信息，具体地，参考图4，包括UE4接入的基站的隧道信息、UE5接入的基站的隧道信息、UPF2的隧道信息、UPF3的隧道信息。
以及，第一SMF实体还向第一终端接入的基站发送第二通知消息，第二通知消息包括目标UPF实体的隧道信息。例如，参考图4，还向UE4、UE5发送第二通知消息，其中包括UPF1的隧道信息。
通过更新隧道信息，可建立不同网元之间的路径，使得目标UPF实体与第一终端的基站之间可以互相通信。
可选地，还可以释放掉第一终端接入的UPF实体的资源，例如释放UPF2、UPF3的资源。
针对上述情形三，针对上述指示方法一，目标网元发送给第一SMF实体的第一请求消息中还包括第三终端接入的基站的隧道信息，和/或，第三终端接入的UPF实体的隧道信息。
针对上述指示方法二，目标网元发送给第二SMF实体的第二请求消息中包括第三终端接入的基站的隧道信息，和/或，第三终端接入的UPF实体的隧道信息。
例如，参考图5，SMF2向SMF1发送的第一请求消息或第二请求消息中，还包括UE5接入的基站的隧道信息，和/或，UPF3的隧道信息。SMF1在接收到这些隧道信息后，将UE5接入的基站的隧道信息、UPF3的隧道信息，以及UE4接入的基站的隧道信息、UPF2的隧道 信息发送给UPF1(目标UPF实体)，进而UPF1可更新隧道信息。进一步地，SMF1还向UE4、UE5发送UPF1的隧道信息，则UE4和UE5可更新隧道信息。
通过更新隧道信息，可建立不同网元之间的路径，使得目标UPF实体与第一终端(UE4、UE5)的基站之间可以互相通信。
本申请，通过确定一个目标UPF实体，该目标UPF实体用于终端群组内的终端之间的本地通信，或称为闭环通信，因而可缩短终端群组内的终端之间的通信路径，进而可降低通信延迟。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
下面结合附图，通过具体的实施例，来进一步介绍本申请的通信方法。
下面的实施例均以终端群组为车队为例进行说明，终端群组内的终端也可以称为车队成员，终端群组信息也可以称为车队信息，包括车队标识和车队成员的标识。应用域的控制功能实体可以是V2X控制功能实体，应用服务器可以是V2X应用服务器。目标UPF实体也可以称为服务UPF实体。
车队可以是由车队内的UE发起建立，或者是由V2X控制功能实体(V2X control Function，V2X-C)或V2X应用服务器(V2X Applicaton Server，V2X-AS)发起建立。如果是由UE发起建立，则UE生成车队信息并发送给V2X-C或V2X-AS，车队信息至少包括车队标识和车队成员(即UE)的标识。如果是由V2X-C或V2X-AS发起建立，则V2X-C或V2X-AS生成上述车队信息。当然，也可以是在UE与V2X-C，和/或，V2X-AS的共同配合下完成车队建立，例如，由UE生成车队成员信息，然后由V2X-C，和/或，V2X-AS生成每个车队成员的标识(ID)。本申请实施例不做限定。
实施例1
该实施例1的场景为：车队成员列表中的UE属于同一个UPF，且属于同一个SMF。如图6所示，为实施例1所适用的网络架构示意图，其中，以车队成员列表中的两个UE，即UE1和UE2为例进行说明。在图6所示的场景中，UE1和UE2的用户面路径均包括UPF和A-UPF(锚点UPF)。
当前，若按照现有技术的通信方法，则UE1向UE2发送的数据的流向为：UE1->基站1(RAN1)->UPF->A-UPF->V2XDN->A-UPF->UPF->RAN2->UE2。
从目前车队内的UE之间的通信流程可以看出，通信需要经过的网元较多，时延较大，为解决该问题，如图7所示，为本申请实施例提供的一种通信方法，包括以下步骤：
步骤1、V2X-C或V2X-AS向PCF发送车队信息，PCF接收来自V2X-C或V2X-AS的车队信息。
步骤2、PCF确定车队信息中的UE均位于同一SMF。
PCF根据接收到的车队信息，本地获取车队成员的上下文，从车队成员的上下文中获取每个UE所在的SMF，并且，PCF确定所有UE所在的SMF为同一SMF。
步骤3、PCF向SMF发送指示信息，SMF接收来自PCF的指示信息。
该指示信息中携带车队信息，该指示信息用于指示SMF为车队选择服务UPF，其中，该SMF即为步骤2中确定的所有UE所在的SMF。
步骤4、SMF确定车队信息中的UE均位于同一UPF。
SMF根据车队信息，本地获取车队成员的上下文，从车队成员的上下文中获取每个UE所在的UPF，并且，SMF确定所有UE所在的UPF为同一UPF，SMF将该UPF作为服务UPF。
步骤5、SMF向UPF发送本地环回路由信息，UPF接收来自SMF的本地环回路由信息。
本地环回路由信息包括车队成员列表中的UE与下行隧道之间的对应关系，例如，表1给出了以表格的形式来表示本地环回路由信息的一种示例。
表1本地环回路由信息
车队成员的标识 下行隧道
UE1 t1
UE2 t2
…… ……
参考图6，t1隧道为UPF与RAN1之间的下行隧道，t2为UPF与RAN2之间的下行隧道。
UPF在接收到该本地环回路由信息之后，后续将使用该本地环回路由信息转发UE之间的通信数据。例如，当UE1需要向UE2发送数据时，按照该实施例的通信方法，则通信流程为：UE1->RAN1->UPF->RAN2->UE2。其中，该UPF也称为服务UPF。
步骤6、UPF向SMF发送响应消息，SMF接收来自UPF的响应消息。
该步骤6为可选步骤，用于向SMF应答接收到本地环回路由信息。
步骤7、SMF向UDM发送车队信息。
UDM可将接收到的车队信息存储，以便其他网元可以使用该车队信息。
该步骤7为可选步骤，或者，该步骤7也可以在步骤3之后的任一步骤执行。
因此，通过该实施例方法，UE之间的通信，在服务UPF内形成本地通信，可减少数据从UE1到达UE2的时延，有利于车队成员之间的即时通信。
实施例2
该实施例2的场景为：车队成员列表中的车队成员(UE)属于不同的UPF，但属于相同的SMF。如图8(a)所示，为实施例2所适用的网络架构示意图，其中，以车队成员列表中的两个UE，即UE1和UE2为例进行说明。在图8(a)所示的场景中，UE1的用户面路径包括UPF1和A-UPF1(锚点UPF)，UE2的用户面路径包括UPF2和A-UPF2(锚点UPF)。也可以理解为：UE1属于UPF1、A-UPF1、SMF，UE2属于UPF2、A-UPF2、SMF。
当前，若按照现有技术的通信方法，则UE1向UE2发送的数据的流向为：UE1->基站1(RAN1)->UPF1->A-UPF1->V2XDN->A-UPF2->UPF2->基站2(RAN2)->UE2。
从上述UE之间的通信流程可以看出，通信需要经过的网元较多，时延较大，为解决该问题，如图9所示，为本申请实施例提供的一种通信方法，包括以下步骤：
步骤1、V2X-C或V2X-AS向PCF发送车队信息，PCF接收来自V2X-C或V2X-AS的车队信息。
步骤2、PCF确定车队信息中的UE均位于同一SMF。
PCF根据接收到的车队信息，本地获取车队成员的上下文，从车队成员的上下文中获取每个UE所在的SMF，并且，PCF确定所有UE所在的SMF为同一SMF。
步骤3、PCF向SMF发送指示信息，SMF接收来自PCF的指示信息。
该指示信息中携带车队信息，该指示信息用于指示SMF为车队选择服务UPF，其中，该SMF即为步骤2中确定的所有UE所在的SMF。
步骤4、SMF决策将UPF1作为服务UPF。
SMF根据车队信息，本地获取车队成员的上下文，从车队成员的上下文中获取每个UE所在的UPF，进而，SMF确定UE1属于UPF1、A-UPF1，确定UE2属于UPF2、A-UPF2，则SMF从UPF1和UPF2中选择一个UPF，作为服务UPF。
选择服务UPF的方法，例如可以包括下列方法中的一个或多个：
1)、UE1和UE2用户面路径上UPF的负荷，即根据UPF1和UPF2的负荷，选择负荷小的UPF作为服务UPF。
2)、选择服务车队内UE的数量最多的UPF，作为服务UPF。
3)、选择距离车队内UE位置最近的UPF，作为服务UPF。
可选地，还可以是选择一个新的UPF作为服务UPF，新的UPF指的是，不包括车队的UE的UPF。
这里，以选择UPF1作为服务UPF为例进行说明。
步骤5、SMF向UPF1发送用户面建立消息，UPF1接收SMF的用户面建立消息。
该用户面建立消息包括UE2的用户面信息、本地环回路由信息、A-UPF2的隧道信息，其中，UE2的用户面信息包括UPF1向RAN2的隧道信息。
当UPF1接收到用户面建立消息后，则UPF1可获取UPF1到RAN2的路径，以及UPF1到A-UPF2的路径。
其中，本地环回路由信息的内容和作用，可参考上述实施例1中的表格1，这里不再赘述。
步骤6、UPF1向SMF发送响应消息，SMF接收来自UPF1的响应消息。
该步骤6为可选步骤，用于向SMF应答接收到通知消息。
步骤7、SMF向基站2(RAN2)发送UPF重选通知消息，基站2(RAN2)接收来自SMF的UPF重选通知消息。
其中，UPF重选通知消息包括UPF1下行用户面(指的是UE2的用户面)隧道信息。从而，基站2(RAN2)可以获取到UPF1的路径，即建立基站2(RAN2)到UPF1的用户面路径。
步骤8、基站2(RAN2)向SMF发送响应消息，SMF接收来自基站2(RAN2)的响应消息。
该步骤8为可选步骤，用于向SMF应答接收到UPF重选通知消息。
步骤9、SMF向A-UPF2发送用户面更新消息，A-UPF2接收来自SMF的用户面更新消息。
该用户面更新消息用于更新用户面隧道信息，所述用户面更新消息携带UPF1上行用户面隧道信息，从而，建立A-UPF2到UPF1的用户面路径。
步骤10、A-UPF2向SMF发送响应消息，SMF接收来自A-UPF2的响应消息。
该步骤10为可选步骤，用于向SMF应答接收到用户面更新消息。
步骤11、SMF向UPF2发送UE用户面释放消息，UPF2接收来自SMF的UE用户面释放消息。
UPF2在接收到该UE用户面释放消息后，释放UPF2与RAN2之间的用户面隧道信息。
步骤12、SMF向UDM发送车队信息。
UDM可将接收到的车队信息存储，以便其他网元可以使用该车队信息。
该步骤12为可选步骤，或者，该步骤12也可以在步骤3之后的任一步骤执行。
通过该实施例的方法，网络侧可将车队内UE重定向至同一UPF，该UPF作为车队服务UPF，车队内UE之间的通信在服务UPF处实现本地通信，该实施例中，SMF决策将UPF1作为车队服务UPF，为UE2执行UPF重选，从UPF2重选至UPF1。因此，将UE2重选至UPF1之后，图8(a)所示的系统架构则更新为图8(b)所示的系统架构，即建立了RAN2与UPF1之间的路径，及UPF1与A-UPF2之间的路径，并释放UPF2与RAN2之间的路径，从而，当UE1需要向UE2发送数据时，按照该实施例的通信方法，则通信流程为：UE1->RAN1->UPF1->RAN2->UE2。其中，该UPF1也称为服务UPF。该实施例方法可减少数据从UE1到达UE2的时延，有利于车队成员之间的即时通信。
实施例3
该实施例3的场景为：车队成员列表中的UE属于不同的UPF，但属于相同的SMF。如图10(a)所示，为实施例3所适用的网络架构示意图。该应用场景与图10(a)所示的应用场景的主要区别为：图10(a)中，UE2的用户面只有一个UPF，即锚点UPF，称为A-UPF2，当SMF将UPF1选择为服务UPF时，由于锚点UPF的用户面隧道不能释放，也就是说，不能按照实施例2的方法，将UE2重选至UPF1并释放A-UPF2的用户面隧道信息，因此，在该实施例3的场景中，可以使用插入服务UPF的方法，完成UPF的重定向。
如图10(b)所示，将UPF1插入到RAN2与A-UPF2之间，并分别更新UPF1、RAN2、A-UPF2的隧道信息，从而，也可以实现减少UE1与UE2之间的数据传输时延，例如，当UE1需要向UE2发送数据时，按照该实施例的通信方法，则通信流程为：UE1->RAN1->UPF1->RAN2->UE2。其中，该UPF1也称为服务UPF。该实施例方法可减少数据从UE1到达UE2的时延，有利于车队成员之间的即时通信。
实施例4
该实施例4的场景为：车队成员列表中的UE属于不同的UPF，以及属于不同的SMF。如图11(a)所示，为实施例4所适用的网络架构示意图，其中，以车队成员列表中的两个UE，即UE1和UE2为例进行说明。在图11(a)所示的场景中，UE1的用户面路径包括UPF1和A-UPF1(锚点UPF)，UE2的用户面路径包括UPF2和A-UPF2(锚点UPF)，也可以理解为， UE1属于UPF1、A-UPF1、SMF1，UE2属于UPF2、A-UPF2、SMF2。
需要说明的是，在该实施例的场景中，每个UE的用户面路径中可以只有一个锚点UPF，也可以是有一个锚点UPF和多个其他UPF，例如，参考图11(a)，以UE1为例，则UE1的用户面路径只有A-UPF1，即删除图中的UPF1，也可以是有A-UPF1和多个其他UPF(图中只示出了一个UPF，即UPF1)。该实施例，每个UE的用户面路径中的UPF数量至少为一个即可。
下面，以图11(a)所示的场景为例进行说明。当前，若按照现有技术的通信方法，则UE1向UE2发送的数据的流向为：UE1->基站1(RAN1)->UPF1->A-UPF1->DN->A-UPF2->UPF2->基站2(RAN2)->UE2。
从上述UE之间的通信流程可以看出，通信需要经过的网元较多，时延较大，为解决该问题，如图12所示，为本申请实施例提供的一种通信方法，包括以下步骤：
步骤1、V2X-C或V2X-AS向PCF发送车队信息，PCF接收来自V2X-C或V2X-AS的车队信息。
步骤2、PCF确定SMF1为服务SMF。
该步骤中，PCF在接收到车队信息后，根据车队信息，本地获取车队成员的上下文，根据上下文，可获取每个UE所在的SMF，并确定车队内的UE属于不同的SMF，具体地，属于至少两个SMF。例如，车队成员为UE1、UE2、UE3、UE4和UE5，UE1、UE2和UE3属于SMF1，UE4和UE5属于SMF2，再比如，UE1、UE2和UE3属于SMF1，UE4属于SMF2，UE5属于SMF3，等等。本实施例，以两个UE，即UE1和UE2为例，例如，UE1属于SMF1，UE2属于SMF2。
进一步地，PCF选择一个SMF作为SMF，选择服务SMF的方法例如可以是：选择覆盖车队内UE的数量最多的SMF，作为服务SMF。
可选地，还可以选择一个新的SMF，作为服务SMF，新的SMF指的是，不包括车队的UE的SMF。
本实施例中，以PCF选择SMF1作为服务SMF为例进行说明。
步骤3、PCF向SMF2发送通知消息，SMF2接收来自PCF的通知消息。该通知消息用于通知SMF2，将SMF1插入UE2的PDU会话，即将SMF1也作为UE2所属的SMF。
其中，通知消息包括：
1)、SMF1的地址和第一指示信息，该第一指示信息用于指示SMF2将SMF1插入UE2的PDU会话，即将SMF1也作为UE2所属的SMF。
2)车队信息。该车队信息需要由SMF2转发给SMF1。
可选地，还包括：
3)、第二指示信息，该第二指示信息是需要由SMF2转发给SMF1，用于指示SMF1为车队的UE选择服务UPF。当然，也可以不包括该第二指示信息，即可以隐式指示SMF1为车队的UE选择服务UPF。
步骤4、SMF2向SMF1发送会话建立请求消息，SMF1接收来自SMF2的会话建立请求消息。
该会话建立请求消息包括：
1)、UPF2的用户面下行隧道。
2)、RAN2的上行隧道信息。
3)、车队信息。
可选地，还包括：
4)、第二指示信息。
其中，信息3)和4)来自PCF实体。
SMF1接收到会话建立请求消息后，选择服务UPF，选择的方法为可参考实施例2中选择UPF的方法，这里不再赘述。
本实施例，以选择UPF1作为服务UPF为例进行说明。
需要说明的是，上述步骤3和步骤4中，是PCF实体先向SMF2发送通知消息，然后SMF2再向SMF1发送会话建立请求消息。可选地，上述步骤3和步骤4还可以由以下步骤Aˉ步骤C替换：
步骤A、PCF向SMF1发送通知消息，SMF1接收来自PCF的通知消息。
通知消息中包括车队信息，车队信息包括车队标识和车队成员的标识，可选地，可以是包括所有车队成员的标识，也可以是只包括由SMF1管理的车队成员的标识。
可选地，通知消息中还包括指示信息，该指示信息用于指示SMF1选择服务UPF。
如果通知消息中不包括上述指示信息，则该通知消息通过发送的车队信息，隐式指示SMF1选择服务UPF。
SMF1在接收到该通知消息后，选择服务UPF，例如选择UPF1作为服务UPF。并且，还将服务UPF进行存储，存储方式可参见前述实施例的具体描述，这里不再赘述。
步骤B、PCF向SMF2发送通知消息，SMF2接收来自PCF的通知消息。
该通知消息用于通知SMF2，将SMF1插入UE2的PDU会话，即将SMF1也作为UE2所属的SMF。
其中，该通知消息包括的内容与前述步骤3中描述的通知消息携带的内容相同，这里不再赘述，可参考前述描述。
步骤C、SMF2向SMF1发送会话建立请求消息，SMF1接收来自SMF2的会话建立请求消息。
该会话建立请求消息包括的内容可参考前述步骤4中描述的会话建立请求消息携带的内容。但需要说明的是，会话建立请求消息中携带的车队信息，可以是只包括车队中由SMF2管理的车队成员，也可以是包括车队中的所有成员。
SMF1接收到会话建立请求消息后，为SMF2管理的终端选择服务UPF，由于上述步骤A中，SMF1已经为SMF1管理的终端选择了服务UPF并进行存储，因此，这里，可以直接将SMF1已经选择的服务UPF，作为SMF2管理的终端的服务UPF，即将选择的UPF1作为SMF2管理的终端的服务UPF。
步骤5、SMF1向UPF1发送用户面建立消息，UPF1接收来自SMF1的用户面建立消息。
其中，用户面建立消息包括UPF2的隧道信息、RAN2的上行隧道信息和本地环回路由信息。
当UPF1接收到用户面建立消息后，则UPF1可建立UPF1到UPF2的路径，以及建立UPF1到RAN2的路径。
其中，本地环回路由信息的内容和作用，可参考上述实施例1中的表格1，这里不再赘 述。
步骤6、UPF1向SMF1发送响应消息，SMF1接收来自UPF1的响应消息。
该步骤6为可选步骤，用于向SMF1应答接收到通知消息。
步骤7、SMF1向SMF2发送响应消息，SMF2接收来自SMF1的响应消息。
该响应消息中包括UPF1的下行隧道。
步骤8、SMF2向UPF2发送用户面更新消息，UPF2接收来自SMF2的用户面更新消息。
该用户面更新消息中包括UPF1的隧道信息。
从而，UPF2可建立从UPF2到UPF1的路径。
步骤9、UPF2向SMF2发送响应消息，SMF2接收来自UPF2的响应消息。
该步骤9为可选步骤，用于向SMF2应答接收到用户面更新消息。
步骤10、SMF2向基站2(RAN2)发送用户面隧道更新消息，基站2(RAN2)接收来自SMF2的用户面隧道更新消息。
其中，该用户面隧道更新消息中包括UPF1的下行隧道，该UPF1的下行隧道由SMF2在上述步骤7中获取得到。
从而，基站2(RAN2)可更新用户面路径，建立基站2(RAN2)到UPF1的路径。
步骤11SMF1向UDM发送车队信息。
UDM可将接收到的车队信息存储，以便其他网元可以使用该车队信息。
该步骤11为可选步骤，或者，该步骤11也可以在步骤4之后的任一步骤执行。
通过该实施例的方法，网络侧可将车队内UE重定向至同一SMF，该SMF作为车队服务SMF，以及，重定向至同一UPF，该UPF作为车队服务UPF，车队内UE之间的通信在服务UPF处实现本地通信，该实施例中，服务SMF(即SMF1)决策将UPF1作为车队服务UPF，为UE2执行UPF插入，将UPF1插入RAN2与UPF2之间。将UPF1插入RAN2与UPF2之间之后，图11(a)所示的系统架构则更新为图11(b)所示的系统架构，即建立了RAN2与UPF1之间的路径，UPF1与UPF2之间的路径，以及UPF2与SMF1之间的路径，从而，当UE1需要向UE2发送数据时，按照该实施例的通信方法，则通信流程为：UE1->RAN1->UPF1->RAN2->UE2。其中，该UPF1也称为服务UPF。该实施例方法可减少数据从UE1到达UE2的时延，有利于车队成员之间的即时通信。
需要说明的是，该实施例4中由SMF2执行的流程，均可以替换为由AMF实体来实现，对于由AMF实体来实现上述实施例的具有过程，可参考SMF2的实现过程，不再赘述。基于相同的发明构思，如图13所示，为本申请提供的一种装置示意图，该装置可以是会话管理功能实体，可执行上述任一实施例中由第一会话管理功能实体(第一SMF实体)执行的方法。或者，该装置还可以是策略控制功能实体，可执行上述任一实施例中由策略控制功能实体(PCF实体)执行的方法。
该装置1300包括至少一个处理器131，收发器132，可选地，还包括存储器133。所述处理器131、收发器132、存储器133通过通信线路连接。
处理器131可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信线路可包括一通路，在上述单元之间传送信息。
所述收发器132，用于与其他设备或通信网络通信，收发器包括射频电路。
存储器133可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically erasable programmabler-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器133可以是独立存在，通过通信线路与处理器131相连接。存储器133也可以和处理器集成在一起。其中，所述存储器133用于存储执行本发明方案的应用程序代码，并由处理器131来控制执行。所述处理器131用于执行所述存储器133中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器131可以包括一个或多个CPU，例如图13中的CPU0和CPU1。
在具体实现中，作为一种实施例，装置1300可以包括多个处理器，例如图13中的处理器131和处理器138。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器，这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
应理解，当该装置为会话管理功能实体时，该装置可以用于实现本发明实施例的通信方法中由第一会话管理功能实体(第一SMF实体)执行的步骤，相关特征可以参照上文，此处不再赘述。
应理解，当该装置为策略控制功能实体时，该装置可以用于实现本发明实施例的通信方法中由策略控制功能实体(PCF实体)执行的步骤，相关特征可以参照上文，此处不再赘述。
本申请可以根据上述方法示例对会话管理功能实体进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图14示出了一种装置示意图，该装置可以是上述实施例中所涉及的第一会话管理功能实体(第一SMF实体)，该装置包括处理单元1401和通信单元1402。
在本实施例中，该会话管理功能实体以对应各个功能划分各个功能模块的形式来呈现，或者，该会话管理功能实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
应理解，该会话管理功能实体可以用于实现本发明实施例的通信方法中由第一会话管理功能实体(第一SMF实体)执行的步骤，相关特征可以参照上文，此处不再赘述。
本申请可以根据上述方法示例对策略控制功能实体进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图15示出了一种装置示意图，该装置可以是上述实施例中所涉及的策略控制功能实体，该装置包括处理单元1501和通信单元1502。
在本实施例中，该策略控制功能实体以对应各个功能划分各个功能模块的形式来呈现，或者，该策略控制功能实体以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
应理解，该策略控制功能实体可以用于实现本发明实施例的通信方法中由策略控制功能实体(PCF实体)执行的步骤，相关特征可以参照上文，此处不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
尽管在此结合各实施例对本发明进行了描述，然而，在实施所要求保护的本发明过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
本领域技术人员应明白，本申请的实施例可提供为方法、装置(设备)、计算机可读存储介质或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式，这里将它们都统称为“模块”或“系统”。
本领域技术人员还可以了解到本申请实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域 技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本申请实施例保护的范围。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中，ASIC可以设置于终端设备中。可选地，处理器和存储媒介也可以设置于终端设备中的不同的部件中。
在一个或多个示例性的设计中，本申请实施例所描述的上述功能可以在硬件、软件、固件或这三者的任意组合来实现。如果在软件中实现，这些功能可以存储与电脑可读的媒介上，或以一个或多个指令或代码形式传输于电脑可读的媒介上。电脑可读媒介包括电脑存储媒介和便于使得让电脑程序从一个地方转移到其它地方的通信媒介。存储媒介可以是任何通用或特殊电脑可以接入访问的可用媒体。例如，这样的电脑可读媒体可以包括但不限于RAM、ROM、EEPROM、CD-ROM或其它光盘存储、磁盘存储或其它磁性存储装置，或其它任何可以用于承载或存储以指令或数据结构和其它可被通用或特殊电脑、或通用或特殊处理器读取形式的程序代码的媒介。此外，任何连接都可以被适当地定义为电脑可读媒介，例如，如果软件是从一个网站站点、服务器或其它远程资源通过一个同轴电缆、光纤电脑、双绞线、数字用户线(DSL)或以例如红外、无线和微波等无线方式传输的也被包含在所定义的电脑可读媒介中。所述的碟片(disk)和磁盘(disc)包括压缩磁盘、镭射盘、光盘、DVD、软盘和蓝光光盘，磁盘通常以磁性复制数据，而碟片通常以激光进行光学复制数据。上述的组合也可以包含在电脑可读媒介中。
本申请是参照本申请的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
尽管结合具体特征及其实施例对本发明进行了描述，显而易见的，在不脱离本发明的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本发明的示例性说明，且视为已覆盖本发明范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (34)

  1. 一种通信方法，其特征在于，包括：
    第一会话管理功能实体根据终端群组信息，确定所述终端群组内的终端接入的用户面功能实体；
    所述第一会话管理功能实体根据所述用户面功能实体，确定目标用户面功能实体，所述目标用户面功能实体用于所述终端群组内的终端之间的通信。
  2. 根据权利要求1所述的方法，其特征在于，所述第一会话管理功能实体根据所述用户面功能实体，确定目标用户面功能实体，包括：
    所述第一会话管理功能实体根据下列因素中的一个或多个，从所述终端接入的用户面功能实体中或其他用户面功能实体中，选择所述目标用户面功能实体：
    所述终端接入的用户面功能实体中每个用户面功能实体的服务范围和所述终端群组内的终端的位置、所述终端接入的用户面功能实体中每个用户面功能实体服务的所述终端群组内的终端的数量、所述终端接入的用户面功能实体中每个用户面功能实体的负荷。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一会话管理功能实体向所述目标用户面功能实体发送第一通知消息，所述第一通知消息包括第一终端的隧道信息，所述第一终端接入的用户面功能实体不同于所述目标用户面功能实体。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述第一会话管理功能实体向所述第一终端接入的基站发送第二通知消息，所述第二通知消息包括所述目标用户面功能实体的隧道信息。
  5. 根据权利要求3或4所述的方法，其特征在于，所述方法还包括：
    所述第一会话管理功能实体释放所述第一终端接入的用户面功能实体的资源。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一会话管理功能实体接收来自策略控制功能实体的第一指示信息，所述第一指示信息用于指示所述第一会话管理功能实体选择用于所述终端群组内的终端进行通信的用户面功能实体。
  7. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一会话管理功能实体接收来自策略控制功能实体的第二指示信息，所述第二指示信息用于指示所述第一会话管理功能实体选择用于所述终端群组内的第二终端进行通信的用户面功能实体，所述第二终端为所述终端群组内的对应所述第一会话管理功能实体的终端；
    所述第一会话管理功能实体根据所述用户面功能实体，确定目标用户面功能实体，包括：
    所述第一会话管理功能实体根据所述第二终端接入的用户面功能实体，确定所述目标用户面功能实体。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述第一会话管理功能实体接收来自目标网元的第一请求消息，所述第一请求消息用于请求所述第一会话管理功能实体选择所述终端群组内的第三终端进行通信的用户面功能实体，所述第三终端为所述终端群组内的对应所述目标网元的终端；
    所述第一会话管理功能实体确定所述目标用户面功能实体，为所述第三终端进行通 信的用户面功能实体；
    其中，所述目标网元为第二会话管理功能实体或接入与移动性管理功能实体。
  9. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一会话管理功能实体接收来自目标网元的第二请求消息，所述第二请求消息用于请求所述第一会话管理功能实体选择所述终端群组内的第三终端进行通信的用户面功能实体，所述第三终端为所述终端群组内的对应所述目标网元的终端；
    所述第一会话管理功能实体根据所述用户面功能实体，确定目标用户面功能实体，包括：
    所述第一会话管理功能实体根据第二终端接入的用户面功能实体，确定所述目标用户面功能实体，所述第二终端为所述终端群组内的对应所述第一会话管理功能实体的终端；
    其中，所述目标网元为第二会话管理功能实体或接入与移动性管理功能实体。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一会话管理功能实体接收来自控制面功能实体或应用服务器的所述终端群组信息。
  11. 根据权利要求1至10中任一项所述的方法，其特征在于，所述终端群组信息包括所述终端群组的标识和所述终端群组内的终端的标识；
    所述方法还包括：
    所述第一会话管理功能实体将所述目标用户面功能实体和所述终端群组的标识，存储至所述终端群组内的终端的上下文，所述终端群组内的终端的上下文用于所述第一会话管理功能实体从所述终端群组内的终端的上下文，获取所述目标用户面功能实体；或者，
    所述第一会话管理功能实体本地存储所述目标用户面功能实体和所述终端群组的标识之间的对应关系，所述对应关系用于所述第一会话管理功能实体从所述对应关系获取所述目标用户面功能实体。
  12. 一种通信方法，其特征在于，包括：
    策略控制功能实体获取终端群组信息，所述终端群组信息至少包括所述终端群组内的终端的标识；
    所述策略控制功能实体根据所述终端群组内的终端的标识，确定第一会话管理功能实体，所述第一会话管理功能实体用于选择目标用户面功能实体，所述目标用户面功能实体用于所述终端群组内的终端之间的通信。
  13. 根据权利要求12所述的方法，其特征在于，所述策略控制功能实体根据所述终端群组内的终端的标识，确定第一会话管理功能实体，包括：
    所述策略控制功能实体根据所述终端群组内的终端的标识，确定所述终端群组内的终端接入的会话管理功能实体；
    所述策略控制功能实体根据所述终端接入的会话管理功能实体，确定所述第一会话管理功能实体。
  14. 根据权利要求13所述的方法，其特征在于，所述策略控制功能实体根据所述终端接入的会话管理功能实体，确定所述第一会话管理功能实体，包括：
    所述策略控制功能实体根据所述终端群组内的终端对应的会话管理功能实体中，每个会话管理功能实体服务的所述终端群组内的终端的数量，确定所述第一会话管理功能 实体。
  15. 根据权利要求12至14中任一项所述的方法，其特征在于，所述方法还包括：
    所述策略控制功能实体向所述第一会话管理功能实体发送第二指示信息，所述第二指示信息用于指示所述第一会话管理功能实体选择用于所述终端群组内的第二终端进行通信的用户面功能实体，所述第二终端为所述终端群组内的对应所述第一会话管理功能实体的终端。
  16. 根据权利要求12至15中任一项所述的方法，其特征在于，所述方法还包括：
    所述策略控制功能实体向目标网元发送通知消息，所述通知消息包括所述终端群组信息、所述第一会话管理功能实体的地址信息，所述通知消息用于指示所述目标网元将所述第一会话管理功能实体插入到所述终端群组内的第三终端的会话，以及指示所述第一会话管理功能实体选择用于所述第三终端进行通信的用户面功能实体；
    其中，所述目标网元为第二会话管理功能实体或接入与移动性管理功能实体，所述第三终端为所述终端群组内的对应所述目标网元的终端。
  17. 一种装置，其特征在于，包括：处理单元和通信单元，所述通信单元用于接收终端群组信息；
    所述处理单元，用于根据终端群组信息，确定所述终端群组内的终端接入的用户面功能实体；
    所述处理单元，还用于根据所述用户面功能实体，确定目标用户面功能实体，所述目标用户面功能实体用于所述终端群组内的终端之间的通信。
  18. 根据权利要求17所述的装置，其特征在于，所述通信单元还用于：
    向所述目标用户面功能实体发送第一通知消息，所述第一通知消息包括第一终端的隧道信息，所述第一终端接入的用户面功能实体不同于所述目标用户面功能实体。
  19. 根据权利要求18所述的装置，其特征在于，所述通信单元，还用于：
    向所述第一终端接入的基站发送第二通知消息，所述第二通知消息包括所述目标用户面功能实体的隧道信息。
  20. 根据权利要求17至19中任一项所述的装置，其特征在于，所述通信单元，还用于：
    接收来自策略控制功能实体的第一指示信息，所述第一指示信息用于指示所述第一会话管理功能实体选择用于所述终端群组内的终端进行通信的用户面功能实体。
  21. 根据权利要求17至19中任一项所述的装置，其特征在于，所述通信单元，还用于：
    接收来自策略控制功能实体的第二指示信息，所述第二指示信息用于指示所述第一会话管理功能实体选择用于所述终端群组内的第二终端进行通信的用户面功能实体，所述第二终端为所述终端群组内的对应所述第一会话管理功能实体的终端；
    所述处理单元根据所述用户面功能实体确定目标用户面功能实体，具体包括：根据所述第二终端接入的用户面功能实体，确定所述目标用户面功能实体。
  22. 根据权利要求21所述的装置，其特征在于，所述通信单元，还用于：
    接收来自目标网元的第一请求消息，所述第一请求消息用于请求所述第一会话管理功能实体选择所述终端群组内的第三终端进行通信的用户面功能实体，所述第三终端为所述终端群组内的对应所述目标网元的终端；
    所述处理单元，还用于：确定所述目标用户面功能实体，为所述第三终端进行通信 的用户面功能实体；
    其中，所述目标网元为第二会话管理功能实体或接入与移动性管理功能实体。
  23. 根据权利要求17至19中任一项所述的装置，其特征在于，所述通信单元，还用于：
    接收来自目标网元的第二请求消息，所述第二请求消息用于请求所述第一会话管理功能实体选择所述终端群组内的第三终端进行通信的用户面功能实体，所述第三终端为所述终端群组内的对应所述目标网元的终端；
    所述处理单元根据所述用户面功能实体确定目标用户面功能实体，具体包括：根据第二终端接入的用户面功能实体，确定所述目标用户面功能实体，所述第二终端为所述终端群组内的对应所述第一会话管理功能实体的终端；
    其中，所述目标网元为第二会话管理功能实体或接入与移动性管理功能实体。
  24. 根据权利要求17至23中任一项所述的装置，其特征在于，所述通信单元，还用于：接收来自控制面功能实体或应用服务器的所述终端群组信息。
  25. 根据权利要求17至24中任一项所述的装置，其特征在于，所述终端群组信息包括所述终端群组的标识和所述终端群组内的终端的标识；
    所述处理单元，还用于：
    将所述目标用户面功能实体和所述终端群组的标识，存储至所述终端群组内的终端的上下文，所述终端群组内的终端的上下文用于所述第一会话管理功能实体从所述终端群组内的终端的上下文，获取所述目标用户面功能实体；或者，
    本地存储所述目标用户面功能实体和所述终端群组的标识之间的对应关系，所述对应关系用于所述第一会话管理功能实体从所述对应关系获取所述目标用户面功能实体。
  26. 一种装置，其特征在于，包括：处理单元和通信单元；
    所述通信单元，用于获取终端群组信息，所述终端群组信息至少包括所述终端群组内的终端的标识；
    所述处理单元，用于根据所述终端群组内的终端的标识，确定第一会话管理功能实体，所述第一会话管理功能实体用于选择目标用户面功能实体，所述目标用户面功能实体用于所述终端群组内的终端之间的通信。
  27. 根据权利要求26所述的装置，其特征在于，所述处理单元根据所述终端群组内的终端的标识确定第一会话管理功能实体，具体包括：
    根据所述终端群组内的终端的标识，确定所述终端群组内的终端接入的会话管理功能实体；
    根据所述终端接入的会话管理功能实体，确定所述第一会话管理功能实体。
  28. 根据权利要27所述的装置，其特征在于，所述处理单元根据所述终端接入的会话管理功能实体确定所述第一会话管理功能实体，具体包括：
    根据所述终端群组内的终端对应的会话管理功能实体中，每个会话管理功能实体服务的所述终端群组内的终端的数量，确定所述第一会话管理功能实体。
  29. 根据权利要求26至28中任一项所述的装置，其特征在于，所述通信单元，还用于：
    向所述第一会话管理功能实体发送第二指示信息，所述第二指示信息用于指示所述第一会话管理功能实体选择用于所述终端群组内的第二终端进行通信的用户面功能实体，所述第二终端为所述终端群组内的对应所述第一会话管理功能实体的终端。
  30. 根据权利要求26至29中任一项所述的装置，其特征在于，所述通信单元，还用于：
    向目标网元发送通知消息，所述通知消息包括所述终端群组信息、所述第一会话管理功能实体的地址信息，所述通知消息用于指示所述目标网元将所述第一会话管理功能实体插入到所述终端群组内的第三终端的会话，以及指示所述第一会话管理功能实体选择用于所述第三终端进行通信的用户面功能实体；
    其中，所述目标网元为第二会话管理功能实体或接入与移动性管理功能实体，所述第三终端为所述终端群组内的对应所述目标网元的终端。
  31. 一种装置，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述装置运行时，所述处理器执行所述存储器存储的该计算机执行指令，以使所述装置执行如权利要求1-11任一项所述的通信方法。
  32. 一种装置，其特征在于，包括：处理器和存储器；所述存储器用于存储计算机执行指令，当所述装置运行时，所述处理器执行所述存储器存储的该计算机执行指令，以使所述装置执行如权利要求12-16任一项所述的通信方法。
  33. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-11任一项，或12-16任一项所述的通信方法。
  34. 一种计算机程序产品，其特征在于，所述计算机程序产品中存储有指令，当其在计算机上运行时，使得计算机可以执行如权利要求1-11任一项，或12-16任一项所述的通信方法。
PCT/CN2018/107580 2017-09-30 2018-09-26 一种通信方法、装置及系统 WO2019062754A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
BR112020006069-0A BR112020006069A2 (pt) 2017-09-30 2018-09-26 método de comunicação, aparelho, e sistema
EP18861939.9A EP3675531B1 (en) 2017-09-30 2018-09-26 Communication method, apparatus and computer-readable storage medium
EP23199575.4A EP4336886A3 (en) 2017-09-30 2018-09-26 Communication method, apparatus, and system
US16/824,267 US11564284B2 (en) 2017-09-30 2020-03-19 Communication method, apparatus, and system for determining a target user plan function entity
US18/153,928 US20230171848A1 (en) 2017-09-30 2023-01-12 Communication Method, Apparatus, and System

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710923300.0A CN109600719B (zh) 2017-09-30 2017-09-30 一种通信方法、装置及系统
CN201710923300.0 2017-09-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/824,267 Continuation US11564284B2 (en) 2017-09-30 2020-03-19 Communication method, apparatus, and system for determining a target user plan function entity

Publications (1)

Publication Number Publication Date
WO2019062754A1 true WO2019062754A1 (zh) 2019-04-04

Family

ID=65900837

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107580 WO2019062754A1 (zh) 2017-09-30 2018-09-26 一种通信方法、装置及系统

Country Status (5)

Country Link
US (2) US11564284B2 (zh)
EP (2) EP3675531B1 (zh)
CN (2) CN113596744B (zh)
BR (1) BR112020006069A2 (zh)
WO (1) WO2019062754A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11832341B2 (en) 2019-05-03 2023-11-28 Ofinno, Llc Group communication service request

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113473391B (zh) * 2017-10-30 2022-10-25 华为技术有限公司 会话建立方法、设备及系统
CN114666859A (zh) * 2018-01-08 2022-06-24 瑞典爱立信有限公司 用于选择服务无线通信设备的会话管理实体的方法和装置
CN111010744B (zh) * 2018-10-08 2022-05-13 华为技术有限公司 建立会话的方法和装置以及发送报文的方法和装置
US11343653B2 (en) * 2019-01-15 2022-05-24 Ofinno, Llc Session establishment to join a group communication
EP3716243A1 (en) * 2019-03-28 2020-09-30 Volkswagen Aktiengesellschaft Methods, apparatuses and computer programs for vehicles and for a base station of a mobile communication system
CN110366119B (zh) * 2019-07-18 2021-09-17 中国联合网络通信集团有限公司 一种网络群组消息管理方法、装置和系统
CN112448875B (zh) * 2019-08-28 2023-10-20 华为技术有限公司 通信处理方法、通信处理装置以及系统
CN112449394B (zh) * 2019-08-28 2022-09-16 中国联合网络通信集团有限公司 一种数据传输方法和核心网设备
CN112584458B (zh) * 2019-09-30 2023-01-06 华为技术有限公司 数据传输方法及装置
CN112584327B (zh) * 2019-09-30 2022-04-05 华为技术有限公司 一种更新用户面路径的方法、装置及系统
MX2022003847A (es) * 2019-10-04 2022-04-29 Ntt Docomo Inc Aparato de control de acceso y aparato de plano de usuario.
CN110602803B (zh) * 2019-10-15 2020-12-08 广州爱浦路网络技术有限公司 一种限制用户终端接入upf的方法
CN114079674B (zh) * 2020-08-10 2023-02-21 大唐移动通信设备有限公司 一种数据处理方法、用户面功能及装置
CN112637896B (zh) * 2020-12-10 2023-04-07 中国联合网络通信集团有限公司 最大聚合速率的分配方法、会话管理功能实体及终端
CN115086886B (zh) * 2021-03-10 2023-10-13 大唐移动通信设备有限公司 群组内点到多点通信业务的话权控制方法、装置及介质
CN113111647B (zh) * 2021-04-06 2022-09-06 北京字跳网络技术有限公司 信息的处理方法、装置、终端和存储介质
CN115250209A (zh) * 2021-04-08 2022-10-28 华为技术有限公司 一种控制用户设备接入网络的方法、装置及设备
CN114158079B (zh) * 2021-12-21 2023-04-18 中国联合网络通信集团有限公司 通信方法和装置、电子设备、计算机可读介质
CN116419429A (zh) * 2021-12-30 2023-07-11 华为技术有限公司 通信方法和装置
CN116939709A (zh) * 2022-03-31 2023-10-24 大唐移动通信设备有限公司 数据传输方法、设备、装置及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102413546A (zh) * 2011-12-01 2012-04-11 大唐移动通信设备有限公司 一种核心网设备的选择方法和设备
CN103781119A (zh) * 2014-01-16 2014-05-07 中国联合网络通信集团有限公司 一种选择mgw的方法和装置
CN106937271A (zh) * 2015-12-31 2017-07-07 电信科学技术研究院 终端设备的移动性管理方法及服务网关的控制面功能实体
CN107071746A (zh) * 2016-01-21 2017-08-18 福特全球技术公司 用于经由专用短程通信的车辆群组通信的系统和方法

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7386000B2 (en) * 2001-04-17 2008-06-10 Nokia Corporation Packet mode speech communication
US7408948B2 (en) * 2001-04-17 2008-08-05 Nokia Corporation Packet mode speech communication
US7782875B2 (en) * 2002-06-18 2010-08-24 Nokia Corporation Megaco protocol with group termination
FI116183B (fi) * 2004-02-13 2005-09-30 Teliasonera Finland Oyj Pakettidatapohjainen ryhmäviestintä
CN102244854B (zh) * 2010-05-10 2016-03-30 中兴通讯股份有限公司 Mtc组选择分组数据网网关的方法及移动性管理网元
CN103609147B (zh) * 2012-10-25 2019-08-16 华为技术有限公司 集群通信系统、集群服务器、接入网络以及集群通信方法
US20170171752A1 (en) * 2015-12-14 2017-06-15 Qualcomm Incorporated Securing signaling interface between radio access network and a service management entity to support service slicing
CN106851856B (zh) * 2016-12-23 2019-04-09 电信科学技术研究院有限公司 一种基于移动中继的无线通信建立方法及网络设备
US11228949B2 (en) * 2017-01-06 2022-01-18 Samsung Electronics Co., Ltd. Intra-RAT handover for next generation system
US10448239B2 (en) * 2017-02-06 2019-10-15 Qualcomm Incorporated Mechanism to enable optimized user plane anchoring for minimization of user plane relocation due to user equipment mobility
CN108419270B (zh) * 2017-02-10 2021-08-06 中兴通讯股份有限公司 一种业务分流实现方法及装置
US10779345B2 (en) * 2017-03-20 2020-09-15 Qualcomm Incorporated User plane relocation techniques in wireless communication systems
CN108632904B (zh) * 2017-03-24 2019-09-17 电信科学技术研究院 一种通信方法及设备
US20210058748A1 (en) * 2017-03-24 2021-02-25 Apple Inc. Systems and methods for group based services provisioning
CN107018542A (zh) * 2017-03-27 2017-08-04 中兴通讯股份有限公司 网络系统中状态信息的处理方法、装置及存储介质
JP2019004409A (ja) * 2017-06-19 2019-01-10 シャープ株式会社 端末装置、コアネットワーク内の装置、データネットワーク内の装置、及び通信制御方法
KR102412288B1 (ko) * 2017-08-14 2022-06-23 삼성전자 주식회사 제 3자 응용 서버에서 단말의 무선 연결 타입 변경을 확인하는 방법
EP3689090A4 (en) * 2017-09-28 2021-05-19 ZTE Corporation MOBILE NETWORK INTERACTION OFFICER
WO2019064531A1 (ja) * 2017-09-29 2019-04-04 富士通株式会社 基地局、端末、処理方法および無線通信システム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102413546A (zh) * 2011-12-01 2012-04-11 大唐移动通信设备有限公司 一种核心网设备的选择方法和设备
CN103781119A (zh) * 2014-01-16 2014-05-07 中国联合网络通信集团有限公司 一种选择mgw的方法和装置
CN106937271A (zh) * 2015-12-31 2017-07-07 电信科学技术研究院 终端设备的移动性管理方法及服务网关的控制面功能实体
CN107071746A (zh) * 2016-01-21 2017-08-18 福特全球技术公司 用于经由专用短程通信的车辆群组通信的系统和方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11832341B2 (en) 2019-05-03 2023-11-28 Ofinno, Llc Group communication service request

Also Published As

Publication number Publication date
EP3675531B1 (en) 2023-11-01
CN113596744A (zh) 2021-11-02
EP3675531A4 (en) 2020-07-08
EP3675531C0 (en) 2023-11-01
CN113596744B (zh) 2023-11-03
CN109600719A (zh) 2019-04-09
US20200221540A1 (en) 2020-07-09
US20230171848A1 (en) 2023-06-01
BR112020006069A2 (pt) 2020-10-06
CN109600719B (zh) 2021-07-09
EP3675531A1 (en) 2020-07-01
EP4336886A2 (en) 2024-03-13
US11564284B2 (en) 2023-01-24
EP4336886A3 (en) 2024-05-29

Similar Documents

Publication Publication Date Title
WO2019062754A1 (zh) 一种通信方法、装置及系统
WO2020168840A1 (zh) 网络节点选择方法及装置
US20200214065A1 (en) User equipment category signaling in an lte-5g configuration
WO2019196643A1 (zh) 通信的方法和通信装置
WO2019184651A1 (zh) 一种通信方法及装置
US10893574B2 (en) Packet data unit session release method and network entity performing the same
WO2021057794A1 (zh) 配置业务的方法、通信装置和通信系统
JP7083925B2 (ja) レート制御方法、装置、およびシステム
US20230337317A1 (en) Method for small data transmission
WO2018202008A1 (zh) 一种会话管理方法、网络设备和通信系统
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2022022322A1 (zh) 访问本地网络的方法和装置
WO2021160096A1 (zh) 一种私网签约信息更新方法及装置
WO2021163894A1 (zh) 一种基于中继的通信方法及装置
KR20240060670A (ko) 통신 방법 및 장치
WO2023052220A1 (en) Method, apparatus and computer program
WO2021147672A1 (zh) 会话处理方法及通信装置
WO2021189496A1 (zh) 用于网络切片的数据传输方法及设备
CN114071649A (zh) 访问本地网络的方法和装置
WO2022188156A1 (zh) 通信方法和通信装置
WO2024208017A1 (zh) 通信方法、通信装置及通信系统
US20230114449A1 (en) Method and arrangements relating to group transmission in a wireless communication network
US20240251462A1 (en) Communication method and apparatus
WO2024140620A1 (zh) 通信方法、装置及系统
WO2024074148A1 (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: 18861939

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018861939

Country of ref document: EP

Effective date: 20200325

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020006069

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112020006069

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200326